Closed hathach closed 4 years ago
@hathach -- See WIP PR #152.
It appears that allowing multiple family IDs, and basing the second allowed family ID on the USB VID/PID, may be relatively easy.
The above PR is still a WIP, mostly because I've not tested the bootloader (and am unsure if I can do so in any reasonable fashion). However, I created the PR to show that it might be a simple change.
@hathach -- See WIP PR #152.
It appears that allowing multiple family IDs, and basing the second allowed family ID on the USB VID/PID, may be relatively easy.
The above PR is still a WIP, mostly because I've not tested the bootloader (and am unsure if I can do so in any reasonable fashion). However, I created the PR to show that it might be a simple change.
Thanks, It is much simpler than I thought. Was switched to other task by now :)
Is your feature request related to a problem? Please describe.
together with #129, accepting additional family as board specific (VID/PID) allow us to bundle multiple firmware of different boards into a single big uf2 (e.g a circuitpyhon uf2 file for all nRF52 boards ). Following is the original discussion
_Originally posted by @mmoskal in https://github.com/adafruit/Adafruit_nRF52_Bootloader/pull/128_
Describe the solution you'd like Bootloader accept family ID =
ada52840
as generic nrf binary and also family id = vid+pid as board specific one.Describe alternatives you've considered Application can also use pinconfig in CF2 of bootloader to write generic binary for all boards.