Hello all,
I intend to use a Codewarrior TAP to debug an existing system featurin MPC5200.
First, I want to connect the TAP via ethernet, as USB drivers sometimes make my computer stuck (on Windows 10) and I had no succes with them.
Could you please provide help with the following questions:
1. To my understanding, I do not need any drivers if I will connect the TAP through ethernet. USB will be used only for power.
2. Accesing the telnet interface of the TAP with putty works. However, when I type:
core> ccs
(removed)
core> ccs version
/mnt/flash/ccs/bin/coreprompt/ccs: exec: line 67: /mnt/flash/ccs/bin/coreprompt/ccs --help: not found
I have reflashed firmware but with no succes.
Can you please tell if this is normal?
Thank you and best regards,
Mihai
Hello Peter,
I am using Installer: CodeWarrior for mobileGT Linux Application Edition (Windows Hosted) v9.2
I have it installed on Windows 10 64 bit.
I could try other version and flash the TAP using the ccs console in that specific version. Maybe the .gp files are different in another version.
I can also try on Windows XP if needed.
Thank you,
Mihai
Hello,
If I remember correctly you need WinXP or older for Classic CodeWarrior which supports MPC5200:
Which exact version of codewarrior are you using?
Best regards,
Peter
Thank you for your quick answers, @petervlna
1. I used USB only for power from a wall adapter, not from the USB port of a computer. It should be able to supply the required 500mA, as described in the user's guide.
However, I can try the USB connection from the computer also on a Windows XP system. To my understanding, the drivers might not support Windows 10.
I am open to any of the ethernet / USB options, or a combination of them. I only want to get it working, get it detected with findcc etaps or utaps in ccs console.
2. Could you please recommend a method to restore the firmware package/CCS inside the TAP?
If there are multiple builds of the firmware depending on the target families, I would be interested in the one which includes MPC5200. Hopefully these builds are available somewhere.
I could also dissasemble the unit and check internal hardware/interfaces if needed.
Best regards,
Mihai
Hello,
1. To my understanding, I do not need any drivers if I will connect the TAP through ethernet. USB will be used only for power.
The TAP itself is USB powered, but the official guide also states that if you only plan to use Ethernet communications, the TAP can be powered from the external power supply provided with the unit, rather than depending on a USB connection to the PC.
Can you please tell if this is normal?
No — this is not normal behavior, and it points to an issue with the CCS installation inside the TAP.
mnt/flash/ccs/bin/coreprompt/ccs --help: not found
means one of these is happening:
The CCS binary is missing or corrupted
- The script exists (ccs launcher), but the actual executable it calls is not there
- Very typical after bad firmware flash or incomplete image
Wrong firmware package
- CodeWarrior TAP firmware has different builds (target families / CCS versions)
- If wrong image is used → CCS part may not be included or mismatched
Broken internal path / environment
- The script (ccs) tries to call itself with parameters (--help) and fails
- This often happens when:
- symbolic links are broken
- filesystem is partially corrupted
Best regards,
Peter
Hello all, follow-up on this topic:
I have used the following ccs.zip file found on this forum at the following link: https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/cw-mcu/11745/1/ccs.zip
It is recommended by "trytohelp" user and worked for me. I have not used Codewarrior IDE so far.
As petervlna recommended, I have tried on Windows XP with USB connection after installing drivers according to readme.txt and I get the result in the attachment.
I have also tried Windows 10 with ethernet connection, no drivers installed. CCS console shows the output in the other attachment.
It seems not it is a matter of probe target power detection.
Thanks for the help,
Mihai
Replying to myself:
I have reflashed the TAP using "update cwtap 192.168.1.2. --force:". No more issues on the ccs version in terminal.
The TAP has been connected to the target system. There are two devices only on the JTAG scan chain, as detected by FT2232H with OpenOCD.
openocd.exe -f interface/ftdi/FT2232HL_24feb.cfg xPack Open On-Chip Debugger 0.12.0+dev-02228-ge5888bda3-dirty (2025-10-04-22:44) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html
Info : clock speed 100 kHz
Info : JTAG tap: altera.tap tap/device found: 0x020b20dd (mfg: 0x06e (Altera), part: 0x20b2, ver: 0x0)
Info : JTAG tap: mpc5200.cpu tap/device found: 0x1001101d (mfg: 0x00e (Freescale (Motorola)), part: 0x0011, ver: 0x1) Warn : gdb services need one or more targets defined
However, in ccs console with Codewarrior TAP i get:
TDO -----
|
* Device 0 IDCODE: 020B20DD Device: Unknown Device
* Device 1 IDCODE: 1001101D Device: FSL MPC5200B rev 2.x
* Device 2 IDCODE: FFFFFFFF Device: Unknown Device
* Device 3 IDCODE: FFFFFFFF Device: Unknown Device
* Device 4 IDCODE: FFFFFFFF Device: Unknown Device
* Device 5 IDCODE: FFFFFFFF Device: Unknown Device
* Device 6 IDCODE: FFFFFFFF Device: Unknown Device
* Device 7 IDCODE: FFFFFFFF Device: Unknown Device
|
TDI -----
What's with devices 2 to 7, with IDCODE FFFFFFFF? Could you please tell if you suspect an issue with the connection?
Thanks,
Mihai