mozzwald

It's still work in progress and requires new firmware which is not yet released (but you can build from source if you like)

I've not used Subcart before but there shouldn't be any issues. Just remember that when FujiNet powers on it will have it's config disk in drive 1 (unless you disable this from the Fujinet web interface). You don't want both devices configured with the same drives, ie, don't put a disk in Drive 2 on both at the same time or you'll have problems

U-Boot is the bootloader and I suspect the button puts the device into FEL mode. Would be cool if someone could hookup UART serial and grab a log of the boot process. If kernel output is sent to the serial port, it could provide some useful info.

Parts arriving this week to make some more. If you get on the email list you'll get notified when they're available. I'm using an 800XL with 512k SRAM upgrade and FujiNet, so nothing excessive here. Of the 50 shipped so far, have not heard from anyone blowing the fuse yet.

indeed, but I have seen some junky meters test leads show ohms. best to touch the leads together and find "0" before testing the components

You should get 5 (or slightly more) Volts out from the USB power brick with no load. Perhaps your power bricks are "smart" and only do PD or IQ charging. Those features require "smarts" on the receiving end to negotiate the voltage and current. Or maybe the cable is not good. Check the resistance from USB to DIN ends for the power and ground wires as mentioned above Anything above a few ohms is not good.

https://github.com/FujiNetWIFI/fujinet-high-scores

I see a UART port on the PCB and some other interesting pins (UBOOT, RECOVER) Whose gunna dump the NAND?

@Goochman you can follow the instructions above or power the FujiNet with a USB cable so that it is ready when the Atari boots. There are changes in the code to make Fujinet bootup faster but they are not available in a firmware update yet

if your network doesn't support mDNS or it's not working, you can always put the IP address of your TNFS server instead of a name

There's a section on the wiki about capturing debug output https://github.com/FujiNetWIFI/fujinet-firmware/wiki/FujiNet-Flasher#capturing-serial-debug-output This would help us try to figure out what the issue is on the latest firmware

perhaps. I was thinking a separate printing server app to run on pc. TNFS doesn't really have anything to do with printing

just an idea, maybe we could add a "server to ping" field in webui for the printer. when a print is done, it sends a message to a local server specified that file is ready. server grabs the pdf and prints it. someone would need to make the server side that does the printing

Are you running the latest firmware version v1.2.0? I see the server is using chunked transfers which should have been fixed in the firmware last August.

Click on a Host Slot to browse the files in the host, then select a file and select the slot... just like in CONFIG