SD Card not working

[mozzwald]

@8BIT 1337 If you've tried multiple SD cards and have them properly formatted, you might have a hardware issue. Contact your vendor

[NISMOPC]

Bringing up old thread - 576+ NUC with Fujinet Cartridge

Same errors as above posts. Same random working/non-working SD card.

I reflowed the SD card socket and it began to work again, but after a few days, it stopped again. I purchased new replacement sockets and they should arrive Friday. Already removed the old socket from board. Hoping this is the only issue. 

Unable to use SIO for other devices as well. If even just the SIO adapter is plugged in - no other devices - NUC will not even boot up. Turns on then cycles back and turns off. If I remove the SIO adapter, NUC boots to FUJI, but will not recognize SD card.

 

If this does not work, I need to reach out to The Brewing Academy to see what my options are.

 

EDIT: Did some more testing. If I turn OFF the Fujinet and use my AVGCart with AVGSIO connected, I can use the SIO adapter and any device connected to it.

 

So, it appears to possibly be an issue with the NUC Fujinet/Cartridge add-on board. 😒

Edited December 27, 2022 by NISMOPC

[mozzwald]

58 minutes ago, NISMOPC said:

So, it appears to possibly be an issue with the NUC Fujinet/Cartridge add-on board. 😒

Since you've already determined bad soldering on the sd cart slot, I recommend you go over the entire fujinet board with magnification and look for more bad solder joints.

[NISMOPC]

3 hours ago, mozzwald said:

Since you've already determined bad soldering on the sd cart slot, I recommend you go over the entire fujinet board with magnification and look for more bad solder joints.

Definitely will check solder joints. Want to see if SD Card socket will read once I replace, then I will trouble shoot the rest. 

[Stefan Both]

My Fujinet is running fine.

( Best all in one Hardware ever)

My main SD Card is a 4GB (Speed10x) Fat32.

NEVER had any prolems.

By opportunity I got 4 really cheap SD Cards

2GB. Formatted 'em Fat32 of course.

None of them work with the Fujinet.

(However all work fine with SD2IEC for example).

Wether I have worries regarding that, nor do I have a solution for the problems mentioned by others.

What I assume is, some SD cards just won't work. Some observations point to a minimum necessary speed. But ... I don't mind.

Just wanted to let you know, maybe it helps.

 

Stefan 

Edited December 28, 2022 by Stefan Both

[NISMOPC]

@mytek Was curious on the SIO switching between FUJINET being ON vs. OFF. As I posted above, whenever I attached the SIO adapter (with or without a device) to the FUJINET and turn it on, the NUC cycles and turns off. I already found an issue with a faulty SD socket and will be replacing that tomorrow. (Already removed the surface mount socket), but still have the same issue with the SIO. If I use the SIO adapter and any device with the FUJINET turned off, the NUC works fine, but anytime I attempt to use the SIO and adapter with or without devices and FUJINET is on, the system shuts down.

 

I understand the esp32 chip in the fujinet is severed from the SIO bus when fujinet is turned off. All SIO lines are always passed through from the plug to receptacle so anything else can still work even though the fujinet is turned off. So that part appears to be working fine, but it appears that this is not working properly when FUJINET is turned on. Just looking for some direction on what circuit(s) I should be focusing on. I have looked over the soldering joints and there appears to be no loose/missing joints.

 

I downloaded schematics and was reviewing them. There appears to be two versions of the schematics. Version 1.5 and 1.6 and found one main difference between them. Version 1.6 has the card detect pin 10 connected to pin 23 on the esp32 chip, but version 1.5 has that same pin conected to pin 14 of the ESP32. What is the difference? Does that even matter and would it cause these issues?
 

[+mytek]

@NISMOPC I seem to recall having discovered an issue with the system sometimes appearing to reset if I plug something directly into the Dsub15 SIO jack, which I think relates to a pin or two getting shorted by the Dsub15's case when first locating the plug in the jack (best to connect or disconnect with power off). Also the same thing can happen due to static electricity if you touch one of the connectors, such as the joy stick ports. The 576NUC+ has marginal filtering and/or protection for this built in, with a stock Atari being far more protected from ESD.

 

I've never experienced the symptoms you mentioned, not to say that they don't exist. I will need to investigate what you are seeing using one of my systems to see if I can duplicate your symptoms, and then diagnose what's causing it.

 

39 minutes ago, NISMOPC said:

I downloaded schematics and was reviewing them. There appears to be two versions of the schematics. Version 1.5 and 1.6 and found one main difference between them. Version 1.6 has the card detect pin 10 connected to pin 23 on the esp32 chip, but version 1.5 has that same pin conected to pin 14 of the ESP32. What is the difference? Does that even matter and would it cause these issues?

This relates to a problem that was discovered when a certain ESP module got used for the build (not the one spec'ed in the BOM), where using that first pin assignment in V1.5 would interfere with doing updates of the firmware. This got changed to an alternate pin assignment in V1.6 that didn't share this same problem. This was done purely to future proof the design and it allow it to work seamlessly with the alternate ESP module. However the firmware can detect which pin is assigned and configure for whichever pin is being used for the SD card Detect function, so V1.5 is still viable and not compromised moving forward -- no need to upgrade to V1.6.

[NISMOPC]

@mytek OK, so I did some more testing. I checked all connections on both the SIO2DUB connector and the female D-SUB on board with one of my trustee multimeters. The grounds on the SIO D-SUB female connector had some intermittent non-grounding. I reflowed solder on them just to be sure they have full contact to ground.

Interesting find: I am able to boot into the FUJINET with the SIO2DSUB connected (with and without devices) successfully, but I have to hold in the SAFE RESET button in on back of FUJINET to do so. So far that is an OK work-around, but I would like to figure out why it has to be held in for the NUC to allow FUJINET to take over the SIO and allow pass-through at the same time. I also noticed noise (static) of varying degree through my speakers with FUJINET ON. I think this has been discussed before, but I thought I would mention that as well.

 

Continuing testing and will report back any new findings. Thanks for all your assistance on this!

 

EDIT

More findings: So, certain SIO devices work fine and some don't. So... I decided to go back to the basics. POWER. The power supply is the one that came with the unit. I decided to power the FUJINET via USB at the same time as NUC is being powered by the included power supply. Everything seems to work. Now I wonder if the power supply is not providing enough AMPS OR it's not truly 12V all the time. Will now place my focus on the power supply and do some more testing (possibly swap PSU's as well if I have another with proper connector or will make one). Hope this is getting to a resolve. It's all enjoyable tinkering but not always fun and games  

Edited December 29, 2022 by NISMOPC

[NISMOPC]

UPDATE:

 

Found a PSU from one of my old SeaGate external hard drives that puts out 12V @ 2AMPS. Swapped power supplies, removed the USB power to Fujinet and all seems good! Appears the cheap PSU that came with NUC is not sufficient or failing.
 

NUC PSU

SeaGate PSU

SUCCESS!!

Currently working 576+ NUC Fujinet w/CART + SIO2DSUB connected to P:R: Connection + WiModem32

I wanted to put some strain on the SIO to make sure everything was working. Would have no reason that I can think of to have this set-up since FUJINET does everything the WiModem32 does and more. Now to stack on some more devices on the chain and see if it keeps working.

 

All that is left to do is install new SD Socket tomorrow (estimated delivery) and put this thing back together!

[NISMOPC]

All better now. Got new 12V @ 5A power supply and installed new SD card socket.

 

I botched the pin 10 card detect on SD socket, but did not seem to impact it's use. Is that pin even needed??

 

[mozzwald]

1 hour ago, NISMOPC said:

I botched the pin 10 card detect on SD socket, but did not seem to impact it's use. Is that pin even needed??

It's not explicitly required. If card detect is working, FujiNet will reset when card is ejected or will mount the card automatically if inserted.

 

Glad you got it up and running

[SlagOMatic]

I'm having the same issue. Just bought my FujiNet about a week ago. I go into the FujiNet's SD card and it jumps to the wifi connection screen. I've tried three different SD cards, including two brand new SanDisk 32GB cards which work fine everywhere else. Running an 800XL with RAMBO 256 and Ultimate Atari Video v2, if it matters.

 

Spoiler

Using '/dev/cu.SLAB_USBtoUART' as serial port.
Using '460800' as baud rate.
Showing logs:
[18:13:15]
[18:13:15]
[18:13:15] --~--~--~--
[18:13:15] FujiNet 0.5.13741956 2023-01-30 22:44:10 Started @ 5
[18:13:15] Starting heap: 4365075
[18:13:15] Detected Hardware Version: 1.6.1 and up
[18:13:15] Safe Reset Button 😄 ENABLED
[18:13:15] SPIFFS mounted.
[18:13:16] E (3546) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
[18:13:16] E (3546) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
[18:13:16] SD mount failed with code #263, "ESP_ERR_TIMEOUT"
[18:13:16] fnConfig::load
[18:13:16] Load fnconfig.ini from spiffs
[18:13:16] fnConfig::load read 1009 bytes from config file
[18:13:16] SPIFFS Config Storage: Enabled
[18:13:16] fnConfig::load read 1009 bytes from SPIFFS config file
[18:13:16] disk UNMOUNT
[18:13:16] disk MOUNT
[18:13:16] ATR MOUNT
[18:13:16] mounted ATR: paragraphs=5760, sect_size=128, sect_count=720, disk_size=0
[18:13:16] Creating a default printer using FS_SPIFFS storage and type 12
[18:13:16] ModemSniffer::ModemSniffer(FS_SPIFFS)
[18:13:16] SIO SETUP
[18:13:16] Set HSIO baud from 0 to 67431 (index 6), alt=68209
[18:13:16] Available heap: 4345607
[18:13:16] Setup complete @ 1641 (1636ms)
[18:13:16] WiFiManager::start() complete
[18:13:16] WIFI_EVENT_STA_START
[18:13:16] WiFi connect attempt to SSID "(my ssid)"
[18:13:16] esp_wifi_connect returned 0
[18:13:16] WIFI_EVENT_STA_CONNECTED
[18:13:17] IP_EVENT_STA_GOT_IP
[18:13:17] Obtained IP address: 192.168.2.76
[18:13:17] SNTP client start
[18:13:17] Starting web server on port 80
[18:13:20] SNTP time sync event: Mon Feb 20, 18:13:20 2023 -0500

 

 

Edited February 20 by SlagOMatic

[tschak909]

49 minutes ago, SlagOMatic said:

I'm having the same issue. Just bought my FujiNet about a week ago. I go into the FujiNet's SD card and it jumps to the wifi connection screen. I've tried three different SD cards, including two brand new SanDisk 32GB cards which work fine everywhere else. Running an 800XL with RAMBO 256 and Ultimate Atari Video v2, if it matters.

 

  Hide contents

Using '/dev/cu.SLAB_USBtoUART' as serial port.
Using '460800' as baud rate.
Showing logs:
[18:13:15]
[18:13:15]
[18:13:15] --~--~--~--
[18:13:15] FujiNet 0.5.13741956 2023-01-30 22:44:10 Started @ 5
[18:13:15] Starting heap: 4365075
[18:13:15] Detected Hardware Version: 1.6.1 and up
[18:13:15] Safe Reset Button 😄 ENABLED
[18:13:15] SPIFFS mounted.
[18:13:16] E (3546) sdmmc_common: sdmmc_init_ocr: send_op_cond (1) returned 0x107
[18:13:16] E (3546) vfs_fat_sdmmc: sdmmc_card_init failed (0x107).
[18:13:16] SD mount failed with code #263, "ESP_ERR_TIMEOUT"
[18:13:16] fnConfig::load
[18:13:16] Load fnconfig.ini from spiffs
[18:13:16] fnConfig::load read 1009 bytes from config file
[18:13:16] SPIFFS Config Storage: Enabled
[18:13:16] fnConfig::load read 1009 bytes from SPIFFS config file
[18:13:16] disk UNMOUNT
[18:13:16] disk MOUNT
[18:13:16] ATR MOUNT
[18:13:16] mounted ATR: paragraphs=5760, sect_size=128, sect_count=720, disk_size=0
[18:13:16] Creating a default printer using FS_SPIFFS storage and type 12
[18:13:16] ModemSniffer::ModemSniffer(FS_SPIFFS)
[18:13:16] SIO SETUP
[18:13:16] Set HSIO baud from 0 to 67431 (index 6), alt=68209
[18:13:16] Available heap: 4345607
[18:13:16] Setup complete @ 1641 (1636ms)
[18:13:16] WiFiManager::start() complete
[18:13:16] WIFI_EVENT_STA_START
[18:13:16] WiFi connect attempt to SSID "(my ssid)"
[18:13:16] esp_wifi_connect returned 0
[18:13:16] WIFI_EVENT_STA_CONNECTED
[18:13:17] IP_EVENT_STA_GOT_IP
[18:13:17] Obtained IP address: 192.168.2.76
[18:13:17] SNTP client start
[18:13:17] Starting web server on port 80
[18:13:20] SNTP time sync event: Mon Feb 20, 18:13:20 2023 -0500

 

 

The error is the 0x107, which means that the ESP32 ran out of low memory (the 320KB block)

 

Question, how many files are on the SD card?

-Thom

 

[SlagOMatic]

Zero. It's a brand new, formatted (FAT, not ExFAT) SD card with nothing on it, not even an empty directory (other than root, of course).

 

EDIT: For clarity, the 32GB SanDisk card is brand new. The other cards I tried (also formatted as FAT volumes) are probably a year or two old and also have nothing on them (because they were formatted).

Edited February 21 by SlagOMatic

[SlagOMatic]

And just a follow-up, for giggles I put a couple of directories on the card and scattered a few ATR files here and there but that didn't change anything. Attempting to access the SD card on FujiNet gives a brief error message of "COULD NOT OPEN DIRECTORY" on the bottom of the screen followed immediately by the wifi status screen.

[mozzwald]

2 hours ago, SlagOMatic said:

I'm having the same issue. Just bought my FujiNet about a week ago. I go into the FujiNet's SD card and it jumps to the wifi connection screen. I've tried three different SD cards, including two brand new SanDisk 32GB cards which work fine everywhere else

I've just tested this 32G card for the first time and it's working for me. Do you know what model your 32Gb card is? What OS and program did you use to format it?

[SlagOMatic]

These are the new SanDisk cards I tried.

[SlagOMatic]

On 2/20/2023 at 8:36 PM, mozzwald said:

I've just tested this 32G card for the first time and it's working for me. Do you know what model your 32Gb card is? What OS and program did you use to format it?

Sorry, should have given more info here. I used Disk Utility on my Mac, first formatting the card as a a FAT/MBR volume and then again as a FAT/GPT volume. I then formatted it on a Windows PC, again as FAT/MBR and then again as FAT/GPT. In all cases when I try to read the card in the FujiNet I get "COULD NOT OPEN DIRECTORY".

[mozzwald]

3 hours ago, SlagOMatic said:

Sorry, should have given more info here. I used Disk Utility on my Mac, first formatting the card as a a FAT/MBR volume and then again as a FAT/GPT volume. I then formatted it on a Windows PC, again as FAT/MBR and then again as FAT/GPT. In all cases when I try to read the card in the FujiNet I get "COULD NOT OPEN DIRECTORY".

Can you try this formatter and see if it makes a difference? https://www.sdcard.org/downloads/formatter/

 

Where did you get the FujiNet from?

[SlagOMatic]

1 hour ago, mozzwald said:

Can you try this formatter and see if it makes a difference? https://www.sdcard.org/downloads/formatter/

 

Where did you get the FujiNet from?

I got it from fujinet.online. I had subscribed for a mail alert when they were back in stock. The alert came with a link, I clicked, I bought.

 

I downloaded the Mac version of the formatter app. I did a quick format of the SD card, same results. I'm right now doing an overwrite format but it's gonna take awhile to complete.

 

UPDATE: Overwrite format complete, same results.

Edited February 25 by SlagOMatic