Jump to content
tschak909

#FujiNet - a WIP SIO Network Adapter for the Atari 8-bit

Recommended Posts

How bizarre - now it's working fine. I dunno what was wrong before. I swear I tried the very same thing that's working now - booting from a disk mounted in the Incognito SIDE Loader, load a BASIC program and simple LIST "P: ... even with the HTML ATASCII printer selected I was getting a PDF output. Now I get the (expected?) HTML page with properly rendered inverse-video and ATASCII graphic symbols.

 

#PEBKAC 

 

image.thumb.png.12213880c88b0cc5cc5523bd32e4564a.png

Share this post


Link to post
Share on other sites

Seeing properly printed ATASCII the first time, made me tear up a little.

 

I had been wanting that BITD so fucking bad.

 

-Thom

  • Like 2

Share this post


Link to post
Share on other sites
15 minutes ago, tschak909 said:

Seeing properly printed ATASCII the first time, made me tear up a little.

 

I had been wanting that BITD so fucking bad.

 

-Thom

Mat*Rat had a util called CUSTOM.BAS that would print ATASCII to a printer. The disk had 2 fonts. Came in handy more than a few times.

custom.atr

  • Like 4

Share this post


Link to post
Share on other sites

The G: driver from ANALOG did the same; LIST G: would print using the current default font.  Supported Gr 8 and 7.5 dumps, too.

  • Like 2

Share this post


Link to post
Share on other sites
On 7/29/2020 at 9:57 AM, mozzwald said:

I just updated the flash tool (https://fujinet.online/download/) so that you can view the serial debug output from FujiNet over USB. This is useful for those who do not want or need to install PlatformIO/vscode but still be able to report problems and supply debug output. 

Is this flash tool only for the current wrover boards, and not for older wroom boards?

Share this post


Link to post
Share on other sites

@mozzwald may want to chime in, but, I believe the current updater always pulls the 16 megabyte flash image, so it would only be compatible with the production WROVER boards.

 

The updater source is written in python and is available for anyone to hack in support for other flash sizes, if we don't get to adding support for it.

 

https://github.com/FujiNetWIFI/fujinet-flasher

 

-Thom

Edited by tschak909
added flasher repo link.
  • Like 1

Share this post


Link to post
Share on other sites
30 minutes ago, Fierodoug5 said:

Is this flash tool only for the current wrover boards, and not for older wroom boards?

 

Just now, tschak909 said:

@mozzwald may want to chime in, but, I believe the current updater always pulls the 16 megabyte flash image, so it would only be compatible with the production WROVER boards.

 

The updater source is written in python and is available for anyone to hack in support for other flash sizes, if we don't get to adding support for it.

 

-Thom

The flash tool is setup to only pull firmware from fujinet.online which is built for the 16MB WROVER boards. As @tschak909 said, it could be modified to do other boards.

  • Like 1

Share this post


Link to post
Share on other sites

As @DrVenkman brought up a good point of not knowing what type of disk a disk image might be. I will be doing two things:

 

* Adding Device slot info to CONFIG (pressing ENTER on device slot will bring up an info screen with geometry)

* Creating a tool called FINFO in fnc-tools to display this information outside of CONFIG (done)

 

The latter has been done and is now part of fnc-tools on atari-apps.

 

image.thumb.png.9f6b30845b64e93053d355438f7ec0e2.png

  • Like 4

Share this post


Link to post
Share on other sites

A longer-term thing to consider, perhaps, might be to allow CONFIG to basically request a direct file-transfer copy of a remote ATR - or any file maybe? - from a Host to local SD card storage. In other words, rather than creating a new local ATR, mounting an original .ATR as a source and then creating a duplicate or sector copy into the new ATR as a destination, you could simply have the FujiNet device sidestep that and retrieve a copy of the target Host file and save it locally on the SD card. 

  • Like 1

Share this post


Link to post
Share on other sites

I have been following along and finally decided to try and breadboard one of these.  

 

I have this module that looks like it should work and please correct me if I an wrong!

https://www.makershop.de/en/plattformen/d1-mini/wemos-lolin-d32-pro/

 

I just flashed it with the flashing tool at:

https://fujinet.online/firmware-dl/

 

That all went fine but now the module is in a boot loop.

[10:46:01]rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
[10:46:01]configsip: 0, SPIWP:0xee
[10:46:01]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[10:46:01]mode:DIO, clock div:2
[10:46:01]load:0x3fff0018,len:4
[10:46:01]load:0x3fff001c,len:5176
[10:46:01]load:0x40078000,len:15912
[10:46:01]load:0x40080400,len:4804
[10:46:01]entry 0x400806a0

 

Anyone have any ideas or suggestions?

 

Thanks

   David

 

Share this post


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

I have been following along and finally decided to try and breadboard one of these.  

 

I have this module that looks like it should work and please correct me if I an wrong!

https://www.makershop.de/en/plattformen/d1-mini/wemos-lolin-d32-pro/

 

I just flashed it with the flashing tool at:

https://fujinet.online/firmware-dl/

 

That all went fine but now the module is in a boot loop.

[10:46:01]rst:0xc (SW_CPU_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
[10:46:01]configsip: 0, SPIWP:0xee
[10:46:01]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[10:46:01]mode:DIO, clock div:2
[10:46:01]load:0x3fff0018,len:4
[10:46:01]load:0x3fff001c,len:5176
[10:46:01]load:0x40078000,len:15912
[10:46:01]load:0x40080400,len:4804
[10:46:01]entry 0x400806a0

 

Anyone have any ideas or suggestions?

 

Thanks

   David

 

Nice find on that board. I've yet to see a devkitc style board with the 16MB WROVER module.

 

Can you post the output from flashing the board? Also, after it finishes flashing, click the Serial Debug Output button and see if there are any messages from our code. The output you pasted is from the bootloader.

 

Did you wire up all the buttons per the schematic? Which schematic did you follow?

Share this post


Link to post
Share on other sites
24 minutes ago, mozzwald said:

Nice find on that board. I've yet to see a devkitc style board with the 16MB WROVER module.

 

Can you post the output from flashing the board? Also, after it finishes flashing, click the Serial Debug Output button and see if there are any messages from our code. The output you pasted is from the bootloader.

 

Did you wire up all the buttons per the schematic? Which schematic did you follow?

Thanks on the board.  Glad it will work for this project!

 

Ok.  I'll try to get a capture of the flash.  I noticed while flashing some stuff was getting over written.  So it may take a few tries to get the parts you need.

 

I haven't wired up the buttons or anything yet.  First wanted to make sure the board was going to work.  What would be the best schematic to use for this one?


David

 

Share this post


Link to post
Share on other sites
13 minutes ago, djones60 said:

I haven't wired up the buttons or anything yet.  First wanted to make sure the board was going to work.  What would be the best schematic to use for this one?

It won't boot properly without the buttons wired up. The "Other"/"B" button when held down forces a clean reboot and subsequent configuration wipe so you'll get stuck in a boot loop. Without the required pull up resistor the button is always "pressed". Serial debug output would confirm this.

 

The latest and greatest schematic is https://github.com/FujiNetWIFI/fujinet-hardware/blob/master/FN32ROV-1.0/fujinet-schematic_20200601_FN32ROV-1.0.jpg. You won't need everything from it since you have the devkit style board. If you have anymore hardware/schematic questions please post them in the hardware thread:

 

Edited by mozzwald
add please so I don't sound like a meanie :)

Share this post


Link to post
Share on other sites

I've been toying with the idea of getting this wrover dev board, they are on AliExpress. Was hoping to get a real fujinet board, then I missed the first 50 list. So maybe I still will. Can't seem to find this board from a American seller.

  • Like 1

Share this post


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

It won't boot properly without the buttons wired up. The "Other"/"B" button when held down forces a clean reboot and subsequent configuration wipe so you'll get stuck in a boot loop. Without the required pull up resistor the button is always "pressed". Serial debug output would confirm this.

 

The latest and greatest schematic is https://github.com/FujiNetWIFI/fujinet-hardware/blob/master/FN32ROV-1.0/fujinet-schematic_20200601_FN32ROV-1.0.jpg. You won't need everything from it since you have the devkit style board. If you have anymore hardware/schematic questions please post them in the hardware thread:

 

Thanks.  That would explain my problem.  I'll wire it up tonight or tomorrow and see what happens then.  I seen the hardware forum and wasn't sure it my question about this should there or here since I was doing my own.  I'll go there after this post.

 

Here is what I get on the serial debug output.

[14:17:04]Baudrate already at 19200 - nothing to do
[14:17:04]OTHER_KEY: LONG PRESS
[14:17:04]Shutdown handler called
[14:17:04]disk UNMOUNT
[14:17:04]disk UNMOUNT
[14:17:04]disk UNMOUNT
[14:17:04]disk UNMOUNT
[14:17:04]disk UNMOUNT
[14:17:04]disk UNMOUNT
[14:17:04]disk UNMOUNT
[14:17:04]disk UNMOUNT
[14:17:05][14:17:05]
[14:17:05]--~--~--~--
[14:17:05]FujiNet 0.1.5f1b883f 2020-07-30 03:48:04 Started @ 5
[14:17:05]Starting heap: 4095772
[14:17:05]PsramSize 3932108
[14:17:05]himem phys 4456448
[14:17:05]himem free 4456448
[14:17:05]himem reserved 262144
[14:17:05]SPIFFS mounted.
[14:17:05]SD mount failed with code #263, "ESP_ERR_TIMEOUT"
[14:17:05]fnConfig::load
[14:17:05]fnConfig deleting configuration file and skipping SD check
[14:17:05]WIFI_EVENT_STA_START
[14:17:05]disk MOUNT
[14:17:05]mounted ATR: paragraphs=5760, sect_size=128, sect_count=720
[14:17:05]Creating a default printer using FS_SPIFFS storage and type 1
[14:17:05]SIO SETUP
[14:17:05]Available heap: 4048104
[14:17:05]Setup complete @ 379 (374ms)
[14:17:06]BOOT_KEY: LONG PRESS
[14:17:06]Starting SIO2BT
[14:17:07]Baudrate already at 19200 - nothing to do
[14:17:07]OTHER_KEY: LONG PRESS
[14:17:07]Shutdown handler called
[14:17:07]disk UNMOUNT
[14:17:07]disk UNMOUNT
[14:17:07]disk UNMOUNT
[14:17:07]disk UNMOUNT
[14:17:07]disk UNMOUNT
[14:17:07]disk UNMOUNT
[14:17:07]disk UNMOUNT
[14:17:07]disk UNMOUNT
[14:17:08][14:17:08]

Edited by djones60
  • Like 2

Share this post


Link to post
Share on other sites

Need some help updating a older Esp32 Wroom board. I have not been able to update since last month when The github changed.

I am following the new github wiki for PlatformIO bulid

When I try to build, i get this error

 

src\main.cpp:10:10:fatal error: fnsystem.h:no such file or directory

#include"fnsystem.h" 

compilation failed

[.pio\build\fujinet-wroom\esp-idf\src\main.cpp.o] error 1

 

Thanx

Doug

Share this post


Link to post
Share on other sites
8 minutes ago, Fierodoug5 said:

Need some help updating a older Esp32 Wroom board. I have not been able to update since last month when The github changed.

I am following the new github wiki for PlatformIO bulid

When I try to build, i get this error

 

src\main.cpp:10:10:fatal error: fnsystem.h:no such file or directory

#include"fnsystem.h" 

compilation failed

[.pio\build\fujinet-wroom\esp-idf\src\main.cpp.o] error 1

 

Thanx

Doug

What platform are you building on (Windows, Linux, etc)?

 

I've had this problem before on Linux before and had to just start over. Delete the old repo, clone again, copy and edit platformio-sample.ini, then open the folder with vscode.

Share this post


Link to post
Share on other sites
10 minutes ago, Fierodoug5 said:

deleted the repo and cloned again(3 more times) 

same error

That's very strange behavior.  It's hard to imagine what would cause that after deleting and re-cloning the repo.  I assume you're deleting the entire folder with the repo in it so that it takes the hidden ".pio" directory with it...

 

Can you post your platformio.ini file here?  It shouldn't have anything to do with it, but I'm curious.

 

Share this post


Link to post
Share on other sites

;FujiNet PlatformIO Project Configuration File
;
;   Build options: build flags, source filter
;   Upload options: custom upload port, speed and extra flags
;   Library options: dependencies, extra library storages
;   Advanced options: extra scripting
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html

[platformio]
description = FujiNet Atari to ESP32 WiFi Multifunction Firmware
; Change this to target the device you use from the list of [env:xxx] sections below
default_envs = fujinet-wroom

[env]
; Common settings for all enivornments
platform = espressif32
framework = espidf
extra_scripts = pre:build_version.py
lib_ldf_mode = deep+
upload_port = COM10 ; Windows
;upload_port = /dev/ttyUSB0 ; Linux
upload_speed = 921600
monitor_port = COM10 ; Windows
;monitor_port = /dev/ttyUSB0 ; Linux
monitor_speed = 921600
monitor_filters = time

; ESP32 WROVER (16MB Flash, 8MB PSRAM) based FujiNet
[env:fujinet-v1]
board = fujinet-v1
build_type = debug
build_flags =
    ;-D JTAG
    -D DEBUG_SPEED=921600
    -D BLUETOOTH_SUPPORT
    ;-D FN_HISPEED_INDEX=0
    ;-D VERBOSE_SIO
    ;-D VERBOSE_TNFS
    ;-D VERBOSE_DISK

; ESP32 WROOM (4MB Flash, NO PSRAM) based FujiNet
[env:fujinet-wroom]
board = fujinet-wroom
build_type = debug
build_flags =
    -D DEBUG_SPEED=921600
    ;-D FN_HISPEED_INDEX=0
    ;-D VERBOSE_SIO
    ;-D VERBOSE_TNFS
    ;-D VERBOSE_DISK

; ESP32 WROVER (4MB Flash, 8MB PSRAM) based FujiNet
[env:fujinet-v1-4mb]
board = fujinet-v1-4mb
build_type = debug
build_flags =
    -D DEBUG_SPEED=921600
    ;-D FN_HISPEED_INDEX=0
    ;-D VERBOSE_SIO
    ;-D VERBOSE_TNFS
    ;-D VERBOSE_DISK

Share this post


Link to post
Share on other sites

Also please check to make sure all your platformio components are up to date.  Here's a screenshot of the button you can hit and recent output:

 

 

pio-update.png

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.

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...