Target Status: IP_TAP_CNTL_-16 is null.

Vignesh,

FlexRay as such does not have anything to do with the error you are seeing. I have seen this error pop up from time to time as well, but it does not prevent me from connecting to the device and debugging.

How is this error hindering your debug?

Regards,

Abhishek

TAP_CTRL_16 is an indication of the ICEPICK JTAG multiplexor connection to the ARM CoreSight DAP module.  I have not personally seen this error but it would seem to indicate that CCS had a temporary issue to connect to the ARM debug logic.

Regards,

Karl

Thanks for responding.

Yes, the error did not affect the debugging. Previously i did not add the startup code to the project. I thought that it would get executed automatically. So it created some problems.

But now after adding it  am facing another problem. The start up code is running for hours together. As far as i i know it would take only few milliseconds.

What kind of problem is this? How to rectify it?

Please clarify.

Thanks in advance,

Vignesh

Vignesh,

did you use HALCoGen to generate this startup code?

Regards,

Abhishek

Vignesh,

that's alright. The key point is that you could solve the problem and are not held up anymore.

Regards,

Abhishek