Problem when enabling tracing and profiling for the P3041DS board -- No matching command converters.

[samehsamir]

Hello,

I'm trying to enable tracing in a CodeWarrior debug session. I've succeeded in debugging the Linux kernel as illustrated in the CodeWarrior for Power Architecture targeting manual via a CodeWarrior TAP in attach mode

(i.e., Stop U-boot from autobooting, Attach from CodeWarrior, boot from U-boot prompt).

When enabling the "Start a trace session" checkbox from within the debug configuration, the following error shows.

Failed to configure plugin Trace Probe - NPC.

The function "applyConfig" returned an error condition  (0x80004005)

Error from TCF: 2147500037 (Did not find matching command converter. Present command converters: cc: 0 cwtap:0)

It also happens when using a DDR buffer for tracing instead of an NPC buffer. I am running CodeWarrior from a 64-bit Ubuntu 12.04 installation.

Thank you,

Sameh

[addiyi · Accepted solution]

Workaround for this kind of issue, when the probe used is CodeWarrior TAP is to use Connection Type: CodeWarrior TAP with Hardware connection: Ethernet, or to use Connection type: USB TAP.

Adrian

[addiyi]

I'm using CodeWarrior for PA 10.4.0 and I was able to collect trace using a cwtap and a stationary project. Please try to use stationary project and Download configuration to see if the issue is reproducible.

Adrian

[samehsamir]

I created a bareboard application -- not sure if that is what you mean by a stationary project -- for P3041 and copied code from the e500mcPerformanceMonitor_eabi sample project. Debugging works fine for both the Download and Cache Download debug configurations, but when enabling tracing the previous error still happens.

Thank you,

Sameh

[addiyi]

Please try only with the default bareboard project. From the Wizard select Download launch and Start a trace session on debug launch. After you start the debug session using Download configuration, and application stops a main, click Resume and trace should be collected.

Adrian

[samehsamir]

I tried the default bareboard project with all the settings you mentioned. The error persists. The only setting I had to modify for debugging was the JTAG clock speed from the target settings. The following error message is shown:

Error launching p3041-core00_RAM_P3041_Download

CCSProtocolPlugin : Failed to configure the JTAG chain. Simulator/CCS is already configured to use a JTAG Chain different than the target type specified in CodeWarrior debugger settings

[CCS last error: Connection refused ]

The default clock speed chosen is 10230 kHz. In the drop down menu, only 4000kHz and 12500kHz are shown. Picking any option from them bypasses this error, but tracing is still not enabled. I also changed this setting in previous projects.

Thank you,

Sameh

[addiyi]

OK, so you are able to enter debug, program stop at main and after Resume you receive errors? Usually after Resume, you can find Trace data in Software Analysis view.

Adrian

[samehsamir]

I see the same original error. Even after pressing OK and cancelling exporting of diagnostics, there is no trace data in the Software analysis window.

This problem also occurs on CodeWarrior 10.4.0 installed on Windows 7 (Evaluation version).

[addiyi]

For CCS server, did you use Automatic launch or Manual launch? Also, if Manual launch is used, CCS server is opened remote?

Adrian

[samehsamir]

Automatic launch was configured for CCS server.

Thanks,

Sameh

[addiyi]

Hi Sameh,

Could you please provide a recent log from /home/<user>/.codewarrior

Adrian

[samehsamir]

Hello Adrian,

Here's the contents of codewarrior.log after this error:

08:08:08.322 WARN  [0xc1089b40] sae.deapi_utils	: [parseDeapiConfigFileLine]: line <> does not have expected format
08:08:08.323 WARN  [0xc1089b40] sae.deapi_utils	: [parseDeapiConfigFileLine]: line <> does not have expected format
08:08:08.343 WARN  [0xbb07cb40] tcf.peer	: Failed connecting to remote peer
08:08:08.346 WARN  [0xbb07cb40] tcf.peer	: Failed connecting to remote peer
08:08:08.397 WARN  [0xbb07cb40] tcf.peer	: Failed connecting to remote peer

Thank you,

Sameh

[addiyi]

Hi Sameh,

The log say nothing about the issue. Let's try to set the logger to debug mode:

1. Rename /home/<user>/.codewarrior/ log4cxx.xml.temp to log4cxx.xml

2. Edit the xml file and set the verbosity to debug if is not already set:

<root>

<priority value="debug"/>

<appender-ref ref="CodewarriorAppender" />

</root>

3. Reproduce the issue again and send the log file.

Adrian

[samehsamir]

Hi Adrian,

The logs are a bit large and I don't have the capability/privilege to upload files. I will send it to you via email.

Thanks,

Sameh

[addiyi]

Please indicate the CodeWarrior version you are using.

Adrian

[samehsamir]

I am using the latest CodeWarrior v10.4 for Power Architecture, with the Linux service pack 1 and e500mc toolchain.

Thank you,

Sameh