Search the Community
Showing results for tags 'fujinet'.
-
Whenever I booted my Sparta DOS 3.2g disk was entering the current date and time manually. It was usually quick, but sometimes I didn't have the time handy. However, my Atari's (130XE and 576NUC+) both have FujiNet. When I saw on the FujiNet Wiki that you can get the current date and time from the internet (https://tinyurl.com/2r5vae5v) I decided that I had a new assembler project... I am still (gradually) working my way through Atari Roots (https://tinyurl.com/4ea7vac8), so I have a lot to learn. I also needed to find out more about how Sparta Dos handled date and time. This led me to the Sparta DOS Construction Set, especially the R-Time 8 supplement - both found on the Serious Computerist website (https://tinyurl.com/3efmbwt8). It took a little while to figure it out, but it was a great chance to try out my MAC/65 & DDT cartridge image (via my A8picoCart). Among the things I learned: 1) DDT does not like to work on Page 6 2) You can hang MAC/65 by picking an assembly address too close to MEMLO 3) Indirect indexed addressing is very useful, and not covered in The Atari Assembler (by Don Inman & Kurt Inman). Luckily, it is in Atari Roots (though briefly). In the end, I replaced my Date and Time calls in the STARTUP.BAT file with a FUJITD.COM file built from the following code: 10 ;LIST#D:FUJITD.ASM 20 ; 30 .OPT OBJ 0000 40 *= $4000 50 ; 4000 4C0940 60 JMP START 70 ; 80 ;--- DATA & CONSTANTS --- 90 ; 0100 ; SD TIME VECTORS =FFC0 0110 VGETTD = $FFC0 ; GET TD =FFC3 0120 VSETTD = $FFC3 ; SET TD =FFC6 0130 VTDON = $FFC6 ; TD ON/OFF =FFC9 0140 VFMTTD = $FFC9 ; GET TD FMT =000A 0150 COMTAB = $0A ; DOSVEC 0160 ; 0170 ; TIME TO SET 0180 ; D/M/Y H/M/S 0190 ; 4003 0200 DATETIME 0210 ; DAY/MONTH/YEAR 4003 010101 0220 .BYTE $01,$01,$01 0230 ; HOUR/MINUTE/SECOND 4006 000001 0240 .BYTE $00,$00,$01 0250 ; 0260 ;-- MAIN -- 0270 ; 4009 0280 START 0290 ; 0300 ; SET IODCB 0310 ; 4009 A945 0320 LDA #$45 ; APETIME ID 400B 8D0003 0330 STA $0300 ; DDEVIC 400E A901 0340 LDA #$01 ; 4010 8D0103 0350 STA $0301 ; DUNIT 4013 A993 0360 LDA #$93 ; GETTIME 4015 8D0203 0370 STA $0302 ; DCOMND 4018 A940 0380 LDA #$40 ; RECEIVE 401A 8D0303 0390 STA $0303 ; DSTATS 401D A903 0400 LDA #DATETIME&255 401F 8D0403 0410 STA $0304 ; DBUFLOW 4022 A940 0420 LDA #DATETIME/256 4024 8D0503 0430 STA $0305 ; DBUFHI 4027 A906 0440 LDA #$06 ; # BYTES 4029 8D0803 0450 STA $0308 ; DBYTLO 402C A900 0460 LDA #$00 ; 402E 8D0903 0470 STA $0309 ; DBYTHI 4031 A9EE 0480 LDA #$EE ; 4033 8D0A03 0490 STA $030A ; DAUX1 4036 A9A0 0500 LDA #$A0 ; 4038 8D0B03 0510 STA $030B ; DAUX2 403B A900 0520 LDA #$00 ; 403D 8D0703 0530 STA $0307 ; DUNUSE 4040 A90F 0540 LDA #$0F ; 15 SEC. 4042 8D0603 0550 STA $0306 ; DTIMLO 0560 ; 0570 ; GET FUJINET DATE TIME 4045 2059E4 0580 JSR $E459 ; CALL SIOV 0590 ; 0600 ; 0610 ; LOAD NEW DATE/TIME 0620 ; 4048 A200 0630 LDX #0 404A A00D 0640 LDY #$0D 404C 0650 DTPUT 404C BD0340 0660 LDA DATETIME,X 404F 910A 0670 STA (COMTAB),Y 4051 E8 0680 INX 4052 C8 0690 INY 4053 E006 0700 CPX #6 4055 D0F5 0710 BNE DTPUT 0720 ; 0730 ; CALL TD SET ROUTINE 0740 ; 4057 AD01D3 0750 LDA $D301 ;PIA 405A 48 0760 PHA ;PUSH PORT 405B 29FE 0770 AND #$FE ;BIT 0 OFF 405D 8D01D3 0780 STA $D301 ;ENABLE RAM 4060 20C3FF 0790 JSR VSETTD ;CALL SET TD 4063 68 0800 PLA ;POP PORT 4064 8D01D3 0810 STA $D301 ;RESTORE PORT 0820 ; 4067 60 0830 RTS 4068 0840 .END It works on both of my machines, but I'd love to hear any suggestions for improvement to make the code more robust, compact, or both. I've attached the files in *.ATR format for others to play or use. Regardless, thanks for taking the time to look this over. FUJITD.atr
-
- fujinet
- sparta dos 3.2g
-
(and 2 more)
Tagged with:
-
Move files around on my TNFS LAN
Darken99 posted a blog entry in Atari 8-bit Memories, Ideas, and Active Projects
The TNFS is working fine, but I would like to move files (not just whole disk images) around (upload and download) my Atari LAN and between the Altirra on my PC and other machines on the network. The following is my solution, but if there is a better way to transfer files across I'd be eager to hear it... As I previously described, I have my wife's old computer "defenestrated" to LINUX MINT. I created a DOS 2.5 disk image (TNFS_transfer.atr) and put it in my PC's /TNFS directory with full access (chmod 777 ...) and owner set to tnfs (chown ...). It attaches easily from host 8 as drive slot (disk) 2: To get files to move between TNFS and my LINUX/WINE Altirra installation I need to keep both a TNFS and an Altirra disk image, in my TNFS directory and my Altirra user's directory, respectively: I can then copy the most recent TNFS_transfer.atr between the Altirra and TNFS directories (adjusting permissions and ownership for each location) when I want to move files between the emulator and other machines on the network. Networked machines can just use the TNFS version without further intervention. I have also made some bash shell scripts to simplify the LINUX side of things. If anyone has a different way, I'd love to hear about it. Otherwise, thanks again for dropping by. -
TNFS on Linux Mint using old PC
Darken99 posted a blog entry in Atari 8-bit Memories, Ideas, and Active Projects
I recently "received" an old computer from my wife (a Dell 2-in-1 with Windows) which I have repurposed as my home Linux learning machine. I installed Linux Mint and decided to try to set up an Atari LAN in my home. Following the Wiki instructions (https://github.com/FujiNetWIFI/fujinet-firmware/wiki/Setting-up-a-TNFS-Server#setting-up-tnfs-on-raspberry-pi-or-linux) was a bit difficult because 1) I am new to Linux, and 2) it is definitely targeted to Raspberry-Pi installations. However, with a little cross-referencing with Atari Age entries and a lot of trial and error, I got it to work! A small victory. I've attached a pdf with my procedure, adapted from the Wiki entry, in case it helps anyone. I am new, so if you see anything that looks wrong please let me know. Otherwise - thanks for dropping by the blog! Setup TNFS.pdf -
I have an ongoing project of bringing my beloved 800XL back up and running to feed my nostalgia pains. Sadly, the 1050 and the 1010 are both dead-ish. Will cover that another time probably. For now though, I'm looking for an SD card solution. Almost all the files I have are in ATR format. So looking for something SIO based rather than cartridge based. Which would seem to narrow that down to the SDrive Max or the Fujinet. What are the pros and cons of each? Is there any ATR compatibility issues with either of them? And one has a touchscreen and one has wireless connectivity, both of which seems a little gimmicky? Other questions may follow.
-
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.
- 31 replies
-
- 15
-
This thread aims to document the process of building fujinet-pc in a Linux environment. As usual, there will be many ways of accomplishing this, so comments, questions, and suggestions are welcome. There is an assumption being made that the person seeking to build fujinet-pc is comfortable with working in a Linux shell (commandline) environment. It's not necessary to be the best in the world at it by any means, but being familiar with package management tools, sudo, running shell scripts, etc. is necessary. It's also worth mentioning that the environment I'm primarily building this in is Raspberry Pi OS on a Raspberry Pi 3B. Depending on the architecture and Linux distribution in use, some parts of the process may be different to how it has been detailed below. If you run into any issues, by all means ask for assistance - just make sure to detail the Linux distribution in use, the architecture you're building under (x86, x64, ARM, etc.) and we'll help with figuring it out. MacOS is not covered by these instructions. With that said, open a terminal and start by making sure that three requirements are satisfied first: Python3 Python3 may already be installed on your system. To test if it is, type `python3 --version' at a shell prompt and hit Return. If you see output along the lines of 'Python 3.x.x', you're good to go. If not, check if it's available from your distribution's package manager (which it almost certainly will be). Platformio Unless you're doing python development, chances are that this one isn't installed. Check your package manager to see if it's available; if it is, go ahead and install it. If the package manager doesn't include it, see https://platformio.org/install/cli for information on how to obtain and install it. jinja2 Also not likely to have been installed unless doing Python development. It can be installed using either the system's package manager or pip. See https://pypi.org/project/Jinja2/ for details. git If git isn't installed, the system's package manager will again come to the rescue. For a quick check, type 'git --version' at a shell prompt; if you don't see a line similar to 'git version 2.39.3 (Apple Git-145)', this would be a good time to install it. Build tools such as g++, cmake, libraries, etc. will also need to be present. These are typically installed by default on most distributions, but not always. Pro-tip: missing packages can cause the build process to fail, so if a build error refers to something missing or not found, install the necessary packages (where appropriate) and try again. Having got that out of the way, it's time to set up a directory to build out of. From the terminal, issue the following command: mkdir ~/build && cd ~/build Next, clone the fujinet-firmware git repo and change directory into it: git clone https://github.com/FujiNetWIFI/fujinet-firmware && cd fujinet-firmware Running the 'build.sh' script in that directory will start the build process, but the target 8-bit platform needs to be specified first: For Atari: ./build.sh -p ATARI For Apple: ./build.sh -p APPLE The capital letters are intentional. There are no other target platforms at this time; simply choose the one that sounds more appealing if yours isn't covered. At this point, the build process should have started. Go grab a snack. If any errors occur, copy and paste them into this thread and we'll try to help you figure out what went wrong. Now that the software is built, we can move on to installing, configuring, and running it. There are a few housekeeping tasks that need to take place first. The first step is to create a user and group for fujinet to run as: sudo adduser --system --no-create-home --shell /sbin/nologin --group fujinet Next, the fujinet binary needs to be copied to a suitable location for it to run from. This example uses /usr/local/bin, but anywhere appropriate on your system can be used: sudo mv build/dist/fujinet /usr/local/bin Third, the support files used by the fujinet binary need to be put somewhere convenient. Again, /usr/local/etc is used for this but can be changed to suit: sudo mkdir /usr/local/etc/fujinet-pc && sudo cp -rp build/dist/* /usr/local/etc/fujinet-pc Moving on, ownership of the support file directory needs to be changed: chown -R fujinet: /usr/local/etc/fujinet-pc Edit the fnconfig.ini file to reflect the environment fujinet-pc is being run in: sudo <name of your favourite editor here> /usr/local/etc/fujinet-pc/fnconfig.ini fujinet-pc is now essentially installed and ready to go. To test it, issue the following command, changing pathnames as needed: /usr/local/bin/fujinet -c /usr/local/etc/fujinet-pc/fnconfig.ini -s /usr/local/etc/fujinet-pc/SD A bunch of text should go scrolling up the terminal window, and if you point a browser to http://<your IP address>:8000, you should see the fujinet-pc web interface. To return to the shell prompt, hit CTRL-C. If the test run was successful, congratulations! You now have a working fujinet-pc installation. But what if you want to start and stop it a bit more conveniently in the future? This is where creating a unit file comes in. Without going too far off into the weeds, if your machine uses systemd to control the starting and stopping of services, it uses unit files to manage those processes. There are other ways of doing this, but as most distributions currently use systemd, this is the one that we'll focus on here. The first order of business is to create a unit file. Again, adjust the pathname as needed to reflect your system: sudo touch /lib/systemd/system/fujinet-pc.service Open the file that was just created for editing, and copy and paste the following into it. Be sure to once again change pathnames as necessary before saving the file: [Unit] Description=Start fujinet-pc as a service After=syslog.target network-online.target remote-fs.target [Service] User=fujinet ExecStart=/usr/local/bin/fujinet -c /usr/local/etc/fujinet-pc/fnconfig.ini -s /usr/local/etc/fujinet-pc/SD WorkingDirectory=/usr/local/etc/fujinet-pc ExecReload=/bin/kill -s HUP $MAINPID ExecStop=/bin/kill -s QUIT $MAINPID PrivateTmp=true [Install] WantedBy=multi-user.target systemd needs to be made aware of the new unit file. Issue the following command: sudo systemd daemon-reload Now go ahead and try starting fujinet-pc: sudo systemctl start fujinet-pc If this returns you straight back to a shell prompt, that's expected. Now issue the following: sudo systemctl status fujinet-pc Check the output for a line similar to the following: Active: active (running) since Sat 2024-03-23 11:23:45 CDT; 6h ago That indicates that fujinet-pc is running, and should again be reachable through a browser at http://<your IP address>:8000 . To stop fujinet-pc, issue the following: sudo systemctl stop fujinet-pc If changes are made to fnconfig.ini while fujinet-pc is running, it can be restarted in order to pick up the changes: sudo systemctl restart fujinet-pc Note that the above commands will only allow fujinet-pc to run while you are logged in. To make it start at boot: sudo systemctl enable fujinet-pc And, predictably, if you don't want it to start at boot, the following will take care of that: sudo systemctl disable fujinet-pc Hopefully this has been useful to anyone looking to build fujinet-pc. Again, comments, questions, and suggestions are most welcome.
- 4 replies
-
- 1
-
- fujinet
- fujinet-pc
- (and 4 more)
-
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?