[MRE] Firmware mismatch with Tuner Studio

Tuning, troubleshooting and the nitty gritty of using rusEFI to make your engine run nicely!
Post Reply
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

[MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

Hi all,

After almost a year of sitting around, I finally got round to connecting my microRusEfi to the computer...
only to be met with Tuner studio not accepting the connection with it.

I've tried with both .ini files / projects (for v0.3 and below / STM32F7 and v0.4 and above / STM32F4) but in both cases, it gives me the attached error.

Is there something I'm doing wrong?

Thanks for the help,
RUSEFI_FirmwareMismatch.JPG
RUSEFI_FirmwareMismatch.JPG (237.34 KiB) Viewed 419 times
mck1117
running engine in first post
running engine in first post
Posts: 875
Joined: Mon Jan 30, 2017 2:05 am
Location: Seattle-ish

Re: [MRE] Firmware mismatch with Tuner Studio

Post by mck1117 »

update the firmware on your ECU, looks like it's running pretty old firmware.
User avatar
AndreyB
Site Admin
Posts: 11404
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: [MRE] Firmware mismatch with Tuner Studio

Post by AndreyB »

marc426 wrote:
Wed Apr 21, 2021 10:34 pm
Is there something I'm doing wrong?
Yes, you are trying to use a unit with old firmware with a new project definition file. Your project definition file should match your firmware. If you want to connect to that old firmware as is, you need to find a matching project definition file.

You are much better updating to latest release and using matching fresh firmware and project definition .ini file

https://github.com/rusefi/rusefi/releases
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239
mck1117
running engine in first post
running engine in first post
Posts: 875
Joined: Mon Jan 30, 2017 2:05 am
Location: Seattle-ish

Re: [MRE] Firmware mismatch with Tuner Studio

Post by mck1117 »

AndreyB wrote:
Wed Apr 21, 2021 10:43 pm
You are much better updating to latest release and using matching fresh firmware and project definition .ini file
PS: newer firmware includes the ini inside the ECU, so you never have to go fishing for it again!
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

Thanks for the reply.

I've looked a bit into it and from what I've gathered, I should download the rusefi console and update directly in DFU mode. Correct me if I'm wrong :-)

One thing I can't figure out though is which package to select : in the latest Malbec release I can't seem to choose...
I would say the autoupdate.zip but not exactly sure... there's also the generic rusefi_bundle.
What are the differences between all these?

rusefi_bundle_mre_f4_autoupdate.zip
rusefi_bundle_mre_f4_hardware_QC_special_build.zip
rusefi_bundle_mre_f4_hardware_QC_special_build_autoupdate.zip
rusefi_bundle_mre_f4_recovery.zip
rusefi_bundle_mre_f4_recovery_autoupdate.zip
User avatar
AndreyB
Site Admin
Posts: 11404
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: [MRE] Firmware mismatch with Tuner Studio

Post by AndreyB »

https://github.com/rusefi/rusefi/wiki/microRusEFI-Manual has the best link and a lot of other useful info for microRusEFI users
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

Thanks Andrey!
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

I guess I'm a bit thick but I can't seem to get the console to open...
I'm trying to execute rusefi_console.exe that's in the latest bundle (20210417_121019_mre_f4_rusefi) but nothing happens...

rusefi_autoupdate.exe does launch a java window prompting me to choose between 4 options for the update. I pressed once and it went to another blank page...

Just looked at the video on how to program 1st time / 2nd time the MRE : it's running Win 7 like me so I guess the problem comes from my configuration. Is there a specific java version to be installed or maybe an update?

Thanks for the help,
User avatar
AndreyB
Site Admin
Posts: 11404
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: [MRE] Firmware mismatch with Tuner Studio

Post by AndreyB »

can you please open "cmd" window and launch java_console.exe from that terminal window? I assume there is an error which you just do not see.

Seeing four buttons tells me that you have at least some relevant java.

java console is working best under java 8, open question if having newer java could be an issue. I would love to see what error you see in that "cmd" window.
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

Well...
java_console.exe in the terminal doesn't execute anything.
I've searched for this particular file but no trace of it.

I did go into the java control panel and checked "show console" but it made no difference. I also updated it to version 8 Update 291.

Oh and if I execute java under the terminal, it gets me this :

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.


C:\Users\Marc>java_console.exe
'java_console.exe' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Marc>cd..

C:\Users>cd..

C:\>java
Usage: java [-options] class [args...]
           (to execute a class)
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)
where options include:
    -d32          use a 32-bit data model if available
    -d64          use a 64-bit data model if available
    -client       to select the "client" VM
    -server       to select the "server" VM
                  The default VM is client.

    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
                  A ; separated list of directories, JAR archives,
                  and ZIP archives to search for class files.
    -D<name>=<value>
                  set a system property
    -verbose:[class|gc|jni]
                  enable verbose output
    -version      print product version and exit
    -version:<value>
                  Warning: this feature is deprecated and will be removed
                  in a future release.
                  require the specified version to run
    -showversion  print product version and continue
    -jre-restrict-search | -no-jre-restrict-search
                  Warning: this feature is deprecated and will be removed
                  in a future release.
                  include/exclude user private JREs in the version search
    -? -help      print this help message
    -X            print help on non-standard options
    -ea[:<packagename>...|:<classname>]
    -enableassertions[:<packagename>...|:<classname>]
                  enable assertions with specified granularity
    -da[:<packagename>...|:<classname>]
    -disableassertions[:<packagename>...|:<classname>]
                  disable assertions with specified granularity
    -esa | -enablesystemassertions
                  enable system assertions
    -dsa | -disablesystemassertions
                  disable system assertions
    -agentlib:<libname>[=<options>]
                  load native agent library <libname>, e.g. -agentlib:hprof
                  see also, -agentlib:jdwp=help and -agentlib:hprof=help
    -agentpath:<pathname>[=<options>]
                  load native agent library by full pathname
    -javaagent:<jarpath>[=<options>]
                  load Java programming language agent, see java.lang.instrument

    -splash:<imagepath>
                  show splash screen with specified image
See http://www.oracle.com/technetwork/java/javase/documentation/index.html for m
ore details.

C:\>java -console
Unrecognized option: -console
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

User avatar
AndreyB
Site Admin
Posts: 11404
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: [MRE] Firmware mismatch with Tuner Studio

Post by AndreyB »

Please try

Code: Select all

java -jar rusefi_console.jar 
from the folder which contains that file not from c:\ root folder
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239
User avatar
AndreyB
Site Admin
Posts: 11404
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: [MRE] Firmware mismatch with Tuner Studio

Post by AndreyB »

Same java_console.exe please try it from the folder which contains it since "'java_console.exe' is not recognized as an internal or external command"
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

And here they are : first the java- jar rusefi_console.jar and then java_console.exe

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Marc>cd documents

C:\Users\Marc\Documents>cd rusefi

C:\Users\Marc\Documents\RUSEFI>cd snapshot_20210416_121019_mre_f4_rusefi

C:\Users\Marc\Documents\RUSEFI\snapshot_20210416_121019_mre_f4_rusefi>cd console


C:\Users\Marc\Documents\RUSEFI\snapshot_20210416_121019_mre_f4_rusefi\console>ja
va -jar rusefi_console.jar
I 210423 211518.972 [main] Launcher - rusEFI UI console 20210415
I 210423 211519.019 [main] Launcher - Compiled Fri Apr 23 00:19:07 CEST 2021
I 210423 211519.019 [main] Launcher -


Tool available: compile_fsio_file
        Convert all lines from a file to RPN form.


Tool available: compile_fsio_line
        Convert a line to RPN form.


Tool available: convert_binary_configuration_to_xml
        NOT A USER TOOL. Development tool to convert binary configuration into X
ML form.


Tool available: decompile_fsio_line
        Convert a line from RPN form.


Tool available: detect
        Find attached rusEFI


Tool available: dfu
        Program specified file into ECU via DFU


Tool available: firing_order
        NOT A USER TOOL. Development tool relating to adding new firing order in
to rusEFI firmware.


Tool available: functional_test
        NOT A USER TOOL. Development tool related to functional testing


Tool available: get_image_tune_crc
        Calculate tune CRC for given binary tune


Tool available: get_performance_trace
        DEV TOOL: Get performance trace from ECU


Tool available: get_xml_tune_crc
        Calculate tune CRC for given XML tune


Tool available: headless
        Connect to rusEFI controller and start saving logs.


Tool available: help
        Print this help.


Tool available: lightui
        Start lightweight GUI for tiny screens


Tool available: local_proxy
        Detect rusEFI ECU and proxy serial <> TCP


Tool available: network_authenticator
        rusEFI Online Authenticator


Tool available: network_connector
        Connect your rusEFI ECU to rusEFI Online


Tool available: print_auth_token
        Print current rusEFI Online authentication token.


Tool available: print_vehicle_token
        Prints vehicle access token.


Tool available: ptrace_enums
        NOT A USER TOOL. Development tool to process performance trace enums


Tool available: read_tune
        Read tune from controller


Tool available: reboot_dfu
        Sends a command to switch rusEFI controller into DFU mode.


Tool available: reboot_ecu
        Sends a command to reboot rusEFI controller.


Tool available: set_auth_token
        Set rusEFI Online authentication token.


Tool available: upload_tune
        Upload specified tune file to rusEFI Online using auth token from settin
gs


Tool available: version
        Only print version


Tool available: write_tune
        Write specified XML tune into controller


rlog Writing to logs/MAIN_rfi_report_2021-04-23_21_15_19_139.csv
Exception in thread "main" java.lang.IllegalStateException: java.io.FileNotFound
Exception: logs\MAIN_rfi_report_2021-04-23_21_15_19_139.csv (Access is denied)
        at com.rusefi.FileLog.start(FileLog.java:57)
        at com.rusefi.ConsoleUI.startUi(ConsoleUI.java:180)
        at com.rusefi.Launcher.main(Launcher.java:44)
Caused by: java.io.FileNotFoundException: logs\MAIN_rfi_report_2021-04-23_21_15_
19_139.csv (Access is denied)
        at java.io.FileOutputStream.open0(Native Method)
        at java.io.FileOutputStream.open(Unknown Source)
        at java.io.FileOutputStream.<init>(Unknown Source)
        at java.io.FileOutputStream.<init>(Unknown Source)
        at com.rusefi.FileLog.openLog(FileLog.java:93)
        at com.rusefi.FileLog.start(FileLog.java:55)
        ... 2 more
Shutdown hook...
Shutdown hook!


C:\Users\Marc\Documents\RUSEFI\snapshot_20210416_121019_mre_f4_rusefi\console>ja
va console.exe
Error: Could not find or load main class console.exe
User avatar
AndreyB
Site Admin
Posts: 11404
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: [MRE] Firmware mismatch with Tuner Studio

Post by AndreyB »

Your console does not have permissions to start writing logs. You can launch it under adminstrator or move it to a different folder?

I've made a software change to survive such scenario https://github.com/rusefi/rusefi/commit/6dab0a2916184e27c76c5060cf451eebed1f721e you can take latest 'nightly' build in about 20 minutes.

Thank you for a great error report!
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

Your console does not have permissions to start writing logs. You can launch it under adminstrator or move it to a different folder?
Bingo! Just put everything in another folder and it now launches! :)
Thank you for a great error report!
Well, I should thank you!
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

Another thing I've noticed : rusefi_simulator tends to get deleted if it encounters an error.
The two instances it happened :
  • Before managing to make rusefi_console work, I just clicked on rusefi_simulator, it tried to execute something but then crashed (or just closed) and deleted itself.
  • Now with rusefi_console, I launched the virtual simulator and randomly clicked on radiator fan or something like this. It opened a dialog box saying : no connectivity then closed itself and deleted itself (rusefi_simulator.exe)
Is there a way to keep it working other than recopying it again and again?

EDIT : After tinkering with the console, it seems it will still open the simulator if I click on connect... weird...
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

Not quite there yet...

The console recognizes the MRE (on COM25) and makes it react when I try to update with the auto-dfu mode but it stops there and I get this :

Code: Select all

Using selected COM25
Reboot command sent!

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

   ***************
   ***************
ERROR: Maybe DFU device not attached? Please check Device Manager.
ERROR: Maybe ST DFU Driver is missing?
ERROR: Maybe driver conflict with STM32Cube?
   ***************
   ***************
Target 00: Error Code: Unknown error 0x12340005. 
Target: 00
Error Code: Unknown error 0x12340005. 
TransferSize: 0
DFU State: (Unknown 0x75)
DFU Status: STATUS_OK
Request: (unknown 0x06416ABB). 
CurrentNBlock: 0x0000
CurrentLength: 0xC8002579
Percent: 0
Under device manager and in DFU mode, I have this :
image.png
image.png (90.37 KiB) Viewed 332 times
And for the record, this under normal (non-DFU) mode :
image.png
image.png (98.75 KiB) Viewed 332 times

I've tried (re?)installing the drivers via the rusefi_console but it makes no change...
User avatar
AndreyB
Site Admin
Posts: 11404
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: [MRE] Firmware mismatch with Tuner Studio

Post by AndreyB »

I have no idea what is this LibUSB-K PS2 I've never seen that before but please kill it with fire. There should be no LibUSB-K PS2 on device manager to update firmware.

Random internet link https://superuser.com/questions/227029/how-can-i-remove-libusb-on-windows-7/1149663
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239
marc426
Posts: 24
Joined: Fri May 08, 2020 9:14 pm

Re: [MRE] Firmware mismatch with Tuner Studio

Post by marc426 »

:) :) :)

Thanks again

Code: Select all

Using selected COM25
Reboot command sent!

Giving time for USB enumeration...
Executing .\.\DfuSe/DfuSeCommand.exe -c -d --v --fn ..\rusefi.dfu
1 Device(s) found : 
Device [1]: STM Device in DFU Mode, having [4] alternate targets 
 Duration: 00:00:01
Target 00: Upgrading - Erase Phase (12)... Duration: 00:00:01
Target 00: Upgrading - Erase Phase (24)... Duration: 00:00:02
Target 00: Upgrading - Erase Phase (49)... Duration: 00:00:02
Target 00: Upgrading - Erase Phase (49)... Duration: 00:00:03
Target 00: Upgrading - Erase Phase (61)... Duration: 00:00:03
Target 00: Upgrading - Erase Phase (61)... Duration: 00:00:04
Target 00: Upgrading - Erase Phase (61)... Duration: 00:00:04
Target 00: Upgrading - Erase Phase (61)... Duration: 00:00:05
Target 00: Upgrading - Erase Phase (74)... Duration: 00:00:05
Target 00: Upgrading - Erase Phase (74)... Duration: 00:00:06
Target 00: Upgrading - Erase Phase (74)... Duration: 00:00:06
Target 00: Upgrading - Erase Phase (74)... Duration: 00:00:07
Target 00: Upgrading - Erase Phase (86)... Duration: 00:00:07
Target 00: Upgrading - Erase Phase (86)... Duration: 00:00:08
Target 00: Upgrading - Erase Phase (86)... Duration: 00:00:08
Target 00: Upgrading - Erase Phase (86)... Duration: 00:00:09
Target 00: Upgrading - Erase Phase (100)... Duration: 00:00:09
Target 00: Upgrading - Download Phase (0)... Duration: 00:00:10
Target 00: Upgrading - Download Phase (2)... Duration: 00:00:10
Target 00: Upgrading - Download Phase (4)... Duration: 00:00:11
Target 00: Upgrading - Download Phase (5)... Duration: 00:00:11
Target 00: Upgrading - Download Phase (7)... Duration: 00:00:12
Target 00: Upgrading - Download Phase (9)... Duration: 00:00:12
Target 00: Upgrading - Download Phase (11)... Duration: 00:00:13
Target 00: Upgrading - Download Phase (12)... Duration: 00:00:13
Target 00: Upgrading - Download Phase (14)... Duration: 00:00:14
Target 00: Upgrading - Download Phase (16)... Duration: 00:00:14
Target 00: Upgrading - Download Phase (18)... Duration: 00:00:15
Target 00: Upgrading - Download Phase (20)... Duration: 00:00:15
Target 00: Upgrading - Download Phase (22)... Duration: 00:00:16
Target 00: Upgrading - Download Phase (24)... Duration: 00:00:16
Target 00: Upgrading - Download Phase (26)... Duration: 00:00:17
Target 00: Upgrading - Download Phase (27)... Duration: 00:00:17
Target 00: Upgrading - Download Phase (29)... Duration: 00:00:18
Target 00: Upgrading - Download Phase (31)... Duration: 00:00:18
Target 00: Upgrading - Download Phase (33)... Duration: 00:00:19
Target 00: Upgrading - Download Phase (35)... Duration: 00:00:19
Target 00: Upgrading - Download Phase (37)... Duration: 00:00:20
Target 00: Upgrading - Download Phase (39)... Duration: 00:00:20
Target 00: Upgrading - Download Phase (41)... Duration: 00:00:21
Target 00: Upgrading - Download Phase (43)... Duration: 00:00:21
Target 00: Upgrading - Download Phase (45)... Duration: 00:00:22
Target 00: Upgrading - Download Phase (47)... Duration: 00:00:22
Target 00: Upgrading - Download Phase (49)... Duration: 00:00:23
Target 00: Upgrading - Download Phase (51)... Duration: 00:00:23
Target 00: Upgrading - Download Phase (52)... Duration: 00:00:24
Target 00: Upgrading - Download Phase (54)... Duration: 00:00:24
Target 00: Upgrading - Download Phase (56)... Duration: 00:00:25
Target 00: Upgrading - Download Phase (58)... Duration: 00:00:25
Target 00: Upgrading - Download Phase (60)... Duration: 00:00:26
Target 00: Upgrading - Download Phase (62)... Duration: 00:00:26
Target 00: Upgrading - Download Phase (64)... Duration: 00:00:27
Target 00: Upgrading - Download Phase (66)... Duration: 00:00:28
Target 00: Upgrading - Download Phase (68)... Duration: 00:00:28
Target 00: Upgrading - Download Phase (70)... Duration: 00:00:29
Target 00: Upgrading - Download Phase (72)... Duration: 00:00:29
Target 00: Upgrading - Download Phase (74)... Duration: 00:00:30
Target 00: Upgrading - Download Phase (75)... Duration: 00:00:30
Target 00: Upgrading - Download Phase (78)... Duration: 00:00:31
Target 00: Upgrading - Download Phase (79)... Duration: 00:00:31
Target 00: Upgrading - Download Phase (81)... Duration: 00:00:32
Target 00: Upgrading - Download Phase (83)... Duration: 00:00:32
Target 00: Upgrading - Download Phase (85)... Duration: 00:00:33
Target 00: Upgrading - Download Phase (87)... Duration: 00:00:33
Target 00: Upgrading - Download Phase (89)... Duration: 00:00:34
Target 00: Upgrading - Download Phase (91)... Duration: 00:00:34
Target 00: Upgrading - Download Phase (93)... Duration: 00:00:35
Target 00: Upgrading - Download Phase (95)... Duration: 00:00:35
Target 00: Upgrading - Download Phase (97)... Duration: 00:00:36
Target 00: Upgrading - Download Phase (100)...
Upgrade successful !
 Duration: 00:00:00
Target 00: Uploading (24)... Duration: 00:00:01
Target 00: Uploading (68)... Duration: 00:00:01
Target 00: Uploading (100)...
Verify successful !
Done!
SUCCESS!
Please power cycle device to exit DFU mode
Post Reply