• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 55 subscribers
  • Views 330 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.

CC1352R: osal_snv_write when Zbee is commisioning

Cosmin Staicu
Prodigy 140 points
Part Number: CC1352R
Other Parts Discussed in Thread: Z-STACK, SYSCONFIG

Hi!

I encountered a problem when using the DMM (Zbee + Ble) stack. Right now I am using a modified dmm example, running v4.20.1.04 stack and TI 20.2.1LTS compiler.

I managed to write some data to the Flash using the osal_snv_write, it works reliably, but whenever the zigbee stack is starting commision then the memory fails at write (the read still works)

The osal_snv_write returns a non-standard value EG "536923948 ". It does not matter if the Zbee is in commisioning mode or not or I restart the board. 
The only fix is to erase the flash and reprogram the board, then it works until I start Zbee commisioning.

Do you have any suggestions?

Thank you!

  • 0
    TI__Guru**** 218357 points

    Hi Cosmin,

    Z-Stack utilizes non-volatile memory to store network configurations which is initialized during network commissioning, as such it may be possible that this region of memory is conflicting with your application's SNV operations once the Zigbee network functionality starts.  I recommend that you further reference the SysConfig NVS internal settings and linker command (.cmd) files.

    Regards,
    Ryan