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.

BLE Stack v2.2 OSAL SNV



Hi, 

How to use osal_snv_write with the new v2.2?

When i execute 

    Grd_snv_status =osal_snv_read(Adress_Params,sizeof(One_Byte_Params), &One_Byte_Params);
	Grd_snv_status = osal_snv_write(Adress_Params,sizeof(One_Byte_Params), &One_Byte_Params);
Grd_snv_status  return "2".
In symbol, i change OSAL_SNV=0 to OSAL_SNV=1 but nothings..

Thanks
  • Hello SkyMan,

    If you use OSAL_SNV=0, there are no SNV pages and all calls will return invalid status.
    Can you provide more details? Since you are only showing snippets of code with variables, it's hard to provide an answer.

    Best wishes
  • Hi SkyMan,

    The BLE Stack v2.2 Developer's Guide (http://www.ti.com/lit/ug/swru393c/swru393c.pdf) explains how to use the SNV in Section 3.10.3. It also contains a code example for reading & writing to the SNV.

  • Thanks, i add 

    //Write first time to initialize SNV ID
    osal_snv_write(SNV_ID_APP, BUF_LEN, (uint8 *)buf);
    

    But now, i have a question :$

    In doc, it's write if i add OSAL_SNV=2 in symbols, "SNV data is protected against power-loss during compaction" but i have an memory error : 

    Description	Resource	Path	Location	Type
    #10010 errors encountered during linking; "sensortag_audio_cc2650stk_app.out" not built	sensortag_audio_cc2650stk_app		 	C/C++ Problem
    <a href="file:/c:/ti/ccsv6/tools/compiler/dmed/HTML/10099.html">#10099-D</a>  program will not fit into available memory.  placement with alignment fails for section ".const" size 0xa91 .  Available memory ranges:	cc26xx_app_oad.cmd	/sensortag_audio_cc2650stk_app/TOOLS	line 125	C/C++ Problem
    

    How can i up memory .const ?

    I use sensortag_audio project app & stack.

  • Hi SkyMan,

    There is not enough available space for the SensorTag Audio project to enable 2 page SNV. You can decrease the size of the project by removing other features such as the OAD. See this thread for more ideas to reduce your flash size: https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/512971