• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 55 subscribers
  • Views 1721 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/CC1310: Error -1170 and -2064 debugging rfEasyLinkTx but not rfEasyLinkRx

Onur YILDIRIM
Intellectual 620 points
Part Number: CC1310
Other Parts Discussed in Thread: SIMPLICITI,

Tool/software: Code Composer Studio

Hello,

I am having the errors below when debugging "RF TX" examples. But it does not happen when debugging "RF RX" examples. 

Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
Cortex_M3_0: GEL Output: Board Reset Complete.
Cortex_M3_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.576.0)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.576.0)
Cortex_M3_0: JTAG Communication Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.576.0)

On the other hand "empty" example debugging successfully and I see blinking.

You can see my board from the thread below:

Do you have any idea why I am getting this on TX examples?

Best regards,

Onur

  • 0
    TI__Expert 6540 points

    Hi, did you modify the rfEasyLinkRx example or do you run it unmodified?
    Which rtos/sdk are you using? Are the two examples from the same SDK/tiros release?

    If on a custom target, can you  try the example on a LaunchPad to see if it works there?

    Can you try a mass erase with Flash Programmer 2, and then try to program it?

  • 0 in reply to FredG
    Intellectual 620 points

    Hello,

    I removed rfEasylinkTx and rfEasylinkRx projects from CCS workspace and re-imported them using resource explorer.

    I followed the Software > Simplelink CC13x0 SDK - v:1.30.00.06 > Examples > CC1310 Launchpad > Easylink > rfEasyLinkRx and Software > Simplelink CC13x0 SDK - v:1.30.00.06 > Examples > CC1310 Launchpad > Easylink > rfEasyLinkTx paths for importing to workspace.

    I hit the debug button without touching anything.

    Both of the projects debugged successfully on TI Launchpads (I have 2 CC1310 launchpads).

    rfEasyLinkRx project debugged successully on my CUSTOM CC1310 board and I see a blinking on pin 12 (This is green led on launchpad). But when I plug in my rfEasyLinkTx  loaded launchpad to USB, I see no blinking on my CUSTOM device on pin 11 (RED LED). This means receiver cannot receive a package.

    I tried to debug rfEasyLinkTx example without touching anything and I got a new error message:

    Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
    Cortex_M3_0: GEL Output: Board Reset Complete.
    Cortex_M3_0: JTAG Communication Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.576.0)
    Cortex_M3_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

    Also I tried Flashprogrammer 2. I can succesfully erase, program and verify. 

    Can you suggest anything about this situation? 

  • 0 in reply to Onur YILDIRIM
    Prodigy 50 points
    Hi Onur,

    Did you get any chance to go through your issue? I'm facing the same issue on my custom board...

    Regards
    Philippe.
  • 0 in reply to Philippe Lumbierres
    Intellectual 620 points

    Hi Philippe,

    I couldnt succeed on my custom board. What I have DIFFERENT from TI's launchpads:

    - I used 805 and 1206 package instead of 402 package. Also some some of them DIP. (I dont know this is a design mistake. If yes, it is very funny).

    - I used standart XTAL instead of TI's launchpad's SMD XTALs. 

    - I designed my board's RF side L shaped to antenna (because of small board dimensions) instead of "linear  to antenna".

    - I didnt cover a metal on MCU and other surrounding elements and ground it.

    And what I did? I bought "ready to go" CC1310 system on module.  :)

    Everything is OK now. 

    And what will you do?

    Onur

  • 0 in reply to Onur YILDIRIM
    Prodigy 50 points
    Hi onur,

    Thanks for your reply, it confirm me a hardware issue on my side as well.

    As I can observed the board resets continuously I finally found out it was during a TX. Thus the DCDC_SW voltage drops so the chip resets and debugger loose the connection. (for information reconnecting it I can see it is stuck at address 0x10003a12)
    In fact I forgot in my schematic a decoupling capacitor. I add it and now no more reset and I can debug the board as well, all with my custom board.
    I can go further now...

    I don't know if it could help.

    Thanks a lot.
    Philippe.