I was tinkering with my QT PY M0 and I seem to have busted the bootloader. I now can't see the device when I connect it to my PC or double press the reset button to enter the bootloader. I see on the back there are SWCLK and SWDIO pads that are used for programming, but I don't see much on how this is actually done or a .BIN file you could use for suck programming.
I don't mind if I would need to purchase something to get this to work, but I'd prefer not to spend much as a new board would cost very little. I also have other Raspberry Picos, arduinos and a raspberry pi laying around if there are any projects that could help fix this QT PY M0.
Busted bootloader on QT PY M0, where to now?
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- ShakeNBlake12
- Posts: 3
- Joined: Mon Dec 26, 2022 7:58 pm
- mikeysklar
- Posts: 13936
- Joined: Mon Aug 01, 2016 8:10 pm
Re: Busted bootloader on QT PY M0, where to now?
Does the Qt Py M0 show up as connected on from your OS device manager? I understand that the mounted boot drives are not appearing.
Our guides document how to use a JTAG programmer to restore these devices through the SWDIO / SWCLK pins. When they are obtainable they can be reasonably priced at $20.
https://www.adafruit.com/product/3571
https://learn.adafruit.com/how-to-progr ... ootloaders
Since you have some Raspberry Pi's you can also program through the JTAG pins on the Qt Py M0. This is a more advanced process, but a good learning experience if nothing else.
https://learn.adafruit.com/programming- ... spberry-pi
There is also a way to load bootloaders from one M0 to another, but I've not found a good guide for that. I mention it only to encourage you to seek out a third option if necessary.
Our guides document how to use a JTAG programmer to restore these devices through the SWDIO / SWCLK pins. When they are obtainable they can be reasonably priced at $20.
https://www.adafruit.com/product/3571
https://learn.adafruit.com/how-to-progr ... ootloaders
Since you have some Raspberry Pi's you can also program through the JTAG pins on the Qt Py M0. This is a more advanced process, but a good learning experience if nothing else.
https://learn.adafruit.com/programming- ... spberry-pi
There is also a way to load bootloaders from one M0 to another, but I've not found a good guide for that. I mention it only to encourage you to seek out a third option if necessary.
- ShakeNBlake12
- Posts: 3
- Joined: Mon Dec 26, 2022 7:58 pm
Re: Busted bootloader on QT PY M0, where to now?
Unfortunately I don't see the device in the device manager, and pressing the reset button seems not to change anything.mikeysklar wrote: ↑Tue Dec 27, 2022 10:57 am Does the Qt Py M0 show up as connected on from your OS device manager? I understand that the mounted boot drives are not appearing.
Our guides document how to use a JTAG programmer to restore these devices through the SWDIO / SWCLK pins. When they are obtainable they can be reasonably priced at $20.
https://www.adafruit.com/product/3571
https://learn.adafruit.com/how-to-progr ... ootloaders
Since you have some Raspberry Pi's you can also program through the JTAG pins on the Qt Py M0. This is a more advanced process, but a good learning experience if nothing else.
https://learn.adafruit.com/programming- ... spberry-pi
There is also a way to load bootloaders from one M0 to another, but I've not found a good guide for that. I mention it only to encourage you to seek out a third option if necessary.
I've spend a night or two messing with the raspberrypi and OpenOCD and I think I was making some progress as I could detect the SAMD21, but it seems programming wasn't going as expected. Since I cant tell if it's actually my SAMD or the Pi that is my issue, I managed to borrow an MPlab PICKit4. I'm still working on getting this working, but I now can't seem to detect the chip at all when using this. I'm not entirely sure what could be causing this issue.
- ShakeNBlake12
- Posts: 3
- Joined: Mon Dec 26, 2022 7:58 pm
Re: Busted bootloader on QT PY M0, where to now?
Consider this case closed. I managed to get my QTPY back after checking and re-checking the connections only to find I had the CLK and DIO pins backwards, causing the chip to not be detected. I'll be continuing with the PI4 debugging now that I know my board is good... Until I can finally get one of those J-Link EDU devices in hand.
Please be positive and constructive with your questions and comments.