Is there a bug in the Debug Terminal?
Hi All,
I've been wrestling with a problem for a few days now, and
haven't been able to come up with an explanation.
I've got a program that I haven't been able to condense small
enough to fit in one EEPROM bank, so I've separated in to 8 sections
for the BS2SX. Bank 0 has all declarations, sub routines and
initialization. All other banks have the declarations and
subroutines, but not initialization. I'm not using any scratchpad RAM.
Bank 0 passes to bank 1 which reads an analog input, and
depending on result, passes it to one of the other banks, which
executes it's program, and passes back to bank 1, and the whole
process repeats.
When I break the program down into single bank sections,
everything is fine. I use lots of debug calls to monitor what's going
on. The problems arise when I combine everything and run it in
combination. As long as I have any debug commands, the program locks
up. Comment out the debugs, and away it goes.
Any suggestions?
Thanks,
Robert
I've been wrestling with a problem for a few days now, and
haven't been able to come up with an explanation.
I've got a program that I haven't been able to condense small
enough to fit in one EEPROM bank, so I've separated in to 8 sections
for the BS2SX. Bank 0 has all declarations, sub routines and
initialization. All other banks have the declarations and
subroutines, but not initialization. I'm not using any scratchpad RAM.
Bank 0 passes to bank 1 which reads an analog input, and
depending on result, passes it to one of the other banks, which
executes it's program, and passes back to bank 1, and the whole
process repeats.
When I break the program down into single bank sections,
everything is fine. I use lots of debug calls to monitor what's going
on. The problems arise when I combine everything and run it in
combination. As long as I have any debug commands, the program locks
up. Comment out the debugs, and away it goes.
Any suggestions?
Thanks,
Robert