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

How can I create *.hex in my application and what utility can be used to download this hex into my picollo?

Kai Ren
Intellectual 355 points

Other Parts Discussed in Thread: UNIFLASH

Hello,

I am a freshman in CCS and C2000 mcu.

I want to know that how can create a hex format file in my application when I do some setting in my CCS 5.2?

Then, what utility can be used to download hex image into c2000 launchpad? I had ever use TI MSP430, I can use Elprotronic FlashPro430 SW to erase, read and write MSP430's flash area, so I want to find similar tool for c2000 launchpad.

Thanks, 

Ren Kai

  • 0
    TI__Guru*** 130875 points

    Hi Kai,

    I believe elprotronic offers tools for the C2000 family as well :  )    Also we now are starting to launch our uniflash tool.  It is currently in beta and I believe has limited C200 support however something further to keep in mind.

    http://processors.wiki.ti.com/index.php?title=Category:CCS_UniFlash

    In CCSv5 you can generate the hex by going to Project->Properties->Build .  In the Steps tab you should see a drop down for "Apply Predefined Step".

    Does this help?

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 355 points

    Hi Lisa

    CCS UniFlash work fine. I can use it to erase and program my picollo.

    An new issue is that when I "Apply Predefined Step" to create TI-TXT format file. CCS Link will report as below:

    Translating to TI-TXT format...
    "Example_F2802xLaunchPad_demo.out" ==> .econst
    "Example_F2802xLaunchPad_demo.out" ==> ramfuncs
    "Example_F2802xLaunchPad_demo.out" ==> .text
    warning: section Example_F2802xLaunchPad_demo.out(.econst) at 07ec000h falls in
    unconfigured memory (skipped)
    warning: section Example_F2802xLaunchPad_demo.out(ramfuncs) at 07ec37eh falls
    in unconfigured memory (skipped)
    warning: section Example_F2802xLaunchPad_demo.out(.text) at 07ec386h falls in
    "Example_F2802xLaunchPad_demo.out" ==> .cinit
    "Example_F2802xLaunchPad_demo.out" ==> codestart
    unconfigured memory (skipped)
    warning: section Example_F2802xLaunchPad_demo.out(.cinit) at 07ed042h falls in
    unconfigured memory (skipped)
    warning: section Example_F2802xLaunchPad_demo.out(codestart) at 07effech falls
    in unconfigured memory (skipped)
    ' '

    Anything wrong in my project setting?

    BR

    Ren Kai

  • 0 in reply to Kai Ren
    TI__Guru**** 173310 points

    Kai Ren said:

    An new issue is that when I "Apply Predefined Step" to create TI-TXT format file. CCS Link will report as below:

    When you use --ti_txt output format, the width of address bits defaults to 8 (this is mentioned in the C28x Assembly Language Tools Users Guide). So the addresses and lengths of the ROMS directive (which is also documented in the same guide) are specified in terms of 8-bit bytes, and not 16-bit words.  When you do not specifically have a ROMS directive, as in your case, it defaults to 16-bit words and hence generates the error you see. To get around the error, you need to double both the origin and length values of the addresses in the ROMS directive. Please see this related thread for more information.

    So basically you need to modify the pre-defined command added to the post-build step to invoke a hex command file which contains a ROMS directive that specifies the address range of your FLASH, but doubled.

    Please see this related thread.