Hi Travis,
If I understand your question fully (Being able to connect tower MCU with USB device MSD enabled so that a file from a PC can be copied to the tower MCU ramdisk. Then copy/move it from SRAM to some other location. Correct?).
I'm using the TWR-K60D100M with TWR-MEM card that has MRAM.
I modified the msd_disk_twrk60d100m example to also mount the MRAM as MFS.
C:\Freescale\Freescale_MQX_4_0\usb\device\examples\msd\disk
Actually the application is always opening up the ram disk and checking if it is formatted or not. I just choose to ignore the MQX application and use the PC to load the ram disk with file as shown below. So at this point in time both the MQX application and PC want to format the ram disk. I choose to have the PC app do it for this example (read observations below).
When the application first runs, I plug the TWR USB cable to PC, PC will want to format it, I format it, then copy (drag-n-drop) a file to the TWR ram disk.




I now eject the USB disk and disconnect the USB cable from PC and do a POR (power on reset) of the TWR.
The application will then see the ram disk with MFS and see that it has been formatted.
Using the serial concole I can copy/move the file from ram disk to MRAM.

Note the "a:" is the ram disk and "b:" is the MRAM disk.
Please note this is currently a hack and just proves that it can be done. I'm sure others can enhance it to better respond to USB attach/detach events so as not to have to do a POR to refresh the FAT table.
Observations:
When formatting the ram disk with Win7 64-bit machine, it initially sees the drive as 30KBytes but after the format only 10KBytes is present. I'm guessing extra overhead of Windows formatting???
When I format using the MQX application I get the expected 25KBytes. If Windows looks at this ram disk it does see all 25KBytes. So clearly we have a difference in formatting the FAT32 from MQX to Windows.
My project source is attached for disk.c and Shell_Task.c (file I added to the project). Also I had to add MFS and Shell libraries to the project "properties" paths for compiler and linker.
Regards,
David