• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 1059 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.

CCS/TMS320F28032: Bootloader and Application Hex File

user4997907
Intellectual 270 points
Part Number: TMS320F28032
Other Parts Discussed in Thread: C2000WARE, TMS320F28335

Tool/software: Code Composer Studio

Is there a way of combining the bootloader and the application into one hex file (intel) for c2Prog? Also how does one build a bootloader. I can't find any information on this

  • 0
    TI__Mastermind 30255 points
    Hello

    If your bootloader is part of your application, the generated .OUT image can then be converted to a single hex file.
    The F2803x Boot ROM guide details the bootloaders in ROM: http://www.ti.com/lit/sprugo0

    You can view the bootloader source for these under /libraries in C2000Ware. Additionally, under /device_support see the f2803x_flash_kernel example which uses SCI bootloader.

    Best regards
    Chris
  • 0 in reply to Christopher Chiarella
    Prodigy 110 points
    Hello,

    I would like to ask for some help and advice with the
    related topic.

    We use TMS320F28335, and we use our proprietary
    bootloader which updates the firmware through
    fieldbus. The problem is that during production we
    need two steps to flash the device. First we download
    the bootloader software via XDS100 and after that we
    download the application software through the
    fieldbus. Our goal is contract this two steps into one.

    The bootloader is not part of the application project.
    The application software and the bootloader software
    are two different CCS projects, with different command
    files, and this two projects produce two OUT/HEX files.

    After some reading it seems to me easier to combine the
    two HEX files instead of the OUT files. The bootloader is
    in the sector A, and the application is in the other flash
    sectors and does not link any data or code to sector A, so
    they do not overlap. The HEX files has start/end markers
    but if we change this markers, seemingly we can merge
    the two file into one HEX file, which downloadable via
    XDS100.

    Has anybody tried this? It is even possible? Or should
    we use the conventional way and combine the OUT
    files?

    I appreciate any help or advice.
  • 0 in reply to Istvan Kobolak
    TI__Mastermind 30255 points
    Hello

    Please start your own post for us to best assist you. Thank you!

    Best regards
    Chris