Add prepare file option to checksum & patch file
Added an option to prepare files for flashing with a different/bench tool, will automatically correct checksums and patch if applicable to the selected module.
Marking as draft for now, still need to do a couple of bits and not 100% on the UI atm:
- Should probably add another section to the docs
- Currently I've added it the same as the unlock dialog since it's not necessarily a "Flash" option for the dropdown, although curious for your thoughts on this?
- Currently the file gets prefixed with "PATCHED_" although on second thoughts "CHECKSUMED_" or even prompting for output file instead of directory would probably make more sense.
- If I get the time I will probably look at doing a refactor PR at the very least on the UI code, repeating the module check for setting flash_utils stressed me out so I should probably move it to seperate function lol
How do i use just the checksum facility? I have a .bin which has various sections modified to support an immo off outside the cal area Most tools only checksum the cal area so when i write back the ecu gets stuck in bootloader. Is there anyway of using this to checksum to entire .bin? Thanks
CLI only.
python3 VW_Flash.py --action prepare --input_bin [inputbin] --output_bin [output bin dir]
On Sun, Jul 21, 2024 at 4:21 AM Golfather @.***> wrote:
How do i use just the checksum facility? I have a .bin which has various sections modified to support an immo off outside the cal area Most tools only checksum the cal area so when i write back the ecu gets stuck in bootloader. Is there anyway of using this to checksum to entire .bin? Thanks
— Reply to this email directly, view it on GitHub https://github.com/bri3d/VW_Flash/pull/130#issuecomment-2241541008, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWS7XYQVS2NDNLWCKB6MHLLZNN4SXAVCNFSM6AAAAABI4GWZTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGU2DCMBQHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
CLI only. python3 VW_Flash.py --action prepare --input_bin [inputbin] --output_bin [output bin dir] … On Sun, Jul 21, 2024 at 4:21 AM Golfather @.> wrote: How do i use just the checksum facility? I have a .bin which has various sections modified to support an immo off outside the cal area Most tools only checksum the cal area so when i write back the ecu gets stuck in bootloader. Is there anyway of using this to checksum to entire .bin? Thanks — Reply to this email directly, view it on GitHub <#130 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWS7XYQVS2NDNLWCKB6MHLLZNN4SXAVCNFSM6AAAAABI4GWZTKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGU2DCMBQHA . You are receiving this because you are subscribed to this thread.Message ID: @.>
Yes tried this option before but it moves and strips data from the ori boot read bin file as well. Just need something to ONLY perform checksums in all areas of the bin.
I think that having these features is better than not having them, goofiness aside. merged. I'll look at cleaning it up a little (I'd like to find a way to refactor the block handling for the Haldex stuff).