Having make the RR SDK for leopardboard,
I am now trying to deploy the system to target board.
The FAQ says to make sure uboot is running on /dev/ttyUSB0, I presume this is on the leopardboard.
Presently the leopardboard boots int the IP Cam demo as factory installed.
The minicom repeatedly shows "SetAlarmResetTrigger".
How do I put the leopardboard into the "Uboot" state?
Do I login to the board and run some command like "uboot xxxx" and quit minicom or
do I try the dip switches and reboot with the correct dip switch boot setting?
Appreciate any tips from experts here.
Thanks
Richard
Once you boot the board and starts the count down hit any key to be in Uboot state.
Thanks.
Seems to have uploaded the new uboot.
Note that I had to install lrzsz first
>apt-get install lrzsz
Also now using serial for "firmwire" upload, note that the text on make config for this option is different from the FAQ pages.
How do I know what is the ipaddress on the target leopardboard? or how to set it?
you can type printenv to see the ip address of the board or set it by typing
setenv ipaddr 192.168.1.100you can put whatever ip address you want I usually set something high so it would not conflict
Had the target leopardboard connected to my route with dhcp server and it seems make install discovered the ip addresses automagically.
So after make install, here is the output from the target board as shown on minicom
==
-Boot customized by RidgeRunU-Boot 2009.11 (Apr 23 2011 - 12:52:54) Cores: ARM 216 MHz DDR: 171 MHz I2C: ready DRAM: 128 MB NAND: 256 MiB Bad block table found at page 131008, version 0x01 Bad block table found at page 130944, version 0x01 nand_read_bbt: Bad block at 0x000000020000 nand_read_bbt: Bad block at 0x000000040000 nand_read_bbt: Bad block at 0x000000060000 nand_read_bbt: Bad block at 0x000000080000 nand_read_bbt: Bad block at 0x0000000c0000 nand_read_bbt: Bad block at 0x000000660000 Net: dm9000 Hit any key to stop autoboot: 0 Loading from nand0, offset 0xc0000 Skipping bad block 0x000c0000 ** Unknown image type DM355 LEOPARD # ====
running make install again will now work as it thinks everything is in order.
what can I do at this point?
thanks
i meant
running make install again will "not" work as it thinks everything is in order.
Try
make installkernel
to force kernel installation.
which tutorial you are following?
I am following this guide
designsomething.org/.../103.aspx
Tried to reinstall ubootloader after install kernel failed.
From Minicom
====
DM35x
initialization passed!
Customized by RidgeRun
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000002.
DONE
Jumping to entry point at 0x81080000.
U-Boot customized by RidgeRun
U-Boot 2009.11 (Apr 23 2011 - 12:52:54)
Cores: ARM 216 MHz
DDR: 171 MHz
I2C: ready
DRAM: 128 MB
NAND: 256 MiB
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
nand_read_bbt: Bad block at 0x000000020000
nand_read_bbt: Bad block at 0x000000040000
nand_read_bbt: Bad block at 0x000000060000
nand_read_bbt: Bad block at 0x000000080000
nand_read_bbt: Bad block at 0x0000000c0000
nand_read_bbt: Bad block at 0x000000660000
Net: dm9000
DM355 LEOPARD #
From host system
===
[root@optasia-desktop ~/DM355SDK840402]# make installbootloader
Ridgerun Linux SDK
Board configuration: Leopard Board
Installation system of uboot images over TFTP for host 192.168.1.75
Please be sure u-boot is running on port /dev/ttyS1 and none process (like minicom) is using it
u-boot port /dev/ttyS1
Performing handshake with u-boot...done.
Trying to identify NAND block size... detected 0x20000
Loading upgrade bootloader version...
Disabling boot command...
Uboot <= setenv bootcmd
Disabling autostart option...
Uboot <= setenv autostart no
Uboot <= saveenv
Loading bootloader...
Configuring the network...
Uboot <= setenv autoload no
Uboot <= dhcp
Uboot <= setenv serverip 192.168.1.75
Uboot <= mw.l 0x82000000 0xff 0x28001
Uboot <= tftp 0x82000000 upgrade_bootloader.bin.root.leopard
Running upgrade bootloader...
Uboot => go 0x82000000
Performing handshake with u-boot...
ERROR: failed to perform handshake with u-boot.
Be sure u-boot is active on port /dev/ttyS1 and you have terminal programs like minicom closed.
Exit: -1
make: *** [installbootloader] Error 255
[root@optasia-desktop ~/DM355SDK840402]#
anyone can please help?
Hi,
I am having the same problem. I got the make install to execute successfully, but when I got to boot the Leopardboard 355 I get the error:
picocom v1.4
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
noinit is : no
noreset is : yes
nolock is : yes
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv
Terminal ready
U-Boot 2009.11 (Apr 26 2011 - 19:48:01)
nand_read_bbt: Bad block at 0x0000000a0000
Hit any key to stop autoboot: 0
Loading from nand0, offset 0xc0000
Skipping bad block 0x000c0000
** Unknown image type
I've been having a lot of trouble with this board and can't seem to get it to work. I tried using:
and that didn't work either. I'm in the process of a 'make clean' and then 'make' to see if my kernel images were bad. I'm using TFTP to transfer images to the board, which I've also had trouble with, but when it does succesfully complete, I get the above error.
Any help would be greatly appreciated!
Thanks,
Billy
are you using the zImage or something like that? because uboot only works with uImage.
I am using the stock RR SDK, wouldnt that be uimage?
If not, how do I get hold of uImage?
Much obliged.
I was looking at the guide did you read this part :
"If you are installing for first time the software built by the SDK on the Leopard Board you MUST install the UBL and Uboot build by the SDK, because there are some features needed by the Uboot installer that the Uboot that comes preinstalled in the board doesn't support."
I think you still using the uboot from leopard board.
Hi Andre,
I have done "make installbootloader" bit.
Maybe that didnt get done correctly, there were a lot of outputs that seems to indicate it was done correctly.
How do I confirm that the installbootloader is done correctly?
Thanks & regards