Cannot compile Device Tree Overlays from Source Code

Technical Support
, ,
21

Hello @rudhi.tx ,

when I execute the make command from ImageDev/DeviceTree/device-tree-overlays/overlays/ directory, many .dtbo file are created in the same directory.
No dtb file are created in ImageDev/linux/arch/arm/boot/dts/ directory.

The last messages from make command are:
DTC /home/showroom/Dev/Toradex/ImageDev/DeviceTree/device-tree-overlays/overlays/verdin-imx8mm_spidev_overlay.dtbo
DTC /home/showroom/Dev/Toradex/ImageDev/DeviceTree/device-tree-overlays/overlays/verdin-imx8mp_spidev_overlay.dtbo
MODPOST /home/showroom/Dev/Toradex/ImageDev/DeviceTree/device-tree-overlays/overlays/Module.symvers
make[1]: uscita dalla directory «/home/showroom/Dev/Toradex/ImageDev/linux»

The file to use to flash the device tree on Colibri, is a .dtb or a .dtbo ?

22

HI @Massimo,

when I execute the make command from ImageDev/DeviceTree/device-tree-overlays/overlays/ directory, many .dtbo file are created in the same directory.
No dtb file are created in ImageDev/linux/arch/arm/boot/dts/ directory.

You are mixing up device tree overlays with device trees here. As I already told you before, your module (Colibri iMX6ULL 256/512MB) does NOT support overlays. You should be working in the linux/arch/arm/boot/dts directory, and not in the device-tree-overlays/overlays/ directory. You should modify the necessary dts file in linux/arch/arm/boot/dts directory, execute the make command in the linux directory and this should generate the dtb files as I explained earlier.

The file to use to flash the device tree on Colibri, is a .dtb or a .dtbo ?

Since this module does not support overlays, you should be updating the ubi partition with the dtb files.

23

Hi @rudhi.tx ,

now I understood.
But please tell me which are the right dts and dtsi files to use to have display working.

Thanks

24

Hello @Massimo,

What type of display are you using? Also which carrier board do you have?

25

Hello @rudhi.tx
I have an Aster board and a VGA display.

26

Hi @Massimo,

From your other post, I understand that the display stopped working after you added the customizations to change the I2C speed. Is that correct?

27

Hi @rudhi.tx ,

yes it is correct.

28

Hello @Massimo

Could you please send me the dmesg logs from the console with the VGA display connected to the module?

29

Hello @rudhi.tx ,

this is the log.
dmesg.txt (21.5 KB)

30

Hi @Massimo !

Please share your device tree source (the .dts / .dtsi) files you customized.

Best regards,

31

Hi @henrique.tx
here the dts files.

Best regards
dts.zip (35.2 KB)

32

Hi @Massimo !

Thanks for the files.

Could you please explain what are each of the files you shared?

Also, what should I test?

Best regards,

33

Hi @henrique.tx,

  • imx6ull-colibri-elsist-slimline.dts is to change I2c speed
  • the others you can compare with the originals you distrubute to see the differences but are for using CAN bus

Thanks

34

Hi @Massimo ,

I took a look at your .dts file, and it shouldn’t have any impact on the VGA output.

Just to be sure, can you check if this issue happens when using a device tree from upstream, like the Aster one:

Just guessing here, but if the problem happens on the compiled upstream device trees as well, then the issue may be related to the device tree compiler (DTC) version being used.

Best regards,
Lucas Akira