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

CCS/CC2640: BLE module Bricks

Will Baker
Prodigy 110 points

Part Number: CC2640
Other Parts Discussed in Thread: CC2650, CC2650MODA

Tool/software: Code Composer Studio

1) Is it possible to unbrick a cc2640 BLE module? If there is, please explain.

2) I am having issues writing to memory addresses 01F000 - 01FFA7 ( near CCFG area). The following srec command is used to generate a BIN file:

 srec_cat btc.srec -motorola -fill 0xFF 0xcf74 0xD000 -fill 0xFF 0x1E000 0x1EFFF -fill 0xFF 0x1F408 0x1FFA7 -o my_bt_image.bin -binary

The BIN file, my_bt_image.bin is sent to the BLE module OTA, after download have complete the module bricks. Is there a better way to fill this area? Please help.

Thanks

  • 0
    TI__Expert 4435 points

    Hi Will,

    I have assigned an expert to help you with your issue. Which SDK version are you using?

    Best Regards,

    Jenny

  • 0 in reply to Jenny T
    Prodigy 110 points

    Hi Jenny,

    I am using ble_sdk_2_02_02_25

  • 0 in reply to Will Baker
    Prodigy 110 points

    Jenny,

    Forgot to mention that CC26xx/CC12xx Forced Mass Erase option of the SmartRF Flash Programmer 2 ver. 1.8.1 app was used several times to seem to erase, target mass erase was successful as shown below. However, after mass erasing the debug interface is still locked. 

    Thanks

  • 0 in reply to Will Baker
    TI__Expert 5345 points

    Hi,

    I have a few questions that I need to resolve before I can help you.

    • Can you please clarify what you mean by "brick"?
    • Are you using custom hardware, based on CC2640?
    • Can you try to reproduce your issue on a LaunchPad?
    • Can you please clarify what's the difference between the first and second image?

    Thanks,

    Luis

  • 0 in reply to Luis M
    Prodigy 110 points

    Hi,

    1) A bricked device is a device that can not be fixed through normal means. In my case, SmartRF Flash Programmer declared my CC2650 was inaccessible, and that the device Debug interface was locked. This message could be seen in the 2nd screenshot that has Failed in red.

    2) I am using CC2650MODA

    3) LaunchPad was not use because it does not support FOTA (firmware-over-the-air). But it was used to test Forced Mass Erase and reprogramming (in that order)

    4) if you look closely at the images, note the 1st image with the Green Success bar, in the status window it shows the app successfully erases device using CC26xx/CC13xx_Forced Mass Erase option. The 2nd image with the Red Failed bar, shows the app failed to program the same CC2650MODA device previously erased. Forced Mass Erase was tried on LaunchPad and reprogrammed using the same option shown in the 2nd image programmed the device without issues.

  • 0 in reply to Will Baker
    TI__Expert 5345 points

    Will,

    Thanks for your answers.

    I have a few comments:

    1. It is possible to disable flash erasing and to disable JTAG access (independently of each other) using the registers in the CCFG area. Please refer to the CC26x0 Technical Reference Manual (swcu117i.pdf), section 9.1 Customer Configuration (CCFG) and specially 9.1.1 CCFG Registers. It is possible that you did that when you programmed the device. Please review your file.
    2. Please review this similar thread.
    3. Please review the CC2640 BLE OAD User's Guide, located on your BLE stack installation: C:\ti\simplelink\ble_sdk_2_02_05_01\docs.
    4. I recommend that you use the tools provided for the file handling, located at C:\ti\simplelink\ble_sdk_2_02_05_01\tools\oad. This is all covered in the OAD guide I mentioned on the previous point.
    5. Can you try reading the device? What's the result? Can you do a power cycle after a mass erase, and then try reading?

    Thanks,

    Luis

  • 0 in reply to Luis M
    Prodigy 110 points

    In reference to questions #1-4, I tried those step prior to posting my question on this Forum. Answer to #5: no, no no.  Based on your questions it sounds like I am out of luck.

    Thanks for your help

  • 0 in reply to Will Baker
    TI__Expert 5345 points

    I'm really sorry. It seems that you did disable all JTAG access.

    -Luis