Jump to content
IGNORED

FujiNet on PC?


apc

Recommended Posts

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?

  • Like 3
Link to comment
Share on other sites

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

  • Like 2
Link to comment
Share on other sites

  • 1 month later...

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

P1120414s.thumb.JPG.0356285764919a7fb69e70b2c894aca7.JPG

 

FujiNet Config boot

P1120415s.thumb.JPG.16f11da3a81e10d27f50e8bf6ac80b21.JPG

 

Firts time start and fake WiFi presented to Atari (networking is configured on OS/Linux)

P1120416s.thumb.JPG.29911d8fbfe4cf3fb737738ed82b8eb8.JPG

 

SD (directory on Linux) added to hosts and some disk drive mounted

P1120418s.thumb.JPG.20d787c47f81452fedaf5b8e440d7394.JPG

 

Booting up XEX from notebook

P1120419s.thumb.JPG.ef865b77188d4f073967344662afcc6a.JPG

 

Config screen without real Fujinet hardware

P1120420s.thumb.JPG.8e1992ed7169e5bfd811868e6e4b4ede.JPG

 

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

  • Like 12
Link to comment
Share on other sites

  • 2 weeks later...

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

 

  • Like 3
Link to comment
Share on other sites

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

2a-telnet-s.thumb.jpg.ae9bf0720ddbf0cde10c7fe9c45bf192.jpg

 

Desktop Terminal sharing - Atari joined the screen session (GNU Screen) which is running on laptop.

2b-gnu-screen-s.thumb.jpg.5a5a4a387a66937a7d92066e60b64d08.jpg

 

Coding in vim ...

2c-vim-s.thumb.jpg.f859e115140b539780ab6cd5e8d99242.jpg

 

... and building

2d-build-s.thumb.jpg.2b006394c53a144df53ca16a110d29bc.jpg

 

?

Jan

  • Like 6
Link to comment
Share on other sites

  • 3 weeks later...

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

 

Link to comment
Share on other sites

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

 

Link to comment
Share on other sites

  • 3 weeks later...

Added basic browser into web interface.

 

Click host name to open host browser:

01.thumb.png.b2b3150ce54626b889c533a33320c962.png 02.thumb.png.d172de9e0f6c140a8488b0489da923f8.png

"Navigation bar":

  • To upper directories 03s.png.88bd7c37aaf0c2afd7dfb1991d052e21.png
  • To root directory  04s.png.80146899033f3a7d7aa9ccbc1644f950.png
  • Back to main page 05s.png.b1691c996385fe98075568e618cab69b.png

Mounting and unmounting images:

 

06.thumb.png.5c72e425fd9cb950412451b79a86acd5.png07.thumb.png.be4b12d3f081c045fbbbd3430f14aadd.png08.thumb.png.ea48542dfabb1bcbc8c3699e756a0d14.png

 

Downloading file:

09.thumb.png.614691de5bc19b1f0b819b849b134b0d.png

 

Jan

 

BTW WOW to Albert !!! I thought my XE is 8-bit :-D

Edited by apc
  • Like 4
Link to comment
Share on other sites

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

Link to comment
Share on other sites

  • 2 weeks later...
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

 

sio.gif.f84d9b9e440cb6dc70a5c7965cef129c.gif

(http://mixinc.net/atari/pinouts/sio.htm)

 

Jan

Edited by apc
Link to comment
Share on other sites

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!

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...