Every time i try and run "make installbootloader" to upload the new RR SDK bootloader i get the following:
sudo make installbootloader
Ridgerun Linux SDK
Board configuration: Leopard Board
Installation system of uboot images over serial port /dev/ttyUSB0
Please be sure u-boot is running on port /dev/ttyUSB0 and none process (like minicom) is using it
u-boot port /dev/ttyUSB0
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
Uboot <= loady 0x82000000
sh: sz: not found
Running upgrade bootloader...
Uboot => go 0x82000000
Uboot <= loady 0x81600000
Uboot <= loady 0x81700000
Uboot <= nand scrub
Uboot <= nand write.ubl 0x81600000 0x20000 0x20000
-------------> Error: didn't match [Leopard Board] Saving bootloader...
Uboot <= nand write 0x81700000 40000 0x400000
Note the error at the end. I always seem to get this and i then have to recover the bricked board each time.
Anyone know how i can solve this error?
Looks like you are missing one package:
sudo apt-get install lrzsz
Embedded Software Engineer, RidgeRun
I tried what you suggested and that seems to have solved that problem. Now i have another. Everything appeared to flash correctly, although it took a REALLY long time to flash the kernel. Over an hour.
Now when it boots up it doesn't seem to respond to the boot command, i get this:
DM35x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Jumping to entry point at 0x81080000.
U-Boot 1.2.0 (Feb 24 2010 - 22:13:23)
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Bad block tBad block table found at page 130944, version 0x01
Davinci musb: using high speed
ARM Clock :- 216MHz
DDR Clock :- 171MHz
Leopard Board # boot
Leopard Board #
Not to worry i fixed the problem. I was running Ubuntu as a vmware image and connecting the USB to serial adapter through the virtual machine. While this appeared to be working for the most part it was obviously causing some issues. I installed Ubuntu on another machine and ran directly and had no problems.