Skip to content

Bootloader compilation and location #508

@rylox

Description

@rylox

I'm trying to implement this fix but I'm having some issues. Where is the script generated bootloader file copied to? I'm running it on debian and it prints out:
Setting up Mbed Application...[mbed] Working path "/tmp/mbed-os-program" (program)
[mbed] ARDUINO_NANO33BLE now set as default target in program "mbed-os-program"
[mbed] Working path "/tmp/mbed-os-program" (program)
[mbed] GCC_ARM now set as default toolchain in program "mbed-os-program"
done.
Switching to /tmp/mbed-os-program/BUILD/ARDUINO_NANO33BLE/GCC_ARM/ I have 3 flashable files mbed-os-program.hex, mbed-os-program_application.hex and mbed-os-program_update.bin none of which work. The mc won't get recognised after flashing them. The script finished successfully without any errors. I also tested all files in DFU mode.

Cheers
Leon

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions