Getting started with Mbed OS on MAX32630 #1218
Replies: 2 comments 4 replies
-
Hi @TijnLosekoot, Even though the MCUboot port casts the If I get the time, I will see if I can get a build working for the MAX chip soon. I will not adjust the other parameters (memory addresses, etc) to make it functional, but it shouldn't be too hard to get it building at least. You seem to be doing everything correct, so it could be something simple breaking your build. |
Beta Was this translation helpful? Give feedback.
-
Okay, I think the problem is this: Unfortunately, the MAX32630 does not have support for internal flash reprogramming via Mbed's APIs. This is to say: the MAX32630 target does not have the following in it's
This API support is required when using the I quickly adapted the similar MAX32660 flash driver implementation and got rid of most of the errors. You can check out my branch of mbed-os here: https://github.com/AGlass0fMilk/mbed-os/tree/max32630-flash-support You will need to check out my latest patch to MCUboot: https://github.com/AGlass0fMilk/mcuboot/tree/boot-record-add-stddef Also check out how I modified the There is still a problem though: the build compiles fine but fails at the linker stage whenever
It seems that the first section is the actual code being generated for the bootloader (~50kB). I'm not sure what the second section is. It is over 500kB. I have also not tested the flash API implementation (I don't have this target) so you may encounter issues there. I just used the Maxim HAL API for reprogramming flash, based on the implementation for the MAX32660 target. At this point, I don't have time to further debug this so I would check with Maxim support to see why this section of flash is always being output by the linker script. This gets you very close I think. I hope it helps. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I've been trying to get a bootloader working with Mbed OS on our MAX32630 MCU for quite a while now. We do not use the FTHR board but rather a custom PCB.
I've tried to follow @AGlass0fMilk 's demo for MCUboot but I can't get very far because he uses another board that apparently does support the FlashIAPBlockDevice class. For testing purposes I made a new, completely empty, project in Mbed OS, and made the following mbed_app.json configuration (it's pretty much a copy-paste of Glass0fMilk's work):
This throws up an error at the end of compilation, stating that the file doesn't exist when
flash_map_backend.cpp
attempts to include it.I've then tried adding this to my mbed_app.json:
but sadly this doesn't fix it.
So then I attempted to add the whole path like so:
#include "COMPONENT_FLASHIAP/include/FlashIAP/FlashIAPBlockDevice.h"
inflash_map_backend.cpp
.Now the following error comes up and it's got me really stumped:
What I'd really like to know is, is there a way to just not use the FlashIAPBlockDevice class at all? After all, it inherits from BlockDevice and the
flash_map_backend.cpp
file just always casts it back to the BlockDevice class.Beta Was this translation helpful? Give feedback.
All reactions