FujiNet on PC?

[apc]

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?

[tschak909]

It should be possible to port, the repo is here:

https://github.com/FujiNetWIFI/fujinet-platformio

 

-Thom

[apc]

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

[apc]

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

[tschak909]

[tschak909]

[billkendrick]

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" >;-)

[apc]

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

 

[apc]

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

[_The Doctor__]

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 by _The Doctor__

[apc]

Good point about ICE T XE. Let's enjoy some colors in command line.

 

 

Almost perfect dev. env.

[phigan]

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?

[apc]

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

 

[tschak909]

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

 

[apc]

Yes, will be pleased to share my bits under FujiNet umbrella 🙂

[apc]

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 😇

[apc]

Almost forgot to mention, I have succeeded with macOS build 🙂

 

Running fujinet on macOS inside KVM

 

[apc]

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 by apc

[atarixle]

Quote

Not (yet) working

• FujiNet network device (N:) with support for various network protocols

Oh, but this is what I am waiting for!

[apc]

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

[phigan]

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 by phigan

[apc]

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 by apc

[phigan]

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!

[apc]

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.

[apc]

Working on N device protocols ...