1. Cypress CY3663 Development Kit
Zach Fister
Sri Harsha Yenuganti
April, 2008
Cypress Dev Kit

2. CY3663 Dev Kit Contents
Single Board Computer (SBC) with StrongARM processor for coprocessor operation
CY7C67300
EZ-Host Development Board
CY7C67200
EZ-OTG Development Board
Cypress Dev Kit

3. StrongArm Board Cypress Dev Kit 1
1. All figures from “USB Multi-Role Device Design by Example” by John Hyde

4. Coprocessor Operation
Coprocessor Operation Handles all of the low-level USB communications on behalf of the external processor.
Parallel I/O :
Link Control Protocol ( LCP )
Serial I/O :
High Speed Serial ( HSS ), I2C, SPI
Cypress Dev Kit

5. Standalone boards
Cypress Dev Kit

6. EZ-Host / EZ-OTG Diagram
Cypress Dev Kit

7. Firmware Architecture
Firmware Architecture The BIOS sets up an event-driven environment with chained idle tasks.
Cypress Dev Kit

8. FW Architecture Event driven
Button push, packet-type, etc.
Application specific callback tasks can be fairly easily inserted into code
Cypress Dev Kit

9. Firmware Features
EZ-Host and EZ-OTG components are software compatible and use the same BIOS.
The BIOS is organized as a set of subroutines that are accessed via an interrupt vector table in low memory.
The BIOS is designed to be override able in whole or in parts.
There are several unassigned vectors where you can add additional capability and you can change existing vectors to change how BIOS operates.
Cypress Dev Kit

10. Application Development
All firmware that we develop for the EZ-Host/EZ-OTG will follow this format of Init_Task, Idle_Task and Callbacks.
The Init_Task is responsible for setting up the Idle_Task and any CallBack_Tasks.
All of the Idle_Tasks are dynamically linked together. When not serving interrupts, the Idle_Task of each software subsystem runs and looks for work to do. Each subsystem calls the next using the chaining mechanism.
CallBack_Tasks are procedures that are run as a result of some event occurring. This event could be a hardware interrupt, a software interrupt.
Cypress Dev Kit

11. Application Development
INT70 Start of Idle Chain
INT71 BIOS’s Idle Task
INT72 Insert task into Idle Chain
Cypress Dev Kit

12. Examples 1) Hello World 2) Scan Records
Example code run via remote debugger on EZ-Host Dev. Board
2) Scan Records
Change BIOS operation on power-up to change default port configuration
Program EEPROM via I2C
Cypress Dev Kit

13. Examples 3) and 4) Buttons and Lights Device 5) Standalone Device
Simple Human Interface Device
Debugger run program
Host program or board button pushes update both displays
5) Standalone Device
Scanwrap utility creates scan record from binary file
Programmed into EEPROM to run standalone
Cypress Dev Kit

14. Examples 6) Standalone Host and Device
Both EZ-Host and EZ-OTG communicating in standalone mode
Cypress Dev Kit

15. Things to Try Next Understand the program execution flow.
Modify code in “Hello World” example to initiate different action on button presses
HW Analyzer to view differences in transfers on different endpoints between host/device
Need updated driver on lab PCs?
Analyze remote camera capture USB traffic for a simple transfer and attempt to emulate with modification of existing examples
Cypress Dev Kit