I ended up reverting to the stock keyboard firmware for this reason.
Hey All, I just got my A04. Assembled and seemed to be working ok. I just updated to the latest OS and also noticed this keyboard FW was recommended. My keyboard/trackball seems to update fine based on the message but was non-responsive as noted in the instructions I tried flashing again but never seems to the second attempt
After a reboot, my keyboard and trackpad are now not responding but can still be flashed. Here is what I have tried:
- Reseating KB
- Reseating Core 04A
- Reverting to Stock Keyboard FW
- Connecting KB via micro USB connection
- Hard resetting
- wiping my SD card with a completely clean install
- Throwing a pity party and crying.
None of these seem to work. So I am hoping you folks have another idea I missed! I can still use the dev term with an external KB/mouse or SSH. If I look under mouse/trackpad in the settings I do not see the clockworkpi device for the Mouse/Trackpad like I did when it worked, only the external drivers for my mouse.
Any help would be appreciated!
have you tried the keyboard on a normal PC? You can supposedly just connect its micro usb with a cable to a PC and use it like any USB keyboard⌠then you know if the keyboard works at all
1 Like
That option was tested.
I think its most likely the arduino IDE and board setup, check Godzil fork if there is something that doesn´t match How to build the firmware
1 Like
I did, no response on mac, linux windows or the devterm itself. Thanks for thr suggestion.
Thanks I will give this a look.
how you did the âHard resettingâ?
and what is the output when you flash the keyboard with new firmware?
and the firmware is
sudo apt install dfu-util -y
wget https://github.com/clockworkpi/DevTerm/raw/main/Code/devterm_keyboard/bin/DevTerm_keyboard_firmware_v0.3_utils.sh
chmod +x DevTerm_keyboard_firmware_v0.3_utils.sh
sudo ./DevTerm_keyboard_firmware_v0.3_utils.sh
?
Hey guu,
Hard reset was done to the Devterm itself. I just held the power button down for ~10seconds, pulled the USB-C and pulled the batteries. Then reinserted everything and powered on.
Here is the output from the firmware update I just did again:
cpi@clockworkpi-a04:~$ sudo ./DevTerm_keyboard_firmware_v0.3_utils.sh
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing keyboard_firmware 100%
Do you wish to flash the devterm keyboard firmware at your own risk?(y|n)y
Failed to open serial device.
dfu-util 0.9
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/
dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 1eaf:0003
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #2 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 2048
Copying data from PC to DFU device
Download [=========================] 100% 54224 bytes
Download done.
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
Resetting USB to switch back to runtime mode
Waiting for /dev/ttyACM0 serial...Done
The keyboard is still unresponsive after this. I suspect that the KB is defective and has nothing to do with the FW update itself.
1 Like
according the output you posted, yeah, the firmware is well flashed
1 Like
Thats what I thought. Thanks. I will get in contact with Clockwork and see what I can do about getting a replacement.
thanks! this is great! this fixes a YUGE problem ive had with my devterm
Thanks so much for this! Big improvement for me 
I know it will sound as some kind of vodoo but I turned on devterm without KB and with usb mouse attached and plug the devterm kb âthe YOLO wayâ as the unit was on⌠And it started to work 
(maybe it restarted some driver / demon ? 
)
1 Like
Lol. Glad that worked out for you. CW is awesome and sending out a replacement so I will just wait patiently for that. Appreciate the response.
Is it guuâs firmware that have a problem with the multiple key input (diagonal arrow input)?
2 Likes
Yes. I never built your code and instead flashed with the official script guu provided above. I didnât realize there was a difference and your version didnât have the multiple keypress bug. I imagine most folks used that script too and have the same problem. 
Sounds like the official script needs to be fixed to use the working version, @guu ?
1 Like
sure, I will dig into
3 Likes
Hey @guu , just to follow up, I got a replacement keyboard from cw and works great. firmware installed with no issues at all. It a huge improvement from the the original.
1 Like
thanks for the feedback
good to know that
and
It is not my improvement actually, just borrowed code from @foriequal0, and according to the report from other users, my version has the issue of multiple key input (diagonal arrow input)
but anyway ,glad to know that your keyboard back on board
2 Likes
Has anyone else run into the issues with the function layer keys? Yikes, this was my issue with the CAPS LOCK key not functioning properly due to using Colemak as my layout. I was looking through the keyboard firmware and didnât see any issues with why CAPS LOCK wasnât working, and thatâs why!