Using Ridgerun SDK. I see the first ubl load output...but not the uboot. Seems to be rebooting to the ubl load over and over.
1. Set jumpers to boot serial. I see "BOOTME" 115k
2. sfh_DM35.exe -nanderase
3. sfh_DM35.exe -nandflash ubl bootloader
4. Change jumpers to boot from NAND and I see the following repeated forever:
Why is the board not booting uboot and rebooting the ubl code? Any help would be great! Also, any further info you need...I'll be happy to give.
Customized by RidgeRunTI UBL Version: 1.20, Flash type: NANDBooting Catalog Boot LoaderBootMode = NANDStarting NAND Copy...Valid MagicNum found. DONEChip initialization passed!Customized by RidgeRunTI UBL Version: 1.20, Flash type: NANDBooting Catalog Boot LoaderBootMode = NANDStarting NAND Copy...Valid MagicNum found.
Are using the UBL generated by the SDK with the serial flasher (sfh_DM35.exe), or you are using the UBL image that comes with the serial flasher?
-- Miguel AguilarEmbedded Software EngineerRidgeRun Embedded Solutions
Thanks for the quick response!
I'm using the ubl made from the RidgeRun compile. In the DM355SDK738407/images directory there are the following files:
I'm using the ubl file below:
drwxrwxr-x 2 10002 10001 4096 2009-11-10 15:17 .
drwxrwxr-x 13 10002 10001 4096 2009-11-10 14:06 ..
-rwxr-xr-x 1 root root 180052 2009-11-10 14:46 bootloader
-rw-r--r-- 1 root root 182272 2009-11-10 14:46 bootloader.nandbin
-rw-r--r-- 1 root root 48831 2009-11-10 14:06 bspconfig
-rw-r--r-- 1 root root 147 2009-11-10 14:46 cmdline
-rw-r--r-- 1 root root 0 2009-11-10 14:46 fsimage
-rw-r--r-- 1 root root 0 2009-11-10 14:46 fsimage.uImage
lrwxrwxrwx 1 root root 7 2009-11-10 14:45 kernel -> vmlinux
-rw-r--r-- 1 root root 2727328 2009-11-10 14:46 kernel.uImage
-rwxr-xr-x 1 root root 180052 2009-11-10 12:12 tmp
-rwxr-xr-x 1 root root 13240 2009-11-10 14:46 ubl
-rw-r--r-- 1 root root 16384 2009-11-10 14:46 ubl.nandbin
-rwxr-xr-x 1 root root 180092 2009-11-10 14:46 upgrade_bootloader.bin
-rwxr-xr-x 1 root root 2727264 2009-11-10 14:45 vmlinux
The UBL built by the RR SDK doesn't work with the serial flasher, since this UBL was modified to look for Uboot is other nand block different from the one that is used by serial flasher, that's why it fails. So, you should use the UBL that is included in the serial flasher, and you can use the Uboot built by the SDK (DM355SDK738407/images/bootloader).
The SDK has a installer to flash the ubl, uboot, kernel, fs and some uboot environment variables. For instance, to install the UBL + Uboot you should use "make installbootloader". But to use this installer it must be a running Uboot in the Leopard, since the installer issues uboot commands in order to flash the images. So, the installer doesn't work for bricked boards.
Thanks! Got it!
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 (Nov 10 2009 - 11:58:56)
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Bad block table not found for chip 0
Bad block table written to 0x0ffa0000, version 0x01
Bad block table written to 0x0ff80000, version 0x01
*** Warning - bad CRC or NAND, using default environment
Davinci musb: using high speed
mtdparts variable not set, see 'help mtdparts'
ARM Clock :- 216MHz
DDR Clock :- 171MHz
Hit any key to stop autoboot: 0
Leopard Board #
I was actually reading your doc "DM355 SDK User Guide.pdf" and I saw that you did use the <path_sfh> for the ubl_DM35x_nand.bin file. I was doing this right when your email came. Your email was very helpful and I really appreciate your quick and very knowledgeable response! Thank you!