Jump to content
IGNORED

TIPI Usage and Support


jedimatt42

Recommended Posts

As reported in the development thread, I've updated the TIPI software so that PI.CLOCK reads like a Corcomp clock...

 

https://github.com/jedimatt42/tipi/wiki/PI.CLOCK

 

I've also fixed a bug Stuart reported, when using the web-ui. It was allowing caching of TIFILES that you download, which prevents getting your latest version :( This has been fixed in a small update tonight. :)

 

-M@

  • Like 6
Link to comment
Share on other sites

For those with CorComp real time clocks and a TIPI's installed, the program below should take the TIPI time from the Internet and save it to your CorComp card without the hassle of typing anything...

 

** REMOVED **
....of course this would be even better compiled into an E/A5 program we could run out of 4A/DOS or even made into a BIN file for the FR/FG99.
Edited by --- Ω ---
Link to comment
Share on other sites

I attached USB drive holding a handful of ti files, but it apparently does not auto mount.

I am used to linux's auto mounting my USB drives.

When i do a lsusb from the command prompt, it does show up.

But i have no idea how to mount it. Even better, i would like this drive auto mounted when i start the pi, to access my library of ti files on it.

Any help?

Link to comment
Share on other sites

Auto mount is usually a function of whatever linux desktop suite you are running... TIPI's linux - raspbian, is raspbian-lite with no desktop ( I think... ) I've never attached an hdmi display.

 

https://elinux.org/RPi_Adding_USB_Drives

 

Not sure if it solves the problem... I find it easier to mount the smb://tipi/tipi share on my laptop, and just push files... or use http://tipi:9900, and upload them... or use scp...

 

 

TI files are so small... it takes more time to plugin and then unmount drives than to network mount...

 

ElectricLab had some procedure in place for automounting usb drives on the PI in the early development phase...

 

-M@

Link to comment
Share on other sites

Oh, and if you want it to be the drive all your TIFILES are served from a.k.a.: "TIPI." then mount it at /home/tipi/tipi_disk

 

There are some files in tipi_disk already, you may want to copy them over first, as a mount will hide the real tipi_disk folder.

 

-M@

Link to comment
Share on other sites

Interesting...

 

In some way's it would be nice to have all my TI programs and files on an easy to access USB stick, leaving the SD card strictly for TIPI related operations giving it fewer re-write cycles and prolonging it's operational life. Swapping USB sticks could also give a different 'personality' to different sticks/setups and would be easy to transport between multiple TIPI units.

 

The USB ports are easy to access on my sidecar unit, but not so much on the P-Box version. The question I have is what kind of USB extension to go with? Any extension must be functional, good looking and mountable. If I did not already have stuff in my disk drive area I'd get one one these...

 

sml_gallery_35324_1027_123394.jpg

 

... but I'll have to look for something more like this...

sml_gallery_35324_1027_40503.jpg

What would make a nice upgrade for the TIPI is if there was an option to toggle such a feature on and off. The end user could easily decide what configuration to run by calling up the TIPI program and checking a box.

Link to comment
Share on other sites

I've pushed a small functional change to allow PI.CLOCK to be opened with an explicit record length of 24, to get the old python time.asctime() formatted string you had before I made it default to the Corcomp style.

 

I have also pushed the code to a 'release' branch instead of what has been called 'unstable' for all this time.

 

After update completes, to 1.0betav036, press space, then R to reload status. You should see another update to 1.37 (no more ugly beta string). U to update again, and all should be caught up.

 

Link to history for this new branch is here:

 

https://github.com/jedimatt42/tipi/commits/release

 

-M@

  • Like 3
Link to comment
Share on other sites

Someone was asking in the arcadeshopper new stuff thread, about the status of Geneve compatibility.

 

A modification was found to the CPLD code on the board that needs to be flashed... A method of flashing that from the raspberry PI has been outlined... requires carefully wiring 5 additional lines temporarily from the JEDEC port on TIPI to the GPIO on the PI.

 

This modification fixes a timing issue with the Geneve. It should not be necessary for any 4A users, however it has been tested against the 4A and also works fine there.

 

Instructions are on the tipi wiki... see: CPLD-Programming-With-PI - https://github.com/jedimatt42/tipi/wiki/CPLD-Programming-With-PI

 

I'm cross posting here, cause the original inquiry was off in a random thread, implying that, I forget who, probably doesn't read the development threads...

 

Anyway, TIPI is supported on Geneve in ROMPAGE mode now.

 

This has been tested only by myself so far... There are no confirmations from any other users.

 

-M@

  • Like 3
Link to comment
Share on other sites

  • 3 weeks later...

Does anyone use the WDS1 mode of TIPI?

 

I would like to remove it to clean up noise.

 

It does not solve the problems I was hoping to solve with it. I have solved them in TIPIFM, client software instead.

 

-M@

 

 

This is not something I am using now.

 

If your TIPFM client will allow one to copy files from a TIPI to a WDS1 device while using Rompage mode under the GPL interpreter on the Geneve, then that is all I personally need. I just need a way to get files onto a hard disk accessible on a Geneve as I do all my assembly work under a MDOS environement using GenASM and 80 column editors.

 

Beery

Link to comment
Share on other sites

I added some WDS support to TIMXT but it is messy. I don't want to maintain it, sounds like a good cleanup step.

 

What would be helpful (in my opinion) would be a TIP1 or TIP0 device name. Most file-based IO devices hold the unit number in position 4 of the device name, making it easy to parse for level 2. Given the challenges with level 2 this may be a moot point. Just putting it out there since you are doing some cleanup.

Link to comment
Share on other sites

I added some WDS support to TIMXT but it is messy. I don't want to maintain it, sounds like a good cleanup step.

 

What would be helpful (in my opinion) would be a TIP1 or TIP0 device name. Most file-based IO devices hold the unit number in position 4 of the device name, making it easy to parse for level 2. Given the challenges with level 2 this may be a moot point. Just putting it out there since you are doing some cleanup.

 

remember there's DSK4. which is basically TIPI with that support, unfort on my corcomp disk controller machine it conflicts

Link to comment
Share on other sites

I added some WDS support to TIMXT but it is messy. I don't want to maintain it, sounds like a good cleanup step.

 

What would be helpful (in my opinion) would be a TIP1 or TIP0 device name. Most file-based IO devices hold the unit number in position 4 of the device name, making it easy to parse for level 2. Given the challenges with level 2 this may be a moot point. Just putting it out there since you are doing some cleanup.

"DSK0." is same as "TIPI." Instruct your users to use that if you don't want to special case "TIPI."

 

-M@

Link to comment
Share on other sites

This is not something I am using now.

 

If your TIPIFM client will allow one to copy files from a TIPI to a WDS1 device while using Rompage mode under the GPL interpreter on the Geneve, then that is all I personally need. I just need a way to get files onto a hard disk accessible on a Geneve as I do all my assembly work under a MDOS environement using GenASM and 80 column editors.

 

Beery

Beery, you'll have to answer that question for us!

 

Nobody else has a TIPI and a whatever Geneve compatible hard drive you have in a Geneve system to my knowledge.

TIPIFM tries to support scsi, ide, wds, dsk, and tipi.

 

It uses a modified DSRLNK that doesn't search crubases, but instead gathers this information up front and allows you to copy from 1000.DSK1. to 1100.DSK1. or vise versa just fine.

For exploration, there is a DRIVES command that lists the things it thinks are drives, grouped by their crubase.

There is also a LVL2 command that will show what single character named basic subroutines are in the ROM's subroutine list... they are shown in hex, such as >14

 

I don't recall if anyone but Greg has tried to use TIPIFM even in their 4A. I last posted it here: http://atariage.com/forums/topic/265136-tipi-ti-994a-to-raspberry-pi-interface-development/?p=4227235

 

80 column mode won't work on the Geneve, it uses F18A accelerated scrolling.

 

If I was in your shoes, I'd write an FTP client, or 'wget' for MDOS...

 

The successor to TIPIFM will be titled 'Force Commander' and is a Grom + ROM cartridge that is too big for the Geneve.

 

-M@

  • Like 3
Link to comment
Share on other sites

Beery, you'll have to answer that question for us!

 

Nobody else has a TIPI and a whatever Geneve compatible hard drive you have in a Geneve system to my knowledge.

TIPIFM tries to support scsi, ide, wds, dsk, and tipi.

 

It uses a modified DSRLNK that doesn't search crubases, but instead gathers this information up front and allows you to copy from 1000.DSK1. to 1100.DSK1. or vise versa just fine.

For exploration, there is a DRIVES command that lists the things it thinks are drives, grouped by their crubase.

There is also a LVL2 command that will show what single character named basic subroutines are in the ROM's subroutine list... they are shown in hex, such as >14

 

I don't recall if anyone but Greg has tried to use TIPIFM even in their 4A. I last posted it here: http://atariage.com/forums/topic/265136-tipi-ti-994a-to-raspberry-pi-interface-development/?p=4227235

 

80 column mode won't work on the Geneve, it uses F18A accelerated scrolling.

 

If I was in your shoes, I'd write an FTP client, or 'wget' for MDOS...

 

The successor to TIPIFM will be titled 'Force Commander' and is a Grom + ROM cartridge that is too big for the Geneve.

 

-M@

 

Well, I will say I did indeed try the program back when you posted on a TI-99/4A. I had trouble with the program, but that was also about the time I had an issue with the HFDC on the TI-99/4A so my issues may be unrelated to the use of the program.

 

As far as "Force Commander", how large of a program are you anticipating? Just a FYI, the Geneve's "TI-Basic" memory space can be used and that would give you an extra 12 to 16K of grom space if you need that room. And then you have all that extra space to whatever Extended Basic would use. If it is something that would only work in a FinalGrom because you are paging in other extra memory, then yeah, it will not work on the Geneve. If it is something that can run in a Pgram or GramKracker, it should be runnable on the Geneve as well.

 

If using the TI-Basic grom space would allow it to run on the Geneve with the other memory space, then there is just a "tad" more effort in the layout of the files. The TI-Basic grom code would need to replace a couple of the GPL interpreter files, and then the remainder of the program would be the "module". That's the simplest route, or modify the GPL interpreter source code to be "Force Commander" and let it tuck all the pieces into the right memory banks on its own. Again, all depends upon how big your program is, etc.

 

Beery

Link to comment
Share on other sites

"DSK0." is same as "TIPI." Instruct your users to use that if you don't want to special case "TIPI."

 

-M@

OK, though I'm not clear on how using DSK0. is any better for level 2 IO when accessing files within folders. For now I'll just work around this special case as I've done in some of my test code. It's just something I'm playing around with for my own use; no users to instruct here. :)

  • Like 1
Link to comment
Share on other sites

Heaven forbid - - I have no issues with folders on any device, DSK or otherwise. It's getting to those files with level 2 IO that is currently a challenge, regardless of device name thanks to unit numbers and subroutines and current paths versus using a fully qualified filename.

 

Edit: removed other suggestions as they are not really support-related..

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...