Differences

This shows you the differences between two versions of the page.

--- sd-8516_assembly_language_part_ii [2026/02/14 02:59] – appledog
+++ sd-8516_assembly_language_part_ii [2026/02/14 03:02] (current) – appledog
@@ Line 210: / Line 210: @@
 == Lesson 11: Debugging Techniques
-There are several ways you can debug programs in SDA assembly. If you look at the console, inserting SED will turn on trace debugging and you will in general be able to see what the CPU is executing (if, debugging has been turned on during compilation). Otherwise you may need to HALT at any particular position and read the registers yourself. However if you can do neither, or are looking for something a bit more helpful, recall the methods of PRINTing that allow you to print messages.
+There are several ways you can debug programs in SDA assembly.
+=== SED/CLD
+In research or development builds, inserting SED will turn on trace debugging and you will be able to see what the CPU is executing. However, for release or community edition builds debugging has been turned off for speed. Therefore if you are interested in debugging your code and the console messages are not helping, you can use the following to help analyze and debug your code:
 === INT 05h IO_PUTNUM
-One way is to use IO_PUTNUM from INT $05 (the CAM/IL interrupt):
+IO_PUTNUM is a CAM/IL function that prints a number (in b) to the screen:
     LDB #10                 ; print a number in b (0-65535)
     LDAH $63                ; IO_PUTNUM
     INT $05
 === INT 05h IO_PRINT_STR
+Similarly, IO_PRINT_STR will print a string followed by a newline.
         LDBLX @hello_world
         LDAH $66                ; IO_PRINT_STR