I am using a custom Board with discrete Micron NAND-Flash 128MByte=1GB. So what I did is changed this line in omapflash2nd.txt
"CUSTOM_OMAP35XX_BOARD 343007 57 GP Targets\2nd-Downloaders\dnld_startup_omap3_gp_1g.2nd -pheriphalboot_reopen -board_config Targets\Configurations\configuration_custom_omap35xx.txt"
I set to NAND, SWECC, Erase region c0000 20000 (as this is the bootenvironment for test)
This ends up with:
¯ -stdout
¯ -omap 3
¯ -no_force_package_alignment
¯ -com 4
¯ -t 60
¯ -p CUSTOM_OMAP35XX_BOARD
¯ -2
¯ chip_erase NANDINFO1BITBOOT 00020000
¯ Leaving parameter file:temp_script.txt
¯ @temp_script.txt
¯ Looking for device (omap com4)
¯ Please turn off device, then turn it on again
¯ Awaiting ASIC id
¯ AsicId items 04
¯ AsicId id 01 05 01 34 30 07 57
¯ 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: CUSTOM_OMAP35XX_BOARD 343007 57 GP
¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_1g.2nd
¯ Entering parameter file:omapflash2nd.txt at line: 7
¯ -pheriphalboot_reopen
¯ Reading board configuration file Targets\Configurations\configuration_custom_omap35xx.txt
¯ Reading definition file .\targets\definitions\definitions_omap3.txt
¯ -board_config Targets\Configurations\configuration_custom_omap35xx.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 com4)
¯ Waiting for 2nd
¯ Unknown status message '?????????' during peripheral boot (waiting for 2nd)
Console program failed, exit code: 2
Question: Do I use the right 2nd - file ?
Currently my system is running on XLOADER that is very simular to EVM board, with the only difference, that UART3 keeps the interface for x-loader and uboot message