tutorials:dvk521:documentations:a10:driver_porting_and_configuration
Differences
This shows you the differences between two versions of the page.
|
tutorials:dvk521:documentations:a10:driver_porting_and_configuration [2013/11/26 13:52] waveshare [Porting I/O Control Driver] |
tutorials:dvk521:documentations:a10:driver_porting_and_configuration [2014/03/13 14:26] (current) waveshare |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| The I/O control driver is built as a module, can be used for controlling common peripherals, such as LED, push button, buzzer. | The I/O control driver is built as a module, can be used for controlling common peripherals, such as LED, push button, buzzer. | ||
| - | Copy [[http://dl.cubieboard.org/parteners/waveshare/Source_Code/A10/Driver%20and%20API/Driver/|io_control_dev]] to your ubuntu system, compile it with your own system setting (refer to Appendix 1 "Compiling Driver Module"), and copy the generated io_control.ko file to the board, use the following command to load the driver module: | + | Copy [[http://dl.cubieboard.org/parteners/waveshare/Source_Code/a10-cubieboard-dvk/Driver%20and%20API/Driver/|io_control_dev]] to your ubuntu system, compile it with your own system setting (refer to Appendix 1 "Compiling Driver Module"), and copy the generated io_control.ko file to the board, use the following command to load the driver module: |
| $insmod io_control.ko | $insmod io_control.ko | ||
| Now you can start to try the I/O control API demo (refer to Appendix 2 "Running API Demo"). | Now you can start to try the I/O control API demo (refer to Appendix 2 "Running API Demo"). | ||
| Line 31: | Line 31: | ||
| Save and exit, re-compile the kernel: | Save and exit, re-compile the kernel: | ||
| #make uImage | #make uImage | ||
| - | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| === Config the script.fex === | === Config the script.fex === | ||
| Config the script.fex as follows, add the [w1_para] setting: | Config the script.fex as follows, add the [w1_para] setting: | ||
| Line 37: | Line 37: | ||
| w1_used = 1 | w1_used = 1 | ||
| w1_pin = port:PB10<1><default><default><default> | w1_pin = port:PB10<1><default><default><default> | ||
| - | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| Reboot the system, insert the DS18B20 device. | Reboot the system, insert the DS18B20 device. | ||
| - | Copy [[http://dl.cubieboard.org/parteners/waveshare/Source_Code/Driver%20and%20API/Driver/|ds18b20l_dev]] to your ubuntu system, compile it with your own system setting (refer to Appendix 1 "Compiling Driver Module"), and copy the generated w1-sunsi.ko file to the board, use the following command to load the driver: | + | Copy [[http://dl.cubieboard.org/parteners/waveshare/Source_Code/a10-cubieboard-dvk/Driver%20and%20API/Driver/|ds18b20_dev]] to your ubuntu system, compile it with your own system setting (refer to Appendix 1 "Compiling Driver Module"), and copy the generated w1-sun4i.ko file to the board, use the following command to load the driver: |
| - | $insmod io_control.ko | + | $insmod w1-sun4i.ko |
| Enter the /sys/bus/w1/devices/w1_bus_master1 directory, there's a folder with the name preceding with "28-", which represents the DS18B20 device. The 28 means the current temperature sensor is DS18B20, the characters/numbers string follows stands for the device unique ID. Enter the folder, you should find it's device file named w1_slave, to get current temperature, enter this command on the terminal: | Enter the /sys/bus/w1/devices/w1_bus_master1 directory, there's a folder with the name preceding with "28-", which represents the DS18B20 device. The 28 means the current temperature sensor is DS18B20, the characters/numbers string follows stands for the device unique ID. Enter the folder, you should find it's device file named w1_slave, to get current temperature, enter this command on the terminal: | ||
| Line 48: | Line 48: | ||
| As shown in the picture below: | As shown in the picture below: | ||
| - | {{.:Documentations-6_1.jpg}} | + | {{..:Documentations-6_1.jpg}} |
| ==== Porting I2C Bus Driver ==== | ==== Porting I2C Bus Driver ==== | ||
| Line 74: | Line 74: | ||
| twi1_scl = port:PB18<2><default><default><default> | twi1_scl = port:PB18<2><default><default><default> | ||
| twi1_sda = port:PB19<2><default><default><default> | twi1_sda = port:PB19<2><default><default><default> | ||
| - | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| Reboot the system. | Reboot the system. | ||
| - | For more info about testing the AT24/FM24 module, like reading/writing data, please refer to the document [[tutorials:DVK521:Documentations:DVK521 User Manual|DVK521 User Manual]] and Appendix 2 "Running API Demo". | + | For more info about testing the AT24/FM24 module, like reading/writing data, please refer to the document [[tutorials:DVK521:Documentations:A10:DVK521 User Manual|DVK521 User Manual]] and Appendix 2 "Running API Demo". |
| Line 93: | Line 93: | ||
| Save and exit, re-compile the kernel: | Save and exit, re-compile the kernel: | ||
| #make uImage | #make uImage | ||
| - | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| === Config the script.fex === | === Config the script.fex === | ||
| Line 116: | Line 116: | ||
| full_duplex = 0 | full_duplex = 0 | ||
| manual_cs = 0 | manual_cs = 0 | ||
| - | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| Now the kernel and script.fex configuration for SPI device have completed, the last step is to load the io_control.ko driver module (refer to the previous section " Porting I/O Control Driver"). | Now the kernel and script.fex configuration for SPI device have completed, the last step is to load the io_control.ko driver module (refer to the previous section " Porting I/O Control Driver"). | ||
| Line 140: | Line 140: | ||
| Save and exit, re-compile the kernel: | Save and exit, re-compile the kernel: | ||
| #make uImage | #make uImage | ||
| - | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| === Config the script.fex === | === Config the script.fex === | ||
| Line 259: | Line 259: | ||
| Re-compile the kernel: | Re-compile the kernel: | ||
| #make uImage | #make uImage | ||
| - | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| === Config the script.fex === | === Config the script.fex === | ||
| Line 290: | Line 290: | ||
| ctp_wakeup = port:PB13<1><default><default><1> | ctp_wakeup = port:PB13<1><default><default><1> | ||
| ctp_io_port = port:PH7<0><default> | ctp_io_port = port:PH7<0><default> | ||
| - | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| Connect the 7inch capacitive LCD, reboot the system, try to touch the icons on the screen. | Connect the 7inch capacitive LCD, reboot the system, try to touch the icons on the screen. | ||
| Line 377: | Line 377: | ||
| sun4i_csi1.ko: | sun4i_csi1.ko: | ||
| /lib/modules/3.4.61+/kernel/drivers/media/video/sun4i_csi/csi1 | /lib/modules/3.4.61+/kernel/drivers/media/video/sun4i_csi/csi1 | ||
| - | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Replace the earlier uImage on the board with the new generated uImage under arch/arm/boot/ directory via NFS. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| Copy the above 4 driver files to the board, and install them in order: | Copy the above 4 driver files to the board, and install them in order: | ||
| Line 496: | Line 496: | ||
| csi_flash_b = | csi_flash_b = | ||
| csi_af_en_b = | csi_af_en_b = | ||
| - | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] | + | Then convert it into script.bin format by using fex2bin, and replace the earlier script.bin on the board. (for more info, refer to the document [[tutorials:DVK521:Documentations:A10:Prepare for Kernel and Drivers Porting|Prepare for Kernel and Drivers Porting]] |
| Connect the OV7670 camera module and the LCD to the board, reboot the system. | Connect the OV7670 camera module and the LCD to the board, reboot the system. | ||
| Line 503: | Line 503: | ||
| ==== Appendix 1: Compiling Driver Module ==== | ==== Appendix 1: Compiling Driver Module ==== | ||
| - | The provided xx.ko files under [[http://dl.cubieboard.org/parteners/waveshare/Source_Code/Driver%20and%20API/Driver/|Driver]] is compiled to run on our system image only. | + | The provided xx.ko files under [[http://dl.cubieboard.org/parteners/waveshare/Source_Code/a10-cubieboard-dvk/Driver%20and%20API/Driver/|Driver]] is compiled to run on our system image only. |
| If the drivers are going to being loaded on your own system, they need to be re-compiled according to you system kernel path. | If the drivers are going to being loaded on your own system, they need to be re-compiled according to you system kernel path. | ||
| Line 509: | Line 509: | ||
| Use the io_control_dev.ko for demonstration. | Use the io_control_dev.ko for demonstration. | ||
| - | 1.1 Copy the [[http://dl.cubieboard.org/parteners/waveshare/Source_Code/Driver%20and%20API/Driver/|io_control_dev]] to ubuntu, assume the target directory is /home/waveshare/cubieboard/waveshare_demo/driver . | + | 1.1 Copy the [[http://dl.cubieboard.org/parteners/waveshare/Source_Code/a10-cubieboard-dvk/Driver%20and%20API/Driver/|io_control_dev]] to ubuntu, assume the target directory is /home/waveshare/cubieboard/waveshare_demo/driver . |
| Modify the files permission: | Modify the files permission: | ||
| #cd /home/waveshare/cubieboard/waveshare_demo/driver/io_control_dev | #cd /home/waveshare/cubieboard/waveshare_demo/driver/io_control_dev | ||
| - | {{.:Documentations-6_2.jpg}} | + | {{..:Documentations-6_2.jpg}} |
| #chmod 777 ./* | #chmod 777 ./* | ||
| | | ||
| 1.2 Modify the Makefile | 1.2 Modify the Makefile | ||
| #vi Makefile | #vi Makefile | ||
| - | {{.:Documentations-6_3.jpg}} | + | {{..:Documentations-6_3.jpg}} |
| Assign the KERNELDIR according to your actual kernel path. | Assign the KERNELDIR according to your actual kernel path. | ||
| 1.3 Clear the old files | 1.3 Clear the old files | ||
| #make clean | #make clean | ||
| - | {{.:Documentations-6_4.jpg}} | + | {{..:Documentations-6_4.jpg}} |
| 1.4 Compile | 1.4 Compile | ||
| Line 532: | Line 533: | ||
| make: *** [modules] Error 1 | make: *** [modules] Error 1 | ||
| As shown in the picture below: | As shown in the picture below: | ||
| - | {{.:Documentations-6_5.jpg}} | + | |
| + | {{..:Documentations-6_5.jpg}} | ||
| It is caused by the different kernel version, can be just omitted. | It is caused by the different kernel version, can be just omitted. | ||
| - | {{.:Documentations-6_6.jpg}} | + | {{..:Documentations-6_6.jpg}} |
| Copy the new generated io_control.ko file to your own system and load it. | Copy the new generated io_control.ko file to your own system and load it. | ||
| Line 547: | Line 550: | ||
| Then copy the executable file to the board, say, "test_led", use the following command to run it: | Then copy the executable file to the board, say, "test_led", use the following command to run it: | ||
| #./ test_led | #./ test_led | ||
| - | |||
tutorials/dvk521/documentations/a10/driver_porting_and_configuration.1385445124.txt.gz · Last modified: 2013/12/23 14:50 (external edit)
Page Tools
