kmoore37918 wrote:
>> I believe if you modify tssdcard.c to include sdcore.h instead of
>> tssdcore.c, you can get sdcore.h and sdcore.o here
>>
>
> nope, doesn't work. see my other post. in brief, tssdcore.c uses
> structure members that aren't defined in sdcore.h, it uses deprecated
> routines, and sdcore.o won't link with an EABI .o file.
>
> I'm going to recommend to my clients that in future projects they
> avoid proprietary (i.e. undocumented) hardware interfaces at all costs.
>
Unfortunately that's the price you have to pay for fully functional
SecureDigital interfaces right now... They're _very_ protective of the
standard and make everyone sign a NDA for gets even a glimpse of the
internals. You can of course use a MMC interface, but won't get
anywhere near the same throughput nor the security features.
Jason Stahls
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|