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.

run code from flash issues (stand-alone operation)



hi

i used to work with CCS 3.3 on my dsk5510, and used to program the flash using flash burn...

now i moved to CCS 5.5, and downloaded flash  burn from SDS, but not sure of the steps i have to make.

is there any tutorial that i can use (that includes how to configure the memory sections, generating the .hex file, boot configuration of the board...)?

thanks

  • Hello,
    There is a getting started guide for Flashburn 4.x:
    softwaredesignsolutions.com/.../GettingStarted.pdf

    You can direct any questions on Flashburn on SDS forums:
    softwaredesignsolutions.com/.../default.aspx

    Thanks
    ki
  • hi ki
    flash burn needs to be provided with .hex file, while CCS will generate .out file. earlier there was a tool that was used to make CCS 3.3 generate .hex file (by adding hex55.exe and a .cmd file to the project and configure the to be built in the final steps).
    is there a way to do so in CCS 5.5?
    BTW, SDS forum is not getting me any reply at all and there web cite doesn't give much information and clarity, i think selling this product to another company is not a good step (for me at least)
    thanks
    aziz
  • Yes the same hex utility comes with CCSv5.5. It comes with the compiler in (C:\ti\ccsv5.5.0.00077\ccsv5\tools\compiler\c5500_4.4.1\bin). You can add it as a post-build step just like you did in CCSv3:

    Thanks

    ki

  • hi ki
    thank you for your support

    i had few question if i may
    first, in the toutorail you mentioned, they used " create flash image Intel-Hex " in "apply predefined steps" of the build settings.
    an automatic code is generated in the "command" space...
    my question is: do i have to change any thing in that line?

    another issue is that i believe that i should provide a .cmd file for the .hex generation in addition to the "hex55" tool in the project folder, is that true? and is there any restrictions on those files?

    third problem is that when I'm doing the previous steps, I'm getting hex file, but when trying to burn it to the flash i get this error:
    Hex File Start: 0x000039D4 - End 0x0004FFFF
    Flash Start: 0x00400000 - End 0x0047FFFF
    do you have an idea how to fix this?

    thank you again for your Patience.
    best regards
    aziz
  • aziz shammas said:
    first, in the toutorail you mentioned, they used " create flash image Intel-Hex " in "apply predefined steps" of the build settings.
    an automatic code is generated in the "command" space...
    my question is: do i have to change any thing in that line?

    The answer is... it depends! The default options specified by the predefined step are the commonly used ones. But of course you made need to change them depending on environment. For more info on the utility, see section 13 of the C55 Asm language user's guide:

    aziz shammas said:
    another issue is that i believe that i should provide a .cmd file for the .hex generation in addition to the "hex55" tool in the project folder, is that true? and is there any restrictions on those files?

    third problem is that when I'm doing the previous steps, I'm getting hex file, but when trying to burn it to the flash i get this error:
    Hex File Start: 0x000039D4 - End 0x0004FFFF
    Flash Start: 0x00400000 - End 0x0047FFFF
    do you have an idea how to fix this?

    The information in the above user's guide will also help answer your other hex related questions.


    Thanks

    ki