One small question: as I understand there’s no way to program using nrf Connect SDK and have a terminal output from Xiao nrf52840 via the USB? Even if using external program/utility outside of VS Code?
BTW, I have a Xiao expansion board with the LCD, so my last resort is just to print some debug messages there if there’s no other good way.
I have started the NCS fundamentals Academy, so far so good, until I probably hit some topics where I really need the DK board. Just want to pass as much as possible on the low-cost xiao setup with UF2 firmware upload feature to get a better understanding whether this fits me or not.
Who told you that? LOL, No this is NOT true, You certainly can. things like Logging output and Debugging output are both possible. On the expansion board when plugged in Shows up in the Serial ports (monitoring on the SDK terminal) or as I do Use the Serial terminal program in the Nrf_connect for Desktop Programs.
See the White Cable., It’s all in what you do and learn.
Start A New thread or resurrect an older one related to this topic.
I have a couple on here, some of which is covered, but worth revisiting. This one has gotten off track but good stuff none the less, Folks can bookmark it for future reference.
You can do a lot with the Xiao Expansion brd. it’s a foundational building block, connected to a external Debugger is were the true power of these devices and connections show themselves. Speed in development and Quick diagnosis for undocumented enhancements (Bugs) make them worth every P&J for lunch instead of Char-Hut and other side hustles makes saving , acquiring and owning such tools a pleasure to do WORK!
HTH
GL PJ
You should know these things if you plan on doing ANY real productive work with this stuff IMO. start there.
Ah! Thanks! I was just able to find this command to run in the terminal:
screen /dev/cu.usbmodem14301 115200
but you are correct, it is indeed available in the VS Code as the nrf Serial Terminal! Even without the expansion board. It requested lots of parameters I don’t understand, except the baud rate, but it was able to connect and show me the output!
Ha-ha! I’ve just realised I can use expansion board to use a normal size RESET button to put XIAO in the bootloader mode. My god, such a revelation. No more mambo-jumbo with the jumping wire end and that small reset button on xiao nrf. Posting just for fun
Little by little I am following the NRF Academy courses.
I’ve just started the BLE one yesterday
And one thing triggered me there:
Important - The nRF Connect SDK contains an alternative controller implementation, the Zephyr Bluetooth LE Controller. However, we strongly recommend using the SoftDevice Controller, as it is specifically designed for the nRF52, nRF53 and nRF54 Series devices.
This referred me back to our discussion above about nrf connect + MCUBoot + Zephyr BLE controller vs nrf SDK (old) with SoftDevice.
I had a feeling, that MCUBoot + Zephyr BLE is the way to go with nrrf Connect, however, the Academy tells me the nRF connect recommedns the SoftDevice controller. Am I missing anything here as I do have a dissonance now?
Yes, SO Nrf_sdk has a defined Nrf52840 SOC DTS file. The Zephyr mainline board repo doesn’t have a Seeed Xiao in it so They try and use the nrf DTS and it ofcourse causes issue’s. YOU can West command your way to installing , Building and flashing just with west commands, and say Menuconfig is all you would need. Its a chicken & egg Situation.
Zephyr is the underlaying layer, Nrf_sdk is on top of that. However the underlayer relies on the upper layer for the board support, You see that makes it appear AFU’d That is to say You need to have the proper West – Version and paths very straight before you get fancy with multi-image DFU moves
The future is MCUboot +app+DFU (serial, BLE, webpage)
here is why,
Zephyr Bluetooth LE Controller
This is a generic Bluetooth Low Energy (BLE) controller that comes with Zephyr OS.
It is not optimized specifically for Nordic devices but is available as an alternative.
It works across multiple platforms, including some Nordic chips, but lacks Nordic’s proprietary optimizations.
2. SoftDevice Controller (Recommended for nRF52, nRF53, nRF54)
This is Nordic’s official BLE controller, developed and optimized specifically for Nordic’s nRF series.
It provides better performance, efficiency, and power consumption for Nordic chips.
It is thoroughly tested and supported by Nordic Semiconductor.
Why Nordic Recommends SoftDevice Controller?
It is optimized for power efficiency and performance on Nordic devices.
It has better support for Nordic-specific features like advertising extensions, long-range mode, and high-duty cycle scanning.
It is actively maintained and tested by Nordic, ensuring better stability and reliability.
Nordic has it on lock so just keep going there’s is all I ever needed, does everything and more, and on the Nrf54L15 Silicon it’s a GAME changer.! Period.
The other thing is getting the partitions correct for the MCUBoot to work and be DFU’ Ninja
LOL, No this is NOT true, You certainly can. things like Logging output and Debugging output are both possible. On the expansion board when plugged in Shows up in the Serial ports (monitoring on the SDK terminal) or as I do Use the Serial terminal program in the Nrf_connect for Desktop Programs.
PJ 
