Here's the symptoms of the AXEVSM1 post-4000 bug that was difficult for me to trace until now:
When a command (or any part of it) in an X1's program lies at any program memory address $4000 and beyond, and the program steps onto that command, it:
What happens (and what happens with the commands after this command in the program that occupy address $4000 and onwards) depends on the type of command, it's parameters, and which program memory address it is situated on. If the program does move onto the next command (on an address further up), then the above is repeated on that next command, and so on.
Therefore, I can only make an X1-part program up to 2048 bytes because the upper 2048 bytes of the program memory has the problem above. Could someone fix this fault?
When a command (or any part of it) in an X1's program lies at any program memory address $4000 and beyond, and the program steps onto that command, it:
- improperly executes,
- does something not intended,
- misleads it's dependent commands,
- misleads target PC addresses for the next command (When the code window displays "No source line at PC address [PC=####])
- seizes program flow (either stays on the command or PC address 'forever', or terminates with a red error message in the error log).
What happens (and what happens with the commands after this command in the program that occupy address $4000 and onwards) depends on the type of command, it's parameters, and which program memory address it is situated on. If the program does move onto the next command (on an address further up), then the above is repeated on that next command, and so on.
Therefore, I can only make an X1-part program up to 2048 bytes because the upper 2048 bytes of the program memory has the problem above. Could someone fix this fault?
Last edited:
