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

Failed to read the multi module! #50

Closed
DerP4si opened this issue Apr 13, 2022 · 17 comments
Closed

Failed to read the multi module! #50

DerP4si opened this issue Apr 13, 2022 · 17 comments
Labels

Comments

@DerP4si
Copy link

DerP4si commented Apr 13, 2022

If i try to do anything with multiflash (reading, writing) it always ends with
"Reading Flash Memory...failed!" "Failed to read the MULTI module!"
is it broken or am i doing something wrong?
Thanks <3
Screenshot 2022-04-13 173758

@benlye
Copy link
Owner

benlye commented Apr 13, 2022

Nine times out of ten this is a driver problem. What module do you have?

Can you enable Verbose Output and show the verbose log?

@DerP4si
Copy link
Author

DerP4si commented Apr 13, 2022

iRangeX IRX4 Plus 2.4G

@benlye
Copy link
Owner

benlye commented Apr 13, 2022

Can you enable Verbose Output and show the verbose log?

@DerP4si
Copy link
Author

DerP4si commented Apr 13, 2022

.\tools\dfu-util-multi.exe -a 2 -d 1EAF:0003 -U "C:\Users\Silas-PC\AppData\Local\Temp\tmp571E.tmp" -v

dfu-util-multi 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
Copyright 2020 Ben Lye
This program is Free Software and has ABSOLUTELY NO WARRANTY

This version of dfu-util has been modified for flashing an STM32 MULTI-Module. It is intended for use with Flash Multi.
Please report bugs to https://github.com/benlye/dfu-util-multi

Filter on vendor = 0x1eaf product = 0x0003
Opening DFU capable USB device... ID 1eaf:0003
Run-time device DFU version 0110
Found DFU: [1eaf:0003] devnum=0, cfg=1, intf=0, alt=2, name="UNDEFINED"
Claiming USB DFU Interface...
Setting Alternate Setting #2 ...
Cannot set alternate interface

@benlye
Copy link
Owner

benlye commented Apr 13, 2022

Yup, driver problem. See the fixes here:
https://github.com/benlye/flash-multi/blob/master/doc/Troubleshooting.md#re-installing-the-maple-dfu-device-drivers

If you've already tried the first method you can skip to the second. You may not have to do step 2 - it depends on the firmware/bootloader that is already on your module. If it shows up as a COM Port when you plug it in then you need to do step 2, if it shows up as a DFU device when you plug it in you can skip step 2.

@benlye
Copy link
Owner

benlye commented Apr 13, 2022

Also, make sure that the module is plugged directly into your computer, not via a USB hub. Older USB hubs can cause problems like this.

@DerP4si
Copy link
Author

DerP4si commented Apr 13, 2022

Hm i tried to do step 2 but the module doesnt apears as COM device but like this instead...even after removing the driver
Screenshot 2022-04-13 181353

@benlye
Copy link
Owner

benlye commented Apr 13, 2022

Never mind - you're using the right driver (libusbK) anyway. Next thing is to make sure that the module is connected directly to the computer and not via a USB hub. After that, try using different USB cables.

@DerP4si
Copy link
Author

DerP4si commented Apr 13, 2022

Well i plugged it directly in the mb and tried another cable... same issue. Gonna try it on my notebook next...

@DerP4si
Copy link
Author

DerP4si commented Apr 13, 2022

same problem

@DerP4si
Copy link
Author

DerP4si commented Apr 14, 2022

Ok i think its the Module itself... even with windows 7 its the same problem...tho I am curious why it says Multi Module Bootloader in the device manager

@benlye
Copy link
Owner

benlye commented Apr 14, 2022

The module is giving the correct USB device ID, which is how Device Manager identifies it. The problem seems to be coming from actually trying to communicate with it - it's not sending back the right information to the programming utility.

It's pretty rare for one of these things to have a faulty USB interface, but it does happen.

@DerP4si
Copy link
Author

DerP4si commented Apr 14, 2022

Ok ^^ my goal at the end is just to get it in ppm standalone mode to use it like this:
https://youtu.be/rYxwIrqE7q8
(on min 56 he shows that he installs the multi-stm-ppm-aetr-v1.3.2.86.bin firmware to do so)
it seems the shop i bought it installed the firmware 1.3.3.0... is there any way to get into ppm mode anyway or have i to refund it? ^^ Thanks for your quick replys btw

@benlye
Copy link
Owner

benlye commented Apr 14, 2022

If you can get the shop to replace it, that might be a good idea as it would probably be easiest.

If not, there are still ways you can program it:

  1. From a radio
    Any radio which runs OpenTX/EdgeTX or erSky9x/erSkyTX and supports the MULTI-Module can update the firmware on a the module. If you have one or know someone who does then you can go this route pretty easily.

  2. Using an external USB to Serial adapter
    You would need to solder some header pins onto the module's PCB and attach at to your computer via a USB-to-serial adapter such as a CP2102 like this. This method is a bit more hassle but completely bypasses the on-board USB interface. It's fiddly to get set up, but as long as you get the soldering and connections right it will work.

@DerP4si
Copy link
Author

DerP4si commented Apr 14, 2022

Yeah i thought so... He just flashed the right firmware and gonna send me the module right away...
Thanks for your help anyway i hope it works now as i intend so that i can finally have a RC Car again ^^

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had any recent activity. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed in 5 days.

@github-actions
Copy link

This issue has been automatically locked because there was no further activity after it was closed. Please open a new issue for any related problems.

@github-actions github-actions bot locked and limited conversation to collaborators May 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants