• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 329 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.

CC2642R: cc2642R1 routine uart2echo: The hex file generated by CCS does not run after burning

Susan Ren
Prodigy 345 points
Part Number: CC2642R
Other Parts Discussed in Thread: SIMPLELINK-CC13XX-CC26XX-SDK, LAUNCHXL-CC26X2R1, UNIFLASH

Hi Team,

CCS enables the arm hex utility of properties. After downloading the generated hex file with flash programmer 2, it doesn't work. Only after the .out file is downloaded, the readback is saved as hex, and then rewritten, it can work. CCS has a warning when hex is generated, showing that padding is added.

I tested it in CCS's intel hex and the motoroa S hex formats, and the flash programmer 2 is not working.

What is the reason for this? Can I generate hex directly ??

Working environment: CCS11.2

Chip: cc2642r1

sdk:5.40

Best Regards,

Susan Ren

  • 0
    TI__Guru**** 218887 points

    Hi Susan,

    Try adding the following Post-build steps from Project Properties -> Build -> Steps:

    ${CG_TOOL_HEX} -order MS --memwidth=8 --romwidth=8 --intel -o ${ProjName}.hex ${ProjName} 

    This generally works for SIMPLELINK-CC13XX-CC26XX-SDK projects which generate hex images.  You can also try adding the same flags/options inside the CCS hex utility if desired

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Genius 10295 points

    Hi Ryan,

    The customer verifies a hex and an out file generated (the firmware prints the serial output data). After many comparisons, it is confirmed that the hex file still does not work, and only the out file generated at the same time can work (the serial port can output content). The problem also exists in the simple_peripheral routine. He can't generate hex file via CCS. However, after adding this post-build step, there is no longer a warning when generating hex.

    (Added the post build step you mentioned in properties: ${CG_TOOL_HEX} -order MS --memwidth=8 --romwidth=8 --intel -o ${ProjName}.hex ${ProjName})

     

    Thanks,

    Annie

  • 0 in reply to Annie Liu
    TI__Guru**** 218887 points

    Hi Annie,

    I did not experience any issues with loading the hex file generated from uart2echo_CC26X2R1_LAUNCHXL_tirtos_ccs in SIMPLELINK-CC13XX-CC26XX-SDK v5.40 after including the shared post-build step.  I tested both Uniflash and Flash Programmer 2, after which it was verified that characters could be echoed from a terminal.  Simple peripheral projects already include this post-build step and have been verified to work as expected.  The customer is experiencing an issue unrelated to the generated hex image and should erase all device memory before attempting to re-progam.  Are they loading a BIM image consecutively and using LAUNCHXL-CC26X2R1 hardware?

    Regards,
    Ryan