apc Posted November 14, 2020 Share Posted November 14, 2020 Sorry for the heretical question. The FujiNet software, the part which is run on the hardware module, how difficult it can be to compile it (port?) and run it on PC? I believe, for SIO2PC (+RespeQt) users it would be interesting alternative. Maybe as a standalone headless "service" (full port) or just new N: device functionality added to RespeQt. What do you think? 3 Quote Link to comment Share on other sites More sharing options...
tschak909 Posted November 14, 2020 Share Posted November 14, 2020 It should be possible to port, the repo is here: https://github.com/FujiNetWIFI/fujinet-platformio -Thom Quote Link to comment Share on other sites More sharing options...
apc Posted November 14, 2020 Author Share Posted November 14, 2020 No sure, I can do it myself. Let's check the code and I will see FujiNet is very nice project or better, multiple projects to make all those pieces (hardware, software for it, software for Atari, TNFS, ...) working together. Thanks for the effort, time, ideas and sharing all that with us! Jan 2 Quote Link to comment Share on other sites More sharing options...
apc Posted January 6, 2021 Author Share Posted January 6, 2021 OK, I did first step. Some sources updated to compile and run on Linux. It's minimum functionality (SD/local host, disk emulation with ATR and XEX), but it seems it can work Fujinet "port" started on old notebook connected via serial port with Atari FujiNet Config boot Firts time start and fake WiFi presented to Atari (networking is configured on OS/Linux) SD (directory on Linux) added to hosts and some disk drive mounted Booting up XEX from notebook Config screen without real Fujinet hardware I need to fix the Atari (keyboard is dying on my XL). Then I am looking forward to port/play with NET part of FujiNET! Jan 12 Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 6, 2021 Share Posted January 6, 2021 Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 6, 2021 Share Posted January 6, 2021 1 Quote Link to comment Share on other sites More sharing options...
billkendrick Posted January 6, 2021 Share Posted January 6, 2021 Yes yes yes... I want to see the "N:" side of Fujinet go from "thing that runs on a physical, ESP-based Fujinet" to "C library that Atari800 can link to" >;-) 2 Quote Link to comment Share on other sites More sharing options...
apc Posted January 16, 2021 Author Share Posted January 16, 2021 Thank you for nice feedback :) I like the idea of FujiNet library, but the path is quite long ... I am doing just small changes to the original code to compile that and run it on Linux (and hopefully others too, later). For the library, more design changes would be necessary. It's next level 3 Quote Link to comment Share on other sites More sharing options...
apc Posted January 16, 2021 Author Share Posted January 16, 2021 Modem emulation was ported. I never used modem with Atari before. I like it. @Thom nice to see telnet protocol and terminal emulation in action! Some fun with FujiNet emulated modem: Running Ice-T, enabling VT100 and telnet, connecting to the laptop Desktop Terminal sharing - Atari joined the screen session (GNU Screen) which is running on laptop. Coding in vim ... ... and building ? Jan 6 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted January 16, 2021 Share Posted January 16, 2021 (edited) Term can be ansi with ICE T XE, and then you will have some color as well or if you mess with ICE T settings you can follow an ISO based set more closely as well. Looking good! Edited January 16, 2021 by _The Doctor__ 1 Quote Link to comment Share on other sites More sharing options...
apc Posted January 17, 2021 Author Share Posted January 17, 2021 Good point about ICE T XE. Let's enjoy some colors in command line. Almost perfect dev. env. 5 Quote Link to comment Share on other sites More sharing options...
phigan Posted February 2, 2021 Share Posted February 2, 2021 So what all did you have to do to get this built? Do you think it would also work on ARM/Termux (Android)/Raspberry Pi? Quote Link to comment Share on other sites More sharing options...
apc Posted February 4, 2021 Author Share Posted February 4, 2021 Hi, @phigan I have no exp. with Raspberries but it should be possible to compile it for ARM based Linux. The dependencies are Linux kernel with serial port driver, glibc (not tested with other libc) and TCP/IP working on a host. Better to call it (Linux) port instead of build. FujiNet is ESP32 based and it relies on framework provided by PlatformIO (file system drivers, UART, timers, tasks, lwIP, HTTP server, ...). To get it running on Linux (and others) all these needs to be replaced by some functional equivalents. To you first question: lot of small changes ... work in progress. It's time to think about GitHub account ? Changes since last post: access remote hosts/images via TNFS protocol (somehow) works, printer emulation added, web interface (http server) works Jan Quote Link to comment Share on other sites More sharing options...
tschak909 Posted February 4, 2021 Share Posted February 4, 2021 4 hours ago, apc said: Hi, @phigan I have no exp. with Raspberries but it should be possible to compile it for ARM based Linux. The dependencies are Linux kernel with serial port driver, glibc (not tested with other libc) and TCP/IP working on a host. Better to call it (Linux) port instead of build. FujiNet is ESP32 based and it relies on framework provided by PlatformIO (file system drivers, UART, timers, tasks, lwIP, HTTP server, ...). To get it running on Linux (and others) all these needs to be replaced by some functional equivalents. To you first question: lot of small changes ... work in progress. It's time to think about GitHub account ? Changes since last post: access remote hosts/images via TNFS protocol (somehow) works, printer emulation added, web interface (http server) works Jan Do you want access to the fujinet github? We can add a sub-repo. -Thom Quote Link to comment Share on other sites More sharing options...
apc Posted February 4, 2021 Author Share Posted February 4, 2021 Yes, will be pleased to share my bits under FujiNet umbrella ? 3 Quote Link to comment Share on other sites More sharing options...
apc Posted February 22, 2021 Author Share Posted February 22, 2021 For now I placed sources here: https://github.com/a8jan/fujinet-pc We can move it to fujinet sub-repo if the offer is still valid ... after you will see the mess I did in a code ? 1 Quote Link to comment Share on other sites More sharing options...
apc Posted February 22, 2021 Author Share Posted February 22, 2021 Almost forgot to mention, I have succeeded with macOS build ? Running fujinet on macOS inside KVM 3 Quote Link to comment Share on other sites More sharing options...
apc Posted February 22, 2021 Author Share Posted February 22, 2021 (edited) Added basic browser into web interface. Click host name to open host browser: "Navigation bar": To upper directories To root directory Back to main page Mounting and unmounting images: Downloading file: Jan BTW WOW to Albert !!! I thought my XE is 8-bit Edited February 22, 2021 by apc 4 Quote Link to comment Share on other sites More sharing options...
atarixle Posted February 23, 2021 Share Posted February 23, 2021 Quote Not (yet) working FujiNet network device (N:) with support for various network protocols Oh, but this is what I am waiting for! Quote Link to comment Share on other sites More sharing options...
apc Posted February 23, 2021 Author Share Posted February 23, 2021 Oh yes me too :-) That's the reason I have started with it! The small issue with N: is that it uses one extra signal (PROCEED PIN) which is not carried by standard SIO2PC adapter (at least not on my home made from 90's). I think, for the old MAX232 it would be possible to wire unused receiver. I am not sure if some more recent SIO2USB adapters (available on the internet) can pass this signal? Anyone knows? Jan Quote Link to comment Share on other sites More sharing options...
phigan Posted March 5, 2021 Share Posted March 5, 2021 (edited) I'm using it from my Raspberry Pi 4 desktop. This is better than AspeQT or APE or any of that Which pin on SIO port would PROCEED pin go to? Edited March 5, 2021 by phigan Quote Link to comment Share on other sites More sharing options...
apc Posted March 5, 2021 Author Share Posted March 5, 2021 (edited) 7 hours ago, phigan said: I'm using it from my Raspberry Pi 4 desktop. This is better than AspeQT or APE or any of that Nice! Cross compiled on x86 or compiled on Raspberry/arm? 7 hours ago, phigan said: Which pin on SIO port would PROCEED pin go to? DTR or RTS converted to TTL to SIO PIN 9 (http://mixinc.net/atari/pinouts/sio.htm) Jan Edited March 5, 2021 by apc Quote Link to comment Share on other sites More sharing options...
phigan Posted March 6, 2021 Share Posted March 6, 2021 10 hours ago, apc said: Nice! Cross compiled on x86 or compiled on Raspberry/arm? Compiled directly on it. I even just built it on the Pi Zero and not even one warning. 10 hours ago, apc said: DTR or RTS converted to TTL to SIO PIN 9 Thanks! I have CTS already going to COMMAND (had to edit fnconfig.ini for that) and I added DTR to PROCEED. I'm not sure if PROCEED is making it work any differently, but it's doing well so far! Quote Link to comment Share on other sites More sharing options...
apc Posted March 6, 2021 Author Share Posted March 6, 2021 52 minutes ago, phigan said: I'm not sure if PROCEED is making it work any differently, but it's doing well so far! Not yet. PROC is used by N device handler and I am at the beginning to make N protocols working on PC. Quote Link to comment Share on other sites More sharing options...
apc Posted March 7, 2021 Author Share Posted March 7, 2021 Working on N device protocols ... 8 Quote Link to comment Share on other sites More sharing options...
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.