30 Oct
2025
30 Oct
'25
5:30 p.m.
On Oct 30, 2025, at 7:43 PM, Glen Slick via cctalk
<cctalk(a)classiccmp.org> wrote:
On Thu, Oct 30, 2025, 4:38 PM Peter Ekstrom via cctalk <
cctalk(a)classiccmp.org> wrote:
Yes that seems likely.
The problem is the "go" command. That isn't like "start" on a
real machine; it just sets the PC and continues. To get the effect of the
"start" switch, do "reset" then "go".
paul
Paul,
Thank you for that. I enabled the history and then loaded and ran my
initial test program:
1 .enabl AMA
2 000000 .asect
3 014000 .=14000
4 014000 012706 002000 start: mov #2000,sp
5 014004 000240 loop: nop
6 014006 000776 br loop
7 014010 000000 halt
8 .end
And it ran for quite a few iterations through the loop, and then:
014004 002000 000000| 000000 NOP
014006 002000 000000| BR 14004
014004 002000 000000| 000000 NOP
014006 002000 000000| BR 14004
014004 002000 000000| 000000 NOP
014006 002000 000000| BR 14004
014004 002000 000000| 000000 NOP
014006 002000 000000| BR 14004
005266 001774 000014| HALT
sim>
- Peter
Just a wild guess, could this possibly be an unhandled LTC interrupt issue?