SX Debug will only RUN
I think I ran into this before, but don't remember a solution.
On my sx28, when I choose Debug, the debug window comes up RUNNING and the options for polling, run, stop etc are grey and I cannot single step through my program.
Any ideas?
Ken
On my sx28, when I choose Debug, the debug window comes up RUNNING and the options for polling, run, stop etc are grey and I cannot single step through my program.
Any ideas?
Ken
Comments
Brian
Bean.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Jon Williams
Applications Engineer, Parallax
Dallas Office
You haven't replied whether any of the suggestions helped, so I thought I'd toss in one more possibility. If you choose "Program", and then choose "Debug (reenter)", you'll find that the debug windows come up, it says, "Running," and all but the "Reset" and "Quit" buttons are greyed out. This is exactly the resulting problem you describe.
The reason is that there is a difference between "Program" and "Debug." When you choose "Program," the only thing sent to the chip is the code you wrote. When you choose "Debug," not only is your code sent, but a little bit of special code is appended and sent to the chip as well. This special code is what enables the SX-Key to properly control the chip being deubgged. Without this code, the IDE just assumes it is there and the SX-Key never gets to tell the debugger windows anything other than that it is alive, well, and waiting for instructions. The actual debugging communication never gets started.
You may already be familiar with all of this, but I know that when I first started using the SXKey IDE, I was not aware of the subtle difference between "Program" and "Debug," and had this sort of thing happen to me more than once. I just figured I could "Program" the chip, then manually jump into the debugger by choosing "Debug (reenter)", and it would all work. Unfortunately, it doesn't, and the IDE has no way of knowing that the chip is not properly prepared for debugging.
Thanks, PeterM
Using SX-Key with just the Mclr pulled high, OSC1, OSC2, Vdd Vss connected, the V2.02 environment goes straight into Running mode. Putting a Break early on in the code does nothing. I did have OSCHS3 and changed that to OSCXT2. Makes no difference. SX-Key is providing the clock. I've tried 4Mhz and 50MHz. Makes no a difference.
It must be the way the circuit is configured,, because a different breadboard works OK with 'Debug' programming the chip and then halting on the Reset.
This is just a simple circuit. +5v and ground going to the SX28 and SX-key. OSC1 OSC2 connected to SX-key. MClr pulled high.
What's going on ?
please double-check what Stephen already mentioned in this thread:
>> Do you have the external clock circuit on the board isolated/removed from the OSC pins?
A while ago, I had the same problem, and then found out that an external clock source was still connected to the OSC1 pin. I'm not sure, but maybe that the SX behaves similar when you have an Xtal or resonator connected to the OSC1 and OSC2 pins. Therefore make sure that at least the OSC1 pin is only connected to the header pin that goes into the SX-Key device, and to nothing else.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Greetings from Germany,
G
I can't get my head around this because the SX-Key configuration works in debug mode with my production boards - so the software is installed on the PC OK, but it won't work with this simple SX28 setup on a breadboard.
I will check carefully on PJ's comments regarding the· way debug is entered.
Ken