• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 281 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:

CC2642R: HCI_EXT_ModemTestTxCmd() Issue

CC2642R: HCI_EXT_EndModemTestCmd() issue in BLE SDK 2.4

Joshua Meyer
Expert 1080 points
Part Number: CC2642R

Hello, 

I recently ported our firmware to BLE SDK 2.4 to support the CC2642 Rev E silicon. While testing the ported software I noticed watchdog resets occurring whenever the HCI_EXT_EndModemTestCmd() API is called. I faced a similar issue back on SDK 1.6, which was fixed by modifying the stack's rom_init.c file. I believe this issue was fixed in some of the versions of the SDK between 1.6 and 2.4, but it looks like it's come back in 2.4.

I modified line 671 of \source\ti\ble5stack\rom\agama_r1\rom_init.c, to not have the "!" in the #if defined() on line 671, and this fixed the issue:

#if defined(CTRL_V50_CONFIG)
  (uint32)LL_EXT_EndModemTest,                               // ROM_JT_OFFSET[191]
#else // !CTRL_V50_CONFIG
  (uint32)ROM_Spinlock,
#endif // CTRL_V50_CONFIG

Will this be fixed in the SDK 3.1 release? I'd prefer not to have to modify stack files, as we don't currently have the stack / SDK under version control.

-Josh

  • 0
    TI__Guru 73361 points
    Hi Joshua,

    Is this a known issue that you found in the release notes?

    Can you provide me with steps and a minimal code example to reproduce this? You say the watchdog resets every time the HCI_EXT_EndModemTestCmd() is called?
  • 0 in reply to Marie H
    Expert 1080 points

    Hi Marie,

    I don't see anything in the release notes about this issue. It's pretty simple to reproduce, I'm guessing if you run the simple_peripheral example on a Launchpad, and just call HCI_EXT_EndModemTestCmd() at any point, the application will lock up. Without the change I made to rom_init.c, the API call routes to ROM_Spinlock(). It might be good to alert the engineers who responded to my previous thread about this issue, they'll know more (see link to related question at the top of thread).

    -Josh

  • 0 in reply to Joshua Meyer
    TI__Guru 73361 points

    Hi Joshua,

    Yes this is still an issue in the CC13x2_26x2 2.40 SDK. We will try to get it fixed in the next release.