Codewarrior not connecting, but 56800E Flash Programmer does!

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

Codewarrior not connecting, but 56800E Flash Programmer does!

2,059 Views
Signalds
Contributor II

Hi,

I have a board with a 56F8367 and I have been successfully programming, and debugging it from Codewarrior using a USB Tap interface. For some reason when I set a breakpoint I can not get the debug to stop execution on it. (I may have changed a Codewarrior setting, but I do not know which!) So, attempting to continue working without using breakpoints, I have now come to a point where the Codewarrior will not load a program onto my target device. If I use the 56800E Flash Programmer, It reads memory, can down load programs and verify them without trouble. I can't then get Codewarrior to connect to my board, even if I use the setting 'leave device in debug mode'. What has happened to Codewarrior?

Labels (1)
Tags (1)
0 Kudos
3 Replies

393 Views
Signalds
Contributor II

Further to this problem, I have now tried two USB Taps with three CPU cards and I get the same results (more or less) with them all. One of my CPU cards has been sitting idle for some weeks, so the fact that it responds in an identical way to the others leads me to conclude that BOTH the USB Taps that I have are now unserviceable. (or jiggered, clapped-out call it what-you-will).

Codewarrior must be ok, and the Flash Programmer software must think its doing its job even though it is not programming the chip correctly. I'm going to see if I can get a parallel interface working which should prove my supposition. Anyone else had trouble like this?

0 Kudos

393 Views
J2MEJediMaster
Specialist I

I think we really need to get to the bottom on what is going on here. Please file a service request for this. Click here to do that.

 

---Tom

0 Kudos

393 Views
PauloBarbosa
Contributor I

I´m using MC56F8006, and having the same problem.

Two USB-TAP´s and two 8006demo boards show the same.

They were running well, but suddenly, after setting some breakpoints, the problem had begun.

It seems to be something wrong with the CCS, but I am not able to see what.

 

0 Kudos