Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > USB Controllers > Memory size of Cypress FX3 hardware-driver

Bookmark and Share
Cypress Developer CommunityTM
Forums | Videos | Blogs | Training | Rewards Program | Community Components



Memory size of Cypress FX3 hardware-driver
Moderator:
RSKV

Post Reply
Follow this topic



Memory size of Cypress FX3 hardware-driver

RobK posted on 20 Apr 2012 12:03 AM PST
Top Contributor
56 Forum Posts

Hi,

I'd like to know how much memory the FX3 hardware-driver uses from the 512KB SRAM-size (besides the 12KB initial stack and DMA-descriptors)? So how large is the code- and data-size and how much heap and stack is roughly used by the driver?

I want to roughly calculate the remaining memory size which can be used by user-specific firmware.

 

Regards,

Robert




Re: Memory size of Cypress FX3 hardware-driver

aasi posted on 23 Apr 2012 01:31 AM PST
Cypress Employee
1073 Forum Posts

There is just a firmware framework running on FX3 so your usage of the word hardware driver is little confusing. Are you talking about the threadX running on it?
 



Re: Memory size of Cypress FX3 hardware-driver

RobK posted on 23 Apr 2012 09:46 AM PST
Top Contributor
56 Forum Posts

No, I mean the FX3-firmware framework including the API's provided by Cypress!



Re: Memory size of Cypress FX3 hardware-driver

Chris R. posted on 23 Apr 2012 10:53 AM PST
Top Contributor
135 Forum Posts

The firmware framework IS the TheadX real time operating system running on the ARM core extended by the Cypress USB API functions.



Re: Memory size of Cypress FX3 hardware-driver

RobK posted on 25 Apr 2012 04:16 AM PST
Top Contributor
56 Forum Posts

However it is called, but does anybody know how much memory the framework occupies roughly?

 

Thanks!



Re: Memory size of Cypress FX3 hardware-driver

RobK posted on 07 May 2012 01:04 AM PST
Top Contributor
56 Forum Posts

No one any idea?

The size of .txt + .data - sections of the FX3-framwwork I assume to be ~130KB by compiling the simple bulk loop auto - example.

But what about the size of the dynamic memory (stack, heap etc.) the FX3-framework uses?



Re: Memory size of Cypress FX3 hardware-driver

Sil posted on 31 May 2012 06:28 AM PST
Top Contributor
93 Forum Posts

I am also interested to know the maximum buffer size for the DMA channels. As long as I use equal or less than 128 kB for my DMA buffers it is working fine. However, as soon as I try to use more, the FX3 won't enumerate anymore.

 

On the other hand there are 512 kB RAM, where the application code uses roughly 130 kB, So there should be 254 kB still available, and the question is how much the RTOS is using.

 

Anybody some more information on this? Thanks.

 

-Silvio



Re: Memory size of Cypress FX3 hardware-driver

Sil posted on 31 May 2012 06:47 AM PST
Top Contributor
93 Forum Posts

It's all ok: I found a nice figure in the FX3 programmers manual (p. 54) that explains everything.






ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". CYPRESS SEMICONDUCTOR AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY CYPRESS SEMICONDUCTOR. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM CYPRESS SEMICONDUCTOR.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms and Conditions of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms and Conditions of this site. Cypress Semiconductor and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.