How to customize Debian 9.2 device tree - Revision history

Pawelzbysinski at 09:18, 16 June 2020

2020-06-16T09:18:52Z

← Older revision		Revision as of 09:18, 16 June 2020
Line 1:		Line 1:
	{{PageHeader\|How to customize Debian 9.2 device tree}}		{{PageHeader\|How to customize Debian 9.2 device tree}}


			[[Image:sl_wiki_new_version_600x180.jpg\|center\|link=VisionSOM-6ULL]]


	Linux version 3.5.7 and newer include a new feature - device trees, they represent connections and structure of the machine it is run on. Modules used in earlier kernels are replaced with Device Tree Blobs (DTB).		Linux version 3.5.7 and newer include a new feature - device trees, they represent connections and structure of the machine it is run on. Modules used in earlier kernels are replaced with Device Tree Blobs (DTB).

Admin at 23:56, 4 July 2018

2018-07-04T23:56:06Z

← Older revision		Revision as of 23:56, 4 July 2018
Line 5:		Line 5:

	<pre>jz@ubuntu:~$ sudo apt install qemu-user-static		<pre>jz@ubuntu:~$ sudo apt install qemu-user-static
	jz@ubuntu:~$ wget ~~https~~://somlabs.com~~/os_images~~/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ wget http://ftp.somlabs.com/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
	jz@ubuntu:~$ sudo tar -xvf somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ sudo tar -xvf somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
	jz@ubuntu:~$ sudo cp /etc/hostname ~/somlabs-debian/etc/hostname		jz@ubuntu:~$ sudo cp /etc/hostname ~/somlabs-debian/etc/hostname

Pawelzbysinski at 15:43, 26 May 2018

2018-05-26T15:43:10Z

Pawelzbysinski at 18:50, 23 May 2018

2018-05-23T18:50:17Z

← Older revision		Revision as of 18:50, 23 May 2018
Line 6:		Line 6:
	<pre>jz@ubuntu:~$ sudo apt install qemu-user-static		<pre>jz@ubuntu:~$ sudo apt install qemu-user-static
	jz@ubuntu:~$ wget https://somlabs.com/os_images/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ wget https://somlabs.com/os_images/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
	jz@ubuntu:~$ sudo tar xf somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ sudo tar -xvf somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
	jz@ubuntu:~$ sudo ./somlabs-debian/chtoolchain		jz@ubuntu:~$ sudo ./somlabs-debian/chtoolchain
	</pre>		</pre>

Admin at 12:40, 22 May 2018

2018-05-22T12:40:31Z

← Older revision		Revision as of 12:40, 22 May 2018
Line 2:		Line 2:
	Linux version 3.5.7 and newer include a new feature - device trees, they represent connections and structure of the machine it is run on. Modules used in earlier kernels are replaced with Device Tree Blobs (DTB).		Linux version 3.5.7 and newer include a new feature - device trees, they represent connections and structure of the machine it is run on. Modules used in earlier kernels are replaced with Device Tree Blobs (DTB).

	We recommend Ubuntu 16 on host PC for customizing Device Tree. Before customizing the device tree you need to download and install VisionSOM-6ULL rootfs image and run it on your host system:		We recommend Ubuntu 16 x64 on host PC for customizing Device Tree. Before customizing the device tree you need to download and install VisionSOM-6ULL rootfs image and run it on your host system:

	<pre>jz@ubuntu:~$ sudo apt install qemu-user-static		<pre>jz@ubuntu:~$ sudo apt install qemu-user-static

Pawelzbysinski at 16:17, 20 May 2018

2018-05-20T16:17:52Z

← Older revision		Revision as of 16:17, 20 May 2018
Line 5:		Line 5:

	<pre>jz@ubuntu:~$ sudo apt install qemu-user-static		<pre>jz@ubuntu:~$ sudo apt install qemu-user-static
	jz@ubuntu:~$ wget ~~http~~://somlabs.com/os_images/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ wget https://somlabs.com/os_images/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
	jz@ubuntu:~$ sudo tar xf somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ sudo tar xf somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
	jz@ubuntu:~$ sudo ./somlabs-debian/chtoolchain		jz@ubuntu:~$ sudo ./somlabs-debian/chtoolchain

Admin at 16:52, 1 May 2018

2018-05-01T16:52:56Z

← Older revision		Revision as of 16:52, 1 May 2018
Line 2:		Line 2:
	Linux version 3.5.7 and newer include a new feature - device trees, they represent connections and structure of the machine it is run on. Modules used in earlier kernels are replaced with Device Tree Blobs (DTB).		Linux version 3.5.7 and newer include a new feature - device trees, they represent connections and structure of the machine it is run on. Modules used in earlier kernels are replaced with Device Tree Blobs (DTB).

	Before customizing the device tree you need to download and install VisionSOM-6ULL rootfs image and run it:		We recommend Ubuntu 16 on host PC for customizing Device Tree. Before customizing the device tree you need to download and install VisionSOM-6ULL rootfs image and run it on your host system:

	<pre>jz@ubuntu:~$ sudo apt install qemu-user-static		<pre>jz@ubuntu:~$ sudo apt install qemu-user-static
	jz@ubuntu:~$ wget http://somlabs.com/os_images/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ wget http://somlabs.com/os_images/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
Line 80:		Line 81:
	You can also use any other method to put the file in your target system.		You can also use any other method to put the file in your target system.

	Now install package on your target:		Now install package on your target system:
	<pre>root@somlabs:~# dpkg -i /root/somlabs-dts_1.0.0_armhf.deb</pre>		<pre>root@somlabs:~# dpkg -i /root/somlabs-dts_1.0.0_armhf.deb</pre>
	Reboot target system, after reboot new device tree will be used.		Reboot target system, after reboot new device tree will be used.

Admin at 15:57, 19 February 2018

2018-02-19T15:57:38Z

← Older revision		Revision as of 15:57, 19 February 2018
Line 77:		Line 77:

	If you enabled SSH access for root on your target board then you can upload package via SCP:		If you enabled SSH access for root on your target board then you can upload package via SCP:
	<pre>jz@ubuntu:~$ scp /home/developer/source~~/kernel~~/somlabs-dts_1.0.0_armhf.deb root@<TARGET_IP>:/root/</pre>		<pre>jz@ubuntu:~$ scp /home/developer/source/somlabs-dts_1.0.0_armhf.deb root@<TARGET_IP>:/root/</pre>
	You can also use any other method to put the file in your target system.		You can also use any other method to put the file in your target system.

Admin at 23:46, 12 November 2017

2017-11-12T23:46:25Z

← Older revision		Revision as of 23:46, 12 November 2017
Line 46:		Line 46:
	};</pre>		};</pre>

	Pin definition has three parts, first is the physical pad name (for example '''MX6UL_PAD_UART5_RX_DATA'''__I2C2_SDA 0x4001b8b0), second one is selected ~~pipn~~ function (for example MX6UL_PAD_UART5_RX_DATA__'''I2C2_SDA''' 0x4001b8b0). All possible combinations are defined in /home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga/arch/arm/boot/dts/imx6ul-pinfunc.h. The third part (for example MX6UL_PAD_UART5_RX_DATA__I2C2_SDA '''0x4001b8b0''') can be used to perform additional pin configuration, its bits are defined as follows:		Pin definition has three parts, first is the physical pad name (for example '''MX6UL_PAD_UART5_RX_DATA'''__I2C2_SDA 0x4001b8b0), second one is selected pin function (for example MX6UL_PAD_UART5_RX_DATA__'''I2C2_SDA''' 0x4001b8b0). All possible combinations are defined in /home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga/arch/arm/boot/dts/imx6ul-pinfunc.h. The third part (for example MX6UL_PAD_UART5_RX_DATA__I2C2_SDA '''0x4001b8b0''') can be used to perform additional pin configuration, its bits are defined as follows:

	<pre>PAD_CTL_HYS (1 << 16)		<pre>PAD_CTL_HYS (1 << 16)

Admin at 21:30, 12 November 2017

2017-11-12T21:30:01Z

← Older revision		Revision as of 21:30, 12 November 2017
Line 83:		Line 83:
	<pre>root@somlabs:~# dpkg -i /root/somlabs-dts_1.0.0_armhf.deb</pre>		<pre>root@somlabs:~# dpkg -i /root/somlabs-dts_1.0.0_armhf.deb</pre>
	Reboot target system, after reboot new device tree will be used.		Reboot target system, after reboot new device tree will be used.

			'''NOTE!''' It is strongly recommended to check startup messages after loading the device tree. If one of I/O lines is requested by more than one driver then you will get message like the one below:
			<pre>[ 0.322774] imx6ul-pinctrl 20e0000.iomuxc: pin MX6UL_PAD_JTAG_TCK already requested by 20e0000.iomuxc; cannot claim for 20f4000.pwm
			[ 0.322821] imx6ul-pinctrl 20e0000.iomuxc: pin-21 (20f4000.pwm) status -22
			[ 0.322859] imx6ul-pinctrl 20e0000.iomuxc: could not request pin 21 (MX6UL_PAD_JTAG_TCK) from group pwm6grp on device 20e0000.iomuxc</pre>

← Older revision		Revision as of 15:43, 26 May 2018
Line 7:		Line 7:
	jz@ubuntu:~$ wget https://somlabs.com/os_images/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ wget https://somlabs.com/os_images/somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
	jz@ubuntu:~$ sudo tar -xvf somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz		jz@ubuntu:~$ sudo tar -xvf somlabs-visionsom-6ull-debian-rootfs-qemu.tar.xz
			jz@ubuntu:~$ sudo cp /etc/hostname ~/somlabs-debian/etc/hostname
			jz@ubuntu:~$ sudo cp /etc/hosts ~/somlabs-debian/etc/hosts
	jz@ubuntu:~$ sudo ./somlabs-debian/chtoolchain		jz@ubuntu:~$ sudo ./somlabs-debian/chtoolchain
	</pre>		</pre>

	Before customizing your device tree for the first time you must build the kernel, to do that enter proper directory, copy default configuration and run make:		Before customizing your device tree for the first time you must build the kernel, to do that enter proper directory, copy default configuration and run make:
	<pre>jz@ubuntu:~$ cd /home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga		<pre>root@ubuntu:~$ cd /home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga
	jz@ubuntu:/home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga# cp /home/developer/source/somlabs-dts-1.0/visionsom-6ull-linux_defconfig /home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga/.config		root@ubuntu:/home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga# cp /home/developer/source/somlabs-dts-1.0/visionsom-6ull-linux_defconfig /home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga/.config
	jz@ubuntu:/home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga# make deb-pkg -j8 CFLAGS_MODULE=-fno-pic</pre>		root@ubuntu:/home/developer/source/kernel/linux-rel_imx_4.1.15_2.1.0_ga# make deb-pkg -j8 CFLAGS_MODULE=-fno-pic</pre>

	Now you can modify the device tree file:		Now you can modify the device tree file:
	<pre>jz@ubuntu:~$ nano /home/developer/source/somlabs-dts-1.0/somlabs-visionsom-6ull.dts</pre>		<pre>root@ubuntu:~$ nano /home/developer/source/somlabs-dts-1.0/somlabs-visionsom-6ull.dts</pre>

	Adding new interface definition usually requires two steps, first you need to add interface to the device tree, for example the code below activates I2C interface:		Adding new interface definition usually requires two steps, first you need to add interface to the device tree, for example the code below activates I2C interface:
Line 74:		Line 76:

	After you finish customization you can create Debian package:		After you finish customization you can create Debian package:
	<pre>jz@ubuntu:~$ cd /home/developer/source/somlabs-dts-1.0/		<pre>root@ubuntu:~$ cd /home/developer/source/somlabs-dts-1.0/
	jz@ubuntu:/home/developer/source/somlabs-dts-1.0# dpkg-buildpackage -us -uc</pre>		root@ubuntu:/home/developer/source/somlabs-dts-1.0# dpkg-buildpackage -us -uc</pre>

	If you enabled SSH access for root on your target board then you can upload package via SCP:		If you enabled SSH access for root on your target board then you can upload package via SCP:
	<pre>jz@ubuntu:~$ scp /home/developer/source/somlabs-dts_1.0.0_armhf.deb root@<TARGET_IP>:/root/</pre>		<pre>root@ubuntu:~$ scp /home/developer/source/somlabs-dts_1.0.0_armhf.deb root@<TARGET_IP>:/root/</pre>
	You can also use any other method to put the file in your target system.		You can also use any other method to put the file in your target system.