User guide

CY3687 MoBL-USB FX2LP18 Development Kit User Guide, Doc. # 001-68582 Rev. *B 81
MoBL-USB Development Kit Firmware Examples
for( i = 0x0000; i < count; i++ )
{
EXTAUTODAT2 = EXTAUTODAT1;
}
// Source is external RAM
APTR1H = 0x28;
APTR1L = 0x00;
// Destination is EP6IN
AUTOPTRH2 = MSB( &EP6FIFOBUF );
AUTOPTRL2 = LSB( &EP6FIFOBUF );
count = (EP2BCH << 8) + EP2BCL;
for( i = 0x0000; i < count; i++ )
{
EXTAUTODAT2 = EXTAUTODAT1;
}
EP6BCH = EP2BCH;
SYNCDELAY;
EP6BCL = EP2BCL; // arm EP6IN
SYNCDELAY;
EP2BCL = 0x80; // re(arm) EP2OUT
}
}
Similarly endpoint EP4 destination and EP8 source buffer is commonly defined as the external RAM
memory-0x2A00.
8.7.2 Building Bulkext fIrmware Example Code for MoBL-USB FX2LP Internal RAM
Memory and EEPROM
Click on Build Target button at the top right corner of the IDE. The total Code bytes of Bulkext firm-
ware example is less than 4k code limit Keil uVision2 IDE provided along with the kit. The output of
the Build Target is bulkext.hex and bulkext.iic files.
8.7.3 Method to Download Firmware Image to MoBL-USB FX2LP18 Internal RAM and
EEPROM
Refer to section Method to Download Firmware Image to MoBL-USB Internal RAM Memory on
page 62 and Method to Download Firmware Image to External I2C EEPROM on page 63 and follow
similar procedure to download bulkext.hex to RAM memory and bulkext.iic to Large EEPROM
using Cyconsole/CyControlCenter. The bulkext.hex and bulkext.iic files are located at
<Installed_directory>\<Version>\Firmware\Bulkext. After downloading, the firmware re-enumerates
with PC using its internal VID/PID-0x04B4/0x1004.
8.7.4 Binding Cypress USB Driver for the Downloaded Firmware Image
The Bulkext firmware uses vendor class (0xFF) with VID/PID-0x04B4/1004.This example should
bind with Cypress generic USB driver cyusb.sys and driver information file cyusbfx2lp18.inf which
contains the relevant VID/PID of this example. Follow the procedure outlined in section Binding