Difference between different HEX files found in build/zephyr folder of nRF Connect SDK project

[witch_mountain]

Hi all! 

I've been working on a project using the nRF Connect extension for VS Code and I've been trying to figure out which HEX file in my build/zephyr folder for my application I'm supposed to flash onto the Thingy 91? I'm asking based of this closed post from ~2 years ago.  Thingy 91 not connecting to VS studio 

I know I'm supposed to be looking for the app_signed.hex file but instead I have:

• b0_container.hex
• s0.hex
• s0_image.hex
• s1.hex
• signed_by_b0_s0_image.hex
• signed_by_b0_s1_image.hex
• signed_by_mcuboot_and_b0_s0_image_moved_test_update.hex
• signed_by_mcuboot_and_b0_s0_image_signed.hex
• signed_by_mcuboot_and_b0_s0_image_test_update.hex
• ssigned_by_mcuboot_and_b0_s1_image_moved_test_update.hex
• signed_by_mcuboot_and_b0_s1_image_signed.hex
• signed_by_mcuboot_and_b0_s1_image_test_update.hex

There's a lot more HEX files than expected and because this was from a few years ago I wanted to ask if what I'm looking for is under a different name? 

Thanks!

[Einar Thorsrud]

Hi,

Please see Output build files.

[witch_mountain]

Hi, 

Yes so I did look through that document before posting and tried those hex files and tired to rebuild to get the app_signed.hex file. I'm trying to flash my application onto the Thingy 91 device and it seems to not be working either through the programmer app or through VS Code. 

Thanks

[witch_mountain]

Hi!

Hmm that's what I suspected but I wanted to make sure, thanks. Looking a the build error I have, I already have my code file in the same larger folder as my toolchain as other posts on Devzone say to move your code to stop the errors. I'm not sure what to do in my case? 

[Einar Thorsrud]

Hi,

You can check the documentation here for how to handle undefined reference to __device_dts_ord_<N>.

[witch_mountain]

Thanks for the direction!

Quick question while I look into the provided documentation, for the NMOS transistors on the Thingy 91, looking at the devicetree overlay are they the P0.13-P0.20 that are connected to the adc block or the pmw2 block? On the hardware files for the Thingy 91 I know that P0.13-P0.16 are the pins associated with the transistors.

Thanks!

[witch_mountain]

So I've been trying to follow through with the devicetree documentation (having some issues trying to implements the led examples to the Thingy91 NMOS pins) to try and debug what's going on here and at the moment this is what I have in my devicetree:

and I'm not entirely sure if this is how I'm supposed to configure the pins I want on devicetree before i can initialize them in main.c? 

Some guidance would be really great! Thanks!

[Einar Thorsrud]

Hi,

I assume you are looking at this because110 (from the error message) maps to pwm2 in your generated devicetree_generated.h?

The pins are configured in the device tree in the snippet you have here. You need to enable the config for PWM as well.

If using the nrfx API you can refer to the samples under modules/hal/nordic/nrfx/samples/src/nrfx_pwm/. As you are using pwm2 you would have to add CONFIG_NRFX_PWM2=y to your project configuration.

If using the Zephyr API you can refer to zephyr/samples/basic/blinky_pwm/, and see the overlay files for the nrf9160 as well as the prj.conf for the config that enables pwm (CONFIG_PWM=y).

[witch_mountain]

Hi!

You would be correct to assume that I had an 110 error. Based on the zephyr.dts file I found that the NMOS pins on the Thingy91 correspond to the pins under pwm2 which is what I'm trying to use. 

I follow you're advice with the blinky_pwm example (thank you so much for that!!) and I've run into this little error:

Wasn't able to find anything relating to this error so would love to understand what exactly is being underdefined?

Thanks!

[Einar Thorsrud]

Hi,

I do not immediately see what the problem could be here. Do you get an error or warning about this in the build log as well, or is it just from the intellisense in VS Code?