Hi Hakeen,

Have you referred the below TI wiki ?

http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137

Do you want to run linux or DSP/ARM app or SYSBIOS on OMAPL137 device?

Hi Hakeen,

hakeen says said:

I read below wiki links.... I'm confused......

sfh_OMAP-L137.exe , HexAIS , HexAIS_OMAP-L137.exe ......

Not to worry. We will help you out. We will go step by step to crack this.

Things at first sight:

1. There is a utility called serial flasher available for TI released EVM, which you can customize for your board and use it. ( From your message, I guess, it is a custom board and not the TI EVM, right? please confirm.)

Steps:

1. First download the sfh utility from http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137#Obtaining_the_software

2. Try modifying acoording to your custom board using the tips given at

http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137#Modifications_for_Custom_Boards

3. Compile and build the sfh utility by following http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137#Compiling

4. observe the output terminal messages. If there are errors post the error messages in your reply to this post.

Regards,

Shankari

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

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

Hi Titus S.

I run DSP appp on OMAPL137.

I readed "Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L137".  

Post my result at another below message.....

Hi Shankari 

Thx!

I developed on TI EVM  (OMAP-L137 EVM) http://www.ti.com/tool/tmdsoskl137

I utilized only the DSP part.

I got stocked at RS232 connection. Below was my connection result. It seems my serial connection is in trouble.

I utilized USB-to-RS232 to connect OMAP-L137 EVM. This USB-to-RS232 is good..... work at other devices....

Configuration : 

OMAP-L137_FlashAndBootUtils_2_40

USB-to-RS232  is COM6

Test A.

Connect TX of USB-to-RS232 to TX of DB9 OMAP-L137 EVM.

Connect RX of USB-to-RS232 to RX of DB9 OMAP-L137 EVM.

Execute "sfh_OMAP-L137.exe -p COM6 -v -erase"

I "Power on/off EVM or press reset button of EVM".   The screen keep as below image.

Test B.

Connect TX of USB-to-RS232 to RX of DB9 OMAP-L137 EVM.

Connect RX of USB-to-RS232 to TX of DB9 OMAP-L137 EVM.

Execute "sfh_OMAP-L137.exe -p COM6 -v -erase"

Screen keep showing  new string "invalid BOOTME string".......

Test C.

Connect TX of USB-to-RS232 to TX of DB9 OMAP-L137 EVM.

Connect RX of USB-to-RS232 to RX of DB9 OMAP-L137 EVM.

Utilize terminal program to watch RS-232 data.

I "Power on/off EVM or press reset button of EVM".   Don't receive any data......

Test D.

Connect TX of USB-to-RS232 to RX of DB9 OMAP-L137 EVM.

Connect RX of USB-to-RS232 to TX of DB9 OMAP-L137 EVM.

Utilize terminal program to watch RS-232 data.

Press "Reset Button of OMAP-L137 EVM"

Receive the red words in the below image.

Test E.

Connect TX of USB-to-RS232 to RX of DB9 OMAP-L137 EVM.

Connect RX of USB-to-RS232 to TX of DB9 OMAP-L137 EVM.

Utilize terminal program to watch RS-232 data.

Power on/off OMAP-L137 EVM

Receive the red words in the below image.

Hi Hakeen,

As per your screenshot of TestB, the boot switch settings may not be correct to receive the "BOOTME" message.

First you have to ensure that you receive "BOOTME".

1. Set the boot pins of the EVM to UART2 boot mode. This is done by setting boot switches on the OMAP-L137 EVM according to the following table: For all revisions after B:

For revisions A and B:

2. Connect a serial cable from the host computer to the OMAP-L137 EVM. Note that for OMAPL137_v1 the host computer must be able to run at a UART baud rate of 230400.

3. Test your UART connection by opening HyperTerminal and connecting to the correct COM port at 115200 (or 230400). When the reset button is pressed on the EVM, the words "BOOTME" should appear on the terminal. If not, recheck the cable connection, baud settings, and boot pins of the EVM. Please note that many PC serial ports do not support a baud rate of 230400. In these cases, a USB->Serial adapter should be used.

4. Disconnect from HyperTerminal.

5. Open a command prompt on the host computer and change directory to where the flashing utility was saved (ex. c:\flasher).

6. Run the flashing utility

Regards,

Shankari

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

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

Hi Shankari

Yes. I changed the BOOT mode switch.

My OMAP-L137 EVM is version I.

Test B1. 

Power off / on EVM.  

Read serial data in terminal program.

Test B2. 

sfh_OMAP-L137.exe -p COM6 -v -erase

Power off / on EVM.  

Hi Hakeen,

After changing the BOOT Mode switch, if you still see the failure, then it is probably due to the first terminal which receives the handle of COM6 instead of serial flasher utility.

So, please close the terminal after verifying that the "BOOTME" is received after pressing reset. That is "DISCONNECT THE HYPERTERMINAL" and run the serial flasher.

Regards,

Shankari

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

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

Hi Shankari

I turned off other terminal program. The COM port can only be accessed by one program at the same time.

If the COM port were accessing by some program, the sfh will show "connection refused". Just like below image.

Without connection error message, sfh connect COM port successfully.

Hi Hakeen,

Do you have linux host machine ?

If yes, Please test it in minicom with appropriate settings.

Is this TI EVM or custom board ?

I hope it is custom board.

I think the issue seems to be mis match of baud rate.

Hi Titus S.

The board is 

OMAP-L137/TMS320C6747 Floating Point Starter Kit

http://www.ti.com/tool/tmdsoskl137

I have no linux environment.  I tested in another window PC. Had the same trouble.

sfh_OMAP-L137.exe could set baud rate.  I changed baud rate. Had the same trouble.

sfh_OMAP-L137.exe -p COM6 -v -erase -baud 230400

I keep changing baud rate and power on/off  , reset EVM to watch to serial data.

None contain "BOOTME"

I set 300/600/1200/2400/4800/9600/14400/19200/28800/38400/56000/57600/115200/128000/256000 baud rate to watch serial data in terminal program.....

None of the above baud rate worked......

Hi,

You have to get "BOOTME" command from serial port when boot switch is in UART boot mode.

Open hyperterminal or teraterm to open the UART port to check whether you are getting "BOOTME" message over UART.

Hi Titus S.

No. I can't get "BOOTME" message form UART port.

Hi,

Did you get any junk message or anything instead "BOOTME" while board is in UART boot mode?

sfh_OMAP-L137.exe -p COM6 -v -erase

Please check your COM port since many PC would use COM1 as serial port.

Are you using any serial to usb converter cable to connect the board into PC ?

Could you please attach your screen shot of boot switch settings and UART connections .

Hi Titus

Yes. I got some serial data. (not "BOOTME")

I set the right com port. Or, sfh will have error message.

My previous post (in this thread) show the screen shot of "Junk Message" and "COM Port Error connection".....

I think we might debug in other way.

So, I had another post: http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/t/353157.aspx

Hi Hakeen,

Debugging gel file it is nice method to validate your new DDR in custom board.

I'm not able understand your tool information.

It is good to me If you have turbo term terminal to view the UART port to check BOOTME message.

What about your CLKIN freq for PLL ref ?

There are no new DDR.

It's just TI OMAP-L137 EVM.

Below is the board information.

http://www.ti.com/tool/tmdsoskl137

The image of my previous post show what hyperterminal got.

CLKIN and PLL are standard OMAP-L137 GEL file in CCS6.

Hi Hakeen,

Sorry, I messed up some different problems with yours.

Could you please attach your snap shot of boot switch settings and UART connections.

The old attachment is not sufficient to me to check.

Are you using any "SERIAL to USB" converter ?

Please answers for the above questions to support further.

Hi Titus

Yes. I utilized USB-to-Serial.  It's PL-2303 product.

Below image is my connection. The USB-to-serial is good. It work at other device.

I think the point is not the USB-to-serial and sft*.exe.

Some FAE had the same issue as me. If you tried the same OMAP-L137 EVM, you could get the same response.

Screen shot of sfh*.exe

Screenshot of hyperterminal

Hi Hakeen,

Please try to use serial port and check whether you are getting BOOTME message.

Try to probe the RXD & TXD signals in UART while you RESET the board and check.

It should work directly w/o any issues if it is EVM board.

0003.Camera.tar.gz

This OMAP-L137 EVM really have this issue.

The problem is not caused by sfh*.exe , not USB-to-serial.

Hi Hakeen,

Is this new board or old one ?

If it is old one, Ask your colleague that anybody worked on this board and somebody might have damaged the board.

If it is new one,

I'm really very sorry about this problem on OMAPL137 LogicPD EVM.

Please try to get new OMAPL137 EVM board, Surely It should work.