-
Notifications
You must be signed in to change notification settings - Fork 204
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
Terminal example 'crashes' USB Serial chip #3
Comments
Interesting, when does that happen? I haven't actively experienced that so far, but maybe I just didn't notice? But my setup is a bit hacky too: let IDF monitor configure the serial port and then pipe the output of |
Oh it might be power related, it crashes the entire hub it's connected to. On a dedicated port: same problem. Tried my second EPDIY board, same problem. |
Ha, that's interesting. So far I have not been able to reproduce it with neither of my machines... |
It seems to be a problem when i'm doing both serial AND updating the eink. Maybe i ordered the wrong parts and have an overcurrent problem. Or a lack of capacitors on the main 5v and 3.3v rails. No clue yet. It also breaks the USB connection in Windows. Its probably hardware :) |
Hm, jup, seems to be hardware. When I've got the time I can test it on a Raspberry Pi, which is not known for its particularly stable usb power / high current output, so I might be able to reproduce it there. |
Hm, I've tried it with my raspberry pi, still no unexpected behaviour :/ |
More digging: this also happens on the 5v rail. Added a 10nF cap to the CH330N, no effect. Current theories are:
It seems to happen when both USB serial and the Eink panel are working simultaneous. Note that i didn't follow the BOM as the BOM seemed outdated, as is the PDF for the schematic and PCB. I got all parts by looking in the schematic and getting them from LCSC. |
Quick question: the LT1945 seems to be powered of the 3.3v rail instead of the 5v rail. Why is that? |
I fixed it. So what i did was cut the trace supplying the P-fet with 3.3v and hooked it up to the 5v rail. Apparantly the LT1945 and subsequent stuff draw too much power and they destroy the 3.3v rail. I noticed in the PDF that an older version had it hooked up to 5v, so i took a chance. |
Thanks a lot, @sebastius! And yes, as you mentioned in #4, I should really update some artefacts. |
i've doubled the 3.3v and 5v caps (both now 2x 10uF) but to no avail. I recommend reverting to the 5v supply on that signal but allow people to use a range of voltages there. Anything above 3.3v and below 12v will probably work (depending on the mosfet, if the CH330n isn't present and the caps are capable of that voltage. I've left the pullup R1 on the 3.3v rail by the way. Also in general i recommend adding in more small caps on the powerrails, like 100n and 10n. Also, i'll do a pullrequest tonight or tomorrow with a bunch of GND via's to get better gndplane coverage on both sides. And i'll do a seperate one with the 5v mod described above. Another thought, we could make it a jumperpad. So you get to choose 3.3v or 5v rail. Yeah, i'll do that. Default on the 5v rail and with a slice and blob get it on the 3.3v (at your own risk). |
Hey, that sounds reasonable. I'm just learning by doing here myself, since my background is more in software than in hardware ;) |
Solved with the 5v patch and is fixed in #6. I've used the C125862, UZ1086L-33-TN3-R which has nearly the same specs but apparantly not good enough :) |
I was using the AMS1086CD-3.3, but aside from a slightly lower dropout voltage they seem pretty similar... |
Somehow the terminal example annoys the USB Serial chip so much it causes to re-enumerate on the USB bus 😎
Tried it with the Arduino IDE serial terminal, screen and IDF monitor. All three are gloriously killed 👍
Could be a shitty driver on my Linux Mint, could be a bad chip. Haven't seen this behaviour before in other USB serial chips, this is my first board with the CH330.
The text was updated successfully, but these errors were encountered: