The HP-15C LE will alternate forever between "running" and "Error 0" in this example:
001- f LBL A
002- g LN
003- /
004- g pi
005- -
006- g RTN1 ENTER f SOLVE A -> running
Error 0
running
Error 0
.
.
.
HP-15C LE -- endless loop in SOLVER
|
10-27-2011, 12:45 PM
The HP-15C LE will alternate forever between "running" and "Error 0" in this example:
001- f LBL A
10-27-2011, 01:29 PM
Interesting. The 15C emulator in Nonpareil gets stuck at the first error message, as would be expected. I suppose the original 15C behaves the same. This is strange, since the 15C LE is based on the same firmware. The error handling seems to be influenced in some way.
10-27-2011, 01:51 PM
The emulator just blinks w/o showing 'running'. Why does it blink in the first place?
10-27-2011, 02:20 PM
The HHC2010 15C+ just stops with Error 0.
10-27-2011, 03:33 PM
Quote:
I'd be quite surprised if this was due to a change in the
Gerson, is the alternating between "running" and "Error 0"
Running this on KEMU I find the expected behaviour. The display
10-27-2011, 03:44 PM
Yes, exactly the same rate of the display blinking frequency (according to my measurement).
10-27-2011, 04:16 PM
You can stop it with any key. It looks like a display problem.
10-27-2011, 07:29 PM
No big issue like the PSE bug, I agree, but worth taking into account in a future firmware upgrade.
10-28-2011, 01:07 AM
Quote:
Ah, I suspected it may be rooted in the lcd controller as it
10-28-2011, 03:32 AM
You need to wait long enough after you have written to display memory before you can safely change the mode. The docs say it takes 2 refresh cycles but my experience is that waiting even longer is a good idea. WP 34S does not do a busy wait, the display refresh triggers an interrupt (at roughly 50 Hz) and the number of interrupts is counted. The logic is in the sources in main.c under LCD_interrupt():
/*I'm not using the blink option but I need the display memory for storing intermediate data. If I remove the 'else' part and clear the variable directly after mode switching, display memory gets corrupted. The trick is to wait for another cycle after switching to 'load only' mode. |
« Next Oldest | Next Newest »
|