tutorials:dvk521:documentations:dvk521_user_manual
Differences
This shows you the differences between two versions of the page.
|
tutorials:dvk521:documentations:dvk521_user_manual [2013/11/21 15:23] waveshare |
tutorials:dvk521:documentations:dvk521_user_manual [2013/12/23 14:50] (current) |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| ===== API and Drivers Source code ===== | ===== API and Drivers Source code ===== | ||
| *The API and Drivers source code of DVK521 can be found on | *The API and Drivers source code of DVK521 can be found on | ||
| - | *[[http://dl.cubieboard.org/parteners/waveshare/Source_Code/sunxi-bsp/Driver and API/|Driver and API]] | + | *[[http://dl.cubieboard.org/parteners/waveshare/Source_Code/Driver and API/|Driver and API]] |
| *Also are accessible in the SD card image: | *Also are accessible in the SD card image: | ||
| */home/linaro/waveshare_demo/ | */home/linaro/waveshare_demo/ | ||
| Since driver compiling relies on the kernel, if you need to compile our source code, you should modify the related Makefile according to your own kernel path, then execute: | Since driver compiling relies on the kernel, if you need to compile our source code, you should modify the related Makefile according to your own kernel path, then execute: | ||
| - | == # make == | + | # make |
| - | For more info, please refer to the appendix of the document [[tutorials:DVK521:Documentations:Driver Porting and Configuration|Drivers Porting and Configuration]]. | + | For more info, please refer to the document [[tutorials:DVK521:Documentations:Driver Porting and Configuration|Drivers Porting and Configuration]]. |
| Line 31: | Line 31: | ||
| Use the following command to check if USB0 or USB1 exists: | Use the following command to check if USB0 or USB1 exists: | ||
| - | == # ls /dev/ttyUSB* == | + | # ls /dev/ttyUSB* |
| /dev/ttyUSB0 | /dev/ttyUSB0 | ||
| Use the screen command to establish connection: | Use the screen command to establish connection: | ||
| - | == #screen /dev/ttyUSB0 115200 == | + | #screen /dev/ttyUSB0 115200 |
| You may want to install the screen command first in case it doesn't exist: | You may want to install the screen command first in case it doesn't exist: | ||
| - | == #apt-get install screen == | + | #apt-get install screen |
| If the Cubieboard has started up, press Enter key to enter command terminal, the default user should be root. | If the Cubieboard has started up, press Enter key to enter command terminal, the default user should be root. | ||
| In case nothing happens when pressing Enter, try to disconnect and reconnect the USB port on Cubieboard, execute the following command again: | In case nothing happens when pressing Enter, try to disconnect and reconnect the USB port on Cubieboard, execute the following command again: | ||
| - | == #screen /dev/ttyUSB0 115200 == | + | #screen /dev/ttyUSB0 115200 |
| Press Enter until any info displayed on the serial port monitor. | Press Enter until any info displayed on the serial port monitor. | ||
| Line 59: | Line 59: | ||
| Burn the provided image into your SD card, when the system startups, connect the board to PC through a USB-to-serial-port cable, then launch the console terminal. | Burn the provided image into your SD card, when the system startups, connect the board to PC through a USB-to-serial-port cable, then launch the console terminal. | ||
| The root permission should be gained by default. In fact, all of the following demos are running under root permission. In case any command can't be executed or any error occurs, it might be that you are not proceeding under root permission, try to switch user using the following command: | The root permission should be gained by default. In fact, all of the following demos are running under root permission. In case any command can't be executed or any error occurs, it might be that you are not proceeding under root permission, try to switch user using the following command: | ||
| - | == $ su root == | + | $ su root |
| Then enter the password: | Then enter the password: | ||
| - | == $ 123456 == | + | $ 123456 |
| It is recommended that disconnect every module after testing to avoid port conflicting. | It is recommended that disconnect every module after testing to avoid port conflicting. | ||
| Line 68: | Line 68: | ||
| The default option is LCD mode, use related command to select other display mode. | The default option is LCD mode, use related command to select other display mode. | ||
| For VGA mode, use: | For VGA mode, use: | ||
| - | == $ test_vga == | + | $ test_vga |
| For LCD mode , use: | For LCD mode , use: | ||
| - | == $ test_lcd == | + | $ test_lcd |
| For HDMI mode, use: | For HDMI mode, use: | ||
| - | == $ test_hdmi == | + | $ test_hdmi |
| After executing the above commands, the board will reboot automatically to apply the new display mode. | After executing the above commands, the board will reboot automatically to apply the new display mode. | ||
| Line 85: | Line 85: | ||
| === OV7670 Demo === | === OV7670 Demo === | ||
| Connect the OV7670 module into the OV7670 interface, connect the 7inch capacitive touch LCD. Enter the following command on the console terminal: | Connect the OV7670 module into the OV7670 interface, connect the 7inch capacitive touch LCD. Enter the following command on the console terminal: | ||
| - | == $ test_camera == | + | $ test_camera |
| The video stream is supposed to be seen on the LCD, and the focal length is also adjustable (in case the screen becomes messing up, reboot the system). Press Ctrl+C to stop. | The video stream is supposed to be seen on the LCD, and the focal length is also adjustable (in case the screen becomes messing up, reboot the system). Press Ctrl+C to stop. | ||
| Line 97: | Line 97: | ||
| Short the onboard LED jumpers. | Short the onboard LED jumpers. | ||
| Enter the following command: | Enter the following command: | ||
| - | == $ test_led == | + | $ test_led |
| You will see the 8 LEDs light up one by one every second. Press Ctrl+C to stop. | You will see the 8 LEDs light up one by one every second. Press Ctrl+C to stop. | ||
| === 8 Push Buttons Demo === | === 8 Push Buttons Demo === | ||
| Connect the 8 Push Buttons accessory board to the onboard 8I/O s interface (The OV7670 module and the push button module share certain same pins, disconnect the OV7670 module while testing the push button). | Connect the 8 Push Buttons accessory board to the onboard 8I/O s interface (The OV7670 module and the push button module share certain same pins, disconnect the OV7670 module while testing the push button). | ||
| Enter the following command: | Enter the following command: | ||
| - | == $ test_key == | + | $ test_key |
| Press any of the 8 push buttons, related value will be displayed on the console terminal. Press Ctrl+C to stop. | Press any of the 8 push buttons, related value will be displayed on the console terminal. Press Ctrl+C to stop. | ||
| Line 108: | Line 108: | ||
| Short the onboard buzzer jumper. | Short the onboard buzzer jumper. | ||
| Enter the following command: | Enter the following command: | ||
| - | == $ test_buzzer == | + | $ test_buzzer |
| The buzzer will start to make sound and stop later. | The buzzer will start to make sound and stop later. | ||
| Line 116: | Line 116: | ||
| Insert the DS18B20 into the 1-WIRE socket, short the onboard 1-WIRE jumper (ensure that the AT45DBXX DataFlash Board has been disconnected). | Insert the DS18B20 into the 1-WIRE socket, short the onboard 1-WIRE jumper (ensure that the AT45DBXX DataFlash Board has been disconnected). | ||
| Enter the following command: | Enter the following command: | ||
| - | == $ cd /sys/bus/w1/devices/ == | + | $ cd /sys/bus/w1/devices/ |
| - | == $ ls == | + | $ ls |
| There's a folder with the name looks like "28-0000054a5bec " (the last 7 characters is a unique device ID of every different DS18B20, in this case, the device ID is 54a5bec). | There's a folder with the name looks like "28-0000054a5bec " (the last 7 characters is a unique device ID of every different DS18B20, in this case, the device ID is 54a5bec). | ||
| Enter the following command: | Enter the following command: | ||
| - | == $ test_ds18b20 54a5bec == | + | $ test_ds18b20 54a5bec |
| The current environment temperature will be displayed on the console terminal. | The current environment temperature will be displayed on the console terminal. | ||
| Line 126: | Line 126: | ||
| Connect the AT45DBXX DataFlash Board to the onboard SPI interface | Connect the AT45DBXX DataFlash Board to the onboard SPI interface | ||
| Enter the following command: | Enter the following command: | ||
| - | == $ test_at45db == | + | $ test_at45db |
| Data will be read and displayed on the console terminal. | Data will be read and displayed on the console terminal. | ||
| Line 132: | Line 132: | ||
| Connect the AT24/FM24 module to the onboard I2C interface. | Connect the AT24/FM24 module to the onboard I2C interface. | ||
| Enter the following command: | Enter the following command: | ||
| - | == $ test_at24c04 –w == | + | $ test_at24c04 –w |
| Data will be written into the device and displayed on the console terminal. | Data will be written into the device and displayed on the console terminal. | ||
| - | == $ test_at24c04 –r == | + | $ test_at24c04 –r |
| Data will be read from the device and displayed on the console terminal. | Data will be read from the device and displayed on the console terminal. | ||
tutorials/dvk521/documentations/dvk521_user_manual.1385018600.txt.gz · Last modified: 2013/12/23 14:50 (external edit)
Page Tools
