• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 471 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:

Does the CC2340 support for flash programmer?

Generating bin files and CCFG files for CC2340R5

Aries Fang
Prodigy 100 points
Other Parts Discussed in Thread: LP-XDS110, LP-EM-CC2340R5, UNIFLASH

Hi,

Already refer to the last section image update example in the docs. (/cfs-file/__key/communityserver-discussions-components-files/538/CC23xx_5F00_BootLoader_5F00_draft.pdf)

I modified the cc13xx-sbl tool to program CC2340.

The UART of LP-EM-CC2340R5 can be directly used for programming without using LP-XDS110.

However, I have question during the implementation.

After completing the BLDR_CMD_CHIP_ERASE command. All main flash bank sectors not protected by FCFG1 and CCFG protect bits will be erased. The CCFG will be erased once the bank erase has completed.

When the CCFG erased, CCS and uniFlah will display an error message(Error -1274 @ 0x0)

It is necessary to reprogram the Default CCFG.

Workround:

1. I have built the CC2340 example (host_test), which can be burned into the LP-XDS110 + LP-EM-CC2340R5 EVM board using CCS.

2. Then use uniFlash to export data.

    host_test_512k.bin (512K bytes), address range: 0x0 - 0x7FFFF

    ccfg.bin (2K bytes), address range: 0x4e020000 - 0x4E0207FF

Where to find bin file & CCFG file???

Is there an easy way to generate bin file & CCFG file?

May I ask if the mass production will still be burned in this way?

Thanks,

Aries

  • +1
    TI__Guru* 94028 points

    Hi Aries,

    Thank you for reaching out.

    One option option for you could be to protect the CCFG sector so it is not erased by the BLDR_CMD_CHIP_ERASE command.

    I have no better option than the one you are using to generate the CCFG.

    The final silicon should be delivered with a valid CCFG area. So this workaround should not be required anymore.

    I hope this will help,

    Best regards,