Closed shenbomo closed 1 year ago
Hi, you could try and reinstall the bootloader but it sounds like a hardware issue to me.
Please open a ticket at: https://kinesis-ergo.com/support/kb360pro/#ticket for hardware related issues
Thanks for the reply. I have already opened a ticket. In the meantime, I am curious to know if you can point me to some documentation/instructions/tools/files for reinstalling the bootloader on this specific board?
Also, the keyboard worked fine right out of the box, and only stopped working after flashing the firmware a few times, it was working fine the first couple of times that I flashed the firmware. If your gut feeling is correct, does that mean flashing the firmware might damage the hardware?
I was sure not to disconnect the USB during each flash.
Thanks again!
It is unlikely that flashing the keyboard will damage the hardware. The bootloader is very resilient to corrupt data transfers
It is unlikely that flashing the keyboard will damage the hardware. The bootloader is very resilient to corrupt data transfers
Thanks! That's what I assumed as well.
BTW in case you missed it, have you come across any publicly available tools, docs, and firmware files that can perform a lower-level bootloader or board re-flash/re-program while forking and customizing the firmware for ADV360Pro by any chance?
I am eager to try it out myself and I couldn't find anything about re-installing the bootloader and resetting the storage space for the firmware other than AdaFruit tools which aren't really compatible with this customized board.
Much appreciated!!
@shenbomo Can you update us on the status of your keyboard please? Hopefully no news is good news.
I have contacted tech support, and they are helping me with the RMA process. Thanks for following up!
No worries, thank you for replying. If you're going through the RMA process I will close this issue out now
Problem:
Cannot properly flash the firmware on the left module, all LEDs are off and it stays in an unresponsive state, with no Bluetooth LED flashing, and no key responses.
Behavior change: After flashing the "Setting Reset" onto the left module, it would NOT immediately reboot into the bootloader mode anymore as before or as the right module would. Power-cycling by reconnecting the left module via USB-C, the 3 LEDs would flash white once quickly and then turn unresponsive, no key is registered, needless to say, the right module would not be able to connect with the left (3 LEDs flashing red).
However, after flashing the "Setting Reset" onto the left module, it has to wait for around 15 - 20 minutes before the left module eventually reboots into the bootloader and is recognized by the PC (3 solid green LEDs and USB drive mounted).
After every power-cycling (disconnecting and reconnecting using USB), it has to wait for around 15 - 20 minutes before the left module eventually comes back online (recognized by the PC) with the profile LED flashing(ready to pair), and registering key, however, it immediately goes unresponsive when I turn on the right module, not able to sync with the right module.
Things I have tried: (NONE of them worked)
Speculation:
The hardware seems intact since I am still able to get into the bootloader mode consistently by double-clicking the reset button on both of the left and right modules. After 15-20 minutes of waiting after a power cycle, the left module registers keystrokes via a USB connection, however not being able to sync with the right module.
Maybe the bootloader itself is messed up and requires a re-install or the SoftDevice s140 of the nRF52840 SoC (I am very new to ZMK and ZephyrOS, this is purely a baseless guess).
I am wondering if someone has run into similar issues before where flashing the Settings Reset UF2 and firmware UF2 messes up the left module like this.
I could not find any information related to fixing this kind of behavior anywhere, seems most problems can be fixed by flashing the reset and the firmware UF2 files.
Any help is much appreciated!! Thanks in advance!!