-
Notifications
You must be signed in to change notification settings - Fork 3
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
DCP enters the bootloader mode at first power on #9
Comments
I think there should also be added an additional button for DCP reset to avoid endless fuss with connectors. |
"Observe DCP disappear from the list of connected devices on the host." you mean device manager or ucvan gui? I'm trying to reproduce the error. |
The USB device is detached from the host. It is not related to UAVCAN at all. |
"Apply high-voltage power to the target (Myxa B0 in my case)." spin the motor? |
No, just connect high voltage power supply. On my setup it is sufficient to trigger a failure. |
I recorded this video for Alexander some time ago: out.mp4 |
Hmm. This is an EMI issue so I would expect it to be difficult to reproduce. Can you try longer USB cables? A USB hub or two? Longer DCP cable? |
I don't think we have that long micro usb cable, I tried adding 2 extension cables. Works normally, Do we have longer DCP cable? |
Extensive testing shows that it is my computer to blame. Closing. |
Apparently, we have the assembly problem of the one particular device. |
This is not an EMI problem, this is a schematics issue. The DCP starts the bootloader instead of launching the main firmware. It is designed to do so if the BOOT button is pressed at power on, so we should ensure that the button is routed correctly. Maybe its pin is left floating? |
The DCP tends to occasionally freeze up when high-voltage power is applied to the target with Babel-Babel connected. Steps to reproduce:
It may take several attempts to reproduce the problem.
The issue affects none of the other three devices connected to Babel-Babel. The DCP can be brought back to life by physically re-connecting Babel-Babel to the host with the DCP port unplugged, and then plugging the DCP port back in.
I suggest equipping the DCP port with EMI mitigation measures, perhaps resistors or chokes. Also, increasing the decoupling capacitance on the MCU might help.
The text was updated successfully, but these errors were encountered: