• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 99 subscribers
  • Views 688 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.

OMAPL137 UART 2 BOOT MODE query

Jitendra Jagasia
Intellectual 840 points

HI,

I have query regarding UART2 boot mode in OMAPL137 board. I have set the OMAPL137 board in UART2 boot mode by setting the SW2 according to the following configuration given below

BOOT PINs   7 2 1 0 3

ON OFF  ON OFF  OFF


According to the wiki link given below, we should have got "BOOTME" reply on the HyperTerminal When the reset button is pressed on the EVM connected to the serial port to the PC.      

Hyperterminal configuration are given below:

Speed: 115200

Data bits: 8

Parity bits: None

Stop bits: 1

Flow control: None

I have also tried using Tera Term instead of HyperTerminal with same configuration as given above & I also tried with Baud rate 230400 on Tera Term but no "BOOTME" reply. But when i change SW2 settings back to SPIO Flash configuration then i can see UBOOT prompt on HyperTerminal, that means my serial port connection is working properly but for Uart2 boot mode there is no "BOOTME" reply.

  • 0
    TI__Mastermind 27585 points

    Hi Jitendra, can you please load this debug GEL file after you have reset in UART2 boot mode?

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

    This will print out the current boot mode and the status of the ROM boot loader. Thanks

    Jeff

  • 0 in reply to jc-ti
    Intellectual 840 points

    Hi Jeff,

    I used OMAP-L1x_Debug Gel file & it displayed following message

    BOOT ROM Info

    ROM ID : d800k001

    Silicon Revision 1.0

    Boot mode : UART 2

    ROM Status code : 0x00000037

    Description Error code not recognized

    Program Counter (PC) = 0xFFFF0004

    Hey can you explain why this error code is occurring & why BOOTME string is not occurring in the Hyper Terminal.

    Regards

    Jitendra  

  • 0 in reply to Jitendra Jagasia
    TI__Mastermind 27585 points

    Since this is a DSP boot device, you should be connecting to the DSP to view the boot information. Based on the PC, you are connected to the ARM.

    You might want to check out this post: http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115/p/92521/323301.aspx#323301. Basically they had to make sure nothing was driving the BOOT pins during reset. That post also has the standard debug methodology you can follow for this issue.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 840 points

    Hi Jeff,

    I used OMAP-L1x_Debug Gel file by connecting to DSP & it displayed following message

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

    |               BOOTROM Info                |

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

    ROM ID: d800k001 

    Silicon Revision 1.0

    Boot Mode: UART2

     

    ROM Status Code: 0x00000000 

    Description: No error

     

    Program Counter (PC) = 0x117FAD38

     

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

    |             Device Information            |

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

    DEV_INFO_00 = 0x0B7DF02F

    DEV_INFO_01 = 0x00000000

    DEV_INFO_02 = 0x0000F3F2

    DEV_INFO_03 = 0x00000020

    DEV_INFO_04 = 0x00000000

    DEV_INFO_05 = 0x000003F0

    DEV_INFO_06 = 0x00000000

    DEV_INFO_07-DEV_INFO_08-DEV_INFO_09-DEV_INFO_10-DEV_INFO_11-DEV_INFO_12 = 8-0-62459-2-19-47

    DEV_INFO_13,DEV_INFO_14,DEV_INFO_15,DEV_INFO_16 = 0,0,0,2102

    -----

    DEV_INFO_17 = 0x00030003

    DEV_INFO_18 = 0x00000000

    DEV_INFO_19 = 00000

    -----

    DEV_INFO_20 = 0x30303864

    DEV_INFO_21 = 0x3130306B

    DEV_INFO_22 = 0x00000000

    DEV_INFO_23 = 0x00000000

    -----

    DEV_INFO_24 = 0x0202F013

    DEV_INFO_25 = 0x0800F3FB

    DEV_INFO_06 = 0x00000000

    DEV_INFO_26 = 0x106C0000

     

    Even though the BOOTROM info is showing UART2 Boot Mode, but still in the Hyper Terminal the BOOTME command doesn't appears.

     I am currently testing the above procedure on OMAPl137 Eval board with UART2 serial interface.

    Regards

    Jitendra

     

  • 0 in reply to Jitendra Jagasia
    TI__Mastermind 27585 points

    Have you tried the debug steps from the post I mentioned previously, such as probing the TXD line to see if there is any activity?

    Jeff

  • 0 in reply to jc-ti
    Intellectual 840 points

    Hi Jeff,

    We are using OMAPL137 Eval board.

    We have Tested UART2 interface on the Eval board by connecting it to the modem, the serial interface communication is working properly.

    However when i set the Eval board in UART2 BOOT mode the UART2 Tx pin is not toggling & we are not getting the BOOTME response. 

    Please revert back as soon as possible.

    Regards 

    Jitendra

  • 0 in reply to Jitendra Jagasia
    TI__Mastermind 27585 points

    In that case it seems like you may have an EVM issue. The UART2_TXD pin should toggle immediately after reset, and according to the GEL file output the device is working correctly. Please double check the voltage levels, especially the IO power rails, to make sure the EVM is working properly after reset.

    Jeff

  • 0 in reply to jc-ti
    TI__Expert 7225 points

    As far as we know, BOOTME message will come only once, that too at 230400 baud rate. This is true for OMAP L137 PG 1.x devices (ROMID: D800K001).

  • 0 in reply to K Md Feroz Irfan
    Intellectual 840 points

    Hi,

    The Uart 2 TX pin is toggling after reset but on the Hyper Terminal which is configured for 115200 baud rate garbage value appears. But according to the startup guide "BOOTME" string  should appear on Hyper Terminal configured for 115200 after reset.

    I have tried the above case with different serial port & also on the different PC too.

    Please revert back for the above query as fast as possible

    Regards

    Jitendra