• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 696 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/TM4C123GH6PM: USB DEV MSC - About transfer speed from USB to SD

Alberto Stolowich
Prodigy 60 points

Part Number: TM4C123GH6PM

Tool/software: Code Composer Studio

Hi, 

I made the project based on the example of dk-tm4c123g \ usb_dev_msc, to manage an SD card from the PC, I find that the transfer speed is always constant and is 355KB/s. Is there any way to make it work at what sets USB2.0 to around 12Mbps?

Thanks and regards!

  • 0
    Guru 117855 points

    Alberto Stolowich said:
    Is there any way to make it work at what sets USB2.0 to around 12Mbps?

    I cannot advise for - this class MCU (M4) - from this vendor - but am able to suggest a, "General, Info Extracting, (potential) Solution."     (firm/I have primarily shifted to more capable, far faster, Cortex M7)

    • Is your objective w/in "reason?"     (you seek "around" a "12 / 0.355 (34x)" performance boost - such is NOT "in the cards."     Unknown then is, "What "speed-up" IS possible?")

    • Might the current speed limitation result from:
      • limitations w/in your 4C123 MCU
      • limitations w/in your PC
      • the above two - in combination

     it would serve you to "first" learn the speed capability of your PC - and under which circumstances - that may be obtained.

    • you may accomplish the above by obtaining an external device which (clearly) is able to meet your speed objective - and then measure/confirm that fact.    (minus that detail - any  limitation w/in your 4C123 proves "uncertain/unproved."     (thus unsatisfying)
    • moving toward your MCU's speed optimization - how have you (or have you) measured and noted the effects of: 
      • transfer size
      • transfer priority
      • prevention of transfer "breaks and/or other delays/restrictions" - potentially caused by (other) code running upon your MCU  

    The intent here is to alert you to the fact that "other factors may be "in play"" - and for the need to fully/properly examine the totality of the transfer system - not just one (assumed) "roadblock" part...