Re: question on mpy-cross
Posted: Fri May 03, 2019 11:14 pm
Yes, a uf2 file is just instructions to the bootloader with chunks of data and destination addresses. Like a .hex file but binary. There are tools for generating this.
The main thing (and this is not complicated, just a matter of reading and figuring it out) is to make sure the firmware image you build has the right memory layout (i.e. leaving enough room for their bootloader etc).
For an example of this (layout changing for different bootloader config), look at how the USE_MBOOT flag in main MicroPython works by selecting a different linker script.
Looks like the meowbit is quite new, maybe they just haven't gotten around to releasing their repo yet. Might be worth emailing them directly?
The main thing (and this is not complicated, just a matter of reading and figuring it out) is to make sure the firmware image you build has the right memory layout (i.e. leaving enough room for their bootloader etc).
For an example of this (layout changing for different bootloader config), look at how the USE_MBOOT flag in main MicroPython works by selecting a different linker script.
Looks like the meowbit is quite new, maybe they just haven't gotten around to releasing their repo yet. Might be worth emailing them directly?