About FLASH writing to "DE C0 AD DE FE 01 1E F1"

[takashina hiroki]

SDK: 15.3.0
Example: ble_app_multirole_lesc
Device: EYSHJNZWZ (nRF52832)

I called "pm_init" to do "PeerManager".
Then, a part of FLASH has been written to "DE C0 AD DE FE 01 1E F1".
Please tell me the cause of this.
Also, please tell me the meaning of this written value.

[tesc]

Hi,

This is the page tag for Flash Data Storage (FDS), which is the library used by Peer Manager for storing peer information in flash. As you can see there are two possible values for the second word; one for swap pages and one for data pages. The pages reserved for FDS should not be used for other purposes.

Regards,
Terje

[takashina hiroki]

Let me ask additional questions.

I am using "SEGGER Embedded Studio".
When debugging with "SEGGER Embedded Studio", it was confirmed that "DE C0 AD DE FE 01 1E F1" was written.

Next, I wrote the generated HEX file to the device using "nRFgo Studio".
After that, when I turned on the power and called "pm_init", I thought that "DE C0 AD DE FE 01 1E F1" would be written.
However, "DE C0 AD DE FE 01 1E F1" was not written.

Please tell me the cause of this.

[tesc]

Hi,

For all of the SDK examples using a SoftDevice, the SES project is set up so that both the application and the SoftDevice gets programmed to the nRF. If you program the hex file through other tools, you must make sure to program both the application hex file and the correct SoftDevice.

Please note also that nRFgo Studio is deprecated, as functionality is replaced by the nRF Connect Programmer app or the nrfjprog command line programming tool (part of nRF Command Line Tools).

Regards,
Terje

[takashina hiroki]

I have programmed both the application hex file and the correct SoftDevice by "nRFgo Studio".
But this is happening.
If both the application HEX file and the correct SoftDevice are programmed, it will be the same phenomenon as when debugging with "SEGGER Embedded Studio".
Is my idea wrong?
Please let me know if there are other causes.

Also, "nRFgo Studio" is deprecated, what is the recommended program tool?

[tesc]

Hi,

I recommend that you try with the examples/peripherals/blinky example first, as with that example it is very easy to see if everything is running as intended or not.

Recommended tools are nRF Connect Programmer application or nrfjprog, see links in my previous post.

Regards,
Terje

[takashina hiroki]

What should I check with the examples/peripherals/blinky example?
I saw the source code, but FDS is not used.
Since this ticket describes the behavior by FDS, this example has a different meaning.

[takashina hiroki]

I am sorry.
The conclusion was a program error.

I confirmed that the program was running on different routes when debugging and writing HEX files.
Also, the process of deleting FLASH was running only when writing a HEX file.
This process removed "DE C0 AD DE FE 01 1E F1".
This problem was solved by correcting the processing of the program.

[tesc]

Hi,

takashina hiroki said:

What should I check with the examples/peripherals/blinky example?

Check to see that you are able to program the application (and SoftDevice) correctly with the programmer that you use. The blinky example is well suited for that, as it is very easy to confirm it works as expected (it blinks LEDs.)

I see that you found out what was the issue. I am happy to see that!

Regards,
Terje

[takashina hiroki]

I confirmed using the examples/peripherals/blinky example.
I have confirmed that programmer can program the application (and SoftDevice) correctly.
As I said above, it seems that it was a program error.