Nordic Academy exercise 2 does not build using SDK v3.2.4 and the Nordic Academy instructions

[peinal]

Trying to work thru the dev academy exercise 2 using v3.2.4 SDK. I presume this should work because the readme says must be greater than v2.8.0 for thingy91.

I made all of the modifications to the prj.conf and main.c files as per the instructions here https://academy.nordicsemi.com/courses/cellular-iot-fundamentals/lessons/lesson-2-cellular-fundamentals/topic/lesson-2-exercise-2/?version=v3.2.0

However, when I try to build I get the following error messages:

main.c,
    #include errors detected. Please update your includePath. Squiggles are disabled for this translation unit (/home/user/git/Cell/l2/l2_e2/src/main.c).
    cannot open source file \"ncs_version.h"
    cannot open source file \"zephyr/kernel.h"
    cannot open source file \"zephyr/logging/log.h"
    cannot open source file \"dk_buttons_and_leds.h"
    cannot open source file \"modem/nrf_modem_lib.h"
    cannot open source file \"modem/lte_lc.h"

CMakeLists.txt

   VERSION keyword not followed by a value or was followed by a value that
   WARNING: Using default MCUboot signing key file, this file is for debug use

Kconfig
The Button and LED Library for Nordic DKs must be enabled by CONFIG_DK_LIBRARY to be included in the build
The Modem library must be enabled by CONFIG_NRF_MODEM_LIB to be included in the build

MCUBOOT_UPDATE_FOOTER_SIZE (defined at subsys/dfu/Kconfig:55) was assigned the value

prj.conf
    The active build context 'build_1' does not use this file
    "UART": Unknown word.

I do not understand why the example exercise does not work 'out-of-the-box' and I also do not know how to fix each of the issues the build is having. Do I need to revert to an earliier version of the SDK for the Academy instructions to work?

Let me add that all of the suggestions AI made regarding these issue/this post were not the cause(s) of the issues. 

[Amanda Hsieh]

Hi Paul, 

Try opening the terminal via Manage Toolchains in the WELCOME frame, then execute "west update". 

I made all of the modifications to the prj.conf and main.c files as per the instructions here https://academy.nordicsemi.com/courses/cellular-iot-fundamentals/lessons/lesson-2-cellular-fundamentals/topic/lesson-2-exercise-2/?version=v3.2.0

You can refer to https://github.com/NordicDeveloperAcademy/cell-fund/tree/main/l2/l2_e2_sol 

Regards,
Amanda H.

[peinal]

That seemed to help: it eliminated the errors in the l2_e2 main.c. However, it did not fix everything. I still am getting the following:

[
{
"resource": "/home/pcalvert/git/Cell/l2/l2_e2/prj.conf",
"severity": 2,
"message": "The active build context 'build_1' does not use this file.",
},
{
"resource": "/home/pcalvert/git/Cell/l2/l2_e2/build_1/l2_e2/zephyr/.config.sysbuild",
"severity": 3,
"message": "CONFIG_MCUMGR_GRP_IMG_QSPI_XIP_SPLIT_IMAGE was already disabled. Missing dependencies:\nMCUBOOT_BOOTLOADER_MODE_DIRECT_XIP && MCUMGR_GRP_IMG_NRF",
},
{
"resource": "/home/pcalvert/git/Cell/l2/l2_e2/build_1/l2_e2/zephyr/.config.sysbuild",
"severity": 3,
"message": "CONFIG_WIFI_NRF70 was already disabled. Missing dependencies:\nDT_HAS_NORDIC_NRF7002_SPI_ENABLED || DT_HAS_NORDIC_NRF7002_QSPI_ENABLED || DT_HAS_NORDIC_NRF7001_SPI_ENABLED || DT_HAS_NORDIC_NRF7001_QSPI_ENABLED || DT_HAS_NORDIC_NRF7000_SPI_ENABLED || DT_HAS_NORDIC_NRF7000_QSPI_ENABLED || n && WIFI",
},
{
"resource": "/home/pcalvert/git/Cell/l2/l2_e2/build_1/l2_e2/zephyr/.config.sysbuild",
"severity": 1,
"message": "CONFIG_MCUBOOT_UPDATE_FOOTER_SIZE couldn't be set. Missing dependencies:\nMCUBOOT_IMG_MANAGER && IMG_MANAGER",

},
{
"resource": "/soc/nordic/nrf54h/Kconfig.defconfig",
"severity": 1,
"message": "PM_DEVICE_RUNTIME (defined at soc/nordic/nrf54h/Kconfig.defconfig:54,",
"source": "kconfig",
},
{
"resource": "/subsys/dfu/Kconfig",
"severity": 1,
"message": "MCUBOOT_UPDATE_FOOTER_SIZE (defined at subsys/dfu/Kconfig:55) was assigned the value",
"source": "kconfig",
},
{
"resource": "/CMakeLists.txt",
"severity": 1,
"message": "WARNING: Using default MCUboot signing key file, this file is for debug use",
"source": "cmake",
},
{
"resource": "/CMakeLists.txt",
"severity": 1,
"message": "VERSION keyword not followed by a value or was followed by a value that",
"source": "cmake",
"

Also, in the interim I have discovered that despite all of the reported items in the PROBLEMS tab, the build actually completes and I can flash it and it seems to work. Appears to perhaps be a vs code extension or build/reporting issue? All I know is that I should see zero warnings, zero errors on builds-- especially examples and tutorial builds. Right?  Thanks for the quick reply and the helpful suggestion! 7 down, 6 to go!

[Amanda Hsieh]

If you don't get any build errors and it can work as expected, you can ignore them. 

[peinal]

Thanks.