JGroth Posted July 27, 2020 Share Posted July 27, 2020 I'm trying to get #fujinet working, so I've built a prototype according to the schematics found at github (https://github.com/FujiNetWIFI/fujinet-hardware/blob/master/Prototype-Schematics/fujinet-schematic_20200229_esp32-devkitc.jpg). The board I'm using is a ESP32-DEVKITC-VB Dev.kit Combo ESP32-WROVER-B ESPRESSIF (https://www.amazon.co.uk/gp/product/B07L9JM29R/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1). So I choose fujinet-v1-4mb and build, upload file system image and upload. The monitor shows this: > Executing task in folder fujinet-platformio: platformio device monitor --environment fujinet-v1-4mb < --- Available filters and text transformations: colorize, debug, default, direct, esp32_exception_decoder, hexlify, log2file, nocontrol, printable, send_on_enter, time --- More details at http://bit.ly/pio-monitor-filters --- Miniterm on /dev/ttyUSB0 921600,8,N,1 --- --- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- 19:44:02.017 > 19:44:02.017 > --~--~--~-- 19:44:02.017 > FujiNet 0.1.547ff5cf 2020-07-26 16:55:01 Started @ 4 19:44:02.018 > Starting heap: 4133392 19:44:02.018 > PsramSize 3932108 19:44:02.018 > himem phys 4456448 19:44:02.018 > himem free 4456448 19:44:02.020 > himem reserved 262144 19:44:02.020 > SPIFFS mounted. 19:44:02.104 > SD mount failed with code #263, "ESP_ERR_TIMEOUT" 19:44:02.117 > fnConfig::load 19:44:02.119 > fnConfig deleting configuration file and skipping SD check 19:44:02.119 > WIFI_EVENT_STA_START 19:44:02.245 > disk MOUNT 19:44:02.269 > mounted ATR to Disk: 19:44:02.269 > num_para: 5760 19:44:02.269 > sectorSize: 128 19:44:02.269 > num_sectors: 720 19:44:02.269 > Creating a default printer using FS_SPIFFS storage and type 1 19:44:02.270 > SIO SETUP 19:44:02.270 > Available heap: 4057020 19:44:02.270 > Setup complete @ 257 (253ms) 19:44:02.272 > BOOT_KEY: LONG PRESS 19:44:03.446 > OTHER_KEY: LONG PRESS 19:44:03.446 > Shutdown handler called 19:44:03.447 > disk UNMOUNT 19:44:03.447 > disk UNMOUNT 19:44:03.447 > disk UNMOUNT 19:44:03.447 > disk UNMOUNT 19:44:03.447 > disk UNMOUNT 19:44:03.448 > disk UNMOUNT 19:44:03.448 > disk UNMOUNT 19:44:03.448 > disk UNMOUNT 19:44:03.448 > WIFI_EVENT_STA_STOP 19:44:03.448 > �������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� 19:44:04.506 > 19:44:04.506 > --~--~--~-- 19:44:04.506 > FujiNet 0.1.547ff5cf 2020-07-26 16:55:01 Started @ 4 19:44:04.507 > Starting heap: 4133392 19:44:04.507 > PsramSize 3932108 19:44:04.507 > himem phys 4456448 19:44:04.507 > himem free 4456448 19:44:04.509 > himem reserved 262144 19:44:04.509 > SPIFFS mounted. 19:44:04.593 > SD mount failed with code #263, "ESP_ERR_TIMEOUT" 19:44:04.606 > fnConfig::load 19:44:04.608 > fnConfig deleting configuration file and skipping SD check 19:44:04.608 > WIFI_EVENT_STA_START 19:44:04.734 > disk MOUNT 19:44:04.758 > mounted ATR to Disk: 19:44:04.758 > num_para: 5760 19:44:04.758 > sectorSize: 128 19:44:04.758 > num_sectors: 720 19:44:04.758 > Creating a default printer using FS_SPIFFS storage and type 1 19:44:04.759 > SIO SETUP 19:44:04.759 > Available heap: 4057020 19:44:04.759 > Setup complete @ 258 (254ms) 19:44:04.761 > BOOT_KEY: LONG PRESS 19:44:05.935 > OTHER_KEY: LONG PRESS 19:44:05.935 > Shutdown handler called 19:44:05.935 > disk UNMOUNT 19:44:05.935 > disk UNMOUNT 19:44:05.935 > disk UNMOUNT 19:44:05.935 > disk UNMOUNT 19:44:05.935 > disk UNMOUNT 19:44:05.937 > disk UNMOUNT 19:44:05.937 > disk UNMOUNT 19:44:05.937 > disk UNMOUNT 19:44:05.937 > WIFI_EVENT_STA_STOP 19:44:05.937 > �������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� This goes into an endless loop. The card doesn't have an SD card so I can understand that failure but its skipping that step so that should be OK. The thing is that I haven't connected it to the Atari yet. But there is no change if I have it connected to the Atari, still an endless loop of boot failures. Has anyone else seen this and even better know of a solution? Regards, JGroth Quote Link to comment Share on other sites More sharing options...
tschak909 Posted July 27, 2020 Share Posted July 27, 2020 Looks like you may have wired the pins for the buttons to ground and therefore they're always being pressed? -Thom Quote Link to comment Share on other sites More sharing options...
JGroth Posted July 27, 2020 Author Share Posted July 27, 2020 But the card isn't connected to anything but the USB port to my PC so how can that be? JGroth Quote Link to comment Share on other sites More sharing options...
jamm Posted July 27, 2020 Share Posted July 27, 2020 1 hour ago, JGroth said: But the card isn't connected to anything but the USB port to my PC so how can that be? JGroth 19:44:02.272 > BOOT_KEY: LONG PRESS 19:44:03.446 > OTHER_KEY: LONG PRESS @mozzwald can better explain why the hardware behaves this way, but it's the fact that you don't have the hardware for the buttons wired up. The assumption was that anyone with a WROVER board would have those buttons wired up, so there's no provision in the build for your setup. The WROOM board configuration (fujinet-wroom) does turn off the checks for those buttons, so it should work on your setup. Change your settings to use the fujinet-wroom and try it out? Quote Link to comment Share on other sites More sharing options...
mozzwald Posted July 28, 2020 Share Posted July 28, 2020 You can fix this behavior by adding a 10k pull up resistor from IO34 to 3.3V and optionally a momentary button to ground (see https://github.com/FujiNetWIFI/fujinet-hardware/blob/master/FN32ROV-1.0/fujinet-schematic_20200601_FN32ROV-1.0.jpg). The code expects this pin to be high, instead you have it floating so it thinks the button is pressed. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.