TM4C1294NCPDT: TM4C129DNCPDT: FATSD and FATSDRAW

Hello Richard,

I am not certain either for that - I don't think that is part of TivaWare. If it's part of TI-RTOS for Tiva-C we were not involved in building that and the offering provided isn't something I can help answer. Though I don't really know who to direct this to either.

As far as:

richard payne said:

The fatsdusbcopy which is based on?

From what I can see it it is using the USBMSCHFatFs driver and that driver seems to be using just standard 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(&params);
 *  params.servicePriority  = somePriority;
 *  handle = USBMSCHFatFs_open(someUSBMSCHFatFs_configIndexValue, &params);
 *  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

Best Regards,

Ralph Jacobi