AnsweredAssumed Answered

DSC56F8345 & CW10.2

Question asked by TurboMan on Oct 9, 2012
Latest reply on Oct 29, 2013 by xiangjun.rong

Has anyone else here used a 56F8345 with CW10.2? Successfully?

 

I'm asking because I'm having real problems getting anything to run. Here's what works / doesn't work:

1. CW7.3, USB Tap, WinXP VM, '8345 custom hardware. Works ok.

2. CW7.3, USB Tap, WinXP VM, '8367 Freescale EVM. Works ok.
3. CW10.2, USB Tap, Win7 x64, '8367 Freescale EVM. Works ok.

4. CW10.2, USB Tap, Win7 x64, '8345 custom hardware. Fails...

 

Failure:

When a basic blank processor expert project is created for the 8345, the debugger (USB Tap ONCE) attaches and it looks to be ok, until you stop, and then see it's locked up in CPU.c, initialising the PLL - well, trying to. It will just loop waiting for lock bit to be set which never happens. It doesn't happen because the PLL power down bit is set, and the PLL is not running. But, according to Freescale, and my service request in with them, the debugger is writing ok.

 

If I then add code to the main{} function, the project will either run erratically, or the debugger will refuse to connect.

 

Has anyone else seen this behaviour? Freescale don't have an 8345 dev board I can use, to eliminate our custom hardware. However, our custom hardware is working ok with CW7.3 with no problems, as stated above.

 

Tried:

USB drivers (Newer libwin drivers are available from sourceforge but this hasn't helped.)

Re-installing CW10.2 + updating to 1.0.0 service / update patch

Different machines (this happens on both XP and Win7 x64, professional and home premium)

CCS config changes to configure for USB Tap explicitly. Also verbose logging and output sent to Freescale.

Numerous new projects / CW settings / USB Tap speed / config settings.

 

None of the above has helped. Any help is appreciated...

Outcomes