"functional_test" is the interesting one for developers
reboot_dfu and reboot_ecu are just cool
Re: Firmware developent status
Posted: Thu May 21, 2020 5:19 am
by AndreyB
rusEFI console time start-up time was improved by 2-3 seconds.
This would not happen without two people providing feedback. Your feedback is really important. Also at the moment it's really unclear if anyone uses rusEFI at all so please let us know
Re: Firmware developent status
Posted: Thu May 21, 2020 7:21 pm
by dexter_lab
I can test during the weekend.
Need to find a documentation how to upgrade.
As today I cannot enter DFU mode with MRE from pin 15,16
It would be handy if it could write it directly to the sd-card, regardless whether console is connected or not - in case there is some crosstalk in usb cable and the connection is not reliable (if its not implemented yet)
Re: Firmware developent status
Posted: Sun May 31, 2020 10:25 pm
by AndreyB
Tune upload using auth tokens now works from both rusEFI console GUI and command line. Command lines now how a brief explanation.
I need help with testing this a bit: I am not 100% confident in .msq files rusEFI console is producing, I wonder if some fields are not making into the tune or maybe some fields are not persisted right. If anyone can play with it and report issues that would be great.
The big theme here is the rusEFI online experience eventually with logs being published and tune modifications taken from internet.
rusEfi UI console 20200531
Compiled Sun May 31 18:18:39 EDT 2020
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 XML form.
Tool available: detect
Find attached rusEFI
Tool available: firing_order
NOT A USER TOOL. Development tool relating to adding new firing order into rusEFI firmware.
Tool available: functional_test
NOT A USER TOOL. Development tool related to functional testing
Tool available: headless
Connect to rusEFI controller and start saving logs.
Tool available: help
Print this help.
Tool available: print_auth_token
Print current rusEFI Online authentication token.
Tool available: ptrace_enums
NOT A USER TOOL. Development tool to process pefrormance trace enums
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 authentication token.
Tool available: upload_tune
Upload specified tune file using auth token from settings
rusEFI console now writes same cranking composite event logging into three files: TS CSV, VCD and logicdata formats.
Re: Firmware developent status
Posted: Mon Jun 15, 2020 12:04 am
by AndreyB
@kon has just contributed E90 gauge cluster support, waiting for a sweet demo video.
rusEFI console now writes logs in binary MLQ format in addition to legacy plain text MSL format. My focus these days is on rusEFI Online, getting closer to logs auto-upload from TS, rusEFI console and small linux devices.
Re: Firmware developent status
Posted: Fri Jul 10, 2020 3:21 am
by AndreyB
@dbh97 has migrated all important infrastructure batch files to bash and moved bundle generation to github actions - that means that all bundles for all boards & platforms are now ready in under 10 minutes after merge!
Re: Firmware developent status
Posted: Fri Jul 24, 2020 3:40 am
by AndreyB
Bundle has bin/ folder now, inside bin/ folder we now have dfu_program.sh which runs rusEFI own DFU tool on Linux and Darwin. On Windows there is just too much drama with drivers to use this tool.
Re: Firmware developent status
Posted: Sat Aug 08, 2020 1:47 am
by AndreyB
New feature: We now have access to SD card logs via rusEFI TunerStudio plugin.
Matt strikes again. rusEFI now gives access to SD card via USB. We are like proper adults now! The magic of composite USB device allows us to tune ECU while downloading logs as well!
Re: Firmware developent status
Posted: Sun Feb 14, 2021 7:49 pm
by mck1117
We also report a serial number over USB now - so multiple rusEFI devices should always show up as the same COM port on your PC (if you're a weirdo like me and have literally 10 ECUs sitting around).
ST burns a serial number in to the chip in the factory, and that's the one we send over USB. They guarantee that no two STM32 devices will ever have the same serial number.
Re: Firmware developent status
Posted: Wed Mar 03, 2021 9:15 am
by mck1117
More neat USB features:
Built in ini file for TunerStudio means if you have the ECU, you never have to go hunting for the matching ini.
Now that we have dozens of different firmware versions
image.png (7.85 KiB) Viewed 30896 times
Re: Firmware developent status
Posted: Thu Oct 07, 2021 3:20 pm
by AndreyB
We are very excited about user-defined Lua and converting some of the system logic into Lua. Nothing definitive yet but it's really recommended to use at least stm32f42x with 256K of ram to future proof your hardware.
Re: Firmware developent status
Posted: Fri Oct 15, 2021 1:34 am
by AndreyB
Let's welcome third generation of live data/live logic/live view feature of rusEFI: the top side of the screen is the new stuff, console shows actual snippets of C/C++ code annotated with live field state.
Bottom side of this screenshot shows TeX approach to live view, it's going to be removed in a couple of days. While it looks amazing it's just too much effort to keep ECU firmware in sync with TeX live view. Second approach to live view was about annotating ECU firmware code but again that was just too much effort. Yesterday I've realized that simply showing ECU source code as is could be the best way for us considering lowest costs of keeping ECU and tools in sync.
