-
Notifications
You must be signed in to change notification settings - Fork 125
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
Unable to get board v5 to work #130
Comments
Hard to say, I may be able to come up with a test firmware that would help determine if B side is even alive (if the problem is with the microcontroller or with the hub chip or something), but to be honest that probably won't help much with making the board work a whole. |
I've had a problem with the flash chips in the past that could affect either the A side or the B side and I think the symptoms would match what you're observing, but I made a revision that was supposed to get rid of that issue. |
I doubt it is something to do with the A or B side. Here is my reasoning: |
Yeah, if you can flash firmware at all and connect from the web config interface, it means side A is working. Can you post a closeup picture of one of the boards? Maybe something will jump out. |
Certainly but it will be in a few days as I am away. Will post update with picture. |
I though maybe there would be some components missing or soldered in the wrong orientation, but I don't see anything like that. Try flashing this test firmware, flashing B side, then connecting again and going to the Monitor tab and see if anything shows up there. |
No luck but I did notice some change. I noticed something. I dont know why but once in a while, I do get 1 input in and it shows on the Monitor but nothing else. It appears the key stays stuck as if held down even after disconnecting the numpad from the HID. Disconnecting the HID "unstucks" the key press. Just to be sure, I tested the numpad connected directly and it works as expected. |
Ah, sorry, that was built for the wrong board, it couldn't have worked. Try this. |
OK, try this. But after clicking "Flash B side", don't unplug the Remapper, but instead go to the Monitor tab and see what is says. |
So that at least means that there is communication with the B side. At least the A side seems to think that is has successfully flashed the B side with its firmware. Maybe there's something wrong with the B-side flash chip. I may be able to come up with a test firmware where the B-side is be RAM-only, meaning that it isn't stored in flash and only runs once after flashing. |
Thank you for the time you are giving to this for what seems to be an hardware issue. |
Yeah, just to be clear, best case scenario here is that we identify which part is broken, we will likely not be able to make these boards work with just a different firmware. |
Yeah, I dont expect these to work anymore but if you want to investigate for whatever reason, I'll help however I can. |
Sorry, I dont mean to turn this into a support request but I ordered via JLCPCB 5 v5 boards. 1 was dead on arrival but the other 4 look fine. I am able to flash the firmware on all 4 using remapper_board.uf2 then flash B side but on all 4, no device connected are detected. Once, I managed to get 1 input on the monitor tab but I am unable to reproduce this.
If it helps, I also bought the adafruit board and everything works fine with it.
Any idea what could be the problem?
The text was updated successfully, but these errors were encountered: