Skip to content
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

Closed
pavel-kirienko opened this issue Apr 23, 2021 · 14 comments · Fixed by #32
Closed

DCP enters the bootloader mode at first power on #9

pavel-kirienko opened this issue Apr 23, 2021 · 14 comments · Fixed by #32
Assignees
Labels
bug Something isn't working
Milestone

Comments

@pavel-kirienko
Copy link
Member

The DCP tends to occasionally freeze up when high-voltage power is applied to the target with Babel-Babel connected. Steps to reproduce:

  1. Connect Babel-Babel to the (unpowered) target via both CAN interfaces, the DCP port, and the USB.
  2. Connect Babel-Babel to the USB host (in my case this is a USB hub with a dedicated wall power supply).
  3. Apply high-voltage power to the target (Myxa B0 in my case).
  4. Observe DCP disappear from the list of connected devices on the host.

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.

@pavel-kirienko pavel-kirienko added bug Something isn't working question Further information is requested labels Apr 23, 2021
@pavel-kirienko pavel-kirienko added this to the v1.1 milestone Apr 23, 2021
@j3qq4hch
Copy link
Contributor

I think there should also be added an additional button for DCP reset to avoid endless fuss with connectors.

@suzonch
Copy link
Contributor

suzonch commented Aug 2, 2021

"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.

@pavel-kirienko
Copy link
Member Author

The USB device is detached from the host. It is not related to UAVCAN at all.

@suzonch
Copy link
Contributor

suzonch commented Aug 2, 2021

"Apply high-voltage power to the target (Myxa B0 in my case)." spin the motor?

@pavel-kirienko
Copy link
Member Author

No, just connect high voltage power supply. On my setup it is sufficient to trigger a failure.

@pavel-kirienko
Copy link
Member Author

I recorded this video for Alexander some time ago:

out.mp4

@suzonch
Copy link
Contributor

suzonch commented Aug 2, 2021

So one or all of those 4 devices should be disconnected if that error happens, right? Trying, hasn't happened yet.
Screenshot from 2021-08-02 18-55-29

@pavel-kirienko
Copy link
Member Author

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?

@suzonch
Copy link
Contributor

suzonch commented Aug 3, 2021

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?
Could be something with your USB hub/desktop?

@pavel-kirienko
Copy link
Member Author

Extensive testing shows that it is my computer to blame. Closing.

@dimracer
Copy link

Apparently, we have the assembly problem of the one particular device.
Let's try to reproduce the issue on the other devices

@pavel-kirienko
Copy link
Member Author

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?

@pavel-kirienko pavel-kirienko removed the question Further information is requested label Oct 18, 2021
@pavel-kirienko pavel-kirienko changed the title Electromagnetic interference issues with DCP DCP enters the bootloader mode at first power on Oct 18, 2021
@pavel-kirienko
Copy link
Member Author

On the original Dronecode Probe design, the button pin is pulled up externally:

image

On Babel-Babel it is left floating:

image

@pavel-kirienko
Copy link
Member Author

The boards that are already manufactured should be patched with a jumpwire between SWITCH and VDD_3V3:

image

This was referenced Oct 22, 2021
suzonch added a commit that referenced this issue Feb 1, 2023
@suzonch suzonch linked a pull request Feb 2, 2023 that will close this issue
suzonch added a commit that referenced this issue Feb 2, 2023
* CAN bus voltage measurement implemented #29

* CAN_VDD_EN pulled up to 5v #28

* #31 #30 #9

* ready for review

* minor changes

* version text added

* update readme
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
5 participants