15_编写OLED驱动_上机实验#
源码:
1. 硬件#
1.1 原理图#
IMX6ULL:
STM32MP157:
原理图:
1.2 连接#
无论是使用IMX6ULL开发板还是STM32MP157开发板,都有类似的扩展板。把OLED模块接到扩展板的SPI_A插座上,如下:
2. 编写设备树#
2.1.1 IMX6ULL#
DC引脚使用GPIO4_20,也需在设备树里指定。
设备树如下:arch/arm/boot/dts/100ask_imx6ull-14x14.dts
&ecspi1 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_ecspi1>;
fsl,spi-num-chipselects = <2>;
cs-gpios = <&gpio4 26 GPIO_ACTIVE_LOW>, <&gpio4 24 GPIO_ACTIVE_LOW>;
status = "okay";
oled: oled {
compatible = "100ask,oled";
reg = <0>;
spi-max-frequency = <10000000>;
dc-gpios = <&gpio4 20 GPIO_ACTIVE_HIGH>;
};
};
2.1.2 STM32MP157#
DC引脚使用GPIOA_13,也需要在设备树里指定。
设备树如下:arch/arm/boot/dts/stm32mp157c-100ask-512d-lcd-v1.dts
&spi5 {
pinctrl-names = "default", "sleep";
pinctrl-0 = <&spi5_pins_a>;
pinctrl-1 = <&spi5_sleep_pins_a>;
status = "okay";
cs-gpios = <&gpioh 5 GPIO_ACTIVE_LOW>, <&gpioz 4 GPIO_ACTIVE_LOW>;
spidev: icm20608@0{
compatible = "invensense,icm20608";
interrupts = <0 IRQ_TYPE_EDGE_FALLING>;
interrupt-parent = <&gpioz>;
spi-max-frequency = <8000000>;
reg = <0>;
};
oled: oled@1{
compatible = "100ask,oled";
spi-max-frequency = <10000000>;
reg = <1>;
dc-gpios = <&gpioa 13 GPIO_ACTIVE_HIGH>;
pinctrl-names = "default";
pinctrl-0 = <&oled_pins>;
};
};
arch/arm/boot/dts/stm32mp157-100ask-pinctrl.dtsi:
oled_pins: oled_pins {
pins {
pinmux = <STM32_PINMUX('A', 13, GPIO)>;
bias-disable;
drive-push-pull;
slew-rate = <1>;
};
};
3. 编译替换设备树#
3.1 IMX6ULL#
3.1.1 设置工具链#
export ARCH=arm
export CROSS_COMPILE=arm-buildroot-linux-gnueabihf-
export PATH=$PATH:/home/book/100ask_imx6ull-sdk/ToolChain/arm-buildroot-linux-gnueabihf_sdk-buildroot/bin
3.1.2 编译、替换设备树#
编译设备树: 在Ubuntu的IMX6ULL内核目录下执行如下命令, 得到设备树文件:
arch/arm/boot/dts/100ask_imx6ull-14x14.dtb
make dtbs
复制到NFS目录:
$ cp arch/arm/boot/dts/100ask_imx6ull-14x14.dtb ~/nfs_rootfs/
开发板上挂载NFS文件系统
[root@100ask:~]# mount -t nfs -o nolock,vers=3 192.168.1.137:/home/book/nfs_rootfs /mnt
更新设备树
[root@100ask:~]# cp /mnt/100ask_imx6ull-14x14.dtb /boot [root@100ask:~]# sync
重启开发板
3.2 STM32MP157#
3.2.1 设置工具链#
export ARCH=arm
export CROSS_COMPILE=arm-buildroot-linux-gnueabihf-
export PATH=$PATH:/home/book/100ask_stm32mp157_pro-sdk/ToolChain/arm-buildroot-linux-gnueabihf_sdk-buildroot/bin
3.2.2 编译、替换设备树#
编译设备树: 在Ubuntu的STM32MP157内核目录下执行如下命令, 得到设备树文件:
arch/arm/boot/dts/stm32mp157c-100ask-512d-lcd-v1.dtb
make dtbs
复制到NFS目录:
$ cp arch/arm/boot/dts/stm32mp157c-100ask-512d-lcd-v1.dtb ~/nfs_rootfs/
开发板上挂载NFS文件系统
[root@100ask:~]# mount -t nfs -o nolock,vers=3 192.168.1.137:/home/book/nfs_rootfs /mnt
确定设备树分区挂载在哪里
由于版本变化,STM32MP157单板上烧录的系统可能有细微差别。 在开发板上执行
cat /proc/mounts
后,可以得到两种结果(见下图):mmcblk2p2分区挂载在/boot目录下(下图左边):无需特殊操作,下面把文件复制到/boot目录即可
mmcblk2p2挂载在/mnt目录下(下图右边)
在视频里、后面文档里,都是更新/boot目录下的文件,所以要先执行以下命令重新挂载:
mount /dev/mmcblk2p2 /boot
更新设备树
[root@100ask:~]# cp /mnt/stm32mp157c-100ask-512d-lcd-v1.dtb /boot/ [root@100ask:~]# sync
重启开发板
4. 编译OLED驱动#
5. 编译APP#
arm-buildroot-linux-gnueabihf-gcc -o spi_oled spi_oled.c
6. 上机实验#
如果spidev没有被编译进内核,那么先执行:
insmod oled_drv.ko
确定设备节点:
ls /dev/100ask_oled
假设设备节点为/dev/100ask_oled
,执行测试程序:
./spi_oled /dev/100ask_oled