Hello,
I am trying to debug and develop in the net core of the nRF5340 and am having trouble flashing and debugging from SES.
I started by following the guide posted here which works as described.
https://devzone.nordicsemi.com/f/nordic-q-a/72544/debug-nrf5340-net-core-using-ses
However if afterwards I make a change to only the net core hci_rpmsg code from within the net core project in ses (in this case only insert a nop and break on it) then proceed to flash using step 1 without erasing or flashing the app core (since nothing changed on app it shouldn’t need a reflash?) I get the following error in the image below.
Flashing just the net core with west from the command line works without issue.
I have also tested west with example thread projects where the app core blinks led 1 and 2 and the net core blinks led 3 and 4. I can flash these separate app images and net images that are not child projects using west without issue so it seems like a SES problem.
Additionally, after wiping the chip if I skip step 1 and only do step 2 to upload the merged.hex from the peripheral_lbs project it looks like the net core isn’t being flashed. I have to wipe the chip, flash net core, then flash app core from 2 SES instances in that order every time I change a line of code.
Which is strange since when using west to build and flash from the command line, I can build only the peripheral_lbs and the single merged.hex gets converted to GENERATED_CP_APPLICATION_merged_domains.hex and GENERATED_CP_NETWORK_merged_domains.hex flashed to both app and net core.
Again this seems like SES has an issue not present in the command line tools.
Is it possible to be able to flash and debug only the net core from one SES instance and not have to wipe and reflash the chip for every change with two SES instances open just to debug the net core while developing?
I am running SES for ARM Nordic Edition on Ubuntu 18.04 Linux V5.34a and JLink V7.20a
Building with west and debugging with Ozone v3.22e works and I am able to flash the net core without re-flashing app core or pre-erasing the chip as described above. If I cannot get SES working then this might have to be the next best thing.
