• State Answer Suggested
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 485 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.

CC2538: Write to NV at specific address

Bumblebee
Expert 2575 points
Part Number: CC2538
Other Parts Discussed in Thread: Z-STACK

Hi TI,

Is there a way to write only at a specific register address and specific column in NV memory? I've tried using the API but somehow, when I try to reprogram the chip, the memory is written in a different address, that is, sometimes it's at 0x0027e260, sometimes at 0x0027e800.

  • 0
    Genius 3415 points
    Hi Bumblebee,

    You can look at the section 10 in the OSAL API.pdf provided at Z-Stack 3.0.0\Documents\API folder. In order to have a new item yo need to use osal_nv_item_init() function, then osal_nv_read() and osal_nv_write() in order to read and write the NV item. The NV items are defined in ZComDef.h so you can look to the items already reserved and add new Id's from 0x0401 to 0x0FFF. By the way I don't think that you need to care about the memory locations where the NV data is stored.

    I hope this helps,
  • 0 in reply to Jose Maria Alvarez
    Expert 2575 points
    I see, but how do I check in SmartProgrammer 2 the data written to the NV address if it keeps on changing?
  • 0 in reply to Bumblebee
    Genius 3415 points

    Hi Bumblebee,

    The NVM section is defined from 0x0027C800 to 0x0027F7FF, so you can read the NVM in the edit section by reading 12287 bytes from the address 0x0027C800.

    Regards,

  • 0 in reply to Jose Maria Alvarez
    Expert 2575 points
    Thanks Jose. Within 12287 bytes, how should I know which exact address and start/end of column I've written to using the NV api? If you can share how to pinpoint this, would be very useful for node failure analysis using only the smart programmer 2 in the future.