Nmcli device wifi list returns nothing

Hello,

When I run nmcli device wifi list on my module nothing gets listed. I am using a verdin imx8mp SoM on a development board, with a custom OS built using the following tcbuild.yaml:

# >> The input section specifies the image to be taken as the base for the customization.
input:
  easy-installer:
    local: ./static/torizon-base-images/torizon-core-docker-verdin-imx8mp-Tezi_5.7.2+build.20.tar

# >> The customization section defines the modifications to be applied to get the desired output image.
customization:
  splash-screen: static/splashscreen/RadiaSoftLogo_1200x234.png
  device-tree:
    # >> Directories where to look for include files.
    include-dirs:
      - static/device-trees/include
    # >> Custom device tree source:
    custom: static/device-trees/dts-arm64/imx8mp-verdin-wifi-dev.dts
    # >> Device-tree overlays configuration:
    overlays:
      # >> Whether to ignore all overlays from the base image (or ostree archive in the future).
      clear: true
      # >> Overlays to add to output image.
      add:
        - static/device-trees/overlays/touch-atmel-mxt_overlay.dts
        - static/device-trees/overlays/verdin-imx8mp_sn65dsi84-lt170410_overlay.dts
        - static/device-trees/overlays/verdin-imx8mp_sn65dsi84_overlay.dts

# >> The output section defines properties of the output image.
output:
  easy-installer:
    local: 5.7.2.CUSTOM
    bundle:
      dir: bundle/

I believe I’m using the right .dts and I didn’t see any missing overlays that seem wifi related. I don’t think the module is damaged because I’ve been able to connect the SoM to wifi last week, and I can’t think if a way my container bundle would cause an issue. Any ideas?

Greetings @bengur,

I don’t think the module is damaged because I’ve been able to connect the SoM to wifi last week, and I can’t think if a way my container bundle would cause an issue. Any ideas?

Are you sure it worked previously on this version of the software? There is a known issue where Wi-Fi wasn’t working on TorizonCore 5.7.X for the Verdin i.MX8M Plus 1.1A: TorizonCore Issue Tracker

This issue did get fixed in TorzionCore 6, but it should still be present in TorzionCore 5.7.2.

Were you perhaps using a different version of Torizon last week? Or maybe you were using a V1.0 module?

Best Regards,
Jeremias

Ah I must’ve used a different version because I’ve updated my image to 6.4.0 and it now shows connection options.

Thanks for the help!