|
Title: VAG MED17.5.2 problem. SOLVED Post by: guille_masco on September 20, 2012, 04:53:06 AM Hi to all, I have a little problem with a MED17.5.2 from a VAG 2.0TSI engine. The ecu is TP8, I read the file, did a .mod, wrote it, read again to see if the writing was good, and... The ecu still with the ORI file.
Then I took a look, and the sector where all maps are, appears as a OTP sector. The strange thing is that some local tuners tune this car. Using CMD, or Kess, even APR tune this car-ecu. Im using X17. magpro people told me that I cannot write on an OTP sector. But then, how can people tune this car?? here is a screenshot that shows the OTP sector on 1C0000h (http://imageshack.us/a/img155/1286/x17screenshot.png) Ori is attached Title: Re: VAG MED17.5.2 problem Post by: prj on September 20, 2012, 06:21:26 AM I do not have any experience with MED17, but if what you say is correct and the maps are indeed in OTP memory, then a way to tune a such car would be to move the maps around by redirecting the map reads to an empty space in the flash and copying the needed maps there.
Title: Re: VAG MED17.5.2 problem Post by: guille_masco on September 20, 2012, 08:41:24 AM i think the only way of doing that would be find all pointers in the software..
Title: Re: VAG MED17.5.2 problem Post by: k0mpresd on September 20, 2012, 08:44:23 AM uh what? your screen shot shows edc17cp46. but then you say you have an MED file.
Title: Re: VAG MED17.5.2 problem Post by: prj on September 20, 2012, 09:15:29 AM i think the only way of doing that would be find all pointers in the software.. Hardly all pointers, only those of the maps you want to tune I have done this plenty of times on older ECU's... But as I said - I don't know much about MEDC17, so maybe this approach is not needed at all here. Title: Re: VAG MED17.5.2 problem Post by: guille_masco on September 20, 2012, 09:22:37 AM uh what? your screen shot shows edc17cp46. but then you say you have an MED file. yes, sorry for that, i was trying differents protocols when i took the screenshot. but the ecu is a med17.5.2 tprot8 from a 2.0TSI Title: Re: VAG MED17.5.2 problem Post by: k0mpresd on September 22, 2012, 02:47:44 AM any updates?
Title: Re: VAG MED17.5.2 problem Post by: msundercober on September 22, 2012, 02:28:20 PM TP8 needs passwort read before. I do them with Byteshooter.
Title: Re: VAG MED17.5.2 problem Post by: k0mpresd on September 22, 2012, 03:41:32 PM TP8 needs passwort read before. I do them with Byteshooter. obviously. his question is not about reading. his question is about writing the section of flash that is shown to be not writable. Title: Re: VAG MED17.5.2 problem Post by: prj on September 22, 2012, 03:47:45 PM Something interesting perhaps:
https://www.facebook.com/permalink.php?story_fbid=10150992832129674&id=21996914673 (https://www.facebook.com/permalink.php?story_fbid=10150992832129674&id=21996914673) Quote OptiCan Debugger News: 1797 OTP TriCore with new possible areas for writing - OTP area can now be written. Write for example the whole ECU EEprom or for cloning the ECU. Manufacturer: all ECU Type: all Title: Re: VAG MED17.5.2 problem Post by: guille_masco on September 24, 2012, 08:17:08 PM Magpro people sent me a test firmware, I will report as soon as I have the car back.
Apart from this problem, people magpro is behaving very professionally, answering all my questions and developing very quickly. TC in this ecu is 1767 Title: Re: VAG MED17.5.2 problem Post by: k0mpresd on September 24, 2012, 10:18:30 PM Apart from this problem, people magpro is behaving very professionally, answering all my questions and developing very quickly. you must be dealing with a different magpro than the rest of us then. ::) Title: Re: VAG MED17.5.2 problem Post by: Gonzo on November 10, 2012, 02:40:55 PM Are you using WinOLS for checksum?
Your flashing tool should be able to skip the OTP sector since the checksum will match. Unless you are flashing a different file from another ECU. Title: Re: VAG MED17.5.2 problem Post by: guille_masco on November 10, 2012, 04:12:52 PM I do not understand...
They sent me a test firmware, to try to write OTP sector. But I coudnt try it. Im not correcting checksum with winols, Im hoping the tool to do it like it does always with others med17 Title: Re: VAG MED17.5.2 problem Post by: Rick on November 11, 2012, 09:57:59 AM Why couldn't you try it? Don't have the ECU?
Title: Re: VAG MED17.5.2 problem Post by: guille_masco on November 11, 2012, 02:25:08 PM I do not own one of those ecus, They cost over US $2000 in my country. So I have to make a friend/client come back.
One question.. Would I be able to read via bootloader one of this cars tuned by APR??? Regards! Title: Re: VAG MED17.5.2 problem Post by: atomiczen on November 26, 2012, 07:26:46 PM yes, but with a good flasher, not with a clone like magpro
Title: Re: VAG MED17.5.2 problem Post by: gremlin on December 05, 2012, 03:59:24 PM yes, sorry for that, i was trying differents protocols when i took the screenshot. but the ecu is a med17.5.2 tprot8 from a 2.0TSI This ECU-type (HW 06J907309x) has TC1767 with only one OTP zone ....010000-....017FFF So your problem is incorrectly operation of programmer tool or in using wrong protocol. Never have any problems with this ECU. Title: Re: VAG MED17.5.2 problem. SOLVED Post by: guille_masco on February 13, 2013, 11:20:25 AM Thank you very much guys you all!! especially Gremlin, that give me a consist answer. I took my time to reply this, becouse I want to try it first. And recently today I have the oportunity to try again. Togheter with MAGPRO people, we solve it. The problem was that MAGPRO was wrongly tagging the sector as OTP.
With new firmware, the problem is solved! Thanks people! (http://img705.imageshack.us/img705/8789/med1752.jpg) |