AM3517: U-boot looking for a boot.scr file

Which EZSDK and version and MPU platform are you working with?

Regards,

Michael T

Dear Micheal,

I didn't Get EZSDK..as I am using Code sourcery Toolchain to compile the Source code for x-loader and u-boot. And i Have Standard board shipped by TechNixon AM3517.

Thanks for your reply !!!!!!!!

Hrishikesh.

I am not sure whether this board is directly supported by TI SDK. You may want to check with TechNixon support here.

Although I can help you to debug this issue -

Looking at your description, it looks like, x-loader is able to find the u-boot image and execution jumped to u-boot, but there seems to be some issue with your DDR access.

My suspect would be,

   - DDR settings?

  - Connect any debugger (if you have any) and then try to R/W on DDR once x-loader executes.

  - OR you can write some instruction in x-loader itself to R/W on DDR and see everything is as per expectation.

Thanks,

Vaibhav

Dear Sir,

Thanks for your reply !!! I have an Android Image shipped along with the board which executes perfectly..and the board comes up..so i think there is no Issue with The ddr settings.

I have placed the Image in Sd card using win32diskmanager..and boots.

Can you confirm ..the nand i am using is 256 mb ..one page size is 128k...i am placing x-loader at 0x00000000 and then u-boot loader at 0x20000 or tried at 0x80000...

using flash tool to burn images...

but still the Issue persist.

Thanks and Regard's

hrishikesh.

Could you post log from Flash tool?

regards,

Michael

You can also try from u-boot prompt to flash the images to NAND Flash, please refer to the UserGuide - http://processors.wiki.ti.com/index.php/AM35x-OMAP35x-PSP_04.02.00.07_UserGuide#NAND

Thanks,

Vaibhav

Dear Micheal,

Output of Flash tool when i have downloaded the MLO image to Location 0x00

¯     -stdout
¯     -omap 3
¯     -no_force_package_alignment
¯     -com 1
¯     -t 60
¯     -p EVM_MDDR_MICRON_2G_EMIF
¯     -2
¯     chip_download NANDINFO1BITBOOT F:\Linux\Images final\Working Images\MLO
¯ Leaving parameter file:temp_script.txt
¯ @temp_script.txt
¯ Looking for device (omap com1)
¯ Please turn off device, then turn it on again
¯ Awaiting ASIC id
¯ AsicId items 04
¯ AsicId id            01 05  01  34 30 07 58
¯ AsicId secure_mode    13 02  01  00
¯ AsicId public_id     12 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
¯ AsicId root_key_hash    14 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
¯ Searching 2nd for: EVM_MDDR_MICRON_2G_EMIF 343007 58 GP
¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_2g.2nd
¯ Entering parameter file:omapflash2nd.txt at line: 15
¯     -pheriphalboot_reopen
¯ Reading board configuration file Targets\Configurations\configuration_am35xxevm_micron_2g.txt
¯ Reading definition file .\targets\definitions\definitions_omap3.txt
¯     -board_config Targets\Configurations\configuration_am35xxevm_micron_2g.txt
¯ Leaving parameter file:omapflash2nd.txt
¯ Sending size of second file (0x00006804 bytes)
¯ Transferring second file to target (0x6804 bytes)
¯ Closing boot connection
¯ Found device (omap com1)
¯ Waiting for 2nd
¯ Found 2nd
¯ Looking for a driver for 'NANDINFO1BITBOOT'
¯ chip_driver NANDINFO1BITBOOT Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin gpmc 0x6E000000 cs 0 address 0x30000000 bberase 0 onfi 0 bpp 2048 sbpp 64 ppb 64 bpl 4096 l 1 acv 0x23 f 0x0019 e‹s...
¯ Downloading driver
¯ Downloading 'Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin'

¯ Sending data (41008 bytes) :::::::::::::::..... [32764]
¯ Sending data (41008 bytes) :::::::::::::::::::: [41008]
¯ Sending data (41008 bytes) :::::::::::::::::::: [41008]
      Interface 'OMAPFLASH DRIVER v5'
      Driver 'NAND ONFI 16/8 BIT'
      Driver configuration: gpmc = 0x6E000000
      Driver configuration: cs = 0x00000000
      Driver configuration: address = 0x30000000
      Driver configuration: bberase = 0x00000000
      Driver configuration: onfi = 0x00000000
      Driver configuration: bpp = 0x00000800
      Driver configuration: sbpp = 0x00000040
      Driver configuration: ppb = 0x00000040
      Driver configuration: bpl = 0x00001000
      Driver configuration: l = 0x00000001
      Driver configuration: acv = 0x00000023
      Driver configuration: f = 0x00000019
      Driver configuration: eccoffset = 0x00000002
      NAND HW ECC
      NAND BCH Mode = 0
      NAND HWECC offset = 2, size = 12
      NAND NONEv0 VENDOR 0x00 UNKNOWN
      NAND 16 BIT DEVICE 0x00 UNKNOWN
      NAND NAND CYCLES 0x23 (3 ROW, 2 COLUMN)
      NAND 2048 BYTES/PAGE (SPARE 64)
      NAND 64 PAGES/BLOCK (131072 BYTES/BLOCK)
      NAND 4096 BLOCKS/UNIT (536870912 BYTES/UNIT)
      NAND 0 BIT(S) ECC REQUIRED
      NAND 512 MB TOTAL SIZE
      NAND ONFI DRIVER INIT COMPLETE
¯ Downloading complete
¯ Elapsed time: 0:03.742 (13669 bytes/s)
¯ End loading driver
¯ Downloading
¯ Downloading 'F:\Linux\Images final\Working Images\MLO'

¯ Sending data (13376 bytes) :::::::::::::::::::: [13376]
¯ Sending data (13376 bytes) :::::::::::::::::::: [13376]
¯ Downloading complete
¯ Elapsed time: 0:01.213 (13376 bytes/s)
¯ Elapsed time: 0:00.000

Console program success, exit code: 0

Output of Flash Tool ...downloading Image u-boot to loaction 0x80000.

¯     -stdout
¯     -omap 3
¯     -no_force_package_alignment
¯     -com 1
¯     -t 60
¯     -p EVM_MDDR_MICRON_2G_EMIF
¯     -2
¯     chip_download NANDINFOSWECC F:\Linux\Images final\Working Images\u-boot.bin
¯ Leaving parameter file:temp_script.txt
¯ @temp_script.txt
¯ Looking for device (omap com1)
¯ Please turn off device, then turn it on again
¯ Awaiting ASIC id
¯ AsicId items 04
¯ AsicId id            01 05  01  34 30 07 58
¯ AsicId secure_mode    13 02  01  00
¯ AsicId public_id     12 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
¯ AsicId root_key_hash    14 15  01  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
¯ Searching 2nd for: EVM_MDDR_MICRON_2G_EMIF 343007 58 GP
¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_2g.2nd
¯ Entering parameter file:omapflash2nd.txt at line: 15
¯     -pheriphalboot_reopen
¯ Reading board configuration file Targets\Configurations\configuration_am35xxevm_micron_2g.txt
¯ Reading definition file .\targets\definitions\definitions_omap3.txt
¯     -board_config Targets\Configurations\configuration_am35xxevm_micron_2g.txt
¯ Leaving parameter file:omapflash2nd.txt
¯ Sending size of second file (0x00006804 bytes)
¯ Transferring second file to target (0x6804 bytes)
¯ Closing boot connection
¯ Found device (omap com1)
¯ Waiting for 2nd
¯ Found 2nd
¯ Looking for a driver for 'NANDINFOSWECC'
¯ chip_driver NANDINFOSWECC Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin gpmc 0x6E000000 cs 0 address 0x30000000 bberase 0 onfi 0 bpp 2048 sbpp 64 ppb 64 bpl 4096 l 1 acv 0x23 f 0x0019 swec‹s@ú2...
¯ Downloading driver
¯ Downloading 'Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin'

¯ Sending data (41008 bytes) :::::::::::::::..... [32764]
¯ Sending data (41008 bytes) :::::::::::::::::::: [41008]
¯ Sending data (41008 bytes) :::::::::::::::::::: [41008]
      Interface 'OMAPFLASH DRIVER v5'
      Driver 'NAND ONFI 16/8 BIT'
      Driver configuration: gpmc = 0x6E000000
      Driver configuration: cs = 0x00000000
      Driver configuration: address = 0x30000000
      Driver configuration: bberase = 0x00000000
      Driver configuration: onfi = 0x00000000
      Driver configuration: bpp = 0x00000800
      Driver configuration: sbpp = 0x00000040
      Driver configuration: ppb = 0x00000040
      Driver configuration: bpl = 0x00001000
      Driver configuration: l = 0x00000001
      Driver configuration: acv = 0x00000023
      Driver configuration: f = 0x00000019
      Driver configuration: swecc = 0x00000001
      Driver configuration: eccoffset = 0x00000028
      NAND SW ECC
      NAND BCH Mode = 0
      NAND HWECC offset = 40, size = 12
      NAND NONEv0 VENDOR 0x00 UNKNOWN
      NAND 16 BIT DEVICE 0x00 UNKNOWN
      NAND NAND CYCLES 0x23 (3 ROW, 2 COLUMN)
      NAND 2048 BYTES/PAGE (SPARE 64)
      NAND 64 PAGES/BLOCK (131072 BYTES/BLOCK)
      NAND 4096 BLOCKS/UNIT (536870912 BYTES/UNIT)
      NAND 0 BIT(S) ECC REQUIRED
      NAND 512 MB TOTAL SIZE
      NAND ONFI DRIVER INIT COMPLETE
¯ Downloading complete
¯ Elapsed time: 0:03.747 (13669 bytes/s)
¯ End loading driver
¯ Downloading
¯ Downloading 'F:\Linux\Images final\Working Images\u-boot.bin'

¯ Sending data (193416 bytes) :::................. [32764]
¯ Sending data (193416 bytes) ::::::.............. [65528]
¯ Sending data (193416 bytes) ::::::::::.......... [98292]
¯ Sending data (193416 bytes) :::::::::::::....... [131056]
¯ Sending data (193416 bytes) ::::::::::::::::.... [163820]
¯ Sending data (193416 bytes) :::::::::::::::::::: [193416]
¯ Sending data (193416 bytes) :::::::::::::::::::: [193416]
¯ Downloading complete
¯ Elapsed time: 0:16.971 (12088 bytes/s)
¯ Elapsed time: 0:00.000

Console program success, exit code: 0


Output on Hyper terminal :

Texas Instruments X-Loader 1.47 (May  9 2011 - 16:49:13)
Booting from nand . . .
Starting OS Bootloader...

Bootloader stops at ...last Line.

Thanks and Regard's

Hrishikesh.

Hello,

I see that even if I just loas u-boot (to address 0), then I get u-boot console...

So I don't understand:

1. Is u-boot sufficient for serial boot ?

2.Doesn't MLO initialize DDR, or is it that u-boot initalize it too ?

3. How is it that u-boot which is 447KBytes can get into sdram which is 64KByte ??

Thank you ,

Ran