CC2650 osal_snv

SkyMan

Expert 1275 points

Other Parts Discussed in Thread: CC2640, CC2650

Hi,

I need help to save values in memory flash.

I read the datasheet development but i don't understand how to save values in flash memory.

I code this :

   //*******OSAL_SNV************//
    	uint8 Item_id = 0x80; //This is in bcomdef.h
    	uint8 snv_status;

    	/*Save*/
    	snv_status = osal_snv_write(BLE_NVID_THOMAS,sizeof(value), value);

		/**Control save**/
		if ( snv_status == 0) //Sauvegarde Ok
			SensorTag_blinkLed(Board_LED2, 5);//G
		else //Sauvegarde PAS OK
			SensorTag_blinkLed(Board_LED1, snv_status);//R
	//***************************//

But my LED1 blink two like snv-status, thus it return "OSAL_SNV Value = 2" if we understand the "3.10.4 Using Simple NV" in the datasheet development. I tryed to erase memory with

"osal_snv_iinit(void)" but it doesn't work.

Thanks,

over 9 years ago

0 YiKai Chen over 9 years ago

Guru 735685 points

For using osal_snv_write, you can refer to the discussions in e2e.ti.com/.../1797159

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

Thanks, i change "#define OSAL_SNV 2" to 1 in SensorTagStack / OSAL / OSAL_SNV_WRAPPER.C but now when i built stack, i have that error : <<#1965 cannot open source file "NVINTF.h">>.

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

Don't change "#define OSAL_SNV 2" to 1 in SensorTagStack / OSAL / OSAL_SNV_WRAPPER.C. Try to put OSAL_SNV=1 in Predefined Symbols of Properties for SensorTagStack.

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

OK i try because i have'nt "OSAL_SNV" in my symbols, juste i have "NO_OSAL_SNV". I delete it and i remplace by "OSAL_SNV=1 "

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

Now, i have again :
#1965 cannot open source file "NVINTF.h" .ccsproject /SensorTagStack line 49, external location:

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

I have no error now if i don't deleete the "NO_OSAL_SNV" so i think it's good. How i can checked if my code is good?

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

I use BLE Stack 2.1 and I add "C:\ti\simplelink\ble_cc26xx_2_01_00_44423\Components\services\nv" to Include Options of Properties for SensorTagStack to fix the problem.

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

Thanks, i think it's good but how i can checked if my code is right? With the same code, the function "snv_status = osal_snv_write(BLE_NVID_CUST_STOP,sizeof(value), value);" return 2. It's not good no?

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

If osal_snv_write works correctly, it should return 0. I think you should use "&value" instead of "value" to parameter 3 of osal_snv_write like the following line:
osal_snv_write(BLE_NVID_THOMAS,sizeof(value), &value);

By the way, what is your BLE_NVID_THOMAS?

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

Adress, i use between 0x80/0x8F like it's say in the datasheet.

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

Here, i try with 0x8F and yes i use &value but it return 2 and not 0.

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

I just see but i have always the error "Can not Open source file "NVINTF.h"

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

I go here :

So when i add the path like it. I have always the same error. And i can't debug the *stack so i can't not checked if my osalwrite is good.

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

Sorry for the monolog :). It's good for the "NVINTF.h" but I have : "#1009-D program will not fit into available memory. placement with alignment fails for section ".rodata" size 0x6e . Available memory ranges:" line 104, 106 and 107 in SENSORTAGSTACK / TOOLS.
I have delete the "NO_OSAL_SNV" and add "OSAL_SNV=1" of symbols predifined.. I desesper :").

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

1. You have to change the following two lines in ccsLinkerDefines.cmd which is under SensorTagStack->TOOLS
--define=ICALL_STACK0_ADDR=0x0000F000
--define=ICALL_RAM0_ADDR=0x2000445C
to
--define=ICALL_STACK0_ADDR=0x0000000
--define=ICALL_RAM0_ADDR=0x20000000
2. Remove the following line from Post-build steps in Build of Properties for SensorTagStack.
"C:\Program Files (x86)\Texas Instruments\Boundary\Boundary.exe" -prj "ccs" -chip "CC2640" -lcf "${ORG_PROJ_DIR}/../../../../../common/cc26xx/CCS/cc26xx_ble_stack.cmd" -map "${PROJECT_LOC}/${ConfigName}/${ProjName}.map" -xml "C:\Program Files (x86)\Texas Instruments\Boundary\BoundaryConfig.xml" -cc "${ORG_PROJ_DIR}/../../../CCS/Config/ccsCompilerDefines.bcfg" -lnk "${ORG_PROJ_DIR}/../../../CCS/Config/ccsLinkerDefines.cmd"

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

Thank very much Chen,but it doesn't work. I have modified the two define and remove the line like you say but i have always the same error :

You can see in the screenshoot, i have this error,

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

I find that I cannot make SNV work on CC26xx SensorTag example with CCS but it works when I use IAR. If you don't have to use CC26xx SensorTag example, I would suggest you to use SimpleBLEPeripheral example to test SNV.

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

I delete my project sensortagstack and re-import it and it's ok but now, i have a error in sensortagApp : http://prntscr.com/apl5td

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

Yes, I see the same issue when I test SensorTag example SNV with CCS. That's why I suggest you to use IAR or switch to SimpleBLEPeripheral example.

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

I install IAR, i modified the same things like you post before?

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

The following steps are for IAR to use SNV in CC2650 SensorTag example.

1. Remove NO_OSAL_SNV and add OSAL_SNV=1 to Defined symbols in IAR->Options->C/C++ Compiler->Preprocessor of SensorTagStack

2. Change the following two lines in IAR-Boundary.xcl of SensorTagStack

--config_def ICALL_STACK0_ADDR=0x0000E000
--config_def ICALL_RAM0_ADDR=0x20004458

to

--config_def ICALL_STACK0_ADDR=0x00000000
--config_def ICALL_RAM0_ADDR=0x20000000

3. You have to build SensorTagStack twice.

4. You can use osal_snv_write in your SensorTag application now.

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

I can't debug, i have error when i follow the developper guid.
1. I make the SensorTagApp and twice the sensortagStack.
2. I set SensorTag App to active.
3. I go to project>Download>Download active application (no error, it's ok).
4. I set Sensortagstack to active.
5. I go to project>Debug without Downloading (no error, just warning : http://prntscr.com/apm7pv).
6. I go make the sensortagstack and i go to project >Download and debug the application (it's ok).
7. I set sensortagApp to active and i download and debug (I have : http://prntscr.com/apm9d0)
So the sensortagapp don't debug. In the android'application, i can't see the sensor with bluetooth.

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

I cannot see the picture. By the way, can you debug original SensorTag example if your don't modify anything?

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

It's good with the project, it debug, without problem maybe with the stack, i have : http://prntscr.com/apmgfk (you can see it?). When i debug, i don't have the LED 1, 2 which blink...

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

I have delete the http://prntscr.com/apmh92 too

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

You cannot debug SensorTagStack. You can only debug SensorTag application.

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

I have that ( http://prntscr.com/apmhuk) when i changed

--config_def ICALL_STACK0_ADDR=0x0000E000
--config_def ICALL_RAM0_ADDR=0x20004458

to

--config_def ICALL_STACK0_ADDR=0x00000000
--config_def ICALL_RAM0_ADDR=0x20000000

It's good if i don't change. Why? it's a memory problem?

(Can you send me your IAR Sensortag Project if it's good to oselwrite for you?)

Thanks

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

I cannot see your attached image. Anyway, I attach my SensorTag project.

2860.SensorTag.zip

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

In your files, when i charge with IAR, i haven't the stack, it's not a problem? Or i add my stack?

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

I have this when i make download & debug my application after debugged my stack

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

Can you debug original SensorTag example with IAR?

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

Yes i can. No problem. I try to modif and debug point to point.

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

So, you still cannot debug SensorTag project that I attach to you?

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

No, but it not the same version of the IAR. I have a message like what IAR make update but it possible that the file cannont start.

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

If you do the first two steps,

1. Remove NO_OSAL_SNV and add OSAL_SNV=1 to Defined symbols in IAR->Options->C/C++ Compiler->Preprocessor of SensorTagStack

2. Change the following two lines in IAR-Boundary.xcl of SensorTagStack

--config_def ICALL_STACK0_ADDR=0x0000E000
--config_def ICALL_RAM0_ADDR=0x20004458

to

--config_def ICALL_STACK0_ADDR=0x00000000
--config_def ICALL_RAM0_ADDR=0x20000000

Then, build SensorTagStack and what do you get?

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

Yes, i retest that, it's good, but i don't modif the IAR-Boundary.xcl. I have always
--config_def ICALL_STACK0_ADDR=0x0000F000
--config_def ICALL_RAM0_ADDR=0x20004458
I need to save for 4k-B, it's possible if i not change that?
I past your file and it's good for the App.

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

Do you mean you can use osal_snv_write successfully now?

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

Yes, i try like your file with the same function and breakpoint. I can save, and point to point, i can see that i can write and after read the variable.

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

Sounds good. So, you can use NV ID from 0x80 to 0x8F which is 4KB in total.

0 SkyMan over 9 years ago in reply to YiKai Chen

Expert 1275 points

Ok, and thanks, and i can sav one value for example on the adress 0x80? Or if i need to sav most values, i need to sav array?

0 SkyMan over 9 years ago in reply to SkyMan

Expert 1275 points

Maybe i can sav a vector?

0 YiKai Chen over 9 years ago in reply to SkyMan

Guru 735685 points

You should save data to SNV in a byte array format.

Bluetooth®︎

Bluetooth forum

CC2650 osal_snv