Open CombatCables opened 4 years ago
There's also a chance it's 0x60060306 and 0x60060305, as seen in issue #24 and #32
There's also a chance it's 0x60060306 and 0x60060305, as seen in issue #24 and #32
Alright I added the other Chip IDs as well. It should work with all boards mentioned. Just need Drop to submit the update for qmk_toolbox to get updated
https://github.com/Massdrop/mdloader/blob/fcef3c437e1c283ea6009435399ebfb2004b4c31/mdloader_common.c#L38
Further documentation can be found here to ultimately future proof this problem: http://ww1.microchip.com/downloads/en/DeviceDoc/SAM-D5x-E5x-Family-Silicon-Errata-DS80000748K.pdf