View Full Version : Xprog distroys dashes ?
bijlaard
14th May, 2011, 08:48 AM
Hi all
I'm new here , a friend told me about this forum.
We have a Xprog (V5.0).
We want to use it for read and write flash in volvo dashes (2001 until 2010).
We did try to do about 8 of them, 4 of them are now dead :-(.
With dead I mean we get the message: Bootloader initialising error. Can't to acces BDM.Check BDM connection.
It hapens when we write the (new) flash, the first writing part is ok. After that it happens.
After that u can try to do it again but imidiatly it gives the bootloader error, so u can do nothing anymore.
http://www.varioclean.nl/error.jpg
the MCU's on the dashes are :MC9s12DG128B
We have the Xprog powered at 15 volts
we have 5 volts on the mcu
Does anyone know why this happens ?
We tryed to bring the dash to live putting 12 volts on the dash itselve ,didn't help.
Does anyone know how to get the dead dashes to work again?
I don't have to tell it's very very important to get them to work again.....
Hope we are at the right community here :-)
regards Ina
pepi
14th May, 2011, 09:49 AM
Try to use other programmer like ETL or Rosfar. Probably you have destroyd flash data on MCU.
bijlaard
14th May, 2011, 10:09 AM
Is this a known problem from the xprog ?
and wil the ETL or Rosfar not have this problem?
exe123
14th May, 2011, 10:53 AM
try to select secured version of the 9s12. maybe bdm protection is active now
bijlaard
14th May, 2011, 11:12 AM
Did try that allready no luck :-(
bijlaard
14th May, 2011, 11:59 AM
Maybe aditional info, don't know if it is of any use :
The ones who worked, it seems (for us) those where only programmed one time. (we did only flash)
The others we did, (the dead/locked ones) first time they functioned, second (writing) time we got the error. (we did only flash)
does somebody know the answer ?
forumams
14th May, 2011, 07:50 PM
Is this a known problem from the xprog ?
and wil the ETL or Rosfar not have this problem?
yes, if the xprog v5.0 cheap china clone.
bijlaard
14th May, 2011, 10:39 PM
Yes it's a china tool,....
When i would buy a ETL or Rosfar would i beable to repair the MCU's ?
mastaflex
14th May, 2011, 10:53 PM
i don't know if i understand well, do you work on volvo for odometer correction or something other? if you work on odometer correction, why do you touch FLASH?
bijlaard
14th May, 2011, 11:30 PM
We try to change language
grinovsky
14th May, 2011, 11:32 PM
MC9s12DG128B must be powred only by 3.3v,
the 5v will distroy the chip
wsc
14th May, 2011, 11:40 PM
I had a similar problem with 9S12B128 flash mask 3L80R mask.
Every time, the BCU that i read was dead and i had no communication with the board
maybe there is problem with this value
PS:i have OIGINAL Xprog-m
wsc
14th May, 2011, 11:44 PM
MC9s12DG128B must be powred only by 3.3v,
the 5v will distroy the chip
OK mate but how we ll set 3,3V in Xprog-m ???
grinovsky
14th May, 2011, 11:55 PM
so easy,make resistor between Vdd and Vddr to get 3.3v
and long life for you chip
wsc
14th May, 2011, 11:59 PM
i will try and report mate,then we ll see if u are right
:D
tachonow
15th May, 2011, 12:04 AM
I read this mcu with UPA at 5V power delivered by programmer and never fails.
wsc
15th May, 2011, 12:11 AM
Yes but in my case the UPA can not read 3L80R secured
bijlaard
15th May, 2011, 12:41 AM
MC9s12DG128B must be powred only by 3.3v,
the 5v will distroy the chip
I just puttet 5 volts on the original input from the dash and slowy made it go to 13,8 volts.
at 6,5 volts the chip had 5,0 volts , it stayed 5,0 volts until the 13,8 was reached.
I did not test what would happen at 20 volts .....:-)
So I think my chip(s) need 5 volt.
So bad,( for me):( it's not the solution to my problems :(
any other suggestions ?
grinovsky
15th May, 2011, 07:33 AM
this is you chip
kareszka
15th May, 2011, 11:51 AM
Hi!
I read same mcu with x-prog_m ver.4.5 on volvo v70 2007 dash.
Last year I dont have problem my x-prog.(I use with micronas , mpc , secured mcu...)
bijlaard
15th May, 2011, 01:05 PM
this is you chip
Sorry for maybe stupid questions,
When I leave gnd on the dash and give the + an external 3,3 volts would that work ?
grinovsky
15th May, 2011, 02:09 PM
yes ,work fine
gadroulll
15th May, 2011, 06:45 PM
i never use power supply to xprog . usb can reach the 5 v and also 9 volts .
exe123
15th May, 2011, 06:58 PM
MC9s12DG128B must be powred only by 3.3v,
the 5v will distroy the chip
That's not true. Read datasheet. 9S12DG128B works with 5V
grinovsky
15th May, 2011, 07:04 PM
no,read the thread and you will find that this guy have distroy 50% of his chips by using 5v
but if you can give to us other reason!!!
exe123
15th May, 2011, 07:12 PM
no,read the thread and you will find that this guy have distroy 50% of his chips by using 5v
but if you can give to us other reason!!!
That is just bullshit. I read/write several 912, 9S12 and 9S12X
they all work with 5V. Just read datasheet and you will see it.
Possible reasons could be everything starting by bad xprog clone, activated security which results in locked bdm port.
first step solder coax wire and check if xprog-m works with 9s12 secured option. in this case it should bypass security and connect to it.
second step is desolder mcu and read with xprog using parallel programming.
micromax
15th May, 2011, 07:14 PM
Vcc out from xprog is regulated 0-5V. if you kill motorola maybe you select wrong device and xprog not regulated corectly Vcc? or your xprog is faulty.
additional resistor to vcc is unnecessary.
bijlaard
15th May, 2011, 08:24 PM
We did measure the volts it is 5 volts that comes out of the Xprog.
We selected MC(s)12 and then the MC9S12-Flash
What do u mean with :
solder coax wire ,..where should we do what ? :-)
(we are real newbees , sorry) do u have a picture of what we should do ?
and what do u mean with parallel programming ? Thnx
greetings Ina and Obbe (beginners from the Netherlands)
exe123
15th May, 2011, 10:55 PM
Select Motorola HC(S)12-secured -> MC9S12-FLASH-secured.
Click show connection diagram. then you will see that it needs to additonal wires (coax signal + gnd for shielding)
extal has to be connected to the oscillator pin. the other one to gnd.
bijlaard
15th May, 2011, 11:09 PM
ok wil try that
bijlaard
18th May, 2011, 11:36 PM
any simple way to get rid of the blue stuff what's on the MCU ?
(sorry we are beginners in this world.) :-)
We tryed thinner, heating, brushing
there shouldbe a better way to remove this blue plastic arround this MCU.
thnx for any help
regards Ina and Obbe
kareszka
19th May, 2011, 06:43 PM
Hi!
I can with 96% alcohol,look at the picture on my previous post.
bijlaard
19th May, 2011, 10:57 PM
I used nailpolish and a tooth brush
putted new new 9s12 on
nice regards
Ina
the Netherlands
bijlaard
19th May, 2011, 11:06 PM
Should we do something before going to write eeprom and then flash to new 9s12 ?
open it ? or whatever ???
update;
I read flash from new 9s12 ok
I write old flash to new 9s12 proccesor
after writing ,we get initialising error ,cannot connect to bootloader bla la
back beginning of threat.................
I don't understand..........
greetings
Ina
Holland
bijlaard
22nd May, 2011, 02:13 PM
Select Motorola HC(S)12-secured -> MC9S12-FLASH-secured.
Click show connection diagram. then you will see that it needs to additonal wires (coax signal + gnd for shielding)
extal has to be connected to the oscillator pin. the other one to gnd.
the external and gnd are only on the pictures for the 256 version, they are not on the pictures about the HC9(s)12DG 128B.
We really think our (china) xprog is not good, we are getting a new one from this firm,
We ordered a ETL ( drpeter gave a link to us) hopefully that is going to work.
In the mean time we have to get these chips (2 remaining) programmed, doe anybody know if this is possible with the gold programmer and how to do that ?
greetings
alfons37
29th December, 2011, 12:39 PM
I have same problem, i have org upa and clone x-prog, how shall i do with upa on mc9s12dg128b?
alfy
29th December, 2011, 01:22 PM
Is this a known problem from the xprog ?
and wil the ETL or Rosfar not have this problem?
Hi!
Look your at your board and see if you too have this diode broken:
http://www.digital-kaos.co.uk/forums/f172/xprog-m-help-238219/
Also on mine was, so when program raise Vcc to 8,5V and than drops on 5V even if powered only by USB!
raedareeg
11th February, 2012, 11:28 AM
you can now read/write flash of dash by obd using volvo commander by abrites.
Nicko_d
14th March, 2012, 10:07 PM
They already use SMOK till thouse problem...
Realy, problem was with 5V power, I always use 3,5v and have never had any dead chip!!!!
Was any repair from colegue, which use 5V, I jast changed chip and became all ok.
gadroulll
5th March, 2013, 04:18 PM
i believe that when you program flash with xprogm the processor change state of locking . the etl suggest that you must do it together flash and eeprom that our xprogm cannot do it.
so is better if you use secured state processor and make flash then you must check if your processor works in unsecured state.
if xprogm make it unsecured then you must go to the apropiate adress and lock the bdm.
can someone check that i write?
pocinas
28th July, 2018, 02:19 PM
Hi There. I know is old topic but maybe my writes helps someone to the future.
So i have the same situation what owner from 1st post, but my processor is MC9S12H256VFVE the reason period broke proccesor was XPROG with firmware 5.7.4 which read / write/verification wrong, when i read flash i not check verification, i just moded file and write and after this my dash was dead, proccesor not respond to initialization and the same infos like Bootloader initialising error. Can't to acces BDM.Check BDM connection.
so after couple od hours spend time i downgrade my xprog to version 5.5.1 which write, verification and read correct. but still can`t wake up dash, still was "Bootloader initialising error. Can't to acces BDM.Check BDM connection."
so only way was use adapter 1-002-0017 BDM ADAPTER and solder 2 more wires like GND and EXTAL (14cm which i twist) look 3rd photo from xprog software i used option "HC(S)12-secured (look photos) after that communication with processor BACK.
Schematic to connection HC9S12H256...128B is the same (look 2nd photo), the same everythink... when is initialization chip (before read, write, Verification) software (xprog) recognize alone model processor
check datasheet https://www.nxp.com/docs/en/user-guide/9S12DT128DGV2.pdf page 73 this chip is 5V so no worries or damage chip.
545266545267545269
tehnosoftex
5th August, 2018, 03:40 PM
I think the xprog which wrote wrong in flash locked the mcu because the locking mechanism is in flash, that s why it is not possible to access anymore the bootloader.
pocinas
10th August, 2018, 12:49 PM
I think the xprog which wrote wrong in flash locked the mcu because the locking mechanism is in flash, that s why it is not possible to access anymore the bootloader.Hmmm.. i not will say right or not. In.my situation when i wrote wrong flash xprog have problem with rwcognize/ ID chip (was soldered 4 wires) and botloader is not recognized..... bla bla bla..
Only option to wake up was connect another 2 wires, EXTAL which i twist with another GND like in instruction and disconnected one pin from cluster quartz and using adapter 1-002-0017 BDM.. in xprog then i used diffrent position with name SECURED mc9s12 secured. on the support list... after this chip was recognized correct, as well not have problem with flashing correct file. After flashing when i back to option with 4 wires without adapter than xprog recognize again my chip.
ricked
26th November, 2022, 08:56 PM
Hmmm.. i not will say right or not. In.my situation when i wrote wrong flash xprog have problem with rwcognize/ ID chip (was soldered 4 wires) and botloader is not recognized..... bla bla bla..
Only option to wake up was connect another 2 wires, EXTAL which i twist with another GND like in instruction and disconnected one pin from cluster quartz and using adapter 1-002-0017 BDM.. in xprog then i used diffrent position with name SECURED mc9s12 secured. on the support list... after this chip was recognized correct, as well not have problem with flashing correct file. After flashing when i back to option with 4 wires without adapter than xprog recognize again my chip.
here is bla bla... locking mechanism is in MCU it self not flash, only way to get the MCU out of this is indeed secure/bypass security then you have it back again
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.