Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > USB Controllers > Several questions about FX3 firmware library

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



Several questions about FX3 firmware library
Moderator:
RSKV

Post Reply
Follow this topic



Several questions about FX3 firmware library

jtzheng posted on 23 Mar 2012 1:30 AM PST
Member
5 Forum Posts

  Reading the FX3API Guide for the APIs of the FX3 firmware libraries...several questions:

*. There's seem no high resolution timer, the OS timer is too "coarse" for many embedded applications, e.g. my application needs a 1ms timer as a "heart beating" timer...and it needs a "micro-second" level one-shot timer to arrange something after the occurrance of a certain external event. Of course, external hardware might help ....but is there any way to do that without other hardware? Understood that for FX3, there's an OS there, but is there any "Native Timer" device which can provide such services (ISR call back based) as other device driver.

*. Interrupt priority, FX3 device drivers (in libraries) handle all the ISR and call user installed callback, there seem no way for user to customize the prority (FIQ or IRQ for a certain device).

*. Big code size, it seems that a very simple sample code uses ~128KB ( ~100KB for release version, there're lots of library codes included) code space, so it needs 2x 128KByte eeproms (or 3x 64KBytes eeproms) in almost all eeprom based devices, is there any considertaion that a third party "high efficiency" compiler/linker (e.g. from Keil) can be used (and the libraries have to be re-built)?

Thanks!

 




Re: Several questions about FX3 firmware library

aasi posted on 26 Mar 2012 01:46 AM PST
Cypress Employee
1073 Forum Posts

Hi,

The timer tick specification of 1ms +/- 4%. Using a complex GPIO you can implement a one-shot, the API guide has details about the same.

I'll check on the interrupt priority with our software team and let you know.

There is a RTOS being run and the application firmware runs on it. The larger firmware size is due to this. We're looking at this as well, will keep everyone posted through the forum.

Regards,

Anand

 






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.