Hi, my name is Vincent.

I ended up here while hunting for documentation, solution and support.
I ended up watching https://www.youtube.com/watch?v=YgMmxa6gRqA . I was impressed by the communication skills and Zephyr’s overall knowledge!

I am actually very new to the Zephyr World and the Nordic development environment.
I have a nRF7002DK board, that I am trying to connect to Azure IoT Hub and provision a device with DPS.

I am able to build the Azure IoT Hub example on its own. But I struggle to integrate it with the rest of my code.

I am using the example from this specific version: v2.5.0\nrf\samples\net\azure_iot_hub

When I add it to my more extensive project, I end up with a flash size error.
I spent more than 3 days trying to fix the issues. But I believe, I need help now to unblock me.

Thanks in advance to anyone who is going to help me get unblocked and show me the path forward in my understanding.

Here’s the actual build error.

[489/616] Building C object modules/nrf/drivers/wifi/nrf700x/CMakeFiles/..__nrf__drivers__wifi__nrf700x.dir/osal/utils/src/queue.c.obj
[489/616] Performing build step for 'mcuboot_subimage'
[1/273] Generating ../../zephyr/include/generated/ncs_version.h
...
[273/273] Linking C executable zephyr\zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       60780 B        64 KB     92.74%
             RAM:      289580 B       440 KB     64.27%
        IDT_LIST:          0 GB         2 KB      0.00%
[498/616] Generating ../../zephyr/net_core_app_update.bin
image.py: sign the payload
[500/616] Generating ../../zephyr/net_core_app_signed.hex
image.py: sign the payload
[518/616] Generating ../../zephyr/net_core_app_test_update.hex
image.py: sign the payload
[599/616] Linking C executable zephyr\zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map 
cmd.exe /C "cd . && C:\ncs\toolchains\c57af46cb7\opt\zephyr-sdk\arm-zephyr-eabi\bin\arm-zephyr-eabi-gcc.exe  -gdwarf-4 @CMakeFiles\zephyr_pre0.rsp -o zephyr\zephyr_pre0.elf  && cmd.exe /C "cd /D C:\Nordic\milo_fw\nRF5340_app_core\build\zephyr && C:\ncs\toolchains\c57af46cb7\opt\bin\cmake.exe -E true""
c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: zephyr\zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
c:/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: region `FLASH' overflowed by 19476 bytes
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\c57af46cb7\opt\bin\cmake.EXE' --build 'c:\Nordic\milo_fw\nRF5340_app_core\build'

 *  The terminal process terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

@morinv what chip are you trying to use with the nRF7002? You may be able to get away with disabling CONFIG_LOG if you have that enabled. That takes up a good 20kB.

    jaredwolff

    Thanks for the hint.
    I deactivated the debug mode, and it was working again.

    But I am a little bit disappointed now! Because I can’t run into debug mode anymore!

    Again, thanks for the help.

    Regards,
    morinv

      You could disable other features you are not using or debugging temporarily as well if you still need logging. Also if you have an external flash chip you can configure the bootloader to pull the second slot off the external flash doubling your application space. This though, is a bit more advanced. 😉

      Terms and Conditions | Privacy Policy