When attempting to flash a recently purchased second hand board i recieve the error:
>>> dfu-programmer.exe atmega32u4 erase --force
Erasing flash... Success
Checking memory from 0x0 to 0x6FFF... Not blank at 0x1.
>>> dfu-programmer.exe atmega32u4 flash "C:\Users\username\Downloads\qmk60.hex"
Checking memory from 0x0 to 0x607F... Not blank at 0x1.
The target memory for the program is not blank.
Use --force flag to override this error check.
>>> dfu-programmer.exe` atmega32u4 reset
I have tried everything i can think of so any help would be greatly appreciated...
Retry, that fixes the issue in a lot of cases.
That doesn't fix the issue, YMDK96 NOT clearing memory on reset in order to flash the QMK hex file.
Hi guys,
Same here. Using latest QMK Toolbox and drivers now but I get the same message when attempting to re-flash my Melody96. Any help/pointer to a solution would be great.
also experiencing this issue, retrying just repeats the errors.
also experiencing this error
Had this issue before, easiest solution was to just force a firmware over with a ISP flasher. After that normal flashing methods worked fine.
Had this issue before, easiest solution was to just force a firmware over with a ISP flasher. After that normal flashing methods worked fine.
Hi, germ. Thanks for the response. I saw this solution a while back in the QMK docs (https://beta.docs.qmk.fm/using-qmk/guides/keyboard-building/isp_flashing_guide) when I was searching around, but this solution requires having another micro-controller and knowledge in soldering (which I don't possess which is why I typically opt for hotswappable boards.
Are you also suggesting perhaps there's no way around forcing it? I was thinking maybe I could attempt force flashing via mingw64, instead of QMK Toolbox, just looking for time to update my copy of qmk. Would this be worth it/a potential alternative to ISP flashing?
If not, it sounds cheaper to just buy a new PCB (and pray it doesn't get screwed up again), instead of investing in a micro-controller and soldering tools. (very short term, but I don't see myself buying higher-end boards in the near future with the economy here in the Philippines)
Correct, if you have an Arduino handy it shouldn't be too bad. Check if you have a HackerSpace nearby or anyone you know that would be able to flash it for you! An alternative solution is to hot-air the 32u4 off and slap a fresh replacement on. That's actually my go-to these days instead of breaking out a ISP flasher when that happens.
I don't think that using Mingw instead of toolbox will make much of a difference. But once you get it flashed, you should be able to flash it normally!
Darn, was really hoping a software-only solution would work. But I understand why it wouldn't make much of any difference since they both work off the same stuff.
I appreciate the response and I guess I'd better get to soldering, sourcing, and or flat out buying a new PCB (whichever is most accessible).
@germ so I'm considering the hot-air and replace solution but since I've never done that before could you clarify these for me:
Apologies if I sound too much like a noob, and based on the line of questioning I think it's more likely I might just buy a new PCB altogether (especially if a regular hair dryer won't work which means procuring a heat gun AND a new mcu which might collectively be more expensive and riskier from my POV).
It's riskier, but more fun. Might be worth posting on mechmarket to see if anyone in your country can do ISP flashing for you. Might be the cheapest overall
@germ hey man!
So I couldn't find a heat gun, and my local mechboard community in the PH talked me into ISP Flashing instead. Long story short it worked like a charm.
Essentially bought a Pro Micro, a multi-tester to trace where the breakout pins connect to my MCU, and soldering equipment, and followed the steps in the QMK ISP Flashing Guide as carefully as I could.
@CormickTreacy @Magascorada @tomwang2011 hey guys I think this actually works. Maybe list this as solved if you try it out yourself? :D
Good to hear! At least now you know what to do next time you see something like this :)