tockloader/board_interface: add flash-file support for stm32f4 - #146
lschuermann wants to merge 1 commit into
Conversation
|
I think this is what tockloader/tockloader/tockloader.py Lines 139 to 142 in bcc70c3 |
|
Hm, good point. Installing apps still didn't work, so I think there's still a bug. But flash-file support can co-exist with direct flash access through a debugger anyways, right? |
|
Yes, but while the flash-file support is convenient when needed, I'm hesitant to lean into it. It's a much more old school approach. Everything can be done via command-line arguments for use cases that need it, but I don't want to converge on every board kind of supports both direct access and a shadow copy and which is getting used becomes confusing. |
|
I disagree. I think the flash file support has legitimate use-cases even when proper direct access is supported and working, e.g. to pre-build an image that is flashed to devices (which appears to be a common use-case among the current production users of Tock). |
This is useful because Tockloader can't install apps on these boards directly, given the erase-unit for flash pages on the STM32F is non-uniform and not equal to the flash page size.