apc

For the Launcher "GUI" utility, more or less the core functionality is there. The stuff to improve is the build process (automate it), add 32-bit for Windows, prepare Linux binary bundle runnable on most common distros (likely in form of AppImage), prepare macOS bundle. Some cosmetics, GUI window can use better background picture. Current picture (borrowed from fujinet.online, thank you ) is jagged on window edges (limited by transparency support). Maybe 800/XL/XE skins? For the emulator bridge it would be nice to get other Atari emulators pluggable too. Altirra was ready for external peripherals. For other emulators it is likely their code needs to be modified/extended to support such thing. And FujiNet-PC, it needs to work on it to catch with HW FujiNet. ..or to start from opposite end, make some programs which will use FujiNet! ?

FujiNet CONFIG: https://github.com/FujiNetWIFI/fujinet-config Loader to speed up CONFIG boot time: https://github.com/a8jan/fujinet-config-loader Lot of valuable info on wiki: https://github.com/FujiNetWIFI/fujinet-platformio/wiki

Thank you for feedback! ?

Hi, I put together bundle with couple of bits: launcher utility, fujinet-pc, netsio hub, and custom device file - all necessary pieces to connect emulated Atari (Altirra) with FujiNet. If interested, Fujinet-PC launcher repository is here: https://github.com/a8jan/fujinet-pc-launcher Instructions are here: https://github.com/a8jan/fujinet-pc-launcher/blob/master/Install.md and video instructions: FujiNet-PC-bundle-20220305.1_win-x64.zip It is not perfect. There is only Windows 64 bit version at this moment and plenty of room for improvements - you are welcome to help ? Jan

Updated Flasher for Ubuntu 21.10: FujiNet-Flasher-Ubuntu21.10.zip

Thanks for extensive testing and great feedback ? (just, how can I download all the log files in one shot?) I'm glad the issue was addressed. Thank you @HiassofT for help! I changed this already in fujinet-pc branch, this will appear with next push on github, but there will be more changes. That's the reason you had to change cmake in this fix branch. So next time it will be there That's weird. Hardware FujiNet is expecting to find a WiFi. On FujiNet-PC "fake" WiFi is presented. Just select it and enter any password (empty is ok). Once selected this is saved in fnconfig.ini and you shouldn't be asked to select/connect anymore. Could you please check fnconfig.ini file? There should be section like this: [WiFi] SSID=Dummy Cafe passphrase= another wip small change is to ship FN-PC with pre-populated fnconfig.ini, with wifi and some host slots already filled in. This should make first steps less confusing. (I will miss "Welcome to #FujiNet!" first time screen ) not by this, this is used to build fujinet-pc, I/O sound is turned off by CONFIG loader: https://github.com/a8jan/fujinet-config-loader I think I can add something like pressing Shift key at start of boot would keep SIO sound enabled, for troubleshooting and be-be-beep fans -Jan

I pushed an updated code into github repo. Now the custom baud rate is setup via Linux IOCTL call (like in atariserver). @E474 you can try a build: # get the source code git clone https://github.com/FujiNetWIFI/fujinet-pc.git # switch branch cd fujinet-pc git checkout fix-custom-uart-speed # enter build directory cd build # prepare build cmake .. -DCMAKE_BUILD_TYPE:STRING=Debug # run build cmake --build .

Speed at Atari end is controlled by POKEY and used divisor - you are right, speed is fixed for given divisor (well, small diff PAL vs NTSC). On PC end, serial port must be configured to the same or close to the same speed as Atari side. This can be done in two ways depending on serial port / UART capabilities. Old UARTs in PCs allowed to switch only to some predefined "standard" speeds, like 9600, 19200, 38400, 57600, 115200. With newer hardware it is possible to control UART similar to Atari, base UART speed with custom divisor. Thus to match e.g. Atari serial port setup with POKEY divisor 8, on PC end one can use (a) standard speed 57600 or (b) with newer UART to setup "custom" speed better matching speed at Atari side, around 59400 in this case. That explains two options for some POKEY divisor values. With nowadays hardware it should not be problem to use (b) ... if properly programmed let me try to fix it

@HiassofT I used TIOCSSERIAL with B38400 as I was not able to get tios2 with BOTHER working. Now I see there were some bits missing. Time to try this approach again. Thanks for pointing the right direction! (and sharing the code) ? Jan

@E474 thank you for testing x3 speed! This confirmed the issue is with setting custom UART speed - the code for standard and custom speed differs. Now I know where to look at. The x6 speed never worked for me. I guess the reason is the difference between standard UART 115200 speed and the speed Atari expects at POKEY divisor 1 (111860) is too large to work. Custom UART speed is needed for divisor 1. I will remove 115200 from settings completely.

hmm, only the HSIO settings which worked on your RPi with FN-PC was "16: 38400 (x2)" which is "standard" UART speed... I have no RPi. With FN-PC could you please try another standard UART speed "8: 57600 (x3)" (not custom "8: 58Kb")? It looks the problem could be with some serial port device setting which is needed to make custom speeds working with RPI embeded UART. I will check the code from Matthias if I can get the idea. @HiassofT do you remember was any specific setting needed for RPi UART? Jan

It looks like the 52400bps does not work on. Whenever the speed is set to 52400 (pokey divisor 10) there are only errors received on FN-PC end. The result is bouncing speed between 19200 and 52400 with lot of checksum errors. @E474 is FN CONFIG loading fine with other pokey divisor values, e.g 8, 6, 0 ?

Starting new topic to follow the issue with HSIO at pokey divisor 10 on FN-PC and RPi.

@E474 I will take a look. Let's move to another thread for this topic.

for zx0 version - no difference in what it does, but how it get loaded (HSIO and inline zx0 decompression) yup, noticed some time ago, it's on the list Tested to boot with Atari+FujiNet@ESP and Atari+FujiNet-PC@Linux box - no success Test with Altirra+FujiNet-PC revealed... CUSTOMDEV: Disk STATUS CUSTOMDEV: Disk READ 1 CUSTOMDEV: Disk READ 4 CUSTOMDEV: Disk READ 5 CUSTOMDEV: NetSIO from Atari @ 52640 CUSTOMDEV: Disk READ 6 CUSTOMDEV: Disk READ 6 CUSTOMDEV: NetSIO to Atari @ 125000 CUSTOMDEV: Disk READ 6 CUSTOMDEV: Disk READ 6 CUSTOMDEV: NetSIO to Atari @ 19200 CUSTOMDEV: Disk READ 6 CUSTOMDEV: Disk READ 6 CUSTOMDEV: NetSIO to Atari @ 125000 ... @E474 that disk is trying to talk on fixed speed 52kb. In WebUI you can change the pokey divisor down to 10 (in HSIO settings) to match the speed.

autotnfs-zx0.atr sure ?

The Linux version in first post seems to work fine with Ubuntu 18.04 and 20.04. Ubuntu 21.10 has some issue with it (runs only with root user). So I made another Linux build on Ubuntu 21.10: FujiNet-Flasher-Ubuntu21.10.zip

https://github.com/FujiNetWIFI/fujinet-pc - UART hot fixed

@Pins, I believe you did all properly but I suspect the merge I did (last Tuesday) into repo introduced buggy behavior when serial port is used. Sorry for that. Let me fix it and I will send an update here about new code ready for build.

At the moment FujiNet PC on Windows can be run via a) Linux binary in WSL or b) work in progress Windows native port. For b) the priority is to get it working on 64-bits first. The answer is: most likely not, not yet. If anyone would like to experiment and/or to contribute, use "mingw" branch from repo https://github.com/FujiNetWIFI/fujinet-pc.git Check https://github.com/FujiNetWIFI/fujinet-pc/blob/mingw/Windows.md for instructions. Jan

Yes! Current netsio.atdevice works with 3.90 and 4.00-testNN (same custom device file). The things has changed slightly with Altirra 4.00 release. It stopped to work in 4.00 release due to small workaround for 3.90: @phaeron not sure, if I am doing something wrong ^^^ It looks like thread in 3.90 is created but not switched into, waiting for next switch. Thread.sleep() helped me to switch. But this is guarded now ? Any idea for better solution? @a8isa1 For quick fix you can edit the netsio.atdevice file and comment out "Thread.sleep(400)" on lines 265 and 271: If I will not find a better way, I will prepare netsio.atdevice in two versions, for 3.90 and for 4.00. Jan

Yes, FujiNet is correct. The code is prepared for both FujiNet-PC as well for the hardware FujiNet ? The firmware with this code has not been released yet. Coming soon ...

The windows port is most challenging one for me. Lack of programming experience in windows, many traps I enter. But I'm still learning and making progress slowly. ? Jan

Maybe you can connect other 2 PINs of your FTDI based adapter, COMMAND and PROCEED. Then you can use hi-speed SIO and you can play with FujiNet too ?

SIO communication looks OK, no issue there. How did you get there? Was the CONFIG working for some time to allow you to select the WiFi+password? Could you mount some known ATR disk image as D1: via web interface and then press "Option" on Atari to try to boot into it. If booted after pressing Option key the issue could be with setting up the display at CONFIG startup... interesting, no others reported this, AFAIK. Anyone with A800/48K can check and report? Jan