pcmhacking.net

PcmBinBuilder 1.8.8
Added about-button

0.9.12

Separated file info reading and displaying.
As a side effect, it was easy to add file info -tab with csv saving

I did a quick test and ls1 extra info with the checkbox don`t work. Might got broke with the new file info tab.

kur4o wrote:I did a quick test and ls1 extra info with the checkbox don`t work. Might got broke with the new file info tab.

True.
Default values was missing, added in 0.9.13

0.9.14
Small bugfixes
Added cvn to File Info tab

I tested some features and some bugs popped up. The crc32 only prints 2 bytes, not sure if the other are missing or the calc is not done correctly.

The latest version somehow doesn`t handle errors very well. Older versions just prints out the error condition and continue on with the task but now we have semi crash conditions and all tasks are halted.
For example when a unsupported os is encountered.

edit:

Can we improve the printing of eeprom data something like this, [taken from ls1 special info]

kur4o wrote:I tested some features and some bugs popped up. The crc32 only prints 2 bytes, not sure if the other are missing or the calc is not done correctly.

The latest version somehow doesn`t handle errors very well. Older versions just prints out the error condition and continue on with the task but now we have semi crash conditions and all tasks are halted.
For example when a unsupported os is encountered.

edit:

Can we improve the printing of eeprom data something like this, [taken from ls1 special info]

Code: Select all

Eeprom_data [4000 - 8000]
 Hardware           12570558
 Serial                1CC0WNEH2218
 Id                     3154131286
 Id2                   12579403
 Broadcast          YCTJ
 PN                    12570558
 Ver                   YCTJ
 VIN                  1GCHC29U83E120616

Fixed in 0.9.15

Great work, now cvn32 is 4bytes but the first 2 are always 0000, It might be some calculation bug.

Can we add the unsupported v6 Os[upon bin info extraction] to the list automatically. So we can gather much more quickly the needed OS for defining.

kur4o wrote:Great work, now cvn32 is 4bytes but the first 2 are always 0000, It might be some calculation bug.

Can we add the unsupported v6 Os[upon bin info extraction] to the list automatically. So we can gather much more quickly the needed OS for defining.

If you define checksum saving address with 2 bytes, checksum is calculated with 2 bytes.
If this is not correct, please specify, how it should be defined.

What I mean when we encounter unsupported OS like the example, to add the OS number in the GM-v6.txt list for future reference.


I noticed that 4 bytes long checksums are displaying only the last 2 bytes in 0.9.16.

I suggest that the checksum count should be taken from the chechksum address field,
On display only checksum we can add some exception character like $:4:hex