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.

CC1310: AUX RAM concern

Part Number: CC1310

Hi,

I've started using AUX RAM to solve a number of application specific feature requests we are seeing that extend beyond the unused RAM in the device; this prevents us needing to re-spin the hardware and replace 1000s of units that are in the field. I followed the guide here:

http://software-dl.ti.com/simplelink/esd/simplelink_cc13x0_sdk/4.10.00.10/exports/docs/proprietary-rf/proprietary-rf-users-guide/proprietary-rf-guide/aux-as-ram.html

which works very well. Though I did need to manually turn on the aux controller before I could use it, this step wasn't mentioned in the guide.

There is a section in the guide which concerns me:

"Certain objects, when put in AUX RAM can cause the application to crash. One should test for each object they want to store in AUX RAM."

I'm using about 1K of AUX RAM. Where almost every bit of that 1K can be set and will change every few seconds. I think we're looking at the sun burning out before I can test every object that can potentially exist in AUX RAM without some guidance. Could you be any more specific about this? What do you mean by object (aligned 16-bit value? unaligned 32-bit value?) Are there any specific memory addresses in AUX RAM where the controller will look for these "objects"?

Just now I'm using the lower 1K of AUX RAM. Would it be safer to use the upper 1K? 

NB: Using flash isn't an option because of the regularity of access.

Thanks

- Oliver