Segment Swap utility

They go by many names, P01, P59, VPW, '0411 etc . Circa 1999 to 2006. All VPW OBD2 PCMs.
User avatar
Posts: 153
Joined: Tue Dec 17, 2019 3:27 am

Re: Segment Swap utility

Postby joukoy » Tue Mar 31, 2020 10:32 pm

PcmBinBuilder 1.8.8
Added about-button

User avatar
Posts: 153
Joined: Tue Dec 17, 2019 3:27 am

Re: Segment Swap utility

Postby joukoy » Wed Apr 01, 2020 11:58 pm

0.9.12

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

Posts: 156
Joined: Sun Apr 10, 2016 9:20 pm

Re: Segment Swap utility

Postby kur4o » Thu Apr 02, 2020 12:30 am

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

User avatar
Posts: 153
Joined: Tue Dec 17, 2019 3:27 am

Re: Segment Swap utility

Postby joukoy » Thu Apr 02, 2020 1:58 am

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

User avatar
Posts: 153
Joined: Tue Dec 17, 2019 3:27 am

Re: Segment Swap utility

Postby joukoy » Fri Apr 03, 2020 1:11 am

0.9.14
Small bugfixes
Added cvn to File Info tab

Posts: 156
Joined: Sun Apr 10, 2016 9:20 pm

Re: Segment Swap utility

Postby kur4o » Fri Apr 03, 2020 7:11 pm

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

User avatar
Posts: 153
Joined: Tue Dec 17, 2019 3:27 am

Re: Segment Swap utility

Postby joukoy » Fri Apr 03, 2020 10:13 pm

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

Posts: 156
Joined: Sun Apr 10, 2016 9:20 pm

Re: Segment Swap utility

Postby kur4o » Fri Apr 03, 2020 11:00 pm

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.

User avatar
Posts: 153
Joined: Tue Dec 17, 2019 3:27 am

Re: Segment Swap utility

Postby joukoy » Sat Apr 04, 2020 12:46 am

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.

Posts: 156
Joined: Sun Apr 10, 2016 9:20 pm

Re: Segment Swap utility

Postby kur4o » Sat Apr 04, 2020 1:01 am

Code: Select all
Unsupported OS:  16266323
Autodetect: v6-98-05.xml

16266348.bin (v6-98-05.xml (v 1))

Unsupported OS:  16266348
Autodetect: v6-98-05.xml

16266368.bin (v6-98-05.xml (v 1))

Unsupported OS:  16266368
Autodetect: v6-98-05.xml

16266373.bin (v6-98-05.xml (v 1))

Unsupported OS:  16266373
Autodetect: v6-98-05.xml

16266375.bin (v6-98-05.xml (v 1))

Unsupported OS:  16266375
Autodetect: v6-98-05.xml


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

PreviousNext

Return to GM LS1 512Kbyte and 1Mbyte

Who is online

Users browsing this forum: Google [Bot] and 5 guests