ERROR: The file specified is not a valid hex file, has data outside valid areas

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Thu, 23 Dec 2021 15:35:54 GMT

If with this module this is not possible do you an alternative module connection that i can make with a module BLE from nordic? That will accept the build and flash? thx in advance

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Thu, 23 Dec 2021 14:36:31 GMT

hi,

What you dont understand is that i have THEmodule yes, i already tested with simples DK it already worked with nrf52840and his config.

i'm using simple DK and everything worked fine until now with this new module. My only request was to help me with the errors that i have with my module... during the build and my incapacity to flash this with the right build configurations parameters.

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

Priyanka — Thu, 23 Dec 2021 13:37:59 GMT

Hi,

From the snippet I can see that you are configuring for a nrf52dk_nrf52805.

But you said that you have only a nrf52840DK? (And in the connected devices section it shows that you have connected a nrf52840DK)

I guess that you are still not familiar with the basics and I would emphasize on building ad running a normal DK first before moving onto the BC805 (I understand that this is a crucial module).

Every application has a set of DK that it supports. For the peripheral_uart sample, when you begin the VS Code page, and give the build configuration, you cannot select a different board name other than the one you are using, for eg, if you are using an nrf52840DK, then you have to select somewhat like this:

Only if you have an nrf52dk_nrf52805 (an nrf52dk with a nrf52805 chip on it) can you select the board as nrf52dk_nrf52805. Also, in the peripheral_uart example, this board is not supported, hence I am not sure whether it will work either.

You should try using the nrf52840DK and learn how this works and also learn a few basics which can be helpful in future.

Regards,

Priyanka

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Thu, 23 Dec 2021 10:27:37 GMT

and look what i have when i try to build.

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Thu, 23 Dec 2021 10:20:26 GMT

what do you think? thank you

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Thu, 23 Dec 2021 10:19:57 GMT

i cant flash the module with visual studio , i did the programmer thing and insert the zephyr.hex file and i have this

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Thu, 23 Dec 2021 10:18:30 GMT

Hi, i did everything that you tell me to do. I'm going to give you my log.devzone.nordicsemi.com/.../2021_2D00_12_2D00_23T08_5F00_21_5F00_33.184Z_2D00_log.txt

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

Priyanka — Wed, 22 Dec 2021 16:40:17 GMT

Hi,

I would suggest you to try using the nrf52dk_nrf52805. It is a modified version of the nRF52 DK that focuses on the limitations imposed by the nRF52805 IC (the flash size mainly), which is a cost-reduced variant of the original nRF52832. Since Nordic does not offer a development kit for the nRF52805, you can use this board to develop for 52805SoC while using the nRF52 Development Kit (PCA10040).

But, in order to program the BC805 module, you will need to connect to the 52840DK via Debug Out and build the "perpheral_uart" project. Then go to the build->zephyr->zephyr.hex and flash this hex file onto the DK via the Programmer App in nRF Connect for Desktop. You can find the guide to the Programmer app helpful. This is a guide to program the Dongle, but you can try the same steps for this case.

But first I would suggest you to familiarize yourself with Nordic Products and ways of programming these. We have various Development Kits and modules which can be programmed using the nrf5 SDK or the nRF Connect SDK.

Regards,

Priyanka

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 09:52:01 GMT

Do you think there is a solution?

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 08:56:41 GMT

the problem is that my module ( bc805) is the most important part of the project because i want to use this to integrate in my future product. thank you again in advance for your help ...

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 08:55:27 GMT

yes... i just did what you say and i can send any type of program..

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

Priyanka — Wed, 22 Dec 2021 08:51:02 GMT

Are you able to build the project successfully when you do not have the BLE BC805 module connected to the DK?

-Priyanka

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 08:39:38 GMT

i gave you what i have in my console

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 08:39:06 GMT

> Executing task: nRF Connect: Build peripheral_uart/build (active) <

Building peripheral_uart
west build --build-dir c:\ncs\projects\peripheral_uart\build c:\ncs\projects\peripheral_uart

[0/1] Re-running CMake...
Including boilerplate (Zephyr base (cached)): C:/ncs/projects/zephyr/cmake/app/boilerplate.cmake
-- Application: C:/ncs/projects/peripheral_uart
-- Zephyr version: 2.6.99 (C:/ncs/projects/zephyr), build: v2.6.99-ncs1-1
-- Found west (found suitable version "0.11.1", minimum required is "0.7.1")
-- Board: nrf52840dk_nrf52840
-- Cache files will be written to: C:/ncs/projects/zephyr/.cache
-- Found dtc: C:/ncs/v1.7.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (c:/ncs/v1.7.1/toolchain/opt)
-- Found BOARD.dts: C:/ncs/projects/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
-- Generated zephyr.dts: C:/ncs/projects/peripheral_uart/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/ncs/projects/peripheral_uart/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/ncs/projects/peripheral_uart/build/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/ncs/projects/peripheral_uart/build/zephyr/dts.cmake
Parsing C:/ncs/projects/peripheral_uart/Kconfig
Loaded configuration 'C:/ncs/projects/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840_defconfig'
Merged configuration 'C:/ncs/projects/peripheral_uart/prj.conf'
No change to configuration in 'C:/ncs/projects/peripheral_uart/build/zephyr/.config'
No change to Kconfig header in 'C:/ncs/projects/peripheral_uart/build/zephyr/include/generated/autoconf.h'
CMake Warning at C:\ncs\projects\zephyr\CMakeLists.txt:1612 (message):
__ASSERT() statements are globally ENABLED

-- Configuring done
-- Generating done
-- Build files have been written to: C:/ncs/projects/peripheral_uart/build
[1/173] Generating misc/generated/syscalls.json, misc/generated/struct_tags.json
[2/173] Building C object zephyr/CMakeFiles/offsets.dir/arch/arm/core/offsets/offsets.c.obj
[3/173] Generating include/generated/offsets.h
[4/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/sem.c.obj
[5/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/notify.c.obj
[6/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/fdtable.c.obj
[7/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/printk.c.obj
[8/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/bitarray.c.obj
[9/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/rb.c.obj
[10/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/onoff.c.obj
[11/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/heap.c.obj
[12/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/heap-validate.c.obj
[13/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/assert.c.obj
[14/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/thread_entry.c.obj
[15/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/reboot.c.obj
[16/173] Building C object CMakeFiles/app.dir/src/main.c.obj
[17/173] Building C object zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/validate_enabled_instances.c.obj
[18/173] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/mpsc_pbuf.c.obj
[19/173] Building C object zephyr/CMakeFiles/zephyr.dir/soc/arm/nordic_nrf/validate_base_addresses.c.obj
[20/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/logging/log_msg.c.obj
[21/173] Linking C static library app\libapp.a
[22/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/logging/log_output.c.obj
[23/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/logging/log_core.c.obj
[24/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/storage/flash_map/flash_map.c.obj
[25/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/logging/log_backend_rtt.c.obj
[26/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/settings/src/settings_init.c.obj
[27/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/storage/flash_map/flash_map_default.c.obj
[28/173] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/isr_wrapper.S.obj
[29/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/settings/src/settings.c.obj
[30/173] Building ASM object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/exc_exit.S.obj
[31/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/settings/src/settings_nvs.c.obj
[32/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/settings/src/settings_store.c.obj
[33/173] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/prep_c.c.obj
[34/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/pm/power.c.obj
[35/173] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/nmi.c.obj
[36/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/fs/nvs/nvs.c.obj
[37/173] Building ASM object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/reset.S.obj
[38/173] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/fatal.c.obj
[39/173] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/fpu.c.obj
[40/173] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/irq_init.c.obj
[41/173] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/scb.c.obj
[42/173] Building C object zephyr/arch/arch/arm/core/aarch32/mpu/CMakeFiles/arch__arm__core__aarch32__mpu.dir/arm_core_mpu.c.obj
[43/173] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/abort.c.obj
[44/173] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/thread_abort.c.obj
[45/173] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/exit.c.obj
[46/173] Building C object zephyr/arch/arch/arm/core/aarch32/mpu/CMakeFiles/arch__arm__core__aarch32__mpu.dir/arm_mpu.c.obj
[47/173] Building C object zephyr/arch/arch/arm/core/aarch32/cortex_m/CMakeFiles/arch__arm__core__aarch32__cortex_m.dir/fault.c.obj
[48/173] Building C object zephyr/soc/arm/common/cortex_m/CMakeFiles/soc__arm__common__cortex_m.dir/arm_mpu_regions.c.obj
[49/173] Building C object zephyr/lib/libc/minimal/CMakeFiles/lib__libc__minimal.dir/source/stdlib/malloc.c.obj
[50/173] Building C object zephyr/lib/posix/CMakeFiles/lib__posix.dir/pthread_common.c.obj
[51/173] Linking C static library zephyr\arch\arch\arm\core\aarch32\mpu\libarch__arm__core__aarch32__mpu.a
[52/173] Building C object zephyr/lib/posix/CMakeFiles/lib__posix.dir/nanosleep.c.obj
[53/173] Linking C static library zephyr\soc\arm\common\cortex_m\libsoc__arm__common__cortex_m.a
[54/173] Linking C static library zephyr\arch\arch\arm\core\aarch32\cortex_m\libarch__arm__core__aarch32__cortex_m.a
[55/173] Linking C static library zephyr\lib\libc\minimal\liblib__libc__minimal.a
[56/173] Building C object zephyr/subsys/bluetooth/common/CMakeFiles/subsys__bluetooth__common.dir/dummy.c.obj
[57/173] Linking C static library zephyr\lib\posix\liblib__posix.a
[58/173] Building C object zephyr/soc/arm/nordic_nrf/nrf52/CMakeFiles/soc__arm__nordic_nrf__nrf52.dir/power.c.obj
[59/173] Building C object zephyr/soc/arm/nordic_nrf/nrf52/CMakeFiles/soc__arm__nordic_nrf__nrf52.dir/soc.c.obj
[60/173] Linking C static library zephyr\soc\arm\nordic_nrf\nrf52\libsoc__arm__nordic_nrf__nrf52.a
[61/173] Building C object zephyr/subsys/bluetooth/common/CMakeFiles/subsys__bluetooth__common.dir/log.c.obj
[62/173] Building C object zephyr/subsys/bluetooth/common/CMakeFiles/subsys__bluetooth__common.dir/rpa.c.obj
[63/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/settings.c.obj
[64/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/hci_common.c.obj
[65/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/buf.c.obj
[66/173] Linking C static library zephyr\subsys\bluetooth\common\libsubsys__bluetooth__common.a
[67/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/hci_ecc.c.obj
[68/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/ecc.c.obj
[69/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/adv.c.obj
[70/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/l2cap.c.obj
[71/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/keys.c.obj
[72/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/id.c.obj
[73/173] Building ASM object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/swap_helper.S.obj
[74/173] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/swap.c.obj
[75/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/conn.c.obj
[76/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/att.c.obj
[77/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/hci_core.c.obj
[78/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/gatt.c.obj
[79/173] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/irq_manage.c.obj
[80/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/tracing/tracing_none.c.obj
[81/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/pm/policy/policy_residency.c.obj
[82/173] Building C object zephyr/CMakeFiles/zephyr.dir/subsys/pm/pm_ctrl.c.obj
[83/173] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/timer/sys_clock_init.c.obj
[84/173] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/timer/nrf_rtc_timer.c.obj
[85/173] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/clock_control/clock_control_nrf.c.obj
[86/173] Generating linker_zephyr_prebuilt.cmd
[87/173] Building C object zephyr/arch/common/CMakeFiles/arch__common.dir/sw_isr_common.c.obj
[88/173] Building C object zephyr/arch/common/CMakeFiles/isr_tables.dir/isr_tables.c.obj
[89/173] Building C object zephyr/arch/arch/arm/core/aarch32/CMakeFiles/arch__arm__core__aarch32.dir/thread.c.obj
[90/173] Building C object zephyr/CMakeFiles/zephyr.dir/drivers/console/uart_console.c.obj
[91/173] Building C object zephyr/CMakeFiles/zephyr.dir/C_/ncs/projects/nrfxlib/crypto/nrf_cc310_platform/src/nrf_cc3xx_platform_abort_zephyr.c.obj
[92/173] Building C object zephyr/CMakeFiles/zephyr.dir/C_/ncs/projects/nrfxlib/crypto/nrf_cc310_platform/src/nrf_cc3xx_platform_mutex_zephyr.c.obj
[93/173] Building C object zephyr/CMakeFiles/zephyr.dir/C_/ncs/projects/nrf/subsys/bluetooth/services/nus.c.obj
[94/173] Linking C static library zephyr\arch\common\libisr_tables.a
[95/173] Linking C static library zephyr\arch\arch\arm\core\aarch32\libarch__arm__core__aarch32.a
[96/173] Building C object zephyr/subsys/random/CMakeFiles/subsys__random.dir/rand32_entropy_device.c.obj
[97/173] Linking C static library zephyr\arch\common\libarch__common.a
[98/173] Linking C static library zephyr\subsys\random\libsubsys__random.a
[99/173] Building C object zephyr/subsys/bluetooth/host/CMakeFiles/subsys__bluetooth__host.dir/smp.c.obj
[100/173] Building C object zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/flash_page_layout.c.obj
[101/173] Linking C static library zephyr\libzephyr.a
[102/173] Building C object zephyr/drivers/gpio/CMakeFiles/drivers__gpio.dir/gpio_nrfx.c.obj
[103/173] Building C object zephyr/subsys/net/CMakeFiles/subsys__net.dir/buf.c.obj
[104/173] Linking C static library zephyr\subsys\bluetooth\host\libsubsys__bluetooth__host.a
[105/173] Building C object zephyr/drivers/flash/CMakeFiles/drivers__flash.dir/soc_flash_nrf.c.obj
[106/173] Building C object zephyr/drivers/entropy/CMakeFiles/drivers__entropy.dir/C_/ncs/projects/nrf/drivers/entropy/entropy_cc310.c.obj
[107/173] Linking C static library zephyr\drivers\gpio\libdrivers__gpio.a
[108/173] Linking C static library zephyr\subsys\net\libsubsys__net.a
[109/173] Linking C static library zephyr\drivers\flash\libdrivers__flash.a
[110/173] Building C object zephyr/drivers/entropy/CMakeFiles/drivers__entropy.dir/entropy_nrf5.c.obj
[111/173] Building C object modules/nrf/lib/multithreading_lock/CMakeFiles/..__nrf__lib__multithreading_lock.dir/multithreading_lock.c.obj
[112/173] Building C object zephyr/drivers/serial/CMakeFiles/drivers__serial.dir/uart_nrfx_uarte.c.obj
[113/173] Linking C static library zephyr\drivers\entropy\libdrivers__entropy.a
[114/173] Building C object modules/nrf/lib/fatal_error/CMakeFiles/..__nrf__lib__fatal_error.dir/fatal_error.c.obj
[115/173] Linking C static library modules\nrf\lib\multithreading_lock\lib..__nrf__lib__multithreading_lock.a
[116/173] Linking C static library zephyr\drivers\serial\libdrivers__serial.a
[117/173] Linking C static library modules\nrf\lib\fatal_error\lib..__nrf__lib__fatal_error.a
[118/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/banner.c.obj
[119/173] Building C object modules/nrf/lib/dk_buttons_and_leds/CMakeFiles/..__nrf__lib__dk_buttons_and_leds.dir/dk_buttons_and_leds.c.obj
[120/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/device.c.obj
[121/173] Building C object modules/nrf/subsys/bluetooth/controller/CMakeFiles/..__nrf__subsys__bluetooth__controller.dir/hci_internal.c.obj
[122/173] Building C object modules/nrf/subsys/bluetooth/controller/CMakeFiles/..__nrf__subsys__bluetooth__controller.dir/crypto.c.obj
[123/173] Linking C static library modules\nrf\lib\dk_buttons_and_leds\lib..__nrf__lib__dk_buttons_and_leds.a
[124/173] Building C object modules/nrf/drivers/mpsl/clock_control/CMakeFiles/..__nrf__drivers__mpsl__clock_control.dir/nrfx_clock_mpsl.c.obj
[125/173] Building C object modules/nrf/subsys/mpsl/init/CMakeFiles/..__nrf__subsys__mpsl__init.dir/mpsl_init.c.obj
[126/173] Linking C static library modules\nrf\drivers\mpsl\clock_control\lib..__nrf__drivers__mpsl__clock_control.a
[127/173] Building C object modules/nrf/subsys/bluetooth/controller/CMakeFiles/..__nrf__subsys__bluetooth__controller.dir/hci_driver.c.obj
[128/173] Building C object modules/nrf/drivers/mpsl/flash_sync/CMakeFiles/..__nrf__drivers__mpsl__flash_sync.dir/flash_sync_mpsl.c.obj
[129/173] Linking C static library modules\nrf\subsys\mpsl\init\lib..__nrf__subsys__mpsl__init.a
[130/173] Building C object modules/nrf/drivers/hw_cc310/CMakeFiles/..__nrf__drivers__hw_cc310.dir/hw_cc310.c.obj
[131/173] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/nrfx_glue.c.obj
[132/173] Linking C static library modules\nrf\subsys\bluetooth\controller\lib..__nrf__subsys__bluetooth__controller.a
[133/173] Linking C static library modules\nrf\drivers\hw_cc310\lib..__nrf__drivers__hw_cc310.a
[134/173] Linking C static library modules\nrf\drivers\mpsl\flash_sync\lib..__nrf__drivers__mpsl__flash_sync.a
[135/173] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/ncs/projects/modules/hal/nordic/nrfx/drivers/src/nrfx_nvmc.c.obj
[136/173] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/ncs/projects/modules/hal/nordic/nrfx/drivers/src/nrfx_ppi.c.obj
[137/173] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/ncs/projects/modules/hal/nordic/nrfx/drivers/src/nrfx_uarte.c.obj
[138/173] Building C object modules/segger/CMakeFiles/modules__segger.dir/SEGGER_RTT_zephyr.c.obj
[139/173] Building C object modules/hal_nordic/nrfx/CMakeFiles/modules__hal_nordic__nrfx.dir/C_/ncs/projects/modules/hal/nordic/nrfx/drivers/src/nrfx_gpiote.c.obj
[140/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/kheap.c.obj
[141/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mem_slab.c.obj
[142/173] Building C object modules/segger/CMakeFiles/modules__segger.dir/C_/ncs/projects/modules/debug/segger/SEGGER/SEGGER_RTT.c.obj
[143/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/fatal.c.obj
[144/173] Linking C static library modules\hal_nordic\nrfx\libmodules__hal_nordic__nrfx.a
[145/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/init.c.obj
[146/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/thread.c.obj
[147/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/errno.c.obj
[148/173] Linking C static library modules\segger\libmodules__segger.a
[149/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/msg_q.c.obj
[150/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/idle.c.obj
[151/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mailbox.c.obj
[152/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/system_work_q.c.obj
[153/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/condvar.c.obj
[154/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/pipes.c.obj
[155/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/queue.c.obj
[156/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/stack.c.obj
[157/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/xip.c.obj
[158/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sem.c.obj
[159/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mutex.c.obj
[160/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timer.c.obj
[161/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/poll.c.obj
[162/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/work.c.obj
[163/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/mempool.c.obj
[164/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/timeout.c.obj
[165/173] Building C object zephyr/kernel/CMakeFiles/kernel.dir/sched.c.obj
[166/173] Linking C static library zephyr\kernel\libkernel.a
[167/173] Linking C executable zephyr\zephyr_prebuilt.elf

[168/173] Generating linker.cmd
[169/173] Generating isr_tables.c, isrList.bin
[170/173] Generating dev_handles.c
[171/173] Building C object zephyr/CMakeFiles/zephyr_final.dir/isr_tables.c.obj
[172/173] Building C object zephyr/CMakeFiles/zephyr_final.dir/dev_handles.c.obj
[173/173] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 206908 B 1 MB 19.73%
SRAM: 38945 B 256 KB 14.86%
IDT_LIST: 0 GB 2 KB 0.00%

Le terminal sera réutilisé par les tâches, appuyez sur une touche pour le fermer.

> Executing task: nRF Connect: Build peripheral_uart/build (active) <

Building peripheral_uart
west build --build-dir c:\ncs\projects\peripheral_uart\build c:\ncs\projects\peripheral_uart

ninja: no work to do.

Le terminal sera réutilisé par les tâches, appuyez sur une touche pour le fermer.

> Executing task: nRF Connect: Flash peripheral_uart/build (active) <

Flashing build to undefined
west flash -d c:\ncs\projects\peripheral_uart\build --skip-rebuild -r nrfjprog --snr 683372301

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\ncs\projects\peripheral_uart\build\zephyr\zephyr.hex
Parsing image file.
ERROR: The file specified is not a valid hex file, has data outside valid areas
ERROR: or does not have data in valid areas.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 52: nrfjprog --program 'c:\ncs\projects\peripheral_uart\build\zephyr\zephyr.hex' --sectoranduicrerase -f NRF52 --snr 683372301
Arrêt du processus de terminal. Code de sortie : 52.

Le terminal sera réutilisé par les tâches, appuyez sur une touche pour le fermer.

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 08:36:25 GMT

maybe i have to change parameter?

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 08:35:51 GMT

i added this, i have to same errors than before during the flash,

i can flash the application blinky, so i dont understand why "periphral uart" doesnt working.... :(

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

Priyanka — Wed, 22 Dec 2021 08:24:00 GMT

Hi,

Could you try adding CONFIG_CPLUSPLUS=y in your prj.conf file and then run the application again?

-Priyanka

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 07:58:40 GMT

and in output i have nothing.

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 07:58:24 GMT

In problems, i have this

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Wed, 22 Dec 2021 07:58:03 GMT

i tried by clicking on the right to connect to my nrf terminal but i can't, because :

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

Priyanka — Tue, 21 Dec 2021 16:50:59 GMT

Hi,

Could you run again and this time, share the log that occurs in "Problems" , "Output" and "NRF Terminal" window in VSCode?

-Priyanka

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Tue, 21 Dec 2021 15:29:18 GMT

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Tue, 21 Dec 2021 13:59:05 GMT

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Tue, 21 Dec 2021 13:58:16 GMT

RE: ERROR: The file specified is not a valid hex file, has data outside valid areas

lm — Tue, 21 Dec 2021 13:56:08 GMT

i have this :)