> I wonder if, an issue that used to be a problem with Flash, of over > programming occurs? I would agree with that except that I know how my boards are programmed and it is not over Flashing. Nicholas symptomatic board problem tells me it was zapped. He went thru a test process that I usually do my with boards before the last resort of removing and replacind MCUs. I am not 100% certain that is the problem with Nicholas' board but with experience you get know these things :-))) --- In 68HC12@68HC..., Andrew Lohmann <andrew.lohmann@b...> wrote: > Hi > I wonder if, an issue that used to be a problem with Flash, of over > programming occurs? In a discussion a long time back I'm sure it was > said that this issue does not now arise. When we have programmed Intel > flash on our programmer in the past I recall that sometimes the flash > won't program unless you take it out of the programmer socket and put it > back again latter. > > I have had a similar experience with two MC9S12DP256B targets, where my > P&E USB BDM interface's unreliability got so bad that it appears to have > corrupted the micro. Unsecure always reported that the device was not > secured. I switched to using a P&E parallel cable and the BDM > programming became completely reliable. But It took a number of attempts > before the two target boards recovered, I was going to have the > processors taken off and replaced, but one more try and they came back > to life and have stayed fine for the past month or so. > > I tried perusing P&E about the USB Multilink12 problem and also where to > get the firmware upload utility for ubmbdmens.510, as the firmware I > have is version 5.09 to no avail. It may be that USB multilink12 Rev.B > is ok, the the parallel version with the patch if you are using XpPro > certainly is excellent. I use Cosmic Zap for debugging and programming > which is a nice tool to use, but does not really have a bearing on the > discussion. > Andrew Lohmann AMIIE > Design Engineer > > > zeta_alpha2002 wrote: > > > > > > I'm just as curious to know what happened as you are. > > > > Not an uncommon thing to happen. A lot of my boards get handled by > > many people. Static Zap is mostly the culprit. Main symptom get > > reported to me as "can't program any longer". If it used to work and > > now won't and certain things were check then the MCU gets removed and > > replace. > >

Hi I wonder if, an issue that used to be a problem with Flash, of over programming occurs? In a discussion a long time back I'm sure it was said that this issue does not now arise. When we have programmed Intel flash on our programmer in the past I recall that sometimes the flash won't program unless you take it out of the programmer socket and put it back again latter. I have had a similar experience with two MC9S12DP256B targets, where my P&E USB BDM interface's unreliability got so bad that it appears to have corrupted the micro. Unsecure always reported that the device was not secured. I switched to using a P&E parallel cable and the BDM programming became completely reliable. But It took a number of attempts before the two target boards recovered, I was going to have the processors taken off and replaced, but one more try and they came back to life and have stayed fine for the past month or so. I tried perusing P&E about the USB Multilink12 problem and also where to get the firmware upload utility for ubmbdmens.510, as the firmware I have is version 5.09 to no avail. It may be that USB multilink12 Rev.B is ok, the the parallel version with the patch if you are using XpPro certainly is excellent. I use Cosmic Zap for debugging and programming which is a nice tool to use, but does not really have a bearing on the discussion. Andrew Lohmann AMIIE Design Engineer zeta_alpha2002 wrote: > > > I'm just as curious to know what happened as you are. > > Not an uncommon thing to happen. A lot of my boards get handled by > many people. Static Zap is mostly the culprit. Main symptom get > reported to me as "can't program any longer". If it used to work and > now won't and certain things were check then the MCU gets removed and > replace. > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > > > Hi Edward, > > > > I have checked all the signals on the pins of the micro, so I don't > > think its a soldering problem. I also check continuity between BDM > > connector and the pins of the micro, and they're all good. > > > > Yes. ECLK is going with or without the BDM cable connected. > > > > Just checked VDD1/2 aswell. Both of them just have a cap to VSS1/2. > > So I don't think thats the problem either. > > > > I'm just as curious to know what happened as you are. > > > > Thanks for the suggestions > > Nicholas > > > > --- In 68HC12@68HC..., "Edward Karpicz" <karpicz@a...> wrote: > > > What about bad soldering? Did you check RESET and BKGD by probing > > them > > > straight at MCU pins? > > > > > > Hm, ECLK output is enabled. If software you flashed to the chip > > last time > > > isn't writing to PEAR.NECLK bit to enable ECLK, and MODA and MODB > > pins are > > > set for single chip operation (MODA=MODB=0) then it looks like part > > enters > > > special single chip mode (BKGD=0 on reset). Do you see ECLK output > > even with > > > BDM cable disconnected? If so then either BKGD pin is all the time > > at 0V and > > > you should double check soldering, or pin is wired to BDM connector > > but > > > there's no mo wire from pin to die... > > > > > > Also, if I remember correctly there was someone on the list who > > wired VDD1 > > > and VDD2 to 5V, and BDM communication was working for a while... If > > it's not > > > the case then I'm curious how did you fry your 9S12. > > > > > > Edward > > > > > > ----- Original Message ----- > > > From: "pickleza" <pickleza@y...> > > > To: <68HC12@68HC...> > > > Sent: Thursday, April 07, 2005 6:04 PM > > > Subject: [68HC12] Re: BDM Not Working > > > > > > > > > > > > > > > > > > Yip. The RESET line is fine. > > > > > > > > 1. Can't unsecure. Unsecure programs can't communicate. > > > > 2. BDM BKGD line is working. There is traffic on the pin, but it > > > > looks like there's no reply. > > > > 3. Oscillator is working. It is buffered on ECLK. > > > > 4. Reset line is good. Comes down for 200ms or so, then back up. > > > > > > > > Nicholas > > > > > > > > --- In 68HC12@68HC..., "zeta_alpha2002" > > <zeta_alpha2002@y...> > > > > wrote: > > > >> > > > >> Your tried and check > > > >> 1. unsecure > > > >> 2. BDM line > > > >> 3. Oscillator is oscillating/ > > > >> 4. If RESET is okay then > > > >> > > > >> Bad MCU, it got sick and fried. > > > >> > > > >> > > > >> > > > >> --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > > >> > > > > >> > I thought it might be the oscillator, so thats what I checked > > > > first. > > > >> > There is clock coming out of the ECLK, so I think the > > oscillator > > > > is > > > >> > working. > > > >> > > > > >> > I will check the RESET line and let you know what I find. > > > >> > > > > >> > Thanks > > > >> > Nicholas > > > >> > > > > >> > --- In 68HC12@68HC..., "zeta_alpha2002" > > > > <zeta_alpha2002@y...> > > > >> > wrote: > > > >> > > > > > >> > > Symptom suggest a reset problem. Check the reset line or the > > > >> > > oscillator not ticking. > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> > > wrote: > > > >> > > > > > > >> > > > I have checked the BDM connections. I checked for traffic > > on > > > > the > > > >> > BKGD > > > >> > > > pin, and its there. > > > >> > > > > > > >> > > > Power is on. All the lights are on. I am using a PC power > > > > supply > > > >> > > > through a LM317 regulator, so there shouldn't be any > > problems > > > >> > with > > > >> > > > current. I measured the current going to the chip somewhere > > > > round > > > >> > > > 50mA when running normally. What does it get up to? > > > >> > > > > > > >> > > > The thing that makes me think the pin is at fault is that > > it > > > >> > worked > > > >> > > > before, then suddenly stopped. Also none of the programs > > are > > > > able > > > >> > to > > > >> > > > detect the clock speed of the chip. > > > >> > > > > > > >> > > > Is there a way to test the pin? Is there traffic on the pin > > > > when > > > >> > the > > > >> > > > BDM programmer is disconnected? > > > >> > > > > > > >> > > > Nicholas > > > >> > > > > > > >> > > > --- In 68HC12@68HC..., "a_ribero" <a_ribero@y...> > > > > wrote: > > > >> > > > > > > > >> > > > > Hi Nicholas: > > > >> > > > > > > > >> > > > > Did you double ckeck the BDM connections. If you 6-pin > > > >> > connector is > > > >> > > > > not connected properly, the BDM box won't be able to > > > >> > communicate to > > > >> > > > > the board. > > > >> > > > > > > > >> > > > > And just to be sure, is the power supply on? Sometimes > > you > > > > have > > > >> > to > > > >> > > > go > > > >> > > > > to the basics... > > > >> > > > > > > > >> > > > > Do you use a Lab power supply? If so, check that the > > current > > > >> > > > > limitation is not too low. Otherwise, there is not enough > > > >> > current to > > > >> > > > > power up the board, therefore, no programming can happen. > > > >> > > > > > > > >> > > > > I would the BKDG pin as the last suspect. Most of the > > time > > > >> > there are > > > >> > > > > other problems that prevent the programming. > > > >> > > > > > > > >> > > > > Regards, > > > >> > > > > > > > >> > > > > Alex > > > > > > > > > > > > > > > > > > > > > > > > > > > > >. -----------------------------Disclaimer----------------------------- This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the addressee. If you are not the addressee please note that any distribution, reproduction, copying, publication or use of this communication or the information is prohibited. If you have received this communication in error, please contact us immediately and also delete the communication from your computer. We accept no liability for any loss or damage suffered by any person arising from use of this e-mail. -----------------------------Disclaimer-----------------------------

> I'm just as curious to know what happened as you are. Not an uncommon thing to happen. A lot of my boards get handled by many people. Static Zap is mostly the culprit. Main symptom get reported to me as "can't program any longer". If it used to work and now won't and certain things were check then the MCU gets removed and replace. --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > Hi Edward, > > I have checked all the signals on the pins of the micro, so I don't > think its a soldering problem. I also check continuity between BDM > connector and the pins of the micro, and they're all good. > > Yes. ECLK is going with or without the BDM cable connected. > > Just checked VDD1/2 aswell. Both of them just have a cap to VSS1/2. > So I don't think thats the problem either. > > I'm just as curious to know what happened as you are. > > Thanks for the suggestions > Nicholas > > --- In 68HC12@68HC..., "Edward Karpicz" <karpicz@a...> wrote: > > What about bad soldering? Did you check RESET and BKGD by probing > them > > straight at MCU pins? > > > > Hm, ECLK output is enabled. If software you flashed to the chip > last time > > isn't writing to PEAR.NECLK bit to enable ECLK, and MODA and MODB > pins are > > set for single chip operation (MODA=MODB=0) then it looks like part > enters > > special single chip mode (BKGD=0 on reset). Do you see ECLK output > even with > > BDM cable disconnected? If so then either BKGD pin is all the time > at 0V and > > you should double check soldering, or pin is wired to BDM connector > but > > there's no mo wire from pin to die... > > > > Also, if I remember correctly there was someone on the list who > wired VDD1 > > and VDD2 to 5V, and BDM communication was working for a while... If > it's not > > the case then I'm curious how did you fry your 9S12. > > > > Edward > > > > ----- Original Message ----- > > From: "pickleza" <pickleza@y...> > > To: <68HC12@68HC...> > > Sent: Thursday, April 07, 2005 6:04 PM > > Subject: [68HC12] Re: BDM Not Working > > > > > > > > > > > > > Yip. The RESET line is fine. > > > > > > 1. Can't unsecure. Unsecure programs can't communicate. > > > 2. BDM BKGD line is working. There is traffic on the pin, but it > > > looks like there's no reply. > > > 3. Oscillator is working. It is buffered on ECLK. > > > 4. Reset line is good. Comes down for 200ms or so, then back up. > > > > > > Nicholas > > > > > > --- In 68HC12@68HC..., "zeta_alpha2002" > <zeta_alpha2002@y...> > > > wrote: > > >> > > >> Your tried and check > > >> 1. unsecure > > >> 2. BDM line > > >> 3. Oscillator is oscillating/ > > >> 4. If RESET is okay then > > >> > > >> Bad MCU, it got sick and fried. > > >> > > >> > > >> > > >> --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > >> > > > >> > I thought it might be the oscillator, so thats what I checked > > > first. > > >> > There is clock coming out of the ECLK, so I think the > oscillator > > > is > > >> > working. > > >> > > > >> > I will check the RESET line and let you know what I find. > > >> > > > >> > Thanks > > >> > Nicholas > > >> > > > >> > --- In 68HC12@68HC..., "zeta_alpha2002" > > > <zeta_alpha2002@y...> > > >> > wrote: > > >> > > > > >> > > Symptom suggest a reset problem. Check the reset line or the > > >> > > oscillator not ticking. > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> > wrote: > > >> > > > > > >> > > > I have checked the BDM connections. I checked for traffic > on > > > the > > >> > BKGD > > >> > > > pin, and its there. > > >> > > > > > >> > > > Power is on. All the lights are on. I am using a PC power > > > supply > > >> > > > through a LM317 regulator, so there shouldn't be any > problems > > >> > with > > >> > > > current. I measured the current going to the chip somewhere > > > round > > >> > > > 50mA when running normally. What does it get up to? > > >> > > > > > >> > > > The thing that makes me think the pin is at fault is that > it > > >> > worked > > >> > > > before, then suddenly stopped. Also none of the programs > are > > > able > > >> > to > > >> > > > detect the clock speed of the chip. > > >> > > > > > >> > > > Is there a way to test the pin? Is there traffic on the pin > > > when > > >> > the > > >> > > > BDM programmer is disconnected? > > >> > > > > > >> > > > Nicholas > > >> > > > > > >> > > > --- In 68HC12@68HC..., "a_ribero" <a_ribero@y...> > > > wrote: > > >> > > > > > > >> > > > > Hi Nicholas: > > >> > > > > > > >> > > > > Did you double ckeck the BDM connections. If you 6-pin > > >> > connector is > > >> > > > > not connected properly, the BDM box won't be able to > > >> > communicate to > > >> > > > > the board. > > >> > > > > > > >> > > > > And just to be sure, is the power supply on? Sometimes > you > > > have > > >> > to > > >> > > > go > > >> > > > > to the basics... > > >> > > > > > > >> > > > > Do you use a Lab power supply? If so, check that the > current > > >> > > > > limitation is not too low. Otherwise, there is not enough > > >> > current to > > >> > > > > power up the board, therefore, no programming can happen. > > >> > > > > > > >> > > > > I would the BKDG pin as the last suspect. Most of the > time > > >> > there are > > >> > > > > other problems that prevent the programming. > > >> > > > > > > >> > > > > Regards, > > >> > > > > > > >> > > > > Alex > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > >

Hi Edward, I have checked all the signals on the pins of the micro, so I don't think its a soldering problem. I also check continuity between BDM connector and the pins of the micro, and they're all good. Yes. ECLK is going with or without the BDM cable connected. Just checked VDD1/2 aswell. Both of them just have a cap to VSS1/2. So I don't think thats the problem either. I'm just as curious to know what happened as you are. Thanks for the suggestions Nicholas --- In 68HC12@68HC..., "Edward Karpicz" <karpicz@a...> wrote: > What about bad soldering? Did you check RESET and BKGD by probing them > straight at MCU pins? > > Hm, ECLK output is enabled. If software you flashed to the chip last time > isn't writing to PEAR.NECLK bit to enable ECLK, and MODA and MODB pins are > set for single chip operation (MODA=MODB=0) then it looks like part enters > special single chip mode (BKGD=0 on reset). Do you see ECLK output even with > BDM cable disconnected? If so then either BKGD pin is all the time at 0V and > you should double check soldering, or pin is wired to BDM connector but > there's no mo wire from pin to die... > > Also, if I remember correctly there was someone on the list who wired VDD1 > and VDD2 to 5V, and BDM communication was working for a while... If it's not > the case then I'm curious how did you fry your 9S12. > > Edward > > ----- Original Message ----- > From: "pickleza" <pickleza@y...> > To: <68HC12@68HC...> > Sent: Thursday, April 07, 2005 6:04 PM > Subject: [68HC12] Re: BDM Not Working > > > > > > Yip. The RESET line is fine. > > > > 1. Can't unsecure. Unsecure programs can't communicate. > > 2. BDM BKGD line is working. There is traffic on the pin, but it > > looks like there's no reply. > > 3. Oscillator is working. It is buffered on ECLK. > > 4. Reset line is good. Comes down for 200ms or so, then back up. > > > > Nicholas > > > > --- In 68HC12@68HC..., "zeta_alpha2002" <zeta_alpha2002@y...> > > wrote: > >> > >> Your tried and check > >> 1. unsecure > >> 2. BDM line > >> 3. Oscillator is oscillating/ > >> 4. If RESET is okay then > >> > >> Bad MCU, it got sick and fried. > >> > >> > >> > >> --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > >> > > >> > I thought it might be the oscillator, so thats what I checked > > first. > >> > There is clock coming out of the ECLK, so I think the oscillator > > is > >> > working. > >> > > >> > I will check the RESET line and let you know what I find. > >> > > >> > Thanks > >> > Nicholas > >> > > >> > --- In 68HC12@68HC..., "zeta_alpha2002" > > <zeta_alpha2002@y...> > >> > wrote: > >> > > > >> > > Symptom suggest a reset problem. Check the reset line or the > >> > > oscillator not ticking. > >> > > > >> > > > >> > > > >> > > > >> > > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > >> > > > > >> > > > I have checked the BDM connections. I checked for traffic on > > the > >> > BKGD > >> > > > pin, and its there. > >> > > > > >> > > > Power is on. All the lights are on. I am using a PC power > > supply > >> > > > through a LM317 regulator, so there shouldn't be any problems > >> > with > >> > > > current. I measured the current going to the chip somewhere > > round > >> > > > 50mA when running normally. What does it get up to? > >> > > > > >> > > > The thing that makes me think the pin is at fault is that it > >> > worked > >> > > > before, then suddenly stopped. Also none of the programs are > > able > >> > to > >> > > > detect the clock speed of the chip. > >> > > > > >> > > > Is there a way to test the pin? Is there traffic on the pin > > when > >> > the > >> > > > BDM programmer is disconnected? > >> > > > > >> > > > Nicholas > >> > > > > >> > > > --- In 68HC12@68HC..., "a_ribero" <a_ribero@y...> > > wrote: > >> > > > > > >> > > > > Hi Nicholas: > >> > > > > > >> > > > > Did you double ckeck the BDM connections. If you 6-pin > >> > connector is > >> > > > > not connected properly, the BDM box won't be able to > >> > communicate to > >> > > > > the board. > >> > > > > > >> > > > > And just to be sure, is the power supply on? Sometimes you > > have > >> > to > >> > > > go > >> > > > > to the basics... > >> > > > > > >> > > > > Do you use a Lab power supply? If so, check that the current > >> > > > > limitation is not too low. Otherwise, there is not enough > >> > current to > >> > > > > power up the board, therefore, no programming can happen. > >> > > > > > >> > > > > I would the BKDG pin as the last suspect. Most of the time > >> > there are > >> > > > > other problems that prevent the programming. > >> > > > > > >> > > > > Regards, > >> > > > > > >> > > > > Alex > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > >

What about bad soldering? Did you check RESET and BKGD by probing them straight at MCU pins? Hm, ECLK output is enabled. If software you flashed to the chip last time isn't writing to PEAR.NECLK bit to enable ECLK, and MODA and MODB pins are set for single chip operation (MODA=MODB=0) then it looks like part enters special single chip mode (BKGD=0 on reset). Do you see ECLK output even with BDM cable disconnected? If so then either BKGD pin is all the time at 0V and you should double check soldering, or pin is wired to BDM connector but there's no mo wire from pin to die... Also, if I remember correctly there was someone on the list who wired VDD1 and VDD2 to 5V, and BDM communication was working for a while... If it's not the case then I'm curious how did you fry your 9S12. Edward ----- Original Message ----- From: "pickleza" <pickleza@pick...> To: <68HC12@68HC...> Sent: Thursday, April 07, 2005 6:04 PM Subject: [68HC12] Re: BDM Not Working > > > Yip. The RESET line is fine. > > 1. Can't unsecure. Unsecure programs can't communicate. > 2. BDM BKGD line is working. There is traffic on the pin, but it > looks like there's no reply. > 3. Oscillator is working. It is buffered on ECLK. > 4. Reset line is good. Comes down for 200ms or so, then back up. > > Nicholas > > --- In 68HC12@68HC..., "zeta_alpha2002" <zeta_alpha2002@y...> > wrote: >> >> Your tried and check >> 1. unsecure >> 2. BDM line >> 3. Oscillator is oscillating/ >> 4. If RESET is okay then >> >> Bad MCU, it got sick and fried. >> >> >> >> --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: >> > >> > I thought it might be the oscillator, so thats what I checked > first. >> > There is clock coming out of the ECLK, so I think the oscillator > is >> > working. >> > >> > I will check the RESET line and let you know what I find. >> > >> > Thanks >> > Nicholas >> > >> > --- In 68HC12@68HC..., "zeta_alpha2002" > <zeta_alpha2002@y...> >> > wrote: >> > > >> > > Symptom suggest a reset problem. Check the reset line or the >> > > oscillator not ticking. >> > > >> > > >> > > >> > > >> > > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: >> > > > >> > > > I have checked the BDM connections. I checked for traffic on > the >> > BKGD >> > > > pin, and its there. >> > > > >> > > > Power is on. All the lights are on. I am using a PC power > supply >> > > > through a LM317 regulator, so there shouldn't be any problems >> > with >> > > > current. I measured the current going to the chip somewhere > round >> > > > 50mA when running normally. What does it get up to? >> > > > >> > > > The thing that makes me think the pin is at fault is that it >> > worked >> > > > before, then suddenly stopped. Also none of the programs are > able >> > to >> > > > detect the clock speed of the chip. >> > > > >> > > > Is there a way to test the pin? Is there traffic on the pin > when >> > the >> > > > BDM programmer is disconnected? >> > > > >> > > > Nicholas >> > > > >> > > > --- In 68HC12@68HC..., "a_ribero" <a_ribero@y...> > wrote: >> > > > > >> > > > > Hi Nicholas: >> > > > > >> > > > > Did you double ckeck the BDM connections. If you 6-pin >> > connector is >> > > > > not connected properly, the BDM box won't be able to >> > communicate to >> > > > > the board. >> > > > > >> > > > > And just to be sure, is the power supply on? Sometimes you > have >> > to >> > > > go >> > > > > to the basics... >> > > > > >> > > > > Do you use a Lab power supply? If so, check that the current >> > > > > limitation is not too low. Otherwise, there is not enough >> > current to >> > > > > power up the board, therefore, no programming can happen. >> > > > > >> > > > > I would the BKDG pin as the last suspect. Most of the time >> > there are >> > > > > other problems that prevent the programming. >> > > > > >> > > > > Regards, >> > > > > >> > > > > Alex > > Yahoo! Groups Links >

Too bad. Oh well if you are willing, time to move on get the MCU remove and replace. --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > Yip. The RESET line is fine. > > 1. Can't unsecure. Unsecure programs can't communicate. > 2. BDM BKGD line is working. There is traffic on the pin, but it > looks like there's no reply. > 3. Oscillator is working. It is buffered on ECLK. > 4. Reset line is good. Comes down for 200ms or so, then back up. > > Nicholas > > --- In 68HC12@68HC..., "zeta_alpha2002" <zeta_alpha2002@y...> > wrote: > > > > Your tried and check > > 1. unsecure > > 2. BDM line > > 3. Oscillator is oscillating/ > > 4. If RESET is okay then > > > > Bad MCU, it got sick and fried. > > > >

Yip. The RESET line is fine. 1. Can't unsecure. Unsecure programs can't communicate. 2. BDM BKGD line is working. There is traffic on the pin, but it looks like there's no reply. 3. Oscillator is working. It is buffered on ECLK. 4. Reset line is good. Comes down for 200ms or so, then back up. Nicholas --- In 68HC12@68HC..., "zeta_alpha2002" <zeta_alpha2002@y...> wrote: > > Your tried and check > 1. unsecure > 2. BDM line > 3. Oscillator is oscillating/ > 4. If RESET is okay then > > Bad MCU, it got sick and fried. > > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > > > I thought it might be the oscillator, so thats what I checked first. > > There is clock coming out of the ECLK, so I think the oscillator is > > working. > > > > I will check the RESET line and let you know what I find. > > > > Thanks > > Nicholas > > > > --- In 68HC12@68HC..., "zeta_alpha2002" <zeta_alpha2002@y...> > > wrote: > > > > > > Symptom suggest a reset problem. Check the reset line or the > > > oscillator not ticking. > > > > > > > > > > > > > > > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > > > > > > > I have checked the BDM connections. I checked for traffic on the > > BKGD > > > > pin, and its there. > > > > > > > > Power is on. All the lights are on. I am using a PC power supply > > > > through a LM317 regulator, so there shouldn't be any problems > > with > > > > current. I measured the current going to the chip somewhere round > > > > 50mA when running normally. What does it get up to? > > > > > > > > The thing that makes me think the pin is at fault is that it > > worked > > > > before, then suddenly stopped. Also none of the programs are able > > to > > > > detect the clock speed of the chip. > > > > > > > > Is there a way to test the pin? Is there traffic on the pin when > > the > > > > BDM programmer is disconnected? > > > > > > > > Nicholas > > > > > > > > --- In 68HC12@68HC..., "a_ribero" <a_ribero@y...> wrote: > > > > > > > > > > Hi Nicholas: > > > > > > > > > > Did you double ckeck the BDM connections. If you 6-pin > > connector is > > > > > not connected properly, the BDM box won't be able to > > communicate to > > > > > the board. > > > > > > > > > > And just to be sure, is the power supply on? Sometimes you have > > to > > > > go > > > > > to the basics... > > > > > > > > > > Do you use a Lab power supply? If so, check that the current > > > > > limitation is not too low. Otherwise, there is not enough > > current to > > > > > power up the board, therefore, no programming can happen. > > > > > > > > > > I would the BKDG pin as the last suspect. Most of the time > > there are > > > > > other problems that prevent the programming. > > > > > > > > > > Regards, > > > > > > > > > > Alex

Your tried and check 1. unsecure 2. BDM line 3. Oscillator is oscillating 4. If RESET is okay then Bad MCU, it got sick and fried. --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > I thought it might be the oscillator, so thats what I checked first. > There is clock coming out of the ECLK, so I think the oscillator is > working. > > I will check the RESET line and let you know what I find. > > Thanks > Nicholas > > --- In 68HC12@68HC..., "zeta_alpha2002" <zeta_alpha2002@y...> > wrote: > > > > Symptom suggest a reset problem. Check the reset line or the > > oscillator not ticking. > > > > > > > > > > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > > > > > I have checked the BDM connections. I checked for traffic on the > BKGD > > > pin, and its there. > > > > > > Power is on. All the lights are on. I am using a PC power supply > > > through a LM317 regulator, so there shouldn't be any problems > with > > > current. I measured the current going to the chip somewhere round > > > 50mA when running normally. What does it get up to? > > > > > > The thing that makes me think the pin is at fault is that it > worked > > > before, then suddenly stopped. Also none of the programs are able > to > > > detect the clock speed of the chip. > > > > > > Is there a way to test the pin? Is there traffic on the pin when > the > > > BDM programmer is disconnected? > > > > > > Nicholas > > > > > > --- In 68HC12@68HC..., "a_ribero" <a_ribero@y...> wrote: > > > > > > > > Hi Nicholas: > > > > > > > > Did you double ckeck the BDM connections. If you 6-pin > connector is > > > > not connected properly, the BDM box won't be able to > communicate to > > > > the board. > > > > > > > > And just to be sure, is the power supply on? Sometimes you have > to > > > go > > > > to the basics... > > > > > > > > Do you use a Lab power supply? If so, check that the current > > > > limitation is not too low. Otherwise, there is not enough > current to > > > > power up the board, therefore, no programming can happen. > > > > > > > > I would the BKDG pin as the last suspect. Most of the time > there are > > > > other problems that prevent the programming. > > > > > > > > Regards, > > > > > > > > Alex

I thought it might be the oscillator, so thats what I checked first. There is clock coming out of the ECLK, so I think the oscillator is working. I will check the RESET line and let you know what I find. Thanks Nicholas --- In 68HC12@68HC..., "zeta_alpha2002" <zeta_alpha2002@y...> wrote: > > Symptom suggest a reset problem. Check the reset line or the > oscillator not ticking. > > > --- In 68HC12@68HC..., "pickleza" <pickleza@y...> wrote: > > > > I have checked the BDM connections. I checked for traffic on the BKGD > > pin, and its there. > > > > Power is on. All the lights are on. I am using a PC power supply > > through a LM317 regulator, so there shouldn't be any problems with > > current. I measured the current going to the chip somewhere round > > 50mA when running normally. What does it get up to? > > > > The thing that makes me think the pin is at fault is that it worked > > before, then suddenly stopped. Also none of the programs are able to > > detect the clock speed of the chip. > > > > Is there a way to test the pin? Is there traffic on the pin when the > > BDM programmer is disconnected? > > > > Nicholas > > > > --- In 68HC12@68HC..., "a_ribero" <a_ribero@y...> wrote: > > > > > > Hi Nicholas: > > > > > > Did you double ckeck the BDM connections. If you 6-pin connector is > > > not connected properly, the BDM box won't be able to communicate to > > > the board. > > > > > > And just to be sure, is the power supply on? Sometimes you have to > > go > > > to the basics... > > > > > > Do you use a Lab power supply? If so, check that the current > > > limitation is not too low. Otherwise, there is not enough current to > > > power up the board, therefore, no programming can happen. > > > > > > I would the BKDG pin as the last suspect. Most of the time there are > > > other problems that prevent the programming. > > > > > > Regards, > > > > > > Alex