Weird nice!nano issue
Out of nowhere, my right side corne split stopped working.
While debugging the issue, I found out that the issue seems to be the nice!nano since when I swapped the nice!nanos between the splits, the left side stopped working. What is very strange, is that if I flash the left side uf2 file on both splits, both are working.
I thought the issue was in my build files — even though both worked until today with the same build files — so I tried tried using an older version, but same issue. The one nice!nano where I flash the right side uf2 file, doesn’t work. @TyperAI any ideas why?
4 Replies
It sounds like the nice!nano you were using on the right side might have an issue with its BLE radio, which is needed for it to communicate with the left half.
Since flashing the left side firmware on both nice!nanos allows them both to work (presumably as left halves), this points away from a general hardware failure and more towards a communication issue when running the right-half specific firmware.
The most likely cause is a problem with the nice!nano itself. While you've already swapped them, the fact that the issue follows the specific nice!nano suggests it's the culprit.
Unfortunately, based on the documentation, there isn't a specific troubleshooting step for a nice!nano that only fails when running the right-half firmware.
You can try reflashing the bootloader on the problematic nice!nano as outlined in the Entering the Bootloader section of the troubleshooting guide. If that doesn't resolve the issue, the nice!nano may need to be replaced.
If you need further assistance, please reply to this message or tag me.
Entering the Bootloader | Typeractive.xyz Documentation
Learn how to enter the bootloader on your nice!nano.
It sounds like you've done some great troubleshooting already! Since the issue follows the nice!nano when you swap them, and flashing the left side firmware on both makes them work, it points to a potential issue with the right side firmware or how that specific nice!nano is interacting with it.
Here are a few things to consider based on the documentation:
1. Split Halves Connection: The right half acts as a peripheral and communicates with the left half (the central). If the right half isn't working, it's likely a pairing issue between the two halves. Try resetting the bonds on both halves using the steps in the Split Halves Won't Connect guide. After clearing the bonds, reset both halves simultaneously.
2. Firmware Files: While you've tried older versions, double-check that you are using the correct right-half firmware file for your specific Corne build (with or without nice!view, 5 or 6 column). You can find the links on the Corne Wireless Firmware page.
3. Re-flashing the Bootloader: In rare cases, the bootloader on the nice!nano could be acting up. The Nice Keyboards documentation has a guide on re-flashing the bootloader. This is a more advanced step, but might be worth considering if other troubleshooting fails.
If you've tried these steps and are still having trouble, feel free to reply to this message or tag me again for further assistance!
Split Halves Won't Connect | Typeractive.xyz Documentation
Fix your split ZMK keyboard halves not pairing.
Firmware | Typeractive.xyz Documentation
If you're not familiar, ZMK is a wireless-focused firmware, and it powers our Corne Wireless.
Troubleshooting - nice!nano
Troubleshooting tips for the nice!nano
Does the connection also happen if I have the both splits connected to the computer by cable? @TyperAI
@TyperAI , can the board be the cause of the issues of communication with the left half?
No, the connection between the split halves is wireless (BLE). Connecting both splits to the computer via cable is primarily for flashing firmware or potentially for power, but it doesn't establish the communication link between the left and right sides for typing. That communication relies on the wireless connection managed by ZMK.
Yes, the PCB itself could potentially be the cause of communication issues between the left and right halves, although it's less common than a nice!nano or firmware issue.
The documentation mentions that a short somewhere on the keyboard can cause battery drain, which could potentially impact the wireless communication. If you've ruled out nice!nano and firmware issues, and you're comfortable with it, you could inspect the PCB for any visible shorts or poor solder joints, particularly around the nice!nano sockets and the components involved in the wireless communication.
However, based on your initial troubleshooting where the issue followed the nice!nano, that still seems like the most probable cause.