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-CC1352P: osal_snv doesn't repond?

Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: UNIFLASH

Champs,

Any ideas/pointers where to look to debug osal_snv writes, and reads actually, though since I can't get the write to pass I wouldn't expect the read to work just yet, actually working?  So the project is kind of old, it's actually on a CC1353P2 SDK version 3.40.02; I was adding the osal SNV to the dmm_wsnnode with OAD so that I could serialize multiple boards over Bluetooth. 

I checked, and in main.c, I call osal_snv_init(), and it returns SUCCESS so I was feeling good. But, later in the code (a differnt task, but I don't think it matters) I try to write or read 12 bytes of data I am storing.  On a write, I get an error code of 0x01 (FAILURE), on the read I get an error code of 0x02 (INVALID_PARAMETER).  At least fo the read I could see that if it can't find that entry becauseit never wrote, that might make sense... so how do I get the write to work?

So here's the kicker, it's not the code; its the state of the board/chip.  So I have 4 boards, all with the same code.  THe two older boards i had from liek a year ago when I wrote this work fine; I can read/write osal....but I just got two new ones in yesterday and tried to FLASH them; and everything runs great EXCEPT for this osal_snv thing (I'm hoping that's a clue to you).  I can provide the project if you need it.  Where do I start looking?

  • Hi,

    If you can I would actually recommend you to update to the newest SDK. We made some changes to the NV driver (the layer below osal_snv) and it caused some issues for a while. I hope we have solved all of them now.

    Can you do a flash mass erase of all your devices, then re-do the test?

  • Marie,

    Thanks- I had forgot about the mass erase thing in Uniflash; that actually did it.  So for those reading that are ALSO using OAD, the steps I did to ultimately make it all work were:

    1) mass erase (its in the utilities tab in Uniflash)

    2) launched the BIM project from the SDK- you need this if using OAD(able) images

    3) launched my actual application- this doesn't overlap with anything in the BIM so this is all clean

    4) and then in my case, the app writes to the osal when commanded by certain BLE commands; but steps 1-3 are the most important

    Thanks