How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

Just built latest Freescale Community BSP core-image-minimal (kernel 5.4.67 was built) for imx8mm-evk and firmware-imx is not included in sdcard image ... which I think is why I'm getting messages like these:

[    0.127623] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.127636] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    0.135771] mxs-dma 33000000.dma-controller: initialized

[    3.921734] cfg80211: failed to load regulatory.db
[    3.939089] imx-sdma 302b0000.dma-controller: external firmware not found, using ROM firmware
[    3.939090] imx-sdma 30bd0000.dma-controller: external firmware not found, using ROM firmware
[    3.939186] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    3.966989] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    4.013621] imx-sdma 302c0000.dma-controller: external firmware not found, using ROM firmware

I found the firmware files in:

build/tmp/work/aarch64-mx8mm-poky-linux/firmware-imx-8m/8.8-r0/firmware-imx-8.8/fi rmware

... and copied them to the sdcard under /lib/firmware/imx directory but I still get the firmware errors.

How "should" I be getting these firmware binaries into the core-image-minimal sdcard image to also get rid of the firmware loading errors?

I'm using a rev B imx8mm-evk board and using the imx8mm-evk-revb.dtb.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 2505 bytes --]

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]

On Mon, Oct 5, 2020 at 06:24 PM, Brian Hutchinson wrote:

> 
> Just built latest Freescale Community BSP core-image-minimal (kernel
> 5.4.67 was built) for imx8mm-evk and firmware-imx is not included in
> sdcard image ... which I think is why I'm getting messages like these:
> 
> [    0.127623] imx-sdma 302c0000.dma-controller: Direct firmware load for
> imx/sdma/sdma-imx7d.bin failed with error -2
> [    0.127636] imx-sdma 302c0000.dma-controller: Falling back to sysfs
> fallback for: imx/sdma/sdma-imx7d.bin
> [    0.135771] mxs-dma 33000000.dma-controller: initialized
> 
> 
> [    3.921734] cfg80211: failed to load regulatory.db
> [    3.939089] imx-sdma 302b0000.dma-controller: external firmware not
> found, using ROM firmware
> [    3.939090] imx-sdma 30bd0000.dma-controller: external firmware not
> found, using ROM firmware
> [    3.939186] imx-sdma 302c0000.dma-controller: Direct firmware load for
> imx/sdma/sdma-imx7d.bin failed with error -2
> [    3.966989] imx-sdma 302c0000.dma-controller: Falling back to sysfs
> fallback for: imx/sdma/sdma-imx7d.bin
> [    4.013621] imx-sdma 302c0000.dma-controller: external firmware not
> found, using ROM firmware
> 
> I found the firmware files in:
> 
> build/tmp/work/aarch64-mx8mm-poky-linux/firmware-imx-8m/8.8-r0/firmware-imx-8.8/fi
> rmware
> 
> ... and copied them to the sdcard under /lib/firmware/imx directory but I
> still get the firmware errors.
> 
> How "should" I be getting these firmware binaries into the
> core-image-minimal sdcard image to also get rid of the firmware loading
> errors?
> 
> I'm using a rev B imx8mm-evk board and using the imx8mm-evk-revb.dtb.
> 
> Regards,
> 
> Brian
> 
> 

I'm using core-image-minimal because I have a custom board based off of imx8mm evk but don't use wifi, bluetooth, video, touch pad etc. so I don't want all the "stuff" that comes in core-image-base.  Just background for those that might ask.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 2879 bytes --]

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 34970 bytes --]

On Mon, Oct 5, 2020 at 06:34 PM, Brian Hutchinson wrote:

> 
> On Mon, Oct 5, 2020 at 06:24 PM, Brian Hutchinson wrote:
> 
>> Just built latest Freescale Community BSP core-image-minimal (kernel
>> 5.4.67 was built) for imx8mm-evk and firmware-imx is not included in
>> sdcard image ... which I think is why I'm getting messages like these:
>> 
>> [    0.127623] imx-sdma 302c0000.dma-controller: Direct firmware load for
>> imx/sdma/sdma-imx7d.bin failed with error -2
>> [    0.127636] imx-sdma 302c0000.dma-controller: Falling back to sysfs
>> fallback for: imx/sdma/sdma-imx7d.bin
>> [    0.135771] mxs-dma 33000000.dma-controller: initialized
>> 
>> 
>> [    3.921734] cfg80211: failed to load regulatory.db
>> [    3.939089] imx-sdma 302b0000.dma-controller: external firmware not
>> found, using ROM firmware
>> [    3.939090] imx-sdma 30bd0000.dma-controller: external firmware not
>> found, using ROM firmware
>> [    3.939186] imx-sdma 302c0000.dma-controller: Direct firmware load for
>> imx/sdma/sdma-imx7d.bin failed with error -2
>> [    3.966989] imx-sdma 302c0000.dma-controller: Falling back to sysfs
>> fallback for: imx/sdma/sdma-imx7d.bin
>> [    4.013621] imx-sdma 302c0000.dma-controller: external firmware not
>> found, using ROM firmware
>> 
>> I found the firmware files in:
>> 
>> build/tmp/work/aarch64-mx8mm-poky-linux/firmware-imx-8m/8.8-r0/firmware-imx-8.8/fi
>> rmware
>> 
>> ... and copied them to the sdcard under /lib/firmware/imx directory but I
>> still get the firmware errors.
>> 
>> How "should" I be getting these firmware binaries into the
>> core-image-minimal sdcard image to also get rid of the firmware loading
>> errors?
>> 
>> I'm using a rev B imx8mm-evk board and using the imx8mm-evk-revb.dtb.
>> 
>> Regards,
>> 
>> Brian
>> 
>> 
> 
> I'm using core-image-minimal because I have a custom board based off of
> imx8mm evk but don't use wifi, bluetooth, video, touch pad etc. so I don't
> want all the "stuff" that comes in core-image-base.  Just background for
> those that might ask.
> 
> Regards,
> 
> Brian

Another update ... decided to build core-image-base just in case it was related to core-image-minimal missing something ... I get the same sdma errors.  So I add IMAGE_INSTALL_append = " firmware-imx-sdma-imx7d firmware-imx-epdc" to local.conf.  Still get the errors.

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.4.67+g001df9337bae (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Wed Sep 23 20:52:03 UTC 2020
[    0.000000] Machine model: FSL i.MX8MM LPDDR4 EVK RevB board
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000078000000, size 640 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xbdbdd500-0xbdbdefff]
[    0.000000] Zone ranges:
[    0.000000]   DMA32    [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000b7ffffff]
[    0.000000]   node   0: [mem 0x00000000b8400000-0x00000000bdffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 24 pages/cpu s58904 r8192 d31208 u98304
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Speculative Store Bypass Disable mitigation not required
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 507008
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk1p2 rootwait rw
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 1336512K/2060288K available (16316K kernel code, 1206K rwdata, 6432K rodata, 2816K init, 1012K bss, 68416K reserved, 655360K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from start_kernel+0x2b8/0x44c with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns
[    0.000369] Console: colour dummy device 80x25
[    0.000432] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.000440] pid_max: default: 32768 minimum: 301
[    0.000506] LSM: Security Framework initializing
[    0.000557] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.000568] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.001721] ASID allocator initialised with 32768 entries
[    0.001793] rcu: Hierarchical SRCU implementation.
[    0.002681] EFI services will not be available.
[    0.002836] smp: Bringing up secondary CPUs ...
[    0.003211] Detected VIPT I-cache on CPU1
[    0.003236] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.003267] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.003676] Detected VIPT I-cache on CPU2
[    0.003692] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.003710] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.004139] Detected VIPT I-cache on CPU3
[    0.004155] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.004171] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.004223] smp: Brought up 1 node, 4 CPUs
[    0.004232] SMP: Total of 4 processors activated.
[    0.004238] CPU features: detected: 32-bit EL0 Support
[    0.004245] CPU features: detected: CRC32 instructions
[    0.010726] CPU: All CPU(s) started at EL2
[    0.010746] alternatives: patching kernel code
[    0.012156] devtmpfs: initialized
[    0.018408] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.018425] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.034622] pinctrl core: initialized pinctrl subsystem
[    0.035321] DMI not present or invalid.
[    0.035578] NET: Registered protocol family 16
[    0.042380] DMA: preallocated 256 KiB pool for atomic allocations
[    0.042408] audit: initializing netlink subsys (disabled)
[    0.042646] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
[    0.043525] cpuidle: using governor menu
[    0.043992] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.044765] Serial: AMBA PL011 UART driver
[    0.044824] imx mu driver is registered.
[    0.044844] imx rpmsg driver is registered.
[    0.050595] imx8mm-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.070937] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.070947] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.070952] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.070959] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.071772] cryptd: max_cpu_qlen set to 1000
[    0.074828] ACPI: Interpreter disabled.
[    0.075717] iommu: Default domain type: Translated
[    0.075850] vgaarb: loaded
[    0.076132] SCSI subsystem initialized
[    0.076470] usbcore: registered new interface driver usbfs
[    0.076508] usbcore: registered new interface driver hub
[    0.076561] usbcore: registered new device driver usb
[    0.077718] mc: Linux media interface: v0.10
[    0.077747] videodev: Linux video capture interface: v2.00
[    0.077810] pps_core: LinuxPPS API ver. 1 registered
[    0.077816] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.077830] PTP clock support registered
[    0.077960] EDAC MC: Ver: 3.0.0
[    0.078730] No BMan portals available!
[    0.078948] QMan: Allocated lookup table at (____ptrval____), entry count 65537
[    0.079195] No QMan portals available!
[    0.079561] No USDPAA memory, no 'fsl,usdpaa-mem' in device-tree
[    0.079995] FPGA manager framework
[    0.080079] Advanced Linux Sound Architecture Driver Initialized.
[    0.080488] Bluetooth: Core ver 2.22
[    0.080512] NET: Registered protocol family 31
[    0.080519] Bluetooth: HCI device and connection manager initialized
[    0.080527] Bluetooth: HCI socket layer initialized
[    0.080535] Bluetooth: L2CAP socket layer initialized
[    0.080547] Bluetooth: SCO socket layer initialized
[    0.081245] clocksource: Switched to clocksource arch_sys_counter
[    0.081394] VFS: Disk quotas dquot_6.6.0
[    0.081439] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.081589] pnp: PnP ACPI: disabled
[    0.086976] thermal_sys: Registered thermal governor 'step_wise'
[    0.086979] thermal_sys: Registered thermal governor 'power_allocator'
[    0.087304] NET: Registered protocol family 2
[    0.087599] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    0.087633] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.087742] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.087970] TCP: Hash tables configured (established 16384 bind 16384)
[    0.088047] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.088089] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.088230] NET: Registered protocol family 1
[    0.088545] RPC: Registered named UNIX socket transport module.
[    0.088550] RPC: Registered udp transport module.
[    0.088554] RPC: Registered tcp transport module.
[    0.088558] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.088904] PCI: CLS 0 bytes, default 64
[    0.089573] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    0.089929] kvm [1]: IPA Size Limit: 40bits
[    0.090525] kvm [1]: GICv3: no GICV resource entry
[    0.090530] kvm [1]: disabling GICv2 emulation
[    0.090548] kvm [1]: GIC system register CPU interface enabled
[    0.090606] kvm [1]: vgic interrupt IRQ1
[    0.090693] kvm [1]: Hyp mode initialized successfully
[    0.093454] Initialise system trusted keyrings
[    0.093571] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[    0.099493] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.100118] NFS: Registering the id_resolver key type
[    0.100142] Key type id_resolver registered
[    0.100146] Key type id_legacy registered
[    0.100158] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.100179] jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
[    0.100531] 9p: Installing v9fs 9p2000 file system support
[    0.113666] Key type asymmetric registered
[    0.113673] Asymmetric key parser 'x509' registered
[    0.113709] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.113715] io scheduler mq-deadline registered
[    0.113720] io scheduler kyber registered
[    0.118440] EINJ: ACPI disabled.
[    0.127158] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.127171] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    0.135136] mxs-dma 33000000.dma-controller: initialized
[    0.136244] Bus freq driver module loaded
[    0.141388] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.143505] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 39, base_baud = 5000000) is a IMX
[    0.143986] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 40, base_baud = 5000000) is a IMX
[    0.144359] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 41, base_baud = 1500000) is a IMX
[    1.129142] printk: console [ttymxc1] enabled
[    1.139639] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.146274] [drm] No driver support for vblank timestamp query.
[    1.152273] imx-drm soc@0:bus@32c00000:display-subsystem: bound imx-lcdif-crtc.0 (ops lcdif_crtc_ops)
[    1.162188] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200
[    1.169742] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[    1.178019] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -517
[    1.194983] loop: module loaded
[    1.200219] imx ahci driver is registered.
[    1.207381] spi-nor spi3.0: n25q256ax1 (32768 Kbytes)
[    1.219068] libphy: Fixed MDIO Bus: probed
[    1.223974] tun: Universal TUN/TAP device driver, 1.6
[    1.229843] thunder_xcv, ver 1.0
[    1.233103] thunder_bgx, ver 1.0
[    1.236370] nicpf, ver 1.0
[    1.239917] pps pps0: new PPS source ptp0
[    1.249222] libphy: fec_enet_mii_bus: probed
[    1.254675] fec 30be0000.ethernet eth0: registered PHC device 0
[    1.261212] Freescale FM module, FMD API version 21.1.0
[    1.266699] Freescale FM Ports module
[    1.270371] fsl_mac: fsl_mac: FSL FMan MAC API based driver
[    1.276096] fsl_dpa: FSL DPAA Ethernet driver
[    1.280586] fsl_advanced: FSL DPAA Advanced drivers:
[    1.285560] fsl_proxy: FSL DPAA Proxy initialization driver
[    1.291241] fsl_oh: FSL FMan Offline Parsing port driver
[    1.297427] hclge is initializing
[    1.300745] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[    1.307973] hns3: Copyright (c) 2017 Huawei Corporation.
[    1.313335] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    1.320390] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.326173] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.332009] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.337967] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
[    1.344933] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.350547] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    1.358382] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.364468] sky2: driver version 1.30
[    1.369040] VFIO - User Level meta-driver version: 0.3
[    1.376006] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.382555] ehci-pci: EHCI PCI platform driver
[    1.387078] ehci-platform: EHCI generic platform driver
[    1.392487] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.398690] ohci-pci: OHCI PCI platform driver
[    1.403179] ohci-platform: OHCI generic platform driver
[    1.408958] usbcore: registered new interface driver usb-storage
[    1.415042] usbcore: registered new interface driver usbserial_generic
[    1.421590] usbserial: USB Serial support registered for generic
[    1.427626] usbcore: registered new interface driver ftdi_sio
[    1.433398] usbserial: USB Serial support registered for FTDI USB Serial Device
[    1.440735] usbcore: registered new interface driver usb_serial_simple
[    1.447281] usbserial: USB Serial support registered for carelink
[    1.453397] usbserial: USB Serial support registered for zio
[    1.459081] usbserial: USB Serial support registered for funsoft
[    1.465112] usbserial: USB Serial support registered for flashloader
[    1.471483] usbserial: USB Serial support registered for google
[    1.477422] usbserial: USB Serial support registered for libtransistor
[    1.483971] usbserial: USB Serial support registered for vivopay
[    1.489998] usbserial: USB Serial support registered for moto_modem
[    1.496288] usbserial: USB Serial support registered for motorola_tetra
[    1.502930] usbserial: USB Serial support registered for novatel_gps
[    1.509303] usbserial: USB Serial support registered for hp4x
[    1.515068] usbserial: USB Serial support registered for suunto
[    1.521010] usbserial: USB Serial support registered for siemens_mpi
[    1.528857] imx_usb 32e40000.usb: No over current polarity defined
[    1.536405] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/soc@0:bus@30000000/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
[    1.551579] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    1.557871] i2c /dev entries driver
[    1.562026] mx6s-csi 32e20000.csi1_bridge: initialising
[    1.567776] mxc_mipi-csi 32e30000.mipi_csi: 32e30000.mipi_csi supply mipi-phy not found, using dummy regulator
[    1.577998] mxc_mipi-csi 32e30000.mipi_csi: mipi csi v4l2 device registered
[    1.584973] CSI: Registered sensor subdevice: mxc_mipi-csi.0
[    1.590657] mxc_mipi-csi 32e30000.mipi_csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 333000000
[    1.604645] imx2-wdt 30280000.watchdog: timeout 60 sec (nowayout=0)
[    1.611250] Bluetooth: HCI UART driver ver 2.3
[    1.615707] Bluetooth: HCI UART protocol H4 registered
[    1.620853] Bluetooth: HCI UART protocol BCSP registered
[    1.626195] Bluetooth: HCI UART protocol LL registered
[    1.631343] Bluetooth: HCI UART protocol ATH3K registered
[    1.636763] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    1.643127] Bluetooth: HCI UART protocol Broadcom registered
[    1.648812] Bluetooth: HCI UART protocol QCA registered
[    1.655931] sdhci: Secure Digital Host Controller Interface driver
[    1.662128] sdhci: Copyright(c) Pierre Ossman
[    1.666686] Synopsys Designware Multimedia Card Interface Driver
[    1.673274] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.679707] mmc0: CQHCI version 5.10
[    1.683707] mmc1: CQHCI version 5.10
[    1.687754] mmc2: CQHCI version 5.10
[    1.723046] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.733183] ledtrig-cpu: registered to indicate activity on CPUs
[    1.740431] caam 30900000.crypto: device ID = 0x0a16040100000000 (Era 9)
[    1.747157] caam 30900000.crypto: job rings = 2, qi = 0
[    1.787984] caam algorithms registered in /proc/crypto
[    1.801233] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto
[    1.811825] caam_jr 30901000.jr: registering rng-caam
[    1.821987] caam-snvs 30370000.caam-snvs: can't get snvs clock
[    1.827873] caam-snvs 30370000.caam-snvs: violation handlers armed - non-secure state
[    1.836357] usbcore: registered new interface driver usbhid
[    1.841989] usbhid: USB HID core driver
[    1.848015] No fsl,qman node
[    1.850923] Freescale USDPAA process driver
[    1.855274] fsl-usdpaa: no region found
[    1.856619] mmc2: Command Queue Engine enabled
[    1.859138] Freescale USDPAA process IRQ driver
[    1.862559] optee: probing for conduit method from DT.
[    1.863619] mmc2: new HS400 Enhanced strobe MMC card at address 0001
[    1.868154] optee: revision 3.7 (7a49776d)
[    1.868370] optee: dynamic shared memory is enabled
[    1.874085] mmcblk2: mmc2:0001 DG4016 14.7 GiB
[    1.879854] optee: initialized driver
[    1.883889] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    1.890162] hantrodec 0 : module inserted. Major = 236
[    1.893334] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    1.897402] hantrodec 1 : module inserted. Major = 236
[    1.903181] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB, chardev (237:0)
[    1.908689] hx280enc: module inserted. Major <235>
[    1.916730]  mmcblk2: p1
[    1.922787] wm8524-codec audio-codec: Failed to get mute line: -517
[    1.982150] fsl-micfil-dai 30080000.micfil: GET IRQ: 16
[    1.987403] fsl-micfil-dai 30080000.micfil: GET IRQ: 17
[    1.992648] fsl-micfil-dai 30080000.micfil: GET IRQ: 18
[    1.997893] fsl-micfil-dai 30080000.micfil: GET IRQ: 19
[    2.009060] imx-spdif sound-spdif: snd-soc-dummy-dai <-> 30090000.spdif mapping ok
[    2.016713] imx-spdif sound-spdif: ASoC: no DMI vendor name!
[    2.025614] imx-ak4458 sound-ak4458: ASoC: failed to init link ak4458: -517
[    2.032597] imx-ak4458 sound-ak4458: snd_soc_register_card failed (-517)
[    2.039908] debugfs: Directory '30080000.micfil' with parent 'imx-audio-micfil' already present!
[    2.048786] imx-micfil sound-micfil: snd-soc-dummy-dai <-> 30080000.micfil mapping ok
[    2.056629] imx-micfil sound-micfil: ASoC: no DMI vendor name!
[    2.064569] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    2.075328] NET: Registered protocol family 26
[    2.080354] NET: Registered protocol family 10
[    2.085531] Segment Routing with IPv6
[    2.089255] NET: Registered protocol family 17
[    2.094094] Bluetooth: RFCOMM TTY layer initialized
[    2.098985] Bluetooth: RFCOMM socket layer initialized
[    2.104153] Bluetooth: RFCOMM ver 1.11
[    2.107913] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.113231] Bluetooth: BNEP filters: protocol multicast
[    2.118476] Bluetooth: BNEP socket layer initialized
[    2.123446] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    2.129377] Bluetooth: HIDP socket layer initialized
[    2.134381] 8021q: 802.1Q VLAN Support v1.8
[    2.138585] lib80211: common routines for IEEE802.11 drivers
[    2.144350] 9pnet: Installing 9P2000 support
[    2.148653] tsn generic netlink module v1 init...
[    2.153420] Key type dns_resolver registered
[    2.158672] registered taskstats version 1
[    2.162780] Loading compiled-in X.509 certificates
[    2.188510] usb_phy_generic usbphynop1: usbphynop1 supply vcc not found, using dummy regulator
[    2.197328] usb_phy_generic usbphynop2: usbphynop2 supply vcc not found, using dummy regulator
[    2.225696] ldo6: supplied by regulator-dummy
[    2.230852] i2c i2c-0: IMX I2C adapter registered
[    2.236757] adv7511 1-003d: 1-003d supply avdd not found, using dummy regulator
[    2.244135] adv7511 1-003d: 1-003d supply dvdd not found, using dummy regulator
[    2.251486] adv7511 1-003d: 1-003d supply pvdd not found, using dummy regulator
[    2.258839] adv7511 1-003d: 1-003d supply a2vdd not found, using dummy regulator
[    2.266275] adv7511 1-003d: 1-003d supply v3p3 not found, using dummy regulator
[    2.273642] adv7511 1-003d: 1-003d supply v1p2 not found, using dummy regulator
[    2.281768] adv7511 1-003d: Probe failed. Remote port 'mipi_dsi@32e10000' disabled
[    2.291113] i2c i2c-1: IMX I2C adapter registered
[    2.296952] pca953x 2-0020: using no AI
[    2.303463] ak4458 2-0010: Failed to request supplies: -517
[    2.309378] ak4458 2-0012: Failed to request supplies: -517
[    2.315232] ak5558 2-0013: Failed to request supplies: -517
[    2.321090] ak4458 2-0011: Failed to request supplies: -517
[    2.326985] ov5640_mipi 2-003c: No sensor reset pin available
[    2.332774] ov5640_mipi 2-003c: 2-003c supply DOVDD not found, using dummy regulator
[    2.340581] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator
[    2.348299] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator
[    2.369589] ov5640_mipi 2-003c: Read reg error: reg=300a
[    2.374910] ov5640_mipi 2-003c: Camera is not found
[    2.379952] i2c i2c-2: IMX I2C adapter registered
[    2.386551] imx6q-pcie 33800000.pcie: couldn't get pcie-phy
[    2.386669] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.392250] imx6q-pcie 33800000.pcie: 33800000.pcie supply epdev_on not found, using dummy regulator
[    2.398775] [drm] No driver support for vblank timestamp query.
[    2.398841] imx-drm soc@0:bus@32c00000:display-subsystem: bound imx-lcdif-crtc.0 (ops lcdif_crtc_ops)
[    2.408198] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
[    2.414520] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200
[    2.423085] imx6q-pcie 33800000.pcie:    IO 0x1ff80000..0x1ff8ffff -> 0x00000000
[    2.430858] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[    2.437263] imx6q-pcie 33800000.pcie:   MEM 0x18000000..0x1fefffff -> 0x18000000
[    2.444657] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -19
[    2.452982] imx6q-pcie 33800000.pcie: PLL REF_CLK is used!.
[    2.460332] imx-drm soc@0:bus@32c00000:display-subsystem: bound 32e10000.mipi_dsi (ops imx_sec_dsim_ops)
[    2.483536] [drm] Initialized imx-drm 1.0.0 20120507 for soc@0:bus@32c00000:display-subsystem on minor 0
[    2.493780] imx_usb 32e40000.usb: No over current polarity defined
[    2.500028] imx_usb 32e40000.usb: 32e40000.usb supply vbus not found, using dummy regulator
[    2.512378] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 3 mkt segment 0 supported-hw 0x8 0x1
[    2.524750] mmc0: CQHCI version 5.10
[    2.558686] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA
[    2.566886] mmc1: CQHCI version 5.10
[    2.570539] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    2.573641] imx6q-pcie 33800000.pcie: PCIe PLL locked after 20 us.
[    2.582031] random: fast init done
[    2.610646] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[    2.619963] debugfs: Directory '30020000.sai' with parent 'bt-sco-audio' already present!
[    2.628277] asoc-simple-card sound-bt-sco: bt-sco-pcm <-> 30020000.sai mapping ok
[    2.635792] asoc-simple-card sound-bt-sco: ASoC: no DMI vendor name!
[    2.642203] debugfs: File 'Playback' in directory 'dapm' already present!
[    2.649012] debugfs: File 'Capture' in directory 'dapm' already present!
[    2.657798] mmc0: queuing unknown CIS tuple 0x01 (3 bytes)
[    2.665135] debugfs: Directory '30030000.sai' with parent 'wm8524-audio' already present!
[    2.673476] asoc-simple-card sound-wm8524: wm8524-hifi <-> 30030000.sai mapping ok
[    2.681087] asoc-simple-card sound-wm8524: ASoC: no DMI vendor name!
[    2.694257] mmc0: queuing unknown CIS tuple 0x1a (5 bytes)
[    2.702036] imx-ak4458 sound-ak4458: ASoC: failed to init link ak4458: -517
[    2.709019] imx-ak4458 sound-ak4458: snd_soc_register_card failed (-517)
[    2.716421] mmc0: queuing unknown CIS tuple 0x1b (8 bytes)
[    2.722594] mmc0: queuing unknown CIS tuple 0x14 (0 bytes)
[    2.729355] OF: graph: no port node found in /soc@0/bus@30800000/i2c@30a30000/tcpc@50/connector
[    2.738117] OF: graph: no port node found in /soc@0/bus@30800000/i2c@30a30000/tcpc@50/connector
[    2.762216] mmc0: queuing unknown CIS tuple 0x80 (1 bytes)
[    2.767753] mmc0: queuing unknown CIS tuple 0x81 (1 bytes)
[    2.773309] mmc0: queuing unknown CIS tuple 0x82 (1 bytes)
[    2.778850] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[    3.110423] ak4458 2-0010: ASoC: failed to probe component -6
[    3.116299] imx-ak4458 sound-ak4458: ASoC: failed to instantiate card -6
[    3.123094] imx-ak4458 sound-ak4458: snd_soc_register_card failed (-6)
[    3.131764] input: bd718xx-pwrkey as /devices/platform/soc@0/soc@0:bus@30800000/30a20000.i2c/i2c-0/0-004b/gpio-keys.1.auto/input/input1
[    3.144798] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01T00:00:01 UTC (1)
[    3.154263] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    3.165385] mmc1: host does not support reading read-only switch, assuming write-enable
[    3.173736] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    3.180360] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    3.188990] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[    3.191524] ALSA device list:
[    3.199722]   #0: imx-spdif
[    3.202531]   #1: imx-audio-micfil
[    3.205947]   #2: bt-sco-audio
[    3.209003]   #3: wm8524-audio
[    3.285647] mmc1: new ultra high speed DDR50 SDHC card at address e624
[    3.293114] mmcblk1: mmc1:e624 SU16G 14.8 GiB
[    3.306939]  mmcblk1: p1 p2
[    3.590760] imx6q-pcie 33800000.pcie: Phy link never came up
[    3.596464] imx6q-pcie 33800000.pcie: failed to initialize host
[    3.602404] imx6q-pcie 33800000.pcie: unable to add pcie port.
[    3.626558] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[    3.634739] VFS: Mounted root (ext4 filesystem) on device 179:98.
[    3.642669] devtmpfs: mounted
[    3.646396] Freeing unused kernel memory: 2816K
[    3.651002] Run /sbin/init as init process
INIT: version 2.96 booting
Framebuffer /dev/fb0 not detected
Boot splashscreen disabled
Starting udev
[    3.982219] udevd[261]: starting version 3.2.9
[    4.005815] random: udevd: uninitialized urandom read (16 bytes read)
[    4.012954] random: udevd: uninitialized urandom read (16 bytes read)
[    4.020129] random: udevd: uninitialized urandom read (16 bytes read)
[    4.051898] udevd[262]: starting eudev-3.2.9
[    4.128369] imx-sdma 302b0000.dma-controller: external firmware not found, using ROM firmware
[    4.128403] imx-sdma 30bd0000.dma-controller: external firmware not found, using ROM firmware
[    4.147199] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    4.159436] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    4.236766] imx-sdma 302c0000.dma-controller: external firmware not found, using ROM firmware
[    4.403659] qca9377: loading out-of-tree module taints kernel.
[    4.498513] qca9377: loading driver v4.5.24.4
[    4.503229] hifDeviceInserted: Dumping clocks (50000000,400000000)
[    4.509526] AR6000: Set async interrupt delay clock as 2.
[    4.651016] AR6000: configuration opcode 3 is not used for Linux SDIO stack
[    4.663171] NUM_DEV=1 FWMODE=0x2 FWSUBMODE=0x0 FWBR_BUF 0
[    5.181234] HIF Interrupt processing is SYNC ONLY
[    5.185961] AR6000: configuration opcode 7 is only used for RTOS systems, not Linux systems
[    5.194317] AR6000: configuration opcode 5 is not used for Linux SDIO stack
[    5.202775] +HWT
[    5.210675] -HWT
[    5.213201] MAILBOX SWAP Service is enabled!
[    5.217486] Reduced Tx Complete service is enabled!
[    5.224931] HTCConnectService, host indicate support b2b bundle
[    5.234150] HTCConnectService, firmware decide to disabled b2b bundle
[    5.240603] HTC Service:0x0300 ep:1 TX flow control disabled
[    5.247021] HTCConnectService, host indicate support b2b bundle
[    5.254558] HTCConnectService, firmware decide to disabled b2b bundle
[    5.279005] target uses HTT version 3.53; host uses 3.28
[    5.284711] Host SW:4.5.24.4, FW:0.0.0.23, HW:QCA93x7_REV1_1
[    5.290557] ol_pktlog_init: pktlogmod_init successfull
[    5.295886] ath_hif_sdio: HIF (Atheros/multi-bss)
[    5.300630] qca9377: driver loaded in 800000
[    5.342974] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[    5.718048] urandom_read: 4 callbacks suppressed
[    5.718053] random: dd: uninitialized urandom read (512 bytes read)
[    5.822564] Atheros 8031 ethernet 30be0000.ethernet-1:00: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=30be0000.ethernet-1:00, irq=POLL)

[   12.065643] random: crng init done

umount: can't unmount /mnt/.psplash: No such file or directory

Poky (Yocto Project Reference Distro) 3.1.3 imx8mmevk /dev/ttymxc1

imx8mmevk login: root
root@imx8mmevk:~# rpm -qa | grep -i firmware
linux-firmware-ath10k-license-20200817-r0.noarch
firmware-qca9377-3.0.2-r0.noarch
firmware-imx-epdc-8.8-r0.noarch
linux-firmware-ath10k-20200817-r0.noarch
firmware-imx-sdma-imx7d-8.8-r0.noarch
root@imx8mmevk:~# cd /lib/firmware/imx/
root@imx8mmevk:/lib/firmware/imx# ls
epdc
root@imx8mmevk:/lib/firmware/imx#

... well, at least there is a /lib/firmware/imx directory this time.  Still no sign of sdma though!

I'm stumped.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 44052 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Otavio Salvador]

Em ter., 6 de out. de 2020 às 00:49, Brian Hutchinson
<b.hutchman@gmail.com> escreveu:
> On Mon, Oct 5, 2020 at 06:34 PM, Brian Hutchinson wrote:
> Another update ... decided to build core-image-base just in case it was related to core-image-minimal missing something ... I get the same sdma errors.  So I add IMAGE_INSTALL_append = " firmware-imx-sdma-imx7d firmware-imx-epdc" to local.conf.  Still get the errors.
...
> [    0.127158] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
> [    0.127171] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
...

> ... well, at least there is a /lib/firmware/imx directory this time.  Still no sign of sdma though!

I fixed this on master and dunfell; please do a repo sync and give it a new try.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]

On Tue, Oct 6, 2020 at 04:29 AM, Otavio Salvador wrote:

> 
> Em ter., 6 de out. de 2020 às 00:49, Brian Hutchinson
> <b.hutchman@gmail.com> escreveu:
> 
>> On Mon, Oct 5, 2020 at 06:34 PM, Brian Hutchinson wrote:
>> Another update ... decided to build core-image-base just in case it was
>> related to core-image-minimal missing something ... I get the same sdma
>> errors. So I add IMAGE_INSTALL_append = " firmware-imx-sdma-imx7d
>> firmware-imx-epdc" to local.conf. Still get the errors.
> 
> ...
> 
>> [ 0.127158] imx-sdma 302c0000.dma-controller: Direct firmware load for
>> imx/sdma/sdma-imx7d.bin failed with error -2
>> [ 0.127171] imx-sdma 302c0000.dma-controller: Falling back to sysfs
>> fallback for: imx/sdma/sdma-imx7d.bin
> 
> ...
> 
> 
>> ... well, at least there is a /lib/firmware/imx directory this time. Still
>> no sign of sdma though!
> 
> I fixed this on master and dunfell; please do a repo sync and give it a
> new try.

Hi Otavio,

That's great!  Just curious when was this done as I did a fresh repo init/sync of dunfell yesterday afternoon.

repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dunfell

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 1519 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Otavio Salvador]

Em ter., 6 de out. de 2020 às 09:04, Brian Hutchinson
<b.hutchman@gmail.com> escreveu:
> That's great!  Just curious when was this done as I did a fresh repo init/sync of dunfell yesterday afternoon.

20 minutes ago :-)


-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

On Tue, Oct 6, 2020 at 05:08 AM, Otavio Salvador wrote:

> 
> Em ter., 6 de out. de 2020 às 09:04, Brian Hutchinson
> <b.hutchman@gmail.com> escreveu:
> 
>> That's great! Just curious when was this done as I did a fresh repo
>> init/sync of dunfell yesterday afternoon.
> 
> 20 minutes ago :-)

Excellent!  Thank you!

I got to poking around in one of the include files and looks like I should have done:

MACHINE_FIRMWARE = 'MACHINE_FIRMWARE_append_mx7d'

... instead of:

IMAGE_INSTALL_append = " firmware-imx-sdma-imx7d firmware-imx-epdc"

... in local.conf.  Is one of these still needed or should it key off the fact I'm using a imx8mm evk machine?

Regards,

Brian
> 
> 
> 
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.br http://code.ossystems.com.br
> Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750

[-- Attachment #2: Type: text/html, Size: 1364 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Otavio Salvador]

Hello Brian,

See if below change fixes it:

diff --git a/conf/machine/include/imx-base.inc
b/conf/machine/include/imx-base.inc
index 83e49969..db27bd84 100644
--- a/conf/machine/include/imx-base.inc
+++ b/conf/machine/include/imx-base.inc
@@ -231,6 +231,7 @@ MACHINE_FIRMWARE_append_mx6sll = " firmware-imx-epdc"
 MACHINE_FIRMWARE_append_mx6ull = " firmware-imx-epdc"
 MACHINE_FIRMWARE_append_mx53 = " firmware-imx-vpu-imx53
firmware-imx-sdma-imx53"
 MACHINE_FIRMWARE_append_mx51 = " firmware-imx-vpu-imx51
firmware-imx-sdma-imx51"
+MACHINE_FIRMWARE_append_mx8mm  = " linux-firmware-imx-sdma-imx7d"
 MACHINE_FIRMWARE_append_mx8mp  = " firmware-imx-easrc-imx8mn
firmware-imx-xcvr-imx8mp firmware-sof-imx"
 MACHINE_FIRMWARE_append_use-mainline-bsp = "
linux-firmware-imx-sdma-imx6q linux-firmware-imx-sdma-imx7d
firmware-imx-vpu-imx6q firmware-imx-vpu-imx6d"




-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

On Tue, Oct 6, 2020 at 09:50 AM, Otavio Salvador wrote:

> 
> Hello Brian,
> 
> See if below change fixes it:
> 
> diff --git a/conf/machine/include/imx-base.inc
> b/conf/machine/include/imx-base.inc
> index 83e49969..db27bd84 100644
> --- a/conf/machine/include/imx-base.inc
> +++ b/conf/machine/include/imx-base.inc
> @@ -231,6 +231,7 @@ MACHINE_FIRMWARE_append_mx6sll = " firmware-imx-epdc"
> MACHINE_FIRMWARE_append_mx6ull = " firmware-imx-epdc"
> MACHINE_FIRMWARE_append_mx53 = " firmware-imx-vpu-imx53
> firmware-imx-sdma-imx53"
> MACHINE_FIRMWARE_append_mx51 = " firmware-imx-vpu-imx51
> firmware-imx-sdma-imx51"
> +MACHINE_FIRMWARE_append_mx8mm = " linux-firmware-imx-sdma-imx7d"
> MACHINE_FIRMWARE_append_mx8mp = " firmware-imx-easrc-imx8mn
> firmware-imx-xcvr-imx8mp firmware-sof-imx"
> MACHINE_FIRMWARE_append_use-mainline-bsp = "
> linux-firmware-imx-sdma-imx6q linux-firmware-imx-sdma-imx7d
> firmware-imx-vpu-imx6q firmware-imx-vpu-imx6d"

So I did build of core-image-minimal with local.conf containing MACHINE_FIRMWARE = 'MACHINE_FIRMWARE_append_mx7d' and still got the sdma errors.

No firmware-imx packages were installed and no /lib/firmware directory created so I guess that explains why.

Now I'm off trying core-image-base.  I'll comment out:

MACHINE_FIRMWARE = 'MACHINE_FIRMWARE_append_mx7d'

... and try that first.

Mush Ryzen 9 3900x, mush!

[-- Attachment #2: Type: text/html, Size: 1651 bytes --]

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 33131 bytes --]

More background information in case it matters.

I did my original setup with:
EULA=1 MACHINE =imx8mmevk DISTRO=poky source setup-environment build

... because I don't want/need graphics etc.

After Otavio did his change, I smoked sstate and tmp dir and rebuilt core-image-base.  Still get sdma errors and do not have /lib/firmware/imx / binaries.

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.4.69+gdd0d7d132f10 (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Sat Oct 3 16:05:58 UTC 2020
[    0.000000] Machine model: FSL i.MX8MM LPDDR4 EVK RevB board
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000078000000, size 640 MiB
[    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xbdbdd500-0xbdbdefff]
[    0.000000] Zone ranges:
[    0.000000]   DMA32    [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000b7ffffff]
[    0.000000]   node   0: [mem 0x00000000b8400000-0x00000000bdffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bdffffff]
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.1
[    0.000000] percpu: Embedded 24 pages/cpu s58904 r8192 d31208 u98304
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Speculative Store Bypass Disable mitigation not required
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 507008
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk1p2 rootwait rw
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 1336512K/2060288K available (16316K kernel code, 1206K rwdata, 6432K rodata, 2816K init, 1012K bss, 68416K reserved, 655360K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 128 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: no VLPI support, no direct LPI support
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[    0.000000] ITS: No ITS available, not enabling LPIs
[    0.000000] random: get_random_bytes called from start_kernel+0x2b8/0x44c with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[    0.000003] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns
[    0.000368] Console: colour dummy device 80x25
[    0.000433] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000)
[    0.000442] pid_max: default: 32768 minimum: 301
[    0.000509] LSM: Security Framework initializing
[    0.000561] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.000572] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.001725] ASID allocator initialised with 32768 entries
[    0.001795] rcu: Hierarchical SRCU implementation.
[    0.002674] EFI services will not be available.
[    0.002831] smp: Bringing up secondary CPUs ...
[    0.003207] Detected VIPT I-cache on CPU1
[    0.003231] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[    0.003264] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.003671] Detected VIPT I-cache on CPU2
[    0.003687] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[    0.003705] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.004125] Detected VIPT I-cache on CPU3
[    0.004140] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[    0.004156] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.004214] smp: Brought up 1 node, 4 CPUs
[    0.004223] SMP: Total of 4 processors activated.
[    0.004228] CPU features: detected: 32-bit EL0 Support
[    0.004235] CPU features: detected: CRC32 instructions
[    0.010798] CPU: All CPU(s) started at EL2
[    0.010819] alternatives: patching kernel code
[    0.012249] devtmpfs: initialized
[    0.018305] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.018322] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.034567] pinctrl core: initialized pinctrl subsystem
[    0.035263] DMI not present or invalid.
[    0.035517] NET: Registered protocol family 16
[    0.042286] DMA: preallocated 256 KiB pool for atomic allocations
[    0.042316] audit: initializing netlink subsys (disabled)
[    0.042552] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
[    0.043412] cpuidle: using governor menu
[    0.043815] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.044603] Serial: AMBA PL011 UART driver
[    0.044661] imx mu driver is registered.
[    0.044680] imx rpmsg driver is registered.
[    0.050379] imx8mm-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[    0.070353] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.070364] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.070369] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.070374] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.071199] cryptd: max_cpu_qlen set to 1000
[    0.074285] ACPI: Interpreter disabled.
[    0.075173] iommu: Default domain type: Translated
[    0.075315] vgaarb: loaded
[    0.075598] SCSI subsystem initialized
[    0.075917] usbcore: registered new interface driver usbfs
[    0.075954] usbcore: registered new interface driver hub
[    0.076005] usbcore: registered new device driver usb
[    0.077181] mc: Linux media interface: v0.10
[    0.077209] videodev: Linux video capture interface: v2.00
[    0.077270] pps_core: LinuxPPS API ver. 1 registered
[    0.077277] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.077296] PTP clock support registered
[    0.077432] EDAC MC: Ver: 3.0.0
[    0.078162] No BMan portals available!
[    0.078367] QMan: Allocated lookup table at (____ptrval____), entry count 65537
[    0.078615] No QMan portals available!
[    0.078979] No USDPAA memory, no 'fsl,usdpaa-mem' in device-tree
[    0.079371] FPGA manager framework
[    0.079452] Advanced Linux Sound Architecture Driver Initialized.
[    0.079850] Bluetooth: Core ver 2.22
[    0.079879] NET: Registered protocol family 31
[    0.079885] Bluetooth: HCI device and connection manager initialized
[    0.079893] Bluetooth: HCI socket layer initialized
[    0.079900] Bluetooth: L2CAP socket layer initialized
[    0.079912] Bluetooth: SCO socket layer initialized
[    0.080626] clocksource: Switched to clocksource arch_sys_counter
[    0.080789] VFS: Disk quotas dquot_6.6.0
[    0.080835] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.080988] pnp: PnP ACPI: disabled
[    0.086347] thermal_sys: Registered thermal governor 'step_wise'
[    0.086351] thermal_sys: Registered thermal governor 'power_allocator'
[    0.086676] NET: Registered protocol family 2
[    0.087007] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    0.087037] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.087146] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.087372] TCP: Hash tables configured (established 16384 bind 16384)
[    0.087449] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.087490] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.087623] NET: Registered protocol family 1
[    0.087946] RPC: Registered named UNIX socket transport module.
[    0.087951] RPC: Registered udp transport module.
[    0.087955] RPC: Registered tcp transport module.
[    0.087958] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.088337] PCI: CLS 0 bytes, default 64
[    0.088994] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[    0.089358] kvm [1]: IPA Size Limit: 40bits
[    0.089954] kvm [1]: GICv3: no GICV resource entry
[    0.089959] kvm [1]: disabling GICv2 emulation
[    0.089976] kvm [1]: GIC system register CPU interface enabled
[    0.090032] kvm [1]: vgic interrupt IRQ1
[    0.090122] kvm [1]: Hyp mode initialized successfully
[    0.092902] Initialise system trusted keyrings
[    0.093042] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[    0.098758] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.099374] NFS: Registering the id_resolver key type
[    0.099397] Key type id_resolver registered
[    0.099401] Key type id_legacy registered
[    0.099411] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.099430] jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
[    0.099769] 9p: Installing v9fs 9p2000 file system support
[    0.112940] Key type asymmetric registered
[    0.112947] Asymmetric key parser 'x509' registered
[    0.112979] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.112985] io scheduler mq-deadline registered
[    0.112990] io scheduler kyber registered
[    0.117751] EINJ: ACPI disabled.
[    0.126468] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.126481] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    0.134362] mxs-dma 33000000.dma-controller: initialized
[    0.135472] Bus freq driver module loaded
[    0.140617] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.142776] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 39, base_baud = 5000000) is a IMX
[    0.143243] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 40, base_baud = 5000000) is a IMX
[    0.143605] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 41, base_baud = 1500000) is a IMX
[    1.128381] printk: console [ttymxc1] enabled
[    1.138932] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.145570] [drm] No driver support for vblank timestamp query.
[    1.151568] imx-drm soc@0:bus@32c00000:display-subsystem: bound imx-lcdif-crtc.0 (ops lcdif_crtc_ops)
[    1.161489] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200
[    1.169037] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[    1.177314] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -517
[    1.194256] loop: module loaded
[    1.199500] imx ahci driver is registered.
[    1.206634] spi-nor spi3.0: n25q256ax1 (32768 Kbytes)
[    1.218432] libphy: Fixed MDIO Bus: probed
[    1.223294] tun: Universal TUN/TAP device driver, 1.6
[    1.229100] thunder_xcv, ver 1.0
[    1.232361] thunder_bgx, ver 1.0
[    1.235627] nicpf, ver 1.0
[    1.239161] pps pps0: new PPS source ptp0
[    1.248463] libphy: fec_enet_mii_bus: probed
[    1.253886] fec 30be0000.ethernet eth0: registered PHC device 0
[    1.260422] Freescale FM module, FMD API version 21.1.0
[    1.265896] Freescale FM Ports module
[    1.269568] fsl_mac: fsl_mac: FSL FMan MAC API based driver
[    1.275292] fsl_dpa: FSL DPAA Ethernet driver
[    1.279787] fsl_advanced: FSL DPAA Advanced drivers:
[    1.284763] fsl_proxy: FSL DPAA Proxy initialization driver
[    1.290455] fsl_oh: FSL FMan Offline Parsing port driver
[    1.296651] hclge is initializing
[    1.299968] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[    1.307197] hns3: Copyright (c) 2017 Huawei Corporation.
[    1.312557] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    1.319613] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    1.325394] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[    1.331232] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.337190] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.6.0-k
[    1.344157] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.349774] igbvf: Intel(R) Gigabit Virtual Function Network Driver - version 2.4.0-k
[    1.357608] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.363684] sky2: driver version 1.30
[    1.368253] VFIO - User Level meta-driver version: 0.3
[    1.375216] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.381762] ehci-pci: EHCI PCI platform driver
[    1.386284] ehci-platform: EHCI generic platform driver
[    1.391705] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.397908] ohci-pci: OHCI PCI platform driver
[    1.402387] ohci-platform: OHCI generic platform driver
[    1.408194] usbcore: registered new interface driver usb-storage
[    1.414276] usbcore: registered new interface driver usbserial_generic
[    1.420823] usbserial: USB Serial support registered for generic
[    1.426865] usbcore: registered new interface driver ftdi_sio
[    1.432649] usbserial: USB Serial support registered for FTDI USB Serial Device
[    1.439989] usbcore: registered new interface driver usb_serial_simple
[    1.446534] usbserial: USB Serial support registered for carelink
[    1.452651] usbserial: USB Serial support registered for zio
[    1.458331] usbserial: USB Serial support registered for funsoft
[    1.464358] usbserial: USB Serial support registered for flashloader
[    1.470730] usbserial: USB Serial support registered for google
[    1.476672] usbserial: USB Serial support registered for libtransistor
[    1.483220] usbserial: USB Serial support registered for vivopay
[    1.489247] usbserial: USB Serial support registered for moto_modem
[    1.495533] usbserial: USB Serial support registered for motorola_tetra
[    1.502167] usbserial: USB Serial support registered for novatel_gps
[    1.508543] usbserial: USB Serial support registered for hp4x
[    1.514315] usbserial: USB Serial support registered for suunto
[    1.520254] usbserial: USB Serial support registered for siemens_mpi
[    1.528117] imx_usb 32e40000.usb: No over current polarity defined
[    1.535658] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/soc@0:bus@30000000/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
[    1.550767] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[    1.557054] i2c /dev entries driver
[    1.561214] mx6s-csi 32e20000.csi1_bridge: initialising
[    1.566961] mxc_mipi-csi 32e30000.mipi_csi: 32e30000.mipi_csi supply mipi-phy not found, using dummy regulator
[    1.577149] mxc_mipi-csi 32e30000.mipi_csi: mipi csi v4l2 device registered
[    1.584124] CSI: Registered sensor subdevice: mxc_mipi-csi.0
[    1.589804] mxc_mipi-csi 32e30000.mipi_csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 333000000
[    1.603800] imx2-wdt 30280000.watchdog: timeout 60 sec (nowayout=0)
[    1.610393] Bluetooth: HCI UART driver ver 2.3
[    1.614849] Bluetooth: HCI UART protocol H4 registered
[    1.619998] Bluetooth: HCI UART protocol BCSP registered
[    1.625336] Bluetooth: HCI UART protocol LL registered
[    1.630482] Bluetooth: HCI UART protocol ATH3K registered
[    1.635904] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    1.642264] Bluetooth: HCI UART protocol Broadcom registered
[    1.647959] Bluetooth: HCI UART protocol QCA registered
[    1.655070] sdhci: Secure Digital Host Controller Interface driver
[    1.661270] sdhci: Copyright(c) Pierre Ossman
[    1.665827] Synopsys Designware Multimedia Card Interface Driver
[    1.672394] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.678834] mmc0: CQHCI version 5.10
[    1.682839] mmc1: CQHCI version 5.10
[    1.686888] mmc2: CQHCI version 5.10
[    1.722293] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA
[    1.732199] ledtrig-cpu: registered to indicate activity on CPUs
[    1.739408] caam 30900000.crypto: device ID = 0x0a16040100000000 (Era 9)
[    1.746179] caam 30900000.crypto: job rings = 2, qi = 0
[    1.761269] caam algorithms registered in /proc/crypto
[    1.767138] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto
[    1.776667] caam_jr 30901000.jr: registering rng-caam
[    1.785369] caam-snvs 30370000.caam-snvs: can't get snvs clock
[    1.791259] caam-snvs 30370000.caam-snvs: violation handlers armed - non-secure state
[    1.799724] usbcore: registered new interface driver usbhid
[    1.805325] usbhid: USB HID core driver
[    1.811586] No fsl,qman node
[    1.814491] Freescale USDPAA process driver
[    1.818681] fsl-usdpaa: no region found
[    1.822541] Freescale USDPAA process IRQ driver
[    1.830895] optee: probing for conduit method from DT.
[    1.836068] optee: revision 3.7 (7a49776d)
[    1.837489] optee: dynamic shared memory is enabled
[    1.846654] optee: initialized driver
[    1.851776] hantrodec 0 : module inserted. Major = 236
[    1.857470] hantrodec 1 : module inserted. Major = 236
[    1.863548] hx280enc: module inserted. Major <235>
[    1.864030] mmc2: Command Queue Engine enabled
[    1.872286] wm8524-codec audio-codec: Failed to get mute line: -517
[    1.872849] mmc2: new HS400 Enhanced strobe MMC card at address 0001
[    1.886243] mmcblk2: mmc2:0001 DG4016 14.7 GiB
[    1.890953] mmcblk2boot0: mmc2:0001 DG4016 partition 1 4.00 MiB
[    1.897036] mmcblk2boot1: mmc2:0001 DG4016 partition 2 4.00 MiB
[    1.903411] mmcblk2rpmb: mmc2:0001 DG4016 partition 3 4.00 MiB, chardev (237:0)
[    1.913593]  mmcblk2: p1
[    1.921448] fsl-micfil-dai 30080000.micfil: GET IRQ: 16
[    1.926699] fsl-micfil-dai 30080000.micfil: GET IRQ: 17
[    1.931944] fsl-micfil-dai 30080000.micfil: GET IRQ: 18
[    1.937188] fsl-micfil-dai 30080000.micfil: GET IRQ: 19
[    1.948366] imx-spdif sound-spdif: snd-soc-dummy-dai <-> 30090000.spdif mapping ok
[    1.955987] imx-spdif sound-spdif: ASoC: no DMI vendor name!
[    1.964815] imx-ak4458 sound-ak4458: ASoC: failed to init link ak4458: -517
[    1.971795] imx-ak4458 sound-ak4458: snd_soc_register_card failed (-517)
[    1.979181] debugfs: Directory '30080000.micfil' with parent 'imx-audio-micfil' already present!
[    1.988069] imx-micfil sound-micfil: snd-soc-dummy-dai <-> 30080000.micfil mapping ok
[    1.995911] imx-micfil sound-micfil: ASoC: no DMI vendor name!
[    2.003871] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    2.014244] NET: Registered protocol family 26
[    2.019255] NET: Registered protocol family 10
[    2.024697] Segment Routing with IPv6
[    2.028405] NET: Registered protocol family 17
[    2.033320] Bluetooth: RFCOMM TTY layer initialized
[    2.038227] Bluetooth: RFCOMM socket layer initialized
[    2.043399] Bluetooth: RFCOMM ver 1.11
[    2.047158] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.052477] Bluetooth: BNEP filters: protocol multicast
[    2.057713] Bluetooth: BNEP socket layer initialized
[    2.062681] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    2.068607] Bluetooth: HIDP socket layer initialized
[    2.073614] 8021q: 802.1Q VLAN Support v1.8
[    2.077819] lib80211: common routines for IEEE802.11 drivers
[    2.083589] 9pnet: Installing 9P2000 support
[    2.087889] tsn generic netlink module v1 init...
[    2.092668] Key type dns_resolver registered
[    2.097910] registered taskstats version 1
[    2.102018] Loading compiled-in X.509 certificates
[    2.127804] usb_phy_generic usbphynop1: usbphynop1 supply vcc not found, using dummy regulator
[    2.136638] usb_phy_generic usbphynop2: usbphynop2 supply vcc not found, using dummy regulator
[    2.165134] ldo6: supplied by regulator-dummy
[    2.170280] i2c i2c-0: IMX I2C adapter registered
[    2.176191] adv7511 1-003d: 1-003d supply avdd not found, using dummy regulator
[    2.183567] adv7511 1-003d: 1-003d supply dvdd not found, using dummy regulator
[    2.190925] adv7511 1-003d: 1-003d supply pvdd not found, using dummy regulator
[    2.198292] adv7511 1-003d: 1-003d supply a2vdd not found, using dummy regulator
[    2.205727] adv7511 1-003d: 1-003d supply v3p3 not found, using dummy regulator
[    2.213081] adv7511 1-003d: 1-003d supply v1p2 not found, using dummy regulator
[    2.221229] adv7511 1-003d: Probe failed. Remote port 'mipi_dsi@32e10000' disabled
[    2.230679] i2c i2c-1: IMX I2C adapter registered
[    2.236516] pca953x 2-0020: using no AI
[    2.242710] ak4458 2-0010: Failed to request supplies: -517
[    2.248610] ak4458 2-0012: Failed to request supplies: -517
[    2.254460] ak5558 2-0013: Failed to request supplies: -517
[    2.260350] ak4458 2-0011: Failed to request supplies: -517
[    2.266248] ov5640_mipi 2-003c: No sensor reset pin available
[    2.272036] ov5640_mipi 2-003c: 2-003c supply DOVDD not found, using dummy regulator
[    2.279841] ov5640_mipi 2-003c: 2-003c supply DVDD not found, using dummy regulator
[    2.287542] ov5640_mipi 2-003c: 2-003c supply AVDD not found, using dummy regulator
[    2.308964] ov5640_mipi 2-003c: Read reg error: reg=300a
[    2.314286] ov5640_mipi 2-003c: Camera is not found
[    2.319331] i2c i2c-2: IMX I2C adapter registered
[    2.325397] imx6q-pcie 33800000.pcie: couldn't get pcie-phy
[    2.326092] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.331085] imx6q-pcie 33800000.pcie: 33800000.pcie supply epdev_on not found, using dummy regulator
[    2.337610] [drm] No driver support for vblank timestamp query.
[    2.337683] imx-drm soc@0:bus@32c00000:display-subsystem: bound imx-lcdif-crtc.0 (ops lcdif_crtc_ops)
[    2.347002] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges:
[    2.353343] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200
[    2.361917] imx6q-pcie 33800000.pcie:    IO 0x1ff80000..0x1ff8ffff -> 0x00000000
[    2.369692] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi
[    2.376096] imx6q-pcie 33800000.pcie:   MEM 0x18000000..0x1fefffff -> 0x18000000
[    2.383494] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -19
[    2.391822] imx6q-pcie 33800000.pcie: PLL REF_CLK is used!.
[    2.399165] imx-drm soc@0:bus@32c00000:display-subsystem: bound 32e10000.mipi_dsi (ops imx_sec_dsim_ops)
[    2.422395] [drm] Initialized imx-drm 1.0.0 20120507 for soc@0:bus@32c00000:display-subsystem on minor 0
[    2.432652] imx_usb 32e40000.usb: No over current polarity defined
[    2.438898] imx_usb 32e40000.usb: 32e40000.usb supply vbus not found, using dummy regulator
[    2.451562] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 3 mkt segment 0 supported-hw 0x8 0x1
[    2.464014] mmc0: CQHCI version 5.10
[    2.498241] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA
[    2.506427] mmc1: CQHCI version 5.10
[    2.510077] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO
[    2.513014] imx6q-pcie 33800000.pcie: PCIe PLL locked after 20 us.
[    2.517232] random: fast init done
[    2.549377] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[    2.559081] debugfs: Directory '30020000.sai' with parent 'bt-sco-audio' already present!
[    2.567413] asoc-simple-card sound-bt-sco: bt-sco-pcm <-> 30020000.sai mapping ok
[    2.574935] asoc-simple-card sound-bt-sco: ASoC: no DMI vendor name!
[    2.581348] debugfs: File 'Playback' in directory 'dapm' already present!
[    2.588166] debugfs: File 'Capture' in directory 'dapm' already present!
[    2.598070] mmc0: queuing unknown CIS tuple 0x01 (3 bytes)
[    2.603880] debugfs: Directory '30030000.sai' with parent 'wm8524-audio' already present!
[    2.612178] asoc-simple-card sound-wm8524: wm8524-hifi <-> 30030000.sai mapping ok
[    2.619789] asoc-simple-card sound-wm8524: ASoC: no DMI vendor name!
[    2.633267] mmc0: queuing unknown CIS tuple 0x1a (5 bytes)
[    2.638796] imx-ak4458 sound-ak4458: ASoC: failed to init link ak4458: -517
[    2.645785] imx-ak4458 sound-ak4458: snd_soc_register_card failed (-517)
[    2.655165] OF: graph: no port node found in /soc@0/bus@30800000/i2c@30a30000/tcpc@50/connector
[    2.663891] mmc0: queuing unknown CIS tuple 0x1b (8 bytes)
[    2.669408] OF: graph: no port node found in /soc@0/bus@30800000/i2c@30a30000/tcpc@50/connector
[    2.678544] mmc0: queuing unknown CIS tuple 0x14 (0 bytes)
[    2.701006] mmc0: queuing unknown CIS tuple 0x80 (1 bytes)
[    2.706553] mmc0: queuing unknown CIS tuple 0x81 (1 bytes)
[    2.712091] mmc0: queuing unknown CIS tuple 0x82 (1 bytes)
[    2.717614] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[    3.015739] ak4458 2-0010: ASoC: failed to probe component -6
[    3.021623] imx-ak4458 sound-ak4458: ASoC: failed to instantiate card -6
[    3.028417] imx-ak4458 sound-ak4458: snd_soc_register_card failed (-6)
[    3.038629] input: bd718xx-pwrkey as /devices/platform/soc@0/soc@0:bus@30800000/30a20000.i2c/i2c-0/0-004b/gpio-keys.1.auto/input/input1
[    3.043169] mmc1: host does not support reading read-only switch, assuming write-enable
[    3.058841] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01T00:00:01 UTC (1)
[    3.068482] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    3.080886] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    3.087650] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    3.094899] ALSA device list:
[    3.096288] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[    3.099252]   #0: imx-spdif
[    3.109793]   #1: imx-audio-micfil
[    3.113207]   #2: bt-sco-audio
[    3.116263]   #3: wm8524-audio
[    3.172648] mmc1: new ultra high speed DDR50 SDHC card at address e624
[    3.180412] mmcblk1: mmc1:e624 SU16G 14.8 GiB
[    3.193719]  mmcblk1: p1 p2
[    3.522110] imx6q-pcie 33800000.pcie: Phy link never came up
[    3.527816] imx6q-pcie 33800000.pcie: failed to initialize host
[    3.533754] imx6q-pcie 33800000.pcie: unable to add pcie port.
[    3.558728] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[    3.566939] VFS: Mounted root (ext4 filesystem) on device 179:98.
[    3.574615] devtmpfs: mounted
[    3.578627] Freeing unused kernel memory: 2816K
[    3.583228] Run /sbin/init as init process
INIT: version 2.96 booting
Framebuffer /dev/fb0 not detected
Boot splashscreen disabled
Starting udev
[    3.911810] udevd[262]: starting version 3.2.9
[    3.938426] random: udevd: uninitialized urandom read (16 bytes read)
[    3.945596] random: udevd: uninitialized urandom read (16 bytes read)
[    3.952954] random: udevd: uninitialized urandom read (16 bytes read)
[    3.983631] udevd[263]: starting eudev-3.2.9
[    4.061197] imx-sdma 302b0000.dma-controller: external firmware not found, using ROM firmware
[    4.061234] imx-sdma 30bd0000.dma-controller: external firmware not found, using ROM firmware
[    4.079145] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    4.089778] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    4.180707] imx-sdma 302c0000.dma-controller: external firmware not found, using ROM firmware
[    4.333245] qca9377: loading out-of-tree module taints kernel.
[    4.431975] qca9377: loading driver v4.5.24.4
[    4.436739] hifDeviceInserted: Dumping clocks (50000000,400000000)
[    4.442993] AR6000: Set async interrupt delay clock as 2.
[    4.587585] AR6000: configuration opcode 3 is not used for Linux SDIO stack
[    4.598653] NUM_DEV=1 FWMODE=0x2 FWSUBMODE=0x0 FWBR_BUF 0
[    5.137761] HIF Interrupt processing is SYNC ONLY
[    5.142482] AR6000: configuration opcode 7 is only used for RTOS systems, not Linux systems
[    5.150865] AR6000: configuration opcode 5 is not used for Linux SDIO stack
[    5.161235] +HWT
[    5.168929] -HWT
[    5.172024] MAILBOX SWAP Service is enabled!
[    5.176319] Reduced Tx Complete service is enabled!
[    5.183719] HTCConnectService, host indicate support b2b bundle
[    5.191627] HTCConnectService, firmware decide to disabled b2b bundle
[    5.198073] HTC Service:0x0300 ep:1 TX flow control disabled
[    5.204434] HTCConnectService, host indicate support b2b bundle
[    5.214381] HTCConnectService, firmware decide to disabled b2b bundle
[    5.236549] target uses HTT version 3.53; host uses 3.28
[    5.242007] Host SW:4.5.24.4, FW:0.0.0.23, HW:QCA93x7_REV1_1
[    5.247890] ol_pktlog_init: pktlogmod_init successfull
[    5.253155] ath_hif_sdio: HIF (Atheros/multi-bss)
[    5.257940] qca9377: driver loaded in 828000
[    5.298178] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[    5.707824] urandom_read: 4 callbacks suppressed
[    5.707831] random: dd: uninitialized urandom read (512 bytes read)
[    5.811537] Atheros 8031 ethernet 30be0000.ethernet-1:00: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=30be0000.ethernet-1:00, irq=POLL)
[   11.417755] random: crng init done
umount: can't unmount /mnt/.psplash: No such file or directory

Poky (Yocto Project Reference Distro) 3.1.3 imx8mmevk /dev/ttymxc1

imx8mmevk login: root
root@imx8mmevk:~# rpm -qa | grep -i firmware
linux-firmware-ath10k-license-20200817-r0.noarch
firmware-qca9377-3.0.2-r0.noarch
linux-firmware-ath10k-20200817-r0.noarch
root@imx8mmevk:~# cd /lib/firmware/
LICENSE.QualcommAtheros_ath10k  ath10k/                         qca/                            qca9377/                        regulatory.db                   regulatory.db.p7s               wlan/

I noticed that my image size jumped form 329M to 621M so thought that was interesting.

Smoking sstate & tmp and trying build again with:

IMAGE_INSTALL_append = " firmware-imx-sdma-imx7d firmware-imx-epdc"

[-- Attachment #2: Type: text/html, Size: 42220 bytes --]

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 593 bytes --]

... what "distro" 'should' I be using since I have a custom board that's based on imx8mm evk but I don't necessarily want/need wifi, bluetooth, video, touchscreen etc.???

Is poky what's causing my pain?

I've been doing TI based builds forever and recently switched over to NXP based products so still learning the lay of the land.  I finally discovered I don't think I want to be building based off NXP releases from codeaurora and that Freescale is the better base for our products but not 100% clear what distro's are available and which ones I should focus on.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 629 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Andrey Zhizhikin]

Hello Brian,

On Tue, Oct 6, 2020 at 9:51 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> ... what "distro" 'should' I be using since I have a custom board that's based on imx8mm evk but I don't necessarily want/need wifi, bluetooth, video, touchscreen etc.???

I suggest you go with your own distro then, as you can leverage the
DISTRO_FEATURES in it yourself. You can either take any of 'fsl-'
prefixed distros over 'poky' if you need some NXP proprietary
components (e.g. VPU, GPU, etc), or take any of 'fslc-' prefixed ones
if you want to stay with mainline. Please note - I do not say that
'poky' would not work here! :) It is just a reference distro from
Yocto Project, which targets qemu on the first place, but also works
well for real HW.

This is the way we build our distro (derived from 'fsl-wayland'), and
so far it has proven to be working quite well. I also do sanity build
and run the 'fsl-wayland' off the master on imx8mmevk to make sure
there are no regressions.

>
> Is poky what's causing my pain?

You can see what distro features you have included when you do
'bitbake -e' and search for DISTRO_FEATURES. If you have (and
according to what you say - you do :) ) some pieces you do not need -
you can always either not include them in your custom distro, or use
DISTRO_FEATURES_remove = "<unneeded list>".

>
> I've been doing TI based builds forever and recently switched over to NXP based products so still learning the lay of the land.  I finally discovered I don't think I want to be building based off NXP releases from codeaurora and that Freescale is the better base for our products but not 100% clear what distro's are available and which ones I should focus on.

Those distros are located in a meta-freescale-distro layer, you can
peek there to see what's available.

>
> Regards,
>
> Brian
> 
>


-- 
Regards,
Andrey.

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 2485 bytes --]

On Tue, Oct 6, 2020 at 01:22 PM, Andrey Zhizhikin wrote:

> 
> Hello Brian,
> 
> On Tue, Oct 6, 2020 at 9:51 PM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> 
>> ... what "distro" 'should' I be using since I have a custom board that's
>> based on imx8mm evk but I don't necessarily want/need wifi, bluetooth,
>> video, touchscreen etc.???
> 
> I suggest you go with your own distro then, as you can leverage the
> DISTRO_FEATURES in it yourself. You can either take any of 'fsl-'
> prefixed distros over 'poky' if you need some NXP proprietary
> components (e.g. VPU, GPU, etc), or take any of 'fslc-' prefixed ones
> if you want to stay with mainline. Please note - I do not say that
> 'poky' would not work here! :) It is just a reference distro from
> Yocto Project, which targets qemu on the first place, but also works
> well for real HW.
> 
> This is the way we build our distro (derived from 'fsl-wayland'), and
> so far it has proven to be working quite well. I also do sanity build
> and run the 'fsl-wayland' off the master on imx8mmevk to make sure
> there are no regressions.

When I did NXP released builds I would use fsl-wayland distro but if memory serves me right a core-image-minimal would not boot.  Only core-image-base images did and they were quite large.

I do need to create my own distro but kind of would like to start from core-image-minimal and build up rather than take something like fsl-wayland and try to figure out what I don't need.  Being new to NXP family this approach "feels" more logical.

> 
> 
>> Is poky what's causing my pain?
> 
> You can see what distro features you have included when you do
> 'bitbake -e' and search for DISTRO_FEATURES. If you have (and
> according to what you say - you do :) ) some pieces you do not need -
> you can always either not include them in your custom distro, or use
> DISTRO_FEATURES_remove = "<unneeded list>".
> 
> 
>> I've been doing TI based builds forever and recently switched over to NXP
>> based products so still learning the lay of the land. I finally discovered
>> I don't think I want to be building based off NXP releases from codeaurora
>> and that Freescale is the better base for our products but not 100% clear
>> what distro's are available and which ones I should focus on.
> 
> Those distros are located in a meta-freescale-distro layer, you can
> peek there to see what's available.

I'll look.   Thanks

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 2650 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Andrey Zhizhikin]

On Tue, Oct 6, 2020 at 10:44 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> On Tue, Oct 6, 2020 at 01:22 PM, Andrey Zhizhikin wrote:
>
> Hello Brian,
>
> On Tue, Oct 6, 2020 at 9:51 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> ... what "distro" 'should' I be using since I have a custom board that's based on imx8mm evk but I don't necessarily want/need wifi, bluetooth, video, touchscreen etc.???
>
> I suggest you go with your own distro then, as you can leverage the
> DISTRO_FEATURES in it yourself. You can either take any of 'fsl-'
> prefixed distros over 'poky' if you need some NXP proprietary
> components (e.g. VPU, GPU, etc), or take any of 'fslc-' prefixed ones
> if you want to stay with mainline. Please note - I do not say that
> 'poky' would not work here! :) It is just a reference distro from
> Yocto Project, which targets qemu on the first place, but also works
> well for real HW.
>
> This is the way we build our distro (derived from 'fsl-wayland'), and
> so far it has proven to be working quite well. I also do sanity build
> and run the 'fsl-wayland' off the master on imx8mmevk to make sure
> there are no regressions.
>
> When I did NXP released builds I would use fsl-wayland distro but if memory serves me right a core-image-minimal would not boot.  Only core-image-base images did and they were quite large.
>
> I do need to create my own distro but kind of would like to start from core-image-minimal and build up rather than take something like fsl-wayland and try to figure out what I don't need.  Being new to NXP family this approach "feels" more logical.

I think you're mixing up 2 conceptual points here: distro vs image.
You can have a wayland distro, but only include a handful of packages
and features of it into the image. Distro does not define the content
of the image, image recipe does.

Section 4.3.2. of Yocto Overview Manual gives a very nice overview of
those concepts:
https://www.yoctoproject.org/docs/3.1.2/overview-manual/overview-manual.html#metadata-machine-configuration-and-policy-configuration

>
> Is poky what's causing my pain?
>
> You can see what distro features you have included when you do
> 'bitbake -e' and search for DISTRO_FEATURES. If you have (and
> according to what you say - you do :) ) some pieces you do not need -
> you can always either not include them in your custom distro, or use
> DISTRO_FEATURES_remove = "<unneeded list>".
>
> I've been doing TI based builds forever and recently switched over to NXP based products so still learning the lay of the land. I finally discovered I don't think I want to be building based off NXP releases from codeaurora and that Freescale is the better base for our products but not 100% clear what distro's are available and which ones I should focus on.
>
> Those distros are located in a meta-freescale-distro layer, you can
> peek there to see what's available.
>
> I'll look.   Thanks
>
> Regards,
>
> Brian
> 
>


-- 
Regards,
Andrey.

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Andrey Zhizhikin]

Hello Brian,

On Tue, Oct 6, 2020 at 10:44 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> On Tue, Oct 6, 2020 at 01:22 PM, Andrey Zhizhikin wrote:
>
> Hello Brian,
>
> On Tue, Oct 6, 2020 at 9:51 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> ... what "distro" 'should' I be using since I have a custom board that's based on imx8mm evk but I don't necessarily want/need wifi, bluetooth, video, touchscreen etc.???
>
> I suggest you go with your own distro then, as you can leverage the
> DISTRO_FEATURES in it yourself. You can either take any of 'fsl-'
> prefixed distros over 'poky' if you need some NXP proprietary
> components (e.g. VPU, GPU, etc), or take any of 'fslc-' prefixed ones
> if you want to stay with mainline. Please note - I do not say that
> 'poky' would not work here! :) It is just a reference distro from
> Yocto Project, which targets qemu on the first place, but also works
> well for real HW.
>
> This is the way we build our distro (derived from 'fsl-wayland'), and
> so far it has proven to be working quite well. I also do sanity build
> and run the 'fsl-wayland' off the master on imx8mmevk to make sure
> there are no regressions.
>
> When I did NXP released builds I would use fsl-wayland distro but if memory serves me right a core-image-minimal would not boot.  Only core-image-base images did and they were quite large.

I just did a following build:
$ MACHINE=imx8mmevk DISTRO=fsl-wayland bitbake core-image-minimal

Image produced boots fine on i.MX8M Mini EVK.

Runtime device info:
# cat /etc/os-release
ID=fsl-wayland
NAME="FSL Wayland"
VERSION="3.2-snapshot-20201008 (master)"
VERSION_ID=3.2-snapshot-20201008
PRETTY_NAME="FSL Wayland 3.2-snapshot-20201008 (master)"

# uname -a
Linux imx8mmevk 5.4.24+gbabac008e5cf #1 SMP PREEMPT Sat May 30
07:25:46 UTC 2020 aarch64 GNU/Linux

Please note: with this configuration you would get a kernel from NXP
(versioned 5.4.24). If you would like to utilize the NXP kernel with
latest stable patch level, you should switch
PREFERRED_PROVIDER_virtual/kernel_mx8mm = "linux-imx" to
PREFERRED_PROVIDER_virtual/kernel_mx8mm = "linux-imx-fslc"


>.

> I do need to create my own distro but kind of would like to start from core-image-minimal and build up rather than take something like fsl-wayland and try to figure out what I don't need.  Being new to NXP family this approach "feels" more logical.
>
> Is poky what's causing my pain?
>
> You can see what distro features you have included when you do
> 'bitbake -e' and search for DISTRO_FEATURES. If you have (and
> according to what you say - you do :) ) some pieces you do not need -
> you can always either not include them in your custom distro, or use
> DISTRO_FEATURES_remove = "<unneeded list>".
>
> I've been doing TI based builds forever and recently switched over to NXP based products so still learning the lay of the land. I finally discovered I don't think I want to be building based off NXP releases from codeaurora and that Freescale is the better base for our products but not 100% clear what distro's are available and which ones I should focus on.
>
> Those distros are located in a meta-freescale-distro layer, you can
> peek there to see what's available.
>
> I'll look.   Thanks
>
> Regards,
>
> Brian
> 
>


--
Regards,
Andrey.

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Otavio Salvador]

Hello all,

Em qui., 8 de out. de 2020 às 06:10, Andrey Zhizhikin
<andrey.z@gmail.com> escreveu:
> Please note: with this configuration you would get a kernel from NXP
> (versioned 5.4.24). If you would like to utilize the NXP kernel with
> latest stable patch level, you should switch
> PREFERRED_PROVIDER_virtual/kernel_mx8mm = "linux-imx" to
> PREFERRED_PROVIDER_virtual/kernel_mx8mm = "linux-imx-fslc"

For all i.MX8 the fslc distributions use the NXP BSP by default so
using 'fslc-wayland' should work just fine.

...
> > You can see what distro features you have included when you do
> > 'bitbake -e' and search for DISTRO_FEATURES. If you have (and
> > according to what you say - you do :) ) some pieces you do not need -
> > you can always either not include them in your custom distro, or use
> > DISTRO_FEATURES_remove = "<unneeded list>".
> >
> > I've been doing TI based builds forever and recently switched over to NXP based products so still learning the lay of the land. I finally discovered I don't think I want to be building based off NXP releases from codeaurora and that Freescale is the better base for our products but not 100% clear what distro's are available and which ones I should focus on.
> >
> > Those distros are located in a meta-freescale-distro layer, you can
> > peek there to see what's available.
> >
> > I'll look.   Thanks

For products we, at O.S. Systems, have been using our OEL[1]
distribution as a baseline where we create the product specific one.

1. https://github.com/OSSystemsEmbeddedLinux/ossystems-embedded-linux-platform

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]

On Tue, Oct 6, 2020 at 12:42 PM, Brian Hutchinson wrote:

> 
> 
> 
> Smoking sstate & tmp and trying build again with:
> 
> 
> IMAGE_INSTALL_append = " firmware-imx-sdma-imx7d firmware-imx-epdc"
> 

So just finished the above cycle and flashed sdcard.  Think we got somewhere this time!

I get only one instance of sdma error:

[    0.117495] EINJ: ACPI disabled.
[    0.126332] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[    0.126346] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[    0.134253] mxs-dma 33000000.dma-controller: initialized
[    0.135378] Bus freq driver module loaded

... of note here is it didn't say it was using ROM version!!!!

And I have firmware package for sdma now:

root@imx8mmevk:~# rpm -qa | grep -i firmware
linux-firmware-ath10k-license-20200817-r0.noarch
firmware-qca9377-3.0.2-r0.noarch
firmware-imx-epdc-8.8-r0.noarch
linux-firmware-ath10k-20200817-r0.noarch
firmware-imx-sdma-imx7d-8.8-r0.noarch

root@imx8mmevk:/lib/firmware# ls -l
-rw-r--r--    1 root     root          2713 Mar  9 12:34 LICENSE.QualcommAtheros_ath10k
drwxr-xr-x   11 root     root          1024 Mar  9 12:34 ath10k
drwxr-xr-x    4 root     root          1024 Mar  9 12:34 imx
drwxr-xr-x    2 root     root          1024 Mar  9 12:34 qca
drwxr-xr-x    2 root     root          1024 Mar  9 12:34 qca9377
-rw-r--r--    1 root     root          3764 Mar  9 12:34 regulatory.db
-rw-r--r--    1 root     root          1182 Mar  9 12:34 regulatory.db.p7s
drwxr-xr-x    3 root     root          1024 Mar  9 12:34 wlan

... and /lib/firmware/imx/sdma looks like:

root@imx8mmevk:/lib/firmware/imx/sdma# ls
sdma-imx7d.bin

So hopefully this helps with the ALSA issue I was chasing that led me to this sdma issue in the first place!

Thanks guys!  I don't know why core-image-minimal isn't working ... I see there is a firmware-imx-8m package so maybe I should add it.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 4232 bytes --]

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

... noticed this in dmesg:

[    4.003745] udevd[263]: starting eudev-3.2.9
[    4.086853] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
[    4.354370] qca9377: loading out-of-tree module taints kernel.
[    4.447875] qca9377: loading driver v4.5.24.4

... curious because I think 4.5 is ROM version ... 8.8 is version of binary in imx-sdma firmware package.

[-- Attachment #2: Type: text/html, Size: 1482 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Fabio Estevam]

On Tue, Oct 6, 2020 at 6:26 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> ... noticed this in dmesg:
>
> [    4.003745] udevd[263]: starting eudev-3.2.9
> [    4.086853] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
> [    4.354370] qca9377: loading out-of-tree module taints kernel.
> [    4.447875] qca9377: loading driver v4.5.24.4
>
> ... curious because I think 4.5 is ROM version ... 8.8 is version of binary in imx-sdma firmware package.

No, 4.5 is the external SDMA firmware version. This looks correct.

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 634 bytes --]

On Tue, Oct 6, 2020 at 04:15 PM, Fabio Estevam wrote:

> 
> On Tue, Oct 6, 2020 at 6:26 PM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> 
>> 
>> ... noticed this in dmesg:
>> 
>> [ 4.003745] udevd[263]: starting eudev-3.2.9
>> [ 4.086853] imx-sdma 302b0000.dma-controller: loaded firmware 4.5
>> [ 4.354370] qca9377: loading out-of-tree module taints kernel.
>> [ 4.447875] qca9377: loading driver v4.5.24.4
>> 
>> ... curious because I think 4.5 is ROM version ... 8.8 is version of
>> binary in imx-sdma firmware package.
> 
> No, 4.5 is the external SDMA firmware version. This looks correct.

Ok, thanks!

[-- Attachment #2: Type: text/html, Size: 680 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Andrey Zhizhikin]

Hello Brian,

On Tue, Oct 6, 2020 at 10:58 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> On Tue, Oct 6, 2020 at 12:42 PM, Brian Hutchinson wrote:
>
>
>
> Smoking sstate & tmp and trying build again with:
>
>
> IMAGE_INSTALL_append = " firmware-imx-sdma-imx7d firmware-imx-epdc"
>
> So just finished the above cycle and flashed sdcard.  Think we got somewhere this time!
>
> I get only one instance of sdma error:
>
> [    0.117495] EINJ: ACPI disabled.
> [    0.126332] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
> [    0.126346] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
> [    0.134253] mxs-dma 33000000.dma-controller: initialized
> [    0.135378] Bus freq driver module loaded
>
> ... of note here is it didn't say it was using ROM version!!!!
>
> And I have firmware package for sdma now:
>
> root@imx8mmevk:~# rpm -qa | grep -i firmware
> linux-firmware-ath10k-license-20200817-r0.noarch
> firmware-qca9377-3.0.2-r0.noarch
> firmware-imx-epdc-8.8-r0.noarch
> linux-firmware-ath10k-20200817-r0.noarch
> firmware-imx-sdma-imx7d-8.8-r0.noarch
>
>
> root@imx8mmevk:/lib/firmware# ls -l
> -rw-r--r--    1 root     root          2713 Mar  9 12:34 LICENSE.QualcommAtheros_ath10k
> drwxr-xr-x   11 root     root          1024 Mar  9 12:34 ath10k
> drwxr-xr-x    4 root     root          1024 Mar  9 12:34 imx
> drwxr-xr-x    2 root     root          1024 Mar  9 12:34 qca
> drwxr-xr-x    2 root     root          1024 Mar  9 12:34 qca9377
> -rw-r--r--    1 root     root          3764 Mar  9 12:34 regulatory.db
> -rw-r--r--    1 root     root          1182 Mar  9 12:34 regulatory.db.p7s
> drwxr-xr-x    3 root     root          1024 Mar  9 12:34 wlan
>
> ... and /lib/firmware/imx/sdma looks like:
>
> root@imx8mmevk:/lib/firmware/imx/sdma# ls
> sdma-imx7d.bin
>
> So hopefully this helps with the ALSA issue I was chasing that led me to this sdma issue in the first place!
>
> Thanks guys!  I don't know why core-image-minimal isn't working ...

Well, this is I guess an expected behavior. firmware packages are
listed in MACHINE_EXTRA_RRECOMMENDS, which is (according to Yocto
Reference manual, link
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-MACHINE_EXTRA_RRECOMMENDS)
is only considered when packagegroup-base is installed in the image
and does not affect 'core-image-minimal' or 'core-image-full-cmdline'
images.

That is the reason that even if the package is added in the
imx-base.inc (like Otavio suggested in his patch) - you would not
receive it in core-image-minimal and you would have to install it
explicitly.

As for firmware packages themselves, I guess it should be changed from
MACHINE_EXTRA_RRECOMMENDS to MACHINE_EXTRA_RDEPENDS in order to bail
out at the build time rather than figure out that they are not present
on the device at boot time. But this is yet a separate point, which
actually would not solve your original issue as you either need an
image recipe which includes packagegroup-base or you have to
explicitly list them in IMAGE_INSTALL.

> I see there is a firmware-imx-8m package so maybe I should add it.

This package is actually empty, and only serves as a deploy target to
provide Cadence HDMI FW for imx-boot to build a boot container. Even
if you try to install it - you would not receive any FW files on the
target.

>
> Regards,
>
> Brian
>
>
> 
>


-- 
Regards,
Andrey.

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

On Wed, Oct 7, 2020 at 5:49 AM Andrey Zhizhikin <andrey.z@gmail.com> wrote:

> Hello Brian,
>
>
> Well, this is I guess an expected behavior. firmware packages are
> listed in MACHINE_EXTRA_RRECOMMENDS, which is (according to Yocto
> Reference manual, link
>
> https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-MACHINE_EXTRA_RRECOMMENDS
> )
> is only considered when packagegroup-base is installed in the image
> and does not affect 'core-image-minimal' or 'core-image-full-cmdline'
> images.
>
> That is the reason that even if the package is added in the
> imx-base.inc (like Otavio suggested in his patch) - you would not
> receive it in core-image-minimal and you would have to install it
> explicitly.
>
> As for firmware packages themselves, I guess it should be changed from
> MACHINE_EXTRA_RRECOMMENDS to MACHINE_EXTRA_RDEPENDS in order to bail
> out at the build time rather than figure out that they are not present
> on the device at boot time. But this is yet a separate point, which
> actually would not solve your original issue as you either need an
> image recipe which includes packagegroup-base or you have to
> explicitly list them in IMAGE_INSTALL.
>
> > I see there is a firmware-imx-8m package so maybe I should add it.
>
> This package is actually empty, and only serves as a deploy target to
> provide Cadence HDMI FW for imx-boot to build a boot container. Even
> if you try to install it - you would not receive any FW files on the
> target.
>
>
>
Hate to bring up an old thread again but I'm back to trying to pair down my
image size and trying to use core-image-minimal and having issues with
firmware-imx-sdma-imx7d & sdma-imx7d.bin

If I just build imx-sdma as a kernel module do I even need to worry about
sdma-imx7d.bin being in the rootfs?

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 2485 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1.1: Type: text/plain, Size: 2079 bytes --]

On Thu, Jul 15, 2021 at 7:49 PM Brian Hutchinson via lists.yoctoproject.org
<b.hutchman=gmail.com@lists.yoctoproject.org> wrote:

>
>
> On Wed, Oct 7, 2020 at 5:49 AM Andrey Zhizhikin <andrey.z@gmail.com>
> wrote:
>
>> Hello Brian,
>>
>>
>> Well, this is I guess an expected behavior. firmware packages are
>> listed in MACHINE_EXTRA_RRECOMMENDS, which is (according to Yocto
>> Reference manual, link
>>
>> https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-MACHINE_EXTRA_RRECOMMENDS
>> )
>> is only considered when packagegroup-base is installed in the image
>> and does not affect 'core-image-minimal' or 'core-image-full-cmdline'
>> images.
>>
>> That is the reason that even if the package is added in the
>> imx-base.inc (like Otavio suggested in his patch) - you would not
>> receive it in core-image-minimal and you would have to install it
>> explicitly.
>>
>> As for firmware packages themselves, I guess it should be changed from
>> MACHINE_EXTRA_RRECOMMENDS to MACHINE_EXTRA_RDEPENDS in order to bail
>> out at the build time rather than figure out that they are not present
>> on the device at boot time. But this is yet a separate point, which
>> actually would not solve your original issue as you either need an
>> image recipe which includes packagegroup-base or you have to
>> explicitly list them in IMAGE_INSTALL.
>>
>> > I see there is a firmware-imx-8m package so maybe I should add it.
>>
>> This package is actually empty, and only serves as a deploy target to
>> provide Cadence HDMI FW for imx-boot to build a boot container. Even
>> if you try to install it - you would not receive any FW files on the
>> target.
>>
>>
>>
> Hate to bring up an old thread again but I'm back to trying to pair down
> my image size and trying to use core-image-minimal and having issues with
> firmware-imx-sdma-imx7d & sdma-imx7d.bin
>
> If I just build imx-sdma as a kernel module do I even need to worry about
> sdma-imx7d.bin being in the rootfs?
>
> Anyone? Anyone?
[image: anyone-anyone.jpg]

[-- Attachment #1.2: Type: text/html, Size: 3062 bytes --]

[-- Attachment #2: anyone-anyone.jpg --]
[-- Type: image/jpeg, Size: 314944 bytes --]

Re: [meta-freescale] How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Andrey Zhizhikin]

Hello Otavio / Brian,

On Tue, Oct 6, 2020 at 7:10 PM Brian Hutchinson <b.hutchman@gmail.com> wrote:
>
> On Tue, Oct 6, 2020 at 09:50 AM, Otavio Salvador wrote:
>
> Hello Brian,
>
> See if below change fixes it:

That should actually do the trick! I just realized that the mx8m is
completely missing the MACHINE_FIRMWARE definition. I'm starting to
wonder - was it actually ever defined for mx8m?

Let me try this out on the imx8mmevk, I'll get back on this one.

>
> diff --git a/conf/machine/include/imx-base.inc
> b/conf/machine/include/imx-base.inc
> index 83e49969..db27bd84 100644
> --- a/conf/machine/include/imx-base.inc
> +++ b/conf/machine/include/imx-base.inc
> @@ -231,6 +231,7 @@ MACHINE_FIRMWARE_append_mx6sll = " firmware-imx-epdc"
> MACHINE_FIRMWARE_append_mx6ull = " firmware-imx-epdc"
> MACHINE_FIRMWARE_append_mx53 = " firmware-imx-vpu-imx53
> firmware-imx-sdma-imx53"
> MACHINE_FIRMWARE_append_mx51 = " firmware-imx-vpu-imx51
> firmware-imx-sdma-imx51"
> +MACHINE_FIRMWARE_append_mx8mm = " linux-firmware-imx-sdma-imx7d"
> MACHINE_FIRMWARE_append_mx8mp = " firmware-imx-easrc-imx8mn
> firmware-imx-xcvr-imx8mp firmware-sof-imx"
> MACHINE_FIRMWARE_append_use-mainline-bsp = "
> linux-firmware-imx-sdma-imx6q linux-firmware-imx-sdma-imx7d
> firmware-imx-vpu-imx6q firmware-imx-vpu-imx6d"
>
> So I did build of core-image-minimal with local.conf containing MACHINE_FIRMWARE = 'MACHINE_FIRMWARE_append_mx7d' and still got the sdma errors.
>
> No firmware-imx packages were installed and no /lib/firmware directory created so I guess that explains why.
>
> Now I'm off trying core-image-base.  I'll comment out:
>
> MACHINE_FIRMWARE = 'MACHINE_FIRMWARE_append_mx7d'
>
> ... and try that first.

Brian,
Did you try Otavio's patch? Would be curious to know if that solved
the absence of SDMA FW package for you.

>
> Mush Ryzen 9 3900x, mush!
>
> 
>


-- 
Regards,
Andrey.

Re: How to get firmware-imx for imx8mm evk into sdcard image? I'm getting firmware loading errors for sdma-imx7d.bin etc.

[Brian Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 322 bytes --]

On Tue, Oct 6, 2020 at 01:28 PM, Andrey Zhizhikin wrote:

> 
> 
>> Mush Ryzen 9 3900x, mush!Brian,
>> Did you try Otavio's patch? Would be curious to know if that solved
>> the absence of SDMA FW package for you.
> 
> 

I did a repo sync before building.  Did I need to do something else?

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 381 bytes --]