请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。
器件型号:TM4C1294NCPDT 你(们)好
我很难在 TI 文档和 FATFS 网站上找到参考资料、以解释 FATSD 和 FASTDRAW 之间的区别。
基于的 fatsdusbcopy?
谢谢
R.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
你(们)好
我很难在 TI 文档和 FATFS 网站上找到参考资料、以解释 FATSD 和 FASTDRAW 之间的区别。
基于的 fatsdusbcopy?
谢谢
R.
您好 Richard、
我也不确定-我认为这不是 TivaWare 的一部分。 如果它是用于 Tiva-C 的 TI-RTOS 的一部分、我们不参与构建、提供的产品是我无法回答的问题。 虽然我不知道是谁将其引导至哪个位置。
就以下方面而言:
[引用 userid="114962" URL"~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1038635/tm4c1294ncpdt-tm4c129dncpdt-fatsd-and-fatsdraw "] 基于以下内容的 fatsdusbcopy?我可以看到、它使用 USBMSCHFatFs 驱动程序、该驱动程序似乎仅使用标准 FatFs:
* The USBMSCHFatFs header file should be included in an application as follows: * @code * #include <ti/drivers/USBMSCHFatFs.h> * @endcode * * # Operation # * * The USBMSCHFatFs driver is a driver designed to hook into FatFs. It * implements a set of functions that FatFs needs to call to perform basic * block data transfers. * * This driver is designed to work with the USB Library. Because it is running * in host mode, we need to add protection when accessing the USB Library. A * gate was added to prevent the task servicing the USB library to preempt any * other task accessing the USB Library. * * Once the driver has been opened, the application may used the FatFs APIs or * the standard C runtime file I/O calls (fopen, fclose, etc...). Once the * driver has been closed, ensure the application does NOT make any file I/O * calls. * * ## Opening the driver # * * @code * USBMSCHFatFs_Handle handle; * USBMSCHFatFs_Params params; * * USBMSCHFatFs_Params_init(¶ms); * params.servicePriority = somePriority; * handle = USBMSCHFatFs_open(someUSBMSCHFatFs_configIndexValue, ¶ms); * if (!handle) { * System_printf("USBMSCHFatFs did not open"); * } * @endcode * * # Implementation # * * This module serves as the main interface for TI-RTOS * applications. Its purpose is to redirect the module's APIs to specific * peripheral implementations which are specified using a pointer to a * USBMSCHFatFs_FxnTable. * * The USBMSCHFatFs driver interface module is joined (at link * time) to a NULL-terminated array of USBMSCHFatFs_Config data structures * named *USBMSCHFatFs_config*. *USBMSCHFatFs_config* is implemented in the * application with each entry being an instance of a USBMSCHFatFs peripheral. * Each entry in *USBMSCHFatFs_config* contains a: * - (USBMSCHFatFs_FxnTable *) to a set of functions that implement a * USBMSCHFatFs peripheral * - (void *) data object that is associated with the USBMSCHFatFs_FxnTable * - (void *) hardware attributes that are associated to the * USBMSCHFatFs_FxnTable
此致、
Ralph Jacobi