Location for reading in memory

Samuel Zottis Dal Magro

Other Parts Discussed in Thread: Z-STACK

Hello.

I have the genericApp example of the cc2538.
I want to know where I record something in non-volatile memory and how to do it?

Thank you!

over 8 years ago

0 Luis Luna over 8 years ago

Expert 1620 points

Hi Samuel,

There is documentation regarding this in OSAL API.pdf (section 10), this comes with the SDK. In the code you can refer to OSAL_Nv.h

Basically you have to initialize an Nv ID with the length of the data to be store and the data (osal_nv_item_init), you have to know this Nv Id as you will have to refer to whenever you want to read/write the data. After being initialize you can read/write with the rest of the API (osal_nv_read, osal_nv_write)

Hope this helps!

0 YiKai Chen over 8 years ago

Guru 735695 points

To add on to Luis reply, NV ID after 0x0401 is reserved for application usage if you use Z-Stack.

0 Samuel Zottis Dal Magro over 8 years ago in reply to Luis Luna

Expert 1780 points

Thank you Luis.

So in osal_nv.h I indicate the id and the data?

My biggest doubt is, which .c or .h I modify?

Thank you very much in advance!

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

NV ID used by Z-Stack are defined in ZCommDef.h,

0 Samuel Zottis Dal Magro over 8 years ago in reply to YiKai Chen

Expert 1780 points

Thank you!

My doubt is where the data like, .c or .h

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

I couldn't understand your question. Can you elaborate? What do you mean data like,.c or .h ?

0 Samuel Zottis Dal Magro over 8 years ago in reply to YiKai Chen

Expert 1780 points

Thank.

To where I enter osal_nv_item_ init, osal_nv_write and osal_nv_read.

In which .c or .h?
For example: I use osal_nv_item_init in GenerecApp.c?

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

You can call those APIs at where you want to store data in GenericApp.

0 Samuel Zottis Dal Magro over 8 years ago in reply to YiKai Chen

Expert 1780 points

Thank you very much!

Great answers.

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

You are welcome.

0 Samuel Zottis Dal Magro over 8 years ago in reply to YiKai Chen

Expert 1780 points

I implemented an example that you gave in another post
uint8 nv_test=0;
uint16 nv_test_id=0x0401;
osal_nv_item_init(nv_test_id, 1, NULL);

osal_nv_write(nv_test_id, 0, 1, &nv_test);
osal_nv_read(nv_test_id, 0, 1, &nv_test);

but there were errors like:

expected an identifier
explicit type is missing ("int" assumed)
identifier-list parameters may only be used in a function

Can you help me?

Thank

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

I put the example code in GenericApp_Init and it build successfully. You can refer to the following codes in red.

void GenericApp_Init( uint8 task_id )
{
GenericApp_TaskID = task_id;
GenericApp_NwkState = DEV_INIT;
GenericApp_TransID = 0;

// Device hardware initialization can be added here or in main() (Zmain.c).
// If the hardware is application specific - add it here.
// If the hardware is other parts of the device add it in main().

GenericApp_DstAddr.addrMode = (afAddrMode_t)AddrNotPresent;
GenericApp_DstAddr.endPoint = 0;
GenericApp_DstAddr.addr.shortAddr = 0;

// Fill out the endpoint description.
GenericApp_epDesc.endPoint = GENERICAPP_ENDPOINT;
GenericApp_epDesc.task_id = &GenericApp_TaskID;
GenericApp_epDesc.simpleDesc
= (SimpleDescriptionFormat_t *)&GenericApp_SimpleDesc;
GenericApp_epDesc.latencyReq = noLatencyReqs;

// Register the endpoint description with the AF
afRegister( &GenericApp_epDesc );

// Register for all key events - This app will handle all key events
RegisterForKeys( GenericApp_TaskID );

// Update the display
#if defined ( LCD_SUPPORTED )
HalLcdWriteString( "GenericApp", HAL_LCD_LINE_1 );
#endif

ZDO_RegisterForZDOMsg( GenericApp_TaskID, End_Device_Bind_rsp );
ZDO_RegisterForZDOMsg( GenericApp_TaskID, Match_Desc_rsp );

#if defined( IAR_ARMCM3_LM )
// Register this task with RTOS task initiator
RTOS_RegisterApp( task_id, GENERICAPP_RTOS_MSG_EVT );
#endif
{
uint8 nv_test=0;
uint16 nv_test_id=0x0401;
osal_nv_item_init(nv_test_id, 1, NULL);

osal_nv_write(nv_test_id, 0, 1, &nv_test);
osal_nv_read(nv_test_id, 0, 1, &nv_test);
}
}

0 Samuel Zottis Dal Magro over 8 years ago in reply to YiKai Chen

Expert 1780 points

Yes! It worked!

So the function has already written 0 in id 0x0401?

If I want to write something as a struct is the same logic?

Thank you!

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

Yes, the logic is similar.

0 Samuel Zottis Dal Magro over 8 years ago in reply to YiKai Chen

Expert 1780 points

Thank Very much!

Any data you want to write or read in memory put into the GenericApp_Init function?
If network layer too, or is it in another function?

Sorry for the questions, but I'm a beginner in the area.

Thank you.

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

Not only in GenericApp_Init, you can put those code at anywhere you want to write or read NV.

0 Samuel Zottis Dal Magro over 8 years ago in reply to YiKai Chen

Expert 1780 points

Ok!

In any GenericApp function can I read or record?

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

Yes, I had replied you at least three times. You can do it anywhere you want to do it.

0 Samuel Zottis Dal Magro over 8 years ago in reply to YiKai Chen

Expert 1780 points

Thank.

Sorry for the inconvenience

0 YiKai Chen over 8 years ago in reply to Samuel Zottis Dal Magro

Guru 735695 points

You are welcome.

Zigbee & Thread

Zigbee & Thread forum

Location for reading in memory