• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 400 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.

LAUNCHXL-CC1352R1: Read/Write to Non-Volatile memory in DMM

Yash 101
Expert 1130 points
Part Number: LAUNCHXL-CC1352R1


Hello,

I am using TI DMM_15.4_Remote_Display example.  I went through the ssf.c file and found the instances where read and write are being used. I followed the nv_external example in Resource Explorer and also referred  to this e2e link -->    

My main objective is to store the information received from the BLE app in the NV memory. I found the read/write functions and tried to replicate the same in remote_display code in BLE. But I am confused with the 3 types of ID's that are being used.

Also, if I want to store the data coming from BLE to NV, then, are the following configurations correct? What should be the itemID and subID?

/* Setup NV ID */
id.systemID = NVINTF_SYSID_BLE;
id.itemID = 0;
id.subID = 0;

I tried with the above configuration, but the sensor node stopped sending 15.4 data as soon as I changed the Reporting_Interval from the Mobile app.

With the changes mention, can you help me in knowing if I am headed in the right direction and/or what changes will I have to do to make it work?

Thanks and Regards,

Yash.

  • 0
    TI__Mastermind 23636 points
    Hello Yash,

    Do you need this data to be in no volatile or can it be passed down from stack to stack?

    What data are you trying to store?

    Regards,
    AB
  • 0 in reply to AB
    Expert 1130 points

    Hi AB,

    Appreciate your quick response.

    Answering your question,

    My aim is to write the data received from the BLE mobile app in Non-Volatile Memory. for example, right now, I am trying to store the Sensor_Report_interval value received from the mobile app to the NV. 
    I had another question regarding that,

    Can I write the data received from the app right away or is there a certain way to do it (let BLE stack complete its proceedings and then store it)?

    Also, can you please elaborate what you meant by "stack to stack", Did you mean the protocol stack (BLE stack to 15.4 Stack)?

    Thanks and Regards,

    Yash.

  • 0 in reply to Yash 101
    TI__Mastermind 23636 points
    Hello YAsh,

    You should be able to write as soon as you get it, I would recommend that you set an event and then serve this event when the stack is no processing any data. As stack services are more important that writing to flash which you can do while the stack is not doing anything.

    Yes, what I meant by stack to stack was ble to 15.4stack.

    Regards,
    AB