rusefi.com

Posted: **Sat May 09, 2020 2:41 am**

Hello all,
My Miata engine exploded the other week so I bought a MicroRusEFI for a different project.

I received a preassembled Microrusefi the other day and I attempted to flash the firmware on my Linux desktop, but it looks like this board doesn't work.

I plugged it in to my computer holding PROGRAM to boot into DFU. Upon connecting, lsusb does not show microrusefi.
So I thought this may be a driver issue. In order to investigate further, I reconnected it to my computer and ran dmesg. Dmesg shows NO evidence my computer had a USB device plugged into it. I tried 3 different USB cables with no results. I retried without booting into DFU, and I get the same result. I also tried 2 different Windows computers and I can't get the device to show up on any of them.

All LEDs on the board are blinking as intended. Attached is the output of dmesg, and the board in DFU as well as regular mode. I've not modified the board in any way or even plugged in my connector.

Upon request, I also made an attempt to communicate with the board in non-DFU mode. So I plugged in the board into my PC NOT holding program as normal and did dmesg. This time it looks like Linux attempted to communicate with the board but failed. lsusb shows nothing. I also tried this with several different USB cables, still no change.

This was the output:

Code: Select all

[ 2470.465898] usb 1-10: Device not responding to setup address.
[ 2470.672219] usb 1-10: device not accepting address 14, error -71
[ 2470.795554] usb 1-10: new low-speed USB device number 15 using xhci_hcd
[ 2470.795991] usb 1-10: Device not responding to setup address.
[ 2471.002729] usb 1-10: Device not responding to setup address.
[ 2471.208884] usb 1-10: device not accepting address 15, error -71
[ 2471.208986] usb usb1-port10: unable to enumerate USB device
[ 2510.352432] usb 1-10: new low-speed USB device number 16 using xhci_hcd
[ 2510.475782] usb 1-10: device descriptor read/64, error -71
[ 2510.705794] usb 1-10: device descriptor read/64, error -71
[ 2510.935769] usb 1-10: new low-speed USB device number 17 using xhci_hcd
[ 2511.059125] usb 1-10: device descriptor read/64, error -71
[ 2511.289142] usb 1-10: device descriptor read/64, error -71
[ 2511.399081] usb usb1-port10: attempt power cycle
[ 2512.042457] usb 1-10: new low-speed USB device number 18 using xhci_hcd
[ 2512.043372] usb 1-10: Device not responding to setup address.
[ 2512.250372] usb 1-10: Device not responding to setup address.
[ 2512.455777] usb 1-10: device not accepting address 18, error -71
[ 2512.579125] usb 1-10: new low-speed USB device number 19 using xhci_hcd
[ 2512.579618] usb 1-10: Device not responding to setup address.
[ 2512.786212] usb 1-10: Device not responding to setup address.
[ 2512.992458] usb 1-10: device not accepting address 19, error -71
[ 2512.992551] usb usb1-port10: unable to enumerate USB device
[ 2540.462647] usb usb1-port10: Cannot enable. Maybe the USB cable is bad?
[ 2540.585943] usb 1-10: new low-speed USB device number 21 using xhci_hcd
[ 2541.535962] usb 1-10: device descriptor read/64, error -71
[ 2541.972636] usb 1-10: device descriptor read/64, error -71
[ 2542.079354] usb usb1-port10: attempt power cycle
[ 2542.929283] usb 1-10: new low-speed USB device number 22 using xhci_hcd
[ 2542.929764] usb 1-10: Device not responding to setup address.
[ 2543.136387] usb 1-10: Device not responding to setup address.
[ 2543.342614] usb 1-10: device not accepting address 22, error -71
[ 2544.715992] usb usb1-port10: Cannot enable. Maybe the USB cable is bad?
[ 2544.716079] usb usb1-port10: unable to enumerate USB device
[ 2545.559298] usb 1-10: new low-speed USB device number 24 using xhci_hcd
[ 2545.682654] usb 1-10: device descriptor read/64, error -71
[ 2545.912656] usb 1-10: device descriptor read/64, error -71
[ 2546.142634] usb 1-10: new low-speed USB device number 25 using xhci_hcd
[ 2546.269325] usb 1-10: device descriptor read/64, error -71
[ 2546.499315] usb 1-10: device descriptor read/64, error -71
[ 2546.606044] usb usb1-port10: attempt power cycle
[ 2547.249317] usb 1-10: new low-speed USB device number 26 using xhci_hcd
[ 2547.250632] usb 1-10: Device not responding to setup address.
[ 2547.455996] usb 1-10: Device not responding to setup address.
[ 2547.662646] usb 1-10: device not accepting address 26, error -71
[ 2547.785983] usb 1-10: new low-speed USB device number 27 using xhci_hcd
[ 2547.787382] usb 1-10: Device not responding to setup address.
[ 2547.994012] usb 1-10: Device not responding to setup address.
[ 2548.199311] usb 1-10: device not accepting address 27, error -71
[ 2548.199413] usb usb1-port10: unable to enumerate USB device

I'm fairly convinced that I received a faulty board, but I may be doing something wrong.
Thank you!

Posted: **Sat May 09, 2020 2:48 am**

Do you have any windows devices around?

Posted: **Sat May 09, 2020 2:56 am**

Blue LED blinking frequency is faster when rusEFI firmware does not sense USB data connectivity
and
Blue LED blinking frequency is slower when rusEFI firmware senses USB data connectivity.

Can you please compare blue LED blinking frequency between connected to PC and connected to wall charger?

Posted: **Sat May 09, 2020 3:03 am**

I just tried another rusEfi ECU (same microcontroller and USB setup) on my Linux machine, and it seems to work fine.

Here's what I get from lsusb in normal mode:

Code: Select all

root@matthew-l-u:~# lsusb
...
Bus 003 Device 007: ID 0483:5740 STMicroelectronics STM32F407
...

When in normal mode, this device appears too, which is the serial port used to communicate with the ECU.

Code: Select all

/dev/ttyACM0

Here's what I get when I hold the program button while plugging in USB (LEDs should NOT flash in program mode, btw):

Code: Select all

root@matthew-l-u:~# lsusb
...
Bus 003 Device 008: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
...

Your board's firmware was installed over USB - so it worked at some point in the past. Do you have another cable and/or computer you can try?

Posted: **Sat May 09, 2020 3:17 am**

Yes, I've tried on 2 different windows computers. I've also tried 3 different USB cables. I'm not currently at home but I will plug it into the wall when I get home but I'm still not convinced I will be able to get this thing working without modifications. The windows PCs have all nessacary drivers installed and NOTHING shows up in the device manager, not even unknown device.

Posted: **Sat May 09, 2020 3:30 am**

just to confirm, these USB cables transferred data previously? I doubt that all 3 of your cables are charge only, statistically at least one would be data not just power.

let me issue a return label for you, please ship this unit back for refund

Posted: **Sat May 09, 2020 3:18 pm**

USB cable length?

Posted: **Sat May 09, 2020 3:25 pm**

kb1gtt wrote: ↑
Sat May 09, 2020 3:18 pm
USB cable length?

I suspect you are referring to https://rusefi.com/forum/viewtopic.php?f=4&t=1712

Posted: **Mon May 11, 2020 6:35 am**

Always a possibility it is cable length, anything above 2m has seemed to potentially cause issues.

Any news on this one?

Posted: **Wed May 13, 2020 12:17 am**

OrchardPerformance wrote: ↑
Mon May 11, 2020 6:35 am
Any news on this one?

This unit is being returned, I am hoping to have it in my hands in 2-7 days.

Posted: **Sat May 16, 2020 7:30 pm**

Refund issued - device was definitely not working properly. Device is now in my hands.

On the one hand we get power via USB and blue LED is blinking fast in "USB not connected" mode.

One concerning thing I've noticed - there was no plastic spacer on the back side of the board, that's my fault - I was converting this board from VR to Hall and must have forgotten to install the spacer. No idea if that would cause issues or not. https://github.com/rusefi/hw_microRusEfi/issues/166 created as an improvement.

Some hot air applied on pins - no change. Pins are sticking from the back side of the board so that bust be GCT USB3131-30-0230-A

I was able to connect via ST-Link and update firmware. This did not improve things.

TL,DR: stm32 works, USB does not. Soldering on USB connector looks good. Maybe USB data pins were shorted by myself and that has damaged stm32 chip?

Posted: **Mon May 18, 2020 9:10 am**

Weird.
I have had issues with solder bridges under some of the smaller chips stopping the USB working but that was a hand assemble and does not explain why it worked before.

is it possible something between the usb and stm has failed? Either a trace or a component?

Posted: **Mon May 18, 2020 9:17 am**

Static electricity? Is there any esd protection on usb lines?

Posted: **Mon May 18, 2020 3:38 pm**

Yes the USB has ESD protection.

Posted: **Sat Jun 20, 2020 6:06 pm**

Status update: it was a mechanical issue with GLOBAL CONNECTOR TECHNOLOGY usb3131-30-0230-A

Going forward we are switching to Wurth Elektronik 614105150721 until a better solution under https://github.com/rusefi/hw_microRusEfi/issues/165

One can distinguish connectors by the small rectangle stamping all the way down.

Posted: **Sun Jun 21, 2020 8:36 pm**

Lcsc has mini usb that should fit same footprint I believe. Part C46396.

Posted: **Sun Jun 21, 2020 8:41 pm**

texasgdp754 wrote: ↑
Sun Jun 21, 2020 8:36 pm
Lcsc has mini usb that should fit same footprint I believe. Part C46396.

Good to know! Unfortunately not offered for assembly https://jlcpcb.com/parts/componentSearch?searchTxt=C46396

Posted: **Wed Jul 01, 2020 12:49 am**

Well I am glad I made a mistake and ordered the SMD ones with my last BOM, that resulted in me getting a bunch of these on next day.

https://uk.rs-online.com/web/p/usb-connectors/1225097/

rusefi.com

Unable to do MicroRusEFI first flash on new pre-assembled board [update: microUSB connector failure]

Unable to do MicroRusEFI first flash on new pre-assembled board [update: microUSB connector failure]

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board

Re: Unable to do MicroRusEFI first flash on new pre-assembled board [update: microUSB connector failure]

Re: Unable to do MicroRusEFI first flash on new pre-assembled board [update: microUSB connector failure]

Re: Unable to do MicroRusEFI first flash on new pre-assembled board [update: microUSB connector failure]

Re: Unable to do MicroRusEFI first flash on new pre-assembled board [update: microUSB connector failure]