RomRaider

I moved all things related to serial communication to serial_port directory because there's 14 files that provide serial port operation. You enter the dir and you know that all that files are hardware related and you don't have to search through the whole dir. That was the only reason. If you think that it's not right, I'll move them back, although I think it clutters up the home dir.

Actually that's a good thing

What I meant that when building, it's easier that you have FastECU folder that contains all sources, and build folder outside that so you don't mix git and build code, named after arch/version that it's build against, which contains all necessary files so app can find them.

EDIT: And of course everyone can keep whatever structure they want, I just use that one as I was compiling code for different archs.

OK, if I understood you right, all serial port files stay in serial_port dir.



Yes, that's a good practice. But Qt by default uses build/ dir for building, and I think we should forsee a case when someone will build with default settings and then will want to commit and will have a lot of files changed. Also pro.user file contains a lot of settings that could be unique for every user. I'm not sure it should be included in repository. Otherwise it will rewrite pro.user file for everyone every time. Also build dir could be effectively excluded from git by adding it to gitignore. As I figured, this is common practice. But again, if you think it's not right, I'll revert .pro.user back. I hope I undestood you right. If I understood you wrong, please could you be more specific. And if I'm doing something wrong, please tell me straight. It won't insult me. Thank you.

And I almost ended with migrating from cmake back to qmake for FastECU-broker. They recommend to use cmake, but it is not compatible well between versions. I just started liking Qt when it striked back, LOL

You can add only a Broker.pro file:


Type qmake and then mingw32-make.

I finished. It also copies all needed files to build dir and should work out of the box. Please pull changes and try again. Thank you!

I think you are right with folder settings and we should forsee how it goes. And of course everyone can have whatever settings they like, just use gitignore to exclude files/folders.

I haven't use cmake much, as I have had problems every time I try to compile someone else project, no matter if it's Qt or plain c/c++ with QtCreator/qmake on Qt projects usually everything just works no matter if it's win or linux

Yeah, I don't like cmake too. But they say move to cmake, so I tried. And failed I thought I would use VSCode because I did not like Qt Creator from ghe first sight. But then I get used to it.

I reverted FastECU-broker back to qmake.

New beta release of FastECU software is out for testing purposes and it can be found on FastECU github release page here.

More info and discussion, please check:
https://www.fastecu.fi/forum/viewtopic.php?t=134

tested the modules:
flash_ecu_subaru_mitsu_m32r_kline - writes / does not read
flash_ecu_subaru_unisia_jecs_20 - writes / reads
flash_ecu_subaru_unisia_jecs_20 - writes / reads
lash_ecu_subaru_denso_sh72531_can - writes / reads
lash_tcu_cvt_subaru_mitsu_mh8111_can - does not writes / does not read
flash_ecu_subaru_denso_sh72531_can - - writes / reads

New beta is available! Check it out and download it from here.

Trying to read a CVT TCU on the bench. The file doesn't have anything in it when it's done reading. All FF

Post up what happens at the start of the connection process.

FastECU produces a log file, or you can copy/paste the text in the output window.

It's not initializing the bootloader. Also shows cal ID as zero's