TI Flash Tool v1.6.0.0 - AM3703 - Waiting for 2nd

Jim Esposito

Hello All,

I am getting inconsistent performance out of the TI Flash Tool across the past couple days, with seemingly the same settings.

I am attempting to write my MLO.bin and u-boot.bin to 0x0h and 0x80000h respectively in two separate operations.

I was able to do both files a few times a couple days ago, but am having trouble repeating the process on not only the same device, but others as well.

The current error message I am seeing is as follows, at the end of this block of output text:

¯     -stdout
¯     -omap 3
¯     -no_force_package_alignment
¯     -com 3
¯     -t 60
¯     -p CUSTOM_AM37XX_BOARD
¯     -2
¯     chip_download NAND1BITBOOT C:\Users\Jim\Desktop\Nano NXT - Programming Deliverables - Rev A\MLO.bin
¯ Leaving parameter file:temp_script.txt
¯ @temp_script.txt
¯ Looking for device (omap com3)
¯ Please turn off device, then turn it on again
¯ Awaiting ASIC id
¯ AsicId items 04
¯ AsicId id        	01 05  01  36 30 07 07 
¯ 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_AM37XX_BOARD 363007 07 GP 
¯ Loading second file Targets\2nd-Downloaders\dnld_startup_omap3_gp_1g.2nd
¯ Entering parameter file:omapflash2nd.txt at line: 9
¯     -pheriphalboot_reopen
¯ Reading board configuration file Targets\Configurations\configuration_custom_am37xx.txt
¯ Reading definition file .\targets\definitions\definitions_omap3.txt
¯     -board_config Targets\Configurations\configuration_custom_am37xx.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 com3)
¯ Waiting for 2nd
¯ Unknown status message 'OCAY: 2nd started?' during peripheral boot (waiting for 2nd)

Console program failed, exit code: 2

My NAND device is a Micron MT29F8G08ADBDA, a 1GB SLC part

I have made the following changes for TI Flash Tool to work with my setup:

omapflsah2nd.txt

Change line #9 from “2g” to “1g” for expected part size

configuration_custom_am37xx.txt

Change the section “# NAND on CS0” to the following:

WAIT_N 0x1000
WRITE GPMC_CONFIG7_0 0x00000000
WRITE GPMC_CONFIG1_0 0x00000800
WRITE GPMC_CONFIG2_0 0x00090900
WRITE GPMC_CONFIG3_0 0x00090902
WRITE GPMC_CONFIG4_0 0x07020702
WRITE GPMC_CONFIG5_0 0x0008080A
WRITE GPMC_CONFIG6_0 0x000002CF
WRITE GPMC_CONFIG7_0 0x00000C70
WAIT_N 0x2000

In-Program Settings

Choose Target: Custom AM37xx Board
Select Target Connection Type: UART
Port: <com port of serial connection>
Choose the Desired Memory Type: NAND
ECC Style: HWECC
ONFI Compliant NAND? Checked
Error Correction: 1 bit ECC
1-Bit ECC Layout: X-Loader / U-Boot
Choose Operation Parameters: Download
Offset (MLO.bin): 0x0h
Offset (u-boot.bin): 0x80000h

I am trying to get suggestions for where to look at next to resolve my error. Since I have verified all my above settings, I am suspecting possibly my PC's state has changed, but I am not having any luck finding something that might be interfering with the COM3 port.

Compounding my confusion over this, is that the entire setup worked the other day the first try. Any advice on where to look would be appreciated, and please let me know if you need any other details!

--Jim--

over 10 years ago

0 Jim Esposito over 10 years ago

Prodigy 20 points

If it helps, the following update:

After rebooting my machine, I was able to, upon running the program the first time, connect to and program both the MLO and u-boot on both the master and slave units of my product.

I then closed the program, performed other operations on my PC, then plugged in a new unit and tried the same operations. I get the following error now:

¯     -stdout
¯     -omap 3
¯     -no_force_package_alignment
¯     -com 3
¯     -t 60
¯     -p CUSTOM_AM37XX_BOARD
¯     -2
¯     chip_download NAND1BITBOOT C:\Users\Jim\Desktop\Nano NXT - Programming Deliverables - Rev A\MLO.bin
¯ Leaving parameter file:temp_script.txt
¯ @temp_script.txt
¯ Looking for device (omap com3)
¯ Please turn off device, then turn it on again
¯ Awaiting ASIC id
¯ Awaiting ASIC id
¯ AsicId items 04
¯ AsicId id        	01 05  01  36 30 07 07 
Console program aborted or crashed, exit code: -1073741819

Afterwards, I have even tried returning to the original product that worked just minutes ago, and get the same error as above.

Could it be the Flash Tool is not properly shutting down after it's first run, or some 'service' or sorts is stuck in a certain state when the program exits for the first time, and cannot be re-initialized correctly afterwards? Perhaps something with my COM3 port? Even though the tool does not report any error using the port, perhaps my use of that port for other operations leaves the port in a certain state?