ERROR: Peripheral Initialization component is not supported for selected target processor for RTC1

[jamesskurski]

I am trying to build a project and now I'm receiving this PE ERROR which I don't recall seeing before as I have been able to generate, flash, debug and run the image.

The date of the PE file I have been using has not changed. Any idea on what else might have changed to cause this error to occur? (I built this project a month ago without issue)

This is the version of CW I have installed:

Installed Products:

- CodeWarrior for MCU

                Version: 10.5

                Build Id:130916

Any insight as to what might have changed to cause this to happen?

Thanks,

Jim

[trytohelp]

Hello James,

You're using CW for MCU V10.5 and Processor Expert in your application.

this worked fine some weeks ago but now, with the same application (no change/modification), Processor Expert generates an error.

Without the Project on my side, it's difficult to say what is the problem.

However, some patches were released for MCU V10.5 these last weeks:

      CW MCU v10.5 Update 1.0.0 

      CW MCU v10.5 RN/RNA Service Pack ,

      ...

The CW MCU v10.5 Update 1.0.0  fixes defects in documentation, DSC compiler and Processor Expert.

I think this could be the cause of the behavior.

We recommend you to check all Processor Expert Beans and to rebuild PE code before to build your project.

May be the Processor Type under PE was not selected anymore.

Before I recommend to backup the current project ... just in case there is a problem.

hope this will help you.

I wish you a Happy New Year.

Regards

Pascal

[jamesskurski]

Hi Pascal,

I applied the patches you suggested but the error still occurs.

Actually, I believe this error has always been there I only see it if I open Processor Expert.

I have been using only CW10.5 and believe this error is not seen in CW10.3 as my co-worker has the same version PE file and does not see this when he builds.

I am, however, still able to generate all build artifacts but I'm still unsure on how to eliminate this error permanently.

Any other ideas on how to resolve?

Thanks,

Jim

[trytohelp]

Hi James,

Can you please provide us more details ?

      - Processor ?

Is it possible to have the project ?

Regards

Pascal

[jamesskurski]

Hi Pascal,

The processor I have is the MCF51JM128VLH but the engineer who started this project selected MCFJM128VLK no longer works here so I'm not sure as to why.

All I know is that if I select MCF51JM128VLH, then other components fail (Admin:AsynchoSerial).

We are currently using this for Serial Debug and as output for a Factory Test so this would be a step in the wrong direction.

Anyhow, I have attached the project files for you to view.

Please let me know if you require any other information.

Thanks!

Jim

[trytohelp]

Hi James,

In fact you will meet the problem with the example I sent you.

the project worked fine but after to restart Eclipse I got the issue.

I will continue to handle the issue and will keep you informed.

Regards

Pascal

[jamesskurski]

Hi Pascal,

Thanks for the update.

I look forward to your next posting.

Regards,

Jim

[trytohelp]

Hi Jim,

There is a bug in Processor Expert.

this will be solved in next release which should be released end of Q1.

To solve the issue I recommend to extract the MCU folder contained in the zip file attached to your CodeWarrior Installation.

Be sure Eclipse is closed before to extract the file.

On my side this solved the issue.

Regards

Pascal

[jamesskurski]

Thanks, Pascal.

I will extract the hotfix zip, follow the instructions and let you know how it goes.

Regards,

Jim

[jamesskurski]

Pascal,

This hot fix has resolved the RTC1 PE error for the MCFJM128VLK. Could these changes be ported over to the MCF51JM128VLH configuration?

Ultimately, I would like to use this configuration as this is the CPU we actually have; however, when I select this configuration, I still get the errors I mentioned above.

(i.e. All I know is that if I select MCF51JM128VLH, then other components fail (Admin:AsynchoSerial, RTCComm). We are currently using this for Serial Debug and as output for a Factory Test)

Would you be able to assist me in this? Or is it just a matter of pushing over the updated items from the MCF51JM128_80.cdb to the MCF51JM128_64.cdb? (most of them anyway as I know not all of the features are available in the VLH?)

If you could help me with this your assistance would be greatly appreciated,

Jim

[trytohelp]

James,

The hotfix is not working for VLH devices.

Processor Expert team is working on a new hotfix.

This will take some days.

Keep you informed.

Pascal

[jamesskurski]

Thanks, Pascal.

I look forward to a new hotfix for VLH devices.

Jim

[trytohelp]

Hi James,

Attached the new hotfix which is solved the VLH derivatif too.

It's working now on my side.

Regards

Pascal

[jamesskurski]

Hi Pascal,

Thanks for the updated hotfix. This, too, has resolved the RTC1 PE Error for the VLH configuration.

Would you be able to assist me in the other components that I still have PE failures? (Admin:AsynchoSerial, RTComm)

Admin:AsynchoSerial returns the following PE Error:
ERROR: Timing setting failed - it is impossible to set the following items: initialization value.

RTCComm returns the following PE Error:
ERROR: Timing setting failed - it is impossible to set the following items: initialization value.

Would you have any insight as to how the best way to resolve and eliminate them?

Thanks,
Jim

[trytohelp · Accepted solution]

Hi Jim,

the RTC problem is fixed now.

To avoid confusion I recommend you to create new thread (post) for other PE questions.

Based on the project you provided me, now I'm able to "Generate Processor Expert code" without problem or error.

To investigate the other/new issues, please can you provide us more info ?

An example reproducing the behavior is the better solution for us.

Regards

Pascal

[trytohelp]

Hi James,

I've reproduced the problem on my side with your project.

On my side I've created a new project for JM128 and added the RTC bean.

I can generate the PE code without problem.

Attached you will find my document.

I think there is something corrupted in the PE config.

I will continue to investigate it.

Keep you informed.

Regards

Pascal

[Jorge_Gonzalez]

Hello Jim:

What MCU target are you using? Have you seen the same error for different MCUs?

Regards!

Jorge Gonzalez