Flatpak

[as400l]

Would it be possible to compile and distribute FastECU as flatpak ?

On Musl distributions (Alpine, Void etc) AppImage will simply not work at all while Flatpak should work for everyone on all distros.

I think this idea is worth considering.

[miikasyvanen]

Yes it is possible :)

I've made some tests, can you test if installing attached flatpak file is possible?

FastECU.flatpak.zip

[as400l]

Wow, that was quick !

Yes, it is possible and app starts.
Should I add some permissions ?

[miikasyvanen]

Well, I didn't yet test it anymore than that app starts. But it should work as normal, it has right to access home folder for configs (~/.config/FastECU/) and devices so only thing that should prevent from using obd adapters is just user group ('dialout' usually) permission.

[as400l]

Hey @miikasyvanen,

So I tried to read from ecu and test write today. It connects to the car since it identifies ECU number and the bottom left bar goes green. But when I click on "Test write" nothing happens and I get below messages:

[2024-11-20 17:46:31.820]  Test write memory with flashmethod 'sub_ecu_denso_sh7058_can' and kernel 'kernels/ssmk_can_sh7058.bin'

[2024-11-20 17:46:34.272]  Connecting to Subaru 07+ 32-bit CAN bootloader, please wait...

[2024-11-20 17:46:34.273]  Checking if kernel is already running...

[2024-11-20 17:46:34.424]  Kernel ID: 

[2024-11-20 17:46:34.424]  No response from kernel, continue bootloader initialization...

[2024-11-20 17:46:35.279]  Initializing bootloader

[2024-11-20 17:46:35.279]  Sent: 00 00 07 e0 01 00 

[2024-11-20 17:46:35.329]  Response: 00 00 07 e8 41 00 be 3f e8 13 

[2024-11-20 17:46:35.329]  Sent: 00 00 07 e0 09 02 

So this logs suggests that the kernel is not running ? I know I have the kernels in .config:

ls -l .config/FastECU/0.1.0-beta.2/kernels/
total 76
-rw-------    1 luke     luke          5828 Oct 26 20:28 ssmk_can_sh7055.bin
-rw-------    1 luke     luke          5184 Oct 26 20:28 ssmk_can_sh7058.bin
-rw-------    1 luke     luke          5196 Oct 26 20:28 ssmk_can_sh7059d_euro5.bin
-rw-------    1 luke     luke          5192 Oct 26 20:28 ssmk_can_tp_sh7058.bin
-rw-------    1 luke     luke          5204 Oct 26 20:28 ssmk_can_tp_sh7058d_euro4.bin
-rw-------    1 luke     luke          5204 Oct 26 20:28 ssmk_can_tp_sh7059d_euro5.bin
-rw-------    1 luke     luke          6064 Oct 26 20:28 ssmk_kline_sh7055.bin
-rw-------    1 luke     luke          5428 Oct 26 20:28 ssmk_kline_sh7058.bin
-rw-------    1 luke     luke          1632 Oct 26 20:28 ssmk_mc68hc916y5.bin
-rw-------    1 luke     luke          3576 Oct 26 20:28 ssmk_tcu_can_sh7055_35.bin
-rw-------    1 luke     luke          2936 Oct 26 20:28 ssmk_tcu_can_sh7058.bin

[miikasyvanen]

It also got one succesful response when initializing ECU
Response: 00 00 07 e8 41 00 be 3f e8 13

I'll need to put one ECU on bench and test it.

[as400l]

Hey Miika,

I have ran flatpak with more verbose output. Not too much more information but may be of some help to you.
Tried read and write operations few times.

App path: "/app/bin/FastECU"
App root path: "/config"
APP DIRECTORY: "/home/luke"
isDevPath length 1
"/config./config"
"/config./kernels"
Config base dir "/home/luke/.config/FastECU/"
Sorted dir by date: "/home/luke/.config/FastECU/0.1.0-beta.2" QDateTime(2024-10-26 20:28:41.520 CEST Qt::LocalTime)
Cal dir: "/home/luke/.config/FastECU/0.1.0-beta.2/calibrations/"
Check file ":/config/fastecu.cfg"
Check file ":/config/menu.cfg"
Check file ":/config/protocols.cfg"
Check file ":/config/logger.cfg"
Check file ":/kernels/ssmk_mc68hc916y5.bin"
Check file ":/kernels/ssmk_can_tp_sh7058.bin"
Check file ":/kernels/ssmk_can_sh7058.bin"
Check file ":/kernels/ssmk_can_sh7055.bin"
Check file ":/kernels/ssmk_can_tp_sh7059d_euro5.bin"
Check file ":/kernels/ssmk_can_tp_sh7058d_euro4.bin"
Check file ":/kernels/ssmk_kline_sh7055.bin"
Check file ":/kernels/ssmk_kline_sh7058.bin"
Check file ":/kernels/ssmk_tcu_can_sh7058.bin"
Check file ":/kernels/ssmk_can_sh7059d_euro5.bin"
Check file ":/kernels/ssmk_tcu_can_sh7055_35.bin"
Looking config file from: "/home/luke/.config/FastECU/0.1.0-beta.2/config/fastecu.cfg"
Width: "maximized" Height: "maximized"
Serial port: "ttyUSB0"
Serial port: "ttyACM0 - "
Protocol ID: "21"
Flash transport: "CAN"
Log transport: "K-Line"
Log protocol: "SSM"
Primary def base: "ecuflash"
Calibration files: ()
Calibration files directory: "/home/luke/.config/FastECU/0.1.0-beta.2/calibrations"
Use RomRaider definitions: "disabled"
RomRaider def files: ()
Use EcuFlash definitions: "enabled"
EcuFlash def files directory: "/home/luke/.config/FastECU/0.1.0-beta.2/definitions/ecuflash/rommetadata"
Logger def file: "/home/luke/.config/FastECU/0.1.0-beta.2/definitions/romraider/logger_METRIC_EN_v370.xml"
Kernel files directory: "kernels/"
ECU protocols read
Protocols ID: "21/50"
"Subaru"
"SH7058"
"yes"
"Impreza WRX STi"
"2.5 6MT"
"sub_ecu_denso_sh7058_can"
"Subaru Forester/Impreza/Legacy 32bit DBW Denso 2007+ CAN (SH7058S/1MB)"
"CAN"
"K-Line"
"SSM"
ECU protocols set
758 EcuFlash definition files found
758 EcuFlash ecu id's found
No RomRaider definition files
QObject::connect(QWebSocket, WebSocketIoDevice): invalid nullptr parameter
QObject::connect(QWebSocket, WebSocketIoDevice): invalid nullptr parameter
QObject::connect(QWebSocket, WebSocketIoDevice): invalid nullptr parameter
QObject::connect(QWebSocket, RemoteUtility): invalid nullptr parameter
void MainWindow::external_logger(QString) "Connection successfull."
Serial port name: "ttyS0" ""
Serial port name: "ttyS1" ""
Serial port name: "ttyS2" ""
Serial port name: "ttyS3" ""
Update logboxes with protocol: "SSM"
EcuFlash cal id "AZ1G301F" found
Alias:  "subarucan"
Protocol: "sub_ecu_denso_sh7058_can"
Update protocol info by selected ROM
Protocol name for selected ROM found: "sub_ecu_denso_sh7058_can"
Protocol info for selected ROM updated
Serial port name: "ttyACM0" ""
Serial port name: "ttyS0" ""
Serial port name: "ttyS1" ""
Serial port name: "ttyS2" ""
Serial port name: "ttyS3" ""
Stop datalog
Protocol: "sub_ecu_denso_sh7058_can"
Make: "Subaru"
Checksum: "yes"
ecuCalDef->McuType: "SH7058" "SH7058"
Size: 1048576 1048576
ROM memory model is "SH7058"
Checksum module: "sub_ecu_denso_sh7058_can"
"Checksum block 0 OK"
"Checksum block 1 OK"
"Checksum block 2 OK"
"Checksum block 3 OK"
"Checksum block 4 OK"
"Checksum block 5 OK"
"Checksum block 6 OK"
"Checksum block 7 OK"
"Checksum block 8 OK"
"Checksum block 9 OK"
"Checksum block 10 OK"
"Checksum block 11 OK"
"Checksum block 12 OK"
"Checksum block 13 OK"
"Checksum block 14 OK"
"Checksum block 15 OK"
"Checksum block 16 OK"
Protocol to use: "sub_ecu_denso_sh7058_can"
MCU type: "SH7058" "SH7058" and index: 10
void MainWindow::external_logger(QString) "Starting"
Interface: "/dev/ttyACM0"
Testing j2534 interface, please wait...
Open J2534 device 0x0 with ID: 0x0
"Result check against: ar"
Result check OK
Result check failed, not maybe an j2534 interface!
Connect received: "61 72 6f 0d 0a " "aro\r\n" 0x5
Set CAN / ISO15765 filters OK
CAN init ready
Interface opened succesfully!
Checking if kernel is already running...
Request kernel id sent: "00 00 07 e0 7a a0 00 00 00 00 00 00 "
Request kernel id received: ""
Initial request kernel id received and length: "" 0
Kernel ID: "" ""
Interface: "/dev/ttyACM0"
Testing j2534 interface, please wait...
Open J2534 device 0x0 with ID: 0x0
"Result check against: ar"
Result check OK
Result check failed, not maybe an j2534 interface!
Connect received: "61 72 6f 0d 0a " "aro\r\n" 0x6
msgId 768
Set CAN / ISO15765 filters OK
ISO CAN init ready
Interface opened succesfully!
Initializing bootloader
Sent: "00 00 07 e0 01 00 "
Response: "00 00 07 e8 41 00 be 3f e8 13 "
Sent: "00 00 07 e0 09 02 "
void MainWindow::external_logger(QString) "Finished"
Stop datalog
Protocol: "sub_ecu_denso_sh7058_can"
Make: "Subaru"
Checksum: "yes"
ecuCalDef->McuType: "SH7058" "SH7058"
Size: 1048576 1048576
ROM memory model is "SH7058"
Checksum module: "sub_ecu_denso_sh7058_can"
"Checksum block 0 OK"
"Checksum block 1 OK"
"Checksum block 2 OK"
"Checksum block 3 OK"
"Checksum block 4 OK"
"Checksum block 5 OK"
"Checksum block 6 OK"
"Checksum block 7 OK"
"Checksum block 8 OK"
"Checksum block 9 OK"
"Checksum block 10 OK"
"Checksum block 11 OK"
"Checksum block 12 OK"
"Checksum block 13 OK"
"Checksum block 14 OK"
"Checksum block 15 OK"
"Checksum block 16 OK"
Protocol to use: "sub_ecu_denso_sh7058_can"
MCU type: "SH7058" "SH7058" and index: 10
void MainWindow::external_logger(QString) "Starting"
Interface: "/dev/ttyACM0"
Testing j2534 interface, please wait...
Open J2534 device 0x0 with ID: 0x0
"Result check against: ar"
Result check OK
Result check failed, not maybe an j2534 interface!
Connect received: "61 72 6f 0d 0a " "aro\r\n" 0x5
Set CAN / ISO15765 filters OK
CAN init ready
Interface opened succesfully!
Checking if kernel is already running...
Request kernel id sent: "00 00 07 e0 7a a0 00 00 00 00 00 00 "
Request kernel id received: ""
Initial request kernel id received and length: "" 0
Kernel ID: "" ""
Interface: "/dev/ttyACM0"
Testing j2534 interface, please wait...
Open J2534 device 0x0 with ID: 0x0
"Result check against: ar"
Result check OK
Result check failed, not maybe an j2534 interface!
Connect received: "61 72 6f 0d 0a " "aro\r\n" 0x6
msgId 140716885665834
Set CAN / ISO15765 filters OK
ISO CAN init ready
Interface opened succesfully!
Initializing bootloader
Sent: "00 00 07 e0 01 00 "
Response: "00 00 07 e8 41 00 be 3f e8 13 "
Sent: "00 00 07 e0 09 02 "
void MainWindow::external_logger(QString) "Finished"
Stop datalog
Update protocol info by selected ROM
Protocol name for selected ROM found: "sub_ecu_denso_sh7058_can"
Protocol info for selected ROM updated
Protocol to use: "sub_ecu_denso_sh7058_can"
MCU type: "SH7058" "SH7058" and index: 10
void MainWindow::external_logger(QString) "Starting"
Interface: "/dev/ttyACM0"
Testing j2534 interface, please wait...
Open J2534 device 0x0 with ID: 0x0
"Result check against: ar"
Result check OK
Result check failed, not maybe an j2534 interface!
Connect received: "61 72 6f 0d 0a " "aro\r\n" 0x5
Set CAN / ISO15765 filters OK
CAN init ready
Interface opened succesfully!
Checking if kernel is already running...
Request kernel id sent: "00 00 07 e0 7a a0 00 00 00 00 00 00 "
Request kernel id received: ""
Initial request kernel id received and length: "" 0
Kernel ID: "" ""
Interface: "/dev/ttyACM0"
Testing j2534 interface, please wait...
Open J2534 device 0x0 with ID: 0x0
"Result check against: ar"
Result check OK
Result check failed, not maybe an j2534 interface!
Connect received: "61 72 6f 0d 0a " "aro\r\n" 0x6
msgId 140716885665834
Set CAN / ISO15765 filters OK
ISO CAN init ready
Interface opened succesfully!
Initializing bootloader
Sent: "00 00 07 e0 01 00 "
Response: "00 00 07 e8 41 00 be 3f e8 13 "
Sent: "00 00 07 e0 09 02 "
void MainWindow::external_logger(QString) "Finished"

[miikasyvanen]

Tested with flatpak install on Linux Mint and it did work... few bug I found was that kernel folder path is parsed wrong in this version with flatpak, somehow it wants to look it from flatpak base folder, in your case I think it is APP DIRECTORY: "/home/luke" so kernels folder needs to be copied over there. Also it tried to use wrong kernel, right one should be "ssmk_can_tp_sh7058.bin" while in protocols.cfg it is "ssmk_can_sh7058.bin" under protocol "sub_ecu_denso_sh7058_can". Will fix these in next release.

In your log it hangs on VIN request but not actually sure why, as previous init command is succesful. Need to investigate bit further.

[as400l]

Hey Miika,

Thanks for looking at it. Will wait for the next version and report.

In the meantime - thanks for your work guys and Happy New Year to all of you :)

[as400l]

I tried latest beta4:

1. As Flatpak - can't write ECU.
2. As AppImage from a clean Debian chroot - can't write ECU.
3. As AppImage from Fedora 41 live CD - can't write ECU.

I can write ECU from Windows VM with ECUFlash normally.
Symptoms are always the same - I can connect to ECU sucessfully but when I try to test write it fails. Log attached.
I also tried to set to set baudrate of the port to 4800 with stty before trying to test write but it didn't help.

Strange thing is that I did write this ECU from precompiled FastECU version even before any beta.

log.txt

[miikasyvanen]

Can you try test write with Windows version?

I had beta.2 flatpak installed on my system and it went straight to seed key but fails there as I have another set of seed bytes on that ROM, not stock. On your log it always stops at VIN (0x09 0x02) request. Could be that you have that disabled so it wont pass that. But so has older codes so if you have not changed ECU / disabled possible VIN request it should work the same way. Master branch code is updated now so it wont stop anymore on non-relevant requests, please test it. Master branch is set on flatpak .yml so just compile it and it should work.

[stayspoolin]

Having issues appimage and locating flatpak-builder

[miikasyvanen]

Having issues appimage and locating flatpak-builder

Can you be bit more specific:
What OS / distro?
What issues with AppImage?
Is problem with installing flatpak-builder?

[stayspoolin]

Having issues appimage and locating flatpak-builder

Can you be bit more specific:
What OS / distro?
What issues with AppImage?
Is problem with installing flatpak-builder?

Im running raspberry pi OS (64-bit) the one in your video you said to put on a usb stick.
-dont know how to excute appimage or where to get it.
-dont see a flatpak-builder to download or know where to get one.