Intermediate course, lesson 8 exercise 2 on nRF5340DK

[davidemania]

Good morning,

I am trying to understand how the bootloader process works on the nRF5340, and working on the excercises from the intermediate course. The target at the moment is an nRF5340DK board, while a custom board based on the same processor is being developed.

I made it to step 5, not everything is crystal clear in detail but the general picture about the bootloader and firmware update process is OK. The exercise asks to build the application and flash it to the board, I used nrf5340dk_nrf5340_cpuapp as a build configuration, is this ok?

Anyway after flashing the code to the board step 6 asks to connect to the target USB connector, near the reset button... may be this is a stupid question but where is the board supposed to get power after that? Nothing happens and no virtual COM port is shown in Windows device manager (while the J-Link USB gives two as usual).

Thanks to anybody that will help, Nordic development environment and documentation is good but I couldn't figure this out.

Besides, did someone try the excercise 1 on the nrf5340DK? I tried it but got nothing out of the serial terminal.

Regards, Davide

[Menon]

Hello,

Sorry, I was sick yesterday, which created the delay in responding.

 The exercise asks to build the application and flash it to the board, I used nrf5340dk_nrf5340_cpuapp as a build configuration, is this ok?

Yes, that should work.

Anyway after flashing the code to the board step 6 asks to connect to the target USB connector, near the reset button... may be this is a stupid question but where is the board supposed to get power after that? Nothing happens and no virtual COM port is shown in Windows device manager (while the J-Link USB gives two as usual).

The nRF USB port on the nRF5340 development kit can provide power to the device. Inside the product specification, see the section Power Supply (page No. 12). USB connector J3 has been defined there.

If you connect the nRF USB port, your device would be visible inside the device manager as a USB serial device with an indication of the port, not as J-Link. For example, see the screenshot below:

Kind Regards,

Abhijith

[davidemania]

I hope you are well now.

Just tried again, the board gets power but no serial port is visible in Windows device manager.

I tried to build the ready made solution, to see if that at least works, but got this error

C:/Users/Davide/zephyrproject/projects/inter_less8_exer2_solution/boards/nrf5340dk_nrf5340_cpuapp_ns.conf:4: warning: attempt to assign the value 'y' to the undefined symbol MCUBOOT_USE_ALL_AVAILABLE_RAM

error: Aborting due to Kconfig warnings

I tried commenting that line but got another error

-- Looking for pthread.h
-- Looking for pthread.h - not found
-- Could NOT find Threads (missing: Threads_FOUND)
-- Performing Test C_COMPILER_SUPPORTS_WFORMAT_SIGNEDNESS
-- Performing Test C_COMPILER_SUPPORTS_WFORMAT_SIGNEDNESS - Failed
-- Could NOT find Threads (missing: Threads_FOUND)
-- Configuring incomplete, errors occurred!
See also "C:/Users/Davide/zephyrproject/projects/inter_less8_exer2_solution/build/tfm/CMakeFiles/CMakeOutput.log".
See also "C:/Users/Davide/zephyrproject/projects/inter_less8_exer2_solution/build/tfm/CMakeFiles/CMakeError.log".
[3/309] Generating misc/generated/syscalls.json, misc/generated/struct_tags.json
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\cf2149caf2\opt\bin\cmake.EXE' --build 'c:\Users\Davide\zephyrproject\projects\inter_less8_exer2_solution\build'

Did someone manage to get this example running on a 5340DK board?