This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP L138 LCDK - BOOTME never received

Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hi

I recently purchased an LCDK L138 board. I have win8.1 and teraterm. I do not have an emulator.

I am not able to run the quick start example. Teraterm is not responsive (blank screen). I tried various switch configurations and got the same.

I also tried to use the flash loader. No matter what I tried (erase for example) I got stuck at the "waiting for bootme" message.

I think I saw all the related posts on this forum. What I gather is that Teraterm should receive something from the device. What if it does not? Does that mean that there is something faulty with the board? If so what can I do?

The problem described in the following thread is the closest to mine.

http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115/t/240851.aspx

Except that no lights (except D3) are lit on my board.

Any help will be greatly appreciated. Even a confirmation that there is something wrong with the board.

Regards.

  • Hi Haydar,

    Could you please provide your boot switch settings that you have you used in your LCDK board for UART boot.

    LCDK board uses UART-USB converter for UART o/p, so could you please provide your commands too that you have followed (you are getting "Waiting for BOOTME" ?)

    Also, you must have USB-UART drivers for WIN8, after you connected the USB cable between PC to LCDK board , just check whether any COM port has been detected or not on your PC.

    After that you can have COM port lists on your tera term.

    You have to pass '-p' argument for COM port while you use SFH flash tool.

    SW1 settings for UART boot on LCDK board.

    1    2    3    4    5    6    7    8

    0    1    0    1    0    0    0    0

  • Also please ensure that you have connected the USB cable on J3 connector not J2(USB OTG) for UART boot

  • Thanks for the response

    The usb cable is connected to J3.

    The switches are 01010000.

    Windows installed the USB Serial driver itself. I did not do it manually. Device manager shows a USB serial port COM3.

    For the record, here is the snapshot of the driver details window.

    Teraterm does not seem to get any response (for any switch settings).

    These are the command lines I try

    sfh_OMAP-L138 -erase -targettype OMAPL138_LCDK -p COM3

    sfh_OMAP-L138 -erase  -p COM3

    The response is the same for the both. 

    (AIS Parse): Waiting for BOOTME... (power on or reset target now)

    It halts (resetting does not help). When I finally press a button I get this.

    (Serial Port): Read error! (Thread was being aborted.)

    Any suggestions?

  • Hi Haydar,

    Could you please try it in different host PC like Linux ubuntu (minicom) ?

    Press "reset" button for getting "BOOTME"

    Also please ensure that you have not used the same port for different purpose.

  • I tried it on a different PC (win 7) with no luck.

    I also borrowed an emulator (xds 510 usb, i tested it with another board successfully). With sdconfigex i was not able to reset the emulator. I used all three switch settings 0101,0111,0001.

    Does this confirm that something is wrong with the board? With power on, only the power led is lit on the board. Is this normal?

  • Hi Haydar,

    No, this is not a normal behavior.

    Are you able to connect emulator and able to debug any ARM app (hello world) ?

    If no, what is the error are you facing ?

  • No I can't. 

    Code composer can not verify the emulator in the first place. Apparently it also tries sdconfig to reset the emulator and fails like this.

    ** Resetting Emulator
    ERROR -- XDS510USB Reset Failed
    ERROR -- Check power to your emulator/eZdsp
    ERROR -- Then check your port address

    I tried for every switch settings. Reset button does not help.

  • Hi Haydar,

    1) Try to debug the app directly without doing "Test connection" and select appropriate settings (OMAPL138 LCDK and XDS510USB emulator)

    Are you getting "initialization error" ?

    2) Try all the suggestions on different LCDK board with the same environment.

  • 1. This is what i get when i run the hello world program.

    Error connecting to the target:

    Error 0x80000240/-2082
    Fatal Error during: Initialization, OCS,
    Device driver: Emulation Connection Loss Detected on Target CPU.
    It is recommended to RESET EMULATOR. This will disconnect each
    target from the emulator. The targets should then be power cycled
    or hard reset followed by an emureset and reconnect to each target.

    2. I dont have a different LCDK board.