Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1,163 Excellent

About Willsy

  • Rank
    River Patroller
  • Birthday 12/03/1970

Contact / Social Media

Profile Information

  • Gender
  • Location
    Uzbekistan (no, really!)
  • Interests
  1. Yes but you need to access vdp regularly to allow the interrupts to fire. Interrupts in TF were an after thought. Most video related commands, and things like JOYST do that for you. For example if you ran this program, interrupts wouldn't work: : test begin again ; But this would work: : test begin 0 [email protected] drop again ;
  2. Shucks, thanks guys!
  3. Just stopping in to say a quick hello to all my TI friends! I still pop by the site most days to read various threads, especially the Forth stuff, but I'm mostly in lurk mode because if I allow myself to go back down the TI/Forth/Assembler rabbit hole my university grades will suffer! I've allowed myself a very enjoyable couple of hours this evening going over old TF threads in search of some info on a question for TSR code for TF. I found a sound player written in FOrth assembler that I had completely forgotten writing. Bit rot, eh? Anyway, wanted to say hi - I'm still kind of around - and will be back once my degree is finished. Take care Mark
  4. For more info on ISR/TSR in TF, see this thread. That was a nice a nice trip down memory lane!
  5. Even I don't know how to call a Forth word (in TF) from an assembler word. I've looked at it a couple of times and it makes my hed hurt! If you guys ever fathom, could you let me now
  6. This might provide some inspiration. The Forth syntax probably won't mean very much, but overall i'm sure it'll make sense. Cheers Mark
  7. NTSC or PAL? In addition, are you guys running any fancies such as F18 etc. It's not really enough to say "it works fine on my system". When you've seen one TI system, you've seen... one TI system
  8. You're probably too far down the track now, but some of the SAMS code in TF may be help/interest. Check out http://turboforth.net/source/Bank1/1-04-Memory.html (the word >MAP i.e "to mapper") ; ; >MAP ( bank address -- ) ; If a SAMS card is present, maps memory bank "bank" to address "address" _sams mov r12,r11 ; save address of NEXT mov *stack+,r1 ; get address andi r1,>f000 ; set to 4k boundary srl r1,11 ; divide by 2048 ai r1,>4000 ; convert to SAMS register address mov *stack+,r2 ; get bank andi r2,>ff ; mask off any crap mov r2,r0 ; keep a copy sla r2,8 ; move to high byte xor r0,r2 ; combine r0 & r2. Hi & lo bytes are now identical li r12,>1e00 ; cru address of SAMS sbo 0 ; enable SAMS registers mov r2,*r1 ; poke sams register sbz 0 ; disable sams registers mov r11,r12 ; restore address of NEXT b @retB0 ; return to caller Also, the SAMS initialisation code in http://turboforth.net/source/Bank1/1-16-Initialise.html ; initialise SAMS card if fitted li r12,>1e00 ; sams CRU base sbo 0 ; enable access to mapper registers sbz 1 ; disable mapping while we set it up li r0,>4004 ; register for >2000 li r1,>f8f8 ; map bank >f8 into >2000 mov r1,*r0+ ; do it li r1,>f9f9 ; map bank >f9... mov r1,*r0+ ; ...into >3000 ; now set up the banks for high memory... li r0,>4014 ; register address li r1,>fafa ; register value li r2,6 ; loop count sams mov r1,*r0+ ; write to the register ai r1,>0101 ; next register value dec r2 ; finished? jne sams ; loop if not sbo 1 ; enable mapping sbz 0 ; lock the mapper registers
  9. The Bunyard manual will probably be the best resource. It was written by one of the TI engineers that worked on the project, if I remember correctly. I think it's available in the resources thread. Regards
  10. 9 years ago I started this and never finished it. I had too many un-answered questions about how Willy jumps.
  11. What they haven't reckoned on is this: Given the choice between coding for $15 an hour or stacking shelves, I'll stack the shelves thank you very much. I can turn up, do my shift, and go home again without dealing with all the other crap that goes with software engineering such as design documentation, myriad meetings, other people's defective code and requirements capture, and a whole host of other stressful issues!
  12. Hey Owen, is that a beige TI? My God man! What sort of parent are you? :-) Seriously though, that's a lovely story. Our 8 year-old son has learning issues so he's a long long way off from being able to do something similar. It breaks our hearts but in all other respects he's fit and healthy so we count our blessings. It could be worse. Great story man!
  • Create New...