-
Notifications
You must be signed in to change notification settings - Fork 26
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
Comments
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? |
iRangeX IRX4 Plus 2.4G |
Can you enable Verbose Output and show the verbose log? |
.\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. This version of dfu-util has been modified for flashing an STM32 MULTI-Module. It is intended for use with Flash Multi. Filter on vendor = 0x1eaf product = 0x0003 |
Yup, driver problem. See the fixes here: 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. |
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. |
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. |
Well i plugged it directly in the mb and tried another cable... same issue. Gonna try it on my notebook next... |
same problem |
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 |
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. |
Ok ^^ my goal at the end is just to get it in ppm standalone mode to use it like this: |
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:
|
Yeah i thought so... He just flashed the right firmware and gonna send me the module right away... |
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. |
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. |
If i try to do anything with multiflash (reading, writing) it always ends with
![Screenshot 2022-04-13 173758](https://user-images.githubusercontent.com/28807283/163217696-c85a0270-83a7-4773-b947-16d5aa3f98b1.png)
"Reading Flash Memory...failed!" "Failed to read the MULTI module!"
is it broken or am i doing something wrong?
Thanks <3
The text was updated successfully, but these errors were encountered: