damage background pin

Started by Darren October 27, 2003

Hi All,

Has anyone else managed to kill a MC9S12DP256 by
connecting the BDM 6 way header backwards...?

I'm using the PE BDM Multilink interface and I'm
sure that this has killed the chip.

Darren Moore




Hi Darren.

Within many years of software development over HC12 and HCS12 series, this
happened a couple of times here, but no chip was damaged ever.
Could your chip be simply BDM locked/secured and erased at the same time
(=> no i/o pins activity)?

Regards,
Gilles At 09:47 AM 10/27/2003, you wrote:

>Hi All,
>
>Has anyone else managed to kill a MC9S12DP256 by
>connecting the BDM 6 way header backwards...?
>
>I'm using the PE BDM Multilink interface and I'm
>sure that this has killed the chip.
>
>Darren Moore >
>-------------------- >
>">http://docs.yahoo.com/info/terms/





--- In , "Darren" <djmoore@t...> wrote:
>
> Hi All,
>
> Has anyone else managed to kill a MC9S12DP256 by
> connecting the BDM 6 way header backwards...?
>
> I'm using the PE BDM Multilink interface and I'm
> sure that this has killed the chip.
>
> Darren Moore

I've plugged mine in backwards several times, and nothing bad has
happend. How ever forgetting to turn the power off on the board
before removing the BDM has resulted in a few chips that just
stopped working for me



Hi All,

Well judging by all the people here that had damaged
the device by plugging the BDM cable backwards (none)
I tried the new version of PE's unsecure program, it
looks like somehow the device had been secured and is
now ok.

It would be better if the Metrowerks True-Time Sim
would report that the device is secured :-(

Thanks,
Darren > -----Original Message-----
> From: Gilles Blanquin [mailto:] > Hi Darren.
>
> Within many years of software development over HC12 and HCS12
> series, this
> happened a couple of times here, but no chip was damaged ever.
> Could your chip be simply BDM locked/secured and erased at
> the same time
> (=> no i/o pins activity)?
>
> Regards,
> Gilles > At 09:47 AM 10/27/2003, you wrote:
>
> >Hi All,
> >
> >Has anyone else managed to kill a MC9S12DP256 by
> >connecting the BDM 6 way header backwards...?
> >
> >I'm using the PE BDM Multilink interface and I'm
> >sure that this has killed the chip.
> >
> >Darren Moore
> >
> >
> >
> >--------------------
> >
> >
> >
> >">http://docs.yahoo.com/info/terms/ > ------------------------
> Yahoo! Groups Sponsor ---------------------~-->
> Rent DVDs Online - Over 14,500 titles.
> No Late Fees & Free Shipping.
> Try Netflix for FREE!
> http://us.click.yahoo.com/vhSowB/XP.FAA/3jkFAA/dN_tlB/TM
> --------------------------
> -------~->
>
> -------------------- >
> ">http://docs.yahoo.com/info/terms/




At 11:45 PM 10/27/2003, you wrote:

>Hi All,
>
>Well judging by all the people here that had damaged
>the device by plugging the BDM cable backwards (none)
>I tried the new version of PE's unsecure program, it
>looks like somehow the device had been secured and is
>now ok.
>
>It would be better if the Metrowerks True-Time Sim
>would report that the device is secured :-(

Hi Darren,
directly copied from the debugger source code:

("Communication to the target failed \n(target MCU has no clock or wrong
BDM clock speed is used\nor derivative is secured!)")

I agree that the messagebox with this text could be displayed immediately,
but first a frequency search should be performed before declaring that the
chip is BDM locked/secured. Indeed, there is no way to make the difference
between a BDM communication speed problem, BDM secured device and a dead
device.

Regards,
Gilles >Thanks,
>Darren > > -----Original Message-----
> > From: Gilles Blanquin [mailto:]
> >
> >
> > Hi Darren.
> >
> > Within many years of software development over HC12 and HCS12
> > series, this
> > happened a couple of times here, but no chip was damaged ever.
> > Could your chip be simply BDM locked/secured and erased at
> > the same time
> > (=> no i/o pins activity)?
> >
> > Regards,
> > Gilles
> >
> >
> > At 09:47 AM 10/27/2003, you wrote:
> >
> > >Hi All,
> > >
> > >Has anyone else managed to kill a MC9S12DP256 by
> > >connecting the BDM 6 way header backwards...?
> > >
> > >I'm using the PE BDM Multilink interface and I'm
> > >sure that this has killed the chip.
> > >
> > >Darren Moore
> > >
> > >
> > >
> > >--------------------
> > >
> > >
> > >
> > >">http://docs.yahoo.com/info/terms/
> >
> >
> > ------------------------
> > Yahoo! Groups Sponsor ---------------------~-->
> > Rent DVDs Online - Over 14,500 titles.
> > No Late Fees & Free Shipping.
> > Try Netflix for FREE!
> > http://us.click.yahoo.com/vhSowB/XP.FAA/3jkFAA/dN_tlB/TM
> > --------------------------
> > -------~->
> >
> > --------------------
> >
> >
> >
> > ">http://docs.yahoo.com/info/terms/
> >
> >
>-------------------- >
>">http://docs.yahoo.com/info/terms/





Hi Gilles again,

Yes I did get that msg, guess once I get used to
this package it will be clear, today again at one
stage the device became locked, I had tried to
unsecure it before and that didn't help, now I have
P&E ver 1.3, it is unsecuring the part. Then I'm
up and running again.

Darren > -----Original Message-----
> From: Gilles Blanquin [mailto:]
>
> At 11:45 PM 10/27/2003, you wrote:
>
> >Hi All,
> >
> >Well judging by all the people here that had damaged
> >the device by plugging the BDM cable backwards (none)
> >I tried the new version of PE's unsecure program, it
> >looks like somehow the device had been secured and is
> >now ok.
> >
> >It would be better if the Metrowerks True-Time Sim
> >would report that the device is secured :-(
>
> Hi Darren,
> directly copied from the debugger source code:
>
> ("Communication to the target failed \n(target MCU has no
> clock or wrong
> BDM clock speed is used\nor derivative is secured!)")
>
> I agree that the messagebox with this text could be displayed
> immediately,
> but first a frequency search should be performed before
> declaring that the
> chip is BDM locked/secured. Indeed, there is no way to make
> the difference
> between a BDM communication speed problem, BDM secured device
> and a dead
> device.
>
> Regards,
> Gilles > >Thanks,
> >Darren
> >




Hi Gilles,

I happened to have a same problem as Darren except that I connected
the 6-way cable correctly. I was using the Codewarrior debugger and
tried to mass erase the flash, it was taking so long that i hit the
reset button on the debugger. It stopped and the chip was secured
(FSEC=$FF), so I tried unsecuring it using Codewarrior and that's
where i got a "Lost Communication" and from then on I could not
communicate with the chip. Whever I attempted communication, the
debugger would give an error of "BDM Speed Error"-->fail to establish
communication.
Did i kill my chip?? If not, is there a way to recover it? I
believe the chip is still in secured mode.

Thanks
Regards
Vivien
-- In , Gilles Blanquin <gblanquin@m...> wrote:
>
> Hi Darren.
>
> Within many years of software development over HC12 and HCS12
series, this
> happened a couple of times here, but no chip was damaged ever.
> Could your chip be simply BDM locked/secured and erased at the same
time
> (=> no i/o pins activity)?
>
> Regards,
> Gilles > At 09:47 AM 10/27/2003, you wrote:
>
> >Hi All,
> >
> >Has anyone else managed to kill a MC9S12DP256 by
> >connecting the BDM 6 way header backwards...?
> >
> >I'm using the PE BDM Multilink interface and I'm
> >sure that this has killed the chip.
> >
> >Darren Moore
> >
> >
> >
> >--------------------
> >
> >
> >
> >">http://docs.yahoo.com/info/terms/




Vivien,

I hadn't killed the chip as it turned out. It had just
become secure some how. I went and got the

"P&E Microcomputer Systems MC912 Unsecure_12 Program"

from P&E's web site www.pemicro.com, this fixed the problem.

Darren Moore > -----Original Message-----
> From: iewgnip [mailto:] > Hi Gilles,
>
> I happened to have a same problem as Darren except that I connected
> the 6-way cable correctly. I was using the Codewarrior debugger and
> tried to mass erase the flash, it was taking so long that i hit the
> reset button on the debugger. It stopped and the chip was secured
> (FSEC=$FF), so I tried unsecuring it using Codewarrior and that's
> where i got a "Lost Communication" and from then on I could not
> communicate with the chip. Whever I attempted communication, the
> debugger would give an error of "BDM Speed Error"-->fail to establish
> communication.
> Did i kill my chip?? If not, is there a way to recover it? I
> believe the chip is still in secured mode.
>
> Thanks
> Regards
> Vivien