MaaXBoard Hardware Design - Recent Threads

MaaxBoard-RT MIPI-DSI connector pinout

sposelenov — Sat, 31 Jan 2026 11:20:28 GMT

Hello,

Could please someone from Avnet confirm that the DSI connector pinout on the MaaxBoard-RT is the same as published here https://community.element14.com/products/devtools/avnetboardscommunity/avnetboard-forums/f/maaxboard-hardware-design/40085/differences-of-raspberry-and-maaxboard-mipi-dsi-port?ReplySortBy=CreatedDate&ReplySortOrder=Ascending ?

We are working on a Linux port to MaaxBoard-RT, currently trying to bring up RPI 7" DSI LCD.

Regards,

Sergei

Order code of J13 (CAN-FD connector)

EVVA — Wed, 14 Jan 2026 08:49:56 GMT

Hi!
I would need the order code for the CAN-FD connector on the MaaXBoard OSM93.

Does anyone have this information?

Many thanks in advance!

Regards, Gerhard

MaaXBoard-RT Bluetooth UART interface

dkon — Thu, 25 Dec 2025 17:00:43 GMT

Hello everyone,

The Hardware User Guide states that the BT interface of 1ZM is connected to LPUART10. LPUART10 uses pads AD_34 and AD_35 for CTS/RTS which are actually occupied by WiFi SDIO. So, this looks like an error in the document.

Which pads and UART interface are actually used for the BT? Is there any demo application for the board that supports BT?

Regards, Dmitry

MaaXBoart RT schematics

dkon — Mon, 24 Nov 2025 03:15:27 GMT

Hello everyone,

Where can I obtain the schematics for the MaaXBoard RT board? It doesn't seem available on the product page.

Regards, Dmitry

Does maaxboard have yocto support? Which branch is currently maintained?

moose_rivieh — Fri, 21 Nov 2025 06:06:00 GMT

Meta-maaxboard documentation lists the following branches as supported for the various maaxboard models

A meta-layer for MaaXBoard series boards

Yocto scarthgap(5.0) support : MaaXBoard-8ULP
Yocto nanbield(4.2) support : MaaXBoard-Osm93
Yocto Mickledore(4.2) support : MaaXBoard-8ULP
Yocto Langdale(4.1) support : MaaXBoard/MaaXBoard-Mini/MaaXBoard-Nano/MaaXBoard-8ULP
Yocto Kirkstone(4.0) support : MaaXBoard/MaaXBoard-Mini/MaaXBoard-Nano/MaaXBoard-8ULP

I have the maaxboard (AES-MC-SBC-IMX8M-G) and I was able to build both avnet-image-lite and avnet-image-full using Langdale branch with no issues. However, neither images boot and got the below kernel panic. Isn't this the correct branch? Is this board maintained or obsolete? I would expect these images to load out of the box. Below is the kernel log for both boots.

U-Boot SPL 2022.04-lf_v2022.04+g0dd7e59924d (Sep 26 2023 - 07:43:51 +0000)
power_bd71837_init
set buck8 to 1.2v for DDR4
DDRINFO: start DRAM init
DDRINFO: DRAM rate 2400MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
Normal Boot
Trying to boot from MMC1

U-Boot 2022.04-lf_v2022.04+g0dd7e59924d (Sep 26 2023 - 07:43:51 +0000)

CPU: i.MX8MQ rev2.1 1500 MHz (running at 1000 MHz)
CPU: Commercial temperature grade (0C to 95C) at 39C
Reset cause: POR
Model: Avnet MaaXBoard
DRAM: 2 GiB
Core: 56 devices, 18 uclasses, devicetree: separate
MMC: FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial

BuildInfo:
- ATF fccc380

switch to partitions #0, OK
mmc0 is current device
flash target is MMC:0
Net:
Warning: ethernet@30be0000 (eth0) using random MAC address - f2:82:a4:34:51:79
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
858 bytes read in 1 ms (837.9 KiB/s)
32512512 bytes read in 1355 ms (22.9 MiB/s)
52629 bytes read in 4 ms (12.5 MiB/s)
Applying DT overlay => ext-gpio.dtbo
575 bytes read in 2 ms (280.3 KiB/s)
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
Using Device Tree in place at 0000000043000000, end 000000004301ffff
Remove /soc@0/bus@30800000/ethernet@30be0000:phy-reset-gpios

Starting kernel ...

U-Boot 2022.04-lf_v2022.04+g0dd7e59924d (Sep 26 2023 - 07:43:51 +0000)

CPU: i.MX8MQ rev2.1 1500 MHz (running at 1000 MHz)
CPU: Commercial temperature grade (0C to 95C) at 35C
Reset cause: POR
Model: Avnet MaaXBoard
DRAM: 2 GiB
Core: 56 devices, 18 uclasses, devicetree: separate
MMC: FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial

BuildInfo:
- ATF fccc380

switch to partitions #0, OK
mmc0 is current device
flash target is MMC:0
Net:
Warning: ethernet@30be0000 (eth0) using random MAC address - f2:44:f9:95:62:be
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
858 bytes read in 1 ms (837.9 KiB/s)
32512512 bytes read in 1355 ms (22.9 MiB/s)
52629 bytes read in 4 ms (12.5 MiB/s)
Applying DT overlay => ext-gpio.dtbo
575 bytes read in 2 ms (280.3 KiB/s)
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
Using Device Tree in place at 0000000043000000, end 000000004301ffff
Remove /soc@0/bus@30800000/ethernet@30be0000:phy-reset-gpios

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 6.1.1+gd59104ae45c4 (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0.20220819) #1 SMP PREEMPT Thu Sep 7 06:56:02 UTC 2023
[ 0.000000] Machine model: Avnet MaaXBoard
[ 0.000000] efi: UEFI not found.
[ 0.000000] Reserved memory: created CMA memory pool at 0x0000000044000000, size 960 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-0x00000000bfffffff]
[ 0.000000] NUMA: NODE_DATA [mem 0xbfbc1700-0xbfbc3fff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000040000000-0x00000000bfffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040000000-0x00000000bfffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bfffffff]
[ 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: MIGRATE_INFO_TYPE not supported.
[ 0.000000] psci: SMC Calling Convention v1.2
[ 0.000000] percpu: Embedded 20 pages/cpu s44520 r8192 d29208 u81920
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: GIC system register CPU interface
[ 0.000000] CPU features: detected: ARM erratum 845719
[ 0.000000] alternatives: applying boot alternatives
[ 0.000000] Fallback order for Node 0: 0
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 516096
[ 0.000000] Policy zone: DMA
[ 0.000000] Kernel command line: console=ttymxc0,115200 console=tty1 root=/dev/mmcblk0p2 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:all(zero), heap alloc:off, heap free:off
[ 0.000000] Memory: 1041108K/2097152K available (19904K kernel code, 1606K rwdata, 6788K rodata, 3328K init, 645K bss, 73004K reserved, 983040K 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 event tracing is enabled.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[ 0.000000] Trampoline variant of Tasks RCU enabled.
[ 0.000000] Tracing variant of 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] Root IRQ handler: gic_handle_irq
[ 0.000000] GICv3: GICv3 features: 16 PPIs
[ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000
[ 0.000000] ITS: No ITS available, not enabling LPIs
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000] arch_timer: cp15 timer(s) running at 8.33MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1ec0311ec, max_idle_ns: 440795202152 ns
[ 0.000000] sched_clock: 56 bits at 8MHz, resolution 120ns, wraps every 2199023255541ns
[ 0.000460] Console: colour dummy device 80x25
[ 0.000931] printk: console [tty1] enabled
[ 0.001010] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.66 BogoMIPS (lpj=33333)
[ 0.001037] pid_max: default: 32768 minimum: 301
[ 0.001112] LSM: Security Framework initializing
[ 0.001219] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.001248] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.002820] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.002843] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.002933] cblist_init_generic: Setting shift to 2 and lim to 1.
[ 0.003122] rcu: Hierarchical SRCU implementation.
[ 0.003136] rcu: Max phase no-delay instances is 1000.
[ 0.004272] EFI services will not be available.
[ 0.004502] smp: Bringing up secondary CPUs ...
[ 0.004986] Detected VIPT I-cache on CPU1
[ 0.005069] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000
[ 0.005110] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.005628] Detected VIPT I-cache on CPU2
[ 0.005702] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000
[ 0.005725] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[ 0.006190] Detected VIPT I-cache on CPU3
[ 0.006264] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000
[ 0.006287] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[ 0.006349] smp: Brought up 1 node, 4 CPUs
[ 0.006439] SMP: Total of 4 processors activated.
[ 0.006453] CPU features: detected: 32-bit EL0 Support
[ 0.006464] CPU features: detected: 32-bit EL1 Support
[ 0.006477] CPU features: detected: CRC32 instructions
[ 0.006556] CPU: All CPU(s) started at EL2
[ 0.006585] alternatives: applying system-wide alternatives
[ 0.008640] devtmpfs: initialized
[ 0.016224] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.016288] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[ 0.046124] pinctrl core: initialized pinctrl subsystem
[ 0.048244] DMI not present or invalid.
[ 0.048943] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.050154] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[ 0.050416] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.050584] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.050680] audit: initializing netlink subsys (disabled)
[ 0.050842] audit: type=2000 audit(0.048:1): state=initialized audit_enabled=0 res=1
[ 0.051387] thermal_sys: Registered thermal governor 'step_wise'
[ 0.051392] thermal_sys: Registered thermal governor 'power_allocator'
[ 0.051437] cpuidle: using governor menu
[ 0.051634] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.051727] ASID allocator initialised with 65536 entries
[ 0.052667] Serial: AMBA PL011 UART driver
[ 0.052744] imx mu driver is registered.
[ 0.052772] imx rpmsg driver is registered.
[ 0.059690] imx8mq-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver
[ 0.069699] KASLR disabled due to lack of seed
[ 0.090409] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages
[ 0.090431] HugeTLB: 16380 KiB vmemmap can be freed for a 1.00 GiB page
[ 0.090447] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages
[ 0.090461] HugeTLB: 508 KiB vmemmap can be freed for a 32.0 MiB page
[ 0.090476] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
[ 0.090491] HugeTLB: 28 KiB vmemmap can be freed for a 2.00 MiB page
[ 0.090505] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages
[ 0.090519] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page
[ 0.092320] ACPI: Interpreter disabled.
[ 0.092886] iommu: Default domain type: Translated
[ 0.092901] iommu: DMA domain TLB invalidation policy: strict mode
[ 0.093254] SCSI subsystem initialized
[ 0.093631] usbcore: registered new interface driver usbfs
[ 0.093681] usbcore: registered new interface driver hub
[ 0.093718] usbcore: registered new device driver usb
[ 0.094566] mc: Linux media interface: v0.10
[ 0.094610] videodev: Linux video capture interface: v2.00
[ 0.094681] pps_core: LinuxPPS API ver. 1 registered
[ 0.094695] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.094722] PTP clock support registered
[ 0.094856] EDAC MC: Ver: 3.0.0
[ 0.095781] FPGA manager framework
[ 0.095875] Advanced Linux Sound Architecture Driver Initialized.
[ 0.096481] Bluetooth: Core ver 2.22
[ 0.096521] NET: Registered PF_BLUETOOTH protocol family
[ 0.096534] Bluetooth: HCI device and connection manager initialized
[ 0.096552] Bluetooth: HCI socket layer initialized
[ 0.096567] Bluetooth: L2CAP socket layer initialized
[ 0.096592] Bluetooth: SCO socket layer initialized
[ 0.096908] vgaarb: loaded
[ 0.097376] clocksource: Switched to clocksource arch_sys_counter
[ 0.097571] VFS: Disk quotas dquot_6.6.0
[ 0.097620] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.097805] pnp: PnP ACPI: disabled
[ 0.105179] NET: Registered PF_INET protocol family
[ 0.105387] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.107217] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[ 0.107259] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.107286] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 0.107432] TCP bind hash table entries: 16384 (order: 7, 524288 bytes, linear)
[ 0.107919] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.108025] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[ 0.108091] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[ 0.108247] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.108574] RPC: Registered named UNIX socket transport module.
[ 0.108590] RPC: Registered udp transport module.
[ 0.108602] RPC: Registered tcp transport module.
[ 0.108613] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.109491] PCI: CLS 0 bytes, default 64
[ 0.110162] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[ 0.110787] kvm [1]: IPA Size Limit: 40 bits
[ 0.112347] kvm [1]: vgic-v2@31020000
[ 0.112371] kvm [1]: GIC system register CPU interface enabled
[ 0.112469] kvm [1]: vgic interrupt IRQ9
[ 0.112573] kvm [1]: Hyp mode initialized successfully
[ 0.113761] Initialise system trusted keyrings
[ 0.113927] workingset: timestamp_bits=42 max_order=19 bucket_order=0
[ 0.121048] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.121815] NFS: Registering the id_resolver key type
[ 0.121858] Key type id_resolver registered
[ 0.121871] Key type id_legacy registered
[ 0.121962] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.121979] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 0.122013] ntfs: driver 2.1.32 [Flags: R/W].
[ 0.122173] ntfs3: Max link count 4000
[ 0.122186] ntfs3: Enabled Linux POSIX ACLs support
[ 0.122196] ntfs3: Read-only LZX/Xpress compression included
[ 0.122297] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.122654] 9p: Installing v9fs 9p2000 file system support
[ 0.166181] Key type asymmetric registered
[ 0.166196] Asymmetric key parser 'x509' registered
[ 0.166254] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[ 0.166274] io scheduler mq-deadline registered
[ 0.166287] io scheduler kyber registered
[ 0.171470] EINJ: ACPI disabled.
[ 0.179210] imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2
[ 0.179244] imx-sdma 302c0000.dma-controller: Falling back to sysfs fallback for: imx/sdma/sdma-imx7d.bin
[ 0.182650] mxs-dma 33000000.dma-apbh: initialized
[ 0.186945] SoC: i.MX8MQ revision 2.1
[ 0.187053] Config NOC for VPU and CPU
[ 0.187645] Bus freq driver module loaded
[ 0.193045] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.195181] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 18, base_baud = 1562500) is a IMX
[ 1.275020] printk: console [ttymxc0] enabled
[ 1.280011] 30a60000.serial: ttymxc3 at MMIO 0x30a60000 (irq = 19, base_baud = 5000000) is a IMX
[ 1.300890] loop: module loaded
[ 1.305062] of_reserved_mem_lookup() returned NULL
[ 1.310053] megasas: 07.719.03.00-rc1
[ 1.314981] imx ahci driver is registered.
[ 1.323866] tun: Universal TUN/TAP device driver, 1.6
[ 1.329645] thunder_xcv, ver 1.0
[ 1.332916] thunder_bgx, ver 1.0
[ 1.336198] nicpf, ver 1.0
[ 1.340598] hns3: Hisilicon Ethernet Network Driver for Hip08 Family - version
[ 1.347841] hns3: Copyright (c) 2017 Huawei Corporation.
[ 1.353215] hclge is initializing
[ 1.356554] e1000: Intel(R) PRO/1000 Network Driver
[ 1.361446] e1000: Copyright (c) 1999-2006 Intel Corporation.
[ 1.367245] e1000e: Intel(R) PRO/1000 Network Driver
[ 1.372224] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.378207] igb: Intel(R) Gigabit Ethernet Network Driver
[ 1.383626] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 1.389244] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[ 1.395527] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[ 1.401597] sky2: driver version 1.30
[ 1.405765] usbcore: registered new interface driver r8152
[ 1.411526] VFIO - User Level meta-driver version: 0.3
[ 1.419363] usbcore: registered new interface driver uas
[ 1.424739] usbcore: registered new interface driver usb-storage
[ 1.430829] usbcore: registered new interface driver usbserial_generic
[ 1.437393] usbserial: USB Serial support registered for generic
[ 1.443451] usbcore: registered new interface driver ftdi_sio
[ 1.449233] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 1.456591] usbcore: registered new interface driver usb_serial_simple
[ 1.463153] usbserial: USB Serial support registered for carelink
[ 1.469280] usbserial: USB Serial support registered for zio
[ 1.474977] usbserial: USB Serial support registered for funsoft
[ 1.481017] usbserial: USB Serial support registered for flashloader
[ 1.487409] usbserial: USB Serial support registered for google
[ 1.493373] usbserial: USB Serial support registered for libtransistor
[ 1.499934] usbserial: USB Serial support registered for vivopay
[ 1.505973] usbserial: USB Serial support registered for moto_modem
[ 1.512273] usbserial: USB Serial support registered for motorola_tetra
[ 1.518920] usbserial: USB Serial support registered for nokia
[ 1.524788] usbserial: USB Serial support registered for novatel_gps
[ 1.531175] usbserial: USB Serial support registered for hp4x
[ 1.536953] usbserial: USB Serial support registered for suunto
[ 1.542910] usbserial: USB Serial support registered for siemens_mpi
[ 1.549310] usbcore: registered new interface driver usb_ehset_test
[ 1.557954] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
[ 1.572323] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc0
[ 1.578546] snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01T00:00:00 UTC (0)
[ 1.587709] i2c_dev: i2c /dev entries driver
[ 1.596143] Bluetooth: HCI UART driver ver 2.3
[ 1.600617] Bluetooth: HCI UART protocol H4 registered
[ 1.605775] Bluetooth: HCI UART protocol BCSP registered
[ 1.611123] Bluetooth: HCI UART protocol LL registered
[ 1.616279] Bluetooth: HCI UART protocol ATH3K registered
[ 1.621713] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 1.628082] Bluetooth: HCI UART protocol Broadcom registered
[ 1.633778] Bluetooth: HCI UART protocol QCA registered
[ 1.640428] sdhci: Secure Digital Host Controller Interface driver
[ 1.646636] sdhci: Copyright(c) Pierre Ossman
[ 1.651575] Synopsys Designware Multimedia Card Interface Driver
[ 1.658121] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.667022] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.673826] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[ 1.680845] usbcore: registered new interface driver usbhid
[ 1.686437] usbhid: USB HID core driver
[ 1.694344] cs_system_cfg: CoreSight Configuration manager initialised
[ 1.698266] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA
[ 1.706131] NET: Registered PF_LLC protocol family
[ 1.714119] NET: Registered PF_INET6 protocol family
[ 1.722234] Segment Routing with IPv6
[ 1.725966] In-situ OAM (IOAM) with IPv6
[ 1.729963] NET: Registered PF_PACKET protocol family
[ 1.735061] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 1.749688] Bluetooth: RFCOMM TTY layer initialized
[ 1.754620] Bluetooth: RFCOMM socket layer initialized
[ 1.759809] Bluetooth: RFCOMM ver 1.11
[ 1.763602] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 1.768949] Bluetooth: BNEP filters: protocol multicast
[ 1.774222] Bluetooth: BNEP socket layer initialized
[ 1.779219] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.785180] Bluetooth: HIDP socket layer initialized
[ 1.791845] 8021q: 802.1Q VLAN Support v1.8
[ 1.796062] mmc0: host does not support reading read-only switch, assuming write-enable
[ 1.797099] lib80211: common routines for IEEE802.11 drivers
[ 1.809232] mmc0: new high speed SDXC card at address 0001
[ 1.811624] mmcblk0: mmc0:0001 SD 58.2 GiB
[ 1.819564] 9pnet: Installing 9P2000 support
[ 1.819994] mmcblk0: p1 p2
[ 1.823968] Key type dns_resolver registered
[ 1.832071] registered taskstats version 1
[ 1.836209] Loading compiled-in X.509 certificates
[ 1.875663] regulator-usb1-vcc GPIO handle specifies active low - ignored
[ 2.224230] ldo5: Bringing 1800000uV into 2500000-2500000uV
[ 2.261583] i2c i2c-0: IMX I2C adapter registered
[ 2.267047] imx8mq-usb-phy 381f0040.usb-phy: supply vbus not found, using dummy regulator
[ 2.275660] imx8mq-usb-phy 382f0040.usb-phy: supply vbus not found, using dummy regulator
[ 2.287855] pps pps0: new PPS source ptp0
[ 2.298404] fec 30be0000.ethernet eth0: registered PHC device 0
[ 2.305830] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller
[ 2.311356] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 1
[ 2.319131] xhci-hcd xhci-hcd.4.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000000001010010
[ 2.328585] xhci-hcd xhci-hcd.4.auto: irq 203, io mem 0x38100000
[ 2.334776] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller
[ 2.340288] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 2
[ 2.347970] xhci-hcd xhci-hcd.4.auto: Host supports USB 3.0 SuperSpeed
[ 2.355606] hub 1-0:1.0: USB hub found
[ 2.359403] hub 1-0:1.0: 1 port detected
[ 2.363663] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.372751] hub 2-0:1.0: USB hub found
[ 2.376545] hub 2-0:1.0: 1 port detected
[ 2.382069] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[ 2.387603] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 3
[ 2.395374] xhci-hcd xhci-hcd.5.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000000001010010
[ 2.404832] xhci-hcd xhci-hcd.5.auto: irq 204, io mem 0x38200000
[ 2.410998] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller
[ 2.416511] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 4
[ 2.424197] xhci-hcd xhci-hcd.5.auto: Host supports USB 3.0 SuperSpeed
[ 2.431760] hub 3-0:1.0: USB hub found
[ 2.435558] hub 3-0:1.0: 1 port detected
[ 2.439793] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.448884] hub 4-0:1.0: USB hub found
[ 2.452677] hub 4-0:1.0: 1 port detected
[ 2.457168] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 3 mkt segment 0 supported-hw 0x8 0x1
[ 2.469642] sdhci-esdhc-imx 30b50000.mmc: allocated mmc-pwrseq
[ 2.469770] galcore: clk_get 2d core clock failed, disable 2d/vg!
[ 2.481974] Galcore version 6.4.11.p1.608260
[ 2.511272] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
[ 2.559837] [drm] Initialized vivante 1.0.0 20170808 for 38000000.gpu3d on minor 0
[ 2.568717] mxc_hantro 38300000.vpu: supply vpu not found, using dummy regulator
[ 2.576229] failed to set hantro voltage: 1000 mV
[ 2.581245] hantrodec: module inserted. Major = 510
[ 2.587873] input: gpio_keys as /devices/platform/gpio_keys/input/input1
[ 2.597965] input: bd718xx-pwrkey as /devices/platform/soc@0/30800000.bus/30a20000.i2c/i2c-0/0-004b/gpio-keys.1.auto/input/input2
[ 2.610577] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 2.622669] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 2.623279] mmc1: new high speed SDIO card at address 0001
[ 2.629308] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 2.634516] ALSA device list:
[ 2.634522] No soundcards found.
[ 2.649745] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[ 2.675997] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
[ 2.684648] VFS: Mounted root (ext4 filesystem) on device 179:2.
[ 2.691768] devtmpfs: mounted
[ 2.695543] Freeing unused kernel memory: 3328K
[ 2.700165] Run /sbin/init as init process
[ 3.130652] systemd[1]: System time before build time, advancing clock.
[ 3.223674] systemd[1]: systemd 251.8+ running in system mode (+PAM -AUDIT -SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN )
[ 3.255489] systemd[1]: Detected architecture arm64.
[ 3.329313] systemd[1]: Hostname set to <maaxboard>.
[ 3.351398] systemd[1]: Initializing machine ID from random generator.
[ 3.509499] systemd-sysv-generator[174]: SysV service '/etc/init.d/sshd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package t.
[ 3.952264] systemd[1]: Queued start job for default target Multi-User System.
[ 4.010685] systemd[1]: Created slice Slice /system/getty.
[ 4.017953] systemd[1]: Created slice Slice /system/modprobe.
[ 4.025202] systemd[1]: Created slice Slice /system/serial-getty.
[ 4.032423] systemd[1]: Created slice User and Session Slice.
[ 4.038483] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 4.046686] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 4.054603] systemd[1]: Reached target Path Units.
[ 4.059550] systemd[1]: Reached target Remote File Systems.
[ 4.065306] systemd[1]: Reached target Slice Units.
[ 4.070362] systemd[1]: Reached target Swaps.
[ 4.111473] systemd[1]: Listening on RPCbind Server Activation Socket.
[ 4.118492] systemd[1]: Reached target RPC Port Mapper.
[ 4.124325] systemd[1]: Listening on Syslog Socket.
[ 4.129555] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 4.136674] systemd[1]: Listening on Journal Audit Socket.
[ 4.142543] systemd[1]: Listening on Journal Socket (/dev/log).
[ 4.148906] systemd[1]: Listening on Journal Socket.
[ 4.154438] systemd[1]: Listening on Network Service Netlink Socket.
[ 4.161310] systemd[1]: Listening on udev Control Socket.
[ 4.167074] systemd[1]: Listening on udev Kernel Socket.
[ 4.172763] systemd[1]: Listening on User Database Manager Socket.
[ 4.209764] systemd[1]: Mounting Huge Pages File System...
[ 4.219426] systemd[1]: Mounting POSIX Message Queue File System...
[ 4.225838] Unable to handle kernel paging request at virtual address ffff8000422244f8
[ 4.233786] Mem abort info:
[ 4.233789] ESR = 0x0000000096000005
[ 4.233792] EC = 0x25: DABT (current EL), IL = 32 bits
[ 4.233797] SET = 0, FnV = 0
[ 4.233799] EA = 0, S1PTW = 0
[ 4.233801] FSC = 0x05: level 1 translation fault
[ 4.233804] Data abort info:
[ 4.233805] ISV = 0, ISS = 0x00000005
[ 4.233807] CM = 0, WnR = 0
[ 4.233810] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000041e2c000
[ 4.233814] [ffff8000422244f8] pgd=10000000bffff003, p4d=10000000bffff003, pud=0000000000000000
[ 4.233824] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP
[ 4.233829] Modules linked in:
[ 4.233834] CPU: 3 PID: 180 Comm: mount Not tainted 6.1.1+gd59104ae45c4 #1
[ 4.233840] Hardware name: Avnet MaaXBoard (DT)
[ 4.233844] pstate: 800000c5 (Nzcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 4.233850] pc : __find_get_block+0x74/0x3fc
[ 4.233865] lr : __getblk_gfp+0x2c/0x3c4
[ 4.233872] sp : ffff80000ac7b7b0
[ 4.233874] x29: ffff80000ac7b7b0 x28: ffff00004191bb00 x27: ffff0000414e8800
[ 4.233883] x26: 0000000000000000 x25: 0000000000000000 x24: ffff00004210be80
[ 4.233890] x23: 0000000000000008 x22: ffff800009b31648 x21: 0000000000001000
[ 4.233898] x20: 000000000000c926 x19: ffff8000422244e0 x18: 0000000000000000
[ 4.233905] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[ 4.233913] x14: 0000000000000000 x13: ffff000040829026 x12: ffff80000ac7bbe4
[ 4.233921] x11: 0000000f643add5b x10: 0000000000000002 x9 : 0000000000000004
[ 4.233928] x8 : 0000000000001000 x7 : ffff80000ac7b7b0 x6 : ffff80007606e000
[ 4.233936] x5 : 000000000000001e x4 : ffff800009b316c0 x3 : 000000000000000f
[ 4.378206] x2 : ffff800009b316c0 x1 : 0000000000000000 x0 : 0000000000000060
[ 4.378216] Call trace:
[ 4.378218] __find_get_block+0x74/0x3fc
[ 4.378227] __getblk_gfp+0x2c/0x3c4
[ 4.378236] ext4_getblk+0xa4/0x310
[ 4.378244] ext4_bread_batch+0x64/0x1d4
[ 4.378251] __ext4_find_entry+0x15c/0x420
[ 4.378257] ext4_lookup+0xa0/0x250
[ 4.378263] __lookup_slow+0x88/0x150
[ 4.378270] walk_component+0xd8/0x190
[ 4.378275] path_lookupat+0x78/0x1a0
[ 4.378281] filename_lookup+0xac/0x1a4
[ 4.378288] vfs_statx+0x8c/0x19c
[ 4.378295] vfs_fstatat+0x60/0x90
[ 4.378301] __do_sys_newfstatat+0x58/0xa0
[ 4.378308] __arm64_sys_newfstatat+0x20/0x30
[ 4.378316] invoke_syscall+0x48/0x114
[ 4.378325] el0_svc_common.constprop.0+0x44/0xec
[ 4.378332] do_el0_svc+0x2c/0xd0
[ 4.378339] el0_svc+0x2c/0x84
[ 4.378349] el0t_64_sync_handler+0xf4/0x120
[ 4.378354] el0t_64_sync+0x18c/0x190
[ 4.378364] Code: aa0403e2 d538d086 f8666853 b4ffff33 (f9400e62)
[ 4.378368] ---[ end trace 0000000000000000 ]---
[ 4.498277] systemd[1]: Mounting Kernel Debug File System...
[ 4.504837] systemd[1]: Kernel Trace File System was skipped because of a failed condition check (ConditionPathExists=/sys/kernel/tracing).
[ 4.527410] systemd[1]: Mounting Temporary Directory /tmp...
[ 4.536903] systemd[1]: Starting Create List of Static Device Nodes...
[ 4.546934] systemd[1]: Starting Load Kernel Module configfs...
[ 4.556353] systemd[1]: Starting Load Kernel Module drm...
[ 4.565332] systemd[1]: Starting Load Kernel Module fuse...
[ 4.580006] systemd[1]: Starting RPC Bind...
[ 4.584720] systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathIsReadWrite=!/).
[ 4.597334] fuse: init (API version 7.37)
[ 4.603063] systemd[1]: Starting Journal Service...
[ 4.618112] systemd[1]: Starting Load Kernel Modules...
[ 4.626905] systemd[1]: Starting Generate network units from Kernel command line...
[ 4.638534] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 4.649026] systemd[1]: Starting Coldplug All udev Devices...
[ 4.660852] systemd[1]: dev-hugepages.mount: Mount process exited, code=killed, status=11/SEGV
[ 4.669609] systemd[1]: dev-hugepages.mount: Failed with result 'signal'.
[ 4.670084] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.
[ 4.677407] systemd[1]: Failed to mount Huge Pages File System.
[ 4.690813] systemd[1]: Started RPC Bind.
[ 4.695572] systemd[1]: Mounted POSIX Message Queue File System.
[ 4.701956] systemd[1]: Mounted Kernel Debug File System.
[ 4.707928] systemd[1]: Mounted Temporary Directory /tmp.
[ 4.714625] systemd[1]: Finished Create List of Static Device Nodes.
[ 4.722056] systemd[1]: modprobe@configfs.service: Deactivated successfully.
[ 4.729859] systemd[1]: Finished Load Kernel Module configfs.
[ 4.730654] mlan: loading out-of-tree module taints kernel.
[ 4.742432] systemd[1]: modprobe@drm.service: Deactivated successfully.
[ 4.750070] systemd[1]: Finished Load Kernel Module drm.
[ 4.756624] systemd[1]: modprobe@fuse.service: Deactivated successfully.
[ 4.764373] systemd[1]: Finished Load Kernel Module fuse.
[ 4.770559] systemd[1]: Started Journal Service.
[ 4.852755] wlan: Loading MWLAN driver
[ 4.858676] wlan: Register to Bus Driver...
[ 4.863431] wlan: Register to Bus Driver Done
[ 4.868354] systemd-journald[189]: Received client request to flush runtime journal.
[ 4.871599] wlan: Driver loaded successfully
[ 4.906853] Unable to handle kernel paging request at virtual address 000000000008b6c0
[ 4.914827] Mem abort info:
[ 4.917646] ESR = 0x0000000096000004
[ 4.921412] EC = 0x25: DABT (current EL), IL = 32 bits
[ 4.926739] SET = 0, FnV = 0
[ 4.929804] EA = 0, S1PTW = 0
[ 4.932947] FSC = 0x04: level 0 translation fault
[ 4.937839] Data abort info:
[ 4.940721] ISV = 0, ISS = 0x00000004
[ 4.944568] CM = 0, WnR = 0
[ 4.947549] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000081ce1000
[ 4.954005] [000000000008b6c0] pgd=0000000000000000, p4d=0000000000000000
[ 4.960816] Internal error: Oops: 0000000096000004 [#2] PREEMPT SMP
[ 4.967089] Modules linked in: moal(O) mlan(O) fuse
[ 4.971984] CPU: 2 PID: 207 Comm: (d-sysctl) Tainted: G D O 6.1.1+gd59104ae45c4 #1
[ 4.980778] Hardware name: Avnet MaaXBoard (DT)
[ 4.985311] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 4.992280] pc : elv_attempt_insert_merge+0xcc/0x10c
[ 4.997260] lr : elv_attempt_insert_merge+0xb0/0x10c
[ 5.002232] sp : ffff80000ac5b5e0
[ 5.005548] x29: ffff80000ac5b5e0 x28: 0000000000080700 x27: ffff000040e13488
[ 5.012697] x26: ffff0000407b8e00 x25: ffff000040e13440 x24: ffff000040dd0000
[ 5.019843] x23: 0000000000000000 x22: ffff8000093e4bb8 x21: ffff000040949800
[ 5.026990] x20: ffff80000ac5b758 x19: ffff80000ac5b6b8 x18: ffff000040dd01a0
[ 5.034136] x17: 0000000091722d65 x16: 00000000000004c7 x15: 0000000000000000
[ 5.041281] x14: 0000000000067544 x13: 0000000000000000 x12: 00000000ffff8004
[ 5.048427] x11: 0000000000000011 x10: fffffc000009c740 x9 : 0000000000000004
[ 5.055573] x8 : 0000000000000004 x7 : 000000000005b630 x6 : 0000000000000000
[ 5.062719] x5 : 0000000000403000 x4 : 0000000000000000 x3 : 000000000004001a
[ 5.069864] x2 : ffff000040e13440 x1 : 000000000008b630 x0 : 0000000000000000
[ 5.077011] Call trace:
[ 5.079460] elv_attempt_insert_merge+0xcc/0x10c
[ 5.084089] blk_mq_sched_try_insert_merge+0x44/0x74
[ 5.089061] dd_insert_requests+0x84/0x2a0
[ 5.093164] blk_mq_sched_insert_requests+0xa4/0x264
[ 5.098133] blk_mq_flush_plug_list+0xd0/0x23c
[ 5.102585] __blk_flush_plug+0xf0/0x140
[ 5.106515] blk_finish_plug+0x38/0xf0
[ 5.110271] read_pages+0x170/0x2f4
[ 5.113766] page_cache_ra_unbounded+0x158/0x1dc
[ 5.118388] page_cache_ra_order+0x90/0x340
[ 5.122576] ondemand_readahead+0x174/0x2e4
[ 5.126763] page_cache_sync_ra+0x94/0xac
[ 5.130777] filemap_get_pages+0xb0/0x6a0
[ 5.134793] filemap_read+0xc0/0x344
[ 5.138374] generic_file_read_iter+0x100/0x18c
[ 5.142911] ext4_file_read_iter+0x50/0x180
[ 5.147100] __kernel_read+0xcc/0x244
[ 5.150767] kernel_read+0x68/0xb0
[ 5.154173] bprm_execve+0x1bc/0x59c
[ 5.157756] do_execveat_common.isra.0+0x198/0x240
[ 5.162554] __arm64_sys_execve+0x40/0x54
[ 5.166571] invoke_syscall+0x48/0x114
[ 5.170328] el0_svc_common.constprop.0+0xcc/0xec
[ 5.175039] do_el0_svc+0x2c/0xd0
[ 5.178360] el0_svc+0x2c/0x84
[ 5.181423] el0t_64_sync_handler+0xf4/0x120
[ 5.185701] el0t_64_sync+0x18c/0x190
[ 5.189373] Code: b5fffdf4 a94153f3 2a1703e0 a9425bf5 (f9401bf7)
[ 5.195473] ---[ end trace 0000000000000000 ]---
[ 5.200147] note: (d-sysctl)[207] exited with preempt_count 1
[ 5.206469] ------------[ cut here ]------------
[ 5.211100] WARNING: CPU: 3 PID: 207 at kernel/exit.c:765 do_exit+0x794/0x8fc
[ 5.218253] Modules linked in: moal(O) mlan(O) fuse
[ 5.223150] CPU: 3 PID: 207 Comm: (d-sysctl) Tainted: G D O 6.1.1+gd59104ae45c4 #1
[ 5.231947] Hardware name: Avnet MaaXBoard (DT)
[ 5.236481] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 5.243450] pc : do_exit+0x794/0x8fc
[ 5.247035] lr : do_exit+0x5c/0x8fc
[ 5.250528] sp : ffff80000ac5b1d0
[ 5.253845] x29: ffff80000ac5b1d0 x28: ffff8000097ef1b0 x27: ffff8000097ef1b8
[ 5.260992] x26: 0000000000000001 x25: ffff80000ac5b312 x24: 0000000000000000
[ 5.268140] x23: 0000000000000000 x22: 000000000000000b x21: ffff000041502100
[ 5.275285] x20: ffff0000407c1200 x19: ffff0000410b8ec0 x18: 0000000000000000
[ 5.282431] x17: 000000040044ffff x16: 00500072b5503510 x15: 0000000000000000
[ 5.289577] x14: ffff000040140ec0 x13: ffff80007606e000 x12: 0000000034d4d91d
[ 5.296723] x11: 0000000000000001 x10: 0000000000000a40 x9 : ffff80000ac5b120
[ 5.303870] x8 : ffff0000410b9960 x7 : ffff0000413fe200 x6 : 000000000016e360
[ 5.311016] x5 : 00000000410fd030 x4 : 0000000000f0000f x3 : ffff00004110d6c8
[ 5.318161] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff80000ac5b830
[ 5.325307] Call trace:
[ 5.327756] do_exit+0x794/0x8fc
[ 5.330996] make_task_dead+0x5c/0x100
[ 5.334753] die+0x200/0x23c +-----------------------------+
[ 5.337644] die_kernel_fault+0x264/0x364 | |
[ 5.341669] __do_kernel_fault+0xfc/0x18c | Cannot open /dev/ttyUSB1! |
[ 5.345697] do_page_fault+0xa8/0x450 | |
[ 5.349369] do_translation_fault+0x9c/0xb0 +-----------------------------+
[ 5.349376] do_mem_abort+0x44/0x94
[ 5.349383] el1_abort+0x40/0x64
[ 5.349391] el1h_64_sync_handler+0xd8/0xe4
[ 5.349396] el1h_64_sync+0x64/0x68
[ 5.367964] elv_attempt_insert_merge+0xcc/0x10c
[ 5.367973] blk_mq_sched_try_insert_merge+0x44/0x74
[ 5.367979] dd_insert_requests+0x84/0x2a0
[ 5.381651] blk_mq_sched_insert_requests+0xa4/0x264
[ 5.381658] blk_mq_flush_plug_list+0xd0/0x23c
[ 5.381667] __blk_flush_plug+0xf0/0x140
[ 5.381675] blk_finish_plug+0x38/0xf0
[ 5.381683] read_pages+0x170/0x2f4
[ 5.381689] page_cache_ra_unbounded+0x158/0x1dc
[ 5.381695] page_cache_ra_order+0x90/0x340
[ 5.381701] ondemand_readahead+0x174/0x2e4
[ 5.381707] page_cache_sync_ra+0x94/0xac
[ 5.381713] filemap_get_pages+0xb0/0x6a0
[ 5.381721] filemap_read+0xc0/0x344
[ 5.381728] generic_file_read_iter+0x100/0x18c
[ 5.381736] ext4_file_read_iter+0x50/0x180
[ 5.381743] __kernel_read+0xcc/0x244
[ 5.381749] kernel_read+0x68/0xb0
[ 5.381754] bprm_execve+0x1bc/0x59c
[ 5.381762] do_execveat_common.isra.0+0x198/0x240
[ 5.381772] __arm64_sys_execve+0x40/0x54
[ 5.381780] invoke_syscall+0x48/0x114
[ 5.381788] el0_svc_common.constprop.0+0xcc/0xec
[ 5.381795] do_el0_svc+0x2c/0xd0
[ 5.381802] el0_svc+0x2c/0x84
[ 5.381811] el0t_64_sync_handler+0xf4/0x120
[ 5.381815] el0t_64_sync+0x18c/0x190
[ 5.381822] ---[ end trace 0000000000000000 ]---

Need Help with Yocto Full Image on Maaxboard

Scott_S — Fri, 03 Oct 2025 18:55:18 GMT

Hi Everyone!

I recently received my Maaxboard and I would like to flash a full image Yocto on microSD card. I am new to the board and Yocto. By following the user manual for Yocto Lite, (https://www.avnet.com/wcm/connect/121336f0-a62f-487c-aad9-48a72ea1f7fd/MaaXBoard-Linux-Yocto-Lite-UserManual-V1.1-EN.pdf?MOD=AJPERES&CACHEID=ROOTWORKSPACE.Z18_NA5A1I41L0ICD0ABNDMDDG0000-121336f0-a62f-487c-aad9-48a72ea1f7fd-nZCsDkH?MOD=AJPERES&CACHEID=ROOTWORKSPACE.Z18_NA5A1I41L0ICD0ABNDMDDG0000-121336f0-a62f-487c-aad9-48a72ea1f7fd-nZCsDkH),

I am able to install Yocto Lite version on my Maaxboard. However, my project involves in adding an ADC on board, It seems like Yocto Full Image mentioned on the Yocto user manual ( https://www.avnet.com/wcm/connect/3cb1a777-3aa8-4394-9ba8-135d9ffa1470/MaaXBoard-Linux-Yocto-UserManual-V2.1.pdf?MOD=AJPERES&CACHEID=ROOTWORKSPACE.Z18_NA5A1I41L0ICD0ABNDMDDG0000-3cb1a777-3aa8-4394-9ba8-135d9ffa1470-oPqIZjK?MOD=AJPERES&CACHEID=ROOTWORKSPACE.Z18_NA5A1I41L0ICD0ABNDMDDG0000-3cb1a777-3aa8-4394-9ba8-135d9ffa1470-oPqIZjK),

may fit my need better, e.g. overlays support and package management like I2c tools, etc. So I need to flash my microSD card with a Yocto Full version. I could not find it so far.

Can anyone please send me the source about this Yocto Full Image "avnet-image-full-maaxboard-20231215021741.rootfs.wic " which is mentioned on the Yocto user manual on section 4.1.2 ? Thanky

Thank you so much!

How to Interface an Ultrasonic Sensor (HC-SR04) with MaaxBoard OSM93 Using Cortex-M33?

Manju123 — Sat, 02 Aug 2025 09:39:05 GMT

Hello Community,

I am working on a project using the MaaxBoard OSM93 (i.MX93, Cortex-M33 core), and I need help interfacing the HC-SR04 ultrasonic sensor for distance measurement.

I would like to implement this using the Input Capture (IC) feature to accurately measure the ECHO pulse width.

Could you please help with the following points:

Pin Selection & Pinmux Configuration:
- Which GPIO pin or TPM input channel is suitable for the ECHO signal (input capture)?
- How do I configure the pinmux to enable input capture on the chosen pin?
- How should I update pinmux.c and app.h files to reflect the configuration?
Trigger Signal Setup:
- For the TRIG pin (output), what’s the correct GPIO configuration and setup in the pinmux tool?
Driver Usage:
- Is there an available Input Capture driver or example code for i.MX93/Cortex-M33 using MCUXpresso SDK?
Application Code Integration:
- Any guidance or example for writing an ISR or polling logic to calculate distance based on pulse width?

Any working examples, configuration files, or documentation links related to using input capture with HC-SR04 on the OSM93 platform would be very helpful.

Thank you!

How to Interface an Ultrasonic Sensor (HC-SR04) with MaaxBoard OSM93 Using Cortex-M33?

Manju123 — Sat, 02 Aug 2025 09:38:59 GMT

Hello Community,

I am working on a project using the MaaxBoard OSM93 (i.MX93, Cortex-M33 core), and I need help interfacing the HC-SR04 ultrasonic sensor for distance measurement.

I would like to implement this using the Input Capture (IC) feature to accurately measure the ECHO pulse width.

Could you please help with the following points:

Pin Selection & Pinmux Configuration:
- Which GPIO pin or TPM input channel is suitable for the ECHO signal (input capture)?
- How do I configure the pinmux to enable input capture on the chosen pin?
- How should I update pinmux.c and app.h files to reflect the configuration?
Trigger Signal Setup:
- For the TRIG pin (output), what’s the correct GPIO configuration and setup in the pinmux tool?
Driver Usage:
- Is there an available Input Capture driver or example code for i.MX93/Cortex-M33 using MCUXpresso SDK?
Application Code Integration:
- Any guidance or example for writing an ISR or polling logic to calculate distance based on pulse width?

Any working examples, configuration files, or documentation links related to using input capture with HC-SR04 on the OSM93 platform would be very helpful.

Thank you!

I’m using the MaaXBoard 8M Mini to design a wireless IoT system

better — Wed, 30 Jul 2025 02:45:37 GMT

我正在使用 MaaXBoard 8M Mini 设计一个无线物联网系统，集成MAX4002EUA+T作为射频信号检测器，用于处理 2.4GHz 无线信号。我通过 MaaXBoard 的 GPIO 或 SPI 接口控制 MAX4002EUA+T，但在高负载条件下（例如，当 i.MX 8M Mini 处理器运行多线程任务时），MAX4002EUA+T 的输出信号偶尔会变得不稳定（例如，电压漂移或噪声增加）。我该如何优化 MaaXBoard 的硬件设计或软件配置（例如，调整 GPIO/SPI 时序、电源去耦或 PMU 设置）以确保 MAX4002EUA+T 稳定运行？是否有推荐的参考设计或注意事项用于将 MAX4002EUA+T 与 i.MX 8M Mini 集成？

How to use GPIO input capture on MaaxBoard i.MX93 when no timer is mapped?

Manju123 — Fri, 25 Jul 2025 05:02:52 GMT

I am working with the MaaxBoard i.MX93 and trying to read ultrasonic sensor pulse timing using input capture.

I checked the GPIO3_IO04 pin, which works for input reading, but it does not have a timer channel.

My goal is to capture pulse width (in microseconds) similar to using TPM input capture on other pins.

I explored TPM options in the SDK, but those channels are not connected to the GPIO I need.

Question:
Is there any method or workaround to perform input capture on a GPIO that does not have timer functionality?
Can I remap or route another timer to this pin?

Avnet MaaXboard 8ULP Board Control Utilities (BCU) Support

danvs — Mon, 14 Jul 2025 11:38:18 GMT

I am currently using the Avnet MaaXBoard 8ULP and I am attempting to gather CPU power measurements using the NXP BCU tool located on their repository here. However, it seems like the current version of BCU does not support the MaaXBoard 8ULP. I was able to find the BCU repository from Avnet here that seems to support the MaaXBoard 8ULP here. However, it seems like the branch that adds support for the board has not been merged with the master branch of BCU, meaning installing BCU via snap gives the version of BCU which still does not support the MaaXBoard. Is there a way I can use Avnet's branch to allow BCU to support the MaaXBoard in order for me to use it for CPU power measurements?

MaaXBoard OSM93 and location of J15 2 pin connector

WilliamEllis — Thu, 03 Jul 2025 13:49:26 GMT

Hi,

The "MaaXBoard OSM93 Development Kit Hardware User Guide" (version 1.0) describes "RTC External Battery Power" as being connected via (verbatim):

The coin cell holder does NOT come pre-populated on board and will need to be installed by the user. Part number of XXXX (Link?) should be used
A connector with PN / LINK? should be used to interface with J15 2pin connector.

Can anyone advise where the J15 2 pin is? Like, physically, on the board, where is it?! (I can't see it cited anywhere else)

Can anyone advise what the template text "XXXX (Link?)" and "PN / LINK?" is meant to convey? Is there a newer version of this document, perhaps, which has these details?

Bill

MaaXBoard OSM93 M.2 pin mapping

breiwe — Wed, 14 May 2025 15:08:57 GMT

Hello,

after reading documentation and hardware user guides for MaaXBoard OSM93 it is still unclear to me how the pins from M.2 connector (J14) are mapped to the OSM93 module.
Are there anywhere more details than this diagram from the hardware user guide?
Especially information about the GPIOs is completely missing.

I also found out that the Block Diagram (Figure 7 in the Hardware User Guide) shows a differen SDIO interface than the one actually used.

Best regards,

Werner

LPADC Interrupt - Reading Constant 4095

TheSanjanaSuresh — Fri, 09 May 2025 10:27:18 GMT

Hello All,

I am currently trying to implement an LPADC interrupt-driven application on the MAAXBOARD RT. To get started. Specifically, I am attempting to read analog values from the following GPIO pins:

GPIO_AD_13
GPIO_AD_19
GPIO_AD_15

However, when I read the ADC values from these pins, I consistently receive a value of 4095. This occurs across all three pins.

Could you please provide some insight into what might be causing this issue? I suspect there might be a configuration problem or a misunderstanding on my part regarding the hardware or software setup for these specific GPIO pins on the MIMXRT1176DVMAA within the MAAXBOARD RT context.

Any guidance or suggestions on how to troubleshoot this constant reading of 4095 would be greatly appreciated. I am available to provide further details about my setup or the modifications I have made to the example code if needed.

Thank you for your time and assistance.

Regards,

Sanjana S

Inquiry Regarding Hyper Flash Flashing on Avnet MaaxBoard RT with NXP MCUBootUtility

TheSanjanaSuresh — Mon, 05 May 2025 09:45:39 GMT

Hello All,

I am writing to seek assistance with flashing the memory on my Avnet MaaxBoard RT using the NXP-MCUBootUtility-6.4.0. I am encountering an issue specifically while trying to flash the Hyper Flash memory.

The "MaaxBoard RT User Guide V1" indicates a Hyper Flash base address of 0x30000000. However, when I use this address as the base address for the raw binary file in the boot utility, I receive an error ("given base address is then 2000!").

Subsequently, I tried using an offset address of 0x30002000, which allowed the bootable image to be generated. Unfortunately, this resulting image does not function correctly on my board.

Could someone please provide guidance on the correct base address to use with the NXP-MCUBootUtility-6.4.0 for flashing the Hyper Flash memory on the Avnet MaaxBoard RT? Any insights into why the documented base address (0x30000000) is causing an error and why the offset address resulted in a non-functional image would be greatly appreciated.

For future reference, if possible, could you also provide guidance on the correct base address for the SDRAM?

Thank you for your time and assistance. I look forward to your valuable insights.

Best Regards,

Sanjana S

Maaxboard-rt parallel camera

zohargolan — Thu, 01 May 2025 14:54:43 GMT

Hi all,
I need to connect a parallel CSI camera to the Maaxboard-RT and I cannot find schematics or the pinout for the Raspberry-PI connectors. Is there an app note or a project using a parallel camera?
Thank you for your help,
Zohar

MaaXBoard RT CM7 project: Failed to execute MI command

TheSanjanaSuresh — Wed, 16 Apr 2025 10:17:56 GMT

I'm currently working on the MaaXBoard RT. When I try to flash CM7 programs from the demo folder of the SDK examples, I get an error like this: ......... ...
deadbeee: Failed to execute MI command:
-data-disassemble -s 3735928558 -e 3735928602 -- 3
Error message from debugger back end:
Cannot access memory at address 0xdeadbeee
deadbeef: Failed to execute MI command:
-data-disassemble -s 3735928558 -e 3735928611 -- 3
Error message from debugger back end:
Cannot access memory at address 0xdeadbeee
......... ...

after enabling optee in maaxboard, memory size change from 2G to 3G wrongly

gonewtinwind — Mon, 07 Apr 2025 15:09:03 GMT

HI all,

long time no see

sorry to bother you again

I am using maaxboard yocto mickledore version https://github.com/Avnet/meta-maaxboard/tree/mickledore ,

and after enable optee, the kernel changes memory size from 2G to 3G wrongly , so if I run : du -sh, find .. such as recursive commands, it will be out of memory, the kernel will be crashed .

I enable optee in meta-maaxboard/conf/machine/maaxboard.conf

MACHINE_FEATURES += " optee wifi bluetooth bcm43455"

anybody know why make this issue. I did in sumo version, no this issuebefore

My Qz:

1.how to fix it in kernel for adding patches

2. if can not fix in kernel ;or how to forcefully set memory to 2G in /boot/uEnv.txt

I tried all versions from zeus to mickledore have the same issue, but I ported by myself a few years ago, sumo version NOT had this issue.

thank you so much.

I also posted my QZ here:

https://community.nxp.com/t5/i-MX-Processors/after-enabling-optee-in-maaxboard-memory-size-change-from-2G-to/m-p/2075204#M235978

see my debug info:

correct iomem before enabling optee: correct the size =2G:40000000-bfffffff : System RAM

cat /proc/iomem
00100000-00107fff : 30900000.crypto caam-sm@100000
30050000-3005ffff : 30050000.sai sai@30050000
30200000-3020ffff : 30200000.gpio gpio@30200000
30210000-3021ffff : 30210000.gpio gpio@30210000
30220000-3022ffff : 30220000.gpio gpio@30220000
30230000-3023ffff : 30230000.gpio gpio@30230000
30240000-3024ffff : 30240000.gpio gpio@30240000
30260000-3026ffff : 30260000.tmu tmu@30260000
30280000-3028ffff : 30280000.watchdog watchdog@30280000
302c0000-302cffff : 302c0000.dma-controller dma-controller@302c0000
30330000-3033ffff : 30330000.pinctrl pinctrl@30330000
30350000-3035ffff : 30350000.efuse efuse@30350000
30380000-3038ffff : 30380000.clock-controller clock-controller@30380000
303a0000-303affff : 303a0000.gpc gpc@303a0000
30660000-3066ffff : 30660000.pwm pwm@30660000
30820000-3082ffff : 30820000.spi spi@30820000
30860000-3086ffff : 30860000.serial serial@30860000
30900000-3093ffff : 30900000.crypto crypto@30900000
30a00300-30a003ff : 30a00300.dphy dphy@30a00300
30a20000-30a2ffff : 30a20000.i2c i2c@30a20000
30a60000-30a6ffff : 30a60000.serial serial@30a60000
30aa0000-30aaffff : 30aa0000.mailbox mailbox@30aa0000
30b40000-30b4ffff : 30b40000.mmc mmc@30b40000
30b50000-30b5ffff : 30b50000.mmc mmc@30b50000
30bd0000-30bdffff : 30bd0000.dma-controller dma-controller@30bd0000
30be0000-30beffff : 30be0000.ethernet ethernet@30be0000
32e2d000-32e2dfff : 32e2d000.interrupt-controller interrupt-controller@32e2d000
33000000-33001fff : 33000000.dma-apbh dma-apbh@33000000
38000000-3803ffff : galcore register region
381f0040-381f007f : 381f0040.usb-phy usb-phy@381f0040
38200000-38207fff : usb@38200000
38200000-38207fff : xhci-hcd.3.auto usb@38200000
3820c100-3820ffff : 38200000.usb usb@38200000
382f0040-382f007f : 382f0040.usb-phy usb-phy@382f0040
38300000-38300423 : hantrodec0
38310000-38310423 : hantrodec0
38800000-3880ffff : GICD
38880000-3893ffff : GICR
3d800000-3dbfffff : 3d800000.ddr-pmu ddr-pmu@3d800000
40000000-bfffffff : System RAM
40410000-41dcffff : Kernel code
41dd0000-4210ffff : reserved
42110000-4234ffff : Kernel data
43000000-4300dfff : reserved
44000000-7fffffff : reserved
bd800000-bf9fffff : reserved
bfa58000-bfb58fff : reserved
bfb59000-bfba8fff : reserved
bfbab000-bfbacfff : reserved
bfbad000-bfbadfff : reserved
bfbae000-bfbc1fff : reserved
bfbc2000-bfffffff : reserved

but after enabling optee the size is 3G

cat /proc/iomem | grep System
40000000-fdffffff : System RAM
root@maaxboard:~# cat /proc/iomem
00100000-00107fff : 30900000.crypto caam-sm@100000
30050000-3005ffff : 30050000.sai sai@30050000
30200000-3020ffff : 30200000.gpio gpio@30200000
30210000-3021ffff : 30210000.gpio gpio@30210000
30220000-3022ffff : 30220000.gpio gpio@30220000
30230000-3023ffff : 30230000.gpio gpio@30230000
30240000-3024ffff : 30240000.gpio gpio@30240000
30260000-3026ffff : 30260000.tmu tmu@30260000
30280000-3028ffff : 30280000.watchdog watchdog@30280000
302c0000-302cffff : 302c0000.dma-controller dma-controller@302c0000
30330000-3033ffff : 30330000.pinctrl pinctrl@30330000
30350000-3035ffff : 30350000.efuse efuse@30350000
30380000-3038ffff : 30380000.clock-controller clock-controller@30380000
303a0000-303affff : 303a0000.gpc gpc@303a0000
30660000-3066ffff : 30660000.pwm pwm@30660000
30820000-3082ffff : 30820000.spi spi@30820000
30860000-3086ffff : 30860000.serial serial@30860000
30900000-3093ffff : 30900000.crypto crypto@30900000
30a00300-30a003ff : 30a00300.dphy dphy@30a00300
30a20000-30a2ffff : 30a20000.i2c i2c@30a20000
30a60000-30a6ffff : 30a60000.serial serial@30a60000
30aa0000-30aaffff : 30aa0000.mailbox mailbox@30aa0000
30b40000-30b4ffff : 30b40000.mmc mmc@30b40000
30b50000-30b5ffff : 30b50000.mmc mmc@30b50000
30bd0000-30bdffff : 30bd0000.dma-controller dma-controller@30bd0000
30be0000-30beffff : 30be0000.ethernet ethernet@30be0000
32e2d000-32e2dfff : 32e2d000.interrupt-controller interrupt-controller@32e2d000
33000000-33001fff : 33000000.dma-apbh dma-apbh@33000000
38000000-3803ffff : galcore register region
381f0040-381f007f : 381f0040.usb-phy usb-phy@381f0040
38200000-38207fff : usb@38200000
38200000-38207fff : xhci-hcd.3.auto usb@38200000
3820c100-3820ffff : 38200000.usb usb@38200000
382f0040-382f007f : 382f0040.usb-phy usb-phy@382f0040
38300000-38300423 : hantrodec0
38310000-38310423 : hantrodec0
38800000-3880ffff : GICD
38880000-3893ffff : GICR
3d800000-3dbfffff : 3d800000.ddr-pmu ddr-pmu@3d800000
40000000-fdffffff : System RAM
40410000-41dcffff : Kernel code
41dd0000-4210ffff : reserved
42110000-4234ffff : Kernel data
43000000-4300dfff : reserved
44000000-7fffffff : reserved
fa200000-fd7fffff : reserved
fd966000-fd966fff : reserved
fd967000-fd9b6fff : reserved
fd9b9000-fd9bafff : reserved
fd9bb000-fd9cffff : reserved
fd9d0000-fd9d0fff : reserved
fd9d1000-fdffffff : reserved

Maaxboard Hardware MIPI camera

master_emb — Fri, 14 Feb 2025 10:36:32 GMT

Hi,

I have gone through the MaaXBoard OSM93 Development Kit Hardware User Guide,

but I was unable to find proper information about the MIPI Camera (OV5640) Module.

Could you please provide detailed information, such as where to purchase this camera module from different websites or other sources? Additionally,

it would be very helpful if you could share the datasheet to assist with integration into the MaaXBoard OSM93.

Thanks & Regards

Ronad

Using the Secure Non Volatile Storage (SNVS) on a Maaxboard. External power source needed.

tom-h — Tue, 10 Dec 2024 16:23:23 GMT

Hi All,

I'm currently trying to use the Secure Non Volatile Storage (SNVS) on my Maaxboard. In the IMX8M technical specification (i.MX 8M Dual/8M QuadLite/8M Quad Applications Processors Reference Manual) it states that:

Throughout the SNVS documentation whenever mention is
made of "always-on" logic, this assumes a version of SNVS that implements an
independent power domain for the LP section, and that the power for this section is
supplied by an uninterrupted power supply. The purpose for the independent power
domain is so that data can be retained and certain logic can remain functional even when
the main chip logic is powered down. But this is possible only if the LP domain remains
powered via an uninterrupted power supply when the main chip power domain is
powered off. Usually this uninterrupted power supply would be a battery, with possibly
some power management logic to power the LP section from main power (and perhaps

recharge the battery) when main power is on, and switch to battery power when the main
power is off. In versions of SNVS with an independent LP power domain the LP section
can be electrically isolated from the rest of the chip logic to ensure that its logic does not
get corrupted when the main chip is powered down

It doesn't appear that the maaxboard has a a battery. Has anyone tried to supply a battery or an additional power source to use the SVNS? Is this possible?

Any help with this would be greatly appreciated.

Thanks,

Tom

maaxboard mickledore branch chromium(chromium-ozone-wayland) service can NOT auto startup on wayland

peterzhanggonewithwind — Fri, 22 Nov 2024 16:19:16 GMT

hi all,
maaxboard mickledore branch chromium(chromium-ozone-wayland) service can NOT auto startup on wayland!
I used zeus branch before, zeus branch worked. before, for zeus branch I posted the solution here
https://community.nxp.com/t5/i-MX-Processors/how-to-write-a-system-service-to-auto-startup-chromium-on/m-p/1275666
https://community.nxp.com/t5/i-MX-Processors/can-not-auto-startup-chromium-chromium-ozone-wayland/td-p/1241104

but I am using the same chromium.service file as below in mickledore branch , but not work
I login with ssh or serial debugging port with root user directly to run chromium --no-sandbox. it works! and I put the command chromium --no-sandbox in /etc/profile and login it works. but I put the command line in /etc/rc.local not work
anyway I need to auto startup, any solutions are OK for me, but not found

[Unit]
Description=launch chromium

[Service]
User=root
Environment=DISPLAY=:0
Environment=XDG_RUNTIME_DIR="/run/user/0"
Type=oneshot
ExecStart=/bin/sleep 9
ExecStart=/home/myuser/mouse.out &
ExecStart=/usr/bin/chromium --no-sandbox --disable-infobars --user-data-dir=/tmp/chromium --gpu-no-context-lost --enable-gpu-rasterization --start-fullscreen --kiosk --no-first-run --incognito http://localhost:3300/iframe.html &

[Install]
WantedBy=multi-user.target

I ran systemctl status chromium, the error oputput is
chromium.service - launch chromium
Loaded: loaded (/etc/systemd/system/chromium.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Thu 2024-11-21 23:01:07 UTC; 1min 11s ago
Process: 287 ExecStart=/bin/sleep 9 (code=exited, status=0/SUCCESS)
Process: 653 ExecStart=/home/myuser/mouse.out & (code=exited, status=0/SUCCESS)
Process: 719 ExecStart=/usr/bin/chromium --no-sandbox --disable-infobars --user-data-dir=/tmp/chromium --gpu-no-context-lost --enable-gpu-rasterization --start-fullscreen --kiosk --no-first-run --in)
Main PID: 719 (code=exited, status=1/FAILURE)

Nov 21 23:00:51 maaxboard systemd[1]: Starting launch chromium...
Nov 21 23:01:07 maaxboard chromium[723]: [719:719:1121/230107.465704:ERROR:wayland_connection.cc(209)] Failed to connect to Wayland display
Nov 21 23:01:07 maaxboard chromium[723]: [719:719:1121/230107.465925:ERROR:ozone_platform_wayland.cc(226)] Failed to initialize Wayland platform
Nov 21 23:01:07 maaxboard chromium[723]: [719:719:1121/230107.465963:ERROR:env.cc(225)] The platform failed to initialize. Exiting.
Nov 21 23:01:07 maaxboard systemd[1]: chromium.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 23:01:07 maaxboard systemd[1]: chromium.service: Failed with result 'exit-code'.
Nov 21 23:01:07 maaxboard systemd[1]: Failed to start launch chromium.

any help?
Thank you very much.
I also posted issue here:
https://community.nxp.com/t5/i-MX-Processors/maaxboard-mickledore-branch-chromium-chromium-ozone-wayland/m-p/2000243#M231125

IMX8M High Assurance Boot (HAB) failing with CAAM error

tom-h — Thu, 21 Nov 2024 14:58:38 GMT

Hi all,

I'm not sure if this is the right place for this question, but please point me in the right direction if not!

I am currently trying to use High Assurance Boot (HAB) on my IMX8M device. And run into the following error once I have booted up the device:

U-Boot SPL 2021.04-00002-gf752480a4c-dirty (Nov 15 2024 - 16:47:52 +0000)
power_bd71837_init
set buck8 to 1.2v for DDR4
DDRINFO: start DRAM init
DDRINFO: DRAM rate 2400MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0:  RNG instantiated
Normal Boot
Trying to boot from MMC1
hab fuse not enabled

Authenticate image from DDR location 0x401fcdc0...


U-Boot 2021.04-00002-gf752480a4c-dirty (Nov 15 2024 - 16:47:52 +0000)

CPU:   i.MX8MQ rev2.1 1500 MHz (running at 1000 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 46C
Reset cause: POR
Model: Avnet Maaxboard
DRAM:  2 GiB
Error binding driver 'caam_jr': -96
Some drivers failed to bind
Error binding driver 'simple_bus': -96
Some drivers failed to bind
Error binding driver 'simple_bus': -96
Some drivers failed to bind
initcall sequence 00000000bffcd8d0 failed at call 000000004021c440 (err=-96)
### ERROR ### Please RESET the board ###

HAB relies on CAAM, so I am assuming the issue I am facing is the error in binding the driver 'caam_jr'.

I have followed these steps:

https://github.com/Avnet/uboot-imx/blob/maaxboard_v2020.04_5.4.24_2.1.0/doc/imx/habv4/guides/mx8m_se...

I am using the default branch of uboot-imx:

https://github.com/Avnet/uboot-imx

I also needed to add the following extra config option to resolve an undefined reference to sec_init. Which is related to the SPL in the secure boot.

CONFIG_SPL_CRYPTO_SUPPORT=y;

Please can someone help me understand why I am seeing this error. I have followed the instructions referenced above, so any advice other than what is just included in the instructions would be greatly appreciated!

Thanks,

Tom

Maaxboard MIPI-CSI Pinout

user1092 — Tue, 17 Sep 2024 09:44:55 GMT

Hello,

Can anyone provide a pinout for the MIPI-CSI connector?

Additionally are there any compatible cameras available to buy? As it seems Avnet have stopped selling the only one they support.

Thanks.

maaxboard-8ulp

tgt007 — Thu, 12 Sep 2024 06:44:48 GMT

hi all

What can I do if an error occurs when executing the following command?

devtool create-workspace
devtool modify linux-imx

devtool 构建 linux-imx

ERROR: /home/ubuntu/nxp8ulp/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_6.1.bb: Error executing a python function in <code>: | ETA: --:--:--

The stack trace of python calls that resulted in this exception/failure was:
File: '<code>', lineno: 17, function: <module>
0013:__anon_157__home_ubuntu_nxp8ulp_sources_poky_meta_classes_recipe_kernel_bbclass(d)
0014:__anon_27__home_ubuntu_nxp8ulp_sources_poky_meta_classes_recipe_kernel_uimage_bbclass(d)
0015:__anon_40__home_ubuntu_nxp8ulp_sources_poky_meta_classes_recipe_image_artifact_names_bbclass(d)
0016:__anon_13__home_ubuntu_nxp8ulp_sources_poky_meta_classes_recipe_kernel_devicetree_bbclass(d)
*** 0017:__anon_146__home_ubuntu_nxp8ulp_sources_poky_meta_classes_externalsrc_bbclass(d)
File: '/home/ubuntu/nxp8ulp/sources/poky/meta/classes/externalsrc.bbclass', lineno: 67, function: __anon_146__home_ubuntu_nxp8ulp_sources_poky_meta_classes_externalsrc_bbclass
0063: else:
0064: d.setVar('B', '${WORKDIR}/${BPN}-${PV}')
0065:
0066: local_srcuri = []
*** 0067: fetch = bb.fetch2.Fetch((d.getVar('SRC_URI') or '').split(), d)
0068: for url in fetch.urls:
0069: url_data = fetch.ud[url]
0070: parm = url_data.parm
0071: if url_data.type in ['file', 'npmsw', 'crate'] or parm.get('type') in ['kmeta', 'git-dependency']:
File: '/home/ubuntu/nxp8ulp/sources/poky/bitbake/lib/bb/fetch2/__init__.py', lineno: 1687, function: __init__
1683:
1684: for url in urls:
1685: if url not in self.ud:
1686: try:
*** 1687: self.ud[url] = FetchData(url, d, localonly)
1688: except NonLocalMethod:
1689: if localonly:
1690: self.ud[url] = None
1691: pass
File: '/home/ubuntu/nxp8ulp/sources/poky/bitbake/lib/bb/fetch2/__init__.py', lineno: 1319, function: __init__
1315: logger.warning('Consider updating %s recipe to use "protocol" not "proto" in SRC_URI.', d.getVar('PN'))
1316: self.parm["protocol"] = self.parm.get("proto", None)
1317:
1318: if hasattr(self.method, "urldata_init"):
*** 1319: self.method.urldata_init(self, d)
1320:
1321: for checksum_id in CHECKSUM_LIST:
1322: configure_checksum(checksum_id)
1323:
File: '/home/ubuntu/nxp8ulp/sources/poky/bitbake/lib/bb/fetch2/git.py', lineno: 253, function: urldata_init
0249: write_tarballs = d.getVar("BB_GENERATE_MIRROR_TARBALLS") or "0"
0250: ud.write_tarballs = write_tarballs != "0" or ud.rebaseable
0251: ud.write_shallow_tarballs = (d.getVar("BB_GENERATE_SHALLOW_TARBALLS") or write_tarballs) != "0"
0252:
*** 0253: ud.setup_revisions(d)
0254:
0255: for name in ud.names:
0256: # Ensure any revision that doesn't look like a SHA-1 is translated into one
0257: if not sha1_re.match(ud.revisions[name] or ''):
File: '/home/ubuntu/nxp8ulp/sources/poky/bitbake/lib/bb/fetch2/__init__.py', lineno: 1354, function: setup_revisions
1350:
1351: def setup_revisions(self, d):
1352: self.revisions = {}
1353: for name in self.names:
*** 1354: self.revisions[name] = srcrev_internal_helper(self, d, name)
1355:
1356: # add compatibility code for non name specified case
1357: if len(self.names) == 1:
1358: self.revision = self.revisions[self.names[0]]
File: '/home/ubuntu/nxp8ulp/sources/poky/bitbake/lib/bb/fetch2/__init__.py', lineno: 1221, function: srcrev_internal_helper
1217: if srcrev == "INVALID" or not srcrev:
1218: raise FetchError("Please set a valid SRCREV for url %s (possible key names are %s, or use a ;rev=X URL parameter)" % (str(attempts), ud.url), ud.url)
1219: if srcrev == "AUTOINC":
1220: d.setVar("__BBAUTOREV_ACTED_UPON", True)
*** 1221: srcrev = ud.method.latest_revision(ud, d, name)
1222:
1223: return srcrev
1224:
1225:def get_checksum_file_list(d):
File: '/home/ubuntu/nxp8ulp/sources/poky/bitbake/lib/bb/fetch2/__init__.py', lineno: 1631, function: latest_revision
1627: key = self.generate_revision_key(ud, d, name)
1628: try:
1629: return revs[key]
1630: except KeyError:
*** 1631: revs[key] = rev = self._latest_revision(ud, d, name)
1632: return rev
1633:
1634: def sortable_revision(self, ud, d, name):
1635: latest_rev = self._build_revision(ud, d, name)
File: '/home/ubuntu/nxp8ulp/sources/poky/bitbake/lib/bb/fetch2/git.py', lineno: 741, function: _latest_revision
0737: """
0738: Compute the HEAD revision for the url
0739: """
0740: if not d.getVar("__BBSRCREV_SEEN"):
*** 0741: raise bb.fetch2.FetchError("Recipe uses a floating tag/branch '%s' for repo '%s' without a fixed SRCREV yet doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for OE)." % (ud.unresolvedrev[name], ud.host+ud.path))
0742:
0743: # Ensure we mark as not cached
0744: bb.fetch2.mark_recipe_nocache(d)
0745:
Exception: bb.fetch2.FetchError: Fetcher failure: Recipe uses a floating tag/branch 'maaxboard_lf-6.1.22-2.0.0' for repo 'github.com/Avnet/linux-imx.git' without a fixed SRCREV yet doesn't call bb.fetch2.get_srcrev() (use SRCPV in PV for OE).

ERROR: /home/ubuntu/nxp8ulp/sources/meta-freescale/recipes-kernel/linux/linux-imx_6.1.bb: Error executing a python function in <code>:

ERROR: Parsing halted due to errors, see error messages above

摘要：有 3 条 ERROR 消息，返回非零退出代码。
错误：无法启动 bitbake 环境

Picozed FMC carrier card with Picozed 7015 SOM is not working

nithinsteffy — Mon, 09 Sep 2024 12:06:33 GMT

Hi Team,

I've been working with Picozed FMC carrier card with Picozed 7015 SOM for the last few weeks, it was working fine.

Recently i found that the clock was not getting properly on the PCLK pin, which was allocated for clk_out in my vivado design

And now i'm unable to flash my code via JTAG , it was not detecting the board. Even the D3, D4 LEDs was not indicating any.

What may be the reason?