-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rama Works U80 - issues with the new framework #5
Comments
Did you download the firmware directly from github? If yes, the firmware is probably corrupted. Download it from https://caniusevia.com/docs/download_firmware |
@Wilba6582 No I downloaded it from https://caniusevia.com/docs/download_firmware |
This might be a firmware install problem. Can you download it again and install it again? The downloaded firmware works fine on my PCB. |
@Wilba6582 Actually I've downloaded + flashed it 3-4 times and nothing changed. I don't know if this helps or not but this is what I've done: Mac OS X 10.14.6
Is there any other way to completely reset the memory? |
I can't explain why it isn't working, I've tested this exact firmware on the PCB and it's fine. Contact Rama Works support: https://rama.works/contact about getting a replacement PCB. |
@Wilba6582 I see sure. Thank you for your help and your prompt replies! |
hey @farbodsalimi I am experiencing a similar issue with my Rama works u80-a seq 2. If I leave my keyboard plugged in to my laptop's usb hub it will stop responding when trying to wake it up. The only fix is to press the reset button and refresh the firmware. My current solution is to unplug the keyboard instead of letting the laptop go to sleep. |
@kikin81 sorry I totally missed this comment. So that PCB was faulty and I got a replacement. However, the replacement is also not perfect it randomly fails to wake up. |
My keyboard stops working after my laptop goes to sleep. I saw this new commit and thought it was a software issue so I flashed my keyboard but after flashing I have all sorts of other issues:
Could you please let me know if it's a software issue or a hardware/PCB issue?
The text was updated successfully, but these errors were encountered: