Debugger Lock-up

pjv

I believe this post should be directed to PJMonty;

This is a new post regarding a problem previously experienced and posted by others that causes the debugger to freeze in a "RUN" condition as soon as it is invoked.

I have the following description that will cause it to happen, but I'm not yet sure I have all the salient details as that could be quite a bit of work to ferret all that out, and you might just be able to home-in on the problem by my following·description.

On writing·seemingly any·program for an SX28 (have not tried 48/52), one can get the debugger to lock into the "RUN" mode, bypassing "IDLE", if one programs the SX with the "DEBUG" command (have not tried "PROGRAM" command), and then alters the FREQ directive in the source code, and then executes a "DEBUG AGAIN" command. Any subsequent "DEBUG AGAIN" will push the debugger directly into the "RUN" state.

If one subsequently restores the FREQ directive in the source code to the value it was originally programmed with, then the proper "IDLE" sequence returns.

The interesting thing there is that the lock-out after altering the source code frequency appears to continue even after power-ups and shut-downs of the SX target, as well as the IDE's PC.

So what appears to be happening is that someone writes some code, programs it, and then decides to change the FREQency, and can then no longer debug that altered code, even after rebooting.

I could be wrong, but I expect that was not how things were intended to operate.

Also could you have a peek as to why a similar lock-out also occurs when one programs the SX with a high speed FREQ setting. I seem to get such results when using 90 MHz or higher, yet not at all times, or on all hardwares. In the last few days I have been able to operate code very happily with a 110 MHz SX clock setting.

Thanks for your help,

Cheers,

Peter (pjv)
·

Electronegativity

Hi pjv, I was one of the people who poster about the SX key locking up in the debug mode.

In my case it turned out that I fried something on the SX key itself by accidentally applying 5V to one of the oscillator pins.
(I plugged it with only 3 of the header pins going into the SX key)
It would still program and read, but not debug.

Is it possible that your device settings create a conflict between the oscillator mode and frequency?
Not all frequencies are supported by all oscillator modes.
I'm at work now and can't test it, but it seems pretty obvious that a combination like OSC_4MHz and FREQ 50_000_000 would cause a problem.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
I wonder if this wire is hot...

Rsadeika

This is a little bit off topic, but I think it addresses your concern. I tried the following, Device OSC4MHz, means you will be using the internal RC. I left off a freq choice, at compile, the compiler defaults to freq 50_000_000. The big problem would be is that if you code thinking 4MHz, and when the program runs it is really working at 50MHz, I think in some cases depnding on code, you might get some unexpected results. So, if the compiler defaults to 50MHz, I do not think that the compiler designers were trying to ruin the equipment.

Ray