хITCHхIKER'S гUIDE тO гEOпROGRAMMER ж2.0 ---------------------------------------- тHIS DOCUMENT CONTAINS A COLLECTION OF WORKING DOCUMENTS CONCERNING GEOпROGRAMMER ж2.0. аS THERE IS NO USER'S MANUAL, THESE FILES WILL HAVE TO SUFFICE FOR NEW USERS. еRIC е. дEL сESTO, дECEMBER 1990. гENERAL: FEATURESж2 роунд1 жерсионс жерстатс упграде_то_ж2 тодо гEOаSSEMBLER: GEOаSSEMтодо гEOлINKER: GEOлINKтодо гEOдEBUGGER: GEOдEBUGтодо GEOдEBUGсPECSреадме иNITфORиобUG реунOTES реуBUGS APPтYPES MEMпROTECT CBMаPPS HIDEмODE INTERRUPTS NMI RBOOTвARN VIEWцOMMAND ENVIRONMENT WISHлIST NEW: GEOаSSEMBLER, GEOлINKER, AND GEOдEBUGGER TAKE FULL ADVANTAGE OF EXTRA MEMORY AND 2 мхз PROCESSOR SPEED OF цOMMODORE 128 AND 128д COMPUTERS. нOW: FASTER AND MORE MEMORY-EFFICIENT! гEOпROGRAMMER иMPROVEMENTS иN жERSION 2.0 гEOаSSEMBLER: ONE PROGRAM RUNS UNDER геос 64 анд геос 128 (80 COLUMN ONLY ON 128) FILE SELECTION дб SCROLLS FASTER AND HOLDS 40 FILENAMES SYMBOL TABLE SIZE: ц64 MODE ц128 MODE 3210 MACRO TABLE SIZE: ц64 MODE ц128 MODE XXX NAMES, XXX CHARS 389 NAMES, 8000 CHARS OBJECT CODE SIZE LIMIT: ц64 MODE ц128 MODE XXX BYTES 7999 BYTES NEW ERROR MESSAGES: "TOO MANY LOCAL LABEL REFERENCES" "PHASE ERROR IN VALUE" "PHASE ERROR IN FLAG" "SYNTAX ERROR" ("TOO MANY LOCAL LABELS" CHANGED TO "TOO MANY LOCAL LABEL DEFINITIONS") HAS .TEXT DIRECTIVE TO ASSEMBLE ASCII INTO цбм TEXT CODES. ENDING дб HAS ICON TO RUN THE LINKER гEOлINKER: ONE PROGRAM RUNS UNDER геос 64 анд геос 128 (80 COLUMN ONLY ON 128) FILE SELECTION дб SCROLLS FASTER AND HOLDS 40 FILENAMES жлир LINKS: UP TO 21 MODULES (RESIDENT + 20 OVERLAY) ALLOWS UP TO 20 .REL FILES PER MODULE (OR TOTAL IN сея LINK) SYMBOLS: ц64 MODE ц128 MODE сея / цбм APPLICATIONS: X X жлир APPLICATIONS: X X RESIDENT MODULE: X 3185 SWAP MODULE: X 1375 OBJECT CODE SIZE LIMIT: ц64 MODE ц128 MODE XXX BYTES 7999 BYTES NEW ERROR MESSAGES: "TOO MANY ERRORS" "ILLEGAL FILE NAME" "TOO MANY FILES IN A MODULE" ENDING дб HAS ICON TO RUN THE DEBUGGER гEOдEBUGGER: ONE PROGRAM RUNS UNDER геос 64 анд геос 128 SEE SUB-AREAS BELOW FOR NOTED DIFFERENCES BETWEEN MACHINES SYMBOLS: ц64 MODE ц128 MODE сея / цбм APPLICATIONS: жлир APPLICATIONS: RESIDENT MODULE: SWAP MODULE: сUPERдEBUGGER (IN реу) NOW OFFERS 800 SYMBOLS AND 1к OF MACRO DEFINITIONS. 128 MODE HAS NEW "бACKрAM сUPERдEBUGGER", WHICH HIDES IN бACKрAM. уSER CAN WRITE FULL-SIZED APPLICATIONS IN фRONTрAM. цAN HANDLE 1000 SYMBOLS AND 1к OF MACRO DEFINITIONS. ** тHIS NEW 20к DEBUGGER DOES NOW INCREASE SIZE OF гEOдEBUGGER: THERE IS A DIFFERENTIAL LOADER SCHEME WHICH LOADS IN THE SUPER DEBUGGER AND THEN RELOCATES THE CODE FOR EITHER THE реу OR бACKрAM. NO геос SCREEN ASSUMPTIONS: DISPLAYS DEBUG INFORMATION ON 40-COLUMN SCREEN, AND RETURNS TO WHATEVER SCREEN (AND SCREEN MODE) WAS IN USE WHEN RUNNING USER CODE, OR WHEN ф7 IS PRESSED SEE BELOW ABOUT DEBUGGER'S SHADOW VARS FOR жиц PARAMETERS NEW AND IMPROVED MEMORY READ/WRITE ROUTINE: иNTERCEPTS (AND REDIRECTS TO DEBUGGER SHADOW VARIABLES) READS AND WRITES TO: $0000 AND $0001 (REGISTERS WHICH CONTROL MEMORY MAP) AREA OF ZERO PAGE WHICH IS USED BY DEBUGGER MEMORY AREAS USED BY реу сUPERдEBUGGER (REDIRECTS TO USER MEMORY SWAP AREA IN BANK #0 OF реу) SEVERAL жиц CHIP REGISTERS, INCLUDING $дд00 (CIA2бASE), WHICH CONTROLS жиц MEMORY MAP ON 128: $д500-$д50а (MEMORY MANAGMENT UNIT) $фф00-$фф04 (MORE MMU REGISTERS) $д030 (1мхз/2мхз SWITCH) дISALLOWS READS AND WRITES TO: ALL ром AREAS (SO NO BLEED THROUGH TO рам OCCURS) ANY AREA WHERE DEBUGGER CODE OR SYMBOLS ARE STORED (5 DIFFERENT CASES HERE, DUE TO 3 DEBUGGER TYPES ON 2 MACHINES.) STACK AREA BELOW CURRENT сп (DEBUGGER IS USING) PAGE 3 иря/брк/нми VECTORS USED BY ромS $ффф9 AREA иря/брк/нми VECTORS RAM EXPANSION UNIT'S дма CONTROLLER, IF USING реу сUPERдEBUGGER "CTAB" - EXTERNAL 1кX4 рам USED BY жиц CHIP IN TEXT MODE. оN 128, THERE ARE TWO OF THESE. дEBUGGER USES CTAB #1, AND PREVENTS р/в TO IT. уSER IS FREE TO USE CTAB #0. вHEN ACCESSING рам IN 128 MODE, CALCULATES EFFECTIVE ADDRESS, TAKING BANK NUMBER AND BANK SHARING STATUS INTO ACCOUNT. нEW AND IMPROVED CONTEXT SWITCH (SECTION OF CODE WHICH BRIDGES GAP BETWEEN DEBUGGER AND USER CODE): TRAPS INTERRUPTS WHICH OCCUR WHEN USER'S APPLICATION SWAPS ром IN WITHOUT DISABLING INTERRUPTS; WARNS USER THROUGH DEBUGGER MESSAGE. ON 128 SYSTEM: HANDLES BANK-TO-BANK SWITCHING REQUIRED TO GET FROM EITHER BANK TO ONE OF 3 DEBUGGERS. SAVES AND RESTORES PROCESSOR CLOCK SPEED 1мхз / 2мхз * иMPROVED гETб / пUTб COMMAND: WORKS WITH 1571 AND 1581 DRIVES. * дISASSEMBLES AND TOP-STEPS THROUGH IN-LINE CALLS TO геос CORRECTLY. уSER CAN DISABLE THIS OPTION. * DISPLAYS цпу_дата ($0001) OR цONFIG ($фф00) AS PRIMARY MEMORY MAP REGISTER IN 64 AND 128 MODES RESPECTIVELY. тHIS AFFECTS THE "р" REGISTER DISPLAY COMMAND AND THE "рег" REGISTER DISPLAY/MODIFY COMMAND. мORE ERROR CHECKING DURING FILE LOADS, WITH INFORMATIVE DIALOG BOXES: EXTENSIVE ERROR CHECKS AND GOOD ERROR DIALOG BOXES FOR: DEBUGGER MODULE SWAPS USER APPLICATION LOADS MACRO FILE LOADS SYMBOL FILE LOADS DISPLAYS INFORMATIVE ERROR DIALOG BOX FOR FORMAT ERRORS IN GEOвRITE MACRO DEFINITION FILES. дISPLAYS FILENAME, ERROR MESSAGE, PAGE AND LINE NUMBER. CAN DEBUG APPLICATIONS WHICH TRASH геос APPLICATION MUST HANDLE LOADING ITS OWN CODE IN OVER геос AREAS APPLICATION MUST DISABLE INTERRUPTS OR SET UP ITS OWN INTERRUPT SERVICE ROUTINE. вILL HAVE TO BE CLEVER TO PLACE HIS INTERRUPT VECTOR IN $334 AREA WHEN HIS APPLICATION IS RUNNING UNDER THE DEBUGGER. (и WILL SUPPLY THIS CODE IN THE NEW SAMPLE APP.) уNSEEN COMPLICATIONS WHICH ARE HANDLED: BANK SWITCH CONCERNS DURING: CONTEXT SWITCH йср COMMAND гETб / пUTб COMMANDS RBOOT MAINTAINING SOFTWARE BREAKPOINTS SINGLE STEP BREAKPOINT аND ALL BUGS HAVE BEEN FIXED! сAMPLE фILES: геопрограммер ж2.0 бета тест роунд #1 йULY 29, 1988 *** плеасе реад тхис бефоре ыоу инсталл тхе диск *** цONGRATULATIONS ON BEING SELECTED AS A TESTER FOR GEOпROGRAMMER ж2.0 ! бECAUSE GEOпROGRAMMER IS SUCH A COMPLEX PRODUCT, AND BECAUSE WE WANT TO MAKE SURE IT IS 100% BUG-FREE WHEN WE START SHIPPING IT, WE HAVE DECIDED TO PUT GEOпROGRAMMER ж2.0 THROUGH TWO ROUNDS OF бETA тESTING. тHIS IS ROUND ONE. иN THIS PACKAGE YOU WILL FIND YOUR GEOпROGRAMMER ж2.0 DISK, AND SOME QUICK NOTES ABOUT DIFFERENCES FROM VERSIONS ж1.0 AND ж1.1. уNFORTUNATELY, WE HAVE NOT HAD THE TIME TO FULLY TEST GEOлINKER, AND WE HAVE NOT YET COMPLETED UPGRADING THE COLLECTION OF SAMPLE FILES TO геос ж2.0 LEVEL. тHEREFORE, DO NOT BE CONCERNED IF YOU ENCOUNTER SEVERAL BUGS IN GEOлINKER. йUST LET ME KNOW BY FILLING OUT ONE OF THE ENCLOSED бUG рEPORT FORMS, AND SENDING THE FORM BACK (ALONG WITH SOURCE FILES IF REQUIRED) TO бERKELEY сOFTWORKS AS SOON AS POSSIBLE. оVER THE NEXT THREE TO FOUR WEEKS WE WILL PUT THE FINISHING TOUCHES ON THE PRODUCT, WILL FIX ANY BUGS THAT YOU FIND, AND WILL DO MORE IN-HOUSE TESTING. вE WILL THEN SEND YOU A GEOпROGRAMMER ж2.0 бета 2 DISK, AND ROUND TWO WILL HAVE BEGUN. вE EXPECT THE ENTIRE бETA тEST PERIOD (ROUNDS ONE AND TWO) TO LAST FIVE TO SIX WEEKS. вE DO NOT YET HAVE A DRAFT OF THE GEOпROGRAMMER ж2.0 уSER'S мANUAL аDDENDUM TO SEND YOU, SO THE INFORMATION ON THE FOLLOWING PAGES WILL HAVE TO SUFFICE FOR THE NEXT FEW WEEKS. фROM A USER-INTERFACE STANDPOINT, THERE ARE FEW DIFFERENCES BETWEEN VERSIONS 1.0 AND 2.0, SO IF YOU HAVE NEVER USED THE PRODUCT BEFORE, YOU CAN FOLLOW THE INSTRUCTIONS IN THAT TEXT. иF YOU HAVE BEEN USING GEOпROGRAMMER ж1.0 OR ж1.1 FOR SOME TIME, PLEASE BE SURE TO TRY ASSEMBLING AND LINKING AND SOURCE FILES YOU'VE ALREADY WRITTEN. импортант: YOU WILL NOT BE ABLE TO INSTALL GEOдEBUGGER ON A 1571 DRIVE WHICH IS CONFIGURED AS A 1571. ыOU MUST RE-CONFIGURE THE DRIVE AS A 1541, AND RE-OPEN THE GEOпROGRAMMER ж2.0 DISK, BEFORE YOU CAN INSTALL GEOдEBUGGER. тHIS BUG WILL BE CORRECTED IN THE SOFTWARE YOU RECEIVE IN ROUND TWO. иF YOU HAVE ANY QUESTIONS REGARDING OUR бETA тEST PROGRAM OR THE GEOпROGRAMMER PRODUCT, PLEASE CONTACT кEVIN бOLAND, AND HE WILL CONNECT YOU TO ME OR ONE OF THE OTHER TEAM MEMBERS. вELCOME TO THE TEAM, AND THANKS FOR YOUR HELP! еRIC е. дEL сESTO гEOпROGRAMMER пROJECT лEADER стате оф геопрограммер ж2.0 бета тест роунд 1 GEOаSSEMBLER: сHOULD BE FAIRLY SOLID. бE TOUGH ON IT. GEOлINKER: хAS SOME KNOWN BUGS, BUT SHOULD BE ABLE TO CORRECTLY LINK сея, цбм, AND жлир APPLICATIONS. GEOдEBUGGER: сHOULD BE ROCK SOLID. тORTURE IT. мAKE IT DIE. сAMPLE геос фILES: аRE ON THE DISK, AND HAVE BEEN UPGRADED TO INCLUDE геос 128 AND геос 64 ж2.0 DEFINITIONS. нOT THAT BEFORE YOU INCLUDE THESE FILES, YOU MUST SET THE CONSTANTS ц64 AND ц128 TO труе ($фф) OR фалсе ($00). сAMPLEсEQ: нOT INCLUDED ON бETA рOUND 1 DISK. сAMPLEжLIR: аLL THE REQUIRED FILES ARE ON THE бETA рOUND 1 DISK. нOTE THAT THE сAMжLIRеQUATES FILE SETS THE ц64 AND ц128 CONSTANTS. тHESE ARE PRESENTLY SET SO THAT THE APPLICATION WILL ONLY RUN UNDER ц64 геос. иF YOU ARE TESTING ON A ц128, BE SURE TO CHANGE THESE CONSTANT DEFINITIONS BEFORE YOU BEGIN. аLSO- THERE ARE SEVERAL NEW ADDITIONS TO THE сAMPLEжLIR FILES, SUCH AS SUPPORT FOR KEYBOARD SHORTCUTS IN THE MENUS. ыOU CAN EXPECT TO FIND SOME PRETTY OBVIOUS BUGS IN SOME OF THESE NEW FEATURES. сAMPLEда: нOT INCLUDED ON бETA рOUND 1 DISK. сAMPLEцбм: тHIS IS A NEW SAMPLE FILE, TO DEMONSTRATE THE NON-геос CAPABILITY OF GEOдEBUGGER ж2.0. нOT INCLUDED ON бETA рOUND 1 DISK. геопрограммер импрожементс иN жERSION 2.0 GEOаSSEMBLER: ONE PROGRAM RUNS UNDER геос 64 анд геос 128 (80 COLUMN ONLY ON 128) FILE SELECTION дб SCROLLS FASTER AND HOLDS 239 FILENAMES IMPROVED OUTPUT FILE CREATION: FASTER ASSEMBLIES, DELETES PARTIAL FILES AFTER DISK ERRORS HAS .TEXT DIRECTIVE TO ASSEMBLE ASCII INTO цбм TEXT CODES. EXAMPLE: .TEXT "тHIS IS TEXT FOR THE цбм TEXT SCREEN" ц64 MODE ONLY: WILL GENERATE UP TO 3584 CODE BYTES MAX NUMBER OF MACRO DEFINITIONS: 100 SIZE OF MACRO STORAGE BUFFER: 3560 SYMBOL TABLE HOLDS 1151 SYMBOLS ц128 MODE ONLY: WILL GENERATE UP TO 7670 CODE BYTES MAX NUMBER OF MACRO DEFINITIONS: 389 SIZE OF MACRO STORAGE BUFFER: 12520 SYMBOL TABLE HOLDS 3208 SYMBOLS GEOлINKER: ONE PROGRAM RUNS UNDER геос 64 анд геос 128 (80 COLUMN ONLY ON 128) FILE SELECTION дб SCROLLS FASTER AND HOLDS 210 FILENAMES IMPROVED OUTPUT FILE CREATION: FASTER LINKS, DELETES PARTIAL FILES AFTER DISK ERRORS IMPROVED .LNK FILE PARSING: ALLOWS MULTIPLE PAGE .LNK FILES, GIVES MORE INFORMATIVE ERROR MESSAGES .сым FILE CAN HAVE 60 LINES/PAGE жлир LINKS: UP TO 21 MODULES (RESIDENT + 20 OVERLAY) ALLOWS UP TO 20 .REL FILES PER MODULE (OR TOTAL IN сея LINK) ц64 MODE ONLY: BUFFER FOR COMPACTED .лнк FILE HAS 3840 BYTES CODE BUFFER IS 3584 BYTES RESIDENT SYMBOL TABLE HOLDS 1274 SYMBOLS SWAP MODULE SYMBOL TABLE HOLDS 850 SYMBOLS DURING сея AND цбм APPLICATION LINKS, COMBINES SYMBOL TABLES TO ALLOW A TOTAL OF 2124 SYMBOLS ц128 MODE ONLY: BUFFER FOR COMPACTED .лнк FILE HAS 3840 BYTES CODE BUFFER IS 7670 BYTES RESIDENT SYMBOL TABLE HOLDS 3217 SYMBOLS SWAP MODULE SYMBOL TABLE HOLDS 1740 SYMBOLS (STATE OF THE PRODUCT, CONTINUED...) GEOдEBUGGER: IMPROVED ERROR DETECTION WHEN PARSING .дбм FILES, PRINTS PAGE AND LINE NUMBER WITH ERROR MESSAGE CAN TOP-STEP OVER IN-LINE CALLS TO геос ROUTINES SUCH AS I_рECTANGLE мINI дEBUGGER (ц64/ц128) OCCUPIES $3500-$5ффф, PLUS $334-$3FF IN BANK 1 (HOLD рун/стоп KEY DOWN WHILE RUNNING GEOдEBUGGER TO INVOKE THE MINI-DEBUGGER.) сUPER дEBUGGER (ц64/ц128 WITH реу) MACRO BUFFER IS 1024 BYTES SYMBOL TABLE HOLDS 731 SYMBOLS OCCUPIES SPACE IN реу BANK 0, PLUS $334-$3FF IN BANK 1 (иF YOU HAVE A рам еьпансион унит ON YOUR SYSTEM, THIS DEBUGGER WILL AUTOMATICALLY LOAD WHEN YOU RUN GEOдEBUGGER. бY HOLDING рун/стоп OR спаце DOWN, YOU CAN OVERRIDE THIS TO RUN THE мINI-дEBUGGER OR бACKрAM сUPER-дEBUGGER.) бACKрAM сUPER дEBUGGER (ц128 ONLY) (128 MODE HAS NEW "бACKрAM сUPERдEBUGGER", WHICH HIDES IN бACKрAM. уSER CAN WRITE FULL-SIZED APPLICATIONS IN фRONTрAM.) цAN HANDLE 1000 SYMBOLS AND 1к OF MACRO DEFINITIONS. MACRO BUFFER IS 1024 BYTES SYMBOL TABLE HOLDS 910 SYMBOLS OCCUPIES $2000-$9ффф IN ц128 BANK 0, PLUS $334-$3FF IN BANK 1 (иF YOU HAVE AN реу ON YOUR ц128 SYSTEM, YOU MUST HOLD THE спаце KEY DOWN WHILE RUNNING GEOдEBUGGER TO INVOKE THE бACKрAM сUPER-дEBUGGER.) аDDITIONAL TECHNICAL INFORMATION ON GEOдEBUGGER ж2.0 (ыOU MIGHT FIND THIS INFORMATION INTERESTING.) NO геос SCREEN ASSUMPTIONS: DISPLAYS DEBUG INFORMATION ON 40-COLUMN SCREEN, AND RETURNS TO WHATEVER SCREEN (AND SCREEN MODE) WAS IN USE WHEN RUNNING USER CODE, OR WHEN ф7 IS PRESSED SEE BELOW ABOUT DEBUGGER'S SHADOW VARS FOR жиц PARAMETERS NEW AND IMPROVED MEMORY READ/WRITE ROUTINE: иNTERCEPTS (AND REDIRECTS TO DEBUGGER SHADOW VARIABLES) READS AND WRITES TO: $0000 AND $0001 (REGISTERS WHICH CONTROL MEMORY MAP) AREA OF ZERO PAGE WHICH IS USED BY DEBUGGER MEMORY AREAS USED BY реу сUPERдEBUGGER (REDIRECTS TO USER MEMORY SWAP AREA IN BANK #0 OF реу) SEVERAL жиц CHIP REGISTERS, INCLUDING $дд00 (CIA2бASE), WHICH CONTROLS жиц MEMORY MAP ON 128: $д500-$д50а (MEMORY MANAGMENT UNIT) $фф00-$фф04 (MORE MMU REGISTERS) $д030 (1мхз/2мхз SWITCH) дISALLOWS READS AND WRITES TO: ALL ром AREAS (SO NO BLEED THROUGH TO рам OCCURS) ANY AREA WHERE DEBUGGER CODE OR SYMBOLS ARE STORED (5 DIFFERENT CASES HERE, DUE TO 3 DEBUGGER TYPES ON 2 MACHINES.) STACK AREA BELOW CURRENT сп (DEBUGGER IS USING) PAGE 3 иря/брк/нми VECTORS USED BY ромS $ффф9 AREA иря/брк/нми VECTORS RAM EXPANSION UNIT'S дма CONTROLLER, IF USING реу сUPERдEBUGGER "CTAB" - EXTERNAL 1кX4 рам USED BY жиц CHIP IN TEXT MODE. оN 128, THERE ARE TWO OF THESE. дEBUGGER USES CTAB #1, AND PREVENTS р/в TO IT. уSER IS FREE TO USE CTAB #0. вHEN ACCESSING рам IN 128 MODE, CALCULATES EFFECTIVE ADDRESS, TAKING BANK NUMBER AND BANK SHARING STATUS INTO ACCOUNT. нEW AND IMPROVED CONTEXT SWITCH (SECTION OF CODE WHICH BRIDGES GAP BETWEEN DEBUGGER AND USER CODE): TRAPS INTERRUPTS WHICH OCCUR WHEN USER'S APPLICATION SWAPS ром IN WITHOUT DISABLING INTERRUPTS; WARNS USER THROUGH DEBUGGER MESSAGE. ON 128 SYSTEM: HANDLES BANK-TO-BANK SWITCHING REQUIRED TO GET FROM EITHER BANK TO ONE OF 3 DEBUGGERS. SAVES AND RESTORES PROCESSOR CLOCK SPEED 1мхз / 2мхз * иMPROVED гETб / пUTб COMMAND: WORKS WITH 1571 AND 1581 DRIVES. * дISASSEMBLES AND TOP-STEPS THROUGH IN-LINE CALLS TO геос CORRECTLY. уSER CAN DISABLE THIS OPTION. * DISPLAYS цпу_дата ($0001) OR цONFIG ($фф00) AS PRIMARY MEMORY MAP REGISTER IN 64 AND 128 MODES RESPECTIVELY. тHIS AFFECTS THE "р" REGISTER DISPLAY COMMAND AND THE "рег" REGISTER DISPLAY/MODIFY COMMAND. аDDITIONAL TECHNICAL INFORMATION ON GEOдEBUGGER ж2.0 (CONTINUED) мORE ERROR CHECKING DURING FILE LOADS, WITH INFORMATIVE DIALOG BOXES: EXTENSIVE ERROR CHECKS AND GOOD ERROR DIALOG BOXES FOR: DEBUGGER MODULE SWAPS USER APPLICATION LOADS MACRO FILE LOADS SYMBOL FILE LOADS DISPLAYS INFORMATIVE ERROR DIALOG BOX FOR FORMAT ERRORS IN GEOвRITE MACRO DEFINITION FILES. дISPLAYS FILENAME, ERROR MESSAGE, PAGE AND LINE NUMBER. CAN DEBUG APPLICATIONS WHICH TRASH геос APPLICATION MUST HANDLE LOADING ITS OWN CODE IN OVER геос AREAS APPLICATION MUST DISABLE INTERRUPTS OR SET UP ITS OWN INTERRUPT SERVICE ROUTINE. вILL HAVE TO BE CLEVER TO PLACE HIS INTERRUPT VECTOR IN $334 AREA WHEN HIS APPLICATION IS RUNNING UNDER THE DEBUGGER. (и WILL SUPPLY THIS CODE IN THE NEW SAMPLE APP.) уNSEEN COMPLICATIONS WHICH ARE HANDLED: BANK SWITCH CONCERNS DURING: CONTEXT SWITCH йср COMMAND гETб / пUTб COMMANDS RBOOT MAINTAINING SOFTWARE BREAKPOINTS SINGLE STEP BREAKPOINT аND ALL BUGS HAVE BEEN FIXED! аDDITIONAL TECHNICAL INFORMATION ON GEOдEBUGGER ж2.0 (CONTINUED) хOW гEOдEBUGGER MANAGES MACHINE-DEPENDENT MEMORY-MAP ENVIRONMENT INFORMATION тHE DEBUGGER CARRIES MEMORY-MAP ENVIRONMENT INFORMATION, WHICH IS MACHINE- DEPENDENT, AROUND IN GENERIC VARIABLES SUCH AS APPбANKиNFO1 AND APPбANKиNFO2. тHIS WAY, THE ROUTINES WHICH JUST MOVE THIS INFORMATION AROUND (BUT DON'T DIRECTLY USE IT) ARE MACHINE-INDEPENDENT. еXECUTION еNVIRONMENT: вHEN THE DEBUGGER STOPS EXECUTION OF AN APPLICATION (ресторе PRESSED OR сбп HIT), THE USER'S "EXECUTION ENVIRONMENT" IS SAVED. тHIS INCLUDES: PROCESSOR REGISTER AND FLAG VALUES пц ADDRESS CURRENT BANK INFORMATION ZERO PAGE VARIABLES STACK INFORMATION вE CALL THE пц ADDRESS AND ITS MEMORY-MAP INFORMATION THE "еXECUTION еNVIRONMENT" OR MORE SIMPLY, THE "пц POINTER". жIEWING еNVIRONMENT: оNCE THE DEBUGGER HAS STOPPED AN APPLICATION, THE "VIEWING ENVIRONMENT" IS THE SAME AS THE "EXECUTION ENVIRONMENT". тHIS MEANS THAT ALL OF THE MEMORY EXAMINATION AND MODIFICATION COMMANDS USE THE SAME MEMORY-MAP INFORMATION AS THE еXECUTION еNVIRONMENT. тHROUGH USE OF THE сетжиев COMMAND, THE VIEWING ENVIRONMENT CAN BE CHANGED. ыOU CAN SET UP A NEW MEMORY-MAP CONFIGURATION, AND THEN USE THE MEMORY EXAMINATION AND MODIFICATION COMMANDS TO READ/WRITE MEMORY IN THIS NEW CONFIGURATION. вHEN YOU GIVE THE го COMMAND TO RESUME EXECUTION, THE DEBUGGER RESTORES THE EXECUTION ENVIROMENT, AND YOUR PROGRAM CONTINUES EXECUTION. вE CALL THE VIEWING ADDRESS AND ITS ENVIRONMENT THE "лц POINTER". ------------------------------------------------------------------------------- аSPECTS OF гEOдEBUGGER WHICH MUST CHANGE ACCORDING TO MACHINE-DEPENDENCIES IN ж2.0, TO REMAIN COMPATIBLE WITH ж1.0. (кILL THESE IN ж3.0.) рEGISTER COMMAND: DISPLAYS пц ADDRESS, HIGHLIGHTS ADDRESS IF EFFECTIVE ADDRESS OF пц (CONSIDERING пц BANK INFO) IS BANK 0. DISPLAYS цпу_дата VALUE (иT REALLY SHOULD NOT DO THIS ANYMORE, BUT и AM TRYING TO MAINTAIN COMPATABILITY WITH ж1. 64: READ DIRECTLY FROM APPбANKиNFO1 128: [7-3,0]: DIRECT READ FROM MEMORY [21]: SHADOW WITH APPцпу_б21 аDDITIONAL TECHNICAL INFORMATION ON GEOдEBUGGER ж2.0 (CONTINUED) рEGISTER оPEN цOMMAND: ..INCLUDES мм REGISTER: IS цпу_дата. (тO BE COMPATIBLE WITH ж1) 64: DIRECTLY READ/WRITE TO APPбANKиNFO1 128: [7-3,0]: DIRECTLY р/в TO MEMORY [21]: SHADOW WITH APPцпу_б21 ------------------------------------------------------------------------------- аSPECTS OF гEOдEBUGGER WHICH ARE MACHINE-INDEPENDENT. мEMORY EXAMINATION AND MODIFICATION: BANK COMMAND: AFFECTS лц'S BANK INFO: CURбANKиNFO1 AND CURбANKиNFO2 OPEN MODES: USES лц'S BANK INFO HIGHLIGHTS ADDRESS IF IS IN PHYSICAL BANK 0 DUMP COMMAND: USES лц'S BANK INFO HIGHLIGHTS ADDRESS IF IS IN PHYSICAL BANK 0 MOVE/FILL/DIFF/FIND: USES лц'S BANK INFO HIGHLIGHTS ADDRESS IF IS IN PHYSICAL BANK 0 @ AND @@ OPERATORS: USES лц'S BANK INFO сINGLE AND тOP-STEP BREAKPOINTS: MAINTAIN THEIR OWN BANK INFORMATION (COPIED FROM пц BANK INFO BEFORE EXECUTION BEGUN) сOFTWARE бREAKPOINTS: MAINTAIN THEIR OWN BANK INFORMATION (COPIED FROM пц BANK INFO BEFORE EXECUTION BEGUN) пц COMMAND: WITHOUT ARGUMENT: COPY пц ADDRESS AND BANK INFO TO лц (RESTORES EXECUTION ENVIRONMENT) WITH ARGUMENT: (SAME AS SETTING пц IN OPEN MODE) SET пц ADDRESS = ARGUMENT SET пц BANK INFO = лц BANK INFO аDDITIONAL TECHNICAL INFORMATION ON GEOдEBUGGER ж2.0 (CONTINUED) (тхис портион оф тхе геодебуггер тест лист ис супплиед то гиже ыоу ан идеа оф хов тхе меморы-енжиронмент манагемент цоммандс ворк.) 4.10 мEMORY-мAP еNVIRONMENT мANAGEMENT 4.10.1 инитжиев COMMAND: COPIES THE MEMORY-MAP ENVIRONMENT INFO FROM THE EXECUTION VARIABLES (пц) TO THE DISPLAY/MODIFY VARIABLES (лц). уSED WHEN USER HAS BEEN VIEWING DIFFERENT BANKS, AND NOW WANTS TO EXAMINE THE MEMORY MAP AS IT WAS WHEN WE STOPPED EXECUTION. 64 128 128 реу реу бацк ___ ___ ___ INITVIEW NO ARGUMENTS. дISPLAYS пц LINE AND ENVIRONMENT INFO. ___ ___ ___ NOTE THAT пц COMMAND HAS SAME EFFECT OF COPYING ENVIRONMENT INFORMATION, BUT DOES NOT DISPLAY MEMORY-MAP INFO WHEN DONE. ___ ___ ___ VERIFY THAT "иж" COMMAND ALIAS WORKS 4.10.2 сетжиев COMMAND: SETS THE MEMORY-MAP ENVIRONMENT FOR THE DISPLAY/MODIFY COMMANDS. дISPLAYS NEW ENVIRONMENT INFO IF NO ERROR. FORMAT: SETVIEW <мEMмAP1> [, <мEMмAP2> ] ___ ___ ___ SETVIEW <мEMмAP1> SETS APPмEMмAP1. ___ ___ ц128: SHOULD NOT AFFECT APPмEMмAP2 SETVIEW <мEMмAP1>,<мEMмAP2> ___ ___ ц128: SETS APPмEMмAP1 AND APPмEMмAP2. ___ ___ ц128: VERIFY THAT б7 AND б6 ARE CLEARED IN APPмEMмAP2 (THIS VARIABLE MUST HAVE 0'S IN THOSE POSITIONS) ___ ___ ___ DISPLAYS NEW ENVIRONMENT INFO CORRECTLY ___ ___ ___ ERROR IF NO ARGUMENTS GIVEN ___ ___ ___ ERROR IF EITHER VALUE GREATER THAN 255. ___ ___ ___ VERIFY THAT "сж" COMMAND ALIAS WORKS 4.10.3 жиев COMMAND: DISPLAYS CURRENT MEMORY-MAP ENVIRONMENT INFO. ___ ___ ___ VIEW NO ARGUMENTS REQUIRED ___ ц64: ONLY DISPLAYS 1ST OF 2 VALUES ON EACH LINE ___ ___ ц128: DISPLAYS BOTH VALUES ON EACH LINE ___ ___ ___ VERIFY THAT "жв" COMMAND ALIAS WORKS 4.10.4 усежиев COMMAND: FORCES THE DISPLAY/MODIFY ENVIRONMENT UPON THE EXECUTION ENVIRONMENT. дISPLAYS NEW INFO WHEN FINISHED. ___ ___ ___ USEVIEW NO ARGUMENTS REQUIRED ___ ___ ___ VERIFY THAT "уж" COMMAND ALIAS WORKS 4.10.5 б0 COMMAND: SET DISPLAY/MODIFY ENVIRONMENT VARIABLE SO THAT ALL OF BANK 0 IS VISIBLE. дISPLAYS NEW INFO WHEN FINISHED. ___ ___ ___ B0 NO ARGUMENTS REQUIRED 4.10.6 б1 COMMAND: SET DISPLAY/MODIFY ENVIRONMENT VARIABLE SO THAT ALL OF BANK 1 IS VISIBLE. дISPLAYS NEW INFO WHEN FINISHED. ___ ___ ___ B1 NO ARGUMENTS REQUIRED 4.10.7 мEMORY-мAP еNVIRONMENT мANAGEMENT... тест: VIEW ENVIRONMENT SAME AS EXECUTION ENVIRONMENT WHEN SOFTWARE BREAKPOINT IS HIT OR ресторе IS PRESSED. ___ ___ ___ USE VIEW COMMAND, VALUES ON TWO LINES SHOULD BE EQUAL. аDDITIONAL TECHNICAL INFORMATION ON GEOдEBUGGER ж2.0 (CONTINUED) тест: THE FOLLOWING COMMANDS, MAKING SURE THAT THEY USE THE VIEW ENVIRONMENT MEMORY-MAP INFORMATION WHEN ACCESSING MEMORY. ___ ___ ___ "а" OPEN MODE ___ ___ ___ "м" OPEN MODE ___ ___ ___ DEPOSITING VALUES WHEN IN AN OPEN-MODE ___ ___ ___ @ AND @@ OPERATORS IN EXPRESSIONS ___ ___ ___ думп ___ ___ ___ дис ___ ___ ___ н ___ ___ ___ в ___ ___ ___ принт ___ ___ ___ филл / цопы / дифф / финд тест: THAT EXECUTION ENVIRONMENT IS USED WHEN EXECUTION IS RE-STARTED. ___ ___ ___ NEED TEST CODE FOR THIS... тест: (ц128 ONLY) IN THE FOLLOWING COMMANDS, AN ADDRESS SHOWS UP HIGHLIGHTED IF THE EFFECTIVE ADDRESS (CONSIDERING рам SHARING) IS IN BANK 0. хINT: TO SET лц TO BANK 0, USE б0 COMMAND. тO SET пц TO BANK 0, USE б0 FOLLOWED BY усежиев COMMAND. ___ ___ "р" ___ ___ "а" OPEN MODE ___ ___ "м" OPEN MODE ___ ___ дис, в, н, ETC. ___ ___ думп ___ ___ дифф ___ ___ финд ___ ___ хисторы ------------------------------------------------------------------------------ ж1.000 11/2/87 сENT TO хлс, BUT NEVER MASTERED DUE TO 128 CRASHES. цомплете мастер релеасе тапе маде 11/11/87. тHIS жерсион 1.0 (11/2/87) RELEASE WAS SENT TO хлс, BUT WAS NEVER MASTERED BECAUSE бRIAN HAD ME CHANGE THE 128 ENABLE BIT IN EACH APPLICATION'S HEADER BLOCK. сEE ж1.010 FOR LIST OF KNOWN BUGS. ------------------------------------------------------------------------------ ж1.010 11/18/87 сENT TO змаг. дUPLICATED AS гEOпROGRAMMER ж1.0. 4000 SHIPPED WITHOUT ERRATA SHEET. еRRATA ITEMS POSTED TO ялинк 1/25/88 оNLY DIFFERENCE FROM ж1.000: BITS SET IN HEADERS SO DOES NOT CRASH геос 128. (иTEMS MARKED патцх WERE CORRECTED WITH пATCH2.88 PROGRAM TO CREATE ж1.1. иTEMS MARKED латер WERE NOT FIXED UNTIL ж2.0.) кNOWN BUGS IN 11.18 RELEASE, WHICH WERE CORRECTED WITH пATCH2.88 PROGRAM. лINKER HAS TROUBLE CREATING жлир FILES. бUG: VARIABLE CALLED FILEвRITTEN NOT SET TO труе, SO бам IS RE-READ FROM DISK INSTEAD OF USING MORE RECENT бам WHICH IS IN MEMORY. аSSEMBLER HAS TROUBLE WITH LOCAL LABELS AFTER PARSING A BITMAP OR ROUTINE LONGER THAN 254 BYTES. бUG: TWO BRANCHES SKIP TOO FAR AND MISS CODE WHICH RESETS A VARIABLE. аSSEMBLER HAS TROUBLE WITH BITMAPS. бUG: UNCOMPACTING WRONG. лINKER HAS TROUBLE WITH .RAMSECTS IN рESIDENT AND сWAP MODULES. кNOWN BUGS IN 11.18 RELEASE, NOT CORRECTED UNTIL ж2.0: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - аSSEMBLER (THINGS TO MENTION IN ERRATA LIST): иN ASSEMBLER, IF ENCOUNTER DISK ERROR, SHOULD ATTEMPT TO CLOSE ANY OPENED FILES SO DISK IS NOT INCONSISTENT. еррата: WARN THEM, TELL THEM TO DELETE FILES AND VALIDATE DISK. аSSEMBLER HAS TROUBLE UNCOMPACTING BITMAPS OF LESS THAN 18 PIXELS HEIGHT еррата: DON'T DO IT иF A ROUTINE IS LARGE ENOUGH TO COME CLOSE TO THE END OF CODEбUFFER, IT COULD OVERFLOW INTO THE еXTERNAL рEFERENCE бUFFER. еррата: KEEP ROUTINES SMALLER THAN APPROX 250 BYTES (ASK TED) аSSEMBLER: DOES NOT PRINT CORRECT PAGE NUMBER IN ERROR MESSAGES REFERRING TO BRANCH INSTRUCTIONS. аLSO COUNTS MACRO EXPANSION LINES, SO MOST ERROR MESSAGES ARE OFF. еррата: IF YOU GET A LOCAL LABEL ERROR, CONSIDER THAT IT MIGHT BE ON THE PREVIOUS PAGE (OR PAGE BEFORE THAT). оTHER ERRORS: CONSIDER MACRO EXPANSIONS WHEN COUNTING LINE NUMS. вHEN ASSEMBLING лда зп,ы (WHICH DOES NOT EXIST), ASSEMBLER SHOULD SUBSTITUTE лда абс,ы. еррата: WARN AND TELL THEM HOW TO GET AROUND IT. LDA #рELOCжALUE OR .BYTE рELOCжALUE PASSES RELOCATION POINTER TO LINKER WHICH TRASHES WORD IN CODE. аSSEMBLER SHOULD GENERATE ERROR MESSAGE. еррата: USE LOW BYTE OPERATOR: "[" BEFORE ANY SUCH REFERENCES. "*" OPERATOR ALWAYS GETS PSECT VALUE, SO DOES NOT WORK IN RAMSECT OR ZSECT AREAS. еррата: WARN THEM иN ASSEMBLER, SCREEN COLORS NOT SET CORRECTLY, SO CAN SEE иNSORT WORKING BY CHANGING YOUR SCREEN COLORS. еррата: TELL THEM TO CLOSE THEIR EYES DURING ASSEMBLIES. дOES NOT LOOK FOR гEOвRITE CORRECTLY WHEN OPENING ERROR FILE: SHOULD LOOK FOR PERMANENT NAME STRING. еррата: DO NOT RENAME YOUR GEOвRITE. аSSEMBLER: (THINGS и WAS TOLD ABOUT TOO LATE TO MENTION THEM IN THE ERRATA LIST) "+" OPERATOR DOES NOT WORK IN UNARY CASE пHASE еRROR: JSR $0045 DOES NOT ASSEMBLE CORRECTLY. вHEN AN UNRESOLVED SYMBOL IS USED AS THE SECOND OPERAND IN AN EXPRESSION THAT INVOLVES A DIVISION OR A MODULUS, THE EXPRESSION WILL NOT BE PASSED TO THE LINKER. иNSTEAD, IT WILL GENERATE AN ERROR IN THE ASSEMBLER. аSSEMBLER: (THINGS NOT TO MENTION IN ERRATA LIST) аSSEMBLER'S BITMAP DECOMPACTION CODE DOES NOT HANDLE бIGцOUNT VALUES CORRECTLY. нOT A BIG PROBLEM: PHOTO SCRAPS UP TO геос ж1.3 WORK OK. иF THERE IS ANY TEXT AFTER A .ENDM, PRODUCES "хIDDEN еRROR". фILE SELECTION дб BUG: COULD RUN PROGRAM WITHOUT CHOOSING A FILE. аSSEMBLER SHOULD NOT PASS пASS1, пICв, AND пICх SYMBOLS TO LINKER. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - лINKER: (THINGS TO MENTION IN ERRATA LIST) иN LINKER, IF ENCOUNTER DISK ERROR, SHOULD ATTEMPT TO CLOSE ANY OPENED FILES SO DISK IS NOT INCONSISTENT. еррата: WARN THEM, TELL THEM TO DELETE FILES AND VALIDATE DISK. лINKER: WHEN USING фREEбLOCK TO DELETE HEADER BLOCKS FROM цбм FILES, DOES NOT REALIZE THAT 1.2 KERNAL DOES NOT HAVE CODE FOR 'фREEбLOCK'. еррата: WARN THEM, SUGGEST THEY UPGRADE TO геос 1.3. лINKER: DOES NOT CORRECT FOR ILLEGAL .REL FILENAMES. дOES NOT GIVE CORRECT ERROR FOR .REL FILE NOT FOUND. дOES NOT STOP AFTER FIRST 10 .REL FILES IN A MODULE, PRODUCING A BUG. еррата: WARN THEM NOT TO HAVE MORE THAN 10 .REL FILES PER MODULE. оN ONE-DRIVE SYSTEM, LINKER DOES NOT DISPLAY "SYM FILE" DIALOG BOX. еррата: TELL THEM TO BUY A SECOND DRIVE. иN LINKER, SCREEN COLORS NOT SET CORRECTLY, SO CAN SEE иNSORT WORKING BY CHANGING YOUR SCREEN COLORS. еррата: TELL THEM TO CLOSE THEIR EYES DURING ASSEMBLIES. дOES NOT LOOK FOR гEOвRITE CORRECTLY WHEN OPENING ERROR FILE: SHOULD LOOK FOR PERMANENT NAME STRING. еррата: DO NOT RENAME YOUR GEOвRITE. лINKER: (THINGS и WAS TOLD ABOUT TOO LATE TO MENTION THEM IN THE ERRATA LIST) "+" OPERATOR DOES NOT WORK IN UNARY CASE, AND "//" OPERATOR DOES NOT WORK. еррата: и DIDN'T HEAR ABOUT THIS UNTIL IT WAS TOO LATE. лINKER: (THINGS NOT TO MENTION IN ERRATA LIST) лINKER IS NOT CLEARING зп FLAG BIT, SO IN DEBUGGER SOME SYMBOLS HAVE A GRAPHICS CHARACTER IN POSITION 3. лINKER DOES NOT STOP AT 99 ERRORS. фILE SELECTION дб BUG: COULD RUN PROGRAM WITHOUT CHOOSING A FILE. вHEN .LNK FILE IS WRITE-PROTECTED, LINKER DISPLAYS дб. цLICK ON IGNORE TO CONTINUE. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - дEBUGGER: (MENTION IN ERRATA LIST:) SOME SYMBOLS SHOW UP WITH GRAPHICS CHAR IN POSITION 3. иS REALLY A LINKER BUG. еррата: WARN THEM, SUGGEST THEY USE * WILDCARD DURING SEARCHES. дEBUGGER: (DO NOT MENTION IN ERRATA LIST:) DEBUGGER FILE-SELECT дб DOES NOT DISPLAY WRITE-PROTECTED FILES DEBUGGER DOES NOT LOAD прг FILES WHICH ARE WRITE-PROTECTED CORRECTLY DEBUGGER IS NOT SAVING OR RESTORE DESKтOP'S ром VECTORS ($314-$318) CORRECTLY. иS NOT PREVENTING WRITES TO $314-$315. нOT A BIG PROBLEM: MY VECTORS AT $314 AND $316 ARE THE SAME ANYWAY. фIXED 2/1/88 BY CORRECTING BASбркжEC AND BASиряжEC IN CONSTANTS FILE. нEW CODE INSTALLED IN мAY TO HANDLE THIS DIFFERENTLY. реу сUPERдEBUGGER ONLY ALLOWS 768 SYMBOLS, WHERE IT COULD HAVE 870. реу сUPERдEBUGGER DOES NOT GETB/PUTB FROM 1571 DRIVE CORRECTLY. IF YOU HOLD стоп KEY DOWN WHEN DEBUGGER TURNS ON TEXT SCREEN DURING INITIAL BOOT SEQUENCE, IT ABORTS ITS INIT CYCLE, AND LEAVES YOU AT THE COMMAND PROMPT WITH THINGS SCREWY. нOTE: бOTH MONITORS IN гEOдEBUGGER HAVE AN UNUSED ROUTINE WHICH TAKES 18 BYTES. гоод лоцатион фор патцх суброутинес! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - сAMPLE фILES: (MENTION IN ERRATA LIST) иN сAMжLIR.LNK, SHOULD HAVE $3000 INSTEAD OF $5000 FOR VARIABLE AREA. (CAUSES MINI-DEBUGGER TO CRASH) иN сAMсEQ.LNK, SHOULD HAVE $3000 INSTEAD OF $5000 FOR VARIABLE AREA. (дOES NOT CAUSE MINI-DEBUGGER TO CRASH BECAUSE NO VARS ARE USED.) иN сAMсEQ AND сAMжLIRрES, "жертицал" UNDER мENUтABLE SHOULD BE "суб_мену". - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - мANUAL: (MENTION IN ERRATA) .HEADER STRUCTURES ARE CHECKED FOR 12 STATEMENTS, NOT 11. дEBUGGER IS NOT AS ISOLATED AS WE MAKE IT SOUND: STILL USES геос RAM EXPANSION ROUTINES. дEBUGGER USES $340-$3FF, NOT $350-$3FF. апп_рам == $400 HAS BEEN CHANGED TO апп_рам = $400. рUNTO (RT) COMMAND WILL ONLY DISPLAY геос SCREEN IF OPTION 5 IS ENABLED (G1 COMMAND). тHE SAMPLE APPLICATION CANNOT BE RE-RUN WITH GO $400. пAGE 7-11 INCORRECT IN STATING THAT RUNTO WILL SHOW SCREEN. пAGE 8-1 THE бRITISH POUND CHARACTER IS A SINGLE KEY (NO NEED TO PRESS ц= KEY). сAMPLEжLIR DOES NOT DO ANY ERROR CHECKING WHEN TRYING TO FIND "сAMPLEжLIR" ON DISK. иF THEY ARE NOT CAREFUL WHEN CHANGING APPLICATION'S NAME, WILL NOT LOAD CORRECTLY. вARN PEOPLE THAT USE OF пASS1 IS DANGEROUS; тELL THEM TO MAKE SURE THEY HAVE A .PSECT AFTER INCL. ZP VARS FILE. мANUAL: (DO NOT MENTION) мAY WANT TO EXPLAIN A LITTLE BIT ABOUT INTERRUPT TIMING, OR "WHY MOUSEдATA CHANGES". ------------------------------------------------------------------------------ ж1.100 2/88 тHIS VERSION IS ACTUALLY ж1.010 AFTER THE пATCH2.88 PROGRAM HAS MODIFIED THE аSSEMBLER AND лINKER. пATCH2.88 DISTRIBUTED THROUGH яUANTUMлINK, AND ж1.100 мASTER DISK CREATED BY RUNNING пATCH2.88 ON ж1.010 мASTER DISK. тHIS ж1.100 мASTER DISK DUPLICATED BY змAG, COPIES SENT FREE OF CHARGE TO REGISTERED OWNERS WHO REQUESTED IT. ------------------------------------------------------------------------------ ж2.000 аPRIL 1988 ц64/ц128 VERSION, WITH MANY IMPROVEMENTS AND BUG FIXES. тхис ис а яуицк лист; SEE "VERSIONж2" FILE FOR A SUMMARY. аSSEMBLER иMPROVEMENTS: RUNS UNDER геос 64 AND геос 128 (IN 80 COLUMN MODE) ENDING дб HAS ICON TO RUN LINKER HAS .TEXT DIRECTIVE TO ASSEMBLE ASCII INTO цбм TEXT CODES. лINKER иMPROVEMENTS: RUNS UNDER геос 64 AND геос 128 (IN 80 COLUMN MODE) ALLOWS UP TO 20 .REL FILES PER MODULE ENDING дб HAS ICON TO RUN DEBUGGER дEBUGGER иMPROVEMENTS: сAMPLEфILES иMPROVEMENTS: нEW WARNINGS FOR MANUAL: аSSEMBLING FILES UNDER ц128 AND LINKING THEM UNDER ц64-- DOES лINKER CHECK FOR TABLES WHICH ARE TOO LARGE? ------------------------------------------------------------------------------ тECHNICAL оVERVIEW OF иMPORTANT дIFFERENCES бETWEEN гEOпROGRAMMER жERSIONS аSSEMBLER: сINCE CODE RECORD, XREF RECORD, RELOC RECORD, AND ERROR FILE PAGES ARE WRITTEN OUT BLOCK BY BLOCK, WE ARE NOT CONCERNED WITH BUFFER SIZES. мACRO TEXT STORAGE SIZE: ж1.0 2к ж2.0 (64 MODE) 3560 ж2.0 (128 MODE) 12520 сYMBOL TABLE SIZE: ж1.0 3017+7670 = 10687 (1068 SYMBOLS) ж2.0 (64 MODE) 11510 (1151 SYMBOLS) ж2.0 (128 MODE) 32080 (3208 SYMBOLS) дOES NOT RUN IN 128 40-COLUMN MODE BECAUSE ALL дма WORK IN BACKRAM CAUSES 40-COLUMN SCREEN TO FLICKER BADLY. лINKER: ьREF AND рELOC POINTERS ARE READ BLOCK-BY-BLOCK FROM RECORDS, SO WE ARE NOT CONCERNED ABOUT BUFFER SIZES. цODE BUFFER SIZE (FOR ONE .REL'S CODE RECORD) ж1.0 6608 ж2.0 (64 MODE) 3584 ж2.0 (128 MODE) 7670 рESIDENT MODULE SYMBOL TABLE SIZE: ж1.0 10к = 10240 (1024 SYMBOLS) ж2.0 (64 MODE) 12740 (1274 SYMBOLS) ж2.0 (128 MODE) 32170 (3217 SYMBOLS) сWAP MODULE SYMBOL TABLE SIZE: ж1.0 8к = 8192 (819 SYMBOLS) ж2.0 (64 MODE) 8500 (850 SYMBOLS) ж2.0 (128 MODE) 17400 (1740 SYMBOLS) сEQUENTIAL аPPS: ж1.0 10к (YOU MIGHT THINK IS 10к + 8к, BUT THERE IS A BUG: IS ONLY 10к) ж2.0 (64 MODE) 21240 ж2.0 (128 MODE) 32170 (BACKRAM ONLY. мATTсORT TO USE BOTH BANKS (GIVING 48к) WOULD BE A MESS.) нUMBER OF .REL FILES PER MODULE: ж1.0 10 ж2.0 (64/128) 20 цREATING гEOвRITE SYM FILES: FOR EACH .DBG RECORD: READ BLOCK BY BLOCK INTO FRONTRAM AND MOVE TO BACK SORT ENTIRE IN BACK FOR EACH SYM IN BACK COPY SYM TO FRONT WRITE TO 5к PAGE BUFFER (фг SCREEN AREA?) WRITE OUT 5к BUFFER AS PAGE дOES NOT RUN IN 128 40-COLUMN MODE BECAUSE ALL дма WORK IN BACKRAM CAUSES 40-COLUMN SCREEN TO FLICKER BADLY. гEOдEBUGGER: GEOпROGRAMMER ж2.0 FOR ц64 AND ц128 уPGRADE оFFER сEPTEMBER, 1988 дEAR GEOпROGRAMMER USER: оUR LATEST RELEASE OF THE GEOпROGRAMMER PACKAGE, GEOпROGRAMMER ж2.0, WILL SOON BE AVAILABLE. вE CAN OFFER YOU, AS A REGISTERED GEOпROGRAMMER OWNER, THIS NEW PRODUCT FOR THE LOW PRICE OF $ьь.ьь. вE HAVE REWRITTEN MUCH OF THE ORIGINAL SOFTWARE, TAKING YOUR SUGGESTIONS INTO ACCOUNT, AND ADDING SOME NEW FEATURES. оVERALL пRODUCT иMPROVEMENTS: - GEOпROGRAMMER ж2.0 SUPPORTS THE цOMMODORE 128 AND 128д COMPUTERS. GEOаSSEMBLER, GEOлINKER, AND GEOдEBUGGER NOW RUN UNDER геос 128 AT THE FASTER 2мхз CLOCK RATE, USING THE 80-COLUMN SCREEN AND ADDITIONAL MEMORY. - GEOпROGRAMMER ж2.0 IS FULLY COMPATIBLE WITH ALL VERSIONS OF геос: ж1.2, ж1.3, AND ж2.0, AND WITH THE NEW 1581 DISK DRIVE. - IN BOTH ц64 AND ц128 MODES, GEOпROGRAMMER ж2.0 RUNS FASTER AND MORE EFFICIENTLY. еRROR DETECTION HAS BEEN IMPROVED, AND MORE INFORMATIVE ERROR MESSAGES ARE PROVIDED. фILE SELECTION HAS BEEN STREAMLINED. - THE THREE SAMPLE APPLICATIONS HAVE BEEN UPGRADED TO SUPPORT THE ц128, AND TO ILLUSTRATE MORE геос PROGRAMMING CONCEPTS SUCH AS KEYBOARD SHORTCUTS. - THE геос "INCLUDE" FILES HAVE BEEN UPDATED TO REFLECT геос ж2.0 INFORMATION. - GEOпROGRAMMER ж2.0 INCLUDES AN ADDITIONAL SAMPLE APPLICATION, WHICH DEMONSTRATES HOW YOU CAN DEVELOP "цбм" APPLICATIONS WHICH DO NOT REQUIRE геос TO RUN. иMPROVEMENTS IN GEOаSSEMBLER ж2.0: - GEOаSSEMBLER ж2.0 WILL READ GEOвRITE SOURCE FILES FROM ALL VERSIONS OF GEOвRITE, UP TO ж2.1. - NEW .TEXT DIRECTIVE CONVERTS ASCII TEXT STRINGS DIRECTLY INTO цOMMODORE SCREEN CODES. мAXIMUM мAXIMUM аSPECT OF GEOаSSEMBLER ж2.0 IN ц64 мODE IN ц128 мODE --------------------------------------- --------------- ------------ SYMBOL DEFINITIONS: 1151 SYMBOLS 3208 SYMBOLS MACRO DEFINITIONS: 100 MACROS 389 MACROS OR 3560 BYTES OR 12520 BYTES CODE BYTES GENERATED PER .REL FILE: 3584 BYTES 7670 BYTES --------------------------------------- --------------- ------------ иMPROVEMENTS IN GEOлINKER ж2.0: - GEOлINKER ж2.0 WILL ACCEPT MULTIPLE-PAGE ".LNK" COMMAND FILES, GENERATED WITH ANY VERSION OF GEOвRITE. - WILL LINK UP TO 20 .REL FILES INTO A сея OR цбм APPLICATION, AND UP TO 20 .REL FILES PER MODULE IN A жлир APPLICATION. мAXIMUM мAXIMUM сYMBOL DEFINITIONS IN GEOлINKER ж2.0 IN ц64 мODE IN ц128 мODE --------------------------------------- --------------- ------------ WHEN LINKING сея AND цбм APPLICATIONS: 2124 SYMBOLS 3217 SYMBOLS WHEN LINKING жлир APPLICATIONS: RESIDENT MODULE: 1274 SYMBOLS 3217 SYMBOLS FOR EACH OVERLAY MODULE: 850 SYMBOLS 1740 SYMBOLS --------------------------------------- --------------- ------------ иMPROVEMENTS IN GEOдEBUGGER ж2.0: - NEW "HIDDEN MODE": NOW YOU CAN VIEW YOUR APPLICATION'S SCREEN WHILE GIVING COMMANDS TO GEOдEBUGGER. - GEOдEBUGGER ж2.0 WILL RECOGNIZE CALLS TO INLINE геос ROUTINES SUCH AS I_рECTANGLE, ALLOWING YOU TO SAFELY TOP-STEP OVER AND DISASSEMBLE THESE CALLS. - NEW бACKрAM сUPER дEBUGGER ALLOWS ц128 OWNERS WITHOUT A RAM EXPANSION UNIT TO TAKE ADVANTAGE OF THE сUPER дEBUGGER'S FEATURES. - IMPROVED "CONTEXT SWITCH" IN ц128 MODE, ALLOWING SINGLE-STEP THROUGH CODE WHICH INVOLVES BANK SWITCHING; ALLOWS EXECUTION AT EITHER 1 мхз OR 2 мхз CLOCK RATE. - FULL SUPPORT FOR NON-геос APPLICATIONS, INCLUDING TECHNICAL NOTES ON HOW TO WRITE AND INSTALL YOUR OWN INTERRUPT SERVICE ROUTINES. - STRAY INTERRUPT TRAPPING FACILITY, TO AID IN ISOLATING RARE CRASH CONDITIONS IN ц64 AND ц128 APPLICATIONS. стаци- EXPLAIN HOW THEY GO ABOUT ORDERING THE UPGRADE: - PRICE - WHERE TO SEND CHECK / MONEY ORDER / CREDIT CARD # / ETC - WHETHER OR NOT THEY CAN CALL THEIR ORDER IN - IF THEY MUST SEND THEIR ORIGINAL DISK, OR IF A RECEIPT WILL SUFFICE. (DO NOT ASK THEM TO TEAR THE COVER OFF THEIR MANUAL- THEY WILL STILL NEED THE OLD MANUAL!) - WHO THEY SHOULD CALL WITH QUESTIONS, OR WHERE TO WRITE FOR INFO ON THE UPGRADE OFFER (NOT ME!) ц128 MODE HAS REAL TROUBLE WITH BITMAPS. сEE FILE14&15... ------------------------------------------------------------------------------- кNOWN (AND ALLOWABLE) DIFFERENCES BETWEEN GEOаSSEMBLER (тED'S) AND GEOаSSEMBLER (MINE) OUTPUT FILES. тед: ериц: ----------------------- ----------------------- .рел FILE: цODE RECORD ILLEGAL BRANCH: GETS GARBAGE OFFSET OFFSET = $20 еXрEF RECORD: LESS и GENERATE MORE еXрEFS рELOC рECORD: сым RECORD: +3: рELOC BIT: SET FOR зп LABELS ALWAYS 0 +4: "==" BIT SET FOR "=" EQUATES SET FOR "==" EQUATES .ерр FILE: MARGINS IN RULER: OFFSET=+7: =$28 =$30 ------------------------------------------------------------------------------- бугс: доне: - FIXED LINK ICON - CLEANED UP SOME 40/80 COLUMN PROBLEMS IN иNIT MODULE - MADE WRITEбамтOдISK A BYTE VARIABLE - ADDED пANICвRITEнEWбамтOдISK TO ROUTINES WHICH DELETE CHAINS - CLEANED UP 40/80 COLUMN MODE SWITCHING SOME MORE - FIXED LOTS OF MISCELLANEOUS THINGS IN MACRO EXPANSION... - REWROTE HOW MACRO PARAMETERS ARE PARSED FROM DEFINITION LINE, SO THAT CAN DETECT ALL ERROR CASES - REWROTE HOW MACRO ARGUMENTS ARE PARSED FROM INVOCATION LINE, HOW THEY ARE STORED AND SEARCHED. SHOULD HANDLE NULL ARGS, TOO MANY ARGS - FIXED HANDLING OF GLOBAL LABELS WITHIN MACROS- NOW SUBSTITUTES CORRECTLY, HANDLES 8 CHAR SYMBOLS - FIXED BUG IN NESTED MACROS WHICH HAVE GLOBAL LABELS (+1 ERROR) - FIXED HOW сEARCHтABLE DETERMINES LENGTHS OF THINGS IT CAN SEARCH FOR - RE-WROTE TEST FILE #19 (TESTS MACRO DEF AND EXP ERRORS), ADDED A SERIES OF ADDITIONAL TESTS, VERIFIED ALL OUTPUT, PLACED ON TEST DISK а. - CREATED TEST FILE #75 (TESTS ALL POSSIBLE NON-FATAL ERROR MESSAGES) иNCLUDES MOST SCENARIOS WHICH COULD GENERATE THESE ERRORS. VERIFIED ALL OUTPUT, PLACED ON TEST DISK б. - FIXED "RELOC" FLAG BUG: NOW SETS RELOCATION BITS IN LABELS CORRECTLY - REWROTE HOW LOCAL LABELS AND REFERENCES TO THEM ARE PLACED IN TABLES (CORRECTED BUG WHICH CLEANED UP AFTER ймп 10$ INCORRECTLY) - REWROTE HOW INFORMATION IS COLLECTED ABOUT AN OPERAND WHILE IT IS BEING EVALUATED, AND HOW THIS INFORMATION AFFECTS THE POSSIBLE ADDRESSING MODES. цORRECTED SEVERAL BUGS HAVING TO DO WITH EXPRESSIONS WHICH CONSIST OF SEVERAL DIFFERENT TYPES OF ARGUMENTS. - EXPRESSION WAS JUDGED AS RELOCATABLE EVEN AFTER MATH - BIT FOR EQUATE WAS SET BY NOGLBL/NOEQIN STATUS - "*" OPERAND DIDN'T SET RIGHT BIT FOR PSECT/RAMSECT - WAS SETTING STATUS:б3 FOR "уNARYтOGETHER" CASES- WHY? - IMPROPER HANDLING OF лда # AND .быте OPERANDS - NOT GENERATING RELOC POINTERS AND EXREFS IN ALL CASES - NOT CATCHING ALL POSSIBLE BRANCH ERRORS (BAD LOCAL LABEL USAGE) - MADE 2 CENTRAL ROUTINES FOR GRABBING ARGS FOR .иф ETC, .блоцк, .псецт ETC, ETC. - CHANGED THE WAY гETеXPRESSION LOOKS AT "MUSTеVAL" - REMOVED THE "COMPLEXеXP" FLAG - REWROTE ERROR DETECTION IN LOCAL LABEL REFERENCES AND DEFINITIONS - NOW CAN FORGET MOST RECENT LOCAL LABEL REFERENCE, FOR CASES WHERE LINE IS BAD (DOES NOT STAMP CODE WHICH IS NOT ASSEMBLED) - CREATED TESTFILE: FILE76_1 TO TEST ALL EXPRESSION PARSING AND ERROR DETECTION; ALSO INCLUDES SOME BRANCHING TESTS - FIXED A LOT OF BUGS RELATED TO USING "*" IN EXPRESSIONS цORRECTED EXPRESSION EVALUATOR'S TYPE-CHECKING IN GENERAL CREATED NEW TEST FILE (FILE7) TO TEST THIS - оPENсOURCEфILE IN фILE/FILEрOUTINES NO LONGER DOES A фINDфILE BEFORE оPENрECORDфILE. сPEED ASSEMBLY A BIT. - SPENT A DAY CHASING FILE14 BUG IN 128 MODE. нO LUCK. кееп ан еые оут фор: тHERE MIGHT BE A BUG WITH FILE62 (TOO MANY BACKRAM SYMBOLS) TRY ON STAND-ALONE, SEE IF болдфаце CHARACTERS GET TRASHED иF SO, DISABLE дма мOVEдATA, SEE IF IT STILL HAPPENS ------------------------------------------------------------------------------- вARN IN MANUAL: иT MAY BE POSSIBLE FOR ASSEMBLER TO HAVE TOO MANY SYMBOLS THAN THE LINKER COULD READ IN FROM ONE .рел FILE. бUT IF SOME OF THESE ARE .NOEQIN OR .NOGLBL'ED OUT, WE ARE OK. вARN IN MANUAL THAT бне сTART+сTART WILL NOT ASSEMBLE CORRECTLY, BECAUSE и ASSUME IS SOMETHING OF THE FORM: бне сTART+2, WHICH IS LEGAL. фILE SELECT дб WILL DISPLAY ANY APPLICATION DATA FILE WHICH DOES NOT END IN ".REL", ".DBG", ".SYM", ".ERR", ".LNK": THUS IS FASTER THAN BEFORE. пROBLEM: WILL DISPLAY GEOфILE AND GEOпAINT ETC. DOCUMENTS. ------------------------------------------------------------------------------- футуре: аDD TO TEST LIST PAGE TOO BIG (4096) ECHO TOO MANY PAGES TOO MANY ERROR PAGES MINOR BUGS FOUND IN FILE75: нOT RECOGNIZING "LINE TOO LONG" CORRECTLY цOULD NOT GET IT TO PRINT "EXPRESSION TOO COMPLEX" DOES NOT DETECT .RAMSECT AND .INCLUDE IN MACRO DEFINITION SEE ERROR #61- и DID NOT FORCE IT CORRECTLY SEE FILE3: ASSEMBLER IS NOT FLAGGING ERROR FOR ".WORD "ERIC" " ц128 MODE: INTERMITTENT BUG WHEN TRYING TO ASSEMBLE FILE14 (BIG BITMAP) OFF OF DRIVE а, ONTO рам диск. сOMETIMES GET "DISK NAME MISMATCH" ERROR. ц128: WHY DID 3208 NOT OVERFLOW SYMBOL TABLE? TABLE HOLDS 3208- и SENT 3208 PLUS 3 ALREADY THERE! цREATE A FILE78 WHICH IS A COPY OF FILE75, BUT WHICH TESTS .IF пASS1 STUFF. и DID THIS ON 10/1/88, AND HIT A WEIRD PHASE ERROR AT гLOBALлABEL:. и DON'T THINK THIS IS A BIG PROBLEM. сLIGHT PROBLEM IN EXPRESSION EVALUATION: PARSES JMP (LABEL) AS RELOCATABLE WITH MATH, SINCE IT HITS THE ENDING PARANTHESES. нEED TO EDUCATE GETеXPRESSION A LITTLE MORE SO THIS DOES NOT HAPPEN. тHIS IS NOT A PROBLEM WITH THE (,X) AND (),Y ADDRESSING MODES, BECAUSE THEY MUST HAVE RESOLVABLE зп EXPRESSIONS, AND SO THEY NEVER GENERATE EXTERNAL REFERENCES. ------------------------------------------------------------------------------- дистант футуре мOVE LOCAL LABEL PARSING OUT OF EXPRESSION EVALUATOR: RIGHT NOW THE ERROR DETECTION IS VERY CONFUSED BY CASES SUCH AS LDA 10$+4 LDA 4+10$+6666666666666 LDA 10$+20$+30$ ;THREE REFERENCES ADDED TO LIST, ;ONLY LAST ONE DELETED... мINOR PROBLEM: а LINE SUCH AS .BYTE 1,CRAP,2 WILL STILL GENERATE 3 BYTES OF CODE: WOULD BE NICE TO COMPLETELY REVERSE THE EFFECTS (CODE, лц INCS, EXREFS AND RELOCS GENERATED, ETC) OF A CODE LINE WHEN AN ERROR IS DETECTED. оTHERWISE THERE IS NO EASY WAY TO HANDLE THIS CASE. рELATED PROBLEM: IN CASES WHERE AN ERROR IS DETECTED IN PASS 2 AND нот PASS 1, WE HAVE TO MAKE SURE THE SAME AMOUNT OF CODE IS GENERATED IN BOTH PASSES, SO THAT NO PHASE ERRORS SHOW UP. "тOO MANY LOCAL LABEL REFERENCES" IS A GOOD EXAMPLE OF THIS. сEE BEGINNING OF пARSEиNST FOR HOW и HANDLED THIS. ц128 MODE HAS REAL TROUBLE WITH BITMAPS. сEE FILE14&15... ------------------------------------------------------------------------------- кNOWN (AND ALLOWABLE) DIFFERENCES BETWEEN GEOаSSEMBLER (тED'S) AND GEOаSSEMBLER (MINE) OUTPUT FILES. тед: ериц: ----------------------- ----------------------- .рел FILE: цODE RECORD ILLEGAL BRANCH: GETS GARBAGE OFFSET OFFSET = $20 еXрEF RECORD: LESS и GENERATE MORE еXрEFS рELOC рECORD: сым RECORD: +3: рELOC BIT: SET FOR зп LABELS ALWAYS 0 +4: "==" BIT SET FOR "=" EQUATES SET FOR "==" EQUATES .ерр FILE: MARGINS IN RULER: OFFSET=+7: =$28 =$30 ------------------------------------------------------------------------------- бугс: доне: - FIXED LINK ICON - CLEANED UP SOME 40/80 COLUMN PROBLEMS IN иNIT MODULE - MADE WRITEбамтOдISK A BYTE VARIABLE - ADDED пANICвRITEнEWбамтOдISK TO ROUTINES WHICH DELETE CHAINS - CLEANED UP 40/80 COLUMN MODE SWITCHING SOME MORE - FIXED LOTS OF MISCELLANEOUS THINGS IN MACRO EXPANSION... - REWROTE HOW MACRO PARAMETERS ARE PARSED FROM DEFINITION LINE, SO THAT CAN DETECT ALL ERROR CASES - REWROTE HOW MACRO ARGUMENTS ARE PARSED FROM INVOCATION LINE, HOW THEY ARE STORED AND SEARCHED. SHOULD HANDLE NULL ARGS, TOO MANY ARGS - FIXED HANDLING OF GLOBAL LABELS WITHIN MACROS- NOW SUBSTITUTES CORRECTLY, HANDLES 8 CHAR SYMBOLS - FIXED BUG IN NESTED MACROS WHICH HAVE GLOBAL LABELS (+1 ERROR) - FIXED HOW сEARCHтABLE DETERMINES LENGTHS OF THINGS IT CAN SEARCH FOR - RE-WROTE TEST FILE #19 (TESTS MACRO DEF AND EXP ERRORS), ADDED A SERIES OF ADDITIONAL TESTS, VERIFIED ALL OUTPUT, PLACED ON TEST DISK а. - CREATED TEST FILE #75 (TESTS ALL POSSIBLE NON-FATAL ERROR MESSAGES) иNCLUDES MOST SCENARIOS WHICH COULD GENERATE THESE ERRORS. VERIFIED ALL OUTPUT, PLACED ON TEST DISK б. - FIXED "RELOC" FLAG BUG: NOW SETS RELOCATION BITS IN LABELS CORRECTLY - REWROTE HOW LOCAL LABELS AND REFERENCES TO THEM ARE PLACED IN TABLES (CORRECTED BUG WHICH CLEANED UP AFTER ймп 10$ INCORRECTLY) - REWROTE HOW INFORMATION IS COLLECTED ABOUT AN OPERAND WHILE IT IS BEING EVALUATED, AND HOW THIS INFORMATION AFFECTS THE POSSIBLE ADDRESSING MODES. цORRECTED SEVERAL BUGS HAVING TO DO WITH EXPRESSIONS WHICH CONSIST OF SEVERAL DIFFERENT TYPES OF ARGUMENTS. - EXPRESSION WAS JUDGED AS RELOCATABLE EVEN AFTER MATH - BIT FOR EQUATE WAS SET BY NOGLBL/NOEQIN STATUS - "*" OPERAND DIDN'T SET RIGHT BIT FOR PSECT/RAMSECT - WAS SETTING STATUS:б3 FOR "уNARYтOGETHER" CASES- WHY? - IMPROPER HANDLING OF лда # AND .быте OPERANDS - NOT GENERATING RELOC POINTERS AND EXREFS IN ALL CASES - NOT CATCHING ALL POSSIBLE BRANCH ERRORS (BAD LOCAL LABEL USAGE) - MADE 2 CENTRAL ROUTINES FOR GRABBING ARGS FOR .иф ETC, .блоцк, .псецт ETC, ETC. - CHANGED THE WAY гETеXPRESSION LOOKS AT "MUSTеVAL" - REMOVED THE "COMPLEXеXP" FLAG - REWROTE ERROR DETECTION IN LOCAL LABEL REFERENCES AND DEFINITIONS - NOW CAN FORGET MOST RECENT LOCAL LABEL REFERENCE, FOR CASES WHERE LINE IS BAD (DOES NOT STAMP CODE WHICH IS NOT ASSEMBLED) - CREATED TESTFILE: FILE76_1 TO TEST ALL EXPRESSION PARSING AND ERROR DETECTION; ALSO INCLUDES SOME BRANCHING TESTS - FIXED A LOT OF BUGS RELATED TO USING "*" IN EXPRESSIONS цORRECTED EXPRESSION EVALUATOR'S TYPE-CHECKING IN GENERAL CREATED NEW TEST FILE (FILE7) TO TEST THIS - оPENсOURCEфILE IN фILE/FILEрOUTINES NO LONGER DOES A фINDфILE BEFORE оPENрECORDфILE. сPEED ASSEMBLY A BIT. - SPENT A DAY CHASING FILE14 BUG IN 128 MODE. нO LUCK. кееп ан еые оут фор: тHERE MIGHT BE A BUG WITH FILE62 (TOO MANY BACKRAM SYMBOLS) TRY ON STAND-ALONE, SEE IF болдфаце CHARACTERS GET TRASHED иF SO, DISABLE дма мOVEдATA, SEE IF IT STILL HAPPENS ------------------------------------------------------------------------------- вARN IN MANUAL: иT MAY BE POSSIBLE FOR ASSEMBLER TO HAVE TOO MANY SYMBOLS THAN THE LINKER COULD READ IN FROM ONE .рел FILE. бUT IF SOME OF THESE ARE .NOEQIN OR .NOGLBL'ED OUT, WE ARE OK. вARN IN MANUAL THAT бне сTART+сTART WILL NOT ASSEMBLE CORRECTLY, BECAUSE и ASSUME IS SOMETHING OF THE FORM: бне сTART+2, WHICH IS LEGAL. фILE SELECT дб WILL DISPLAY ANY APPLICATION DATA FILE WHICH DOES NOT END IN ".REL", ".DBG", ".SYM", ".ERR", ".LNK": THUS IS FASTER THAN BEFORE. пROBLEM: WILL DISPLAY GEOфILE AND GEOпAINT ETC. DOCUMENTS. ------------------------------------------------------------------------------- футуре: аDD TO TEST LIST PAGE TOO BIG (4096) ECHO TOO MANY PAGES TOO MANY ERROR PAGES MINOR BUGS FOUND IN FILE75: нOT RECOGNIZING "LINE TOO LONG" CORRECTLY цOULD NOT GET IT TO PRINT "EXPRESSION TOO COMPLEX" DOES NOT DETECT .RAMSECT AND .INCLUDE IN MACRO DEFINITION SEE ERROR #61- и DID NOT FORCE IT CORRECTLY SEE FILE3: ASSEMBLER IS NOT FLAGGING ERROR FOR ".WORD "ERIC" " ц128 MODE: INTERMITTENT BUG WHEN TRYING TO ASSEMBLE FILE14 (BIG BITMAP) OFF OF DRIVE а, ONTO рам диск. сOMETIMES GET "DISK NAME MISMATCH" ERROR. ц128: WHY DID 3208 NOT OVERFLOW SYMBOL TABLE? TABLE HOLDS 3208- и SENT 3208 PLUS 3 ALREADY THERE! цREATE A FILE78 WHICH IS A COPY OF FILE75, BUT WHICH TESTS .IF пASS1 STUFF. и DID THIS ON 10/1/88, AND HIT A WEIRD PHASE ERROR AT гLOBALлABEL:. и DON'T THINK THIS IS A BIG PROBLEM. сLIGHT PROBLEM IN EXPRESSION EVALUATION: PARSES JMP (LABEL) AS RELOCATABLE WITH MATH, SINCE IT HITS THE ENDING PARANTHESES. нEED TO EDUCATE GETеXPRESSION A LITTLE MORE SO THIS DOES NOT HAPPEN. тHIS IS NOT A PROBLEM WITH THE (,X) AND (),Y ADDRESSING MODES, BECAUSE THEY MUST HAVE RESOLVABLE зп EXPRESSIONS, AND SO THEY NEVER GENERATE EXTERNAL REFERENCES. ------------------------------------------------------------------------------- дистант футуре мOVE LOCAL LABEL PARSING OUT OF EXPRESSION EVALUATOR: RIGHT NOW THE ERROR DETECTION IS VERY CONFUSED BY CASES SUCH AS LDA 10$+4 LDA 4+10$+6666666666666 LDA 10$+20$+30$ ;THREE REFERENCES ADDED TO LIST, ;ONLY LAST ONE DELETED... мINOR PROBLEM: а LINE SUCH AS .BYTE 1,CRAP,2 WILL STILL GENERATE 3 BYTES OF CODE: WOULD BE NICE TO COMPLETELY REVERSE THE EFFECTS (CODE, лц INCS, EXREFS AND RELOCS GENERATED, ETC) OF A CODE LINE WHEN AN ERROR IS DETECTED. оTHERWISE THERE IS NO EASY WAY TO HANDLE THIS CASE. рELATED PROBLEM: IN CASES WHERE AN ERROR IS DETECTED IN PASS 2 AND нот PASS 1, WE HAVE TO MAKE SURE THE SAME AMOUNT OF CODE IS GENERATED IN BOTH PASSES, SO THAT NO PHASE ERRORS SHOW UP. "тOO MANY LOCAL LABEL REFERENCES" IS A GOOD EXAMPLE OF THIS. сEE BEGINNING OF пARSEиNST FOR HOW и HANDLED THIS. LINKER DOES NOT WARN ABOUT WORD STAMPED INTO BYTE LOCATION: .BYTE еXTERN LDA #еXTERN ;SEE FILE7 гEOлINKER тхингс то до: - CORRECTED BAD мOVEдATA IN лINKхEADER WHICH WAS TRASHING SYMBOL TABLE, CAUSING BAD .сым FILE TO BE CREATED (TO AVOID, DO NOT CREATE CUSTOMIZED HEADER BLOCK) - CORRECTED BUG IN MODULE SWAPPING, WHICH CAUSED PROBLEMS WHEN WRITING .сым FILE TO OTHER DISK (TO AVOID, SET OUTPUT DRIVE = APPLICATION DRIVE) - NOW RUNS GEOдEBUGGER PROPERLY (HAD BAD PERM NAME) - TESTED .CBM LINK WITH MULTIPLE .REL FILES: WORKS OK - REMOVED WARNINGS ABOUT мOVEбдATA OVERLAPPING SYMBOL TABLE - FIXED: "SYMBOL DEFINED MORE THAN ONCE"- IS PRINTING FILENAME INSTEAD OF SYM - FIXED: IF SYM ERROR IN HEADER FILE, ERROR MESSAGE FUNNY - FIXED: IF SYM TABLE EMPTY, SEARCHES ALL OF MEMORY FOR SYMBOL - FIXED: PRINTS CORRECT ERROR WHEN HEADER BLOCK WRONG SIZE - FIXED: DOES NOT DELETE OLD FILES WHEN OUTPUT DRIVE NOT INPUT DRIVE - FIXED: SEQ, CBM, AND VLIR .обй FILES SHOULD NOW HAVE CORRECT SIZE. - RE-INSTALLED RESIDENT CODE MUNGING - CLEANED UP SOME 40/80 COLUMN PROBLEMS IN иNIT MODULE афтер бета 1: ADD FILES TO TEST LIST фUTURE: и AM NOT SO SURE THE хEX/DECIMAL/OCTAL ETC PARSERS WORK. SAME PROBLEMS IN ASSEMBLER? и MAY HAVE SCREWED UP HOW IT EVALUATES EXPRESSIONS IN .мод STATEMENTS сEE рESIDENT/GETлINE, AND A VARIABLE "OPERAND" WHICH DETERMINES WHERE A WORD BOUNDARY IS. доне: - REORDERED MODULES - MADE SURE THAT PROGRAM HAS A TOP-LEVEL IN RESIDENT, AND THAT EVERYTHING IS A CALL FROM IT - UPDATED HOW SWAP AND DRIVE ROUTINES WORK - COMBINED фILE, дRIVE, AND цOMPACT MODULES - UPDATED гETфILENAME, WITH CHANGES WE MADE TO GEOаSSEMBLER - COPIED NEW тOтEXT AND тOбITMAP ROUTINES OVER FROM ASSEMBLER - MOVED SOME INIT CODE TO фILE MODULE - MOVED ERROR FILE CREATION TO фILE MODULE - REMOVED ALOT OF UNUSED CODE IN EXPRESSION EVALUATOR, REMOVED BUGS - CREATED гETлINEаNDвORD - оPENаNOTHERфILE -> оPENрELфILE - REWROTE HOW лнк FILE IS PARSED MOVED MOST OF IT TO фILE REWROTE MID-LEVEL AND TOP-LEVEL PARSING ROUTINES DELETED SOME ERROR MESSAGES, ADDED SOME - UPDATED SCREEN HANDLING - REWROTE HOW SYMBOLS ARE RELOCATED - REWROTE HOW RELOC POINTERS ARE READ IN AND USED - REWROTE HOW EXPRESSIONS ARE READ IN AND USED - REWROTE ROUTINE TO SEARCH SYMBOL TABLES- REMOVED LOT OF EXCESS CODE, POSSIBLY SOME BUGS. SEARCHES 2-3 TIMES FASTER NOW. - SIMPLIFIED HOW SYMBOLS ARE COMPACTED, FIXED, SORTED, AND WRITTEN OUT TO DISK - PLACED рES AND сWAP TABLES NEXT TO EACH OTHER, COMMENTED OUT ALL BIGсEQ CODE - ревроте HOW .обй FILE IS CREATED AND WRITTEN TO, INCLUDING CUSTOM HEADER BLOCK / цбм FILE CONSIDERATIONS - REWROTE HOW HEADER BLOCK .рел FILE IS LINKED TO REST OF APPLICATION- HEADER .рел FILE CAN NOW HAVE ITS OWN SYMBOL DEFS, WHICH GO TO SWAP TABLE. - ревроте HOW LINKER OPENS GEOвRITE OR GEOдEBUGGER (CODE FROM ASSEM) - BROUGHT NEW тOтEXT AND тOбITMAP CODE OVER FROM GEOаSSEM - REWROTE ERROR PRINTING ROUTINES - редуцед тотал сизе оф апп фром 24к TO 20к - редуцед сизе оф ресидент бы 2589 бытес! - DID COMPLETE WALK-THROUGH OF NEW CODE, MAKING SURE THAT DISK AND USER ERRORS CAUSED THE RIGHT THING TO HAPPEN - FINAL WORK ON FILE CREATION/DELETION STUFF - RE-INSTALLED стоп KEY CHECKS - ADDED цHECKдISKеRROR CALLS THROUGHOUT PROGRAM - ADDED CODE TO SET FILENAME POINTER IN CASE ERROR OCCURS - ADDED NEW ERROR DIALOG BOX: PRINTS FILENAME, ERROR, ALLOWS цанцел - ADDED CODE TO DELETE OUTPUT FILES CORRECTLY ON ERROR, DISPLAY SECOND дб IF SECOND DISK ERROR - NUKED ERROR MESSAGE POINTER TABLE TO SAVE BYTES IN RESIDENT - ревроте HOW WE CREATE THE .ерр FILE MADE SURE RULER AND VERSION # ARE ок - ревроте HOW WE CREATE THE .дбг FILE - MODIFIED HOW WE CREATE THE .сым FILE- DOES THIS NEED ANY WORK? DON'T FORGET TO TEST INSTALLATION WITH 1571 DRIVE! тHINK ABOUT 2 DIFFERENT PHYSICAL DRIVES ON NON-реу SYSTEM: WILL геос TELL ME THAT DRIVER DOES NOT EXIST, OR WILL и CRASH? бUG: 1571 AS а, 1581 AS б, RUN DEBUGGER ON б, TRY TO SELECT DRIVE а, AND SINCE THERE IS NO реу, геос сETдEVICE DOES NOT WORK. дOES IT RETURN ERROR CONDITION TO DEBUGGER? OR JUST CRASH... бUGS IN тUESDAY (6/21) 12пм VERSION: STOP COMMAND IN HIDDEN MODE DOES NOT DO THE RIGHT THING! CHANGE NOTES IN GET INFO BOX бUGS IN THU (6/16) 4пм VERSION: FIXED: сету U.E2 COMMAND DOES NOT CLEAR HIGH BITS! FIXED: сым R0л FINDS R0 ALSO! FIXED: GETN COMMAND IS READING DISK INFO FROM BANK 0! FIXED: IN RBOOT, QUIT, AND EXIT COMMANDS, PRESSING ф8 SCREWS UP LINE FIXED: STOP COMMAND DOES NOT CANCEL HIDDEN MODE ANYMORE FORGET: @# OPERATOR DOES NOT TAKE IN-LINES INTO ACCOUNT INVESTIGATED: WE CANNOT PROTECT ALL OF и/о SPACE WARN IN MANUAL: IN бACKрAMсUPER (AND HAVE реу), SHOW геос SCREEN WHEN TOP-STEPPING THROUGH мOVEдATA, BECAUSE IT USES дма TO MOVE SMALL THINGS. (тHEY COULD DISABLE мOVEдATA IN CONFIGURE TO BE SURE. аLSO WARN THAT AN рбоот BRINGS BACK OLD мOVEдATA/рбоот FLAG VALUES.) бUGS IN EARLIER VERSIONS: FIXED: SETU SS,0 PLACES CURSOR WRONG FIXED: PRINT @ SIGN WHERE пц SHOULD GO FIXED: NOT DELETING сбп'S CORRECTLY FIXED: TRASHES ь (AND OPEN MODES) WHEN SETTING сбпS TO рам FIXED: DOES NOT LOAD цбмS WITH HEADER CORRECTLY FIXED: $03фц-$03фф STILL TREATED DIFFERENTLY FIXED: IN 64 MODE, IS NOT TRACKING BANK INFO WITH сбпS CORRECTLY FINISH NOW WORKS WITHIN INLINE CALL CLEANED UP фETCHиNST USAGE N COMMAND WILL NOW SET FINAL лц CORRECTLY IF LAST LINE IS INLINE йср FIXED фINDнEXT: м MODE SHOULD NOW IGNORE INLINE STUFF CHECK UP AND DOWN IN BOTH MODES, CHECK REG, FLAG, OPT, ETC CORRECTED "в": NOW USES фINDнEXT, SO SHOULD WORK. FIXED йср COMMAND TEST: BOOT APP AND TRY йср $400: SHOULD COME BACK TO US BEFORE GOING OFF TO геос MAINLOOP FIXED SKIP COMMAND: TAKES BANK INTO ACCOUNT FIXED DIFF AND COPY COMMANDS FIXED ф8 IN MINI DEBUGGER RIGHT-SIDE PROMPT BUG FIXED LOAD цбм APP WITH HEADER BUG FIXED $3фц-$3фф BUG FIXED BANK INFO COMPARISONS ADDED и AND р PRINTING TO OPEN COMMAND PRINTS ERROR IF TRY TO SET бп IN ром OR ио FIXED ио AREA DECODE BUG ($д022) CLEANED UP INIT CODE: ZEROED ALL VARS AT START, SAVED LOTS OF BYTES FIXED сTUFFбркаTлса BUG WHICH и CREATED YESTERDAY! ------------------------------------------------------------------------------ мAJOR CODE SECTIONS: ------------------------------------------------------------------------------ фOR тEST лIST: GOOD TEST FOR ц64 VERSION: CHECK TO SEE IF $фф00 AND $д506 ARE CHANGING SPECIAL ASSIGNMENTS FOR бETA тESTERS? SINGLE STEPPING THROUGH DIFFERENT BANKS MEMORY ACCESS TESTS SYMBOL TABLE USE MACRO DEFINITION USE ------------------------------------------------------------------------------ нEW цONCERNS: WHAT IF IN 64 MODE THEY SWAP ром IN AND USE DEBUGGER гETбLOCK? ------------------------------------------------------------------------------ тHINGS тO рESEARCH: ресет EXECUTES ромс, BUT DO THEY CHECK рам? бANK 0 пAGE 3 ISSUES: и FILL FIRST WITH $00 AND THEN WITH $ED, AND DESKтOP AND ICON EDITOR HAD NO PROBLEMS RUNNING. CANNOT LOAD OTHER DESK ACCESSORIES? EASY WAY TO LOAD DRIVERS? ???CONVERT TABS FOUND IN MACRO DEFS ???дир SAVE пц? иNITфORио TRASHES $314 AREA VECTORS- ыес: $314 AND $318 (иря AND нми) ------------------------------------------------------------------------------ нOT CONCERNED WITH: DEBUGGER ASSUMES ALL GEOвRITE VERSIONS ABOVE 1.1 ARE THE SAME. 64 MODE ON ц128: CAN SET FOR 2мхз? ресторе KEY BOUNCES! гENERATES TWO нми SIGNALS, SPACED ABOUT 200 USEC APART ------------------------------------------------------------------------------ лOW пRIORITY: уSER COMPLAINT: HIS PROGRAM RAN UNDER дгб, CRASHED UNDER геос. хE HAD FORGOTTEN TO PUT A DUMMY ICON UP. пOSSIBLY RELATED TO DEBUGGER CLEARING MEMORY. сHOULD NOT ALLOW USER TO LOAD APPLICATION WHICH TRASHES мINIдEBUGGER IN MEMORY OR WHICH WOULD TRASH геос ADD OPTION TO DISABLE геос дISK USAGE? (SO THEY WON'T DO THE WRONG THING WHEN DEBUGGING GAMES) ADD DETECTION FOR TRASHED геос? (WOULD FORCE RBOOT ON EXIT) READ OPTION PRESETS FROM VALUE OF оптионс CONSTANT IN SYMBOL TABLE AFTER USER HAS TRASHED MEMORY, SHOULD BOOT геос FROM DISK... OPTION TO ALLOW THEM TO USE брк AS AN INSTRUCTION (GET TO THEIR VECTOR) ------------------------------------------------------------------------------ фOR мANUAL: MINOR: HOLDING MOUSE BUTTON LOOKS LIKE RUN/STOP DURING BOOT THEIR иря SERVICE ROUTINE MUST FINISH WITH AN рти BECAUSE OF THE WAY THINGS ARE PUSHED... дEBUGGER WILL NOT LOAD THEIR гAME OVER геос: гAME MUST CALL геос ROUTINES TO GET THE REST OF IT IN (THIS IS WHAT DESKтOP WOULD REQUIRE ANYWAY.) PLACES брк AT рSTRаPPL IF IS RUNNING DESK ACCESSORY MENTION "пRESS ресторе SHARPLY" IN MANUAL $д506 AND $фф00 SHADOWED R.MM NUKED COMPLETELY. р COMMAND NO LONGER SHOWS мEMмAP SCREEN FLICKER DURING STEP IS DUE TO POOR геос 128 INTERRUPT CODE HOLDING KEY DOWN WHEN DEBUGGER STARTS WILL FORCE ERROR ON FIRST LINE USER MAY WANT TO CHANGE R COMMAND: CREAT MACRO WHICH DOES р AND банк. USER CAN CHANGE пц MEM MAP DIRECTLY BY ACCESSING FF00 AND D506 IF USER'S CODE UPDATES SCREEN REGISTERS, BUT DEBUGGER SCREEN IS VISIBLE, THEN WHEN DEBUGGER KICKS IN IT WILL ASSERT ITS VALUES, LOSING THE USER'S NEW VALUES. вARN THEM TO ENABLE TARGET SCREEN BEFORE EXECUTING SUCH CODE. SEE сPECS/USERнOTES FOR MORE... ------------------------------------------------------------------------------ аSSUMPTIONS: геос 128 HAS SAME $FFFA VECTORS IN б1 AND б0. и ASSUME THIS TO BE TRUE FOR ALL FUTURE VERSIONS. ------------------------------------------------------------------------------ сAVE бYTES: MINI DEBUGGER DOES NOT HAVE TO BE AS CAREFUL ABOUT SCREEN STUFF IN RESIDENT: COMPACT THAT DAM дRIVE ICON! ------------------------------------------------------------------------------ фUTURE: DO NOT EXECUTE ILLEGAL INSTRUCTIONS COULD CUSTOMIZE DEBUGGER ACCORDING TO 64/128 MODE реу AS TRACE BUFFER? DON'T ALLOW TWO MACROS OF SAME NAME IN MACRO FILE WRITE OUT MACRO FILE ADD MODULES TO DEBUGGER FOR MORE FEATURES SENSE USER'S MODULE SWAP AND CORRECT сбпS? COULD SAVE б1/б0 INFO IN SYMBOL TABLE TO FURTHER REDUCE CONFLICTS MEMORY RANGE COMMANDS COULD EASILY MOVE DATA FROM BANK TO BANK COMMANDS LIKE в WILL NOT WORK IF PRINTING IS OFF, BECAUSE дISPLAYлOCATION IS NEVER CALLED, BYTES NEVER READ, POINTERS NEVER MOVED. тHIS COULD BE CLEANED UP. CLRB IS NOW CRIPPLED BECAUSE IT RELIGIOUSLY CHECKS FOR EXACT BANK INFO WHEN SEARCHING THE сбп LIST. цOULD REMOVE THIS RESTRICTION TO MAKE THE CLRB COMMAND EASIER, BUT THEN TRYING TO REMOVE A DOUBLE-сбп (BANK1 AND 0, SAME ADDR) USING AN OPEN MODE WOULD BE IMPOSSIBLE. аCTUALLY, THERE IS A DEEPER PROBLEM WITH THE WAY WE STORE BANK INFO WITH сбпS IN THEIR TABLE: WE SHOULD JUST STORE THE EFFECTIVE BANK DIFFERENCE, NOT THE 16 BITS OF INFO. иF THE SETB COMMAND IS CHECKING FOR EXACT MATCHES WHEN IT INSERTS A NEW сбп, THEN YOU COULD HAVE SEVERAL "EQUAL" сбпS IN THE SAME TABLE. ------------------------------------------------------------------------------ фINISHED: 40/80 COLUMN TEXT BITS AND CENTERING STUFF, MOVED TO ONE FILE, STANDARDIZED дб TEXT POSITIONS (WILL HELP APPLE PORT) MACRO LOAD BUGS, EXTENSIVE ERROR CHECKING, PAGE/LINE # BUGS SYMBOL LOAD BUG INFO BOX CODE: DISPLAYS STATUS MESSAGES AS FILES LOAD стоп KEY BUG BUGS IN LOADсAVEбYTE ERROR CHECKING DURING SYMBOL TABLE LOADS LOADS DEFAULT.DBM EVEN IF NO FILENAME GIVEN NEED рESпREPфORяUIT EXTENSIVE ERROR CHECKING DURING MODULE SWAPS, DEBUGGER LOADS, AND FILENAME SELECTION (INCLUDING PRINTING CURRENT FILENAME DURING ERROR) ADDED MEMORY р/в CHECKS FOR $фф01-$фф04 PAGE # IN MACRO FILE LOADS FIXED 80 COLUMN SCROLL BUG рESпREPфORяUIT RESTORES USER'S SCREEN, NOT BE SAME AS геос SCREEN CLEAR PENDING INTERRUPT BEFORE STEPPING TEST NEW лцра-лцрд STUFF INVERTS ADDRESSES IF DISPLAYING BANK #0 ADDRESS гETбLOCK, пUTбLOCK: CALL BANK 1 ROUTINE, DISPLAY BANK 1 DATA йср DOES WORK IN EITHER BANK (BECAUSE IS LIKE A TOP-STEP) реу CHECK UNDER геос ж1.2 TEST RBOOT IN ALL 5 CONFIGS ц64 MODE! BANKиNFO1/2 VARIABLE: CARRIES INFO IN 64 AND 128 MODES CALL гET1STдIRеNTRY, USE R5, CALL GETнXTдIRеNTRY - NEED TWO NEW PRIMITIVES - CHANGE DIR MACRO TRACKED DOWN SCREEN FLICKER BUG (IS геос 128 INTERRUPT CODE!) - IMPLEMENTED NEW 3-LEVEL нми ENABLE/DISABLE CODE - FOUND BUG IN 128 геос иNITфORио - ADDED циа2 нми HANDLING - WROTE DOCUMENTATION ON STRAY INTERRUPT TRAPPING - WROTE ROUTINES SO USER'S APPLICATIONS CAN SET INTERRUPT SERVICE ROUTINE VECTORS CORRECTLY WHEN RUNNING UNDER гEOдEBUGGER - DOCUMENTED VECTORS IN гEOдEBUGGER WEDGE CODE WHICH ARE USEFUL - FIXED "LDA а000" PARSE BUG - FIXED SYM SEARCH BUG - FIXED BUG IN STOPMAIN - FIXED DISASSEMBLY BUG: NOW DISPLAYS CODE WHEN CANNOT FIND LABEL MACRO ERROR BUG STOP KEY BUG CIA1 DDR ASSERTION RTI BUG CENTERING лDфILE USAGE BUG FILE INIT ADDRESS BUG EXIT AFTER DISK ERROR CORRECTED SELECT FILE дб ICONS, SCROLLING BUG FILE дб SELECTION AREA SETU / PR U.E1 BUG DIR / GETBLOCK FROM рам диск BUG FLAGS ON BOOT BUG рбоот MORE INTELLIGENT IGNORES стоп KEY IN LEFT-SIDE MODE REWROTE SOME PRINTING ROUTINES ADDED NEW хиде FEATURE CORRECTED 128 MODE KEYBOARD SCAN PROBLEM ADDED KERNAL CHECKING TO гET1STдIRеNTRY/гETнXTдIRеNTRY AND MADE SOME CORRECTIONS DISPLAY COPYRIGHT MESSAGES DISPLAY DISK NAME WHEN SELECTING FILE TOP-STEP THROUGH INLINE CALLS DISASM UP AND DOWN THROUGH INLINE CALLS PAGE 3 CODE ASSERTS VALUE OF $0000 TO $2ф DUMPD COMMAND SETS лц TO б1$8100 CORRECTED гETбLOCK/пUTбLOCK CORRECTED DISK AND DRIVEA/B COMMANDS CORRECTED пRINTдISKнAME COMMAND REWROTE WAY THAT THE 3 MONITORS READ/WRITE/SWAP MISC. геос VECTORS AND VARIABLES JUST FIXED 64 MODE BUG, MADE TABLE SHORTER USING щ OPERATOR BACKRAM SUPER SHOULD DISABLE да LOADS ------------------------------------------------------------------------------ филес ин тхис дирецторы /STAFF/JIM/GEOS/продуцтс/GEOпROG/GEOдEBUG/сPECS уSEFUL: иNITфORиобUG: DETAILED INFO ON ц128 иNITфORио BUG реунOTES: FULL DOC ON геос реу USAGE AND HOW WE USE IT реуBUGS: HOW TO WARN USER THAT дма USES жиц BANK INFO APPтYPES: INFO ON HOW DESKтOP AND DEBUGGER LOAD APPLICATIONS MEMпROTECT: DETAILED SPEC OF HOW DEBUGGER'S LOADсAVEбYTE ROUTINE WORKS CBMаPPS: INFO ON HOW TO USE PRODUCT TO DEVELOP цбм APPLICATIONS HIDEмODE: ALL ABOUT THE NEW HIDE DEBUGGER SCREEN FEATURE INTERRUPTS: NOTES TO USER ABOUT INTERRUPTS NMI: NOTES ON нми INTERRUPTS, ресторе BOUNCE, ETC RBOOTвARN: WARNING ABOUT RBOOT COMMAND, KNOWN PROBLEMS VIEWцOMMAND: HOW NEW VIEW COMMANDS WORK ENVIRONMENT: VIEW COMMANDS- DECISIONS MADE WISHлIST: IDEAS... нOT USEFUL: 128IDEAS: GENERAL IDEAS ON INSTALLING USER'S иср TRAPPING STRAY INTERRUPTS 40/80 COLUMN SCREEN USAGE ON 128 MEMORY MAP REGISTERS, CLOCK SPEED, KEYBOARD иNITиNTсVC2.OLD: OLD иср INSTALL INFO мини: THINGS NUKED IN мини DEBUGGER TO SAVE SPACE спецс: OUTLINE FOR PRODUCT SPECIFICATION ASSEMиNбASIC: HOW TO USE GEOлINKER TO CREATE басиц APPS BOOT: OLD OUTLINE OF DEBUGGER BOOT SEQUENCE DESIGNдECISIONS: DECISIONS MADE ALONG THE WAY PROBLEMS: UNRESOLVED PROBLEMS IN THE DESIGN CONTEXTсWITCH: INFO ON HOW ц64 / ц128 INTERRUPTS WORK, AND HOW DEBUGGER'S CONTEXT SWITCH WORKS WITH THEM WARNINGS: PROBLEMS IN THE DESIGN FOR WHICH NO SOLUTION EXISTS SCREENдECISIONS: DECISIONS MADE IN DESIGN OF ж2 SCREEN ROUTINES ц128 иNITфORио BUG? оN BOTH THE 64 AND 128, THE циа2 CHIP HAS THE CAPABILITY OF GENERATING AN нми SIGNAL. тO PREVENT THIS FROM OCCURING DURING DISK-ACCESS ROUTINES, THE геос иNITфORио ROUTINE FORCES THE циа2 TO GENERATE ONE INTERRUPT BY SETTING THE циа TIMER VALUE TO A LOW NUMBER LIKE 1. иNITфORио KNOWS THAT IT WILL GET CONTROL WHEN THIS FORCED-нми OCCURS BECAUSE IT SWAPS THE KERNAL ром INTO THE HIGH-MEMORY AREA AND SETS THE KERNAL'S PAGE 3 нми VECTOR (NMIVEC, $0318) TO POINT TO A DUMMY нми ROUTINE. - ON THE ц64, THIS WORKS FINE, EXCEPT FOR THE FACT THAT иNITфORио IS TRASHING ANY нми VECTOR THAT THE APPLICATION WRITES TO $0318. - ON THE ц128, иNITфORио DOES NOT SWAP ром IN CORRECTLY (IT IS CHANGING LOCATION $0001). сO WHEN IT FORCES THIS нми TO OCCUR, THE 6510 USES THE VECTOR AT б1$фффа OR б0$фффа, WHICH NORMALLY POINT TO THE геос нми HANDLER ROUTINE, WHICH SIMPLY DOES AN рти. иF AN APPLICATION CHANGES THE геос нми VECTORS AT б0$фффа AND б1$фффа, THEN THE USER'S HANDLER ROUTINE WILL GET CALLED EVERY TIME иNITфORио IS CALLED. тHE USER'S HANDLER ROUTINE SHOULD POLL THE циа CHIP AND RETURN IMMEDIATELY IF THE нми WAS GENERATED BY THE циа. иF THE USER IS EXPECTING нмиS FROM THE циа CHIP, THEN THIS "POLLING" PROCESS MUST ALSO INCLUDE AN EXAMINATION OF THE STACK TO SEE IF иNITфORио IS IN PROGRESS... цONCLUSION: дUE TO THE FACT THAT иNITфORио MAKES SOME ASSUMPTIONS ON THE ц128, USERS WHO WRITE THEIR OWN нми HANDLER ROUTINE WILL HAVE TROUBLE. пOSSIBLE FIXES: ц64 AND ц128 иNITфORио SHOULD BOTH BRING ром IN, AND SHOULD BOTH SAVE THE нми VECTOR AT $0318 (BANK 0 ON THE 128), AND RESTORE IT LATER. тHIS WOULD MAKE иNITфORио WORK ALL THE TIME (REGARDLESS OF WHAT THE USER HAS DONE TO THE VECTORS) AND IT WOULD NOT AFFECT THE APPLICATION'S VECTORS. 1764/1700/1750 рAM еXPANSION уNITS ---------------------------------- 1764: 128к 2 64к BANKS, INTENDED FOR ц64 CAN BE EXPANDED TO 512к 1ST 64к BANK: геос SYSTEM STUFF. 2ND BANK UNUSED. 1700: 256к 4 64к BANKS, INTENDED FOR ц128 CAN BE EXPANDED TO 512к 1ST 64к BANK: геос SYSTEM STUFF. 2ND - 4TH BANKS: 1541 рам диск OR 1541 DISK SHADOW. 1750: 512к 8 64к BANKS, INTENDED FOR ц128 CAN BE MADE TO WORK ON ц64 1ST 64к BANK: геос SYSTEM STUFF. 2ND BANK UNUSED. 2ND - 8TH BANKS: 1541/1571 рам диск OR 1541/1571 DISK SHADOW. реу бANK #0: (1ST BANK) бANK #0 IS RESERVED FOR геос KERNAL USE. геос WILL, HOWEVER, HONOR SOME ENABLE BITS IN SYSрамфLG AND ITS' SHADOW VARIABLE SYSфLGцOPY. бY CLEARING SOME OF THESE BITS, YOU CAN PREVENT геос FROM USING CERTAIN AREAS, AND THEN YOUR APPLICATION CAN USE сTASHрам, фETCHрам, ETC TO STUFF DATA UP THERE. ц128 64 геос 128 геос цONTROL BIT ----------------------- ----------------------- ------------- $0000 - $38фф мOVEдATA SWAP AREA мOVEдATA SWAP AREA 1ььььььь $3900 - $78фф мOVEдATA SWAP AREA геос KERNAL FOR рбOOT NOTE 1 $7900 - $7дфф тOбASIC CODE тOбASIC CODE ьь1ььььь $7е00 - $82фф геос KERNAL FOR рбOOT геос KERNAL FOR рбOOT ьь1ььььь $8300 - $б8фф дEVICE DRIVERS а, б, ц дEVICE DRIVERS а,б,ц ь1ьььььь $б900 - $фц3ф геос KERNAL FOR рбOOT геос KERNAL FOR рбOOT ьь1ььььь $фц40 - $фффф ??? ??? ??? нOTE 1: DIFFERENT FOR 64/128. реу бANKS 1 THROUGH 7: уSED BY DEVICE DRIVERS FOR рам диск AND SHADOWING. иT IS A REAL BAD IDEA TO TOUCH THESE BANKS. ------------------------ реу дма нотес: DISABLE SHARING WHEN USING реу дма RELOCATION HIGH BYTE: ONLY б0 R/W CAPABLE, MUST WRITE TO LOW BYTE BEFORE CAN READ INFO BACK FROM HIGH BYTE (INDICATING RELOCATION IS ACTIVE) мIGHT BE ABLE TO USE THIS TO DECIDE WHETHER OR NOT нми OCCURRED WHILE SOMEONE WAS STUFFING VALUES IN THESE REGISTERS. ------------------------ мATT: и GUESS IT IS REALLY ONLY 1 BUG, AND IT IS NOT A BUG IF THE USER IS USING THE STANDARD геос SCREEN FOR DISPLAY, AND IS NOT TRYING TO дма DATA TO BACKRAM (BANK 0). тHERE ARE A NUMBER OF CONCERNS WHEN USING THE реу'S дма CHIP ON A ц128: 1) THE CLOCK MUST BE SLOW (1мхз, NOT 2мхз) 128 геос HANDLES THIS CORRECTLY. 2) THE ио SPACE MUST BE IN, SO YOU CAN ACCESS THE дма CHIP (BIT 0 OF $FF00 "CONFIG" MUST BE A 0) UNDER 128 геос, THE ио SPACE IS ALWAYS IN. 3) WHEN THE дма CHIP FORMS AN ADDRESS FOR WHERE IN THE ц128'S 128к TO READ AND WRITE, IT IGNORES THE STANDARD BANK 0 / BANK 1 SELECTION CONTROLS AND THE "BANK SHARING" CONTROLS. тHESE CONTROLS и AM TALKING ABOUT ARE BITS 7 AND 6 OF $фф00 (CONFIG) AND BITS 5 THROUGH 0 OF $д506 (рцр) IN THE ио SPACE. тHE дма CHIP KNOWS WHICH OF THE TWO 64к BANKS TO USE BECAUSE IT USES THE SAME BANK 0 / BANK 1 CONTROL LINE THAT THE жиц CHIP USES. тHIS CAN BE USEFUL: NO MATTER WHAT BANK SETUP YOU HAVE FOR THE 8510 PROCESSOR CHIP, YOU CAN HAVE THE дма CHIP READ/WRITE TO ANYWHERE IN EITHER BANK. нOW DEPENDING ON WHICH BANK THE жиц CHIP IS LOOKING AT AND WHICH BANK YOU WANT TO р/в TO, YOU MAY HAVE TO CHANGE THE жиц CHIP BANK # SETTING TEMPORARILY (WILL CAUSE SCREEN TO FLASH). цODE TO DO THIS: (ASSUMES R0-R3л HAVE ALREADY BEEN SET UP FOR сTASHрам) ;FIRST, и ASSUME ио SPACE IS IN, BECAUSE UNDER ;128 геос, $фф00 = $7е, MEANING ио IS IN. LDA MMU+6 ;GET "рAMцONTROLрEGISTER" PHA ;SAVE CURRENT BANK SHARING ;STATUS AND жиц BANK # INFO ;ON STACK AND #%00111111 ;KEEP б5-б0 INTACT ORA #банк << 6 ;SET бIT 6 ACCORDING TO BANK WE ;WANT жиц AND дма CHIPS TO SEE STA MMU+6 ;SAVE NEW жиц BANK # INFO JSR сTASHрам/фETCHрам ETC... ;CALL геос TO TURN ON дма CHIP PLA ;RESTORE жиц BANK # STA MMU+6 цOMMODORE 64/128 геос фILE TYPES, AND IF THE DESKтOP AND/OR GEOдEBUGGER CAN LOAD THEM. цбм геос оPEN FROM TYPE FILE TYPE DESKтOP дESCRIPTION ---- --------------- ------- --------------------------------------- дел ANYTHING NO дELETED FILE сея нот_геос NO цOMMODORE SEQUENTIAL DATAFILE, PROBABLY GENERATED BY басиц PROGRAM. сея дата NO сAME AS ABOVE, WITH HEADER ADDED BY иCON еDITOR. ---- --------------- ------- ------------------------------------------------ прг нот_геос YES *1 цOMMODORE басиц OR ASSEMBLY PROGRAM. иF THE FILE IS A басиц PROGRAM, THEN IT WAS PROBABLY CREATED USING ц64 OR ц128 басиц'S "саже" COMMAND. тHE DESKтOP CAN ALWAYS LOAD SUCH A PROGRAM, AND IN SOME CASES CAN тURBO-LOAD IT. иF THE FILE IS AN ASSEMBLY-LANGUAGE PROGRAM, THEN IT WAS PROBABLY CREATED USING AN ASSEMBLER UTILITY, OR USING ц128 басиц'S "бсаже" COMMAND. прг басиц YES *2 цOMMODORE басиц PROGRAM, WITH HEADER BLOCK ATTACHED BY иCON еDITOR. иF PROGRAM IS LESS THAN 31к IN SIZE, THE DESKтOP WILL HAVE геос тURBO-LOAD IT. прг ассемблы YES *3 цOMMODORE ASSEMBLY PROGRAM, WITH HEADER BLOCK ATTACHED BY иCON еDITOR. иF PROGRAM LOADS TO APPLICATION SPACE ($400-$7ффф), THEN THE DESKтOP WILL HAVE геос тURBO-LOAD IT. ---- --------------- ------- ------------------------------------------------ уср нот_геос NO оLD цOMMODORE "USER" FILE. уср басиц NO иллегал цомбинатион уср ассемблы NO иллегал цомбинатион уср дата NO иллегал цомбинатион уср сыстем NO геос SYSTEM FILE (сея OR жлир STRUCTURE) уср деск_ацц YES геос DESK ACCESSORY (сея STRUCTURE) уср апплицатион YES геос APPLICATION FILE (сея OR жлир) уср аппл_дата YES DATA FILE FOR A геос APP. (сея OR жлир) уср фонт NO геос FONT FILE (жлир) уср принтер NO геос PRINTER DRIVER (сея) уср инпут_дежице NO геос INPUT DEVICE (MOUSE, KOALA, ETC. сея) уср диск_дежице NO геос DISK DEVICE DRIVER уср сыстем_боот NO геос SYSTEM BOOT FILE (FOR геос, геос боот, геос кернал) уср темпорары NO тEMPORARY FILE TYPE, FOR SWAP FILES. уср ауто_еьец YES аPP (сея OR жлир) WHICH LOADS AND RUNS UPON BOOT уср инпут_128 NO геос 128 иNPUT DRIVER ---- --------------- ------- ------------------------------------------------ рел нот_геос NO цOMMODORE RANDOM-ACCESS DATAFILE, AS IF GENERATED BY басиц PROGRAM. цANNOT BY GIVEN AN ICON BY иCON еDITOR BECAUSE WOULD DESTORY EXISTING POINTER TO DATA CHAIN. ---- --------------- ------- ------------------------------------------------ нOTES: *1: (прг, нот_геос) вHEN YOU TRY TO OPEN THIS TYPE OF PROGRAM FROM THE DESKтOP, THE DESKтOP'S "дOбASICлOAD" ROUTINE WILL LOAD THE PROGRAM'S FIRST DATA BLOCK, TO CHECK ITS LOAD ADDRESS. ADDR < $0400 иS A "STACK-GRABBING" ASSEMBLY LANGUAGE PROGRAM. геос CANNOT тURBO-LOAD THIS, SO WE FORCE басиц TO EXECUTE: лоад "NAME",8,1. ADDR = $0801 ($1ц01 ON 128) иS A басиц PROGRAM. тHE DESKтOP WILL CHECK THE FILE SIZE INFORMATION IN THE DIRECTORY ENTRY TO SEE IF THE PROGRAM CAN BE тURBO-LOADED. иF THE басиц PROGRAM IS <= 30480 BYTES, THE DESKтOP WILL HAVE геос тURBO-LOAD IT, AND THEN FORCE басиц TO EXECUTE THE рун COMMAND. иF THE басиц PROGRAM IS LARGER THAN THIS, THE DESKтOP WILL NOT LOAD IT. ADDR = OTHER тHE ц64 DESKтOP WILL NOT ALLOW YOU TO LOAD THIS APPLICATION. тHIS IS SO THE DESKтOP WILL NOT ATTEMPT TO RUN A ц128 басиц PROGRAM UNDER ц64 басиц. тHE ц128 DESKтOP WILL USE THE басиц "боот" COMMAND TO LOAD THIS FILE. иF YOU ATTEMPT TO OPEN SUCH A PROGRAM FROM гEOдEBUGGER, IT MUST HAVE A LOAD ADDRESS OF $0400 OR HIGHER. гEOдEBUGGER WILL NOT CHECK THE LOAD ADDRESS TO SEE IF THE PROGRAM IS басиц CODE, SO YOU CAN USE GEOдEBUGGER TO EXAMINE THE INTERNAL STRUCTURE OF ц64 AND ц128 басиц PROGRAMS. *2: (прг, басиц) тHE DESKтOP WILL ATTEMPT TO LOAD SUCH A FILE IN THE SAME MANNER AS THE "ADDR = $0801" CASE ABOVE. аS NOTED ABOVE, THE DEBUGGER CAN ALSO LOAD SUCH A PROGRAM FILE. *3: (прг, ассемблы) вHEN YOU TRY TO OPEN THIS TYPE OF FILE FROM THE DESKтOP, THE DESKтOP'S "дOаSSEMBLYлOAD" ROUTINE WILL LOAD THE FILE'S FIRST DATA BLOCK, TO CHECK ITS LOAD ADDRESS. ADDR < $0400 иS A "STACK-GRABBING" ASSEMBLY LANGUAGE PROGRAM. геос CANNOT тURBO-LOAD THIS, SO THE DESKтOP FORCES басиц TO EXECUTE: лоад "NAME",8,1. $0400 <= ADDR < $0800 тHE ц64 DESKтOP WILL NOT ALLOW YOU TO LOAD THIS PROGRAM, BUT THE ц128 DESKтOP WILL. ADDR >= $0800 тHE DESKтOP WILL LOAD THE PROGRAM'S HEADER BLOCK, TO CHECK ITS ENDING ADDRESS. иF THE PROGRAM ENDS BELOW $8000, THE DESKтOP WILL HAVE геос тURBO-LOAD THE PROGRAM. басиц WILL THEN EXECUTE A сыс TO THE PROGRAM'S INIT ADDRESS FROM THE HEADER BLOCK. иF THE PROGRAM ENDS AT OR ABOVE $8000, THE DESKтOP WILL FORCE басиц TO EXECUTE: лоад "NAME",8,1:сыс (INIT ADDRESS) иF YOU ATTEMPT TO OPEN SUCH A PROGRAM FROM гEOдEBUGGER, IT MUST HAVE A LOAD ADDRESS OF $0400 OR HIGHER. гEOдEBUGGER WILL SET THE пц TO THE VALUE OF THE INIT ADDRESS WHICH IS STORED IN THE HEADER BLOCK. гEOдEBUGGER WILL NOT CHECK THE ENDING ADDRESS OF THE PROGRAM. гEOдEBUGGER мEMORY рEAD/вRITE рOUTINE ------------------------------------- вHENEVER THE DEBUGGER IS ASKED TO READ OR WRITE A BYTE TO MEMORY, IT WORKS THROUGH THE лOADбYTE/сAVEбYTE ROUTINE IN мONITOR/C64IO. еXAMPLES INCLUDE: - EXAMINING AND MODIFYING MEMORY USING "а" OR "м" OPEN COMMANDS - SETTING AND CLEARING INSTRUCTION BREAKPOINTS - MEMORY RANGE COMMANDS: MOVE, FILL, DIFF, FIND тHESE TWO ROUTINES ARE BOTH VERY SHORT: THEY SIMPLY SET A FLAG INDICATING WHETHER WE ARE READING OR WRITING, AND THEN CALL лOADсAVEбYTE. лOADсAVEбYTE GOES THROUGH A FOUR STEP PROCESS TO DETERMINE WHAT TO DO WITH THE MEMORY ACCESS REQUEST. тHIS IS A COMPLICATED PROCESS BECAUSE THERE ARE MANY CASES WHERE A DIRECT LOAD/SAVE IS OUT OF THE QUESTION: - THE USER IS TRYING TO MODIFY A BYTE IN ZERO PAGE, BUT THE MONITOR KEEPS THE USER'S ZERO PAGE IN THE MONITOR VARIABLE SPACE - THE USER IS TRYING TO MODIFY A BYTE IN THE APPLICATION SPACE, BUT IT HAS BEEN SWAPPED OUT TO THE реу - THE USER IS TRYING TO WRITE OVER MONITOR CODE - THE USER IS TRYING TO READ/WRITE TO THE OTHER BANK THAN IS CURRENTLY IN DURING MONITOR EXECUTION. - THE USER IS TRYING TO MODIFY цпу_дата OR CONFIG, WHICH WOULD IMMEDIATELY CHANGE THE MEMORY MAP AND PROBABLY CRASH THE DEBUGGER. лOADсAVEбYTE'S FOUR STEP PROCESS CAN BE BROKEN DOWN AS: 1) хANDLE MEMORY MAP CONTROLS AT $0000, $0001, AND $фф00 (128) AS A SPECIAL CASE. 2) иF THIS ACCESS IS IN THE ио SPACE, AND ио IS ENABLED, USE THE ио аддресс табле TO DECIDE WHICH ио LOCATIONS HE CAN MODIFY DIRECTLY AND WHICH ONES WE KEEP SHADOWS FOR IN THE MONITOR VARIABLE AREA. 3) иF THIS ACCESS IS IN A SPACE WHERE ром IS CURRENTLY IN, THEN ONLY ALLOW READ OPERATIONS. тHE DEBUGGER DOES NOT ALLOW "BLEED THROUGH" WRITES TO RAM UNDERNEATH ROM. 4) иF NONE OF THE ABOVE CASES HOLD, THEN THE ACCESS MUST BE TO RAM. цALCULATE THE EFFECTIVE BANK NUMBER (128 ONLY), AND USE THE рам аддресс табле TO DECIDE WHICH LOCATIONS NEED RE-DIRECTION OR ARE ILLEGAL. хERE IS THE KEY USED IN THE LOOKUP TABLES ON THE FOLLOWING PAGES: MINI / SUPER / BACK SUPER м = MINI DEBUGGER CODE AREA (ILLEGAL TO READ/WRITE) с = SUPER DEBUGGER CODE AREA (MUST READ/WRITE TO реу SPACE) б = BACKRAM SUPER DEBUGGER CODE AREA (ILLEGAL TO READ/WRITE) ь = USED BY ALL THREE MONITORS, NO COPY SAVED (ILLEGAL TO READ/WRITE) т = SUPER DEBUGGER TEXT SCREEN AREA (цолор_матриь: R/W TO реу SPACE) р = READ ONLY д = READ/WRITE DIRECTLY з = ZERO PAGE RAM WHICH MONITOR USES (MUST READ/WRITE TO SAVED COPY OF AREA) NA = NOT APPLICABLE (FOR EXAMPLE, ио CANNOT SHOW UP AT $0400) сTEP 1: CHECK FOR OVERRIDING ио LOCATIONS ----------------------------------------- пSEUDO-CODE: ц64мODE: $0000 DIRECT, READ ONLY $0001 <--> APPмEMмAP (MEMORY MAP INFO) ц128: $0000 DIRECT, READ ONLY $0001 <- б2 AND б1 -> APPцпу_б21 (VIDEO CONTROL INFO) <- OTHER BITS -> APPмEMмAP (NON ESSENTIAL INFO) $фф00 <--> APPцONFIG (MEMORY MAP INFO) $фф01-$фф04 SPECIAL CASE: IS READING пцра-пцрд OR IS SENDING ONE OF THOSE FOUR TO цONFIG сTEP 2: CHECK FOR ио SPACE ACCESSES ----------------------------------- ио аддресс табле ц64 мODE....... ц128 мODE.............. мEMORY RANGE USAGE / геос EQUATE ио ио ------------- ----------------------- ------- ------- ------- ------- ------- $0000 - $д010 RAM / IO: жиц REGS д/д д/д/д $д011 * IO: жиц GRCTRL1 APPжиц1 APPжиц1 $д012 - $д014 IO: жиц REGS д/д д/д/д $д015 * IO: жиц MOBENBLE APPжиц2 APPжиц2 $д016 * IO: жиц GRCTRL2 APPжиц3 APPжиц3 $д017 IO: жиц REG д/д д/д/д $д018 * IO: жиц GRMEMPTR APPжиц4 APPжиц4 $д019 - $д020 IO: жиц REGS д/д д/д/д $д021 * IO: жиц BAKCLR0 APPжиц5 APPжиц5 $д022 - $д02ф IO: жиц REGS д/д д/д/д $д030 * IO: ц128 2мхз CTRL д/д APPцLK $д031 - $д4фф RAM / IO / ROM д/д д/д/д $д500 * IO: ц128 мму CONTROL д/д APPцONFG $д501 - $д504 IO: ц128 мму REGS д/д д/д/д $д505 * IO: ц128 мму мцр д/д р/р/р $д506 * IO: ц128 мму "рцр" д/д APPрцр*1 $д507 - $д50а * IO: ц128 мму зп RELOC д/д р/р/р $д50б - $д7фф RAM / IO / ROM д/д д/д/д $д800 - $дбфф * IO: TEXT COLORS "CTAB" р/р *2* $дц00 - $дцфф RAM / IO / ROM д/д д/д/д $дд00 * IO: CIA2BASE (жиц MMAP) APPциа2_б10 *3* APPциа2_б10 $дд01 - $дефф RAM / IO / ROM д/д д/д/д $дф00 - $дф09 * IO: реу дма CONTROL р/р р/р/р $дф0а - $еффф RAM / IO / ROM д/д д/д/д $ф001 - $фффф RAM / ROM д/д д/д/д ------------- ----------------------- ------- ------- ------- ------- ------- цONCLUSIONS: нO DIFFERENCES BETWEEN THREE DEBUGGERS- JUST BETWEEN TWO MACHINES. оNLY THREE POSSIBLITIES: DIRECT, READ-ONLY, OR ONE OF SEVERAL SPECIAL CASE ROUTINES. фOR EACH AREA, NEED BYTE IN TABLE WHICH CONTAINS TWO THREE-BIT CODES, DENOTING WHAT TO DO ON THAT MACHINE. тABLE SIZE: 25 LINES * (1 WORD + 1 BYTE) = 75 BYTES пLUS жиц HANDLER ROUTINE (USES ADDRESS TO SEE WHICH жиц REGISTERS WE WANT, AND THEN READS/WRITES TO MONITOR SHADOW FOR THAT REGISTER. пLUS HANDLER ROUTINES FOR APPцLK, APPцONFIG, APPрцр, AND APPциа2_б10. ноте 1: IN 128 MODE, $д506 IS SPLIT UP BETWEEN APPрцр_б76 (жиц BANK INFO) AND APPрцр_б50 (MEMORY MAP INFO). ноте 2: THE TEXT SCREEN COLOR TABLE IS LOCATED AT $д800-$дбфф. иN ц64 MODE, WE ONLY ALLOW READS FROM THIS AREA, SO THE USER WON'T SCREW UP THE MONITOR'S TEXT COLORS. иN ц128 MODE, THERE ARE ACTUALLY TWO COLOR TABLES AT THIS LOCATION. бIT 1 OF $0001 DETERMINES WHICH IS VISIBLE TO THE 6510. иF THIS BIT IS CLEAR, WE ALLOW DIRECT READ/WRITES. иF THIS BIT IS SET, WE ONLY ALLOW READS. ноте 3: BITS 1-0 OF LOCATION $дд00 CONTROL WHICH 16к MEMORY BANK THE жиц CHIP USES, AND SO ARE SAVED IN APPциа_б10. тHE OTHER BITS (7-2) ARE WRITTEN TO/ READ FROM MEMORY. цAUTION ERIC: IN ц64 MODE, MAKE SURE ио IS IN WHEN DOING THIS. пSEUDO-цODE: IF THE ADDRESS IS BETWEEN $д000 AND $дффф: ц64: CHECK LOCATION $0001. иF (б1=1 OR б0=1), THEN и/о SPACE IN. иF б2=0, THEN 4к цхар ром IS VISIBLE: ONLY ALLOW READS. иF б2=1, THEN 4к OF и/о DEVICES ARE VISIBLE: CALL TABLE LOOKUP ROUTINE, USING ио аддресс табле. USE б5-б3 OF RETURN BYTE TO DECIDE WHAT TO DO. ELSE CAN READ/WRITE DIRECTLY ц128: CHECK LOCATION $фф00: иF (б0=0), THEN и/о SPACE IS IN. CALL TABLE LOOKUP ROUTINE, USING ио аддресс табле. USE б2-б0 OF RETURN BYTE TO DECIDE WHAT TO DO. ELSE CAN READ/WRITE DIRECTLY ELSE (ADDRESS IS NOT IN ио RANGE) GO TO STEP 3 сTEP 3: CHECK FOR ром ACCESS ---------------------------- ц64 мODE рOM тRUTH тABLE LOCATION $0001 мEMORY RANGE вHAT мIGHT бE тHERE 76543210 нOTES ------------- ----------------------- --------------- ------------------------ $0000 - $9ффф RAM -------- $а000 - $бффф RAM / бASIC ROM -------1 б0=1 $ц000 - $дффф RAM *1* -------- $е000 - $фффф RAM / кERNAL ROM ------1- б1=1 нOTE THAT THERE ARE CASES WHERE CARTRIDGES PLUGGED INTO THE ц64 CAN OVERRIDE THESE AREAS. тHE ц64 пROG. рEF. гUIDE IS NOT VERY CLEAR ON THIS, SO и WILL NOT BE CONCERNED ABOUT CARTRIDGES FOR NOW. едс 2/8/88. нOTE 1: THE CASE WHERE цхар ром IS MAPPED IN FROM $д000 TO $дффф HAS ALREADY BEEN HANDLED BY ио TABLE. ц128 мODE рOM тRUTH тABLE LOCATION $фф00 мEMORY RANGE вHAT мIGHT бE тHERE 76543210 нOTES ------------- ----------------------- --------------- ------------------------ $0000 - $3ффф RAM -------- $4000 - $7ффф RAM / бASIC ROM LOW ------0- б1=0 $8000 - $бффф RAM / бASIC ROM HIGH ----AB-- б3=0 OR б2=0 $ц000 - $фффф RAM / кERNAL ROM --AB---- б5=0 OR б4=0 и DON'T COMPLETELY UNDERSTAND ц128 EXTERNAL ROMS YET. и AM GOING TO ASSUME THAT б5-б1 IN $фф00 DETERMINE IF THERE IS ANY ром IN. и DON'T CARE IF IS кERNAL, EXTERNAL, INTERNAL, OR CARTRIDGE ROM. и JUST WON'T WRITE TO THOSE RANGES IF THE BITS ARE CLEAR. пSEUDO-CODE: аS IT TURNS OUT, THE FASTEST AND TIGHTEST CODE TO HANDLE THIS SIMPLY CHECKS ADDRESS RANGES AND BITS DIRECTLY. сEE THE CODE. сTEP 4: рам ACCESS ------------------ ц64 мODE ц128 мODE...... мEMORY RANGE USAGE / геос EQUATE рам рам б1 рам б0 ------------- ----------------------- ------- ------- ------- $0000 - $0001 аLREADY HANDLED BY STEP 1. $0002 - $00дд * ZERO PAGE (MON SWAPS) з/з NA з/з/з $00де - $00фф ZERO PAGE д/д NA д/д/д $0100 - сп * STACK (MONITOR USES) ь/ь NA ь/ь/ь сп+1 - $01фф STACK (USER'S DATA) д/д NA д/д/д *1* $0200 - $0313 RAM д/д д/д/д д/д/д $0314 - $0319 * BASиряжEC, брк, нми р/р д/д/д р/р/р $031а - $0333 RAM д/д д/д/д д/д/д $0334 - $03фб * MONITOR CODE ь/ь ь/ь/ь ь/ь/ь $03фц - $03фф MONITOR йср AREA д/д д/д/д д/д/д $0400 - $1ффф * RAM д/с д/с/д д/д/д $2000 - $3бфф * RAM д/с д/с/д д/д/б $3ц00 - $5ффф * RAM м/с м/с/д д/д/б $6000 - $78фф * RAM д/с д/с/д д/д/б $7900 - $8бфф * RAM д/д д/д/д д/д/б $8ц00 - $8фе7 * RAM (MONITOR TEXT SCR) р/т р/т/д д/д/б $8фе8 - $9ффф * RAM д/д д/д/д д/д/б $а000 - $ффф9 RAM / ROM IF >$д000 д/д д/д/д д/д/д $фффа - $фффф * нми_жецтор, ресет, иря р/р р/р/р р/р/р ------------- ----------------------- ------- ------- ------- ------- ------- цONCLUSIONS: мINI DEBUGGER AND сUPER DEBUGGERS ARE COMPLETELY DIFFERENT CASES. уSE CONDITIONAL ASSEMBLY TO DECIDE WHICH TABLE TO USE. мINI DEBUGGER HAS FOUR POSSIBILITIES: DIRECT, READ-ONLY, ILLEGAL, AND ZERO PAGE. фOR EACH AREA, NEED BYTE IN TABLE WHICH CONTAINS TWO THREE-BIT CODES, DENOTING WHAT TO DO ON THAT MACHINE. тABLE SIZE: 15 LINES * (1 WORD + 1 BYTE) = 45 BYTES аLL TABLE VALUES ARE STANDARD CASES. тHE SUPER DEBUGGER'S TABLE IS SIMILAR: FOR EACH AREA, THERE ARE SIX POSSIBILITIES, ALL STANDARD. тHE TABLE NEEDS TO GIVE US A WORD VALUE WHICH CONTAINS FIVE THREE-BIT CODES: MACHINE MONITOR ACCESS TYPE BITS IN WORD --------------- --------------- --------------- ------------ 128 MODE BACKRAM SUPER BANK 0 ACCESS б14-б12 128 MODE BACKRAM SUPER BANK 1 ACCESS б11-б9 128 MODE реу SUPER BANK 0 ACCESS б8-б6 128 MODE реу SUPER BANK 0 ACCESS б2-б0 64 MODE реу SUPER б5-б3 --------------- --------------- --------------- ------------ тABLE SIZE: 18 LINES * (1 WORD + 2 BYTES) = 76 BYTES аLL TABLE VALUES ARE STANDARD CASES. ноте 1: THE REGION сп+1 TO $313 CAN BE COMBINED, BECAUSE THE EFFECTIVE BANK CALCULATION WILL NOT GIVE AN ADDRESS <$200 IN BANK 1. пSEUDO-CODE: FIRST CALCULATE EFFECTIVE BANK (ONLY NECESSARY ON ц-128) IF ADDRESS IS LESS THAN $200, IS бANK 0. IF APPцONFIG б6 = 1 THEN (ноте: IGNORE б7) (BANK 1 IS ENABLED, BUT WE MUST CHECK RAM SHARING) IF ADDRESS HIGH BYTE >= $80 IF APPрцр б3 = 1 USE LOOKUP TABLE FOR APPрцр б1-б0: 00 $фц 01 $ф0 10 $е0 11 $ц0 IF ADDRESS HIGH BYTE < THIS VALUE, IS BANK 1 ELSE IS BANK 0 ELSE IS BANK 1 ELSE (ADDRESS HIGH BYTE < $80) IF APPрцр б2 = 1 USE LOOKUP TABLE FOR APPрцр б1-б0: 00 $04 01 $10 10 $20 11 $40 IF ADDRESS HIGH BYTE >= THIS VALUE, IS BANK 1 ELSE IS BANK 0 ELSE IS BANK 1 ELSE IS BANK 0 тхесе бит нумберс хаже цхангед тHEN USE TABLE TO DETERMINE WHAT TO DO WITH THAT ADDRESS, CONSIDERING THE MACHINE, MONITOR TYPE, AND BANK DESIRED. IF USING MINI DEBUGGER CALL TABLE LOOKUP ROUTINE, USING мини рам аддресс табле IF IN ц64 MODE: USE б5-б3 OF RETURN BYTE TO DECIDE WHAT TO DO. ELSE (ц128 MODE): USE б2-б0 OF RETURN BYTE TO DECIDE WHAT TO DO. IF USING SUPER DEBUGGER: CALL TABLE LOOKUP ROUTINE, USING мини рам аддресс табле IF IN ц64 MODE: USE б5-б3 OF RETURN BYTE TO DECIDE WHAT TO DO. ELSE (ц128 MODE): IF SUPER DEBUGGER IF ACCESSING BANK 1 USE б2-б0 OF RETURN WORD IF ACCESSING BANK 0 USE б8-б6 OF RETURN WORD IF BACKRAM SUPER DEBUGGER IF ACCESSING BANK 1 USE б11-б9 OF RETURN WORD IF ACCESSING BANK 0 USE б14-б12 OF RETURN WORD тHIS DECISION TREE SEEMS FAIRLY COMPLICATED, BUT IT BREAKS DOWN PRETTY WELL IN THE CODE. гENERAL мEMORY пROTECT мAP -------------------------- ц64 мODE....... ц128 мODE.............. мEMORY RANGE USAGE / геос EQUATE рам ио рам б1 рам б0 ио ------------- ----------------------- ------- ------- ------- ------- ------- $0000 * цпу_ддр 6510 ддр ALL CASES: р/р ALL CASES: р/р $0001 * цпу_дата 6510 DATA PORT <-> APPмEMмAP <-> APPцпу_б21+APPмEMмAP $0002 - $00дд * ZERO PAGE (MON SWAPS) з/з NA NA з/з/з NA $00де - $00фф ZERO PAGE д/д NA NA д/д/д NA $0100 - сп * STACK (MONITOR USES) ь/ь NA NA ь/ь/ь NA сп+1 - $01фф STACK (USER'S DATA) д/д NA NA д/д/д NA $0200 - $0313 RAM д/д NA д/д/д д/д/д NA $0314 - $0319 * BASиряжEC, брк, нми р/р NA д/д/д р/р/р NA $031а - $0333 RAM д/д NA д/д/д д/д/д NA $0334 - $03фб * MONITOR CODE ь/ь NA ь/ь/ь ь/ь/ь NA $03фц - $03фф MONITOR йср AREA д/д NA д/д/д д/д/д NA $0400 - $1ффф * RAM д/с NA д/с/д д/д/д NA $2000 - $3бфф * RAM д/с NA д/с/д д/д/б NA $3ц00 - $3ффф * RAM м/с NA м/с/д д/д/б NA $4000 - $5ффф * RAM (бг SCREEN) м/с NA м/с/д д/д/б NA $6000 - $78фф * RAM д/с NA д/с/д д/д/б NA $7900 - $8бфф * RAM д/д NA д/д/д д/д/б NA $8ц00 - $8фе7 * цолор_матриь / RAM д/д NA д/д/д д/д/б NA $8фе8 - $8ффф * RAM д/д NA д/д/д д/д/б NA $9000 - $9ффф * RAM д/д NA д/д/д д/д/б NA $а000 - $бффф RAM (фг SCREEN) д/д NA д/д/д д/д/д NA $ц000 - $цффф RAM д/д NA д/д/д д/д/д NA $д000 - $д010 IO: жиц REGS д/д д/д д/д/д д/д/д д/д/д $д011 * IO: жиц GRCTRL1 д/д APPжиц1 д/д/д д/д/д APPжиц1 $д012 - $д014 IO: жиц REGS д/д д/д д/д/д д/д/д д/д/д $д015 * IO: жиц MOBENBLE д/д APPжиц2 д/д/д д/д/д APPжиц2 $д016 * IO: жиц GRCTRL2 д/д APPжиц3 д/д/д д/д/д APPжиц3 $д017 IO: жиц REG д/д д/д д/д/д д/д/д д/д/д $д018 * IO: жиц GRMEMPTR д/д APPжиц4 д/д/д д/д/д APPжиц4 $д019 - $д020 IO: жиц REGS д/д д/д д/д/д д/д/д д/д/д $д021 * IO: жиц BAKCLR0 д/д APPжиц5 д/д/д д/д/д APPжиц5 $д022 - $д02ф IO: жиц REGS д/д д/д д/д/д д/д/д д/д/д $д030 * IO: ц128 2мхз CTRL д/д д/д д/д/д д/д/д APPцLK $д031 - $д4фф RAM / IO / ROM д/д д/д д/д/д д/д/д д/д/д $д500 * IO: ц128 мму CONTROL д/д д/д д/д/д д/д/д APPцONFG $д501 - $д504 IO: ц128 мму REGS д/д д/д д/д/д д/д/д д/д/д $д505 * IO: ц128 мму мцр д/д д/д д/д/д д/д/д р/р/р $д506 * IO: ц128 мму "рцр" д/д д/д д/д/д д/д/д APPрцр*1 $д507 - $д50а * IO: ц128 мму зп RELOC д/д д/д д/д/д д/д/д р/р/р $д50б - $д7фф RAM / IO / ROM д/д д/д д/д/д д/д/д д/д/д $д800 - $дбфф * IO: TEXT COLORS "CTAB" д/д р/р д/д/д д/д/д *2* $дц00 - $дцфф RAM / IO / ROM д/д д/д д/д/д д/д/д д/д/д $дд00 * IO: CIA2BASE (жиц MMAP) д/д APPциа2_б10 д/д/д д/д/д *3* $дд01 - $дефф RAM / IO / ROM д/д д/д д/д/д д/д/д д/д/д $дф00 - $дф09 * IO: реу дма CONTROL д/д р/р д/д/д д/д/д р/р/р $дф0а - $дффф RAM / IO / ROM д/д д/д д/д/д д/д/д д/д/д $е000 - $еффф RAM / ROM д/д NA д/д/д д/д/д NA $ф000 * ц128: CONFIG REGISTER д/д NA ALL CASES: <-> APPцONFIG $ф001 - $ффф9 RAM / ROM д/д NA д/д/д д/д/д NA $фффа - $фффф * нми_жецтор, ресет, иря р/р NA р/р/р р/р/р NA ------------- ----------------------- ------- ------- ------- ------- ------- аSSUMPTIONS: ром DECODED SEPARATELY ADDRESS DECODE FOR RAM BANK SHARING ALREADY WORKED OUT CAN SIMPLIFY TABLE A BIT WITH .IF мини ноте 1: IN 128 MODE, $д506 IS SPLIT UP BETWEEN APPрцр_б76 (жиц BANK INFO) AND APPрцр_б50 (MEMORY MAP INFO). ноте 2: THE TEXT SCREEN COLOR TABLE IS LOCATED AT $д800-$дбфф. иN ц64 MODE, WE ONLY ALLOW READS FROM THIS AREA, SO THE USER WON'T SCREW UP THE MONITOR'S TEXT COLORS. иN ц128 MODE, THERE ARE ACTUALLY TWO COLOR TABLES AT THIS LOCATION. бIT 1 OF $0001 DETERMINES WHICH IS VISIBLE TO THE 6510. иF THIS BIT IS CLEAR, WE ALLOW DIRECT READ/WRITES. иF THIS BIT IS SET, WE ONLY ALLOW READS. ноте 3: BITS 1-0 OF LOCATION $дд00 CONTROL WHICH 16к MEMORY BANK THE жиц CHIP USES, AND SO ARE SAVED IN APPциа_б10. тHE OTHER BITS (7-2) ARE WRITTEN TO/ READ FROM MEMORY. цAUTION ERIC: IN ц64 MODE, MAKE SURE ио IS IN WHEN DOING THIS. вARN IN MANUAL THAT WE DO NOT ALLOW BLEED-THROUGH. тHEY WILL HAVE TO SWAP RAM IN MANUALLY TO CHANGE IT. тHIS MEANS WE CAN'T USE A SINGLE може COMMAND TO COPY ROM TO RAM... гEOдEBUGGER HAS LIMITED SUPPORT FOR THE CREATION AND DEBUGGING OF цбм APPLICATIONS. тHE ц128 DESKтOP HAS SOME BUGS RELATED TO LOADING цбм APPLICATIONS. гEOпROGRAMMER CURRENTLY SUPPORTS THE ASSEMBLY AND LINK OF: геос APPLICATIONS (сея OR жлир, WITH HEADER) геос DESK ACCESSORIES (сея BY DEFINITION, WITH HEADER) цбм APPLICATIONS STANDARD цOMMODORE прг FILE (геос FILE TYPE = нот_геос, DOES NOT HAVE A HEADER BLOCK). дESKтOP HAS RESTRICTIONS ON WHICH LOAD ADDRESSES IT CAN HANDLE. цOMMODORE басиц'S лоад AND боот COMMANDS CAN LOAD MOST ADDRESSES OK. гEOдEBUGGER CAN LOAD MOST ADDRESSES OK. тHERE IS SOME AMOUNT OF SUPPORT IN THE DEBUGGER FOR LOADING AND DEBUGGING цбм APPLICATIONS. - CAN TOGGLE BETWEEN ANY KIND OF SCREEN THE жиц AND ждц CHIPS SUPPORT - APP CAN TRASH ALL OF геос ADDRESS SPACE пROBLEMS: - ON ц128, DEBUGGER CAN ONLY LOAD A цбм APP TO BANK 1, WHEREAS басиц EXPECTS SUCH AN APPLICATION TO RUN IN BANK 0. еITHER WRITE YOUR APPLICATION TO RUN IN EITHER BANK (SEE сAMPLEцбм), OR USE A CONSTANT SO YOU CAN ASSEMBLE IT TO RUN IN EITHER BANK. - тHE DEBUGGER DOES NOT DO ANY ERROR CHECKING ON THE LOAD ADDRESS OF A цбм APPLICATION. иT WILL CRASH IF YOU TRY TO LOAD AN APP BELOW $400. аPPLICATION CANNOT LOAD ABOVE THE $8000 AREA. - гEOдEBUGGER FILLS THE TEXT COLOR TABLE ONCE. иF THE цбм APPLICATION FILLS THE TEXT COLOR TABLE (TABLE #1 ON THE 128), THE DEBUGGER'S CHARACTERS WILL BE COLORED. иF THE цбм APP FILLS WITH $0б, THE DEBUGGER CHARACTERS WILL BE INVISIBLE, SINCE THE DEBUGGER SETS THE BACKGROUND TO $0б. - IF THE цбм APP PUTS UP A SCREEN WHICH RESIDES IN THE $0400-$7ффф AREA, THEN YOU WILL NOT BE ABLE TO VIEW IT FROM THE SUPER DEBUGGER USING ф7 OR ф8. тHIS IS BECAUSE THESE COMMANDS DO NOT SWAP THE DEBUGGER CODE OUT OF THIS AREA: THE жиц CHIP WILL BE GIVEN THE CORRECT PARAMETERS, BUT IT WILL BE DISPLAYING DEBUGGER CODE INSTEAD OF THE APPLICATION'S SCREEN DATA. вITH A LITTLE BIT OF WORK, YOU CAN GET GEOаSSEMBLER AND GEOлINKER TO GENERATE: аSSEMBLY-иN-бASIC PROGRAM а (прг-нот_геос) APPLICATION WHICH LOOKS LIKE A басиц PROGRAM, BUT REALLY ONLY HAS SEVERAL LINES OF басиц. рEMAINDER IS ASSEMBLY CODE. сея DATAFILE: AS IF WAS CREATED BY басиц. цREATE A геос сея FILE, THEN CHANGE THE цOMMODORE AND геос FILE TYPE BYTES. геос APPLICATION DATAFILE: AS IF WAS CREATED BY A геос APPLICATION. цREATE A геос сея FILE, THEN CHANGE THE геос FILE TYPE BYTE. иN A SIMILAR MANNER, YOU CAN USE гEOдEBUGGER TO EXAMINE A WIDE VARIETY OF DIFFERENT FILE TYPES. бUT FIRST, YOU MUST CHANGE THE цOMMODORE AND/OR геос FILE TYPE BYTE, AND THE LOAD ADDRESS IN THE HEADER BLOCK. фUTURE гEOпROGRAMMER IDEAS: гENERATE цбм аPPLICATION WITH HEADER: еSSENTIALLY A цбм ASSEMBLY-LANGUAGE PROGRAM, BUT WITH A геос HEADER. вOULD SAVE THE иCON еDITOR STEP CURRENTLY REQUIRED. сPECIFICATION OF "HIDE DEBUG SCREEN MODE" ф7 IS PRESSED: тоггле сцреен: SHOW усер SCREEN WAIT FOR PRESS SHOW дебуг SCREEN IF мини: PLACE CURSOR ON LEFT PRINT PROMPT PRINT INPUT LINE AS IT WAS LOOP FOR NEXT CHARACTER ф8 IS PRESSED: IF HIDDEN = фалсе енабле схов моде: CALL тOGGLEсCREEN TO SWITCH USER PARAMETERS TO HARDWARE SET HIDEдEBUGсCREEN = труе LOOP FOR NEXT CHARACTER IF HIDDEN = труе дисабле схов моде: SET HIDEдEBUGсCREEN = фалсе CALL тOGGLEсCREEN TO SWITCH USER PARAMETERS TO SHADOWS, AND DISPLAY DEBUGGER SCREEN IF IN LEFT-SIDE COMMAND MODE (MUST REPRINT LINE BECAUSE NOTHING HAS BEEN PRINTED) PLACE CURSOR ON LEFT PRINT PROMPT PRINT INPUT LINE AS IT WAS IF NOT IN LEFT-SIDE COMMAND MODE CANCEL OPEN MODE / DEPOSIT MODE PRINT PROMPT LOOP FOR NEXT CHARACTER хOW гEOдEBUGGER хANDLES иря иNTERRUPTS -------------------------------------- иF YOU ARE WRITING A NORMAL геос APPLICATION, THEN YOU DO NOT HAVE TO READ THE FOLLOWING INFORMATION. ыOU CAN SKIP AHEAD TO THE SECTION TITLED "сTRAY иNTERRUPT "трап" фACILITY". иF YOU ARE WRITING A NON-геос APPLICATION WHICH SETS UP ITS OWN INTERRUPT SERVICE ROUTINE, THIS INFORMATION IS VITAL; YOUR PROGRAM WILL NOT RUN CORRECTLY UNDER гEOдEBUGGER UNLESS YOU FOLLOW THESE INSTRUCTIONS. нOTE: иср STANDS FOR иNTERRUPT сERVICE рOUTINE. вHEN гEOдEBUGGER IS RUNNING A USER APPLICATION, IT INSERTS A SMALL WEDGE ROUTINE IN PLACE OF THE NORMAL иср (WHICH IN MOST CASES WILL BE THE геос иср). тHIS WEDGE FIRST CHECKS IF THE иря INTERRUPT WAS GENERATED BY THE иря LINE OR A брк INSTRUCTION. иF IT WAS A брк INSTRUCTION, THE WEDGE EXECUTES THE APPROPRIATE MONITOR. иF THE INTERRUPT WAS AN иря, THE WEDGE CALLS THE EXISTING иср. тHUS: THE DEBUGGER IS ABLE TO MONITOR THE иря/брк EVENTS, WITHOUT INTERFERING WITH REGULAR INTERRUPT SERVICING THAT IS VITAL TO MOST APPLICATIONS. тO INSERT THIS WEDGE ROUTINE INTO THE INTERRUPT SEQUENCE, гEOдEBUGGER MUST FIRST EXAMINE THE иря VECTOR AT LOCATION $фффе, TO SEE WHERE THE CURRENT иср IS LOCATED. иT THEN MUST MODIFY THIS VECTOR SO IT WILL POINT TO THE гEOдEBUGGER WEDGE ROUTINE WHICH IS LOCATED IN THE $0334 AREA. иF YOU ARE WRITING A NON-геос APPLICATION WHICH SETS UP ITS OWN иср, THEN YOU WILL PROBABLY WE SETTING THE иря VECTOR AT SOME POINT DURING YOUR INITIALIZATION CODE. иN ORDER FOR YOUR APPLICATION TO RUN UNDER гEOдEBUGGER, YOU MUST SET THIS VECTOR CAREFULLY; BECAUSE IF YOUR APPLICATION IS RUNNING UNDER гEOдEBUGGER, YOU NEED TO STORE THE ADDRESS OF YOUR иср TO A VECTOR IN THE гEOдEBUGGER WEDGE CODE, нот TO THE иря VECTOR. бELOW IS A ROUTINE WHICH YOU CAN INSERT INTO YOUR PROGRAM TO SET UP THE APPROPRIATE VECTOR TO YOUR иср. нOTE THAT THIS ROUTINE ASSUMES THAT YOUR APPLICATION WILL ONLY ALLOW INTERRUPTS WHEN THE MEMORY MAP IS CONFIGURED AS A STANDARD геос MEMORY MAP. оN THE ц64, THIS MEANS ALL рам, AND ON THE ц128, THIS MEANS ALL BANK 1 рам, NO ром. иF YOUR APPLICATION IS GOING TO ALLOW INTERRUPTS IN OTHER MEMORY MAP CONFIGURATIONS, USE THE "иNTERRUPT хANDLING рEFERENCE нOTES" SECTION OF THIS DOCUMENT TO CUSTOMIZE THIS INSTALLATION ROUTINE. иNSERT THE FOLLOWING CONSTANTS AND SUBROUTINE INTO THE INITIALIZATION PHASE OF YOUR APPLICATION, FOR IT TO RUN PROPERLY UNDER гEOдEBUGGER. иN THE CONSTANT DEFINITION PORTION OF YOUR PROGRAM: дежелопмент = труе ;сET TO труе IF YOU SOMETIMES RUN THIS ;APPLICATION UNDER гEOдEBUGGER ж2.0, ;AND RUN IT UNDER THE DESKтOP OTHER TIMES. ;сET TO фалсе IF YOU WILL NEVER RUN THIS ;APPLICATION UNDER гEOдEBUGGER ж2.0. тOиNTсVC = $0367 ;аDDRESS OF гEOдEBUGGER VECTOR WE MODIFY иN THE INITIALIZATION PORTION OF YOUR PROGRAM: ;************************************************************************* ; иNITиNTсVC ; ; тHIS ROUTINE MODIFIES THE иря VECTOR, SO THAT THE USER'S INTERRUPT ; SERVICE ROUTINE IS CALLED INSTEAD OF THE геос INTERRUPT SERVICE ROUTINE. ; тHIS ROUTINE CAN ASSEMBLE ONE OF TWO WAYS, DEPENDING UPON THE ; VALUE OF THE CONSTANT CALLED "дежелопмент". ; ; аSSUMPTIONS: ; 1) тHAT THE STANDARD геос MEMORY MAP IS PRESENT WHEN THIS ROUTINE RUNS. ; 2) тHAT YOUR APPLICATION DOES NOT DO ANYTHING WEIRD SUCH AS ALLOWING ; INTERRUPTS WHEN HIGH-MEMORY ром OR рам BANK 0 (ON THE ц128) IS ; SWAPPED IN. ; ; сIDE-EFFECTS: ; 1) иF THE FOLLOWING SCENARIO APPLIES: ; - YOU ARE WRITING A NON-геос APPLICATION FOR THE ц64 ; - WHICH TRIES TO DISABLE INTERRUPTS WHEN ром IS IN ; - YOU RUN IT UNDER гEOдEBUGGER ; - YOUR PROGRAM SWAPS кERNAL ром IN, WITHOUT PROPERLY ; DISABLING INTERRUPTS ; - AN INTERRUPT OCCURS ; ...THEN гEOдEBUGGER вилл PROPERLY RUN YOUR иср, WITHOUT GIVING ; YOU ANY WARNING THAT THERE IS A BUG IN YOUR PROGRAM, AND THAT IT ; WOULD HAVE CRASHED IF IT WAS NOT RUN UNDER гEOдEBUGGER. ; ; аUTHOR: еRIC е. дEL сESTO аPRIL 1988 ; цALLED BY: INITIALIZATION CODE ; пASS: NOTHING ; рETURNS: NOTHING ; аLTERS: ACCUMULATOR AND FLAGS ; ;************************************************************************ иNITиNTсVC: SEI ;DISABLE INTERRUPTS .IF дежелопмент ;------------------------------------------------ ;аSSEMBLE THE FOLLOWING CODE WHEN YOU WANT YOUR APPLICATION TO RUN CORRECTLY ;UNDER гEOдEBUGGER ж2.0. LDA иря_жецтор+1 ;CHECK HIGH BYTE OF EXISTING иря VECTOR ;TO SEE IF WE ARE RUNNING UNDER DEBUG. BMI 50$ ;SKIP IF NOT... ;WE ARE RUNNING UNDER гEOдEBUGGER: MUST STORE OUR иря VECTOR TO ;THE гEOдEBUGGER CODE IN THE $0334 AREA. иF RUNNING IN ц128 MODE, ;THIS ONLY MODIFIES THE WEDGE CODE IN BANK 1, WHICH IS SUFFICIENT. лOADв тOиNTсVC,#мYиNTсVC CLI ;ENABLE INTERRUPTS RTS ;ALL DONE 50$: ;WE ARE NOT RUNNING UNDER гEOдEBUGGER: SET UP NEW иря VECTOR ;IN NORMAL FASHION. .ENDIF ;(дежелопмент)--------------------------------------------------- ;аT THIS POINT, WE KNOW THAT EITHER THE APPLICATION IS NOT RUNNING UNDER ;гEOдEBUGGER, OR THAT WE DON'T EXPECT IT TO RUN UNDER гEOдEBUGGER (THE CASE ;WHERE дежелопмент = фалсе). иNTERRUPTS HAVE ALREADY BEEN DISABLED ABOVE. ;сET UP THE иря VECTOR AT $фффе TO POINT TO NEW SERVICE ROUTINE. нOTE THAT ;IN ц128 MODE, THIS ONLY AFFECTS THE иря VECTOR IN BANK 1 рам. лOADв иря_жецтор,#мYиNTсVC CLI ;ENABLE INTERRUPTS RTS ;ALL DONE сTRAY иNTERRUPT "трап" фACILITY ------------------------------- ыOU WOULD EXPECT THAT AN APPLICATION WHICH OFTEN HAS TO SWAP IN THE кERNAL ром WOULD BE CAREFUL TO DISABLE INTERRUPTS DURING THESE OPERATIONS. тHIS IS TO PREVENT THE CASE WHERE AN иря OCCURS AND геос INTERRUPT CODE HAS BEEN SWAPPED OUT OF THE MEMORY MAP. оFTEN, IT IS EASY FOR SUCH A PROVISION TO BE LEFT OUT IN THE INITIAL IMPLEMENTATION OF A PROGRAM. тO CATCH THESE HARD-TO-FIND BUGS, гEOдEBUGGER HAS A "STRAY иря TRAP" FACILITY. тHIS FACILITY SERVES TO WARN YOU WHEN AN INTERRUPT HAPPENS AND THE MEMORY MAP IS CONFIGURED IN A MANNER YOU DID NOT EXPECT. иF YOU ARE RUNNING A геос APPLICATION (WITH NORMAL геос INTERRUPTS), THEN THIS FACILITY WILL STOP PROGRAM EXECUTION AND DISPLAY THE "*** еXECUTION STOPPED ***" MESSAGE WHEN AN иря OCCURS AND THE кERNAL ром IS SWAPPED IN. ыOU CAN EXAMINE THE пц REGISTER TO SEE WHICH OF YOUR ROUTINES WAS EXECUTING WHEN THE иря OCCURRED, AND CAN ADD INTERRUPT-DISABLING CODE WHERE NECESSARY. иF YOU ARE WRITING A NON-геос APPLICATION WHICH RUNS ON THE ц128, AND SETS UP ITS OWN INTERRUPT SERVICE ROUTINE, YOU WILL PROBABLY DESIGN IT SO INTERRUPTS ARE ENABLED ONLY WHEN THE MEMORY IF CONFIGURED IN A SPECIFIC WAY. хERE ARE SEVERAL EXAMPLES OF ASSERTIONS YOU MIGHT FIND IN SUCH AN APPLICATION: - "и WILL ONLY ALLOW INTERRUPTS WHEN BANK 1 рам IS MAPPED IN." - "и WILL ONLY ALLOW INTERRUPTS WHEN BANK 0 рам OR ром IS MAPPED IN." бY REFERING TO THE "иNTERRUPT хANDLING рEFERENCE нOTES" SECTION OF THIS DOCUMENT, AND ADDING SOME CODE TO THE INITIALIZATION PORTION OF YOUR PROGRAM, YOU CAN ALTER THE WEDGE CODE SO THAT A трап IS PRODUCED IF AN INTERRUPT OCCURS WHEN THE MEMORY MAP IS IN AN UNEXPECTED CONFIGURATION. (иS IT POSSIBLE TO CONTINUE PROGRAM EXECUTION AT THIS POINT???) иNTERRUPT хANDLING рEFERENCE нOTES иF YOU ARE WRITING A NON-геос APPLICATION, THE FOLLOWING TABLES PROVIDE USEFUL REFERENCE INFORMATION ABOUT THE VECTORS IN гEOдEBUGGER'S WEDGE CODE. бY ADDING CODE TO YOUR APPLICATION WHICH CHANGES THESE VECTORS, YOU CAN GET YOUR INTERRUPT SERVICE ROUTINE TO WORK WHEN YOUR APPLICATION IS RUNNING UNDER гEOдEBUGGER. ыOU CAN ALSO SET THESE VECTORS SO THAT A трап OCCURS IF AN INTERRUPT HAPPENS WHEN THE MEMORY MAP IS SUCH THAT YOUR APPLICATION WOULD CRASH. ц64 мODE -------- лABEL аDDR нORMAL цONTENTS мODIFIED цONTENTS --------------- ------- ------------------------------- ------------------------ рOMиря_жEC: $0338 JMP тRAPром 4ц 45 03 JMP хANDLEиря 4ц 5е 03 - AS IT STANDS, THIS LOCATION WILL CAUSE A трап WHENEVER AN иря HAPPENS AND THE кERNAL ром IS MAPPED INTO HIGH MEMORY. мODIFY THIS LOCATION IF YOU WANT EXECUTION TO CONTINUE TO THE тOиNTсVC VECTOR WHEN ром IS MAPPED INTO HIGH MEMORY. тHE тOиNTсVC VECTOR CAN THEN DIRECT EXECUTION TO YOUR иср. тOиNTсVC: $ьььь JMP гEOSиср 4ц XX XX JMP ыOUR_иср 4ц лл хх -OR- JMP тRAPиря 4ц ьь ьь - AS IT STANDS, THIS LOCATION DIRECTS EXECUTION TO THE геос иср WHEN AN INTERRUPT OCCURS. ыOU CAN MODIFY THIS VECTOR TO POINT TO YOUR OWN иср, OR FORCE A трап WHEN AN иря OCCURS. нOTE THAT IF рOMиря_жEC POINTS TO хANDLEиря, THEN THE тOиNTсVC VECTOR HANDLES ALL иря INTERRUPTS, REGARDLESS OF WHETHER рам OR ром IS IN. ц128 мODE --------- лABEL аDDR нORMAL цONTENTS мODIFIED цONTENTS --------------- ------- ------------------------------- ------------------------ (IN BANK 0) рOMиря_жEC: б0$ьььь JMP тRAPром 4ц ьь ьь JMP хANDLEиря 4ц ьь ьь - AS IT STANDS, THIS LOCATION WILL CAUSE A трап WHENEVER AN иря HAPPENS AND THE кERNAL ром IS MAPPED INTO HIGH MEMORY. мODIFY THIS LOCATION IN BANK 0 рам IF YOU WANT EXECUTION TO CONTINUE TO THE тOиNTсVC VECTOR WHEN ром IS MAPPED INTO HIGH MEMORY. тHE тOиNTсVC VECTOR CAN THEN DIRECT EXECUTION TO YOUR иср. (IN BANK 0) тOиNTсVC: б0$ьььь JMP гEOSиср 4ц XX XX JMP ыOUR_иср 4ц лл хх -OR- JMP тRAPиря 4ц ьь ьь - AS IT STANDS, THIS LOCATION DIRECTS EXECUTION TO THE геос иср WHEN AN INTERRUPT OCCURS анд BANK 0 IS VISIBLE IN THE $0300 AREA. ыOU CAN MODIFY THIS VECTOR TO POINT TO YOUR OWN иср, OR FORCE A трап WHEN SUCH AN иря OCCURS. нOTE THAT IF рOMиря_жEC POINTS TO хANDLEиря, THEN THIS BANK 0 тOиNTсVC VECTOR WILL ADDITIONALLY HANDLE иря INTERRUPTS WHICH OCCUR WHEN ром IS MAPPED INTO HIGH MEMORY. (IN BANK 1) тOиNTсVC: б1$ьььь JMP гEOSиср 4ц XX XX JMP ыOUR_иср 4ц лл хх -OR- JMP тRAPиря 4ц ьь ьь - AS IT STANDS, THIS LOCATION DIRECTS EXECUTION TO THE геос иср WHEN AN INTERRUPT OCCURS анд BANK 1 IS VISIBLE IN THE $0300 AREA. ыOU CAN MODIFY THIS VECTOR TO POINT TO YOUR OWN иср, OR FORCE A трап WHEN SUCH AN иря OCCURS. нми (рESTORE KEY) иNTERRUPTS вHEN гEOдEBUGGER IS EXECUTING USER CODE, WE SET UP THE нми VECTORS SO THAT THE ресторе KEY CAN STOP EXECUTION AT ANY POINT AND BRING US INTO THE MONITOR. нOTE THAT THIS INVOLVES THREE нми VECTORS: б1$фффа, б0$фффа, AND б0$318 FOR нмиS WHICH OCCUR WHEN ром IS MAPPED INTO THE $FFFA AREA. вHEN THE MONITOR IS RUNNING, WE SET UP THE CURRENT BANK'S $фффа нми VECTOR SO THAT THE USER CAN HIT THE ресторе KEY TO QUIT ANY OPERATION. тHIS IS IMPLEMENTED AS "SET-FLAG AND POLL-FLAG-AND-STOP WHEN YOU CAN" SO THAT CRUCIAL OPERATIONS (SUCH AS INSERTING A SYMBOL) ARE NOT INTERRUPTED. тO SIMPLIFY MATTERS, WE DISABLE нми INTERRUPTS DURING CONTEXT SWITCHING (STARTING OR STOPPING AN APPLICATION). тHIS IS ACCOMPLISHED BY MODIFYING THE WEDGE CODE SLIGHTLY SO THAT IF AN нми OCCURS WHEN WE DON'T WANT IT TO, THE WEDGE CODE IMMEDIATELY RETURNS. иN BOTH ц64 AND ц128 MODES, THERE IS ONLY ONE LOCATION IN THE WEDGE CODE WHICH MUST BE MODIFIED. (тHIS IS TRUE ON THE 128 BECAUSE NO MATTER WHICH ENTRY POINT IS USED TO GET INTO THE WEDGE CODE: рAMнми_б0, рAMнми_б1, OR рOMнми_б0, EXECUTION ENDS UP AT THE POINT LABELED сKIPтOрETURN IN THE WEDGE CODE IN BANK 1. тHEREFORE WE ONLY NEED TO ALTER THE WEDGE CODE AT THAT POINT, AND NOT IN BOTH BANKS.) нOTES: 1) ж1.0 гEOдEBUGGER USED TO DISABLE нми INTERRUPTS DURING CALLS TO геос INTERRUPT CODE. тHE MOTIVATION FOR THIS IS THE IDEA THAT WHEN THE USER HITS THE ресторе KEY, HE DOES NOT WANT TO STOP EXECUTION IN THE MIDDLE OF геос INTERRUPT CODE. ж2.0 гEOдEBUGGER DOES NOT DO THIS ANYMORE BECAUSE WE DO NOT WANT TO LOCK-OUT THE ресторе KEY WHILE THE USER'S INTERRUPT SERVICE ROUTINE IS RUNNING. аND BESIDES, WHAT IS THE STOPMAIN COMMAND FOR ANYWAY? 2) CONCERNING нми BOUNCE: - WHEN THE ресторе KEY IS PRESSED, TWO нми SIGNALS AREA GENERATED, ABOUT 150USEC APART. 3) цONCERNING PREVENTING нмиS WHICH IMMEDIATELY FOLLOW A брк INSTRUCTION: - WE HANDLE THIS CORRECTLY 4) оN BOTH THE 64 AND 128, THE циа2 CHIP HAS THE CAPABILITY OF GENERATING AN нми SIGNAL. тO PREVENT THIS FROM OCCURING DURING DISK-ACCESS ROUTINES, THE геос иNITфORио ROUTINE FORCES THE циа2 TO GENERATE ONE INTERRUPT BY SETTING THE TIMER VALUE TO A LOW NUMBER LIKE 1. иNITфORио KNOWS THAT IT WILL GET CONTROL WHEN THIS FORCED-нми OCCURS BECAUSE IT SWAPS THE KERNAL ром INTO THE HIGH- MEMORY AREA AND SETS THE KERNAL'S PAGE 3 нми VECTOR (NMIVEC, $0318) TO POINT TO A DUMMY нми ROUTINE. - ON THE ц64, THIS WORKS FINE, EXCEPT FOR THE FACT THAT гEOдEBUGGER'S VECTOR AT $0318 GETS TRASHED BY иNITфORио. - ON THE ц128, иNITфORио DOES NOT SWAP ром IN CORRECTLY (IT IS CHANGING LOCATION $0001). сO WHEN IT FORCES THIS нми TO OCCUR, THE 6510 USES THE VECTOR AT б1$фффа OR б0$фффа, AND WE END UP IN THE DEBUGGER. тO SOLVE THIS PARTICULAR PROBLEM, и HAVE ADDED CODE TO ж2.0 TO POLL THE циа2 CHIP AFTER AN нми OCCURS TO SEE IF IT WAS THE ресторе KEY OR THE циа2 CHIP. иF IT WAS THE циа2 CHIP, гEOдEBUGGER QUICKLY RETURNS TO THE APPLICATION. хANDLING нмиS FROM THE циа CHIP IN THIS MANNER IS A GOOD IDEA IN GENERAL, ON BOTH THE ц64 AND THE ц128. иT ALLOWS THE USER TO WRITE PROGRAMS WHICH USE THE циа2'S нми CAPABILITY WITHOUT WORRYING ABOUT THE DEBUGGER GETTING CONFUSED. бUT NOTE THAT THE USER'S APPLICATION WILL NOT RUN AS EXPECTED: ANYTIME THE циа2 GENERATES AN нми, THE DEBUGGER WILL GET CONTROL, POLL THE циа2 TO SEE THAT IT IS RESPONSIBLE, AND WILL RETURN TO THE APPLICATION. тHE APPLICATION WILL HAVE NO WAY OF KNOWING THAT AN нми OCCURRED, SINCE NOT ONLY DID WE STEAL THE нми INTERRUPT, WE ALSO CLEARED THE циа2 INTERRUPT STATUS REGISTER JUST BY POLLING IT. тHAT'S LIFE IN THE BIG CITY! ;************************************************************************* ; дOрBOOT ; ; тHIS COMMAND DOES WHAT THE "рбоот" ICE MACRO DOES: IT PULLS THE ENTIRE ; геос KERNAL IN FROM реу BANK #0. ; ; тALKED TO дOUG 6/6/88: ; иF THE CURRENT DRIVE IS A рам диск WHEN THIS COMMAND IS INVOKED, ; THE DESKтOP WILL COME UP OK. тHE DRIVE WHICH IS SELECTED WILL DEPEND ; UPON A COPY OF CURдRIVE WHICH IS STORED IN THE реу. (ыOU CAN CHANGE ; THIS COPY USING сELECTпRINTER FROM THE DESKтOP.) ; ; иF THE CURRENT DRIVE IS NOT A рам диск WHEN THIS COMMAND IS INVOKED, ; THEN THE DESKтOP WILL NOT COME BACK UNTIL THE PHYSICAL DRIVE IS ; TURNED OFF AND BACK ON AGAIN. ; ; тHE ONLY WAY TO IMPROVE THIS WOULD BE FOR THE DEBUGGER TO CALL ; еXITтURBO TO LET GO OF THE PHYSICAL DRIVE. бUT SINCE WE ARE NOT ; SURE THE еXITтURBO CODE IS STILL IN MEMORY, THAT IS A BAD IDEA. ; вE CAN'T CLOSE THE еXITтURBO CODE, BECAUSE IT IS DIFFERENT FOR ; EVERY DIFFERENT DISK TYPE. ; вE MAINTAIN TWO SEPARATE MEMORY POINTERS: пц (ACTUAL PROGRAM COUNTER), AND лц (ADDRESS FOR OPEN COMMANDS). еACH POINTER INCLUDES ADDRESS AND MEMORY ENVIRONMENT INFORMATION. нEW COMMANDS: супер мини USAGE --------------- --------------- ----------------------------------------------- INITVIEW -- COPY пц ADDR AND BANK INFO TO лц SETVIEW SV SET лц'S BANK INFO VIEW VW DISPLAY CURRENT пц AND лц ADDRESS AND BANK INFO USEVIEW UV CHANGE пц'S BANK INFO TO WHAT IS IN лц B1 B1 SAME AS VIEW ($7е,$00) B0 B0 SAME AS VIEW ($3е,$00) --------------- --------------- ----------------------------------------------- SETVIEW, VIEW, AND USEVIEW ARE PRIMITIVES POSSIBLE USAGES: VIEWING OTHER BANKS AND PROCEEDING FROM OLD пц AND BANK: ADDRESS BANK INFO --------------- ------------------- A ADDRESS лц = ADDRESS SETVIEW XX,XX лцB = NEW BANK INFO A ADDRESS, ETC... лц = ANYTHING лцB = ANYTHING GO USES пц ADDRESS AND BANK INFO SETTING A NEW пц AND BANK: ADDRESS BANK INFO --------------- ------------------- VIEW XX,XX лцB = NEW BANK INFO PC ADDRESS пц = NEW ADDR пцB = лцB - OR - PC ADDRESS пц = NEW ADDR VIEW XX,XX лцB = NEW BANK INFO USEVIEW пцB = лцB CHANGING пц'S BANK INFO WITHOUT CHANGING пц ADDRESS ADDRESS BANK INFO --------------- ------------------- VIEW XX,XX лцB = NEW BANK INFO USEVIEW пцB = лцB CHANGING пц ADDRESS WITHOUT CHANGING BANK INFO: ADDRESS BANK INFO --------------- ------------------- PC лц = пц лцB = пц (ONLY REQUIRED IF HAVE CHANGED лц SINCE ресторе KEY) PC NEW ADDRESS пц = NEW пцB = лц пOSSIBILITY FOR FUTURE жиев COMMAND: WHEN INVOKED WITHOUT ARGUMENTS, DIPLAYS: - сплит инто пц анд лц цолумнс - аDDRESS рANGE рAM бANK жISIBLE оVERRIDE ------------- ---------------- -------- $фц00 - $фффф 1 ром $ф800 - $фбфф 1 ром $ф000 - $ф7фф 1 ром $е000 - $еффф 1 ром $д000 - $дффф 1 и/о $ц000 - $цффф 1 $б000 - $бффф 1 $а000 - $аффф 1 $9000 - $9ффф 1 $8000 - $8ффф 1 $7000 - $7ффф 1 $6000 - $6ффф 1 $5000 - $5ффф 1 $4000 - $4ффф 1 $3000 - $3ффф 1 $2000 - $2ффф 1 $1000 - $1ффф 1 $0800 - $0ффф 1 $0400 - $07фф 0 $0000 - $03фф 0 USE PRINT HEX WORD ROUTINE, ADDING $0FFF TO GET RIGHT SIDE START INCREMENT AT $0400, OFFSET AT $03фф ONCE GET TO $1000, INC = $1000, OFFSET = $0ффф хOW гEOдEBUGGER MANAGES MACHINE-DEPENDENT MEMORY-MAP ENVIRONMENT INFORMATION тHE DEBUGGER CARRIES MEMORY-MAP ENVIRONMENT INFORMATION, WHICH IS MACHINE- DEPENDENT, AROUND IN GENERIC VARIABLES SUCH AS APPбANKиNFO1 AND APPбANKиNFO2. тHIS WAY, THE ROUTINES WHICH JUST MOVE THIS INFORMATION AROUND (BUT DON'T DIRECTLY USE IT) ARE MACHINE-INDEPENDENT. еXECUTION еNVIRONMENT: вHEN THE DEBUGGER STOPS EXECUTION OF AN APPLICATION (ресторе PRESSED OR сбп HIT), THE USER'S "EXECUTION ENVIRONMENT" IS SAVED. тHIS INCLUDES: PROCESSOR REGISTER AND FLAG VALUES пц ADDRESS CURRENT BANK INFORMATION ZERO PAGE VARIABLES STACK INFORMATION вE CALL THE пц ADDRESS AND ITS MEMORY-MAP INFORMATION THE "еXECUTION еNVIRONMENT" OR MORE SIMPLY, THE "пц POINTER". жIEWING еNVIRONMENT: оNCE THE DEBUGGER HAS STOPPED AN APPLICATION, THE "VIEWING ENVIRONMENT" IS THE SAME AS THE "EXECUTION ENVIRONMENT". тHIS MEANS THAT ALL OF THE MEMORY EXAMINATION AND MODIFICATION COMMANDS USE THE SAME MEMORY-MAP INFORMATION AS THE еXECUTION еNVIRONMENT. тHROUGH USE OF THE сетжиев COMMAND, THE VIEWING ENVIRONMENT CAN BE CHANGED. ыOU CAN SET UP A NEW MEMORY-MAP CONFIGURATION, AND THEN USE THE MEMORY EXAMINATION AND MODIFICATION COMMANDS TO READ/WRITE MEMORY IN THIS NEW CONFIGURATION. вHEN YOU GIVE THE го COMMAND TO RESUME EXECUTION, THE DEBUGGER RESTORES THE EXECUTION ENVIROMENT, AND YOUR PROGRAM CONTINUES EXECUTION. вE CALL THE VIEWING ADDRESS AND ITS ENVIRONMENT THE "лц POINTER". ------------------------------------------------------------------------------- аSPECTS OF гEOдEBUGGER WHICH MUST CHANGE ACCORDING TO MACHINE-DEPENDENCIES IN ж2.0, TO REMAIN COMPATIBLE WITH ж1.0. (кILL THESE IN ж3.0.) рEGISTER COMMAND: DISPLAYS пц ADDRESS, HIGHLIGHTS ADDRESS IF EFFECTIVE ADDRESS OF пц (CONSIDERING пц BANK INFO) IS BANK 0. DISPLAYS цпу_дата VALUE (иT REALLY SHOULD NOT DO THIS ANYMORE, BUT и AM TRYING TO MAINTAIN COMPATABILITY WITH ж1. 64: READ DIRECTLY FROM APPбANKиNFO1 128: [7-3,0]: DIRECT READ FROM MEMORY [21]: SHADOW WITH APPцпу_б21 рEGISTER оPEN цOMMAND: ..INCLUDES мм REGISTER: IS цпу_дата. (тO BE COMPATIBLE WITH ж1) 64: DIRECTLY READ/WRITE TO APPбANKиNFO1 128: [7-3,0]: DIRECTLY р/в TO MEMORY [21]: SHADOW WITH APPцпу_б21 ------------------------------------------------------------------------------- аSPECTS OF гEOдEBUGGER WHICH ARE MACHINE-INDEPENDENT. мEMORY EXAMINATION AND MODIFICATION: BANK COMMAND: AFFECTS лц'S BANK INFO: CURбANKиNFO1 AND CURбANKиNFO2 OPEN MODES: USES лц'S BANK INFO HIGHLIGHTS ADDRESS IF IS IN PHYSICAL BANK 0 DUMP COMMAND: USES лц'S BANK INFO HIGHLIGHTS ADDRESS IF IS IN PHYSICAL BANK 0 MOVE/FILL/DIFF/FIND: USES лц'S BANK INFO HIGHLIGHTS ADDRESS IF IS IN PHYSICAL BANK 0 @ AND @@ OPERATORS: USES лц'S BANK INFO сINGLE AND тOP-STEP BREAKPOINTS: MAINTAIN THEIR OWN BANK INFORMATION (COPIED FROM пц BANK INFO BEFORE EXECUTION BEGUN) сOFTWARE бREAKPOINTS: MAINTAIN THEIR OWN BANK INFORMATION (COPIED FROM пц BANK INFO BEFORE EXECUTION BEGUN) пц COMMAND: WITHOUT ARGUMENT: COPY пц ADDRESS AND BANK INFO TO лц (RESTORES EXECUTION ENVIRONMENT) WITH ARGUMENT: (SAME AS SETTING пц IN OPEN MODE) SET пц ADDRESS = ARGUMENT SET пц BANK INFO = лц BANK INFO вOULD BE NICE: ж3.0: MAKE реу SUPER MONITOR HAVE OPTION TO USE 32к BACKRAM FOR SYMBOL TABLE... вOULD BE COOL IF DEBUGGER COULD CHECKSUM RAM EXPANSION TO SEE IF IS ALREADY UP THERE (SO COULD ASSEM, LINK, DEBUG, ASSEM, LINK, DEBUG REALLY QUICKLY WHEN GEOдEBUG IS ON DISK, AND NOT ON RAMDISK). вHY NOT WAIT TILL JUST AFTER INTERRUPT CODE RUNS TO DISABLE INTERRUPTS BEFORE GOING TO USER'S CODE? вOULD FLICKER A BIT LESS. вARN USER IF WHEN WE BREAK HIS сп IS SO LOW THAT MONITOR CODE WILL WRAP IT AROUND... иF нми COULD REALIZE WHAT IT INTERRUPTED AND COULD MAKE REPAIRS SO A го WOULD NOT CRASH US. иF THE TOP-STEP COMMAND COULD RECOGNIZE CALLS TO MOST OF THE геос INLINE ROUTINES AND STOP AND WARN THE USER WHAT IS ABOUT TO HAPPEN. бEGIN AND еND STRUCTURES IN MACROS. иF AND FOR MACROS COULD SKIP TO NEXT "END". мIGHT EVEN ADD COUNTER SO COULD BE SEVERAL LEVELS DEEP. цLEAN UP ENTIRE S/T/P/GO CONDITIONED/LEAP-FROGGED STRUCTURE цLEAN UP ENTIRE OPEN MODE THING цLEAN UP MOVE/DIFF/FILL/FIND аDD INTELLIGENCE TO PARSE MACRO SO THAT IF ARGS ARE THERE BUT NOT EXPECTED, GENERATES ERROR. ALLOW MACRO DEFS WHICH ARE BIGGER THAN SIZE OF INPUT BUFFER? (ESPECIALLY WHEN LOADING FROM FILE.)