MicroRusEFI, not recognised by computer? [Update: driver issue]

[Joey120373]

Just got my MicroRusEFI out of the box,

I ordered the DIY kit without the main connector and a few other parts installed.

Its a R0.5.0 pcb

After soldering the components, cleaning and checking for solder bridges and shorts etc. I powered it up, one green and 2 red LEDs.

I opened up the bundle made sure it was for the microRusEFI, installed the drivers ( i was following along with the video ) , however, i cannot get my windows 10 laptop to see the board. I have tried 2 known good cables, and rebooted the PC a couple times, but aside from the LEDs coming on, its as if my PC just doesnt see the board. I cleaned the micro usb connector a second time and reflowed it for good measure. there dont appear to be and shorts or bad joints.

Does the board need a second power input?

Not sure where to go from here, any help would be apriciated.


Ill try to post some pics if i can get some decent ones.

Thanks

[Joey120373]

A few pics

[Dron_Gus]

Hi.
Did you check power lines?
Check that you have 3.3V on TP3.
Check that RESET line is high (Reset button side close to MCU)
If you have oscilloscope - check that X1 is oscillating.

[Joey120373]

Hi.
Did you check power lines? _yes, 5v rail~4.5v, 3.3v rail is 3.3v
Check that you have 3.3V on TP3.yes, 3.3v
Check that RESET line is high (Reset button side close to MCU)_No, side furthest from MCU appears to be ground, side closest to MCU is only 0.35v
If you have oscilloscope - check that X1 is oscillating. No scope handy, but my bench meter does show something,but not the right tool

I am hoping that the reset line is supposed to be 3.3v, not 0.3v?

[Joey120373]

ok, checked the schem, and it looks like r43 and c20 are on the reset line, i reflowed r43, and i pulled c20 in case it was shorted.

r20 seems fine, as is c20, if i jumper 3.3v to nrst, my computer can see it, it shows up as "STM32 BOOTLOADER" in my device manager, however i am still unable to get the firmware to load.....

as i cant see anything else on that circuit that could pull the signal low, is it safe to assume the MCU is dead?

I pulled the reset button off as well just to check that, its fine.

[Joey120373]

Giving time for USB enumeration...
Executing .\.\DfuSe/DfuSeCommand.exe -c -d --v --fn ..\rusefi_mre-f4.dfu
0 Device(s) found. Plug your DFU Device !

Target 00: Error Code: Unknown error 0x12340005.
Target: 00
Error Code: Unknown error 0x12340005.
TransferSize: 0
DFU State: (Unknown 0x74)
DFU Status: STATUS_OK
Request: (unknown 0xACB82DFD).
CurrentNBlock: 0x6975392C
CurrentLength: 0x74D33C
Percent: 0

this is the error that i get when attempting to update the firmware in manual DFU mode i also note that D29 lights dimly when i power it up in DFU mode, so looks like something it trying to work....

[AndreyB]

Is that on Windows 7 or Windows 10 or else?

I program firmware into kit boards to validate them, can you please try talking to the board with rusEFI console or Tuner Studio?

As for DFU programming failure, we had reports of this utility not working from some people. At this point step to reproduce are not clear, a work around is to install https://www.st.com/en/development-tools/stm32cubeprog.html which would install different DFU driver and use that tool for all programming. With https://www.st.com/en/development-tools/stm32cubeprog.html rusEFI console DFU uploader would no longer work.

[AndreyB]

[Dron_Gus]

as i cant see anything else on that circuit that could pull the signal low, is it safe to assume the MCU is dead?

On MRE 0.5.0 TLE8888's WatchDog can pull reset low. You should remove R2 (if you populated it)... Looks like you did.
Also, as TLE8888 is powered from +12V it may pull it low when board is powered from USB only.
Anyway this is a new feature (reset driven from TLE), so I would recommend to remove R2.

[Joey120373]

ill try removing R2, it was on the board when i got it, thanks


I have a windows 10 computer.

[Joey120373]

Removing R2 did bring the reset line up to 3.3v, however still no luck with manual DFU mode, ill try downloading

https://www.st.com/en/development-tools/stm32cubeprog.html

thanks

[AndreyB]

I program firmware into kit boards to validate them, can you please try talking to the board with rusEFI console or Tuner Studio?

It's important to figure out if stm32 in general is not happy or if the issue is only about DFU.

[Joey120373]

That appears to have done the trick.

Using the STM32 Cube program i was able to load the .bin file and everything seems to be fine.

Tunerstudio works fine as well.

So it looks like it was an issue with the DFU? I can try some other tests if you like.

Ill start testing the outputs tonight, thanks for all the help.

[Joey120373]

ok, after getting the firmware to load using the STM32 cube program, I tried it again with the RusEFI console, in both auto and manual DFU mode.

It still throws the same error message. So appears something with the Console is not happy.

I'm using the snapshot_20200530_002826_mre-f4_rusefi\console , however i have tried the others that had the "microxxx ' file.

[AndreyB]

ok, after getting the firmware to load using the STM32 cube program, I tried it again with the RusEFI console

I am trying my best but I am not good with words.

"which would install different DFU driver and use that tool for all programming. "

would install different DFU driver I guess I should have said "a driver not compatible with console flasher"

use that tool for _all_ programming I guess I should have said "at this point you are in the cube programming universe until you revert the DFU driver"

[Joey120373]

. I am trying my best but I am not good with words.

"which would install different DFU driver and use that tool for all programming. "

would install different DFU driver I guess I should have said "a driver not compatible with console flasher"

use that tool for _all_ programming I guess I should have said "at this point you are in the cube programming universe until you revert the DFU driver"

AndreyB,

My apologies, thank you for the help, i did not explain well enough. I did attempt to use the console (DFU) after installing the cube program, however I got the same results. I have no way of knowing what drivers the console is using, so I tried the cube program
Just to see if I could get anything to work.

I would be happy to do more testing for you to try and isolate the issue , and I will try to follow instructions better. I tend to get ahead of myself at times.

[AndreyB]

Do you have another windows device?

In order to have a chance with DFU integrated with console you would need to switch driver. See "device manager" - see what you have there now. Uninstall it, install console driver pack, difference is expected.

Some info on https://github.com/rusefi/rusefi/issues/1170
Some info on https://github.com/rusefi/rusefi/issues/1477

[Joey120373]

Do you have another windows device?

In order to have a chance with DFU integrated with console you would need to switch driver. See "device manager" - see what you have there now. Uninstall it, install console driver pack, difference is expected.

I do not have another windows device, only a macbook pro.
My windows laptop is a lenovo thinkbook.

I will try uninstalling the driver from device manager and report back.

[Joey120373]

Ok, My new MRE arrived in the mail yesterday

This board already has firmware loaded, I soldered the USB connector and plugged it into my laptop, a windows 10 unit.

Green USB LED = On
Yellow Warn LED = On
Blue Comms LED = Blinking ~5 hz
Red 3.3v LED = On
Red GP5 LED = On

Start up RusEFI console and it connects :

Console 20200522; firmware=20200522@22961microRusEfi MICRO_RUS_EFI 548@COM28

is listed at the top of the console.

However, when I attempt to update the firmware using the console, in auto DFU mode
I get

Giving time for USB enumeration...
Executing .\.\DfuSe/DfuSeCommand.exe -c -d --v --fn ..\rusefi_mre-f4.dfu
0 Device(s) found. Plug your DFU Device !

Target 00: Error Code: Unknown error 0x12340005.
Target: 00
Error Code: Unknown error 0x12340005.
TransferSize: 0
DFU State: (Unknown 0x74)
DFU Status: STATUS_OK
Request: (unknown 0xAC10C53B).
CurrentNBlock: 0x69775C2C
CurrentLength: 0x75F43C
Percent: 0


Blue LED goes out, and so does the yellow LED.
And I have to cycle power to get it back online.
STM32 BOOTLOADER
does still appear in my device manager though

So What can i do from here to help resolve this issue?
The board works fine, and i can update using the cube program if i want to, however i would like to do what i can to solve this problem. This is a spare board so i dont mind playing around with it

[kb1gtt]

Is the console windows or other platform? I know Java is multiplatform but knowing the platform is useful information.

[Joey120373]

Windows 10 pro 64 bit

Lenovo ThinkBook

[AndreyB]

Console 20200522; firmware=20200522@22961microRusEfi MICRO_RUS_EFI 548@COM28
So What can i do from here to help resolve this issue?
The board works fine, and i can update using the cube program if i want to, however i would like to do what i can to solve this problem. This is a spare board so i dont mind playing around with it

1) look at the calendar
2) move to fresh bundle with fresh console
3) report results once attempted with latest console
4) attempt manual DFU with physical button if above does not help

we had (?) a defect where console was not switching RE into DFU mode. https://github.com/rusefi/rusefi/issues/1477

[Joey120373]

1) look at the calendar
2) move to fresh bundle with fresh console
3) report results once attempted with latest console
4) attempt manual DFU with physical button if above does not help

1, My calendar 6/9/2020 11:57am
2, downloaded 202006608
3, same exact results as above
4, attempted manual DFU, twice, same results as above

Auto DFU:

Auto-detecting port...
Reboot command sent!
Detected rusEFI on COM28

Giving time for USB enumeration...
Executing .\.\DfuSe/DfuSeCommand.exe -c -d --v --fn ..\rusefi_mre-f4.dfu
0 Device(s) found. Plug your DFU Device !

Target 00: Error Code: Unknown error 0x12340005.
Target: 00
Error Code: Unknown error 0x12340005.
TransferSize: 0
DFU State: (Unknown 0x74)
DFU Status: STATUS_OK
Request: (unknown 0xAC5C86E3).
CurrentNBlock: 0x69775C2C
CurrentLength: 0x75F43C
Percent: 0

ManualDFU :

Giving time for USB enumeration...
Executing .\.\DfuSe/DfuSeCommand.exe -c -d --v --fn ..\rusefi_mre-f4.dfu
0 Device(s) found. Plug your DFU Device !

Target 00: Error Code: Unknown error 0x12340005.
Target: 00
Error Code: Unknown error 0x12340005.
TransferSize: 0
DFU State: (Unknown 0x74)
DFU Status: STATUS_OK
Request: (unknown 0xACC48AA5).
CurrentNBlock: 0x69775C2C
CurrentLength: 0x75F43C
Percent: 0

[mck1117]

It's a known issue trying to use the DFU update thru the console if you also have STM32CubeProgrammer installed. They use different drivers (which is insane), and the stm32cubeprog one seems to always take precedence.

The board works fine, and i can update using the cube program if i want to

So sounds like you're not blocked on this issue?

[AndreyB]

Oh, please un-install cube, please go back to the other driver, and please report if console auto switch works now.

It _could_ be that we have moved you to cube because auto-DFU-switched in console was broken.

on our end our improvement could be defecting the wrong driver and printing a clear message but I have no idea how to do it.

[AndreyB]

PS: maybe "0x12340005" is the unique ID of the "please uninstall your cube" situation.

[mck1117]

PS: maybe "0x12340005" is the unique ID of the "please uninstall your cube" situation.

a quick googling indicates that error code means dfuse couldn't open the driver

Code: Select all

ErrorCode = 0x12340005 which is ''The system cannot open the specified driver''

[Joey120373]

Ill give that a shot.

[Joey120373]

Well, I tried to uninstall cube,

however, i get an error:
"windows cannot find C:\program files\java\jre1.8.0_251\bin\javaw.exe "

I wonder what thats all about. Would it work to just delete the program folder form rhe program files directory?

[AndreyB]

We do not care about the cube application itself. we care about the driver it comes with. I believe you can uninstall the driver via device manager.