This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Do I have to worry about the address of softdevice, App etc. when using nRFgo Studio?

It is to my understanding that you DO have to worry about that when using keil download function or other means to program either the softdevice or your program to the nrf514xx /nrf518xx devices, but is the same thing necessary for nRFgo studio? And what are the telltale signs by which I will know that everything were written to the right place? Where in the UI can I look up to know that?

Parents
  • Assuming that you don't compile SoftDevice by yourself (obviously), and you take it from the SDK - hex has correct addresses inside, so you don't have to worry. You can read more about hex format here, so you could understand it better. Same for the application - it is flashed to location, where it is supposed to be flashed according to the compilation settings.

  • Well I'm just gonna slack it on and ask how exactly does nrf51xxx devices interact with the softdevice and my compiled firmware? As in, how does it know where in the memory does my firmware begin? Or, maybe the firmware address were given by a .s file (configurable in keil, that magic wand button), and relevant softdevice information can then be found in the firmware (decided by include header files)? I could use a bit more detail. Thanks in advance.

Reply
  • Well I'm just gonna slack it on and ask how exactly does nrf51xxx devices interact with the softdevice and my compiled firmware? As in, how does it know where in the memory does my firmware begin? Or, maybe the firmware address were given by a .s file (configurable in keil, that magic wand button), and relevant softdevice information can then be found in the firmware (decided by include header files)? I could use a bit more detail. Thanks in advance.

Children
No Data
Related