Hi Stan,
Thanks for your input.
It has been just a few weeks since I have got the board, and in this while I have never gone around to doing any flash programming or for that matter the selection of any flash algorithm, since it is not required at this stage of our project. However, I believe every time we are changing the processor mode from DPM--> LSM the shadow flash region would have to be updated through the User Option Status Register which mirrors the Shadow block region. And since the application code that I have as of now does not explicitly modify this register, I believe it would be a part of the Codewarrior10.5 hardware package.
The sequence of events through which the problems came about are:
1. In one of my attempts to flash the code, Codewarrior Crashed following which I got the error :
>>> Error launching Test_MPC5675K_DPM_FLASH_PnE USB-ML-PPCNEXUS
EPPC GDI protocol error: Failed to configure target. Processor configured as DPM/LSM opposite of the project settings.
2. Following this I tried the usual steps to fix the problem as suggested on the Freescale community posts - to re-install the P&E drivers, re-install Codewarrior10.5 etc but to no avail.
3. Then I used Codewarrior Developement Studio 5.9.0 and did tried launching one of the sample projects along with providing the hex password within the PEMICRO Connection manager -->Advanced Option.
Following this step, the error message changed to: "Attempting to uncensor device" and now on trying on Codewarrior10.5 the error message changed to "Device may be censored. Please enter the password (in hex) to uncensor".
4. After this the status of the board has not changed and the same error message continues to show-up.
Since I have not explicitly erased the shadow flash region using any of the flash programming algorithm I presume, that it should be still be intact(hopefully) and if there is any way that the board can be recovered without the need for replacing -it would be a great help.
In any-case I will post the same steps on the community forum as well so others can avoid the same problem.
Thanks and regards,
Girish Rao Bulusu