CodeWarrior 10.6 with MQX 4.0 debugger issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

CodeWarrior 10.6 with MQX 4.0 debugger issue

1,156 Views
vines
Contributor III

Hi,

 

I recently upgraded my CW software from 10.2 to 10.6. However when I try to debug my application with BSP of MQX 4.0, there was this problem "GDI Protocol fatal error" "The Debugger is not connected to PE device". I am suing PE micro Multilink Universal as my programmer/debugger. I search the forums and I saw a suggestion of updating the driver and then closing CW and re launch with new project workspace. I tried this method but to no avail. I then tried to install MQX 4.2 and debug one of the example programs. I can debug without any problems.

 

You might asked then just used 4.2 instead? My target platform is Kinetis TWR60d100. And I am still using CW compiler. I have not switch to GNU C Compiler yet. On MQX 4.2 there is no BSP for my target platform. And I am hesitant to convert my application to GNU C as it will cause a ton of problems ( align, etc).

 

Is there anything I need to do to be able to debug under CW 10.6/MQX 4.0? Or is this a limitation like I read on 1 of the questions here in forum about no support for MQX 3.8 in CW 10.6.

FYI

I can see that the chip was programmed correctly, but when I try to break then this dialog box pops out.

 

Thanks in advance for the help.

Labels (1)
0 Kudos
7 Replies

910 Views
vines
Contributor III

Hi,

Anybody out there with similar problems?

Thanks.

0 Kudos

910 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

hi,

MQX 3.8 was developed to work with CW MCU v10.1. It is not supported in CW MCU v10.6.

MQX Task Aware Debugger is integrated with CW MCU v10.6 and is automatically installed. This plug-in can be used with all supported MQX versions (i.e. MQX 4.0.x, MQX 4.1, MQX4.2 and MQX Lite).


Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

910 Views
vines
Contributor III

Hi Jennie,

I am not using 3.8. I just cited it as an example for not being supported in CW 10.6. I am using 4.0 as my MQX. If you could read the first part of my message I mentioned my problems on using 4.0 and CW 10.6 with CW compiler.

Thanks.

0 Kudos

910 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

Vines,

normally the error message "GDI Protocol fatal error" "The Debugger is not connected to PE device" are not because of the compatibility of CW and MQX version, but a target connection problem.

what debug interface do you work with?

How is the connection work if you create a new project with wizard without MQX support?


Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos

910 Views
vines
Contributor III

Hi Jennie,

When you say connection problem is it the physical connection between programmer to target board? If that is the case, I doubt so. I'll explain why.

I still maintain a CW 10.2 version on my PC. I can debug the same project without an issue using the same PE micro Multilink Universal setup. Then using the same setup, I close CW 10.2 and open my project and try to debug on 10.6 I will have this error.

0 Kudos

910 Views
vines
Contributor III

Also after clicking OK in the dialog box "GDI Protocol fatal error" "The Debugger is not connected to PE device" there is another pop up dialog shown below.

pastedImage_0.png

pastedImage_1.png

Thanks,

Carlo

0 Kudos

910 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

Hi,

I ever have similar problem and I fixed the problem by create a new workspace and update the multilink universal driver to the latest.

the driver is included in USB Multilink Universal (and FX) Resource CD  from this url

P&E Microcomputer Systems: Over 30 years as an Industry leader in Embedded Systems Development Tools...

there is also a discussion about this problem, can you please check if this can help.

GDI Protocol fatal error

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

0 Kudos