P&E ICD not in list in CW5.0 for HC(S)08

[w8abz]

All,

Just received the DEMO9S08QG8 board.  I've installed CW 5.0 for HC(S)08, and installed the Service Pack for HC(S)08.  I'm working through the DEMO9S08QG8 Quick Start and getting stuck with Code Warrior.

I'm able to open the project, but in the pull-down just below the project-name tab, there is no option for the P&E ICD.  The only ones listed are:

 Full Chip Simulation

 P&E Multilink / Cyclone Pro

 SofTec HCS08

 HCS08 Serial Monitor

The Full Chip Simulation works fine.  If I select P&E Multilink / Cyclone Pro and click the debug icon, the debug window opens but locks up.  I have to right-click on the start bar item, click close and select End Now.  (DUH -- don't have a Multilink or Cyclone Pro.  I'm trying to use the USB BDM on the DEMO... board.)

The DEMO... board is connected by USB, and the drivers appear to be loading fine.  LEDs are lit (LED2 blinks, LED1 toggles with the switch), so the demo app is running on the MCU.  Jumpers look to be correct.

How do I get the "P&E ICD" option into the dropdown so I can connect to the demo board for debugging, etc.?

I'm new to the latest IDEs in general and Code Warrior in particular, so apologies if all this is documented someplace I haven't encountered yet.

TIA,

Dale, W8ABZ

[RockyRoad]

I tested it out on a DEMO9S08QG8 that I have and it worked.

As you've probably noted, the demo and documentation were originally written for CodeWarrior 3.1. So the screen shot and documentation about the debug selection aren't exactly right.

In CW 5.0, the drop down box shows the actually debug device. In 3.1, this was more like the class of debug tools (like PE ICD). You used to select PE ICD and then when you got in the debugger, you'd select the specific debug device.

In your case, in CW 5.0, you would select "P&E Mulitilink/Cyclone Pro." The USB BDM on the demo board is actually the guts of a Multilink 2.0. So when you first connected the board, you should have seen a Multilink 2.0 driver get installed.

You said that you installed a service pack. Hopefully, this was the "CW08 v5.0 Patch 1." This is the only update that you need for CodeWarrior 5.0. This patch also installs a new version of the DEMO9S08QG8_APP that might work better for you. (When I tested, I used the original one off of the demo CD - not this new one.)

If you're still having problems, post back and we'll work on it.

[w8abz]

All,

Well, I installed CW 5.0, then the Service Pack (yes, it was "CW08 v5.0 Patch 1") on a different PC, being careful to reboot between/after.  Then I connected the DEMO9S08QG8 board, which came up fine.  Then I ran the DEMO..._APP software, did the make, debug and flash just fine (with the P&E Multilink / Cyclone Pro selection) and all was well.  The pot sweeps from 0x000 to 0x3FF, etc., etc.

Just to verify, I popped the chip, plugged in a new (unflashed) part and flashed it, ran the demo again, etc.  No problems.

So it's probably just a mangled install on the first PC.  I've had some other CW (3.1) install / remove issues on that PC anyway, so I guess it's time to clean it up in general.

I look forward to an updated set of DEMO..._APP instructions!  First for the corrected screen shots for CW 5.0, but also for little items like explicitly instructing you to start your terminal emulator BEFORE you do the flash cycle (so it's ready to receive the demo banner page when the MCU comes back up)!  I'm reminded of the cute comic where the guy build a yacht in his basement, then gets to step 4: "Perform steps 1-3 in a large open space near a body of water".

Thanks for the help.  Now I'm off to find SCI and IIC demos and figure out my (top secret hush hush!) application.

Best Regards,

Dale, W8ABZ

Cleveland Heights, Ohio  USA

[FC]

Hello,

I have the same problem of the debugger locking up.  I installed CodeWarrior from the supplied cds (including the service pack) and still cannot connect to the target.

The board is running the preloaded program fine.  I checked the flash registers of the demo program running full chip simulation (under examples) and it seems the flash is secure with no back door key enabled.  According to the datasheet, with a secure flash and no backdoor access key enabled, the on chip debug module will not work, the entire flash needs to be erased.

Perhaps I should get a blank mcu, but samples are not available yet and neither are in stock.