Cannot FLASH MPC55xx targets using CW 2.8

[Sruggles2]

I am unable to FLASH either MPC5675K or MPC5643L targets using CW, v2.8.  I get an Exception Error when the RESET macro runs after loading code.  ICD open and the RESET macro runs normally the 1st time, then the PROG window opens and Flashed code to the target.  However, when the RESET macor runs the 2nd time, the program produces and Exception Error and freezes.  I have no option but to kill the program.

I am unable to debug application code for either target.  I ensured the correct target is selected when ICD opens.  The attachment shows the problem I experience. 

System:

Win XP, SP3

4GB RAM

P&E MPC Multilink

[stanish]

Hi Spencer,

Unfortunately your email (SR1-790255456) seems do not exist.

The problem is probably related to the fact the standard CodeWarrior libraries includes some absolute paths to the different drives. It's because the libraries were located in the different paths when built on our side (e.g. "D:\workspace\EPPC\workspace_codegen...") and the debugger is trying to access these source files.

 Could you possibly try to Rebuild the standard MSL + Runtime libraries on your side and then rebuild and debug the test project?

To rebuild the libraries:

1) open the CodeWarrior libs projects "<CodeWarrior directory>\PowerPC_EABI_Support\EPPC_Build_All_*.mcp

2) remove object code (ctrl + "-")

3) rebuild

Hope this will help.

Stanish

[stanish]

Hi Spencer

It seems that the debugger is accessing a disc drive for some reason.

I'd suggest you to reinstall the CodeWarrior (CW).

After uninstall CW, restart PC, then delete the leftover CW folders, please also delete all CodeWarrior prefs (they exist in the usual Windows locations for application prefs, usually is: %userprofile%\Local Settings\Application Data\Metrowerks\).\).  After this run regedit.exe, search then delete CW information in registration form.  Restart PC and install new CW.

You can also search for some relevant information on google searching "Windows - no disk"

Stanish

[J2MEJediMaster]

You need to file an on-line service request for this problem. Click here to go to the service request page.

---Tom