topic Meaning of "Invalid target system access" error message for CodeWarrior TAP in CodeWarrior Development Tools

Meaning of "Invalid target system access" error message for CodeWarrior TAP

christiankeller — Fri, 13 Jan 2017 09:40:54 GMT

I have a CodeWarrior TAP connected via USB. The device has worked fine before. Cables have not been changed or disconnected. However upon today's start of the CodeWarrior IDE, the connection seems not to get recognised. Instead the IDE tells me the error message:

"Invalid target system access: 'C:\Freescale\CW_PA_v10.5.1\PA\cdde\bin\cdde.exe'"

I have no idea what this is supposed to mean. Is there a list of error message for the tooling with a description about its meaning?

The connection server does identify the probe correctly with the "findcc cwtap -usb" command.

From my experience the connection reliability with the tap and the IDE has been...unstable...to put it politely.

Re: Meaning of "Invalid target system access" error message for CodeWarrior TAP

addiyi — Fri, 13 Jan 2017 09:46:20 GMT

You are trying to use QCVS or Performance Analysis or just a bareboard project?

Adrian

Re: Meaning of "Invalid target system access" error message for CodeWarrior TAP

christiankeller — Fri, 13 Jan 2017 10:11:37 GMT

SerDes Line config read in with the Assistant on the ProcessorExpert validation tool.

Same message appears with the DDR settings validation tool, which has worked before.

Re: Meaning of "Invalid target system access" error message for CodeWarrior TAP

addiyi — Fri, 13 Jan 2017 10:22:52 GMT

Check if any cdde instance is running. Close all ccs/cdde/python process, restart CodeWarrior and check if in Target Connection the path to cdde is correct.

Adrian

Re: Meaning of "Invalid target system access" error message for CodeWarrior TAP

christiankeller — Fri, 13 Jan 2017 10:27:57 GMT

Thank you, that did the trick! If only the message would be more helpful...

Re: Meaning of "Invalid target system access" error message for CodeWarrior TAP

addiyi — Fri, 13 Jan 2017 10:46:01 GMT

We are working on this :smileyhappy: