SES no long knows the $(Target), the simulator or the device register maps.

Question

I recently moved my custom board definition from the zephyr board dir to the nrf board dir, to unify my changes into on git repo for internal use. I think that's when the Segger Embedded Studio stopped knowing the $Target and the JLINK debug interface. Along with the nrf53 device register groups. 
 If I manually set the target and the debugger to jlink, it can debug find, but it loses this when I exec SES. It also does not know about other register groups such as GPIOTE and all others. 
 Is there a fix for this? Where does SES store that infomation?

Jordan Archer · Accepted Answer

Can you open the project under? And it appears that if you run cmake, SES loses all of the device and jlink info. nrf\projects\onedrop_pod\build_onedrop_cpuapp_pod1 
 The files: 
 CMakeCache.txt Output build.ninja mcuboot onedrop_pod.emSession regions.yml zephyr_modules.txt CMakeFiles app cmake_install.cmake modules partitions.yml rules.ninja zephyr_settings.txt Kconfig build.emProject hci_rpmsg onedrop_pod.emProject pm.config zephyr

SES no long knows the $(Target), the simulator or the device register maps.

Top Replies