• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 40 subscribers
  • Views 274 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/CC3220SF-LAUNCHXL: Error connecting to the target

Erica Kim
Prodigy 20 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF

Tool/software: Code Composer Studio

Tool/software: Code Composer Studio

I've downloaded an example program: portable_CC3220SF_LAUCHXL_freertos_ccs.I was able to execute this program but every time I press 'q', I get the following error message:

Cortex_M4_0: JTAG Communication Error: (Error -242 @ 0x0) A router subpath could not be accessed. The board configuration file is probably incorrect. (Emulation package 9.2.0.00002) 
Cortex_M4_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

Then I get this connection issue. Can't connect to the board. (Need to do factory reset to recover but same thing happens after pressing 'q').I did not modify the code.

Can someone please help?

Error connecting to the target:
(Error -241 @ 0x0)
A router subpath could not be accessed.
A security error has probably occurred.
Make sure your device is unlocked.
(Emulation package 9.2.0.00002)
  • 0
    TI__Mastermind 22935 points

    Hi Erica,

    This is because the power manager is on. When you hit quit, UART gets closed so the device automatically goes into deep sleep which disables the debug inteface.

    Jesu

  • 0 in reply to Jesu
    Prodigy 20 points

    Hi Jesu, 

    So is this expected behavior? if the device goes into deep sleep, we get that error message? And need to reset the board to reload another program?

    I remember when I first ran this program, I didn't get that error message and I didn't have to reset the board to reload another program.

    Thanks,

    Erica

  • 0 in reply to Erica Kim
    TI__Mastermind 22935 points

    Yes. This happens because when you press 'q' UART_close is called. This causes the task to block on the sem_wait semaphore in the while(1) loop where it waits for you to press the button again. Because all tasks are blocked and there is nothing to do the device automatically goes to sleep which causes the debug session to end. 

    Jesu