Hey, PJ. Thanks for the answer.
I am already closer to do some real programming: was able to run a CPP on nrf52840 with nrf Connect SDK. Will study the nrf SDK Academy course for sure.
I do not have a J-Link and it looks like a real bummer. To be honest, I’ve expected everything to magically work via the USB, similar to ESP32C3 (at least the serial communication). But then I understand that was an Arduino layer and programming with idf framework, most probably, the J-link is required as well.
I saw you were suggesting getting the nrf DK as a J-link. I don’t want to go for nrf52 DK, to be honest, since the nrf54 is out there already. Hence, a question: if I go nrf54 DK way, will I be efficiently able to still develop with Xiao nrf52840? So, the DK in this set up is just considered as a J-Link, correct? And then, the other advantage is that I am able to use nrf54DK as my next platform, testing my program for, let’s say, future migration to nrf54 chip. Does it sound legitimate? Alternatively there should be some cheap clones or analogs of Segger j-link, for example. Not sure how good are they.
Speaking of SoftDevice: do I understand correctly, that the ncs (nrf Connect SDK) is based on Zephyr and doesn’t use Soft Device? Like it is the latest and greatest thing? And they recommend the MCUboot. As I understand you need to have a J-link in order to flash the firmware with MCUBoot, so no drag&drop anymore. But is it the way to go? To be honest, I got confused on where the DFU BLE supported and where not. But as of today, it is the following in my brain: if you develop with NCS and need DFU BLE - you should go for MCUBoot.