Thank You for your continued support and contributions!
If the card isn't taking writes it is probably badIt could be flaky and maybe it needs higher voltage levels idkYou could try a build with higher voltage levels or just mark it as a bad card for the device and use it for something else You might do a flash test with 3rd party tools to see how stable it really is
sudo f3probe --destructive --time-ops /dev/mmcblk0 F3 probe 8.0Copyright (C) 2010 Digirati Internet LTDA.This is free software; see the source for copying conditions.WARNING: Probing normally takes from a few seconds to 15 minutes, but it can take longer. Please be patient.Good news: The device `/dev/mmcblk0' is the real thingDevice geometry: *Usable* size: 58.36 GB (122388480 blocks) Announced size: 58.36 GB (122388480 blocks) Module: 64.00 GB (2^36 Bytes) Approximate cache size: 0.00 Byte (0 blocks), need-reset=no Physical block size: 512.00 Byte (2^9 Bytes)Probe time: 3'05" Operation: total time / count = avg time Read: 723.2ms / 4816 = 150us Write: 2'56" / 4192321 = 42us Reset: 1us / 1 = 1us
const struct sdmmc_config_t sdmmc_config[] ={#ifdef SANSA_FUZEPLUS /* The Fuze+ uses pin #B0P8 for power */ { .name = "microSD", .flags = POWER_PIN | POWER_INVERTED | REMOVABLE, .power_pin = PIN(0, 8), .ssp = 1, .mode = SD_MODE, }, /* The Fuze+ uses pin #B1P29 for power */ { .name = "eMMC", .flags = POWER_PIN | POWER_INVERTED | WINDOW | POWER_DELAY, .power_pin = PIN(1, 29), .power_delay = HZ / 5, /* extra delay, to ramp up voltage? */ .ssp = 2, .mode = MMC_MODE, },
Maybe there is already a build with these changes floating around that you could test, but if you can compile, make this change for the line above for the Clip Zip and see if the SD card works better:https://git.rockbox.org/cgit/rockbox.git/commit/firmware/target/arm/as3525?id=c75aac84243abef6a5b7e2e84863cef13931ee8f
Page created in 0.094 seconds with 17 queries.