• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 483 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28027: Help Filing Boot table Options for generating Hex file using C2000 hex utility

Madhav Bhaku
Prodigy 10 points
Part Number: TMS320F28027
Other Parts Discussed in Thread: C2000WARE

Hi,

I am quite new to using the C2000 HEX utility option in CCS to generate a .HEX file for my project. I have been going through the sub section of the C2000 HEX Utility and came across the Boot Table Options.

I wanted to know whether its mandatory to fill the Boot Table Options sections or it should be left blank for generating the .HEX file. If the Boot table options section is left empty after the flash update will the code run from flash?

I will be using this .HEX file to flash update the TMS320F28027 via SCI with another processor.

Kind Regards

Madhav Bhaku

  • 0
    TI__Mastermind 34645 points

    Madhav

    You can refer the following example provided in C2000Ware 

    C:\ti\c2000\C2000Ware_5_01_00_00\device_support\f2807x\examples\cpu1\F2807x_sci_flash_kernel

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    Prodigy 10 points

    Thanks Siddharth. I will go through the example.

    Kind Regards

    Madhav Bhaku

  • 0 in reply to Madhav Bhaku
    TI__Mastermind 34645 points

    Madhav

    Sure, let me know if you have any other questions.

    Best Regards

    Siddharth

  • 0 in reply to Siddharth Deshpande
    Prodigy 10 points

    Hi Siddharth,

    I have gone through the example but it does not help me what I want to achieve.

    To give the overview, I have a system where there are 2 processors, 1 is STM32 and the other is Ti DSP TMS320F28027. 

    I am writing a field update routine so that STM32 and Ti DSP firmware's can be field updated. 

    STM32 talks to the Ti DSP and tell it when its time to field update. 

    That's why I need to write my custom bootloader code for Ti DSP.  This custom bootloader is the first thing that will run in Ti DSP after rest and will decide whether to update the flash or jump to main application code. 

    How can I move my application code to another flash sector ? Can DSP have 2 different firmware's in this case custom bootloader and application code sitting in different flash locations?

    Is there any example that I can follow to achieve this? 

    Kind Regards

    Madhav Bhaku

  • 0 in reply to Madhav Bhaku
    TI__Mastermind 34645 points

    Hi Madhav

    How is the STM32 interfaced with TMS320F28027?

    The example that I shared takes the application over SCI and then programs it. 

    Best Regards

    Siddharth 

  • 0 in reply to Siddharth Deshpande
    Prodigy 10 points

    Hi Siddharth,

    The STM32 interfaces with TMS320F28027 vis SCI. The example of F2807x_sci_flash_kernel gives the bootloader code but where does it put it. As I was going through the example it suggested Flash Kernel was sent to the DSP via SCI terminal and then the application code was transferred. I might have mis understood it. 

    Kind Regards

    Madhav Bhaku

  • 0 in reply to Madhav Bhaku
    TI__Mastermind 34645 points

    Madhav,

    This flash kernel (F2807x_sci_flash_kerne) is loaded to RAM using a SCI boot loader - it is then executed and used to program the target device's on-chip Flash memory with the end application.

    Pls refer this app note for more details - https://www.ti.com/lit/an/sprabv4g/sprabv4g.pdf

    Best Regards

    Siddharth