Using demo boards as BDM interfaces - 08AW60

[TurboBob]

A little background:  I have been using CW6.1 for a while with the AW60 demo board to develop my JM60 application.  It seems to work ok, but I am suspecting a bug in 6.1 and tried to update to 6.2

My CW installation is fully licensed.

When updating to 6.2, the AW60 demo board was not accepted by the TrueTime app as a valid interface for a JM60 chip.  Since I have almost all of the demo kits, I got out my JM demo kit, put a header on it and plugged it in.  TrueTime updated the firmware, and appears willing to talk to it.  It will load my code into an on-board JM60 chip,  but it will not connect to my target (remove daughter card, plug in ribbon cable).  It does halt the target system but will not connect.

The demoboard will connect,load, and run if I use the CW6.1 to connect to it (yes I have 6.1 and 6.2 loaded on my machine.)

I hope I am being clear,  basically 6.2 won't talk to my target, but will talk to a chip on the demo board.

Any ideas?

Thanks,

Bob Bailey

Added p/n to subject.

Message Edited by NLFSJ on 2008-12-24 07:19 AM

[kef]

On AW60 board, is your chip supplied with 5V or 3.3V? Is chip on your target board powered the same? I don't know, but I guess that BDM on demo board may lack voltage level translator like in full featured USB-ML-12.

[TurboBob]

In all cases I am using 5 volts.  I have tried using the USB from my host PC, and using the target power.

Oddly (or perhaps by design)  the exact same setup works fine with CW 6.1  no problems.  When I use CW 6.2, the true-time application cannot enter background mode.

Bob

[kef]

Oh, on QE (and JM probably) /RESET pin by default is not functioning as /RESET, but as I/O pin. To enter special mode, target should be reset with BKGD pulled low. Since there's no real /RESET pin, external reset can be done only cycling target power on/off. Isn't demo board cycling socket power on/off?

Message Edited by kef on 2008-12-24 12:36 PM