• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 97 subscribers
  • Views 537 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.

No BootMe message on a custom C6747 board.

Frederic Leger
Intellectual 310 points

Hi community,

We can't boot our custom board built around a C6747 (silicon rev 2.0) . So I am interested in any idea that can help !!! 

The board works fine with an emulator, we can load a program and then remove the JTAG cable : the firmware keeps running...

But without an emulator : After a poweron there are no signs of the DSP BOOTROM : BootMe test of AISGEN/UARTboothost fails and even using a scope , nothing on UART0_TX, UART2_TX...   

I had a look to the reset signals for the DSP : TRST# is low and RESET# is high. (I read that TRST# can be left low so we designed that way...)

We have three bootmodes availables : UART0 (on an FTDI USB/serial converter), UART2 (on an RS232 chip) and NOR Flash.

DSP/BIOS tests programs I wrote showed that both interfaces UART0 and UART2 are valid at 115200bauds.

Using the JTAG under CCS to have a look to the BOOTCFG register and using the appropriate micro-switch (BOOT0/3//7) on our board can have :

31...................................................76543210

00000000000000001111001111110010                  UART2 boot mode selected

00000000000000001111001111110011                  UART0 boot mode selected

00000000000000001111001101110001                  NOR boot mode selected

Any advise ?

Thanks for your help.

Best regards,

Frédéric

 

 

  • 0
    TI__Mastermind 27585 points

    Use the debug gel file which will verify the boot mode and report any boot rom errors that might have occurred:

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

    Paste all the information the GEL is outputting here for us to look at.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 310 points

    Hi Jeff,

    Please find the report below.

    Frederic


    ---------------------------------------------
    |             Device Information            |
    ---------------------------------------------
    DEV_INFO_00 = 0x9B7DF02F
    DEV_INFO_01 = 0x00000000
    DEV_INFO_02 = 0x0000F3F2
    DEV_INFO_03 = 0x00000002
    DEV_INFO_04 = 0x00000000
    DEV_INFO_05 = 0x000003E0
    DEV_INFO_06 = 0x00000080
    DEV_INFO_07-DEV_INFO_08-DEV_INFO_09-DEV_INFO_10-DEV_INFO_11-DEV_INFO_12 = 8-0-62617-17-8-23
    DEV_INFO_13,DEV_INFO_14,DEV_INFO_15,DEV_INFO_16 = 0,0,0,9086
    -----
    DEV_INFO_17 = 0x00030003
    DEV_INFO_18 = 0x00000000
    DEV_INFO_19 = 00000
    -----
    DEV_INFO_20 = 0x30303864
    DEV_INFO_21 = 0x3330306B
    DEV_INFO_22 = 0x00000000
    DEV_INFO_23 = 0x00000000
    -----
    DEV_INFO_24 = 0x11017008
    DEV_INFO_25 = 0x0800F499
    DEV_INFO_06 = 0x00000080
    DEV_INFO_26 = 0x46FC0000


    ---------------------------------------------
    |               BOOTROM Info                |
    ---------------------------------------------
    ROM ID: d800k003
    Silicon Revision 2.0
    Boot Mode: UART2

    ROM Status Code: 0x00000000
    Description: No error

    Program Counter (PC) = 0x007F5D20

  • 0 in reply to Frederic Leger
    Intellectual 310 points

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

    | BOOTROM Info |

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

    ROM ID: d800k003

    Silicon Revision 2.0

    Boot Mode: UART0

    ROM Status Code: 0x00000000

    Description: No error

    Program Counter (PC) = 0x007F5D66

    　

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

    | BOOTROM Info |

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

    ROM ID: d800k003

    Silicon Revision 2.0

    Boot Mode: NOR

    ROM Status Code: 0x00000005

    Description: Peripheral Open Failed

    Program Counter (PC) = 0x00712144

  • 0 in reply to Frederic Leger
    TI__Mastermind 27585 points

    For UART, the PC shows that the bootrom is waiting to receive data, and it has already sent out BOOTME. If you are not seeing any activity on the pins then there is an issue with the board or the device.

    Can you perform a warm reset (TRST is high) and check for the BOOTME again?

    Also try connecting with the emulator and toggling the UART_TXD pin as a GPIO to verify that the connection is there all the way to the package.

    Jeff

  • 0 in reply to jc-ti
    Intellectual 310 points

    The debug gel file you provided is a great help !

    I finally saw the BOOTME message on UART2 this morning using a terminal at 115200.

    Using the UART boot host, I am now able to begin a binary transfer, which crashes shortly.

    I will have another try after wiring a safer RS232 cable.

    Thanks for your support.

    Frederic 

  • 0 in reply to Frederic Leger
    TI__Mastermind 27585 points

    Great news! Can you let us know what you changed to fix the issue?

    Jeff

  • 0 in reply to jc-ti
    Intellectual 310 points

    Hi Jeff,

    I understood a few things :

    1) May be I was looking on the wrong UART channel after configuring the microswitch configuring the boot pins.

        I inserted in our GEL file the code of the debug GEL file you provided, so that I can verify quickly the DSP boot config register before powering off the board.

    2) the BOOTME message appears only once after a board powerup.

    3) Our UART0 is linked to an FTDI serial/USB converter powered by the board => almost no chance to get the BOOTME message due to the time Windows take to launch the CDC/ACM driver.

    4) I need to be very very quick to click on the UART Boot HOST v1.01 start button after the board powerup !!!!! otherwise nothing appends.

    5) I need to have a very safe custom RS232 cable. ( single in-line to DB9)

    I still don't know if I can safely use an USB/serial converter on top of my custom cable with UART Boot HOST v1.01.....

    Nowadays RS232 is unavailable on most computers.

    Best regards.

    Frédéric

     

     

     

     

     

  • 0 in reply to Frederic Leger
    TI__Mastermind 27585 points

    4) The correct order is to check the "Wait for BOOTME" box, press Start, and then reset the board. You shouldn't reset the board before starting the boot host, otherwise you will have to click very quickly as you have seen!

    Jeff