Xprog distroys dashes ?

[bijlaard]

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]

Hi!
I can with 96% alcohol,look at the picture on my previous post.

[bijlaard]

I used nailpolish and a tooth brush
putted new new 9s12 on


nice regards
Ina
the Netherlands

[bijlaard]

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]

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]

I have same problem, i have org upa and clone x-prog, how shall i do with upa on mc9s12dg128b?

[alfy]

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...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]

you can now read/write flash of dash by obd using volvo commander by abrites.

[Nicko_d]

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]

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]

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-gui...2DT128DGV2.pdf page 73 this chip is 5V so no worries or damage chip.





mc9s12xxxxxxxxxxx.jpgmc9s12xxxxxxxxxxx2.jpgmc9s12xxxxxxxxxxx wires.jpg

[tehnosoftex]

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]

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]

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