Device tree overlay test

Technical Support
, , ,
1

Colibri Evaluation Board V3.2
Colibri iMX6ULL 1GB IT

I’m asking you a question because it doesn’t work when I do an overpayment test.
I want to toggle the LED using SODIMM_23/25.
This is the content of custom overlay.

/dts-v1/;
/plugin/;

#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/leds/common.h>
#include "imx6ull-pinfunc.h"

/ {
    compatible = "toradex,colibri-imx6ull";
};

&pwm1 {
    status = "disabled";
};

&pwm2 {
    status = "disabled";
};

&uart1 {
    status = "disabled";
};

&{/} {
    leds {
        compatible = "gpio-leds";

        pinctrl-names = "default";
        pinctrl-0 = <&pinctrl_my_led>;

        myled_sodimm_23 {
            label = "my_led_sodimm_23";
            gpios = <&gpio1 18 GPIO_ACTIVE_HIGH>;
            linux,default-trigger = "heartbeat";
            default-state = "on";
        };

        myled_sodimm_25 {
            label = "my_led_sodimm_25";
            gpios = <&gpio1 19 GPIO_ACTIVE_HIGH>;
            linux,default-trigger = "heartbeat";
            default-state = "on";
        };
    };
};

&iomuxc {
    /*pinctrl-0 = <&pinctrl_gpio1>, <&pinctrl_gpio2>,
                <&pinctrl_gpio3>, <&pinctrl_gpio4>,
                <&pinctrl_gpio7>, <&pinctrl_gpio8>,
                <&pinctrl_gpio_hog1>, <&pinctrl_gpio_hog2>, <&pinctrl_gpio_hog3>,
                <&pinctrl_pmic_tpm_ena>, <&pinctrl_my_led>;*/
    pinctrl_my_led: myledgrp {
        fsl,pins =
            <MX6UL_PAD_UART1_CTS_B__GPIO1_IO18 0x104>, // SODIMM 19 // pull-down enabled and drive strength X2
            <MX6UL_PAD_UART1_RTS_B__GPIO1_IO19 0x104>; // SODIMM 55 // pull-down enabled and drive strength X2
    };
};

The boot status of my board.

root@colibri-imx6ull-emmc-15161321:~# ls /boot/overlays
colibri-imx6ull_panel-cap-touch-10inch-lvds_overlay.dtbo    colibri-imx6ull_panel-res-touch-7inch_overlay.dtbo          **naruhyo-overlay.dtbo**
colibri-imx6ull_panel-cap-touch-7inch_adapter_overlay.dtbo  colibri-imx6ull_spidev_overlay.dtbo
colibri-imx6ull_panel-cap-touch-7inch_overlay.dtbo          colibri-imx6ull_vga-640x480_overlay.dtbo
root@colibri-imx6ull-emmc-15161321:~# 
root@colibri-imx6ull-emmc-15161321:~# cat /boot/overlays.txt 
**fdt_overlays=colibri-imx6ull_vga-640x480_overlay.dtbo naruhyo-overlay.dtbo**
root@colibri-imx6ull-emmc-15161321:~#
2

Try removing default-state = "on"; from your overlay. It conflicts with the heartbeat trigger as that is instructing the system you want the LED on all the time.

3

I modified the overlay.dts file as below, but there is a kernel error.

/dts-v1/;
/plugin/;

#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/leds/common.h>
#include "imx6ull-pinfunc.h"

#include "imx6ull-colibri-emmc-nonwifi.dtsi"
#include "imx6ull-colibri-eval-v3.dtsi"

/ {
    compatible = "toradex,colibri-imx6ull-emmc-eval",
                 "toradex,colibri-imx6ull-emmc",
                 "toradex,colibri-imx6ull",
                 "fsl,imx6ull";
};

&uart1 {
    status = "disabled";
};

&{/} {
    leds {
        compatible = "gpio-leds";

        pinctrl-names = "default";
        pinctrl-0 = <&pinctrl_my_led>;

        myled_sodimm_25 {
            label = "my_led_sodimm_25";
            gpios = <&gpio1 18 GPIO_ACTIVE_HIGH>;
            linux,default-trigger = "heartbeat";
        };
    };
};

The kernel error is like below
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND

CPU:   Freescale i.MX6ULL rev1.1 792 MHz (running at 396 MHz)
CPU:   Industrial temperature grade (-40C to 105C) at 43C
Reset cause: POR
DRAM:  1 GiB
Core:  81 devices, 16 uclasses, devicetree: separate
MMC:   FSL_SDHC: 1, FSL_SDHC: 0
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Model: Toradex 0062 Colibri iMX6ULL 1GB IT V1.1A
Serial#: 15161321
Net:   eth0: ethernet@20b4000
Hit any key to stop autoboot:  0 
MMC: no card present
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
5998 bytes read in 2 ms (2.9 MiB/s)
## Executing script at 88280000
Loading DeviceTree: imx6ull-colibri-emmc-eval-v3.dtb
47130 bytes read in 3 ms (15 MiB/s)
31 bytes read in 2 ms (14.6 KiB/s)
Applying Overlay: test_overlay.dtbo
52199 bytes read in 5 ms (10 MiB/s)
**failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND**
9589152 bytes read in 226 ms (40.5 MiB/s)
Bootargs: user_debug=30 root=PARTUUID=bb858632-02 ro rootwait console=tty1 console=ttymxc0,115200n8 consoleblank=0 video=mxsfb:640x480M-16@60
Kernel image @ 0x84200000 [ 0x000000 - 0x9251a0 ]
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
Booting from mmc failed!
SCRIPT FAILED: continuing...
47130 bytes read in 4 ms (11.2 MiB/s)
No EFI system partition
BootOrder not defined
EFI boot manager: Cannot load any image
starting USB...
Bus usb@2184000: USB EHCI 1.00
Bus usb@2184200: USB EHCI 1.00
scanning bus usb@2184000 for devices... 1 USB Device(s) found
scanning bus usb@2184200 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
BOOTP broadcast 1
DHCP client bound to address 192.168.0.53 (54 ms)
Using ethernet@20b4000 device
TFTP from server 192.168.10.1; our IP address is 192.168.0.53; sending through gateway 192.168.0.1
Filename 'boot.scr'.
Load address: 0x88280000
Loading: T T T T T T T T T T 
Retry count exceeded; starting again
BOOTP broadcast 1
DHCP client bound to address 192.168.0.53 (53 ms)
Using ethernet@20b4000 device
TFTP from server 192.168.10.1; our IP address is 192.168.0.53; sending through gateway 192.168.0.1
Filename 'boot.scr'.
Load address: 0x84200000
4

Hi @vorutesv , are you referring to this guide?

Are you able to compile an even simpler overlay just to check that the environment is OK?