9 months, 3 weeks ago.
Generating just the Application HEX file during compilation.
When I compile via the online compiler or the offline compiler the resulting hex file contains both the soft device + Application. Is there a way to generate the resulting hex file to contain only the application in the offline compilation mode.
Question relating to:
9 months, 2 weeks ago.
The hex file for the application (minus the softdevice) needs to be built so the combined image can be constructed. If you examine the output of the CLI (here we are using the BLE LED example), you will see the the file you are looking for is "mbed-os-example-ble-LED_application.hex" (located under \BUILD\nrf52_dk\gcc_arm):
$ mbed compile -m nrf52_dk -t gcc_arm Building project mbed-os-example-ble-LED (NRF52_DK, GCC_ARM) Scan: . Scan: env Scan: mbed Scan: FEATURE_BLE Using regions bootloader, application in this build. Region bootloader: size 0x23000, offset 0x0 Region application: size 0x5d000, offset 0x23000 Merging Regions Filling region bootloader with C:\Users\xyz\_work\mbed-os-example-ble-LED\mbed-os\targets\TARGET_NORDIC\TARGET_NRF5x\TARGET_SDK_14_2\TARGET_SOFTDEVICE_S132_FULL\hex/s132_nrf52_5.0.0_softdevice.hex Padding region bootloader with 0xb58 bytes Filling region application with .\BUILD\nrf52_dk\gcc_arm\mbed-os-example-ble-LED_application.hex
The combined image is called "mbed-os-example-ble-LED.hex".
To post an answer, please log in.