[Matthew53]

I guess your endgoal is to add the GPS to the headunit. Let me know how it goes. As i saw from your adjblock you're trying with the whole chip, not with the G7 one.

Yep. Have a variety of LEA-* modules. LEA-M8S wouldn't even let the evo turn on. Put the most common LEA-6R on at the moment. powered on at least.

The eeprom chip needs to be replaced, and I'm still not entirely sure why, or why it has to be new. I'm not sure if I'm supposed to clone the current one, or it'll write to it whatever it needs. I think it has some write-once functionality on certain blocks based on the datasheet, so maybe that's why it needs to be replaced... That's the next thing to swap.

What do you mean by "the G7 one"?

There are two value types for GPS - 1 - verbaut[CRLF], 2 - G7. Apparently G7 is the other kind of GPS module

NBT_AdjBlock_Jacinto.txt
File Type:
Downloaded:	71 times
Size:	24.26 KB

[RomeyRome]

There are two value types for GPS - 1 - verbaut[CRLF], 2 - G7. Apparently G7 is the other kind of GPS module

Oh weird. I have looked at that file many times and never noticed the second option. But I have never even seen what that hardware would look like.

[RomeyRome]

Swapped eeprom for a brand new one.

Unit booted into bootloader
Switched it into app mode.
EEPROM was still blank.
CAFD was gone in esys.
Coded cafd, stuff got written to eeprom.
Did some GPS FDL coding, some stuff changed in eeprom.

Still don't seem to be getting a gps signal. I'm just testing through tool32.

Like I said, I don't know the point of changing eeprom is, but I'm doing it. lol

sysetV850io only dumps 5k. It's a 64k chip, so I don't know what the rest of it is.

[m5proud]

here is your original eeprom with gps activated. But in your file checksumm was not correct, so i don't know if modified would be correct

---

here is your original eeprom with gps activated. But in your file checksumm was not correct, so i don't know if modified would be correct

[Matthew53]

That's interesting. In my case sysetV850io dump only 2k. Maybe it depend where syset is copied on the HU?

sysetV850io_dump_adjust_0_1792209003.bin.txt
File Type:
Downloaded:	7 times
Size:	1.99 KB

[walkernight88]

Swapped eeprom for a brand new one.

Unit booted into bootloader
Switched it into app mode.
EEPROM was still blank.
CAFD was gone in esys.
Coded cafd, stuff got written to eeprom.
Did some GPS FDL coding, some stuff changed in eeprom.

Still don't seem to be getting a gps signal. I'm just testing through tool32.

Like I said, I don't know the point of changing eeprom is, but I'm doing it. lol

sysetV850io only dumps 5k. It's a 64k chip, so I don't know what the rest of it is.

95640 -> 64kilobits -> 8KB. 

Here's a complete dump from mine without GPS from 95640. Or what have you dumped?


"Matthew53
That's interesting. In my case sysetV850io dump only 2k. Maybe it depend where syset is copied on the HU?"

Adjustblock is 2036bytes. So it's correct. He's talking about an eeprom...

[RomeyRome]

Swapped eeprom for a brand new one.

Unit booted into bootloader
Switched it into app mode.
EEPROM was still blank.
CAFD was gone in esys.
Coded cafd, stuff got written to eeprom.
Did some GPS FDL coding, some stuff changed in eeprom.

Still don't seem to be getting a gps signal. I'm just testing through tool32.

Like I said, I don't know the point of changing eeprom is, but I'm doing it. lol

sysetV850io only dumps 5k. It's a 64k chip, so I don't know what the rest of it is.

95640 -> 64kilobits -> 8KB. 

Here's a complete dump from mine without GPS from 95640. Or what have you dumped?

Right. I was thinking kBytes, not bits.

How do you get 8k? sysetV850io --eeprom --dump only gives me 5k on old and new 95640s.

I have various 95640s to play with. This particular one is 95640-DWDW4TP/K.
I guess I could solder up o it and read it with external tools,

[RomeyRome]

here is your original eeprom with gps activated. But in your file checksumm was not correct, so i don't know if modified would be correct

How would it get the wrong checksum? I have not edited the eeprom manually. Only through esys.

[Matthew53]

@walkernight88 Ok, it makes sense. I read 95640 with VVDI. So as I understand GPS need to be enabled in eeprom as well as in adjustblock?

95640_EEPROM_nbt_evo_ID4_without_GPS.bin.txt
File Type:
Downloaded:	9 times
Size:	8 KB

[RomeyRome]

@walkernight88 Ok, it makes sense. I read 95640 with VVDI. So as I understand GPS need to be enabled in eeprom as well as in adjustblock?

Someone correct me if I’m wrong, but it seems like eeprom is just fdl coding data…? I just don’t understand why the chip needs to be replaced to enable gps, but it does.