OMAP-L138 LCDK booting problem

Hi Gergely,

I tried the mentioned procedure several times, but the program stops at the "Waiting for SFT on the OMAP-L138..." line and when I finally ( I waited 30min ) abort it and switch back to NAND boot mode, the still does not boot. I tried flashing both from Ubuntu 12.04 and Windows 7 host computers.

What command are you using for SFH tool ?

Like,

sfh_OMAPL138.exe -flashType NAND -targetType OMAPL138 -p COM13 -flash_noubl u-boot-lcdk_ais.bin

That is the command I try to use on Ubuntu:
mono ./sfh_OMAP-L138.exe -targettype OMAPL138_LCDK -flashtype NAND -p /dev/ttyUSB0 -flash_noubl ./u-boot-lcdk_ais.bin

I specified NAND as a flashtype. The board is set to UART boot mode and I receive the BOOTME message ( both if I connect with putty and when I use the flash tool ).
I copied my terminal screen here:

mono ./sfh_OMAP-L138.exe -targettype OMAPL138_LCDK -flashtype NAND -p /dev/ttyUSB0 -flash_noubl ./u-boot-lcdk_ais.bin
-----------------------------------------------------
TI Serial Flasher Host Program for OMAP-L138
(C) 2012, Texas Instruments, Inc.
Ver. 1.67
-----------------------------------------------------


[TYPE] Single boot image
[BOOT IMAGE] ./u-boot-lcdk_ais.bin
[TARGET] OMAPL138_LCDK
[DEVICE] NAND
[NAND Block] 1

Attempting to connect to device /dev/ttyUSB0...
Press any key to end this program at any time.

(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 14372-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 1324-Byte section to address 0x80003824.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

Aborting program...


The abort arrived about 10 min later than the "Waiting for SFT", when I closed the program.

Could you try the following command.

./sfh_OMAP-L138.exe -targetType OMAPL138 -flashType NAND -p /dev/ttyUSB0 -flash_noubl ./u-boot-lcdk_ais.bin

I run the given command but got the same result as before:

./sfh_OMAP-L138.exe -targetType OMAPL138 -flashType NAND -p /dev/ttyUSB0 -flash_noubl ./u-boot-lcdk_ais.bin
-----------------------------------------------------
TI Serial Flasher Host Program for OMAP-L138
(C) 2012, Texas Instruments, Inc.
Ver. 1.67
-----------------------------------------------------


[TYPE] Single boot image
[BOOT IMAGE] ./u-boot-lcdk_ais.bin
[TARGET] OMAPL138
[DEVICE] NAND
[NAND Block] 1

Attempting to connect to device /dev/ttyUSB0...
Press any key to end this program at any time.

(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 14372-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 1320-Byte section to address 0x80003824.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

Aborting program...


Again I waited about 10 min before end the program which caused the "Aborting..."

Sorry for the inconvenience.
Okay. You can also try our CCS NAND writer tool for flashing the u-boot.

<MCSDK installed dir>/host-tools/OMAPL138_utils/CCS/NANDwriter.

Please import the CCS project into CCS IDE and change NAND BUS width 8 to 16 (if) then build and run.
Copy the u-boot.ais file into CCS project location.

http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/235749

Hi,

Thank you for your help so far. I found only a CSS installer for Windows ( ccs_setup_5.1.0.09000.exe ) on the attached SD card with the development tools. Unfortunately I do not have administrator access to the Win pcs of the college.

Gergely

Hi Gergely,

OK, fine. Try the following options.

Option 1:

Try the below command to make sure that the NAND memory is accessible and doesnot have any problem before flashing the binary into it.

./sfh_OMAP-L138.exe -targetType OMAPL138 -flashType NAND -p /dev/ttyUSB0 -erase

Post what is the error message you got for the above command. If the command is succesful, try option 2.

 

Option 2:

Instead of using mono, use the windows machine and command line prompt and attempt the same.

 

Option 3:

Get administrator access from your college and try out the NAND writer using CCS.

 

Regards,

Shankari

-------------------------------------------------------------------------------------------------------

Please click the Verify Answer button on this post if it answers your question.
--------------------------------------------------------------------------------------------------------

 

 

Hi,
Thanks for the early reply.
I tried the option 2 before, I run the given flashing command on a Windows pc with the only modification of using COM5 insted of /dev/ttyUSB0 .
Now I tried option 1, the erase, as well, here is the output:

./sfh_OMAP-L138.exe -targetType OMAPL138 -flashType NAND -p /dev/ttyUSB0 -erase
-----------------------------------------------------
TI Serial Flasher Host Program for OMAP-L138
(C) 2012, Texas Instruments, Inc.
Ver. 1.67
-----------------------------------------------------


[TYPE] Global erase
[TARGET] OMAPL138
[DEVICE] NAND
[NAND Block] 1

Attempting to connect to device /dev/ttyUSB0...
Press any key to end this program at any time.

(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 14372-Byte section to address 0x80000000.
(AIS Parse): Processing command 1: 0x58535901.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading section...
(AIS Parse): Loaded 1320-Byte section to address 0x80003824.
(AIS Parse): Processing command 2: 0x58535906.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Performing jump and close...
(AIS Parse): AIS complete. Jump to address 0x80000000.
(AIS Parse): Waiting for DONE...
(AIS Parse): Boot completed successfully.

Waiting for SFT on the OMAP-L138...

Aborting program...


I have waited 5 minutes after the "Waiting for SFT..." before I end the program which resulted the "Aborting..."

Hi Gergely,

I have personally used this sfh tool multiple times with variuos boards and not faced any problems.

 

In your post you said you were using the COM5 but in the sft command, it doesnot come out.

You should have used the command like below with correct parameter for OMAPL138 LCDK.

 

./sfh_OMAP-L138.exe -targetType OMAPL138_LCDK -flashType NAND -p COM5 -erase

Regards,

Shankari

-------------------------------------------------------------------------------------------------------

Please click the Verify Answer button on this post if it answers your question.
--------------------------------------------------------------------------------------------------------

I copied the linux output but I got exactly the same on a Windows 7 host. On Windows I used COM5 intead of /dev/ttyUSB0 since that was the serail port via usb according to the Control Center, so I run ./sfh_OMAP-L138.exe -targetType OMAPL138_LCDK -flashType NAND -p COM5 -erase .

Thanks,
Gergely

Hi Gergely,
Apologize for the inconvenience.
Is that new board or bought long back ?
Actually we will test this board completely and then we ship to customers.
Typically we would face this problem due to DDR memory config mismatch.
Could you connect your board to CCS and try to run any examples on it.
Also tell us what is the DDR part no on your board.