My Development Setup
Windows 10 , nRF5_SDK_15.0.0_a53641a , I am using Segger Embedded Studio for ARM V5.10a
My Development Setup
Windows 10 , nRF5_SDK_15.0.0_a53641a , I am using Segger Embedded Studio for ARM V5.10a
You are using an old nRF5 SDK, the latest is nRF5 SDK v17.1.
In general it's a bad idea to put data in UICR that you need to update run-time, since the only way to update data in UICR will be to erase UICR, which can impact pin reset, readback protection and NFC. So data written in UICR should be production data/configuration that is read-only by the application.
If you need to store and update data in the application, then you can for instance use FDS:
https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_fds.html
You are using an old nRF5 SDK, the latest is nRF5 SDK v17.1.
In general it's a bad idea to put data in UICR that you need to update run-time, since the only way to update data in UICR will be to erase UICR, which can impact pin reset, readback protection and NFC. So data written in UICR should be production data/configuration that is read-only by the application.
If you need to store and update data in the application, then you can for instance use FDS:
https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_fds.html
Hii Kenneth,
In my case , I want to generate serial number during compile time.I had generated serial number via JFLASH Tool & stored that in UICR register (@ CUSTOMER[2] i.e., UICR_ADDR_0x88 ) . I did that, my serial number is write properly on flash memory .But i want to send that serial number to BLE Frame. For that i used below logic in frame :
m_beacon_info1[15]=UICR_ADDR_0x88>>24;
m_beacon_info1[16]=UICR_ADDR_0x88>>16;
m_beacon_info1[17]=UICR_ADDR_0x88>>8;
m_beacon_info1[18]=UICR_ADDR_0x88;
[Note : My serial number is 32 Bit & my m_beacon_info1 is of 8 Bit.] so bit shifting logic used here
when i pass serial number (12) to BLE Frame i get different serial number ( its ffffffff) .
( my ble frame also disturbed)