topic Re: DEMO9S08LC60 - Communication problem in 8-bit Microcontrollers

DEMO9S08LC60 - Communication problem

Valval — Mon, 17 Nov 2008 15:23:57 GMT

I cannot communicate with the DEMO9S08LC60. When I want to debug, a window open and says: Lost communication with the target device: possible causes:

1. Target board is not powered (yes, it is)
2. Oscillator frequency is out of range ( I did not change the oscillator)
3. The device has been reset ( ??)

Second windows:
Communication error during frame frequency:
1. BDM is not connected to the instrumer (yes, it is)
2. Invalid device is selected (no)
3. The device has been reset.

What can I do to solve this problem?

Many thanks in advance

PS: The project is the original one and use to work fine...

Valval

Re: DEMO9S08LC60 - Communication problem

Ake — Mon, 17 Nov 2008 16:49:48 GMT

Hi,

I picked up my DEMOLC60 board and tried to burn a piece of code.

It behaved the same way as your board did!

But then I removed the +9V power, and applied it again, and bingo it worked!

So my suggestion is to set the POWER_SEL jumper to UNREG.

Connnect the USB cable.

Connect the power cable. Note that it should not be a +5 V supply, but a + 9 V.

And then you should be able to run your code.

Regards,

Ake

Re: DEMO9S08LC60 - Communication problem

Valval — Mon, 17 Nov 2008 18:01:10 GMT

Hi Ake!

I tried your solution but I still have the same error...

Do you have another idea ?

Thank's

Valval

Re: DEMO9S08LC60 - Communication problem

J2MEJediMaster — Mon, 17 Nov 2008 21:30:03 GMT

You say the project used to work. Given that, then what changed? Did you:

1) Switch to another board? Then the new board is suspect.
2) Move your tools to a new PC? Then system/connector settings might be suspect.
3) Upgrade CodeWarrior? Sadly, sometimes there are changes/new features in the upgrade that can whack your project. Double-check all CodeWarrior settings and read the release notes.
4) Change a cable? Try the old cable.

---Tom

Re: DEMO9S08LC60 - Communication problem

Valval — Mon, 17 Nov 2008 21:42:13 GMT

Hi Tom,

Thank you for the answer:

1) I am still using the Demoboard
2) No change
3) No change
4) No change

BUT, I tried to put the device in sleep mode (Stop1 mode) and since this moment, I cannot communicate any more. Can the problem be here?
(Now I am trying to program the device with the demo application)

Best regards,

Valval

You say the project used to work. Given that, then what changed? Did you:

1) Switch to another board? Then the new board is suspect.
2) Move your tools to a new PC? Then system/connector settings might be suspect.
3) Upgrade CodeWarrior? Sadly, sometimes there are changes/new features in the upgrade that can whack your project. Double-check all CodeWarrior settings and read the release notes.
4) Change a cable? Try the old cable.

---Tom

Re: DEMO9S08LC60 - Communication problem

Ake — Mon, 17 Nov 2008 22:31:02 GMT

Hi,

I think that if you go into STOP mode, then you must get out of it before trying to run the debugger.

Here is some wild guessing:

If the DEMO gets stuck, you will have to start over again.

So start with upnplug the USB cable.

Then remove the power cable.

Now you should either plug in the USB cable first or the power cable.

This is different on different DEMO boards.

After that you should start it by hitting the Debug key in the CodeWarrior window.

Regards,

Ake

Re: DEMO9S08LC60 - Communication problem

Sockey — Fri, 27 Nov 2009 20:35:44 GMT

I have the same problem with the DEMO9S08LC60. The person using it said he was downloading a program through the USB connection and when it got to the 100% downloaded it hung up at that point. He gave the board to me to try on my PC and it gives the same messages as you got.

The board is powered up and the USB interface chip's (on the back side of the board) clock is running.

I tried uninstalling and reinstalling the Softec operating system with the same result. I figure the board is blown up and ordered another. Hopefully the new board will work. If not I'll remove all of the Codewarrior software and Softec software and reinstall it. But I don't see it being the software.

If you find an answer let me know at rsockey@cbgbiotech.com. thanks