Jump to content

tschak909

Members
  • Posts

    6,891
  • Joined

  • Last visited

  • Days Won

    6

tschak909 last won the day on December 1 2022

tschak909 had the most liked content!

About tschak909

  • Birthday 10/24/1978

Contact / Social Media

Profile Information

  • Location
    USA
  • Interests
    IRATA.ONLINE system operator. Software Development, I also have extensive production experience on various artistic media. Also roast my own coffee.

Recent Profile Visitors

34,045 profile views

tschak909's Achievements

Quadrunner

Quadrunner (9/9)

7.6k

Reputation

  1. I thought I would ask around, before digging in to make one, I need a cartridge PCB that can accept an EEPROM (e.g. a 28C64, or 27C64 EPROM), for doing bootstrap development on FujiNet. Has anyone made one yet? If not, no big deal, I have the schematics and the pinouts. -Thom
  2. If you pay attention to the video, it is pointing directly to it. https://fujinetwifi.github.io/ACTION-NIO/NIO.ACT as a N: URL: N:https://fujinetwifi.github.io/ACTION-NIO/NIO.ACT -Thom
  3. With #FujiNet on your #Atari8bit. Using the N: device, you can include code and libraries directly from GitHub, directly in your programs. Shown here is a compile and run example MASTODON client that's part of the upcoming user's manual, but fetching NIO from N: #retrocomputing
  4. Yes! https://github.com/FujiNetWIFI/fujinet-firmware/issues -Thom
  5. Can you print the tnfsd version that comes up when you start it? -Thom
  6. Can you paste output from the flasher's debug monitor, as the error happens?
  7. Is there a significant delay before it states that it can't open the directory? It can possibly be a firewall on your Mac preventing connection to the tnfs server.
  8. You're asking for an info-dump, so I'll start slow. All the info needed is in the wiki, if you dig. Firmware Bring-up instructions are here: https://github.com/FujiNetWIFI/fujinet-firmware/wiki/pio-6-x-howto In a very basic sense: Applications set up a DCB pointing to the device they want to deal with, call SIOV, repeat. The commands implemented by the Atari target: FujiNet device (control, setup): https://github.com/FujiNetWIFI/fujinet-firmware/wiki/SIO-Commands-for-Device-ID-%2470 Network Device: https://github.com/FujiNetWIFI/fujinet-firmware/wiki/SIO-Commands-for-Device-IDs-%2471-to-%2478 The Firmware is set up in three main sections: lib/ bus/ device/ media/ bus/ implements all the required bus arbitration bits. device/ implement all the various sub-devices media/ implements the media types used by the disk device. And yes, the fact that you're trying to implement a parallel implementation on an existing platform, without experiencing the existing solution is a bit silly. -Thom
  9. Because the platform itself is built around a stable microcontroller, while there will be hardware changes (e.g. changing from micro-USB to USB-C), the firmware will always be in development, as new features are added. -Thom
  10. We don't build them ourselves, but work with vendors to ensure they can build and make them available, a list of them are here: https://fujinet.online/purchase/ (if your favorite vendor is out, ask them to make more) As for the Astrocade, unless I am missing something, the whole processor bus is available at the expansion slot, no? -Thom
  11. Yes. One is being developed for the Atari 2600, that is extending PlusCart. On the Astrocade, you have a full system bus via the expansion slot. -Thom
  12. Thanks, any images at the moment, are placeholders, which will be re-drawn to match. (especially because as is, the images are far too dark to print well) -Thom
  13. Would anyone be interested in starting a bring-up of FujiNet to the Astrocade? It could potentially work using the RP2040 as a front-end to the ESP32 running the network stack, and connecting via the expansion port. -Thom
  14. Hello all. I've finally started on a User's Guide for the ATARI FujiNet. It's being written in DocBook, which is a standard for publishing technical books, articles, etc. Its big advantages are that it separates content from style, but it also has a good deal of tags to provide semantic context (such as marking up commands, screen shots, call-outs, etc.) The current style-sheet is being based on the type setting used by Atari for its more technical software products, such as "Telelink I" and "Music Composer" where the Optima font face is used as the primary font, and the highlight color is a light blue. The documentation, like everything else in FujiNet is being developed publicly, and is available in GitHub: https://github.com/FujiNetWIFI/fujinet-manuals in the fujinet_for_atari_users folder. The main DocBook file is: https://github.com/FujiNetWIFI/fujinet-manuals/blob/main/fujinet_for_atari_users/fujinet_for_atari_users.dbk I am using a combination of emacs, and XMLMind DocBook Editor to compose the material: http://www.xmlmind.com/xmleditor/docbook_editor.html While there is preliminary styling in place, this isn't being actively changed at the moment, as content floods in. Once content is stable, we can start thinking about refining the style sheets, not just for PDF, but for HTML and EPUB as well. I will periodically attach a render of content, as a PDF, as we go along. Any and all help would be appreciated, as this is a very important undertaking. Some snips of pages: I also recorded a video showing the process, here: -Thom fujinet_for_atari_users.pdf
  15. Awesome! No, none of the Atari printers do ATASCII, this is why we made the ATASCII printers. -Thom
×
×
  • Create New...