• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1027 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.

CC1310: Error flashing firmware using Flash Programmer 2

Kian
Expert 1595 points
Part Number: CC1310

Hi all,

I am encountering an error while flashing firmware onto a CC1310F128. It says the debug interface is locked. As such, I followed the instructions to do a mass erase and was able to successfully flash an image onto the CC1310.

However, without closing the program, when I try to flash firmware onto another CC1310F128, I am getting this error: 

I am unable to connect or do a mass erase unless I close the program and relaunch Flash Program 2. When I do a refresh, it says the debug interface is locked and I can do mass erase again. I have a few hundred CC1310 to flash and all of them have the debug interface locked somehow. I can't possibly be closing and re-launching Flash Programmer 2 every time. Anyone know what is wrong and how can I flash the firmware without having to close and reload the program everytime.

Thanks in advance.

  • 0
    Guru 735475 points
    What FW do you flash into your CC1310? Does the FW lock debug interface?
  • 0 in reply to YiKai Chen
    Expert 1595 points
    Hi Yikai,

    Those are modules which I bought and they have come with lock debug interface and I am using Flash Programmer 2 to write my own firmware in. I have hundreds of them to program.
  • 0 in reply to Kian
    Guru 735475 points
    If they have come with lock debug interface, I see no other choice that you have to do mass erase before you can download FW again.
  • 0 in reply to YiKai Chen
    TI__Guru**** 317180 points
    First, where did you get the modules from? It sounds a bit strange that you have received modules with locked debug interface. Do they come with pre-programmed image?

    You can try to run the CLI version of flash programmer 2. It looks like the program has some issues with enumeration of the chip when it tries to reconnect after a mass erase. This could be linked to a similar bug in the program that I believe will be fixed in the Q3 release.
  • 0 in reply to TER
    Expert 1595 points
    Hi TER,

    I bought these modules from a supplier in China. I believe they might have their own firmware inside and had locked it to prevent overwriting of their own firmware. I need to load my own firmware inside.

    So the trouble now is I have to close Flash Programmer 2 and restart the program for every single module that I want to re-flash. And its too much of a trouble. Will using the CLI version help?

    Thanks!
  • 0 in reply to Kian
    TI__Guru**** 317180 points
    By using a script and the CLI version you could potentially call flash programmer twice, once to do mass erase and once to reprogram the chip and hence avoid the original problem. It should be fairly easy to test.