Can anyone tell me why one pin (pin 7) is not installed on the debug header (P3) on the MCB1343 eval kit board? I've been using this board to develop code for several weeks while waiting for the board we designed (with the same microcontroller as the one on the MCB1343 eval kit board) to show up from our board shop. Now that our board is here, it powers up and seems to work just fine, except for one thing. The problem is that after pressing F10 while stopped on a breakpoint it behaves differently. On the MCB1343 board the debugger stops on the next line of C code, but on our board it seems to act as though I pressed RUN followed by STOP, such that the next line of code the debugger is stopped on may be in any function in any file (that happened to have been executed after pressing F10). Pin 7 on the debug header on our board is grounded. Does that matter?
The header for the ULINK2 on our board is much closer to the microcontroller that it is on the MCB1343 board. Other than that, the circuitry for the two ULINK2 headers would seem to be identical (other than for pin 7 being grounded on our board). Can anyone give me any hints or suggestions for how to make the uVision debugger behave properly on our board, or shed any light on this problem?
Thanks, Dave
The common reason for having one pin missing is that you can then plug that position on the cable, making it impossible to plug in the cable reversed.
Have you tried to look at all the signals, to see if voltage levels or signal quality differs between the two boards?
... is that you can then plug that position on the cable, making it impossible to plug in the cable reversed.
Hence the pin 7 position is labelled 'Key' in the diagram:
http://www.keil.com/peripherals/coresight/connectors.asp
Thanks for the response. As best as I can tell using my o-scope, there are no differences between the shape, min max voltage levels, idle voltage levels, and signal activity between the MCB1343 board and my board on every pin of the debug header.
I tried slowing the debugger clock down too, but that had no effect on the problem.
Any other suggestions...?
Problem solved! The debugger works fine on both boards now.
The problem was all my fault. I got the new board and started bringing it up and added a piece of code that caused the debugger to malfunction, but I didn't know that because I hadn't tried to actually step through code since getting the new board. The problem was that I had enabled the watchdog timer. This morning I tried to run the debugger with the new code on the eval kit board too, and then realized that it no longer worked on that board either. DOH!
After disabling the watchdog, the debugger started working properly on both boards.
Sorry for the false alarm!
Dave :$