Hi all,
Is there anything “special” i need to do to enable the 2nd ethernet to be picked up on the Verdin Development Carrier Board V1.1F?
Here’s my dmesg output
root@meercam-controller:~# dmesg | grep -i eth
[ 0.000000] psci: probing for conduit method from DT.
[ 0.887024] igb: Intel(R) Gigabit Ethernet Network Driver
[ 5.601284] On-module +V3.3_ETH: supplied by On-module +V3.3 (BUCK4)
[ 5.845964] imx-dwmac 30bf0000.ethernet: IRQ eth_lpi not found
[ 5.853078] imx-dwmac 30bf0000.ethernet: User ID: 0x10, Synopsys ID: 0x51
[ 5.859917] imx-dwmac 30bf0000.ethernet: DWMAC4/5
[ 5.864718] imx-dwmac 30bf0000.ethernet: DMA HW capability register supported
[ 5.871877] imx-dwmac 30bf0000.ethernet: RX Checksum Offload Engine supported
[ 5.879025] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported
[ 5.885189] imx-dwmac 30bf0000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 5.892861] imx-dwmac 30bf0000.ethernet: Enabled L3L4 Flow TC (entries=8)
[ 5.899671] imx-dwmac 30bf0000.ethernet: Enabled RFS Flow TC (entries=8)
[ 5.906383] imx-dwmac 30bf0000.ethernet: Enabling HW TC (entries=256, max_off=256)
[ 5.913973] imx-dwmac 30bf0000.ethernet: Using 34 bits DMA width
[ 11.471941] imx-dwmac 30bf0000.ethernet eth0: PHY [stmmac-0:07] driver [Microchip KSZ9131 Gigabit PHY] (irq=85)
[ 11.488724] imx-dwmac 30bf0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[ 11.496588] imx-dwmac 30bf0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-1
[ 11.504290] imx-dwmac 30bf0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-2
[ 11.512104] imx-dwmac 30bf0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-3
[ 11.519876] imx-dwmac 30bf0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-4
[ 11.537504] imx-dwmac 30bf0000.ethernet eth0: No Safety Features support found
[ 11.544782] imx-dwmac 30bf0000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported
[ 11.553379] imx-dwmac 30bf0000.ethernet eth0: registered PTP clock
[ 11.559928] imx-dwmac 30bf0000.ethernet eth0: FPE workqueue start
[ 11.566114] imx-dwmac 30bf0000.ethernet eth0: configuring for phy/rgmii-id link mode
[ 11.577168] 8021q: adding VLAN 0 to HW filter on device eth0
[ 14.235309] imx-dwmac 30bf0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 14.243477] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 14.786317] imx-dwmac 30bf0000.ethernet eth0: Link is Down
[ 17.351544] imx-dwmac 30bf0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
root@meercam-controller:~#
I’m assuming it’s related to this? Network on Toradex Computer on Modules | Toradex Developer Center but as a bit of a hadrware noob I don’t really understand what I need to do to follow that guide…
Sorry for all these questions, and thanks in advance… again 
Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
To enable the second Ethernet interface on the Verdin Development Carrier Board V1.1F, ensure that the device tree is correctly configured to support both Ethernet interfaces. The dmesg output you’ve shared indicates that the system recognizes the Ethernet hardware (imx-dwmac 30bf0000.ethernet), but only one Ethernet interface (eth0) is mentioned. This typically means that the second Ethernet interface might not be enabled or correctly configured in the device tree.
Here are steps to troubleshoot and enable the second Ethernet interface:
-
Check Device Tree Configuration: Verify that the device tree file used by your system includes configurations for both Ethernet interfaces. The device tree should define both interfaces, including their respective PHY connections.
-
Update Device Tree: If the second Ethernet interface is not defined, you will need to update the device tree to include it. This involves adding a node for the second Ethernet interface, specifying its address, PHY connection, and any relevant properties similar to the first Ethernet interface.
-
Recompile and Deploy the Device Tree: After updating the device tree, recompile it and deploy the new DTB (Device Tree Blob) to your system. Ensure that your bootloader is configured to load the updated DTB on boot.
-
Verify Interface Detection: After making these changes and rebooting your system, check the dmesg output again to see if the second Ethernet interface is detected. You should see similar initialization messages for the second interface as you do for the first.
-
Configure Network Interface: Once the second Ethernet interface is detected by the system, configure it using standard Linux networking tools or through your system’s network configuration files to bring the interface up and assign it an IP address.
If after these steps the second Ethernet interface is still not detected, it might be necessary to review the hardware connections and ensure that the Verdin Development Carrier Board V1.1F supports the second Ethernet interface as expected and that there are no hardware issues preventing its detection.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
First Steps with Capacitive Touch Display 10.1 Inch LVDS | Toradex Developer Center.
Hello @alan01252,
You should not need to do anything to enable the second ethernet port (X35) on the Verdin Development Board when using the Verdin iMX8MP.
When using a Reference Image or an unaltered version of Torizon OS, by default the Verdin Development Board’s device tree will be loaded and it includes the needed configuration for the second ethernet port.
On your logs, I see imx-dwmac which is the MAC connected to the on-module phy for the Verdin iMX8MP.
This is used for the first ethernet port (X25).
Are you having problems using either of the ethernet ports?
Best Regards,
Bruno
Thanks Bruno ( sorry you must be sick of me by now!! )
This is our own custom image, so I’m assuming it’s missing something but it uses the toradex-bsp etc
Eth0 (x25) is detected fine, but eth1 (x35 ) shows nothing.
gpinfo shows this.
root@controller:/# gpioinfo | grep eth1
line 20: unnamed "regulator-module-eth1phy" output active-high [used]
And I have all these files in the /uboot/ on the built image ( no idea if this helps? )
./uboot/imx8mp-verdin-wifi-dahlia.dtb
./uboot/imx8mp-verdin-wifi-mallow.dtb
./uboot/imx8mp-verdin-nonwifi-dahlia.dtb
./uboot/imx8mp-verdin-nonwifi-mallow.dtb
./uboot/imx8mp-verdin-nonwifi-dev.dtb
./uboot/imx8mp-verdin-wifi-yavia.dtb
./uboot/overlays/verdin-imx8mp_ar0521_overlay.dtbo
./uboot/overlays/verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo
./uboot/overlays/verdin-imx8mp_nau8822-btl_overlay.dtbo
./uboot/overlays/verdin-imx8mp_mezzanine_ov5640-default-jumpers_overlay.dtbo
./uboot/overlays/verdin-imx8mp_mezzanine_ar0521-alt-jumpers_overlay.dtbo
./uboot/overlays/verdin-imx8mp_mezzanine_panel-lvds-dual-channel-1080p_overlay.dtbo
./uboot/overlays/verdin-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
./uboot/overlays/verdin-imx8mp_hmp_overlay.dtbo
./uboot/overlays/verdin-imx8mp_dsi-to-hdmi_overlay.dtbo
./uboot/overlays/verdin-imx8mp_dsi-to-lvds_panel-lvds-dual-channel-1080p_overlay.dtbo
./uboot/overlays/verdin-imx8mp_mezzanine_panel-cap-touch-10inch-lvds_overlay.dtbo
./uboot/overlays/verdin-imx8mp_spidev_overlay.dtbo
./uboot/overlays/verdin-imx8mp_hdmi_overlay.dtbo
./uboot/overlays/verdin-imx8mp_mezzanine_ar0521_overlay.dtbo
./uboot/overlays/verdin-imx8mp_mezzanine_ov5640-alt-jumpers_overlay.dtbo
./uboot/overlays/verdin-imx8mp_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dtbo
./uboot/overlays/verdin-imx8mp_ov5640_overlay.dtbo
./uboot/imx8mp-verdin-nonwifi-yavia.dtb
./uboot/imx8mp-verdin-wifi-dev.dtb
Okay, so the reference image does produce to ethernet adapters.
root@verdin-imx8mp-15290589:~# dmesg | grep eth
[ 0.000000] psci: probing for conduit method from DT.
[ 2.144386] fec 30be0000.ethernet eth0: registered PHC device 0
[ 2.151091] imx-dwmac 30bf0000.ethernet: IRQ eth_lpi not found
[ 2.157270] imx-dwmac 30bf0000.ethernet: User ID: 0x10, Synopsys ID: 0x51
[ 2.164083] imx-dwmac 30bf0000.ethernet: DWMAC4/5
[ 2.168905] imx-dwmac 30bf0000.ethernet: DMA HW capability register supported
[ 2.176056] imx-dwmac 30bf0000.ethernet: RX Checksum Offload Engine supported
[ 2.183210] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported
[ 2.189356] imx-dwmac 30bf0000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 2.197034] imx-dwmac 30bf0000.ethernet: Enabled L3L4 Flow TC (entries=8)
[ 2.203833] imx-dwmac 30bf0000.ethernet: Enabled RFS Flow TC (entries=8)
[ 2.203844] imx-dwmac 30bf0000.ethernet: Enabling HW TC (entries=256, max_off=256)
[ 2.224670] imx-dwmac 30bf0000.ethernet: Using 34 bits DMA width
[ 7.048991] using random self ethernet address
[ 7.054298] using random host ethernet address
[ 7.709106] Microchip KSZ9131 Gigabit PHY 30be0000.ethernet-1:07: attached PHY driver (mii_bus:phy_addr=30be0000.ethernet-1:07, irq=192)
[ 7.796083] imx-dwmac 30bf0000.ethernet eth1: PHY [stmmac-0:07] driver [Microchip KSZ9131 Gigabit PHY] (irq=88)
[ 7.817905] imx-dwmac 30bf0000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-0
[ 7.826386] imx-dwmac 30bf0000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-1
[ 7.836892] imx-dwmac 30bf0000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-2
[ 7.847043] imx-dwmac 30bf0000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-3
[ 7.880857] imx-dwmac 30bf0000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-4
[ 7.909493] imx-dwmac 30bf0000.ethernet eth1: No Safety Features support found
[ 7.917269] imx-dwmac 30bf0000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
[ 7.926058] imx-dwmac 30bf0000.ethernet eth1: registered PTP clock
[ 7.932868] imx-dwmac 30bf0000.ethernet eth1: FPE workqueue start
[ 7.939178] imx-dwmac 30bf0000.ethernet eth1: configuring for phy/rgmii-id link mode
[ 7.952026] 8021q: adding VLAN 0 to HW filter on device eth1
[ 11.077597] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 11.085226] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 13.952036] imx-dwmac 30bf0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[ 13.960200] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
So I’m definitely missing something any clues to what? Is there a yocto recipe/variable I should explicitly be putting in?
Hello @alan01252,
What device tree is being loaded to the board?
You can check this by running tdx-info -dt.
If it is loading either imx8mp-verdin-nonwifi-dev.dtb or imx8mp-verdin-wifi-dev.dtb, I would expect both ethernet ports to work without the need for additional configuration.
If a custom device tree is being loaded, you need to make sure to add the needed configuration for the phy regulator and to configure this in the fec node:
reg_eth2phy: regulator-eth2phy {
compatible = "regulator-fixed";
enable-active-high;
gpio = <&gpio_expander_21 4 GPIO_ACTIVE_HIGH>; /* ETH_PWR_EN */
off-on-delay = <500000>;
regulator-max-microvolt = <3300000>;
regulator-min-microvolt = <3300000>;
regulator-name = "+V3.3_ETH";
startup-delay-us = <200000>;
vin-supply = <®_3p3v>;
};
&fec {
phy-supply = <®_eth2phy>;
status = "okay";
};
Please let me know if this helps, we can also look into the customization done in the image to check if there is something else causing the problem.
Best Regards,
Bruno
Hmmm looks the same as the reference image ( I have two dev boards now, gosh this makes life easier when comparing! )
My image
root@controller:/tmp# ./tdx-info -dt
Device tree
------------------------------------------------------------
Device tree enabled: imx8mp-verdin-wifi-yavia.dtb
Compatible string: toradex,verdin-imx8mp-wifi-yaviatoradex,verdin-imx8mp-wifitoradex,verdin-imx8mpfsl,imx8mp
Device trees available:
imx8mp-verdin-nonwifi-dahlia.dtb
imx8mp-verdin-nonwifi-dev.dtb
imx8mp-verdin-nonwifi-mallow.dtb
imx8mp-verdin-nonwifi-yavia.dtb
imx8mp-verdin-wifi-dahlia.dtb
imx8mp-verdin-wifi-dev.dtb
imx8mp-verdin-wifi-mallow.dtb
imx8mp-verdin-wifi-yavia.dtb
------------------------------------------------------------
Device tree overlays
------------------------------------------------------------
Overlays enabled: fdt_overlays=verdin-imx8mp_hdmi_overlay.dtbo verdin-imx8mp_dsi-to-hdmi_overlay.dtbo verdin-imx8mp_spidev_overlay.dtbo verdin-imx8mp_ar0521_overlay.dtbo
Overlays available:
verdin-imx8mp_ar0521_overlay.dtbo
verdin-imx8mp_dsi-to-hdmi_overlay.dtbo
verdin-imx8mp_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_dsi-to-lvds_panel-lvds-dual-channel-1080p_overlay.dtbo
verdin-imx8mp_hdmi_overlay.dtbo
verdin-imx8mp_hmp_overlay.dtbo
verdin-imx8mp_mezzanine_ar0521-alt-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_ar0521_overlay.dtbo
verdin-imx8mp_mezzanine_ov5640-alt-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_ov5640-default-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_mezzanine_panel-lvds-dual-channel-1080p_overlay.dtbo
verdin-imx8mp_nau8822-btl_overlay.dtbo
verdin-imx8mp_ov5640_overlay.dtbo
verdin-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_spidev_overlay.dtbo
------------------------------------------------------------
Reference image
root@verdin-imx8mp-15290589:/boot# tdx-info -dt
Device tree
------------------------------------------------------------
Device tree enabled: -
Compatible string: toradex,verdin-imx8mp-nonwifi-devtoradex,verdin-imx8mp-nonwifitoradex,verdin-imx8mpfsl,imx8mp
Device trees available:
imx8mp-verdin-nonwifi-dahlia.dtb
imx8mp-verdin-nonwifi-dev.dtb
imx8mp-verdin-nonwifi-mallow.dtb
imx8mp-verdin-nonwifi-yavia.dtb
imx8mp-verdin-wifi-dahlia.dtb
imx8mp-verdin-wifi-dev.dtb
imx8mp-verdin-wifi-mallow.dtb
imx8mp-verdin-wifi-yavia.dtb
------------------------------------------------------------
Device tree overlays
------------------------------------------------------------
Overlays enabled: fdt_overlays=verdin-imx8mp_hdmi_overlay.dtbo verdin-imx8mp_dsi-to-hdmi_overlay.dtbo verdin-imx8mp_spidev_overlay.dtbo
Overlays available:
verdin-imx8mp_dsi-to-hdmi_overlay.dtbo
verdin-imx8mp_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_dsi-to-lvds_panel-lvds-dual-channel-1080p_overlay.dtbo
verdin-imx8mp_hdmi_overlay.dtbo
verdin-imx8mp_hmp_overlay.dtbo
verdin-imx8mp_mezzanine_ov5640-alt-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_ov5640-default-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_mezzanine_panel-lvds-dual-channel-1080p_overlay.dtbo
verdin-imx8mp_nau8822-btl_overlay.dtbo
verdin-imx8mp_ov5640_overlay.dtbo
verdin-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_spidev_overlay.dtbo
------------------------------------------------------------
Is it weird that the reference image appears to say there’s no device tree enabled?
Hello @alan01252,
This output is certainly not expected, maybe there is an issue with the tdx-info script.
I will try to reproduce this problem.
It looks like your image is selecting the imx8mp-verdin-wifi-yavia.dtb device tree.
As the Yavia board has no second ethernet, its device lacks the needed configuration for a second ethernet.
To test if the second ethernet works in your custom image you can run the following command to force the correct device tree to be loaded:
fw_setenv fdtfile imx8mp-verdin-wifi-dev.dtb
And then reboot the board.
If the above works, then you can fix the device tree which will be loaded by u-boot.
At the end of the “Customize the Kernel” section in the following page there is a guide on what configurations are needed: Custom meta layers, recipes and images in Yocto Project (hello-world examples) | Toradex Developer Center
If you have questions or problems while doing this, please feel free to reach out.
Best Regards,
Bruno
Hmmm
still only the one device 
@alan01252,
Can you send me the full dmesg logs?
I am starting to suspect that there is a missing override related to the u-boot problem.
Best Regards,
Bruno
@bruno.tx
As requested 
dmesg-custom-image.txt (32.7 KB)
My brain was heading there too… I think I still have a custom image before I made the name override, I’ll see if that loads both…
Hello @alan01252,
Thanks for the logs.
[ 0.000000] Machine model: Toradex Verdin iMX8M Plus WB on Yavia Board
Considering that they show the board as if it was using a Yavia Carrier Board even with the correct device tree, I think this may be linked to the override issue.
I will look into that and hopefully with a working solution the device configuration should be correct for the second ethernet.
Best Regards,
Bruno
Thank you!
Weird the image where I hadn’t overridden the machine name is still coming up with it using Yavia board.
Trying to work out what in my local.conf I might be missing compared to the reference board.
Apologies for all this agro… big learning curve
Device tree
------------------------------------------------------------
Device tree enabled: imx8mp-verdin-wifi-dev.dtb
Compatible string: toradex,verdin-imx8mp-wifi-yaviatoradex,verdin-imx8mp-wifitoradex,verdin-imx8mpfsl,imx8mp
Device trees available:
imx8mp-verdin-nonwifi-dahlia.dtb
imx8mp-verdin-nonwifi-dev.dtb
imx8mp-verdin-nonwifi-mallow.dtb
imx8mp-verdin-nonwifi-yavia.dtb
imx8mp-verdin-wifi-dahlia.dtb
imx8mp-verdin-wifi-dev.dtb
imx8mp-verdin-wifi-mallow.dtb
imx8mp-verdin-wifi-yavia.dtb
------------------------------------------------------------
Device tree overlays
------------------------------------------------------------
Overlays enabled: fdt_overlays=verdin-imx8mp_hdmi_overlay.dtbo verdin-imx8mp_dsi-to-hdmi_overlay.dtbo verdin-imx8mp_spidev_overlay.dtbo verdin-imx8mp_ar0521_overlay.dtbo
Overlays available:
verdin-imx8mp_ar0521_overlay.dtbo
verdin-imx8mp_dsi-to-hdmi_overlay.dtbo
verdin-imx8mp_dsi-to-lvds_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_dsi-to-lvds_panel-lvds-dual-channel-1080p_overlay.dtbo
verdin-imx8mp_hdmi_overlay.dtbo
verdin-imx8mp_hmp_overlay.dtbo
verdin-imx8mp_mezzanine_ar0521-alt-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_ar0521_overlay.dtbo
verdin-imx8mp_mezzanine_ov5640-alt-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_ov5640-default-jumpers_overlay.dtbo
verdin-imx8mp_mezzanine_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_mezzanine_panel-lvds-dual-channel-1080p_overlay.dtbo
verdin-imx8mp_nau8822-btl_overlay.dtbo
verdin-imx8mp_ov5640_overlay.dtbo
verdin-imx8mp_panel-cap-touch-10inch-dsi_overlay.dtbo
verdin-imx8mp_panel-cap-touch-10inch-lvds_overlay.dtbo
verdin-imx8mp_spidev_overlay.dtbo
------------------------------------------------------------
root@verdin-imx8mp:/tmp# dmesg -T | head
[Wed Aug 14 14:03:49 2024] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[Wed Aug 14 14:03:49 2024] Linux version 5.15.148-0+git.23a8e831749d (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Thu Feb 29 20:25:21 UTC 2024
[Wed Aug 14 14:03:49 2024] Machine model: Toradex Verdin iMX8M Plus WB on Yavia Board
Right…
NOTE: Executing Tasks
WARNING: u-boot-toradex-2022.04-r0 do_provide_mender_defines: Found more than one dtb specified in KERNEL_DEVICETREE ( freescale/imx8mp-verdin-nonwifi-dahlia.dtb freescale/imx8mp-verdin-nonwifi-dev.dtb freescale/imx8mp-verdin-nonwifi-mallow.dtb freescale/imx8mp-verdin-nonwifi-yavia.dtb freescale/imx8mp-verdin-wifi-dahlia.dtb freescale/imx8mp-verdin-wifi-dev.dtb freescale/imx8mp-verdin-wifi-mallow.dtb freescale/imx8mp-verdin-wifi-yavia.dtb ). Only one should be specified. Choosing the last one: freescale/imx8mp-verdin-wifi-yavia.dtb. Set KERNEL_DEVICETREE to the desired dtb file to silence this warning.
I hadn’t noticed this before. Weirdly though I am setting KERNEL_DEVICETREE in my local.conf and still have this warning. Investigating now…
Hello @alan01252,
While there could be a relation to the override problem here, it could be something else.
Looking at your logs, it looks like you are adding mender to the image.
I am unsure of the requirements for mender, but it seems that they require a single device tree to be in KERNEL_DEVICETREE.
The KERNEL_DEVICETREE variable is configured in the verdin-imx8mp.conf file:
KERNEL_DTB_PREFIX = "freescale/"
KERNEL_DEVICETREE = " \
${KERNEL_DTB_PREFIX}imx8mp-verdin-nonwifi-dahlia.dtb \
${KERNEL_DTB_PREFIX}imx8mp-verdin-nonwifi-dev.dtb \
${KERNEL_DTB_PREFIX}imx8mp-verdin-nonwifi-mallow.dtb \
${KERNEL_DTB_PREFIX}imx8mp-verdin-nonwifi-yavia.dtb \
${KERNEL_DTB_PREFIX}imx8mp-verdin-wifi-dahlia.dtb \
${KERNEL_DTB_PREFIX}imx8mp-verdin-wifi-dev.dtb \
${KERNEL_DTB_PREFIX}imx8mp-verdin-wifi-mallow.dtb \
${KERNEL_DTB_PREFIX}imx8mp-verdin-wifi-yavia.dtb \
"
In your custom machine, you could set this variable again:
KERNEL_DTB_PREFIX = "freescale/"
KERNEL_DEVICETREE = " \
${KERNEL_DTB_PREFIX}imx8mp-verdin-wifi-dev.dtb \
"
Best Regards,
Bruno
Thanks @bruno.tx,
So this does look entirely to do with mender. I set this
KERNEL_DEVICETREE = "freescale/imx8mp-verdin-nonwifi-dev.dtb"
MENDER_DTB_NAME_FORCE = "freescale/imx8mp-verdin-nonwifi-dev.dtb"
and now I have
and
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.15.148-0+git.23a8e831749d (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Thu Feb 29 20:25:21 UTC 2024
[ 0.000000] Machine model: Toradex Verdin iMX8M Plus on Verdin Development Board
I know I keep saying it but thank you SO much for all your support and patience.
I am learning a ton from you and all your help it’s deeply appreciated.
Hello @alan01252,
Thanks for the update.
I am glad you were able to get this resolved.
Best Regards,
Bruno
