• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 52 subscribers
  • Views 678 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:

LP-EM-CC2340R5: Unable to program CC2340 device via XDS110 debugger

LP-EM-CC2340R5: Unlock PG2.0 chip - suggested steps give error

Shashank Kulkarni
Intellectual 2930 points
Part Number: LP-EM-CC2340R5
Other Parts Discussed in Thread: CC2340R5

Hello team,

I tried out the steps mentioned by Ryan exactly as in the attached post. However, I see the log as below. I am also using CCS12.3.0 as the OP of that post.

Can you help to understand if I am committing a mistake here in the process of unlocking the CC2340?

Cortex_M0P: Flash loader: CC23xx_FLASH_LIBRARY_VERSION 3.17.09.20
CS_DAP_0: GEL Output: This GEL script should only be used when an invalid CCFF was programmed into a Loki Low Plus PG2.0.
Error code of @-614 or @-615 is expected to be thrown by the CCS before using this workaround!
CS_DAP_0: Error connecting to the target: (Error -615 @ 0x0) The target failed to see a correctly formatted SWD header. The connection to the target may be unreliable. Try lowering the TCLK setting before trying again. (Emulation package 9.11.0.00128)
CS_DAP_0: GEL Output: DAP core is connected! Programming a default CCFG to unblock the device...
UnblockLokiLowPlusPG2() cannot be evaluated.
Register not found: CFGAP_DEVICEID
at GEL_EvalOnTarget("CS_DAP_0", "'REG'::CFGAP_DEVICEID") [cc23xx_util.gel:15]
at ReadDeviceId() [cc23xx_util.gel:44]
at IsCC23x0R5() [cc23xx_util.gel:26]
at IsCC23xx() [cc23xx_dap.gel:33]
at EnterSaci() [unblock_loki_low_plus_pg2.gel:55]
at ProgramValidCcfg() [unblock_loki_low_plus_pg2.gel:23]
at UnblockLokiLowPlusPG2()

Regards,

Shashank

  • 0
    TI__Guru**** 207157 points

    Hello Shashank,

    Can you confirm that you are using PG2.0 hardware with SMARTRFTM-STUDIO 8, and that the same debug interface lock behavior was present before attempting the unlock script?  I will ask the Tools Team about the issue you are experiencing.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Intellectual 2930 points

    Hi Ryan,

    Ryan Brown1 said:
    Can you confirm that you are using PG2.0 hardware with SMARTRFTM-STUDIO 8,

    No, I am trying to use a customer board with CCS. They have inadvertently flashed a ble_basic project from an older version of the SDK. After the device got programmed the first time, it does not get programmed again and throws the error.

    Ryan Brown1 said:
    the same debug interface lock behavior was present before attempting the unlock script

    Yes, the same errors were seen.

    Kindly let me know what I can try out.. they have currently bricked 4 boards before I asked them to stop and ship those to me. Slight smile

    Regards,

    Shashank

  • 0 in reply to Shashank Kulkarni
    TI__Guru**** 207157 points

    By "PG2.0 hardware" I am not referring to the hardware EVM or LaunchPad version, rather the device revision.  The customer board should be capable of connecting to Smart RF Studio 8 with a JTAG interface.

    Does the customer encounter this issue when programming the new SDK version, SIMPLELINK-LOWPOWER-F3-SDK v7.10?  Have they submitted their custom design to SIMPLELINK-2-4GHZ-DESIGN-REVIEWS for further review?  And are you able to replicate behavior with a LP-EM-CC2340R5?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Intellectual 2930 points

    Hi Ryan,

    Thank you for your response and the questions!

    TLDR: I have two client boards, both have PG2.0 CC2340R5 chip on them. One is blank, the other is programmed with a firmware with the old SDK. The blank one is accessible over SWD (proved by the Smart RF Studio snapshot below), the programmed one is not. The GEL file that worked for the gentleman in the other post does not work for me although we are using the same software versions and (most) probably are in the same situation (SDK-Hardware mis-match).

    Answers to your questions below. 

    Ryan Brown1 said:
    By "PG2.0 hardware" I am not referring to the hardware EVM or LaunchPad version, rather the device revision.

    Same here - I refer to the device revision as well. Clement's email titled "CC2340R5 is RTMed" sent on 8 May had an image (pasted below) that indicated how to identify a revision B (PG 2.0) material. The client's board is mounted with a revision B (PG 2.0) material.

    Ryan Brown1 said:
    The customer board should be capable of connecting to Smart RF Studio 8 with a JTAG interface.

    Unfortunately, it is not. See below snapshot for what I see. The client board debug interface is SWD. I use XDS110EMU SWD pins to try to connect to Smart RF Studio 8. The first snapshot shows the bricked board status (device not detected). The second snapshot shows the unprogrammed board status (device detected).

    Ryan Brown1 said:
    Does the customer encounter this issue when programming the new SDK version, SIMPLELINK-LOWPOWER-F3-SDK v7.10?

    Since the device is not accessible over SWD, this does not work. Pasting the snapshot of the connection test here. Also, pasting below the log when I try to debug an example project from the SDK.

    Cortex_M0P: Flash loader: CC23xx_FLASH_LIBRARY_VERSION 3.17.09.20
    CS_DAP_0: Error connecting to the target: (Error -615 @ 0x0) The target failed to see a correctly formatted SWD header. The connection to the target may be unreliable. Try lowering the TCLK setting before trying again. (Emulation package 9.11.0.00128)
    Cortex_M0P: File Loader: Memory write failed: (Error -615 @ 0x0) The target failed to see a correctly formatted SWD header. The connection to the target may be unreliable. Try lowering the TCLK setting before trying again. (Emulation package 9.11.0.00128)
    Cortex_M0P: GEL: File: C:\Users\a0132277\workspace_v12_3_cc23xx\basic_ble_LP_EM_CC2340R5_freertos_ticlang\Release\basic_ble_LP_EM_CC2340R5_freertos_ticlang.out: Load failed.

    Ryan Brown1 said:
    Have they submitted their custom design to SIMPLELINK-2-4GHZ-DESIGN-REVIEWS for further review?

    Yes, the design has been reviewed by Jake - I am attaching the review report here.

    Schneider-5x5-DR-2023-02-15.pdf

    Ryan Brown1 said:
    And are you able to replicate behavior with a LP-EM-CC2340R5?

    I don't have an LP-EM-CC2340R5 with PG2.0 chip. Will place an order for one immediately.

    ******************

    I hope this clarifies, Ryan. Look forward to your help and unbricking the chip!

    Regards,

    Shashank

  • +1 in reply to Shashank Kulkarni
    TI__Guru**** 207157 points

    Shashank, thanks for the additional information.  First of all, my apologies for mentioning "JTAG", which is not available on the CC2340R5, when I should have written "SWD".

    In the unlocking script a board reset is done, which asserts the Reset line of CC2340R5,  If this fails then the above issue is a possibility. So the customer should check the reset line while issuing this gel script or Device reset option in CCS.

     

    This could also explain why the gel script works with LP-EM-CC2340R5 but not the customer PC board.  The customer should closely review their RST, GND, VCC, and SWDIO/SWDCK lines.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Intellectual 2930 points

    Hi Ryan,

    Thank you for the tip about the RESET line. It worked. The client has a RESET line coming out of another connector. I manually toggled from HIGH > LOW > HIGH just after the script execution. It worked on the second attempt itself.

    Accepting your answer as a resolution.

    Regards,

    Shashank