Cypress EZ-USB® FX3™ SDK Quick Start Guide, Version 1.3.1 32
1. No code changes should be required in user applications while porting from
SDK 1.2.1 to SDK 1.2.2. However, it is possible that the memory footprint of
an application be increased when using the SDK 1.2.2. This happens
because of some additional error checks that have been added to the
ThreadX OS services used in the SDK.
This increase in footprint can be offset through the use of the “-Wl,--gc-
sections” linker command line flag. The FX3 libraries in SDK 1.2.2 have
been updated to compile each function into a separate section; so that the
use of the above option can give significant footprint reduction.
All of the Eclipse projects in the SDK have been updated to include this
linker flag. The following Eclipse UI screenshot shows the place where this
linker flag can be updated.
Figure 5-1: Eclipse Linker Flag Settings
2. SDK 1.2.2 provides USB event notifications when it detects the connection
or removal of a valid voltage on the USB Vbus pin. These events are
provided even if the CyU3PConnectState() API has not been called.
It is possible for a self-powered FX3 application to wait until the Vbus
voltage is available before enabling the USB connection through the
CyU3PConnectState() API.