Search the Community
Showing results for tags 'finalgrom 99'.
Found 3 results
(Special thanks to @Omega-TI for keeping these updated) "Images for FlashROM 99 (FR99) and FinalGROM 99 (FG99)" thread Cartridge binaries compatible with each or both the FR99 and FG99 "ROM burning images" thread Cartridge and other images for burning your own cartridges and ROMs "Manuals, keyboard strips, labels, and much more" thread Scans and re-makes of various manuals, keyboard strips, etc., as well as printable 3D objects
The image I've uploaded is preloaded in Assembly Language Storage mode(>7000=>A55A) with LINE BY LINE ASSEMBLER and the LINES demonstration program on PAGE 1(use NEW,OLD,LINES from MINI MEMORY option 2 RUN), (see MINI MEMORY pamphlet page 74). Using SAVE MINIMEM from TI BASIC will force the current PAGE's (>7000 to >5AA5) TI BASIC Files mode(see MINI MEMORY pamphlet page 73). Each RAM PAGE can have it's own mode. Using the SAVE option after the TITLE SCREEN will save the current page to the SD card's image file. I believe the main difference between the two modes is that in TI BASIC Files mode, you have no REF/DEF table. I tend to use absolute addresses anyway and keep tight control over all program/data sections/pages, loading from tape or by using EMU and a HEX EDITOR on the SD cards image file, rather than by using REFs and DEFs. But once again, each PAGE can have it's own mode. One thing of note, might be, that when you LOAD, RELOCATABLE TAGGED OBJECT CODE from MINI MEMORY option 1, the loading destination is controlled by the following addresses: >701C first free address in MEDIUM MEMORY (>7000-7FFF) >701E last free address in MEDIUM MEMORY >7022 first free address in HIGH MEMORY (>A000-FFE0) >7024 last free address in HIGH MEMORY >7026 first free address in LOW MEMORY (>2000,3FFF) >7028 first free address in LOW MEMORY The single REF/DEF table goes downward from >7FFF. When the 32K memory pointers are not >0000, TAGGED OBJECT CODE will try to load in 32K, rather than MEDIUM MEMORY! So Best to ZERO these manually, So as to force code to load into MINI MEMORY. From MINI MEMORY use option 3 RE-INITIALIZE to clear/reset MEDIUM MEMORY before starting your project. Be aware that this will only RE-INITIALIZE the current PAGE! ROM pages are switched by writing to: 6000=page 1 6002=page 2 6004=page 3 RAM pages are switched by writing to: 6800=page 1 6802=page 2 6804=page 3 Page switching can be done from EASY BUG or by way of CALL LINK combined with a small assembly routine, either copied to all pages or stored in an non-paged RAM address range. So far I'm using this exclusively to run machine code, and to store data. Expecting the application(HOME AUTOMATION CONTROLLER) to grow as it is developed! But I'm certain that there are other uses as well. Alex. 256k Banked Minimem.zip
Finally got around to making a video on the FinalGROM 99. You can check it out here: The video covers the following: 1. How to use the FinalGROM 99 by Ralph Benzinger 2. How to copy the .bin files to the FG99 3. How to apply the 3D Printed case (I used a model from thingiverse) 4. Testing Stuart's Browser on the FG99 (using twoodland's .bin file - worked great thank you!) 5. Playing a small portion of many games (retro and homebrew) 6. At the end, play the full Don't Mess With Texas Demo by Rasmus, Tursi and others (really awesome job guys!) I want to thank all of the excellent TI developers (HW & SW) that keep the TI alive! Also thanks to OmegaTI for keeping the archives up-to-date and well documented.