• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 487 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.

No debug connection to a CC2640

Harald Ilg
Genius 3060 points

Hy,

I have asked pretty much the same question before:

Can't connect

I have received some helpful hints about exception handling, but no answer to my question. My situation again: After running without any problems for some weeks some of my devices get in a state, where they don't advertise any more, are not connectable any more and obviously the software does not run any more.

I can't see anything special on the tags, battery voltage is quite normal, nothing extraordinary happened to them, after resetting them they continue to run without any issues.

Since my last question I built in the exception handling:

void myExceptionHandler(exceptionFrame *e, unsigned int execLr)
{
    HAL_SYSTEM_RESET();
}

Which apparently works (tested by an illegal memory access:

uint8_t *myAccess;
myAccess = (uint8_t*)0x12345;
globalArray[5] = myAccess[95];

But still, ever once in a while (2 devices out of 20 after 2 weeks) gets into this bad state. When trying to connect the debugger I get this error message:

I am pretty stuck in this situation. Any hints?

Regards

Harald

  • 0
    TI__Guru** 105180 points
    Hello Harald,

    I remember this thread quite well. Unfortunately, given the low rate of occurrence, it's difficult to provide a meaningful answer based on a description.

    Can you post your schematic and layout, along with specs for the crystals you are using?
    Have you tried running the TI sample application (simpleBLEPeripheral) without enabling any sensors, or external communication, to see if the stability is maintained?

    Best wishes
  • 0 in reply to JXS
    Genius 3060 points
    Hy JXS,
    sorry for me not getting back to you, it might be a bit difficult to provide schematics and more information due to NDA reasons.
    At this moment, I hope to have overcome the issue after porting my project to BLE stack 2.1. During this action I noticed some difficulties with the boundary tool (has not been called properly). Could it be, that a non-functioning boundary tool setup leads to my behaviour?
    All of my devices run smoothly since beginning of this week...
    Regards
    Harald