• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 417 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.

Original question:

Linux/LAUNCHCC3220MODASF: file .out to .bin

CCS/LAUNCHCC3220MODASF: How to convert *.out to *.bin?

cy w
Intellectual 350 points
Part Number: LAUNCHCC3220MODASF
Other Parts Discussed in Thread: CC3220SF, , UNIFLASH

Tool/software: Code Composer Studio

nortos: How to convert *.out to *.bin?

  • 0
    TI__Mastermind 40965 points

    Hi,

    Are you trying to convert the .out of a complied example to a .bin manually? All of the examples in the CC32xx SDK should have a post-build setup that performs the conversion from .out to .bin automatically.

    If you really want to perform it manually, you can use the following command:

    ${CG_TOOL_ROOT}/bin/armobjcopy -O binary --only-section .text --only-section .const --only-section .cinit --only-section .resetVecs ${BuildArtifactFileName} ${BuildArtifactFileBaseName}.bin

    Where ${CG_TOOL_ROOT} is the path to your compiler bin folder, ex. ccs/tools/compiler/ti-cgt-arm_20.2.1.LTS

    and where ${BuildArtifactFileName} is the name of your .out file.

    Let me know if you need more clarification on converting .out files, or have further questions on the .bin build process.

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Intellectual 350 points

    Hi,

    Thank you for your detailed reply.

    My CCS version is 9.2. The result of automatic compilation is as below:

    ......

    Finished building target: "uartecho_CC3220SF_LAUNCHXL_nortos_ccs.out"

    C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS/bin/armobjcopy -O binary --only-section .text --only-section .const --only-section .cinit --only-section .resetVecs uartecho_CC3220SF_LAUNCHXL_nortos_ccs.out uartecho_CC3220SF_LAUNCHXL_nortos_ccs.bin
    makefile:175: recipe for target 'post-build' failed
    process_begin: CreateProcess(NULL, C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS/bin/armobjcopy -O binary --only-section .text --only-section .const --only-section .cinit --only-section .resetVecs uartecho_CC3220SF_LAUNCHXL_nortos_ccs.out uartecho_CC3220SF_LAUNCHXL_nortos_ccs.bin, ...) failed.
    make (e=2): 系统找不到指定的文件。

    gmake[2]: [post-build] Error 2 (ignored)

    In CCS9.2, I can't find 'armobjcopy ', but I find 'arm-none-eabi-objcopy'. So I  edited the makefile. But, still failed. The result is:

    Finished building target: "uartecho_CC3220SF_LAUNCHXL_nortos_ccs.out"

    C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS/bin/arm-none-eabi-objcopy -O binary --only-section .text --only-section .const --only-section .cinit --only-section .resetVecs uartecho_CC3220SF_LAUNCHXL_nortos_ccs.out uartecho_CC3220SF_LAUNCHXL_nortos_ccs.bin
    makefile:175: recipe for target 'post-build' failed
    C:/ti/ccs920/ccs/tools/compiler/ti-cgt-arm_18.12.3.LTS/bin/arm-none-eabi-objcopy:uartecho_CC3220SF_LAUNCHXL_nortos_ccs.out: file truncated
    gmake[2]: [post-build] Error 1 (ignored)

    What's the mean?

    Thank you sincerely!

  • 0 in reply to cy w
    TI__Mastermind 40965 points

    Hi,

    The post build step I provided assumes you are using CCS 10, or at least have the latest v.20.2.1 TI ARM compiler.

    For earlier versions of CCS + the TI ARM compiler the steps are different. Looking through my old workspace materials, it appears that the old method to make the .bin from a .out used this command:

    ${CCS_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin ${BuildArtifactFileName} ${BuildArtifactFileBaseName}.bin ${CG_TOOL_ROOT}/bin/armofd ${CG_TOOL_ROOT}/bin/armhex ${CCS_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin

    Does running that command as a post-build step work for you?

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Intellectual 350 points

    Hi,

    Running that command as a post-build step can generate *. bin. Then I burn the *.bin using UniFlash5.2.0, but the board(LAUNCHCC3220MODASF) didn't work as I designed.

    I am sure my burn process is OK.

  • 0 in reply to Michael Reymond
    Intellectual 350 points

    Hi,

    I have upgraded CCS to version 10.1. It works well.

    Regards.

  • 0 in reply to cy w
    Intellectual 350 points

    Hi，

    I have a new issue: I have burned  the *.bin to flash and it works well,  when I want to continue debugging, I can't  connect to the target.

    I have tried to restore to factory status ,failed too.

    Can you give me some help?

    Best regards.

  • 0 in reply to cy w
    Guru 73255 points

    Hi,

    It is likely that your device is in production mode. Please use Uniflash software to switch into development mode. Additional information you find here.

    Jan

  • 0 in reply to Jan D
    Intellectual 350 points

    Hi,

    Yes, my Image mode is production mode. 

    According to your instructions, I switch into development mode, it's OK.

    Sincerely thanks.