I am using an evaluation version of Code Warrior 8.2.3 for 56F801 EVM. The EVM was working fine but all of a sudden i am getting the following error "CCS Protocol Plugin: Unknown Protocol error" when i try to download my code on to the EVM. Is this error because of the expiry of the evaluation version(my evaluation version expired a few days ago)? If not what else could be the reason? I have followed the instrucations in http://forums.freescale.com/freescale/board/message?board.id=CWDSPCOMM&message.id=697&query.id=11033... , but it didn't solve the issue.
I strongly feel the error is not because of the connectivity problem between the computer and the EVM.
Please let me know the reason as a lot of us who are using this board for a course are facing the same problem.
Solved! Go to Solution.
I have the same issue when I connected the ONCE USB TAP to a MC56H8367EVME board, but when I used the parallel port cable, it worked. I tested two ONCE USB TAP, the same error displayed. The TX/RX led flashed green, but no light from the RUN/PAUSE led. Anything could be wrong?
We are also facing the same problem, but only with some of the target boards. The boards are same in all respects and we are using Parallel port JTAG as well as USB-TAP.
The problem is on some boards, the code gets downloaded instantly without any problems, but on some boards I am getting "Unknown Protocol Error"...
As you pointed out in solution, the cable is the same for all the boards, still this issue is there...
Is there a possibility that the processor chip may be faulty??
You need to find a common pattern here as to why some boards work and others do not. You mention two probe interfaces: USB and parallel. Are the boards working with one interface and not the other? For a system that downloads successfully to a board, can you substitute a faulty board and see what happens? Are all of the boards identical? If so, have you compared the jumpers on the boards that work against the ones that do not?
I have tried with other cables and it me does not work, even I have tried with several computers and they do not work, I have combined the cables in the computers trying with all and it me has not worked....
Is it possible that the EVM has damaged?, The last code programmed in the EVM even works.
The EVM that I use is 8323.
I Tried it with Service Pack's different versions of Windows (SP1, SP2 and SP3) and the result is the same.
I tried It from a computer newly formatted and the mistake persists, please help me, already I am losing the hopes.
Do you get the unknown Protocol error, while some percentage of the code has been downloaded or right at the beginning when the download process begins. This is in reference to the graphic which appears on the screen showing the download progress.
If the error appears while some percentage of the code has been downloaded, then the problem is mostly due to the connectivity issue. Also remove any pci cards connected to the motherboard. Try the above suggestions with an example code from freescale. Also avoid connecting two or cables as it only worsens the problem.
I tried in another EVM the code and the laptop with which I work and it worked correctly, I tried with my EVM and the mistake went out for me again " Unknown Protocol error", I believe that I damage something in my card and more exactly the JTAG, which I am going to do is to try to programme my card with the JTAG of the EVM that works to know if the DSP works still, nevertheless I let's not be how it is exactly the configuration of the jumper in every card not to provoke a damage, please if you know how it is the configuration please explain it to me.
Other one that I still have in doubt is that the this Blocked DSP and I do not know if any method exists to unblock it, in this point I am sure that the problem is in the EVM and not in the PC.
The parallel port wiggler interface is a fidigty thing if you are using laptops or a computer loaded down with peripherals. The voltage driving the parallel port can fall below useful levels if the laptop or PC is driving a slew of external devices. Try uncabling all of your peripherals and see if that corrects the problem.