Synergy Demo. USB Host and Device

Transcription

1 Synergy Demo 1. Introduction This Demo illustrates the communication between the two SK-Kits over USB: one SK-Kit uses its USB Host and the other uses its USB Device. One kit sends the actual time and the information of sine curve to the other every second, and other receives them in time, so that there are the same time and sine curve on the displays of the both kits. The application also includes key elements to demonstrate how they work together in a typical design, including: ThreadX RTOS,, LCD driver, GUI design/ animation, etc Connect to the Board This section describes how to connect the board to power, the J-Link debugger to the PC, and the connection of the both kits. Refer to the Quick Start Guide for PE-HMI1, DK-S7G2, DK-S3A7, or SK-S7G2 for setting up the power connection and the J-link debugger connection from your PC to the JTAG connector on the target board 1. Connect the both kits together. The both kits connect with each other over USB, Please see abobe figure.

2 Every Sk-kit has two USB devices (J5 and J19) and one USB Host interface (J6), the J6 of one kit is connected with J5 of the other over USB cable. 3. Import the Project into e2 studio These zipped demo project files can be copied from: XXX 1 Refer to the "Synergy Project Import Guide" 1 (r11an0023eu0100_synergy_ssp.pdf) for instructions on importing the project into e2 Studio and building/running the project. When debugging, use the USB_Device Debug USB_Host Debug configuration. Please pay attention: the kit who uses USB Host should be flashed with the image of USB_Host project, and the other with the image of USB_Device project. If they are reversed, they don t work! The following tools should be used for compile and debug: e2 studio V SSP V1.1.0 GNU V GUIX V

3 4. Architecture and function description A high-level view of the architecture of this application is shown below. 4.1 Architecture of Device RTC Thread Time update: TimeUpdate() Events to HMI Thread: gx_system_event_send() Info to HOST: _ux_device_class_cdc_acm_write() HMI Thread Events receiving, text update, display update: optional1() Sine chart drawing: chart_window_draw() 4.2 Architecture of HOST Demo Thread Info from Device: ux_host_class_cdc_acm_read () Events to HMI Thread: gx_system_event_send() HMI Thread Events receiving, text update, display update: optional1() Sine chart drawing: chart_window_draw() 4.3 Function description of the Device In the device of this demo, the RTC Thread and HMI thread are added.

4 In RTC Thread, the function tx_application_define_user() initiates the USB device; the function rtc_thread_entry() provides a system clock from RTOS that the function TimeUpdate() uses to generate the new clock and sine information, it sends also an event with the clock and sine chart information to the HMI thread every second through using system function gx_system_event_send(), at the same time, it sends also this clock and sine chart information to USB Host through USB interface through calling function _ux_device_class_cdc_acm_write(). In HMI Thread, the function options1() receives the events that come from RTC Thread, and from them it gets the clock information and shows them on TFT in time; at the same time, through calling the function chart_window_draw() and using the information coming from RTC Thread it updates the sine chart which moves left about PI/6 at every update. 4.4 Function description of the Host In the Host of this demo, the RTC Thread and HMI thread are added. In RTC Thread, the function tx_application_define_user() initiates the USB Host, the function tx_demo_class_cdc_acm_get() decides whether the USB Host is used; in the function rtc_thread_entry(), through calling the ux_host_class_cdc_acm_read() continuously, the Host gets the new clock and sine chart information every second which are also sent to the HMI thread every second through using system function gx_system_event_send(), In HMI Thread, the function options1() receives the events that come from RTC Thread, and from them it gets the clock information and shows them on TFT in time; at the same time, through calling the function chart_window_draw() and using the information coming from RTC Thread it updates the sine chart which moves left about PI/6 at every update. 4.5 Function description of GUI and LCD The screen of the both Device and Host is same, so their GUI design and their software are also same. Through using the GUIX, the screen is defined which includes the both widgets Text und window which are used to show the clock information and sine chart, it includes also a wallpaper on which our company symbol is showing. To display the text and the sine chart, some GUI functions are used such as gx_canvas_line_draw, gx_prompt_text_set, gx_system_dirty_mark, etc.. To use the TFT and GUI, man should at first initiate them, which can be seen in function hmi_thread_main().

5 5. Application Features This section describes the key features of this demo application and the steps needed to run the application. This demonstration application illustrates the communication between the two SK-Kits over USB through these four functions: Create a USB Host interface and write its application software in one kit Create a USB Device interface and write its application software in other kit Write the software to display a clock and the sine curve on the LCD of the both kits Synchronize the time and the sine curve in both kits To run the demonstration application: 1. Click Resume twice. 2. If the connection is broken, on one kit the time and the sine curve are updated every second, but on the other kit, the both information are frozen; after the both kits are connected again, the time and the sine curve are updated on both kids every second and these information should be always identified. 3. Click Terminate to close the debugger. 1. If you have any questions or want to get the source code of this demo, please do not hesitate to contact Mr. Weizhong Xu, Weizhong.Xu@rutronik.com.