Re: flash-kernel and dtbs
Hi Vagrant,
many thanks for you excellent suggestions, they helped me a lot.
Am Dienstag, 28. November 2017, 13:12:42 schrieb Vagrant Cascadian:
[...]
>
> When the user installs them. Install u-boot-imx and see
> /usr/share/doc/u-boot-imx/README.Debian* for instructions on how to
> install u-boot manually.
That worked, but I had to install it to /dev/mmcblk1 (not mmcblk0)
Now the correct machine model is deteced:
root@mohot:~# grep fdt /var/log/syslog
Nov 28 21:27:24 mohot kernel: [ 0.000000] OF: fdt: Machine model: SolidRun
Cubox-i Dual/Quad
Nov 28 21:35:28 mohot kernel: [ 0.000000] OF: fdt: Machine model: SolidRun
Cubox-i Dual/Quad
Nov 28 21:46:35 mohot kernel: [ 0.000000] OF: fdt: Machine model: SolidRun
Cubox-i Dual/Quad
Nov 30 21:46:04 mohot kernel: [ 0.000000] OF: fdt: Machine model: SolidRun
Cubox-i Dual/Quad
Nov 30 21:50:03 mohot kernel: [ 0.000000] OF: fdt: Machine model: SolidRun
Cubox-i Dual/Quad
Nov 30 21:53:21 mohot kernel: [ 0.000000] OF: fdt: Machine model: SolidRun
HummingBoard Dual/Quad
Nov 30 21:54:26 mohot kernel: [ 0.000000] OF: fdt: Machine model: SolidRun
HummingBoard Dual/Quad
Nov 30 22:03:43 mohot kernel: [ 0.000000] OF: fdt: Machine model: SolidRun
HummingBoard Dual/Quad
root@mohot:~#
root@mohot:~# cat /proc/device-tree/model
SolidRun HummingBoard Dual/Quadroot@mohot:~#
> If you have no memory of installing it explicitly, it was probably
> included as part using an old debian-installer image, such as the
> netboot SD card images:
I think I installed from netboot SD card image, I did not install it myself.
>
> https://deb.debian.org/debian/dists/jessie/main/installer-armhf/current/ima
> ges/netboot/SD-card-images/
>
>
> For a newer installer image:
>
>
> https://deb.debian.org/debian/dists/stretch/main/installer-armhf/current/im
> ages/netboot/SD-card-images/
I could avoid reinstallation :-)
The dtb has 4 spi entries
ecspi@02008000 {
#address-cells = <0x00000001>;
#size-cells = <0x00000000>;
compatible = "fsl,imx6q-ecspi", "fsl,imx51-ecspi";
reg = <0x02008000 0x00004000>;
interrupts = <0x00000000 0x0000001f 0x00000004>;
clocks = <0x00000002 0x00000070 0x00000002 0x00000070>;
clock-names = "ipg", "per";
dmas = <0x0000000d 0x00000003 0x00000008 0x00000001
0x0000000d 0x00000004 0x00000008 0x00000002>;
dma-names = "rx", "tx";
status = "disabled";
};
ecspi@0200c000 {
#address-cells = <0x00000001>;
#size-cells = <0x00000000>;
compatible = "fsl,imx6q-ecspi", "fsl,imx51-ecspi";
reg = <0x0200c000 0x00004000>;
interrupts = <0x00000000 0x00000020 0x00000004>;
clocks = <0x00000002 0x00000071 0x00000002 0x00000071>;
clock-names = "ipg", "per";
dmas = <0x0000000d 0x00000005 0x00000008 0x00000001
0x0000000d 0x00000006 0x00000008 0x00000002>;
dma-names = "rx", "tx";
status = "disabled";
};
ecspi@02010000 {
#address-cells = <0x00000001>;
#size-cells = <0x00000000>;
compatible = "fsl,imx6q-ecspi", "fsl,imx51-ecspi";
reg = <0x02010000 0x00004000>;
interrupts = <0x00000000 0x00000021 0x00000004>;
clocks = <0x00000002 0x00000072 0x00000002 0x00000072>;
clock-names = "ipg", "per";
dmas = <0x0000000d 0x00000007 0x00000008 0x00000001
0x0000000d 0x00000008 0x00000008 0x00000002>;
dma-names = "rx", "tx";
status = "disabled";
};
ecspi@02014000 {
#address-cells = <0x00000001>;
#size-cells = <0x00000000>;
compatible = "fsl,imx6q-ecspi", "fsl,imx51-ecspi";
reg = <0x02014000 0x00004000>;
interrupts = <0x00000000 0x00000022 0x00000004>;
clocks = <0x00000002 0x00000073 0x00000002 0x00000073>;
clock-names = "ipg", "per";
dmas = <0x0000000d 0x00000009 0x00000008 0x00000001
0x0000000d 0x0000000a 0x00000008 0x00000002>;
dma-names = "rx", "tx";
status = "disabled";
};
Is that sufficient for enabling the spi interfaces on the 26 pin interface?
I do not see a /dev/spidev* even after loading spi_imx, which also does not
produce any entry in syslog. Do you have any clue why the the spi devices do
not show up?
Many thanks again
Rainer
Reply to: