-
Notifications
You must be signed in to change notification settings - Fork 126
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
can you please provide some test firmware? #3
Comments
Maybe a blink firework? At the keyboard part every mx switch is an io,so we can connect a led to the mx switch foot to test it. |
This is a really great idea. Pester me if it's not up by next weekend. :) |
https://youtu.be/kEVsoy24RTQ |
any chance you can publish that 'blinky' sketch, YFC? |
@TyberiusPrime I modified the mitosis PCB, so some led position may be different, but each led should be bright. PS: maybe left is right! ;-P |
@YCF cool! Your blink test works for me. Could you please also build something to test receiver and its module? I haven't soldered any leds to receiver, because I have no PLCC-4 but I tried individual leds and they don't seem to light up at all. I'm not getting any response from it and keyboard doesn't work, and I have no idea why. Pro Micro recognizes as HID keyboard, receiver's and left/right modules respond to openOCD but it doesn't send any keystrokes. Could you upload all the firmwares you're currently using including QMK? Maybe I've just built it wrong. Maybe YJ-14015 has different RX/TX pins or I have faulty PCB but for the love of god I can't make it work. I've asked @reversebias to upload his QMK firmware as well. P.S. could you please share the source of that blink test? I've soldered keyboard led to the right half (PIN 17) but I can't turn it on using mitosis toolchain. I'm trying:
...but it doesn't light up. I've tried to build SDK11 rtc samples with IAR (edited boards.h) and upload it the same way, they blink just fine. Upd: IT FINALLY WORKS. I had to re-create and rebuild the entire project with IAR. Had to #define CLOCK_ENABLED 1 and #define RTC0_ENABLED 1 for the receiver otherwise it doesn't compile there. I've also added LED suport for the keyboard halves (it just blinks a couple of times on power up). See my fork (devel branch). |
EDIT: This is now fixed. I had a floating RX pin on the pro micro I'm having similar issues to @joric's post. All chips are programming ok but the keyboard as a whole isn't working. I've no idea how to debug it with OpenOCD so it's a total black box to me I'd appreciate advice on how to:
Thanks |
I just realised this issue is closed so people wouldn't have got notifications Pinging @YCF @reversebias @joric (hope that's not spammy) |
Hey man! I managed to solve it with #7. You can also browse https://github.com/joric/mitosis/tree/devel there are precompiled binaries I used. |
First of all, thank you very much for the design.
At present I was in trouble, I have welded the receiver and keyboard, it does not work properly. The two modules and the pro micro I have flashed.
But,because the PCB does not some indicate working status leds, so we do not know whether the wireless module is working properly.
I hope you can provide some basic wireless test firmware, I can think of is:
Receiver Test firmware:
After the power is on, send a button keep pressing and releasing to Pro micro , so we can know that the receiver module is working properly.
Keyboard Test firmware:
Send the letter 'A'( S6 ?) to the receiver repeat, so we can know that the wireless part of the receiver and keyboard is working properly.
Now I am facing a non-working mitosis, and I totally do not know how to fix it.
T_T
The text was updated successfully, but these errors were encountered: