SD card support?

Krassimir Slavchev krassi at bulinfo.net
Fri Feb 23 11:19:28 UTC 2007


Bernd Walter wrote:
> On Thu, Feb 22, 2007 at 06:36:22PM +0200, Krassimir Slavchev wrote:
>   
>> M. Warner Losh wrote:
>>     
>>> In message: <45DD6E45.5000505 at bulinfo.net>
>>>            Krassimir Slavchev <krassi at bulinfo.net> writes:
>>> : Hello,
>>> : 
>>> : I've read that SD is not supported by qdmmc and now qdmmc does not exist 
>>> : in the source tree.
>>> : Are the SD cards supported by mmcsd driver?
>>>
>>> Yes.  The qdmmc driver is no more.  The at91_mci driver is the host
>>> adapter driver, mmc is the bus, and mmcsd is support for mmc/sd cards
>>> (although only sd will work at the moment due to lack of hardware).
>>>
>>>  
>>>       
>> Good!
>>
>> I am going to investigate why my SD card is not detected.
>>
>> dmesg says only:
>>
>> at91_mci0: Setting controller bus width to 1
>> at91_mci0: Setting controller bus width to 1
>> at91_mci0: Setting controller bus width to 1
>> at91_mci0: Setting controller bus width to 1
>> mmc0: setting transfer rate to 30.000MHz
>> at91_mci0: Setting controller bus width to 1
>>     
>
> I noticed a problem when netbooting, that cards are only detected on
> reboot.
> Booting via boot2 doesn't hsow this problem.
> Another point, which I noticed yesterday is that the kernel did not
> find a verbatim media, although boot2 sucessfully loaded the kernel.
>
>   
Yes, because bootspi does not call sdcard_init() function!

After adding:

Timecounters tick every 10.000 msec
at91_mci0: Setting controller bus width to 1
at91_mci0: Setting controller bus width to 1
at91_mci0: Setting controller bus width to 1
at91_mci0: Setting controller bus width to 1
at91_mci0: Setting controller bus width to 1
at91_mci0: Setting controller bus width to 1
SD CARD: 998768640 bytes
at91_mci0: Setting controller bus width to 1
mmcsd0: <mmc or sd flash card> on mmc0
mmc0: setting transfer rate to 30.000MHz
at91_mci0: Setting controller bus width to 1
Trying to mount root from ufs:/dev/mmcsd0s1a

>>> : Also what this line in dmesg means:
>>> : 'Cannot get 100 Hz clock; using 100Hz'
>>> : May be something is not initialized?
>>>
>>> No, that just means you can't divide 32768 by 100 evenly.
>>>
>>> Warner
>>>
>>>  
>>>       
>> And another problem:
>>
>> ate0: <EMAC> mem 0xdffbc000-0xdffbffff irq 24 on atmelarm0
>> ate0: Cannot find my PHY.
>> device_attach: ate0 attach returned 6
>>
>> Looks like nothing on miibus. Very strange because the bootspi is able 
>> to boot from tftp server.
>> The PHY is RTL8201CP and I use rlphy driver which is for RTL8201L.
>>
>> Any hints where to look?
>>     
>
> Enhance the rlphy driver - should be enough to add the device ID.
> The additional automdix feature should be tranparent.
>
>   




More information about the freebsd-arm mailing list