Search the Community
Showing results for tags 'fujinet'.
-
I wrote this library for managing text windows starting in 2015 in the Action! language. The windows have different ornamental controls. I've added features I've dubbed gadgets like radio buttons, regular buttons, checkboxes, progress bars, spinners, and input controls that have type restrictions and scroll if they are larger than displayable space. The gadgets allow building forms which are very close to modern dialogs. I blogged the progress of the library over the years, and over the last couple of months converted the library to C (CC65). I blogged about the C conversion as well. I created full API documentation for both and build some sample apps in each language. The blog has some video demonstrations. Once I completed the C version, I decided to create GitHub repositories for distribution rather than my blog. Maybe someone will find them useful. The C version now includes support for FujiNet, SIO, and APE Time. FujiNet bindings include support for Base64 encode/decode and Hashing using SHA1, SHA256, and SHA512. These updates are not in the Action! library, or the Pascal library. (edit) Amarok converted the C version to Mad-Pascal. I created a corresponding API document, and published it on GitHub. Thanks Amarok! Here are the links: C blog entries: https://unfinishedbitness.info/tag/c-cc65/ C GitHub page: https://github.com/Ripjetski6502/A8CLibrary Action! blog with latest release: https://unfinishedbitness.info/2022/08/27/action-library-v1-51/ Action! blog entries: https://unfinishedbitness.info/2016/04/27/action-windows/ (first post on window library) Action! GitHub page: https://github.com/Ripjetski6502/A8ActionLibrary Mad-Pascal GitHub page: https://github.com/Ripjetski6502/A8MadPascalLibrary Enjoy.
- 30 replies
-
- 15
-
There is a new DIY through hole FujiNet hardware design that uses the espressif devkitc-ve board. It's basically a shield for the devkit board with all the needed bits for FujiNet. I'm happy to finally see someone else release hardware based on the completely open FujiNet design. https://github.com/djtersteegc/fujinet-devkit-shield
-
#FujiNet code is here in GitHub: https://github.com/FujiNetWIFI Patreon page here: https://www.patreon.com/user?u=8255002 (funds here are used to take care of operational expenses such as shipping boards back and forth.) Website Describing the Production Firmware is Here: http://fujinet.online/ What is #FujiNet? #FujiNet (formerly known at #AtariWiFi) is a network adapter that attaches to the SIO (Peripheral) port of an Atari 8-bit system. It currently (as of Rev3) consists of an NodeMCU 1.0 device attached to an interface board which electrically attaches the NodeMCU to the SIO bus and provides the needed SIO connectors. What does it provide? #FujiNet is planned to provide the following functionality: "D:" Emulation, to virtually mount, read, and write ATR disk images over a protocol borrowed from the Spectranet community called TNFS. "R:" Emulation, via Type 1 POLL handler, to provide a virtual Wi-Fi modem for use with existing Communications programs such as Ice-T, BobTerm, AMODEM, and PLATOTERM. "N:" A new device for establishing TCP and UDP communication with other hosts, as well as controlling the adapter (setting configuration, mounting images, etc.) More functionality to be available by future over-the-air (OTA) updates to the firmware, such as IPP printing. Who can use it? Hopefully, everyone! The "D:" emulation provides an immediate out-of-the-box use case, to mount disks over the network, whatever network that may be, such as your local one, or an internet host. The "R:" handler will allow anybody who wants to call internet BBSes and services like IRATA.ONLINE to immediately use the device, and the "N:" device will allow whole new programs to be written which can natively handle network traffic! When will it be available? #FujiNet development (as of November 2019) is proceeding rapidly. Since the firmware is being written in Arduino, the firmware functionality is being sketched out and tested in very rapid cycles. I will be optimistic and say that by this time next year, we will have something well polished and usable. How much will it cost? Too early to tell, but, given that it is based on NodeMCU hardware, and given that the interface board is wholly populated with passive components, we (those of us working on the hardware side) expect the cost to be inexpensive, comparable to an SDrive-MAX. Still interested? More info: Wasn't this called #AtariWiFi? Yes, it was. In response to the name change, I have asked that the original thread be locked, previous updates, and demo videos can be found here: Where is the documentation? The documentation is being stored here in Google Docs: https://docs.google.com/document/d/1dIKFuxmX9O9cckz0HLN_7GmDKrYcbHury7Mgoomzqtg/edit?usp=sharing How are Disk Images Shared for "D:" Emulation? Disk images are shared using a file sharing protocol called TNFS. It was developed by Dylan Smith, the man who developed the Spectranet interface for the ZX Spectrum. It was understood that protocols like NFS and SMB were way too heavyweight to implement on 8-bit microcomputers, protocols like FTP and HTTP had way too much overhead, and protocols like TFTP and BOOTP were far too simple. So a nice medium was developed which maps the underlying filesystem in a simple, easy to implement protocol that can be used over UDP or TCP that uses a single connection. Where can I get a copy of tnfsd? The TNFSD server can be downloaded here: http://spectrum.alioth.net/doc/index.php/TNFS_server , it is available for Windows, Mac, and Linux. Source code is also available. Is the TNFS Protocol Information available? Absolutely, it is being used to implement the Arduino firmware: http://spectrum.alioth.net/svn/filedetails.php?repname=Spectranet&path=%2Ftrunk%2Ftnfs%2Ftnfs-protocol.txt What Atari-specific information is being used to implement the firmware? @phaeron's excellent Altirra Hardware Reference Manual is being used for the SIO side of things: http://www.virtualdub.org/downloads/Altirra Hardware Reference Manual.pdf Who is working on this? @tschak909 working on Firmware @mozzwald working on Hardware and Firmware, did first pass of enclosure. @jeffpiep working on Hardware and Firmware @Mr Robot working on Hardware and enclosure @Bill Lange Helping test. @48kRAM helping test. @a8isa1 helping test with his own board/interface @ivop helping test with his own board/interface Joe Decuir will also have a board for testing, soon. How is the hardware being implemented? The Hardware is being implemented in two pieces, a NodeMCU 1.0 comprises the majority of the hardware, providing the microcontroller, the WiFi interface, and a USB UART and power connection. The other major piece of hardware is the interface board which consists of a series of passive components which not only connect the board to the SIO bus, but also sufficiently isolate it where needed. This is a Rev2 board and its associated NodeMCU: I see an SIO connector on there, how is that being managed? @mozzwald and @Mr Robot have come up with an ingenious method of fabricating a connector that will not only fit the existing Molex sockets and cables, but also be easy to produce, which involves 3D printing a sandwich shell containing in-line pins that are soldered to a board-edge connector on the 'hole' side to provide a male pin for an SIO socket, or on the pin side to provide a female socket for the cabling, as seen here: How is the firmware being implemented? The firmware is being implemented as a series of small test programs. Each test program implements one piece of functionality (or a sub-functionality), and is used to determine where the problems may lie. Each test program typically involves one piece of Arduino firmware running on the device itself, and one piece of software running on the Atari. Each test is in its own directory in tests/ under the github repo. Does this mean there will be a lot of test programs? Yes. A lot. I estimate roughly a couple hundred test programs may be written over the course of development. The advantage to this is that everyone will see functionality develop quickly, in very small increments. What does DONE look like for 1.0? (D) emulation, read, write, mount disk images (R) emulation, CIO handler with baud rate/comms parameter configuration, and hardware handshaking for those that can use it via unused PROCEED line. (N) emulation, network scan and connect, TCP connect, stream, and read/write packets, UDP read/write packets, incoming packets trip INTERRUPT line, UDP multicast OTA updates for future updates. I want to help! What can I do? Contribute to this thread. Contact @tschak on twitter if you want to participate in the inner discussions (highly technical, very active.) Can you help write Arduino code? Can you help write example programs for the Atari in BASIC, Assembler, and/or C? Can you help improve the hardware? Can you help work out production logistics? And when we get hardware distributed, can you help test? Excited? So are we. -Thom
-
Anyone who prefers to use AtariAge as their bug reporting thread, can do so here. Please try to provide a concise description, doesn't have to be verbose, but enough information to reproduce the problem, e.g. if the problem is with a disk image, please provide the disk image (or a TNFS location). We'll try to fold this into github issues, so we can keep track. -Thom
-
This thread is for discussion of the #FujiNet hardware and it's progress. Hardware schematics and design files when made available will be in the Wiki and the fujinet-hardware repository on github. Current vertical hardware design looks like:
-
Fujinet users with U1MB and SIDE3 may wish to update their PBI BIOS with a version which fixes a high-speed polling bug when HSIO is applied to 'All' devices. Special thanks to @fenrock.
-
FujiNet is a 1.6X - SDrive-Max is flashed to 1.3 - It was from Vintage Computer. It has a 9341 display and it looks like it has an UNO2SIO board - I attached the SDrive-Max to the FujiNet SIO a few months ago and set it all aside until recently. When I tried to use the SDrive-Max without the FujiNet, it wouldn't boot any DOS or disk images and wouldn't load D0: - It also does not boot on a different Atari 8-bit computer. I opened the SDrive-Max, removed the display, tightened the cables, and reassembled the device and re-flashed the SDrive-Max to 1.3 - It still did not boot on SIO or external power. Strangely, the SDrive-Max DOES boot when it's attached to the FujiNet SIO. I also tried recopying sdrive.atr to the SD card and trying the original SD card - Neither SD card boots. Is there any reason this would happen? Is there a way to make the S-Drive Max boot again as the only SIO device? Thanks! AK
-
- sdrive-max
- sdrive max
-
(and 1 more)
Tagged with:
-
Hi All, I just set up Altirra 4.10 and FujiNet-PC PC 2307.1 on my Windows 11 laptop. I followed the setup instructions and I am able to get Altirra to boot to the FujiNet. Problem is any disk or cart image I mount never loads, it boots into the Altirra BASIC screen. I am not sure what I might be doing wrong or miss-configuring. Has anyone run into this issue or might know of a fix? Thanks in advance.
-
I've been working on a way to use a remote SQL database from the A8 via FujiNet. I originally wanted to use cubeSQL since its free, and offers SQLite wrapped in a server. However I need full JSON to and from to make it work, and thats still WIP on the outbound side. In the mean time, I've been writing my own SQLite wrapper in the form of a proxy using Perl. I wanted to use SQLite because the db's are small and it doesn't have any running process requirements. I chose Perl because its readily available, and has easy integration with both IP and DBI. Since SQLite doesn't have user authentication compiled in (by default), and I want to keep it simple, so I added some basic authentication into the proxy itself (you'll maintain this DB directly with SQLite admin tools). The proxy will listen for connections, accept commands, and return responses. Right now, it will open and close a database, and handles user authorization successfully. I'm working on the add/delete/update and query functions now. The first 3 should be fairly easy to implement, with delete/update also having a user perm tied to them. Select will be a little more complex in how it returns larger datasets back to the A8, and I need to think through that a bit more. My initial thought is to allow up to three 4K chunks to be returned - the first result would have only two (current 4K, and next 4K), once progressed to next 4K then there would be three (previous 4K, current 4K, and next 4K). Chunk sized could be changed depending on program requirements/memory restrictions on the A8. The other thought is to just return some # of results which could be asked through calls to the proxy, which would free up a lot of storage memory on the A8. Here is a shot of the proxy server running, and a simulation client showing how the calls would be made. Just the basics right now.
-
LinguaXE is my first program which uses FujiNet. Its main purpose is to support Google translate functionality for Atari XL/XE. It is very early work in progress demo which is relatively simple yet. On my TODO list I have some ideas for additional features and improvements. For example there will be possiblity to type of international characters. It will give possiblity to set the source language different than English. Also I need to implement error handing routines in case of lack of FujiNet, Internet, Google translate service, etc. The program is implemented in MadPascal using @bocianu libraries dedicated for FujiNet. Some day I will release the program with its source codes. I will keep you informed about the progress of development in this thread.
-
-
@mozzwald and I have been working towards a #FujiNet bring-up on the #AtariLynx. Can anyone verify that this is a valid RedEye packet? 14:26:17.756 > LYNX-IN: 06 00 00 01 00 FF FF FA 14:26:17.756 > 14:26:17.784 > LYNX-OUT: 06 00 00 01 00 FF FF FA 14:26:17.784 > 14:26:17.784 > LYNX-IN: 06 00 00 01 00 FF FF FA 14:26:17.785 > 14:26:17.806 > LYNX-OUT: 06 00 00 01 00 FF FF FA -Thom
-
The #ColecoAdam version of the #Fujinet News program has been released. Like the #Atari8bit version, It provides a viewer into a bunch of aggregated news sources. You can run it on adam-apps.irata.online/Displays/news.ddp Source is @ https://github.com/FujiNetWIFI/fujinet-apps/tree/master/news/adam
-
Dear All! This is our "Atari 8-bit Programming" Discord server. It is a twin Discord server to the Fujinet Discord. Here is an invitation: https://discord.gg/GTapZjCsgp Best, Peter Kaczorowski
-
fujinet FujiNet for #ColecoAdam 1.0 Schematic released.
tschak909 posted a topic in ColecoVision / Adam
@mozzwald has released version 1.0 of the #ColecoAdam #FujiNet to the public, for anyone who wishes to make the hardware. https://github.com/FujiNetWIFI/fujinet-hardware/blob/master/ADAM-Prototype/adamfuji-v1.0-schematic.jpg -
While brainstorming other features for the FujiNet hardware, I stumbled upon https://github.com/MockbaTheBorg/RunCPM/, a MIT-licensed CP/M 2.2 emulator that already runs on the ESP32. Given that the FujiNet already does drive emulation, buffers printer output, and acts like a serial port, CP/M mode is the last bit of functionality needed to do everything that the ATR8000 did. I don't know enough yet about the memory usage of the FujiNet core -- RunCPM needs 64K for the CP/M system memory, plus additional RAM for running the Z80 emulation. The ESP32 port was done using the Arduino support, so it would need to be ported to PlatformIO as well as changed to use SD card code that FujiNet already has internally. Does this seem viable? Interesting?
-
This is the latest SIO Breakout Board I've designed with FujiNet style connectors. I've posted in some other threads about it but figured I should put it here in it's own thread. The idea came originally during development of FujiNet when we needed to hookup a logic analyzer to watch the signals. After many suggestions and several versions later, this is what I've come up with. It uses 3D printed FujiNet style connectors and thus the board is on a vertical plane with a 3D printed case to hold it all together. There is a 13 pin 2.54mm header on the top for external connection to your equipment of choice. Optionally, there are pads for a Through Hole and/or SMD 0805 capacitor connected to the 5V power rail and ground. This design uses new longer / thicker receptacle pins which fit SIO plugs better than the currently available FujiNet hardware (these pins will be in the next FujiNet hardware release too). The board can be assembled in two ways: Plug and Receptacle: plug for connecting to any SIO receptacle and a receptacle for connecting your SIO cable Dual Receptacle: requires use of 2 SIO cables for pass through. Also doubles as a cable extender / coupler Assembled board rear side with capacitors. Left is Dual Receptacle with SMD cap, right is Plug & Receptacle with Thru Hole cap. Assembled board front side. Left is Dual Receptacle, right is Plug & Receptacle. Assembled case front side. Left is Dual Receptacle, right is Plug & Receptacle. Assembled case rear side. Left is Dual Receptacle, right is Plug & Receptacle. Since this a derivative work of the FujiNet connector design I will be following the open-source hardware license and releasing all design files at some point in the near future. I would like feedback from users before that happens so any changes or fixes can be made first. They will be put up on the FujiNet github when released. I will be attending VCFMW 2021 this year (as long as covid doesn't crash the party) and will have one of each with me if anyone wants to see them. I'll be the tall dude with long hair wearing a FujiNet T-Shirt Five boards are up for sale on fujinet.online and I added a free pickup at VCFMW shipping for all items if you will be there.
-
I have tried loading disk images off 4 different net sources and none will boot. I keep getting a "mount device error." Any ideas what's wrong?
-
Okay, have started committing to a repository called FujiNetWifi/Adam-Arduino-Tests. These are prototype sketches being written against the Arduino framework, but built in Platform.io. The repository is here: https://github.com/FujiNetWIFI/Adam-Arduino-Tests and I am currently working on test #4, which should send a single block as if it's coming from Device #4 (Disk Drive 1), to boot a simple message. https://github.com/FujiNetWIFI/Adam-Arduino-Tests/blob/main/04-send-bootblock/src/main.cpp Thing is, I'm definitely getting messages meant for me, but am immediately getting a NACK, before I even send anything back! WTF? How could this be happening? Any ideas while I grind through the 6801 code? -Thom
- 1 reply
-
- 1
-
Hello Apologies if I missed it, but is there any way to set up a local only TNFS server that operates within my firewall? I bookmarked the page on setting up a TNFS and it seemed as though it was geared towards establishing an online server. Many thanks!!!
-
Hello there, I don't really know if that's the right category for this topic, don't know where else to put it... ¯\_(ツ)_/¯ Does anyone have experience in hosting a server for the PLATO protocol (like irata.online:8005)? I'd like to try it out, nothing serious though, just for fun.... so is there possibly any software or instructions available? Because I couldn't really find what I'm looking for on irata and I don't know any other sites who host PLATO. Thanks in advance for any advice. Cheers
-
- irata.online
- platoterm
-
(and 1 more)
Tagged with:
-
Hi to all, I need to understand why some softwares in .ATR images are not loading correctly from the MicroSD Card with Fujinet, I have an Atari 800XL with the Ultimate 1MB and the PIA COVOX, my Fujinet is 1.0, it is updated with the latest firmware and have a MicroSD of 16GB. Maybe you think that maybe this upgrade is creating a compatibility issues, but no, I have a 130XE and a 64XE in perfect condition and I've got the same problem, loading with errors, look at these examples: AlleyCat: Chaos Music Composer: I think Fujinet is awesome but this is so weird because the softwares that are not loading are so specific, I tried to load the same softwares with an SDrive Max and works great. Can you give me some advice to fix this problem? Thank you all!