Jump to content
apc

FujiNet on PC?

Recommended Posts

@apc we need to sometime soon start working on folding your changes into our master branch, so that you're not having to constantly pull in from upstream.

 

-Thom

  • Like 1

Share this post


Link to post
Share on other sites

oh yes, the look at diff scares me. I am not sure how to do it, if to add dozens of #ifdefs into the code and how to include sometimes completely different files into the build process...

 

Share this post


Link to post
Share on other sites

well, I could perhaps work with you to see what you've changed, help figure out how to fold in each change?

(and yes, probably lots of ifdefs.)

 

-Thom

 

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

I don’t quite get what you’ve done here apc. You mean you’re connecting an Atari to a pc with an SIO2PC cable and the Fujinet code that normally runs on the ESP instead is talking to the 8-bit over the cable to give N: access ?

Edited by Alfred

Share this post


Link to post
Share on other sites
9 hours ago, Alfred said:

You mean you’re connecting an Atari to a pc with an SIO2PC cable and the Fujinet code that normally runs on the ESP instead is talking to the 8-bit over the cable to give N: access ?

Yes.

 

For most of emulated devices (disks, printer, modem) and FujiNet config the regular SIO2PC should work.

 

N: device handler (network access) needs one extra link/signal which is likely not present on old style SIO2PC (attaches to serial port on PC, I had to extend my old SIO2PC to pass this extra signal).

I have no exp. with modern devices like SIO2USB or SIO2BT, there is some chance the signal is carried.

Another option would be to build cable similar to:

...and connect RTS to PROCEED pin on SIO

 

Jan

  • Like 1

Share this post


Link to post
Share on other sites

whoa please measure RTS voltage level while asserted and not asserted with a multimeter... while not connected to your Atari !   You may need a level adjuster in the mix.... You may be stressing or damaging stuff and not know it. I depends on the rs232 port... please check!

Share this post


Link to post
Share on other sites
1 hour ago, apc said:

...and connect RTS to PROCEED pin on SIO

Ops, would be more precise. @_The Doctor__ thanks for pointing this out. Any signal from regular RS232 cannot be connected directly to SIO.

I meant RTS signal from USB to TTL converter. When planning to share SIO port with other devices, better to use diode, similar to the one for TxD signal on provided link (TheMontezuma replied to rcamp48)

 

Share this post


Link to post
Share on other sites

Is anyone known to be working on bringing Fujinet to Mister by running the N: driver on the ARM side?  For that matter is anyone aware of efforts to bring SIO support to Mister via the user port or other means?

Share this post


Link to post
Share on other sites
On 3/24/2021 at 5:31 PM, weasel5053 said:

Is anyone known to be working on bringing Fujinet to Mister by running the N: driver on the ARM side?  For that matter is anyone aware of efforts to bring SIO support to Mister via the user port or other means?

I wish for this too, but it doesn't seem like it :)

Share this post


Link to post
Share on other sites
15 hours ago, phigan said:

I wish for this too, but it doesn't seem like it

I worry, my skills is limited to do that ;-)

 

  • Like 1

Share this post


Link to post
Share on other sites

Is fujinet-pc at the point of development where it can support Bill Kendrick's ISS.XEX? I ask because I'm not sure about the cable I cobbled together. I think I have PROCEED connected to RTS but ISS.XEX is not retrieving data.

 

-SteveS

Share this post


Link to post
Share on other sites
Posted (edited)
3 hours ago, a8isa1 said:

Is fujinet-pc at the point of development where it can support Bill Kendrick's ISS.XEX?

Yes. It should work. Plain HTTP request-response called by ISS.XEX is handled by fujinet-pc just fine.

You should get similar output in terminal to each ISS update (Open, Status, Read, Close):

CF: 71 4f 04 00 c4
sioNetwork::sio_process 0x4f 'O': 0x04, 0x00
sioNetwork::sio_open()

write: 1
ACK!
Deleting existing rateTimer
<-SIO read 256 bytes
read: 0
read: 24
read: 30
read: 30
read: 31
read: 30
read: 30
read: 30
read: 30
read: 21
read: 1
write: 1
ACK!
sioNetwork::parseURL(N:HTTP://api.open-notify.org/iss-now.json)
sioNetwork::parseURL transformed to (N:HTTP://api.open-notify.org/iss-now.json, HTTP://api.open-notify.org/iss-now.json)
Parse and instantiate protocol: N:HTTP://api.open-notify.org/iss-now.json
NetworkProtocol::ctor()
sioNetwork::open_protocol() - Protocol HTTP opened.
NetworkProtocolHTTP::mount(HTTP://api.open-notify.org/iss-now.json)
mgHttpClient::begin "http://api.open-notify.org/iss-now.json"
NetworkProtocolFS::resolve(/iss-now.json,/,iss-now.json)
Resolved to http://api.open-notify.org/iss-now.json
NetworkProtocolHTTP::open_file_handle()
write: 1
COMPLETE!
SIO CMD processed in 149 ms
+read: 0
read: 5

CF: 71 53 00 00 c4
sioNetwork::sio_process 0x53 'S': 0x00, 0x00
write: 1
ACK!
sioNetwork::sio_status_channel(0)
PROTOCOL
Channel mode is 0
mgHttpClient::GET
000b2d39 _perform
Connected
Status: 200
Received: 295
Header0: Server = nginx/1.10.3
Body: 113 bytes
000b2e9f _perform status = 200, length = 0, chunked = 0
sio_status_channel() - BW: 113 C: 1 E: 1
->SIO write 4 bytes
write: 1
COMPLETE!
write: 4
write: 1
SIO CMD processed in 369 ms
-read: 0
read: 5

CF: 71 52 71 00 35
sioNetwork::sio_process 0x52 'R': 0x71, 0x00
sioNetwork::sio_read( 113 bytes)
write: 1
ACK!
NetworkProtocolFS::read_file(113)
NetworkProtocolHTTP::read_file_handle(0x55bbcef9eb90,113)
NetworkProtocolHTTP::read_file_handle_data()
::read from buffer 113
NetworkProtocol::read(113)
->SIO write 113 bytes
write: 1
COMPLETE!
write: 113
write: 1
SIO CMD processed in 66 ms
+read: 0
read: 5

CF: 71 43 00 00 b4
sioNetwork::sio_process 0x43 'C': 0x00, 0x00
sioNetwork::sio_close()
write: 1
ACK!
NetworkProtocolHTTP::close_file_Handle()
mgHttpClient::close
NetworkProtocolHTTP::umount()
mgHttpClient::close
2021-06-30 16:27:56  I mongoose.c:2091:mg_mgr_fr All connections closed
write: 1
COMPLETE!
NetworkProtocol::dtor()
SIO CMD processed in 6 ms

Jan

Edited by apc

Share this post


Link to post
Share on other sites
Posted (edited)

I get this instead.

Spoiler

 

sioNetwork::parseURL(N:HTTP://api.open-notify.org/iss-now.json)
sioNetwork::parseURL transformed to (N:HTTP://api.open-notify.org/iss-now.json, HTTP://api.open-notify.org/iss-now.json)
Parse and instantiate protocol: N:HTTP://api.open-notify.org/iss-now.json
Invalid protocol: HTTP
Could not open protocol.
write: 1
ERROR!
write: 1
ERROR!
SIO CMD processed in 149 ms
read: 0
read: 5

CF: 71 53 00 00 c4
sioNetwork::sio_process 0x53 'S': 0x00, 0x00
write: 1
ACK!
sioNetwork::sio_status_local(0)
->SIO write 4 bytes
write: 1
COMPLETE!
write: 4
write: 1
SIO CMD processed in 14 ms
read: 0
read: 5

CF: 71 52 00 00 c3
sioNetwork::sio_process 0x52 'R': 0x00, 0x00
sioNetwork::sio_read( 0 bytes)
write: 1
ACK!
write: 1
ERROR!
SIO CMD processed in 4 ms
read: 0
read: 5

CF: 71 52 00 00 c3
sioNetwork::sio_process 0x52 'R': 0x00, 0x00
sioNetwork::sio_read( 0 bytes)
write: 1
ACK!
write: 1
ERROR!
SIO CMD processed in 5 ms
read: 0
read: 5

CF: 71 43 00 00 b4
sioNetwork::sio_process 0x43 'C': 0x00, 0x00
sioNetwork::sio_close()
write: 1
ACK!
write: 1
COMPLETE!
SIO CMD processed in 5 ms

 

 

Edited by a8isa1

Share this post


Link to post
Share on other sites

Sorry, as typical for me, it was a user error.

 

I extracted newer fujinet-pc not realizing the files were extracting into folder ../fujinet-pc-fujinet-pc.    I had moved the prior version into ../fujinet-pc.  This folder name was easier for me to remember.    The newer version never got compiled.

 

It's working now.

 

Share this post


Link to post
Share on other sites
5 minutes ago, a8isa1 said:

It's working now.

Nice 🙂

 

Share this post


Link to post
Share on other sites

cannot wait to see it in atari800 and altirra :))))))))))))))))

Share this post


Link to post
Share on other sites

Thanks for making FujiNet on PC.  This is an exciting new use for a RPi and SIO2PC-USB I've had laying around.

  • Thanks 1

Share this post


Link to post
Share on other sites
On 7/1/2021 at 4:05 PM, pirx said:

cannot wait to see it in atari800 and altirra :))))))))))))))))

quick & dirty attempt:

Altirra-CUSTOMDEV-1600.thumb.png.c4f20d87bcf83b0f4915d9543db7fa1f.png

 

Altirra-CUSTOMDEV2-1600.thumb.png.c21316329b5184cfe4566e14796f97cc.png

 

It's proof of concept, trying to make SIO over UDP exposed by Altirra custom device and FujiNet connected to this "NetSIO bus".

 

🙂 Jan

  • Like 8
  • Thanks 1

Share this post


Link to post
Share on other sites
On 7/10/2021 at 4:33 PM, apc said:

Altirra-CUSTOMDEV2-1600.thumb.png.c21316329b5184cfe4566e14796f97cc.png

I approve ;)

 

As a Linux user, I'd love to see something like this done for Atari800, too.  My build process for both non-FujiNet games and FujiNet projects that I've been working on lately has been, basically "make run", where "run" is a Makefile target that runs "atari800 -run whatever.xex".

 

So when I was rapidly working on ISS tracker, for example, I had to just have a special "host build" that included hard-coded sample JSON for the ISS-tracking and astronaut-counting APIs that would normally be fetched via HTTP over N:.  I'd run that under Atari800 until I got things working right, and then copied it over to an SD card to plug into my Ultimate Cart (since it boots into it basically instantaneously) to confirm that things actually worked.

 

So, I love seeing N: getting some life in emulators, but I've never run Altirra, since I don't have Windows. ;-(

 

Share this post


Link to post
Share on other sites
2 hours ago, billkendrick said:

So, I love seeing N: getting some life in emulators, but I've never run Altirra, since I don't have Windows.

I only run Linux also. I rarely use emulation, but Altirra does run perfectly for me under Wine.

 

Last I saw, atari800 doesn't have complete SIO support so adding N: is not likely to happen soon.

  • Like 1

Share this post


Link to post
Share on other sites
7 hours ago, mozzwald said:

I only run Linux also. I rarely use emulation, but Altirra does run perfectly for me under Wine.

Okay, I took a stab at it.  My one major problem at the moment is the help text doesn't appear when I try to read the online documentation. 😕

 

What I never realized was that Altirra is released under the GPL v2, so that's good news!  Someone (smarter than me) could potentially make, say, a GTK+ or Qt based port, perhaps!? :-D

  • Like 1

Share this post


Link to post
Share on other sites
On 7/12/2021 at 1:23 PM, billkendrick said:

Okay, I took a stab at it.  My one major problem at the moment is the help text doesn't appear when I try to read the online documentation. 😕

 

What I never realized was that Altirra is released under the GPL v2, so that's good news!  Someone (smarter than me) could potentially make, say, a GTK+ or Qt based port, perhaps!? :-D

Or macOS-native :D

 

I have absolutely nothing against Atari800macX, which is my go-to emulator.  But having a backup that isn't MAME would be a plus.

Share this post


Link to post
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...