• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 1243 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Serial flashing OMAP L-138 Eval. board

ALex Movasseghi
Prodigy 140 points
Other Parts Discussed in Thread: OMAPL138, OMAP-L138

I followed the instructions in http://wiki.davincidsp.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138 to flash the SPI flash on the OMAPL138 Eval board from Zoom (LogicPD). I tried erasing the flash first and then flashing the default UBL and U-Boot bin files  from TI.

I used the following command

sfh_OMAP-L138.exe -erase

I set the S7 switch to boot from UART2 i.e. switched 1-6 off and 7 and 8 on, connected the Null modem cable to RS232 of my PC 

I get the message

 

C:\flasher>sfh_OMAP-L138.exe -erase
-----------------------------------------------------
   TI Serial Flasher Host Program for OMAP-L138
   (C) 2010, Texas Instruments, Inc.
   Ver. 1.67
-----------------------------------------------------


Platform is Windows.
      [TYPE] Global erase
    [DEVICE] SPI_MEM

Attempting to connect to device COM1...
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)
(Serial Port): Read error! (The operation has timed out.)
(AIS Parse): Read invalid BOOTME string.
(AIS Parse): Boot aborted.
Booting SFT failed. Trying again (you may need to reset the target)...
(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(Serial Port): Read error! (The operation has timed out.)
(AIS Parse): Read invalid BOOTME string.
(AIS Parse): Boot aborted.
Booting SFT failed. Trying again (you may need to reset the target)...
(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)

Also tried to connect Tera Term directly to Com port 1 and set the baud rate to 115200/8/1  but still can not see the BOOTME prompt.

If I set the S7 switch pins 7 and 8 back to OFF, I can see the the U-boot messages in serail console:

 

U-Boot 2009.01 (Jul 30 2009 - 11:58:01)

DRAM:  64 MB
In:    serial
Out:   serial
Err:   serial
ARM Clock : 300000000 Hz
DDR Clock : 300000000 Hz
Ethernet PHY: GENERIC @ 0x00
Hit any key to stop autoboot:  0
U-Boot >

Please let me know how I can pass this point and load the UBL and U-BOOT to SPI Flash through Serial falshing.

Also, where is the Serail loader program resides in OMAP processor that responses to host utility with BOOTME message? Is that a fix code that gets executed by setting the BOOTCFG register to boot from UART2 or do we need to download it to any new board with no code in Flah?

 

Thanks,

 

--Alex

  • 0
    TI__Guru* 83965 points

    Hi Alex

    ALex Movasseghi said:
    Also tried to connect Tera Term directly to Com port 1 and set the baud rate to 115200/8/1  but still can not see the BOOTME prompt.

    This is not a good sign. If you configure the dip switches on S7 to set the boot mode to boot from UART2 , then you should definitely see a BOOTME prompt. Whenever I have encountered a similar issue (no BOOTME prompt) then it is either

    1) Required to reboot the PC (some times docking/undocking my laptop, puts the COM1 in bad state)

    2) You are dealing with a baud rate mismatch somehow.

    If possible, can you try this with another PC (although I can understand that since the serial console is working when SPI boot mode is set, you might be completely convinced that it is a serial console issue).

    Also, if you have CCS availalble and can connect to ARM side, please provide us the contents of the STDOUT window, running the following gel file (with the board configured to boot from UART2)

    http://processors.wiki.ti.com/index.php/OMAP-L1x_Debug_Gel_Files

    Regards

    Mukul

  • 0 in reply to Mukul Bhatnagar
    Prodigy 140 points

    Hi Mukul,

    BAsed on the error that I got in UART2 boot mode, it seems that the device gets stuck in Reset when I set the dip switch to UART2 mode (7 & 8 ON), please check the following:

    1) I did reboot the PC and still got the same error message

    $ ./sfh_OMAP-L138.exe -erase
    -----------------------------------------------------
       TI Serial Flasher Host Program for OMAP-L138
       (C) 2010, Texas Instruments, Inc.
       Ver. 1.67
    -----------------------------------------------------


    Platform is Windows.
          [TYPE] Global erase
        [DEVICE] SPI_MEM

    Attempting to connect to device COM1...
    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): Read invalid BOOTME string.
    (AIS Parse): Boot aborted.
    Booting SFT failed. Trying again (you may need to reset the target)...
    (AIS Parse): Read magic word 0x41504954.
    (AIS Parse): Waiting for BOOTME... (power on or reset target now)
    (AIS Parse): Read invalid BOOTME string.
    (AIS Parse): Boot aborted.
    Booting SFT failed. Trying again (you may need to reset the target)...
    (AIS Parse): Read magic word 0x41504954.
    (AIS Parse): Waiting for BOOTME... (power on or reset target now)
    (AIS Parse): Read invalid BOOTME string.

    Tried another PC but the same result.

    2) Tried to connect CCS through USB with boot mode configure for UART2 (7 & 8 ON) and I got this error msg:

    Error connecting to the target: Error 0x80000240/-1180 Fatal Error during: Initialization, OCS,  The target is stuck in Wait-in-Reset mode.  The applied reset must be released before progressing.

     

    Then switched back to default boot mode (SPI1, all the dip switches OFF) and loaded the debug Gel file and got the following:

    In Defualt Boot Mode (SPI1 Flash)

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

    |               BOOTROM Info                |

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

    ROM ID: d800k002

    Silicon Revision 1.0

    Boot Mode: SPI1 Flash

     

    ROM Status Code: 0x00000001

    Description: DSP was put to sleep

     

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

    |             Device Information            |

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

    DEV_INFO_00 = 0x0B7D102F

    DEV_INFO_01 = 0x00000000

    DEV_INFO_02 = 0x0000000C

    DEV_INFO_03 = 0x00000030

    DEV_INFO_04 = 0x00000000

    DEV_INFO_05 = 0x000003E0

    DEV_INFO_06 = 0x00000000

    DEV_INFO_07-DEV_INFO_08-DEV_INFO_09-DEV_INFO_10-DEV_INFO_11-DEV_INFO_12 = 0-0-6228662-2-25-32

     

    Thanks,

    --alex

  • 0 in reply to ALex Movasseghi
    TI__Guru* 83965 points

    Hi Alex

    Thanks for collecting the additional information. I am still suspecting that somehow the device is not detecting the UART2 boot mode , that would be the only reason you don't see a BOOTME prompt (given that you think it is not a PC issue etc) , unless you are just missing the BOOTME prompt (as it shows up only one time, details on page 20 in the bootloader appnote http://focus.ti.com/lit/an/sprab41b/sprab41b.pdf )

    It would be great if you could connect to CCS in UART2 boot mode, and have the debug ROM gel file confirm that is indeed seeing a UART2 boot mode

    ALex Movasseghi said:

    2) Tried to connect CCS through USB with boot mode configure for UART2 (7 & 8 ON) and I got this error msg:

    Error connecting to the target: Error 0x80000240/-1180 Fatal Error during: Initialization, OCS,  The target is stuck in Wait-in-Reset mode.  The applied reset must be released before progressing.

    Can you clarify whether you were trying to connect to ARM or DSP side on CCS. Note that for OMAPL138 ARM is enabled by default and DSP is clocked off. You will see similar error messages reported on other forum posts

    http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115/p/31742/121588.aspx

    http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/p/29437/102369.aspx

    If you tried to connect to DSP then you would see similar error messages.

    One issue is that from your description it seems like you are just using just a USB cable, that would imply XDS100v1 --> If that is the case you will not be able to connect to ARM side CCS. You need some other emulator or XDS100v2.

    Can you please also make sure that you are using the latest serial flashing utilities

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

    Regards

    Mukul

     

  • 0 in reply to Mukul Bhatnagar
    Prodigy 140 points

    Hi Mukul,

     

    After some hw debugging, it seems that there is something wrong with the board in UART2 boot mode. I have another OMAP-EVAL board that I connected to my set-up and be able to erase and load the SPI flash through UART2. In anycase thanks for all your help.

     

    --alex