SD Card Issues - error -110 whilst initialising SD card


#1

Hello All,

I’ve got my mangOH Red up and running with a WP7603 module. I just completed an app using GNSS and threads! Anyway, I decided to try and write some of the location data to the SD card that came with the kit. Unfortunately I couldn’t find the device while SSH’d into it. After some research it looks like the controller is failing to initialize it. Here’s (what I think is) the appropriate dmesg info …

[    0.835176] sdhci: Secure Digital Host Controller Interface driver
[    0.835188] sdhci: Copyright(c) Pierre Ossman
[    0.835201] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.841609] sdhci_msm 7864900.sdhci: sdhci_msm_probe: ICE device is not enabled
[    0.841632] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/soc/sdhci@07864900[0]'
[    0.841998] sdhci_msm ": sdhci_msm_pm_qos_parse_irq: error -22 reading irq cpu
[    0.842011] sdhci_msm 7864900.sdhci: sdhci_msm_pm_qos_parse: PM QoS voting for IRQ will be disabled
[    0.842026] sdhci_msm 7864900.sdhci: sdhci_msm_pm_qos_parse: PM QoS voting for cpu group will be disabled
[    0.850611] sdhci_msm 7864900.sdhci: No vmmc regulator found
[    0.850626] sdhci_msm 7864900.sdhci: No vqmmc regulator found
[    0.851017] mmc0: SDHCI controller on 7864900.sdhci [7864900.sdhci] using 32-bit ADMA in legacy mode
[    1.290132] mmc0: mmc_sd_init_card() failure (err = -110)
[    1.290145] mmc0: error -110 whilst initialising SD card

I searched through the forum and the internet and couldn’t find an answer to this. Here’s what I’ve done to try and get it to work.

Bad SD Card
A few suggestions about a bad SD card but I don’t think that’s the case. First, it came with the kit so it should work. Second, it works with my other systems (linux, Windows) and I’ve reformatted it as FAT and exFAT to no avail. Also tried MBR and GPT partition tables. In the end I feel the SD card is working properly and that’s not the cause. Also, I also tried a different SD card that I know is good and experienced the same error.

IoT Connector & SD Card
Another post on this forum suggests that you can’t use an SD card at the same time as an IoT connector/module/expansion. I did have the IoT pin expansion in when I first tried to access the SD card. So I powered down and removed it, then started it back up. Unfortunately I still saw the same error.

GPIO Pin for SD Card Detection
I also came across a post where the person mentioned a “GPIO pin for SD card detection.” I cannot find one on this board and I can’t find anything else in the docs about it. Maybe I’m overlooking something?

Hardware Info
Device: WP7603
Firmware Version: SWI9X07Y_02.18.05.00 000000 jenkins 2018/07/19 17:40:21
Bootloader Version: SWI9X07Y_02.18.05.00 000000 jenkins 2018/07/19 17:40:21
MCU Version: 002.009
PRI Part Number (PN): 9906965
PRI Revision: 002.003
Carrier PRI Name: GENERIC
Carrier PRI Revision: 002.041_002

Related Posts
I’m new so I’m only allowed to post two links. Here are the most related topics…

In the end I here because I’m out of ideas. Any help would be appreciated. Let me know if I can provide any more info.

Thanks!


#2

Hi @vBit,
Happy to see that we aren’t the only one to get that result.
What kind of mSD card is it? Because depending on four aspects I think which are manufacturer, transfer speed, card class and memory size, the mangOh Red will react differently.
I have tried with SanDisk Ultra Plus microSDHC UHS-I 16 Go class A1 with speed up to 98 MB/s and I’ve got the same error like you. I managed to change the format of mSD in ext4 (add support for the mangOH too), exFAT and FAT32 and till the same. With or without IoT. See also Using MicroSD MangOH Red and https://forum.mangoh.io/t/micro-sd-support-on-mangoh/91/11
I post that.

root@mangoh9:~# dmesg |grep mmc
[    1.148887] sdhci_msm 7864900.sdhci: No vmmc regulator found
[    1.148904] sdhci_msm 7864900.sdhci: No vqmmc regulator found
[    1.149297] mmc0: SDHCI controller on 7864900.sdhci [7864900.sdhci] using 32-bit ADMA in legacy mode
[    1.630132] mmc0: mmc_sd_init_card() failure (err = -110)
[    1.634557] mmc0: error -110 whilst initialising SD card

root@mangoh9:~# dmesg |grep sdhci
[    1.103241] sdhci: Secure Digital Host Controller Interface driver
[    1.103253] sdhci: Copyright(c) Pierre Ossman
[    1.103267] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.113726] sdhci_msm 7864900.sdhci: sdhci_msm_probe: ICE device is not enabled
[    1.113750] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/soc/sdhci@07864900[0]'
[    1.114120] sdhci_msm 7864900.sdhci: sdhci_msm_pm_qos_parse_irq: error -22 reading irq cpu
[    1.134004] sdhci_msm 7864900.sdhci: sdhci_msm_pm_qos_parse: PM QoS voting for IRQ will be disabled
[    1.134023] sdhci_msm 7864900.sdhci: sdhci_msm_pm_qos_parse: PM QoS voting for cpu group will be disabled
[    1.148887] sdhci_msm 7864900.sdhci: No vmmc regulator found
[    1.148904] sdhci_msm 7864900.sdhci: No vqmmc regulator found
[    1.149297] mmc0: SDHCI controller on 7864900.sdhci [7864900.sdhci] using 32-bit ADMA in legacy mode

I suspect mangOhRed may accept only mSD cards with 8 Go capacity and not so high speed, is that right @asyal? Or is it just software?

But it’s still incomprehensible that mSD provided in the kit doesn’t work.

Thanks for any help!


#3

We don’t provide sd card with mangoh red kit


#4

@alex1 & @asyal,

Sorry, I thought the 8GB SD card came with the kit but I must have purchased it at the same time? Regardless, here are the two cards I’ve tried.

  • SanDisk Industrial 8GB microSD, Model SL08G

  • SanDisk Ultra 32GB microSD, Model SU32G

    I’m doing by best to try and find more details (parted -l, /sys/block/*) on them but they’re plugged in through a USB multi-slot reader so I’m only pulling info about that. I’ll post more info if I can find it.

Thanks!

EDIT: Added SD card model numbers


#5

Oh sorry, maybe with Orange Kit Starter.

EDITED : no mSD provided in any kit :wink:

By the way, I have looked at some sites and they suggest to check the state of gpios in the kernel.

Here : [https://community.nxp.com/thread/430385]( MMC Issue with Upgrade to Kernel 4.1.15)


#6

@alex1,

Thanks for sharing the link. I read through it and it appears that the SD Card Detect signal is also a GPIO pin. At some point a kernel change was made so that it’s active low instead of high. I’m just not sure what NXP is or how it relates to mangOH and Legato. I’m guessing it would be in the Legato firmware since the boot process is where it fails and that thread talks about kernel changes. So for me the firmware source is installed under /opt/swi/y22-ext-SWI9X07Y_02.18.06.00. I grep’d for the terms below but can’t seem to find anything that I could change.

Grep Terms

  • GPIO_ACTIVE_LOW
  • GPIO_ACTIVE_HIGH
  • cd-gpios
  • mmc_of_parse

Grep Results

 /opt/swi/y22-ext-wp76xx $ sudo grep -r "GPIO_ACTIVE_LOW" ./*
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/spi/mmc_spi.h:#define MMC_SPI_CD_GPIO_ACTIVE_LOW		(1 << 2)
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/spi/mmc_spi.h:#define MMC_SPI_RO_GPIO_ACTIVE_LOW		(1 << 3)
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/mfd/wm8350/gpio.h:#define WM8350_GPIO_ACTIVE_LOW			0
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/gpio/machine.h:	GPIO_ACTIVE_LOW = (1 << 0),
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/of_gpio.h:	OF_GPIO_ACTIVE_LOW = 0x1,
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/dt-bindings/gpio/gpio.h:#define GPIO_ACTIVE_LOW 1
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/linux/spi/mmc_spi.h:#define MMC_SPI_CD_GPIO_ACTIVE_LOW		(1 << 2)
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/linux/spi/mmc_spi.h:#define MMC_SPI_RO_GPIO_ACTIVE_LOW		(1 << 3)
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/linux/mfd/wm8350/gpio.h:#define WM8350_GPIO_ACTIVE_LOW			0
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/linux/gpio/machine.h:	GPIO_ACTIVE_LOW = (1 << 0),
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/linux/of_gpio.h:	OF_GPIO_ACTIVE_LOW = 0x1,
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/dt-bindings/gpio/gpio.h:#define GPIO_ACTIVE_LOW 1

 /opt/swi/y22-ext-wp76xx $ sudo grep -r "GPIO_ACTIVE_HIGH" ./*
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/mfd/wm8350/gpio.h:#define WM8350_GPIO_ACTIVE_HIGH			1
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/gpio/machine.h:	GPIO_ACTIVE_HIGH = (0 << 0),
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/dt-bindings/gpio/gpio.h:#define GPIO_ACTIVE_HIGH 0
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/linux/mfd/wm8350/gpio.h:#define WM8350_GPIO_ACTIVE_HIGH			1
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/linux/gpio/machine.h:	GPIO_ACTIVE_HIGH = (0 << 0),
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/dt-bindings/gpio/gpio.h:#define GPIO_ACTIVE_HIGH 0

 /opt/swi/y22-ext-wp76xx $ sudo grep -r "cd-gpios" ./*

 /opt/swi/y22-ext-wp76xx $ sudo grep -r "mmc_of_parse" ./*
./sysroots/armv7a-neon-poky-linux-gnueabi/boot/Module.symvers-3.18.44:0x00000000	mmc_of_parse	vmlinux	EXPORT_SYMBOL
./sysroots/armv7a-neon-poky-linux-gnueabi/boot/Module.symvers-3.18.44:0x00000000	mmc_of_parse_voltage	vmlinux	EXPORT_SYMBOL
./sysroots/armv7a-neon-poky-linux-gnueabi/boot/System.map-3.18.44:c049771c T mmc_of_parse_voltage
./sysroots/armv7a-neon-poky-linux-gnueabi/boot/System.map-3.18.44:c049a28c T mmc_of_parse
./sysroots/armv7a-neon-poky-linux-gnueabi/boot/System.map-3.18.44:c0a9446c R __ksymtab_mmc_of_parse
./sysroots/armv7a-neon-poky-linux-gnueabi/boot/System.map-3.18.44:c0a94474 R __ksymtab_mmc_of_parse_voltage
./sysroots/armv7a-neon-poky-linux-gnueabi/boot/System.map-3.18.44:c0ab7285 r __kstrtab_mmc_of_parse_voltage
./sysroots/armv7a-neon-poky-linux-gnueabi/boot/System.map-3.18.44:c0ab75d2 r __kstrtab_mmc_of_parse
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/System.map-3.18.44:c049771c T mmc_of_parse_voltage
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/System.map-3.18.44:c049a28c T mmc_of_parse
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/System.map-3.18.44:c0a9446c R __ksymtab_mmc_of_parse
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/System.map-3.18.44:c0a94474 R __ksymtab_mmc_of_parse_voltage
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/System.map-3.18.44:c0ab7285 r __kstrtab_mmc_of_parse_voltage
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/System.map-3.18.44:c0ab75d2 r __kstrtab_mmc_of_parse
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/Module.symvers:0x00000000	mmc_of_parse	vmlinux	EXPORT_SYMBOL
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/Module.symvers:0x00000000	mmc_of_parse_voltage	vmlinux	EXPORT_SYMBOL
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/mmc/host.h:int mmc_of_parse(struct mmc_host *host);
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/include/linux/mmc/core.h:extern int mmc_of_parse_voltage(struct device_node *np, u32 *mask);
./sysroots/armv7a-neon-poky-linux-gnueabi/usr/src/kernel/usr/include/linux/mmc/host.h:int mmc_of_parse(struct mmc_host *host);

Unfortunately I can’t seem make much sense of it or figure out what to change. Can you point me in the right direction?

Thanks!


#7

You’re right, something has to be done in the firmware source (Yocto). As I am not a hardware specialist, I am not sure of which change could make mSD card read.

I found a definition bus file here : kernel/arch/arm/boot/dts/qcom/mdm9607.dtsi
We can find sdhc_1 and sd_hc2. This is another way to follow.

Because the main problem is still we don’t know exactly what kind of error it is.
The function mmc_sd_init_card()may come from kernel/drivers/mmc/core/sd.c.

And another point is we may activate or deactivate GPIO pin with some commands like for the Ethernet IoT port:

echo <number_pin> > /sys/class/gpio/export
cat < /sys/class/gpio/gpio<number_pin>/direction # check the output
echo <in/out> > /sys/class/gpio/gpio<number_pin>/direction
cat < /sys/class/gpio/gpio<number_pin>/value
echo <0/1> > /sys/class/gpio/gpio<number_pin>/value

So trying to activate GPIO2 and GPIO42 with those commands

echo 2 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio2/direction
echo 1 > sys/class/gpio/gpio2/value

echo 42 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio42/direction
echo 1 > sys/class/gpio/gpio42/value

and gave me respectively this

[  744.086283] gpio_sync_ri: RI owner is Modem
[  744.086323] gpio_map_name_to_num: find GPIO 38
[  744.086338] export_store: Export GPIO: 38
[  744.086380] gpio_sync_ri: RI owner is Modem
[  744.086400] gpiod_export: sierra--find GPIO,chipdev = -824028144,chipngpio = 80,chipbase = 0

and

[ 5786.834248] gpio_sync_ri: RI owner is Modem
[ 5786.834300] gpio_map_name_to_num: find GPIO 79
[ 5786.834315] export_store: Export GPIO: 79
[ 5786.834357] gpio_sync_ri: RI owner is Modem
[ 5786.834378] gpiod_export: sierra--find GPIO,chipdev = -824028144,chipngpio = 80,chipbase = 0

So why pins 2 and 42? Because it should use the same pin like Ethernet IoT (2) and the SD detect is connected to 42 in the DV5 schematics.

SD connector

Outter ring

Inner ring

I inserted the mSD card again (no IoT inserted) and still the same error as we insert it before booting the mangOH Red.

So many things to check.


#8

From other post : All wifi commands failing with Mirage board
We can see another module cited for SDIO/MMC module : msm_sdcc .
This one is not provided in my kernel.

EDIT: My bad, it is a module made for mangOH green. ^^

Summary

root@mangoh9:~# cat /lib/modules/3.18.44/modules.dep
kernel/fs/quota/quota_v1.ko:
kernel/fs/quota/quota_v2.ko: kernel/fs/quota/quota_tree.ko
kernel/fs/quota/quota_tree.ko:
kernel/crypto/seqiv.ko:
kernel/crypto/ctr.ko:
kernel/crypto/ccm.ko:
kernel/crypto/arc4.ko:
kernel/crypto/michael_mic.ko:
kernel/crypto/ansi_cprng.ko:
kernel/block/test-iosched.ko:
kernel/drivers/net/phy/at803x.ko:
kernel/drivers/net/phy/qca8337.ko:
kernel/drivers/net/ethernet/qualcomm/emac/qcom_emac.ko: kernel/drivers/net/phy/qca8337.ko
kernel/drivers/net/wireless/ti/wlcore/wlcore.ko: kernel/net/mac80211/mac80211.ko kernel/net/wireless/cfg80211.ko
kernel/drivers/net/wireless/ti/wlcore/wlcore_sdio.ko:
kernel/drivers/net/wireless/ti/wl12xx/wl12xx.ko: kernel/drivers/net/wireless/ti/wlcore/wlcore.ko kernel/net/mac80211/mac80211.ko kernel/net/wireless/cfg80211.ko
kernel/drivers/net/wireless/ti/wl1251/wl1251.ko: kernel/net/mac80211/mac80211.ko kernel/net/wireless/cfg80211.ko
kernel/drivers/net/wireless/ti/wl18xx/wl18xx.ko: kernel/drivers/net/wireless/ti/wlcore/wlcore.ko kernel/net/mac80211/mac80211.ko kernel/net/wireless/cfg80211.ko
kernel/drivers/usb/serial/usbserial.ko:
kernel/drivers/usb/serial/ftdi_sio.ko: kernel/drivers/usb/serial/usbserial.ko
kernel/drivers/input/misc/gpio_event.ko:
kernel/drivers/input/misc/gpio_matrix.ko:
kernel/drivers/input/misc/gpio_input.ko:
kernel/drivers/input/misc/gpio_output.ko:
kernel/drivers/input/misc/gpio_axis.ko:
kernel/drivers/mmc/card/mmc_test.ko:
kernel/drivers/mmc/card/mmc_block_test.ko: kernel/block/test-iosched.ko
kernel/drivers/iio/imu/bmi160/bmi160.ko:
kernel/net/netfilter/xt_physdev.ko:
kernel/net/wireless/cfg80211.ko:
kernel/net/mac80211/mac80211.ko: kernel/net/wireless/cfg80211.ko
kernel/lib/crc7.ko:
extra/embms_kernel.ko:

Maybe this fails due to that lack?

Edit : Not the case because not made for this platform.

For the persons who can perform with their SD card what modules do you use?


#9

@alex1,

Great research! Thanks for going through all of it. I ran the commands you posted on my hardware. Unfortunately I experienced the same result when plugging in the 8GB mSD card.

I also checked for the msm_sdcc module and, just like you, I don’t show it.

I may try some older firmware versions to see if that changes anything.

Thanks Again!


#10

All,
We will order 10-15 send cards and test, will provide name of compatible cards. @Habib can you give them the name of the card we use internally?


#11

@vBit

Nothing is better to make some research to understand and make things work with mates.
Unfortunately, the last point was not the problem as I edited, it is mangOH green intended.

I put research forward with enabling MMC debugging in Yocto kernel and it tries continuously to initiate the uSD card.

dmesg

mmc-debug.rtf (125.1 KB)

enabling mmc-debugging

Summary
cd yocto
make dev
bitbake -f linux-quic -c menuconfig
 Symbol: MMC_DEBUG [=y]                                            
bitbake -f linux-quic -c compile
bitbake -f linux-quic -c build
bitbake mdm9x28-image-minimal
exit
cfglegato
fwupdate download build_bin/tmp/deploy/images/swi-mdm9x28-wp/yocto_wp76xx.4k.cwe 192.168.2.2

normal state with no uSD card inserted

root@mangoh9:/sys/kernel/debug/mmc0# cat ios
clock:		400000 Hz
actual clock:	400000 Hz
vdd:		18 (3.0 ~ 3.1 V)
bus mode:	1 (open drain)
chip select:	0 (don't care)
power mode:	2 (on)
bus width:	0 (1 bits)
timing spec:	0 (legacy)
signal voltage:	0 (3.30 V)



root@mangoh9:/sys/kernel/debug/mmc0# cat ios
clock:		400000 Hz
actual clock:	400000 Hz
vdd:		18 (3.0 ~ 3.1 V)
bus mode:	1 (open drain)
chip select:	1 (active high)
power mode:	2 (on)
bus width:	0 (1 bits)
timing spec:	0 (legacy)
signal voltage:	1 (3.30 V)

root@mangoh9:/sys/kernel/debug/mmc0# cat ios
clock:		0 Hz
actual clock:	400000 Hz
vdd:		0 (invalid)
bus mode:	1 (open drain)
chip select:	0 (don't care)
power mode:	0 (off)
bus width:	0 (1 bits)
timing spec:	0 (legacy)
signal voltage:	0 (3.30 V)

root@mangoh9:/sys/kernel/debug/mmc0# cat ios
clock:		0 Hz
vdd:		18 (3.0 ~ 3.1 V)
bus mode:	1 (open drain)
chip select:	0 (don't care)
power mode:	1 (up)
bus width:	0 (1 bits)
timing spec:	0 (legacy)
signal voltage:	0 (3.30 V)

now with uSD card inserted after 3-4s

root@mangoh9:/sys/kernel/debug/mmc0# cat ios
clock:		0 Hz
vdd:		0 (invalid)
bus mode:	1 (open drain)
chip select:	0 (don't care)
power mode:	0 (off)
bus width:	0 (1 bits)
timing spec:	0 (legacy)
signal voltage:	0 (3.30 V)

then 

root@mangoh9:/sys/kernel/debug/mmc0# cat ios
clock:		0 Hz
vdd:		18 (3.0 ~ 3.1 V)
bus mode:	1 (open drain)
chip select:	0 (don't care)
power mode:	1 (up)
bus width:	0 (1 bits)
timing spec:	0 (legacy)
signal voltage:	0 (3.30 V)

loopback then

@asyal, thanks for your support, we are looking forward your info and the uSD models compatible.


#12

I have tested the following SD cards with WP7603 Rel 10.1 and both works:
Kingston 8 GB microSD HC class 10
PNY 4 GB microSD HC, class 4


#13

Hi there

We have tested and found that Sandisk SDSDQAD-128G works fine together with
WP7202 and WP7204 modules.

BR

Jess


#14

Hi,

Finally on a WP7607 Rev 10.1 the Kingston 8GB uSDHC class 4 works.


#15

Hello All,

I picked up two more uSD cards and they worked! Here are the two new cards.

  • Samsung 32GB - GB1QT
  • Kingston 16GB - SA16G

And their partition info …

Samsung 32GB - GB1QT

Model: SD GB1QT (sd/mmc)
Disk /dev/mmcblk0: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
 1      4194kB  32.0GB  32.0GB  primary  fat32        lba

Kingston 16GB - SA16G

Model: SD SA16G (sd/mmc)
Disk /dev/mmcblk0: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
 1      4194kB  15.6GB  15.5GB  primary  fat32        lba

I compared that to one of the SanDisk uSD cards that didn’t work. The only difference I could find was the partition Start position. The working partitions start at 4194kB and the ones that don’t start at 1049kB. Regardless, here’s the info …

San Disk 8GB SL08G

Model: SD SL08G (sd/mmc)
Disk /dev/mmcblk0: 7948MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  7948MB  7947MB  primary  fat32        lba

I removed the first partition and forced the start position of 4194kB. When doing that parted complained about the sectors not lining up, but I was still able to format it as FAT32. Afterwards I verified it would mount in and successfully stored a PDF on it. Afterwards I tried it on the WP7603 and mangOH Red but, unfortunately, it still didn’t work. The errors were the same as my original post.

So for whatever reason I now have 3 (found a third SanDisk uSD laying around) SanDisk uSDs that do not work. I purchased a Samsung and Kingston and they both work. Let me know if I can provide any more info to figure out why that is.

Thanks,
vBit