• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 280 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.

CC3220SF: Device abort bug in Carrier Wave mode

Hnz
Guru 39650 points

Part Number: CC3220SF

Hi Team,

I want to report a minor bug in NWP related to Carrier Wave (CW) radio test mode. It seems that multiple consecutively opening and closing CW mode may to cause device abort. Generally this is not a big deal, but I want to report found problem only. I can imagine that radio testing modes were not extensively tested for a stability.

Additional information:

  • Device: CC3220SF
  • SDK + SP: 3.10.00.04, 3.11.0.6
  • Own code based on code from radio tools 1.0.3.7
  • Error from handler:
    • SL_DEVICE_EVENT_FATAL_DEVICE_ABORT
    • DeviceAssert.Code: 3
    • DeviceAssert.Value: 0

Regards,

Jan

  • 0
    TI__Mastermind 28285 points
    Hnz,

    Can you test this on the latest Radio Tool 1.0.3.10 and see if it's still a issue?

    BR,
    Vince
  • 0 in reply to Vincent Rodriguez
    Guru 39650 points
    Hi Vince,

    I use my own code based on radio tools code. Code related to TX CW mode is same at 1.0.3.10 and 1.0.3.7 version.

    Occurrence of this issue increasing in case of lowering time between closing previous and opening new sockets in SL_AF_RF mode. Delay 500ms or more dramatically decrease occurrence of this device abort error. With Radio tool GUI is probably not possible to simulate issue because it not fast enough to send close and open RF socket command. We was not able simulate issue in TX_CONTINUOUS mode which we have already implemented inside our firmware.

    We have already implemented workaround with delay between close and open socket. From this reason we don't need assistance with this issue from TI side. I want only want to report bug in NWP.

    Jan