Willsy Posted October 31, 2013 Share Posted October 31, 2013 I can't remember if I posted here or not. TurboForth V1.2 is now released. Have a look here for list of changes/improvements (there's a lot). Bob Carmany will be at the Faire with V1.2 Eproms if anyone wants it. It's also available for download from the TurboForth website. Tursi is also going to include it in releases of Classic99 (make sure you distribute the matching blocks disk, Tursi! - see web site). If anyone wants a TF V1.2 cartridge please get in touch. Last time I put them on eBay, but I don't know if I'll bother this time. Mark 4 Quote Link to comment Share on other sites More sharing options...
OX. Posted October 31, 2013 Share Posted October 31, 2013 Nice one, thanks Willsy. Quote Link to comment Share on other sites More sharing options...
Tursi Posted October 31, 2013 Share Posted October 31, 2013 Bob Carmany will be at the Faire with V1.2 Eproms if anyone wants it. It's also available for download from the TurboForth website. Tursi is also going to include it in releases of Classic99 (make sure you distribute the matching blocks disk, Tursi! - see web site). It has been in there for the last two releases, Mark! 2 Quote Link to comment Share on other sites More sharing options...
+OLD CS1 Posted October 31, 2013 Share Posted October 31, 2013 Cool! I wish I had brought my TF cart with me. I will get my EPROM Saturday! Quote Link to comment Share on other sites More sharing options...
Willsy Posted October 31, 2013 Author Share Posted October 31, 2013 Nice one Tursi! Quote Link to comment Share on other sites More sharing options...
Opry99er Posted November 22, 2013 Share Posted November 22, 2013 Congrats, Willsy... You're truly a brilliant programmer and an essential piece of the TI puzzle. And props to Tursi for including TF in Classic99. =) For guys like me with hardware problems. Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted January 7, 2014 Share Posted January 7, 2014 (edited) Ok I burned this to a eeprom and load it fine on my 4/a with corcomp fdc etc.. but on the nanopeb it sticks at the copyright and never says anything about the blocks file.. me problem? Tried both my v2 (com1) and v3 (rs232) versions.. f18a v1.5 Greg Edited January 7, 2014 by arcadeshopper Quote Link to comment Share on other sites More sharing options...
Willsy Posted January 7, 2014 Author Share Posted January 7, 2014 Thanks for the bug report. Looks like the nano DSR is doing something different/un-anticipated. It certainly worked on the first edition CF7. Bummer. Is there a DSK1 volume set up on your nano? It looks for DSK1 (by default). If you don't press any key while TF starts, it looks for DSK1.BLOCKS, however, if you press and hold a key immediately after selecting TF from the cart menu, it uses that key as the drive number/letter. So, if you press and hold A it looks for DSKA.BLOCKS. If you press and hold 9 it looks for DSK9.BLOCKS etc. If you press and hold ENTER then TF does not look for a file at all, and will simply give you the flashing cursor. This is useful if your system uses something different to DSK. For example, HDX. If you were using a HDX system, you would start TF up by holding ENTER, and then type the following: S" HDX1.BLOCKS" USE Note the space after the first quote character. That would tell TF to use the file BLOCKS on HDX1. You could then do: 1 LOAD To boot the blocks file. Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted January 7, 2014 Share Posted January 7, 2014 (edited) Thanks for the bug report. Looks like the nano DSR is doing something different/un-anticipated. It certainly worked on the first edition CF7. Bummer. Is there a DSK1 volume set up on your nano? It looks for DSK1 (by default). If you don't press any key while TF starts, it looks for DSK1.BLOCKS, however, if you press and hold a key immediately after selecting TF from the cart menu, it uses that key as the drive number/letter. So, if you press and hold A it looks for DSKA.BLOCKS. If you press and hold 9 it looks for DSK9.BLOCKS etc. If you press and hold ENTER then TF does not look for a file at all, and will simply give you the flashing cursor. This is useful if your system uses something different to DSK. For example, HDX. If you were using a HDX system, you would start TF up by holding ENTER, and then type the following: S" HDX1.BLOCKS" USE Note the space after the first quote character. That would tell TF to use the file BLOCKS on HDX1. You could then do: 1 LOAD To boot the blocks file. Yeah the nanopeb is just like the cf7 where it has mounted disk1,2,3 it seems to be exactly the same. I owned all 3..but sold my cf7 a while back as the parallel port was useless.. I don't have a blocks file on a disk image yet, when it loads turbofourth I don't see any activity on the floppy light on the nanopeb.. On the pbox 4/a it goes to disk and then says that it can't find the blocks file.. On the nano i loaded "a disk" into DSK1. and still sticks at that point Greg Edited January 7, 2014 by arcadeshopper Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted January 11, 2014 Share Posted January 11, 2014 Ok if I hold space when loading it it says DSK .BLOCKS not found I copied the blocks file from your utility over to the 4/a and tried to load it as you described.. the S command says OK then it hangs on the 1 LOAD command.. Greg Yeah the nanopeb is just like the cf7 where it has mounted disk1,2,3 it seems to be exactly the same. I owned all 3..but sold my cf7 a while back as the parallel port was useless.. I don't have a blocks file on a disk image yet, when it loads turbofourth I don't see any activity on the floppy light on the nanopeb.. On the pbox 4/a it goes to disk and then says that it can't find the blocks file.. On the nano i loaded "a disk" into DSK1. and still sticks at that point Greg Quote Link to comment Share on other sites More sharing options...
Willsy Posted January 11, 2014 Author Share Posted January 11, 2014 You should be holding ENTER not space! But other than that it sounds like you are doing it correctly. Sounds like something is badly wrong somewhere. I'll probably have to buy a nano peb before I can debug it. The only thing I can think of is that the nano is using some pad memory that is also used by TF. Does anyone know if there's a published list of memory addresses used? Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted January 11, 2014 Share Posted January 11, 2014 You should be holding ENTER not space! But other than that it sounds like you are doing it correctly. Sounds like something is badly wrong somewhere. I'll probably have to buy a nano peb before I can debug it. The only thing I can think of is that the nano is using some pad memory that is also used by TF. Does anyone know if there's a published list of memory addresses used? Are you relying upon 0x8370 to determine VDP free space? I do not have a nanoPEB, but given how the creator uses 8 bytes of VDP as pointers to the mounted volumes in the earlier devices, perhaps he adjusted the used space again? Just a thought... See my short writeup regarding Funnelweb elsewhere in the forum. Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted January 12, 2014 Share Posted January 12, 2014 (edited) Are you relying upon 0x8370 to determine VDP free space? I do not have a nanoPEB, but given how the creator uses 8 bytes of VDP as pointers to the mounted volumes in the earlier devices, perhaps he adjusted the used space again? Just a thought... See my short writeup regarding Funnelweb elsewhere in the forum. ... The only thing I can think of is that the nano is using some pad memory that is also used by TF. Does anyone know if there's a published list of memory addresses used? I just put together one of the 64KB boards I got from @arcadeshopper and installed the EPROM I got from Bob Carmany with TurboForth v1.2 on it. I'm having the same problem Greg is having with my nanoPEB v1.0. If I hold down the Enter key, I can use TF but cannot USE DSK1.BLOCKS, which is properly located. I checked 8370h for high VRAM and it reported 37D7h, which is definitely wrong! As Tim said, the nanoPEB uses 8 bytes as pointers. 8370h should contain 37CFh with 3 simultaneous files allowed. If I actually store 37CFh in 8370h, I can successfully execute S" DSK1.BLOCKS" USE ; but, as soon as I execute 1 LOAD , things head south. One time I got block 1 to load—sort of. The big letters of TurboForth started moving across the screen and some of the subsequent info was displayed; but, the screen was trashed and the system froze. But, of course, I should not be messing with 8370h—except to read it. When I load fbForth with the nanoPEB v1.0, 8370h has 37CFh for 3 simultaneous files allowed. Somehow, TF v1.2 is getting it wrong when the nanoPEB is present. I'm pretty sure the nanoPEB is not using any PAD RAM not used by other DSRs. It is using those extra 8 bytes in VRAM, however. I just checked the high 8 bytes and the low 8 bytes of the relevant block of VRAM (37D0h – 3FFFh) and it looks like the nanoPEB is using the high 8 bytes, i.e., 3FF8h – 3FFFh to track which volumes are mounted as DSK1, DSK2 and DSK3. ...lee Edited January 12, 2014 by Lee Stewart Quote Link to comment Share on other sites More sharing options...
Willsy Posted January 12, 2014 Author Share Posted January 12, 2014 (edited) Thanks guys this is useful information. TF uses a lot of pad ram - it copies the executable code of some forth words to pad to allow them to run out of 0 wait state memory. I'm currently thinking that TFs and the nono's pad ram requirements are stepping on each other. See http://turboforth.net/pad_ram.html Mark Edited January 12, 2014 by Willsy Quote Link to comment Share on other sites More sharing options...
Willsy Posted January 12, 2014 Author Share Posted January 12, 2014 Though I note from the memory map on the TF site that it doesn't use >8370. It's marked as used by the OS. Mark Quote Link to comment Share on other sites More sharing options...
sometimes99er Posted January 12, 2014 Share Posted January 12, 2014 Cool ScratchPad memory layout. 1 Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted January 12, 2014 Share Posted January 12, 2014 Though I note from the memory map on the TF site that it doesn't use >8370. It's marked as used by the OS. Mark Hey Mark, I sent you a PM for review.... Quote Link to comment Share on other sites More sharing options...
Willsy Posted January 13, 2014 Author Share Posted January 13, 2014 Looks like the cause of the problem has been found. Thanks to Lee and InsaneMultitasker and in particular to InsaneMultitasker to pointing me to the line of (my own ) code that writes >37D7 to >8370. I'll produce a new build. Can I ask Greg and Lee to give it a spin? Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted January 13, 2014 Share Posted January 13, 2014 Looks like the cause of the problem has been found. Thanks to Lee and InsaneMultitasker and in particular to InsaneMultitasker to pointing me to the line of (my own ) code that writes >37D7 to >8370. I'll produce a new build. Can I ask Greg and Lee to give it a spin? Certainly!—though, if the offending code is in ROM, I'll need to get a programmer first. I plan to do that soon, anyway; but, that would delay my testing. ...lee Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted January 13, 2014 Share Posted January 13, 2014 Looks like the cause of the problem has been found. Thanks to Lee and InsaneMultitasker and in particular to InsaneMultitasker to pointing me to the line of (my own ) code that writes >37D7 to >8370. I'll produce a new build. Can I ask Greg and Lee to give it a spin? Of course! Quote Link to comment Share on other sites More sharing options...
+arcadeshopper Posted January 22, 2014 Share Posted January 22, 2014 Looks like the cause of the problem has been found. Thanks to Lee and InsaneMultitasker and in particular to InsaneMultitasker to pointing me to the line of (my own ) code that writes >37D7 to >8370. I'll produce a new build. Can I ask Greg and Lee to give it a spin? Any eta on a new build? And I can burn a rom for the other tester if needed. Greg Quote Link to comment Share on other sites More sharing options...
Willsy Posted January 22, 2014 Author Share Posted January 22, 2014 I have done a build but for some reason it won't run on an EVPC equipped TI, and we're not sure why. I've tried it in MESS with an EVPC card, and it works in 40 column mode just fine, but in 80 column mode it crashes. I will begin investigating using MESS (never done that before) tomorrow to see if I can narrow the issue down. I'm fairly sure that it's PAD RAM usage (TF uses a lot of scratch pad, it moves common Forth words like DUP SWAP etc to pad on start-up, so they run twice as fast as they would from cart ROM). Does anyone have a link the nanoPEB site? Specifically, I'm looking for the DSR code in the hope that I can determine its PAD RAM requirements. Thanks Mark Quote Link to comment Share on other sites More sharing options...
+Lee Stewart Posted January 23, 2014 Share Posted January 23, 2014 ... Does anyone have a link the nanoPEB site? Specifically, I'm looking for the DSR code in the hope that I can determine its PAD RAM requirements. http://webpages.charter.net/nanopeb/ ...lee Quote Link to comment Share on other sites More sharing options...
+InsaneMultitasker Posted January 25, 2014 Share Posted January 25, 2014 I have done a build but for some reason it won't run on an EVPC equipped TI, and we're not sure why. I've tried it in MESS with an EVPC card, and it works in 40 column mode just fine, but in 80 column mode it crashes. I will begin investigating using MESS (never done that before) tomorrow to see if I can narrow the issue down. I'm fairly sure that it's PAD RAM usage (TF uses a lot of scratch pad, it moves common Forth words like DUP SWAP etc to pad on start-up, so they run twice as fast as they would from cart ROM). Does anyone have a link the nanoPEB site? Specifically, I'm looking for the DSR code in the hope that I can determine its PAD RAM requirements. Thanks Mark Is the problem the EVPC card, nanoPEB, or both? I thought we found the nanoPEB problem hence my question Quote Link to comment Share on other sites More sharing options...
Willsy Posted January 25, 2014 Author Share Posted January 25, 2014 Well, for all I know, it now works fine with the nano PEB - but the changes that I introduced to the pad restore code have had some effect on the evpc card in 80 column mode only. Works perfectly in 40 column mode. (The above observations made using MESS). I'll post the binaries today for anyone that wants to burn an eprom and try out on the real hardware. I have been corresponding with the developer on the nano and he is also looking into the issue. He informs me that the pad ram requirements for the nano are the same as the TI disk controller. Well v1.2 works fine with that so it should be working with the nano. Something else is going on. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.