sdio
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sdio [2025/03/22 19:37] – arisotura | sdio [2025/04/16 20:24] (current) – arisotura | ||
|---|---|---|---|
| Line 50: | Line 50: | ||
| | 0xE00100FE | SD_HostControllerVersion | | | 0xE00100FE | SD_HostControllerVersion | | ||
| - | This SDIO host controller seems to be mostly standards compliant. | + | There is also a register at 0xF0004800 that seems to control something related to the SDIO controller. The reset value for that register is 3, any other value breaks SDIO functionality. Not known yet how this works in detail. |
| + | |||
| + | This SDIO host controller seems to be mostly standards compliant. | ||
| When setting the block size for a CMD53 transfer, the stock firmware sets bit 12-14 in SD_BlockSize to 7. The open-source BCM43xx drivers do not do this. These bits are the SDMA buffer boundary: a DMA transfer stops when crossing the specified boundary (here configured to 512K). Writing a new address to SD_SysAddr will resume the DMA transfer. If not using fancy memory tricks, one can just write the current SD_SysAddr value back to continue the transfer where it stopped. | When setting the block size for a CMD53 transfer, the stock firmware sets bit 12-14 in SD_BlockSize to 7. The open-source BCM43xx drivers do not do this. These bits are the SDMA buffer boundary: a DMA transfer stops when crossing the specified boundary (here configured to 512K). Writing a new address to SD_SysAddr will resume the DMA transfer. If not using fancy memory tricks, one can just write the current SD_SysAddr value back to continue the transfer where it stopped. | ||
| Register SD_Capabilities reads as 0x69EF30B0. (TODO: document some of the other fixed registers) | Register SD_Capabilities reads as 0x69EF30B0. (TODO: document some of the other fixed registers) | ||
| + | |||
sdio.1742672268.txt.gz · Last modified: 2025/03/22 19:37 by arisotura