RAM retention issue

RE: RAM retention issue

Vidar Berg — Thu, 21 Mar 2019 17:37:36 GMT

Hi Jyoti,

[quote user="Jyoti"]But I do have the Segger RTT Viewer open to look at the log. Does that mean the program is running in debug interface mode?[/quote]

Yes, RTT goes through the debug interface.

[quote user="Jyoti"]Also, I have evaluation version of keil, so I think scatter file will not work[/quote]

That's correct. You can't edit the scatter file in the lite version. This is why I didn't use the scatter file in the example I sent you.

For IAR it shouldn't be necessary to create a new linker section. You can try to define your variable like this:

__no_init uint8_t m_addl_adv_manuf_data[ADV_ADDL_MANUF_DATA_LEN] @ <RAM address> ; (IAR doc)

Or if you chose to use Segger embedded Studio:

uint8_t m_addl_adv_manuf_data[ADV_ADDL_MANUF_DATA_LEN] __attribute__((section(".non_init")));

RE: RAM retention issue

Jyoti — Thu, 21 Mar 2019 16:11:03 GMT

Hi Vidar,

Thanks for the response and the example. I have not defined DEBUG in the project settings and I am not debugging the project from the IDE. But I do have the Segger RTT Viewer open to look at the log. Does that mean the program is running in debug interface mode?

Also, I have evaluation version of keil, so I think scatter file will not work. How do I do the similar thing of creating IRAM2 in IAR?

Thanks,

Jyoti

RE: RAM retention issue

Vidar Berg — Thu, 21 Mar 2019 09:13:09 GMT

Hi Jyoti,

[quote user="Jyoti"]Thanks for the response. Does that mean that we do not need ram retention if NRF52 just waking up from system off mode. As the RAM is not reset when waking up from system off then I can expect for it to retain it's content.[/quote]

Sorry, I meant to say that the RAM power settings are retained, not the RAM itself. RAM blocks are power gated in system OFF so you cannot expect data to be kept without retention enabled. Also, note that in debug interface mode the device will enter emulated system OFF mode, which means that RAM will remain on. That could be another reason for why you didn't have to enable retention in your test.

I have made an example based on the ble_app_uart project in sdk 15.3.0 with a "noinit" section placed at the end of RAM. The project is attached below along with some screenshots showing relevant project settings. Hope this helps.

Adding IRAM2 for NoInit data:

I have not found a way to selectively chose which variables to place in NoInit without touching the Scatter file so l defined the m_addl_adv_manuf_data variable in a separate source file:

And the *.map file confirms that m_addl_adv_manuf_data got placed in IRAM2

Example project. You can test it by performing the following steps:

1. Extract zip and copy it to \nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral. Compile and program

2. Power cycle the board to ensure that the chip goes out of debugging mode

3. Open a serial client and open the Jlink COM port (assuming you have a DK)

4. The app will enter system OFF mode after 5 seconds of advertising

5. Wait 5 seconds and press button 1 on the DK for wake-up

6. You should see the "Valid data in no init section" message in the UART log if the data was retained.

devzone.nordicsemi.com/.../ble_5F00_app_5F00_uart_5F00_w_5F00_ram_5F00_retention_5F00_test.zip

RE: RAM retention issue

awneil — Wed, 20 Mar 2019 16:34:12 GMT

[quote userid="77452" url="~/f/nordic-q-a/45106/ram-retention-issue/177424"]I am using Keil. How do I know if it is placed correctly in non initialized section?[/quote]

Check the Linker Map file.

[quote userid="77452" url="~/f/nordic-q-a/45106/ram-retention-issue/177424"]what is the correct way of putting it on non initialized section?[/quote]

Whatever it is would not be specific to Nordic - so check Keil documentation.

Search the Keil forum: http://www.keil.com/forum/

RE: RAM retention issue

Jyoti — Wed, 20 Mar 2019 15:56:52 GMT

Hi Vidar,

Thanks for the response. Does that mean that we do not need ram retention if NRF52 just waking up from system off mode. As the RAM is not reset when waking up from system off then I can expect for it to retain it's content.

I am using Keil. How do I know if it is placed correctly in non initialized section? what is the correct way of putting it on non initialized section?

Thanks,

Jyoti

RE: RAM retention issue

Vidar Berg — Wed, 20 Mar 2019 14:28:58 GMT

Hi Jyoti,

The power settings are retained until you power cycle the chip, maybe that could explain why you didn't have to enable retention for the second test.

Are you using Keil/SES or GCC? I wonder if the m_addl_adv_manuf_data variable gets placed correctly in a "non initialized" section since it seems to work when you use RAM_MEMORY_TEST_ADDRESS pointer.

Best regards,

Vidar