Segger Embedded Studio debugging

[smok]

Hello Nordic

I am testing SEGGER EMBEDDED STUDIO and I think it is little buggy.

When i simulate NRF52 application without actual device (I can not

debug on hardware because I don’t have one yet).So when I simulate

not all mcu registers reflect the code being processed. For example I have

written

NRF_RADIO->FREQUENCY=3;

But simulated register didn’t change to reflect that line of code, there are

Many more examples like this. Even worse because when I attached dev

Board (other than Nordic device) I found that programmed device do not

reflect code in editor that was built for that device. Could somebody explain

Why this happens with this TIP TOP development ide.

  

[awneil]

Note that Segger Embedded Studio is a 3rd-party product, nothing to do with Nordic - the clue is in the name.

So you need to raise support issues with Segger.

As to simulation, where did you read that SES fully supports the nRF chips?

EDIT

From the SES Manual (with my emphasis):

"Core Simulator:As well as providing cross-compilation technology, SEGGER Embedded Studio for ARM provides a PC-based fully functional simulation of the target microcontroller core so you can debug parts of your application without waiting for hardware"
https://www.segger.com/downloads/embedded-studio/EmbeddedStudio_Manual 

Things like the Radio are not part of the CPU core!

[smok]

Ok,thanks, simulation ok. But you are absolutely certain that the same code will be reflected perfectly on actual hardware when i will use it in conjunction with j-link?

[Jørgen Holmefjord]

smok said:

But you are absolutely certain that the same code will be reflected perfectly on actual hardware when i will use it in conjunction with j-link

This is something you need to ask Segger. Nordic does not support any chip simulation. I do not expect any of the peripherals of the chip to work in a simulated environment. CPU part of application might work.