Request: Thingy-91x support in DevAcademy Intermediate Exercise 3 – DFU with external flash

[sd30]

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-9-bootloaders-and-dfu-fota/topic/exercise-3-dfu-with-external-flash/

I have this exercise building under SDKv3.0.2/Windows11/VScode and running on a nrf5340dk board.

thingy-x91 (an active nRF product with an nRF5340 & spi external flash) is not listed on the exercise web page above as supported

>would it be possible to add thingy-91x or better time wise for you to reply here with the necessary changes?

https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91-X

https://docs.nordicsemi.com/bundle/ug_thingy91x/page/UG/thingy91x/hw_description/ext_memory.html 

I have tried to make it work but keep running into failures after 'add build configuration' - generate phase with errors like;

error: Aborting due to Kconfig warnings

-- Configuring incomplete, errors occurred!
See also "C:/Nordic/myapps/blinky_external_flash/build/CMakeFiles/CMakeOutput.log"

That log file contains only one line;

The system is: Windows - 10.0.26100 - AMD64

I am still learning how to troubleshoot generate phase problems.  It's not like traditional build/compiler/linker error troubleshooting.

It's not clear where some of the symbols come from in build\_sysbuild\autoconf.h for instance.

This file for thingy:91x/nrf5340/app is created with many changes vs a working build for the 5340dk/nrf5340/app, with it not being clear to me yet where the changes originate and how to control using prj.conf/, sysbuild.conf, sysbuild/mcuboot..conf files even after completing all devAcademy exercises thus far.

Some tips on how to setup thingx-91x for this exercise would be very helpful and time saving.

Thanks in advance.

[Benjamin]

Hi Richard,

I’ll be handling this ticket. Please note that due to summer vacation, there may be a slight delay in response times.

Best regards,

Benjamin

[sd30]

Thanks, i keep trying but also keep getting hard to decipher config errors so looking forward to expert advise. 

[Benjamin]

Hi,
I have forwarded this to the Academy developers. You will hear from me later this week.

Best regards,
Benjamin

[Benjamin]

Hi again Richard,

The DevAcademy team has clarified that the nRF Connect SDK Intermediate course is intentionally limited to Nordic DKs. Their reasoning is that many exercises depend on features like the onboard debugger, which Thingy devices lack. Supporting Thingies would require adding extra logic and exceptions throughout the course content, making the exercises more complex and less focused. The goal is to keep the material simple and easy to follow, and adding support for Thingy devices would make it more complicated.

[sd30]

Thanks for the update.

I should have mentioned, am using an external JTAG/SWD adapter (Segger) with the Thingy-91x to flash and debug - via the nice front panel connection on the board provided for this essential tool.  This works very well.

It would be reasonable to note in dev acadamy that non DK Nordic products are supported this way and that flashing using other means is out of scope for the course (or link to instructions you have elsewhere on the site)

BTW, I found a work around by modifying a copy of the thingy-91x board directory as below;

ncs/v3.0.2/nrf/boards/nordic/thingy91x/Kconfig.defconfig.nrf5340

Change 'y' to 'n' below.

config BOOTLOADER_MCUBOOT

default y if BOARD_THINGY91X_NRF5340_CPUAPP || BOARD_THINGY91X_NRF5340_CPUAPP_NS

This works but is there a better way to override this in the application configuration?  My newbie attempts to change the config result in configuration/build failures as you see up thread.