AM335x MMC1 Card is not detected

Pascal Krauth73

Hello everyone,

I have a AM335x Board and I am successfully accesing a SD-Card on MMC0. I used MMC2 in another project which does also work well.

Now I am using MMC1 to connect a SD-Card which does not work.

The MMC Debug messages hint me that the card is not detected, it gets disabled immediatly after the first messages pop up. But I can't find the correct setting for the initialization.

Question 1:

Do I need to register the MMC1 anywhere else in the code, otherwise then that part that I post below?

Question 2:

Is this a card detect issue, is the MMC1 handled differently then MMC0?

Here is my muxxing:

static struct omap2_hsmmc_info am335x_mmc[] __initdata = {
{
.mmc = 1,
.caps = MMC_CAP_4_BIT_DATA,
//.gpio_cd = GPIO_TO_PIN(0, 6),
.gpio_cd = -EINVAL,
.gpio_wp = -EINVAL,
.ocr_mask = MMC_VDD_32_33 | MMC_VDD_33_34, /* 3V3 */
},
{
.mmc = 2,
.caps = MMC_CAP_4_BIT_DATA,
.nonremovable = true,
.gpio_cd = -EINVAL,
.gpio_wp = -EINVAL,
.ocr_mask = MMC_VDD_32_33 | MMC_VDD_33_34,
},
{
.mmc = 0, /* will be set at runtime */
},
{} /* Terminator */


};

/* mmc0 initialization */
static void mmc0_init(void)
{
setup_pin_mux(mmc0_pin_mux);
setup_pin_mux(mmc1_pin_mux);
omap2_hsmmc_init(am335x_mmc);

return;
}



/* pin-mux for mmc0 */
static struct pinmux_config mmc0_pin_mux[] = {
{"mmc0_dat3.mmc0_dat3", OMAP_MUX_MODE0 | AM33XX_PIN_INPUT_PULLUP},
{"mmc0_dat2.mmc0_dat2", OMAP_MUX_MODE0 | AM33XX_PIN_INPUT_PULLUP},
{"mmc0_dat1.mmc0_dat1", OMAP_MUX_MODE0 | AM33XX_PIN_INPUT_PULLUP},
{"mmc0_dat0.mmc0_dat0", OMAP_MUX_MODE0 | AM33XX_PIN_INPUT_PULLUP},
{"mmc0_clk.mmc0_clk", OMAP_MUX_MODE0 | AM33XX_PIN_INPUT_PULLUP},
{"mmc0_cmd.mmc0_cmd", OMAP_MUX_MODE0 | AM33XX_PIN_INPUT_PULLUP},
/* {"spi0_cs1.mmc0_sdcd", OMAP_MUX_MODE7 | AM33XX_PIN_INPUT_PULLUP},*/
{NULL, 0},
};

/* pin-mux for mmc1 */
static struct pinmux_config mmc1_pin_mux[] = {
{"gpmc_ad11.mmc1_dat3", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
{"gpmc_ad10.mmc1_dat2", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
{"gpmc_ad9.mmc1_dat1", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
{"gpmc_ad8.mmc1_dat0", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
{"gpmc_csn1.mmc1_clk", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
{"gpmc_csn2.mmc1_cmd", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
{NULL, 0},
};

over 9 years ago

0 Biser Gatchev-XID over 9 years ago

TI__Guru**** 393215 points

Hi,

I will forward this to the SW team.

0 Yordan Kovachev over 9 years ago

TI__Guru**** 161600 points

Hi,

Have you tried using the CD pin?
Also can you paste the debug messages from the console?

"Do I need to register the MMC1 anywhere else in the code, otherwise then that part that I post below? "
No, all IPs used are described & initialized in the board file or DTS, depending on your linux version. From your code I get that you are using board file.

"Is this a card detect issue, is the MMC1 handled differently then MMC0?"
No MMC1 should be handled the same way as the other MMC instances. Have you verified that the device pads, are not used by another IP?

Best Regards,
Yordan

0 Pascal Krauth73 over 9 years ago in reply to Yordan Kovachev

Prodigy 80 points

Helllo Yordan,

we tried to use a non related GPIO and the PIN mmc1_sdcd (GPIO3_15) for the CD. Which didn't change the behaviour.

We have done some measurement on the PINs, if we use the mentioned AD8..11 PINs as GPIOs everything works fine, e.g. we can enable disable the internal Pullups. If we set those PINs as Input Pullup in Mux Mode 2 instead of 7, the Pullups are not activated.

The Pinmuxxing and routing seems to be correct as we proved by using the PINs as GPIOs. The console from our Linux 3.2 Kernel is showing no message in dmesg if we register only the mmc1, if we register also the mmc0 we get to the point that :

omap_hsmmc.0: alias fck already exists
omap_hsmmc.1: alias fck already exists

is printed. After that the plugged card in the MMC0 slot is recognized. No further information from MMC1.
If we use the MMC_DEBUGGING Kernel switch the MMC1 initialization does stop at the point at BUSMODE is set to 0.
For the MMC0 the BUSMODE is also 0 at first and does switch up to 2 when the card is recognized.

At this point we have absolutely no clue how to debug this further.

Best regards,
Pascal

0 Pascal Krauth73 over 9 years ago in reply to Pascal Krauth73

Prodigy 80 points

Hello Dear Ti and Forum,

our product is still on hold due to this problem.

Any suggestions?

Best regards,
Pascal

0 Biser Gatchev-XID over 9 years ago in reply to Pascal Krauth73

TI__Guru**** 393215 points

Pascal,

What is your sysboot sequence? Please note that some of the the pins you use for MMC1 will be initialized to their GPMC mode by ROM code if GPMC is involved in the boot sequence.

0 Biser Gatchev-XID over 9 years ago in reply to Biser Gatchev-XID

TI__Guru**** 393215 points

And another question - what are your VDDSHV1 and VDDSHV2 voltages?

0 Pascal Krauth73 over 9 years ago in reply to Biser Gatchev-XID

Prodigy 80 points

Biser Gatchev-XID said:

What is your sysboot sequence? Please note that some of the the pins you use for MMC1 will be initialized to their GPMC mode by ROM code if GPMC is involved in the boot sequence.

We are booting from MMC0

lcd_data_d0 = 1

lcd_data_d1 = 1

lcd_data_d2 = 1

lcd_data_d3 = 0

lcd_data_d4 = 1

Biser Gatchev-XID said:
And another question - what are your VDDSHV1 and VDDSHV2 voltages?

We have the package ZCZ, VDDSHV1 is 3.3V and VDDSHV2 is 3.3V. On the data Pins of MMC1 MMC0 I can measure this, the PIns of MMC2 MMC1 stay low (equally no card is plugged on both) measured in the Barebox so propably a muxxing issue from the Bootloader.

0 Biser Gatchev-XID over 9 years ago in reply to Pascal Krauth73

TI__Guru**** 393215 points

So SYSBOOT and voltage issues can be discarded, there are none. Up to now you were referring to MMC0 and MMC1. I don't understand.

0 Pascal Krauth73 over 9 years ago in reply to Biser Gatchev-XID

Prodigy 80 points

You are correct, I did by mistake use the wrong postfix. I corrected my last post.
Best regards,
Pascal

0 Biser Gatchev-XID over 9 years ago in reply to Pascal Krauth73

TI__Guru**** 393215 points

No, it can't be the ROM code, based on the SYSBOOT settings you post. You should check that your MMC1 pinmux settings don't get overwritten somewhere else.

0 Pascal Krauth73 over 9 years ago in reply to Biser Gatchev-XID

Prodigy 80 points

I tried to verify my settings by changing the above mentioned Pins to Muxmode 7 and enabling the Pullups, which worked fine (verified by measurement).

Any suggestions?

Best regards,
Pascal

0 Biser Gatchev-XID over 9 years ago in reply to Pascal Krauth73

TI__Guru**** 393215 points

Just changing the muxmode in the same structure? Pullups should work regardless of muxmode selected, unless the I/O output driver drives the pin low (this will override the pullup). Could you check this post for a possible solution: e2e.ti.com/.../963179

0 Pascal Krauth73 over 9 years ago in reply to Biser Gatchev-XID

Prodigy 80 points

I did include the rootdelay=2 with no luck.

Best regards,
Pascal

0 Pascal Krauth73 over 9 years ago in reply to Pascal Krauth73

Prodigy 80 points

It turns out that there was an late initialization of a csn Pin which caused the bug.
Thank you Biser for pointing in the right direction.

Best regards,
Pascal

Processors

Processors forum

AM335x MMC1 Card is not detected