• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 531 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.

TMS320C6678: Means of Debugging using BOOTLOADER

Alban MICHELANGELI
Intellectual 270 points
Part Number: TMS320C6678


Hello,

We currently develop a software using TMS320C6678 DSP on evaluation Card FMC667 from 4DSP.

I am responsible for the BOOT software development. Consequently, my activity deals with the BOOTLOADER which is present inside the TMS320C6678 (@ 0x20C00000).

BOOT software is stored in a NOR FLASH. As soon as a device reset occurs, the BOOTLOADER reads the DEVSTAT register which contains the Boot Mode.

For our product, Boot Mode shall be SPI. Then, the BOOTLOADER reads the Boot Parameter Table from the aforementioned NOR FLASH.

From this Boot Parameter table, the BOOTLOADER configures the SPI to load the BOOT software in RAM (Boot Table format).

Let's Imagine problem occurs during the BOOT software loading. The problem could be due to an erroneous Boot Parameter Table, an erroneous Boot Table format or many other reasons.

I would like to know what means of debugging are available for me if such problem occurs, as i don't have any access to the implemented BOOTLOADER  source code or/and format ELF file.

Note that we use a TRACE32 probe LAUTERBACH for debugging. The most efficient mean of debugging should be for us the ability to set Breakpoint in BOOTLOADER to get the origin of the problem.

Regards

Alban MICHELANGELI

  • 0
    TI__Guru 65405 points
    Hi Alban,

    I've forwarded this to the experts. Their feedback should be posted here.

    BR
    Tsvetolin Shulev
  • 0
    TI__Guru** 116180 points
    Hi Alban,

    The ROM source code for this device is provided in source on the URL below:
    processors.wiki.ti.com/.../Keystone_Device_Architecture

    We don`t provide the binary the the source is only for reference.

    To debug boot related issues, you can collect Debug log using the Debug GEL file and post it on the forums. the Debug GEL will capture clock ssstates, peripheral states and Program counter with which we can provide feedback.

    For boot parameter, you can read the location of the boot parameter defined in internal DSP memory if the table has been copied from flash correctly.

    Regards,
    Rahul

    PS: For more such bootloader questions please refer to :
    processors.wiki.ti.com/.../KeystoneI_Bootloader_Resources_and_FAQ
  • 0 in reply to Rahul Prabhu
    Intellectual 270 points
    Hi Rahul,

    Thanks for your quick answer.

    I'm currently looking the BOOTLOADER source code concerning SPI Boot Mode.
    If my analyzis is good, BOOTLOADER supports only 8 characters length and MSB first tranmission SPI transfer.

    If a FLASH NOR supporting only 16 characters length and LSB first tranmission SPI transfer is chosen (only hypothetic use case) ,
    this FLASH NOR is not supported by the BOOTLOADER. What happens in this case ?
    Will TI develop a specific BOOTLOADER or shall the customer choose only a 8 characters length and MSB first tranmission SPI transfer FLASH NOR ?

    I ask this question for Hardware design purpose.

    Regards

    Alban