|
ktm733
|
 |
« Reply #15 on: April 05, 2016, 08:10:28 PM »
|
|
|
Yep. I really wish the program was more user friendly... if I had time i'd make it a bit more smrts..
1) have it determine eeprom from id
2) add an option to try all (known) cs pins, possibly exhaustively, possibly with only known good chipid/cspin combinations.
I don't know how to do that? How would you do that? I actually tried doing it manual without the gui and still failed. Thanks for the quick reply also |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #16 on: April 05, 2016, 08:29:06 PM »
|
|
|
buy a programmer. problem solved.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #17 on: April 05, 2016, 08:39:06 PM »
|
|
|
I don't know how to do that? How would you do that? I actually tried doing it manual without the gui and still failed. Thanks for the quick reply also
What? I would modify the source code to autodetect for you. Not sure why you think the gui would help here. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #18 on: April 05, 2016, 08:40:03 PM »
|
|
|
Why haven't you tried
"ME7EEPROM.exe --bootmode 95080 --CSpin P4.7 -rp3 -b 10400 95080.bin" with the correct eeprom type yet?
|
|
|
|
|
Logged
|
|
|
|
|
ktm733
|
|
« Reply #19 on: April 05, 2016, 09:49:31 PM »
|
|
|
Why haven't you tried
"ME7EEPROM.exe --bootmode 95080 --CSpin P4.7 -rp3 -b 10400 95080.bin" with the correct eeprom type yet?
Just got home, time to test some things. Here are the results I get. The gui was to make sure I wasn't typing something incorrectly. C:\Users\Troy\Desktop>ME7EEPROM.exe --bootmode 95080 --CSpin P4.7 -rp3 -b 10400 95080.bin ME7_EEPROM v1.40 COM: 3, Baud Rate: 10400 Memory type: 95080, size: 1024 Chip Select pin: P4.7 Opening COM3 ... OK Starting Boot_mode ... uC ID response 0xD5 ... OK Sending Loader + MonitorCore ... MonitorCore successfully launched Reading IDCHIP ... 0x1143. Not supported FAIL. (error=0x11001) Closing COM3 |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #20 on: April 05, 2016, 10:03:56 PM »
|
|
|
ME7EEPROM.exe --bootmode 95080 --CSpin P4.7 -rp3 -b 10400 95080.bin As i already told you, 95080 is the wrong eeprom. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #21 on: April 05, 2016, 10:04:26 PM »
|
|
|
0x1143 is 95160 iirc
Are you really not figuring out what my earlier posts regarding detecting eeprom type from IdChip was all about? Are you actually reading any of the posts I'm making? |
|
|
|
« Last Edit: April 05, 2016, 10:06:45 PM by nyet »
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #22 on: April 05, 2016, 10:24:41 PM »
|
|
|
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #23 on: April 05, 2016, 10:27:32 PM »
|
|
|
SMH no kidding. I've been telling him to use 95160 from the very start, but for some reason he keeps ignoring my posts and babbling about other stuff.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #24 on: April 05, 2016, 10:28:27 PM »
|
|
|
I'm trying to read an 07 jetta eeprom but I dont know what chip is in there.
The tool shows 95040, 95080, 95160,and 95p08
I could go off of what people state about my ecu as it's 95p08 but I want to verify.
From the VERY first post, he's asking which eeprom type it is. |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #25 on: April 05, 2016, 10:32:54 PM »
|
|
|
SMH no kidding. I've been telling him to use 95160 from the very start, but for some reason he keeps ignoring my posts and babbling about other stuff.
did you read the post? lol. it said it would not work because of chipID. his post says he patched it to accept it. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #26 on: April 05, 2016, 10:42:03 PM »
|
|
|
did you read the post? lol. it said it would not work because of chipID. his post says he patched it to accept it.
He keeps using 95080 As i keep posting over and over: 0x1143 is 95160 iirc |
|
|
|
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #27 on: April 05, 2016, 10:49:41 PM »
|
|
|
V1.40 will not work no matter what's in the command line on that ecu.
|
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
|
k0mpresd
|
|
« Reply #28 on: April 05, 2016, 10:51:57 PM »
|
|
|
He keeps using 95080
As i keep posting over and over: 0x1143 is 95160 iirc
again though, did you read his post? he said it would not work originally. he said he patched it. i feel like the pot is meeting the kettle here. im guessing its because of st10 and not c167. |
|
|
|
|
Logged
|
|
|
|
|
vwaudiguy
|
|
« Reply #29 on: April 05, 2016, 10:53:01 PM »
|
|
|
im guessing its because of st10 and not c167.
Yes. I went through this a while back. |
|
|
|
|
Logged
|
"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
|
|
|
|
