Jump to content

mozzwald

Members
  • Posts

    1,041
  • Joined

  • Last visited

Posts posted by mozzwald

  1. 20 hours ago, chevymad said:

    Well Wifi doesn't seem to be working. I was able to pair bluetooth with an older firmware last night. I'm also able to access and load from the SD card. So far I can't get it to find or connect to my network however. I'm done playing around with it tonight. I'll give it some thought and research, see if I'm missing something or it is. 

    Does it see any networks? If yes, then it may not like your router. Some routers that have the same ssid for 2.4G and 5G have been known to not work.

     

    I can't tell from the picture, does your WROVER module have the tiny IPEX antenna connector on it?

     

  2. 24 minutes ago, JagChris said:

    Are you sure? Because we got a dude here with a box full of them he's looking to unload.

    If one appeared on my doorstep, I wouldn't complain, but I don't have $500 to throw down on a console and gobs more for games

  3. 3 hours ago, cubanismo said:

    Would be nice if someone had time to prototype something and see how well the games deal with internet latency to see if it's worth it though.

    I just did less than 5 minutes of research and it appears the Jaglink is just a serial connection. This would be trivial to get started with FujiNet. All you really need to do is hookup the TX/RX/GND (optionally 5V) lines to an ESP32 and you're almost done. I assume the Jaguar uses 5V for logic levels which is absolutely fine and safe on the esp32. No need for level shifting, just hookup directly to the gpio pins. This is what we started with for the Lynx:

     

    image.thumb.jpeg.b6b1fb74e606e97effa4e3d4fa0473cc.jpeg

    A new bus/platform can be created in the code and tweaked for Jaguar, probably using Lynx a the basis. We can assist with that when you're ready, just hop onto the Discord server (or if you want to start a new thread here instead). Note, I don't have a Jaguar and no plans to get one so it's all on the Jaguar community to start this. We will help where we can.

     

     

    • Like 3
    • Thanks 2
  4. On 8/12/2022 at 10:18 AM, SoulBuster said:

    I ran the firmware program as administrator.  This is on a Nuc576+.

     

    I need suggestions on how to complete this.

     

    On 8/12/2022 at 10:24 AM, SoulBuster said:

    You know the funny thing is that my stand alone fujinet updated the first try.

    Perhaps the Prolific driver you were able to get installed still has some issues? I'm not sure if the NUC Fuji has it, but you could try holding button A then turn on the fuji and continue holding the button during the entire flash process.

  5. 9 hours ago, chevymad said:

    Started hooking up the wires tonight, and I'm wondering if all the wires on J1 need to be connected?

     

    7 hours ago, mytek said:

    Perhaps @mozzwald can answer that one.

    ALL the SIO signal lines are used so I recommend you hook them up to get full functionality. PROCEED & INTERRUPT are used for the network device, CLOCK lines are used for MIDIMaze, MOTOR for cassette emulation, AUDIO for SAM, and of course CMD & DATA are absolutely needed. I guess if you don't want a feature, you can leave it off, but you may as well hook em up now before you close it up ;) 

    • Like 2
    • Thanks 1
  6. 30 minutes ago, x=usr(1536) said:

    Well...  I found that @mozzwald solved this problem some time ago :-D

     

    https://gist.github.com/mozzwald/0151050835d2f3f92c8ac824e904ae28

     

    That version (from what I can tell from briefly running it against my TNFS server) handles spaces in file/directory names just fine.

     

    There's also a second option: the PHP-TNFS gateway on cacaculopedopis.net (giggle), which allows for bi-directional transfer to preset or user-entered TNFS servers.

     

    Given that we've got a python and a web-based client ready to go, it seems like the only things that need to be agreed upon are where to upload to, and how to sync between different TNFS servers if that's something we want to do.

    The python and fuse client were updated back in march and I'm not sure if it has my changes in it or not. https://github.com/FujiNetWIFI/spectranet-tnfs-fuse

     

    The fuse driver could be used to mount a tnfs server and copy files as if it were a local disk. I've been keeping disks updated from @bocianu with a shell script that downloads the image and compares my file to his and updates if needed. This isn't ideal, but it works for now ;)

     

    I'd be happy to host files on fujinet.online if you want that to be 'the place'. All the files are also available directly for web download from https://fujinet.online/tnfs-data. I should change that to just /tnfs which would be easier and more memorable.

    • Like 2
  7. 5 hours ago, tsom said:

    Success!!

     

    That firmware seems to have done the trick. Rebooted several times before and after adding the WiFi info, and after inserting my SD card! This was on the new device, I’m going to flash my v1.0 and see but I have hope!

     

    thanks!!

    That's great! I'll push the change to the repo and it will be in the next update

    • Like 3
  8. 1 minute ago, tsom said:

    I believe that it has to do with connecting to the WiFi that is causing the delay in booting.

    I was able to move the wifi connect out of the regular setup and run it after the SIO service has started. This shaved 100-150ms off the boot time for me. Here is a test build you can try by running Fujinet Flasher from the command line. Let me know if it works

    FujiNet-Flasher /path/to/fujinet-ATARI-0.5.slow-boot-fix.zip

    fujinet-ATARI-0.5.slow-boot-fix.zip

    • Like 1
  9. 6 hours ago, billyc said:

     

    So, back to my question (!) -- I'm guessing this is just not possible, and I'll find a non-FujiNet way to solve this problem...

     

    I'm not up to speed on using Atariwriter. Does it require your data disk as drive 1 only? You could make a backup of your real disks to ATR files on the FujiNet SD card. Then in FujiNet config, put Atariwriter XEX in slot 1 and your new disk image in slot 2. Boot. When you need your data disk in drive 1, press button A on fujinet to swap disks.

     

    You might also be able to keep the 1050 as drive 1, but turn it off. Mount the Atariwriter XEX and boot. When it's finished loading Atariwriter, turn off FujiNet and turn the disk drive on.

     

    I could be way off here, but it's something to try :)

     

  10. 4 hours ago, tsom said:

    I'm still seeing the issue on my 130xe and my FujiNet's (v1.0 and v1.3).

     

    4 hours ago, tsom said:

    I tried my 800XL, and it does the same thing.

    Are you using the same power supply when testing both machines?

     

    What is the SIO voltage reported in the webui when powered by SIO only and when external USB power is applied?

  11. 9 hours ago, 8bit-Dude said:

    Hi Mozz! Are you still looking into this?

    I have been mulling something along the same lines myself for a while, I would be interested to bounce ideas together.

    We've made some progress. It works, with some lag / latency.

     

     

     

    I finally have a Lynx with working screen and we played a nice long round of Rampart the other day until Thom's batteries died :D Had a blast, and I kicked his ass :lol:

    • Like 2
  12. A new firmware update is available from https://fujinet.online/download

    "version": "0.5.fd038d41",
    "version_date": "2022-06-05 01:37:38",
    "build_date": "2022-06-08 18:27:12",
    "description": "Fix HTTP auth bug, add UDPStream webui stop button",
    "git_commit": "fd038d41",
    "url": "https://fujinet.online/firmware/releases_atari/fujinet-ATARI-0.5.fd038d41.zip",
    "sha256": "c280c03dc92765942432f80a369f34601e999970925dbc3970f40544b28941a7"

     

    • Fix HTTP auth bug. Thanks to @bocianu for finding it and @apc for the fix
    • Add STOP button for UDPStream mode webui
    • Correct/matching firmware version numbers this time, sorry!

    747115232_Screenshotfrom2022-06-0818-52-59.thumb.png.2484421e1dcea1a7dafdec3eba92ed19.png

     

    Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.

    • Like 2
    • Thanks 2
  13. 1 hour ago, Tron04 said:

    Hi, I wanted to flash the latest firmware 0.5.b28073ee from 2022-05-31 02:48:41

     

    Interesting enough after flashing my Fujinet reports in the boot log:

    FujiNet 0.5.16670e91 2022-05-31 01:44:54 Started @ 4

     

    Any explanation for this? Seems also like a version from 31. May, but  built a bit earlier?

    I am using the Winx64 FujinetFlasher on Windows 10.

     

    Sorry, it's my fault. I put the wrong hash in the release zip file.

    • Thanks 1
  14. A new firmware update is available from https://fujinet.online/download

     

    	"version": "0.5.b28073ee",
    	"version_date": "2022-05-31 02:48:41",
    	"build_date": "2022-05-31 02:48:41",
    	"description": "Fix JSON bug, replace MIDIMaze mode with UDPStream mode",
    	"git_commit": "b28073ee",
    • Fix bug in JSON parser
    • Replace MIDIMaze mode with new UDP Stream mode

    The new UDP Stream mode expands the functionality of MIDIMaze mode. You can now open a UDP Port of your choosing to any hostname or ip address. This can be enabled via the web ui or from the new $F0 SIO Command for the Fuji Device $70. When this mode is enabled all serial data is sent out to the host/port via UDP packets and all received UDP packets are pushed back to the Atari. Any SIO command (triggered by the COMMAND line) will automatically turn this mode off and FujiNet will return to normal SIO processing. A good use case for this is fast action games. The idea for this change came from some experiments @tschak909 and I did over the weekend with the Atari Lynx where we successfully played a game of Rampart from roughly 2000 miles apart. Can't wait to see what you game devs can come up with for this.

     

    MIDIMaze mode will still work on port 5004 only. RTP MIDI typically uses port 5004 so I've reserved that port for MIDIMaze. MIDIMaze requires the CLK_IN line to be set so the SIO baud rate can be changed for MIDI data. When selecting a host and port 5004, this is automatically done on the FujiNet.

     

    896808357_Screenshotfrom2022-05-3017-45-41.thumb.png.9f1a0531d5c1c2918530c702d85942ee.png

    Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.

    • Like 6
  15. For those who use SIO2BT Bluetooth enabled builds of FujiNet firmware, there is a new update available that brings in all the latest changes. When running the fujinet-flasher, it's the second firmware in the list: 0.5.24fbef77-SIO2BT

     

    Please do not respond to this thread. If you have an issue, start a new post in the FujiNet subforum, open an issue on the github tracker or ask for assistance in Discord chat.

    • Thanks 1
×
×
  • Create New...