Atmega32AU I believe? I'll send that guy a message. I don't know how to use flip.
Pancake, have you tried any of this?
@Pancake: Try this please.
- Disconnect your Exent if connected
- Open EK switch hitter or some kind of program like that to identify keypresses
- Connect your Exent and see if switch hitter receives ESC, TAB, Block Mayus, Left Shift, etc
- Write that down and give us the results. Then open Bootmapper client, last version
- Go here ( https://meckeyalpha.com/pages/guide-on-bootmapper-client#remap ) and follow the steps in Bootmapper Mode.
- When hitting the keys while in bootmapper mode, see if the ESC, TAB, etc keys register properly (as in highlighting the correct position) or do anything else. Compare it with the other keys and post results. Screen caps if possible
- Upload a new layout, even if it's just random rubbish
- Make sure to uncheck the togge bootmapper mode after uploading it
- Disconnect the board and repeat the first 4 steps
You can also try to change ESC, TAB, etc. keys to just letters and open a notepad before connecting the board to see if it sends the keycodes when plugged in. I remember that happened to me once, but a reflash solved that.
Reading your last messages, it kind of seems you are shorting somehow the keys to put it in bootmapper mode, so toggle-in out of it with the bootmapper client should get your keyboard out of that state.
Hope this helps man
So I've effectively done this. I tested it a little bit just now and it confirms the results I've gotten before.
- On plugging in the keyboard, it outputs the row/col info for the ESC key (0,.14 or something). EK picks this up, meaning specifically it picks up that "0", ",",".","1","4" were "pressed."
- Toggling bootmapper off sort of lets me type normally. Like pressing "q" gives me an actual q, not row/col. My guess is EK would pick this up.
- I can in fact download and upload layouts from and to the exent, and typing confirms this. For example I can map "q" to the number "1," and type it out.
- Unplugging then plugging it back in puts me back into the row/col output state, but does retain the programmed layout.
- Left column remains unresponsive.