nRFGo studio user Getting started with nRFConnect -- anatomy of the memory map?

[riceman0]

Hello, trying to make the leeap from nRFGo studio to nRFConnect, programming tool.  I have connected to an old device programmed with nRFGo, and see the memory map below.  I have a question to get me pointed in the right direction:

This is an old device using the S110 soft device.  With nRFGo studio, we just had to select the softdevice hex and it would place it where it needed to go.  Does nRFConnect know where to place things too?  When I drop the S110 and then my hex and then program it, it just seems to work -- but I've told I need to  be smarter when using it.  Generally speaking can I trust nRFConnect to lay out my hex and softdevice, no matter which SoftDevice I use?

Also, what is the green section at the top?  It doesn't appear when I program, but appears when I read back.  It's labeled "Application" and its 368 bytes long.

Thanks.

[Vidar Berg]

Hi,

.hex (intelHex format) files specify exact address locations for each data record so nrfgostudio and other program utilities don't have to make any assumptions about where to place the data.  

Also, what is the green section at the top?  It doesn't appear when I program, but appears when I read back.  It's labeled "Application" and its 368 bytes long.

Looks like the app is using this flash page for persistent storage and that it wrote 368 bytes with something on the first run after programming. It would have shown up during programming if it was part of the app image.

[riceman0]

Thank you!