There are some important things to know about VIA and the F77
There are two main ways with stock VIA to get it to ignore a key map stored in EEPROM
1. Use Bootmagic lite to reset the keyboard, VIA enabled firmware will then ignore the currently stored keymap
2. flash the KB with a version of VIA firmware that was compiled on a different day (VIA compares the FW date with a value stored in EEPROM)
The issue with the F77 is that you can't use bootmagic because the keyboard calibration routine that runs on powerup will mean that a held key is not detected when the control gets to the bootmagic routine.
So if you are using VIA on the F77, and the keymap becomes corrupt in some way (and e.g. causes the FW to crash), then your recovery choice is to compile a new version of VIA and flash it in yourself. Flashing in a regular QMK build *will not* clear the EEPROM, when you go back to your VIA FW the same key map will still be there. Non QMK FW may or may not fix it depending on whether it actually changes the EEPROM.
pandrew has a utility that in theory can clear the EEPROM, but it uses the same communication channel as VIA, so to use it will likely have to flash in a non VIA FW to make it work.
It is unknown how much of problem not being able to clear the EEPROM is. I have had no issues with any of my VIA enabled keyboards to date, so possibly this is a non issue, but the VIA folk thought it was important enough to enforce Bootmagic lite in VIA builds.
My take, use it, by just be warned you may have to muck around a bit more to recover a messed up keymap
Sorry for my late response:Tarmac wrote: ↑28 Apr 2021, 03:27Hi,
I have just received a new Model F62 and thought I'd give this firmware upload a try but a few things are not clear to me - sorry for the newcomer questions.
I downloaded "QMK Toolbox", "VIA" and "Firmware for VIA" from the links on www.modelfkeyboards.com/manual and I also see the layout files from "https://www.bucklingspring.com/via-firmware-and-layout/" for the F62 - the "all keys" one.
1. The PDF readme instructions mention that; If Fn+Space+R works then I already have QMK installed - this indeed worked on my F62. So first question, if this is the case do I still have to Erase the
firmware or can I just go ahead and flash one of the Layout .hex VIA specific firmware files. The action to be taken is not clear to me?
2. In the Layout zip file are some 46 layout files, clearly I should choose one of the F62. However, I have a HHKB - split right shift + spit backspace. There don't appear to be any that match this? Also there appear to be three types; (i) F**, (ii) Via F** and (iii) zF**, I guess Via is for Via but what are the other 2 types for?
3. Lastly, given that I already have firmware on my F62 why do I need to flash anyway? Shouldn't VIA just be able to detect my keyboard so I can make key assignments - again this is not clear? I have
tried it and VIA just reports " searching for devices ..", clearly my mental model of the process is not right ...
Thank you in advance for any insights you can give me ....
Code: Select all
% Define which version should be produced Digital or Print
% Options in the typesetting docs are:
% \processifversion{Print}{Hello Print Version!}
% or
% \processifversion{Digital}{Hello Digital Version!}
\excludeversion{Print}
\includeversion{Digital}
I hope to be less occupied soon and spend more time on things. Actually I am working on several updates at this very moment...
I am in the process to move the site to a different cloud space. Unfortunately, I had to stop in the middle for a week or so. I have uploaded the actual version to this temporary link for now: http://195.90.200.37/ModelFManual.pdf
I totally will - it is released under OpenSource anyway. I am also going to release a github-link of the full LaTeX document in the end. I wish I could move forward faster, but as everybody knows ... life has the tendency to distract you at times.
