(VERY VERY WIP) mcuboot Support #70
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now the process for getting mcuboot to build is very fragile, that will be addressed later once I can actually figure out how to even get it properly working.
The zephyr submodule was bumped to the specific commit that merged support for the RP2350 flash controller (zephyrproject-rtos/zephyr#89182), and the following diffs will need to be applied to mcuboot (lib/zephyr-workspace/bootloader/mcuboot):
You will then also need a python venv for some build requirements, I just made a venv and installed zephyr's requirements.txt and that worked (from what I remember).
This is the build command I used (paths will need to be changed for your machine)
west build -c -b proves_flight_control_board_v5c/rp2350a/m33 /Users/aychar/code/lib/zephyr-workspace/bootloader/mcuboot/boot/zephyr -- -DBOARD_ROOT=/Users/aychar/code/proves-core-reference, and as well I had to specifically run it while inside of proves-core-reference, otherwise I'd get errors about pem keys(??).boards/bronco_space/proves_flight_control_board_v5c/Kconfig.proves_flight_control_board_v5c will also need to be changed to your specific path for proves-core-reference for now, the relative path was not working for me when trying to build mcuboot with the board definition still being in proves-core-reference.
The current state this is in right now, I'm able to build the uf2 for mcuboot and put it on a v5c board, and as well the serial connection does show up in /dev. However, whenever I try to use mcumgr(will probably also want to install this) to flash proves-core-reference to the first partition, nothing happens. I think that the board may be crashing, or possibly could be an issue with how I set up the serial, because the
mcumgr echocommand also returns nothing from the board.