Opened 13 months ago

Last modified 13 months ago

#17604 new bug

sdhci intel not working

Reported by: korli Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Drivers/Disk/MMC Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All


vendor intel device id: 0x4dc4 connected to a 128GB flash.

Attachments (1)

syslog (163.2 KB ) - added by korli 13 months ago.
syslog with

Download all attachments as: .zip

Change History (3)

comment:1 by korli, 13 months ago

Seems a bit better with the change.

comment:2 by pulkomandy, 13 months ago

CMD0 (reset) works fine.

Then CMD8 never completes:

828	2022-02-20 20:14:14 KERN: [33mmmc_bus:[0m Scanning the bus
830	2022-02-20 20:14:14 KERN: [33msdhci_pci:[0m SDCLK frequency: 200MHz / 500 = 400kHz
832	2022-02-20 20:14:14 KERN: [33mmmc_bus:[0m Clock set
834	2022-02-20 20:14:14 KERN: [33msdhci_pci:[0m CALLED void set_bus_width(void*, int)
836	2022-02-20 20:14:14 KERN: [33mmmc_bus:[0m BusWidth set
838	2022-02-20 20:14:14 KERN: [33mmmc_bus:[0m CALLED status_t MMCBus::_ActivateDevice(uint16_t)
840	2022-02-20 20:14:14 KERN: [33msdhci_pci:[0m ExecuteCommand(8, 1aa)
842	2022-02-20 20:14:14 KERN: [33msdhci_pci:[0m Wait for command complete... 

This is possible for SD 1.0 cards or MMC cards (that command didn't exist there, but the controller should give a "no response" interrupt). Or it could be that the clock and bus width changes did not work correctly.

Note: See TracTickets for help on using tickets.