Open geoff701 opened 1 year ago
People have reported that formatting the SD card in a phone solves many problems
on two new tinySA, I encounter the same problem when reading and writing to the SD "fail write"
thanks for the advices ....
Did you try other cards?
everything solved! the SD cards that arrive with the instrument are defective! many thanks for tip
I have managed to create an SD Read / Write problem in the bitmap capture folder. Operation of the Settings and Trace folders are still working correctly.
While I had the SD card in my reader and connected to my PC I deleted a couple of bmp files from the SD card, I had no problems prior to this action. Subsequently I’m now having problems opening saved bmp files and writing to the SD card in relation to bmp files when selecting Load Capture; when loading a selected bmp file the display freezes. Selecting Load Capture again results in the unit reporting “Error: No Card”. Turning power off and on enables access to SD card again but with same results. Can select Load Capture and it displays the available files but once a file is selected it freezes again. I’m wondering if I have corrupted the File Allocation Table.
Operation for Load Settings, Save Settings and Save Trace are still working ok. Can successfully Save Capture, Save Settings and Save Traces, Load Settings file.
Interestingly the file DEL function does not work, it freezes the display before the DEL button is supposed to go red.
I performed a system file query on the SD card and it reported, G:>fsutil fsInfo volumeInfo G: Volume Name : Volume Serial Number : 0xf0e9334e Max Component Length : 255 File System Name : FAT32 Is ReadWrite Not Thinly-Provisioned Preserves Case of filenames Supports Unicode in filenames Returns Handle Close Result Information Supports Encrypted File System
I formatted a 2GB SD card (sitting in my draw) as FAT32 however the TinySA Ultra will not detect the SD card when inserted in the TinySA Ultra.
My unit details are: Version: tinySA4_v1.4-49-g4f5396a Build Time: Feb 9 2023-09:51:54 Kernel: 4.0.0 HW Version: VO.4.5.1 (168)
Is there a solution to my self-inflicted problem? Regards, Geoff