Sand_Death

@alexc Hi, thanks for the response and for the patch! Just to clarify — we actually used your PCIe BSP fix (commit a9eaa51d) and the stock, unmodified hailo_pci 4.21.0 driver from the official Hailo GitHub (v4.21.0 tag). No changes were made to the Hailo driver side at all. Earlier in the process we had experimented with workarounds on the Hailo driver (INTx bypass + polling thread), but those were reverted completely before the final test. The report describes the end state: your kernel patch + stock driver. Result with your fix: hailo 0000:04:00.0: Enabled MSI interrupt No INTx fallback, no polling. Load average dropped from 18+ to ~12, Frigate CPU from ~485% to ~83% (real inference on 9 cameras). Regarding the GitHub PR / kernel patch — that would be great. The fix is clearly in the right place (PCIe driver), and a proper patch submission would help other Allwinner A733 users with PCIe devices.

@alexc I tested the modified kernel and asked Claude to report it, he reported it like this. System Refinement and Build Optimization Report Feedback 1. MSI Fix Confirmed Working Details: The MSI fix has been verified and successfully tested on Hailo8L (sun60iw2/A733 platform). Result: Massive reduction in system load: load avg dropped from 18+ to ~12, and Frigate CPU usage plummeted from 485% to 83% during real-world inference. High Priority 2. sunxi-autogen.h in .gitignore Issue: This file is currently ignored by .gitignore, yet it is strictly required for the build to succeed and is not automatically generated. Solution: Either implement automatic generation of this file inside the Makefile OR properly document the creation steps in the README. 3. Undocumented LOCALVERSION Behavior Issue: Building from a dirty Git tree automatically appends a + suffix to the kernel version string, leading to a critical vermagic mismatch for compiled modules. Solution: Document this behavior in the README or enforce proper default behavior in the default configuration file. Medium Priority 4. Missing BSP_TOP Export Issue: Running make olddefconfig crashes unless BSP_TOP=bsp/ is explicitly passed as an environment variable. Solution: Add path auto-detection directly into the root Makefile to make the build self-contained. 5. Missing DKMS Config for hailo_pci Issue: Since this is an out-of-tree module, users must manually rebuild it after every routine kernel update. Solution: Provide a DKMS configuration to automate the rebuild process on the OS level. Low Priority 6. hailo_pci Driver Integration in initramfs Issue: The module is not automatically included in the initramfs image during the build phase. Solution: Create a dedicated hook script or add a section in the documentation explaining manual configuration via modules-load.d and update-initramfs. 7. Overly Permissive /dev/hailo0 Permissions (World-Writable) Issue: The device node permissions are set to crw-rw-rw- (anyone can write to it), which poses a security risk. Solution: Deploy a standard udev rule to restrict permissions and grant access safely via a dedicated system group. !!! At the moment, I confirm that it works with these edits.

Hi @alexc, I'd be happy to test your changes! I've now achieved full functionality with AI; it did a very extensive and time-consuming refactoring of not only the kernel but also the driver. Its conclusions about what it did were as follows; I don't know if this will help! I've now achieved functionality with the old kernel (taking into account Claude's edits). I'm attaching its conclusions. CLAUDE CONCLUSION: The stock BSP/mainline implementation fails at two distinct architectural levels: 1. Hardware/SoC Layer (Inbound ATU) The SUNXI PCIe Root Complex (sun60iw2) does not have its inbound ATU (Address Translation Unit) entries properly configured for the DDR memory range. The Consequence: When the Hailo-8 endpoint attempts to write an MSI packet to the physical DDR address (pp->msi_data), the Root Complex returns an Unsupported Request (UR) TLP response. The Hailo firmware immediately panics on the unexpected UR, dropping the PCIe link entirely. From this point onward, the entire BAR register space returns 0xFF. 2. Interrupt Path Layer (DTS Routing) Even when falling back to legacy INTx interrupts to avoid the MSI-driven crash, the INTA# signal forwarded from the Hailo-8 through the ASM1182e switch never reaches the CPU. The IRQ counter in /proc/interrupts stays completely stagnant. This strongly points to an incorrect PCIe interrupt-map configuration in the device tree (DTS) for the sun60iw2. ComponentResponsibility / Issue Kernel (pci-sun6i.c / RC driver)Bug: Lacks inbound ATU window configuration for DDR space. MSI target addresses are dropped at the RC level. Driver (hailo-pci)Limitation: Expects a fully functional hardware interrupt path. Requires a software fallback mechanism to handle the broken RC. The Proper Solution (Kernel-Level Fix) The cleanest fix belongs in the SUNXI PCIe RC driver (e.g., drivers/pci/controller/dwc/pci-sun6i.c or its equivalent for the A527). Right after the PCIe link is established, an inbound window covering the system's DDR space must be explicitly mapped: /* After setting up the PCIe link, program the inbound ATU window for system DDR */ dw_pcie_prog_inbound_atu(pci, 0, PCIE_ATU_TYPE_MEM, phys_ddr_base, /* target address */ phys_ddr_base, /* base address */ ddr_size); /* size (Map entire DDR pool) */ Implementing this would allow: Inbound MSI writes to successfully target the GIC. Inbound DMA transfers to pass cleanly without getting filtered out by the RC. Note: The DTS interrupt-map for sun60iw2 also needs a close look to ensure legacy INTx lines map correctly to the GIC. The Temporary Workaround (3 Driver-Level Patches) Since changing the upstream kernel wasn't immediately viable, we implemented a robust workaround directly inside the hailo-pci kernel driver split across 3 patches: Patch 1: Enforce Legacy INTx over MSI (pcie.c) We forced the driver to avoid MSI and use legacy INTx. Because legacy interrupts rely on dedicated sideband signaling rather than inbound write TLPs, it prevents the inbound ATU failure from triggering an immediate firmware panic and a hard PCIe link drop. Patch 2: The Core Fix — Kernel Polling Thread (fops.c + pcie.c) Since regular interrupts are completely deaf on this platform, we introduced a dedicated kernel polling thread that fires alongside enable_interrupts(): // Kernel thread mimicking the interrupt handler via register polling int hailo_poll_thread_fn(void *data) { struct hailo_pcie_board *board = (struct hailo_pcie_board *)data; u32 irq_source; while (!kthread_should_stop()) { usleep_range(900, 1100); // ~1ms interval balances latency and CPU overhead if (!hailo_pcie_read_interrupt(&board->pcie_resources, &irq_source)) continue; // Manually dispatch: firmware control SW IRQ + vDMA channel completions nnc_irq_handler(board, &irq_source); if (irq_source.vdma_channels_bitmap) { hailo_vdma_irq_handler(&board->vdma, 0, irq_source.vdma_channels_bitmap); } } return 0; } Why this works: The Hailo firmware writes completion bits directly to the BCS_ISTATUS_HOST register (BAR0 offset 0x018C) regardless of whether the actual MSI/INTx block successfully alerts the CPU. By reading this register in a 1ms loop and manually routing the completions, processing functions seamlessly. Patch 3: VMA Locking Update for Modern Kernels (memory.c) For compatibility with modern kernels (Linux $\ge$ 6.18), we wrapped find_vma() with the mandatory read lock to prevent kernel warnings and memory subsystem instability: mmap_read_lock(mm); vma = find_vma(mm, address); mmap_read_unlock(mm); Real-World Performance & Results We tested this setup under heavy real-time Object Detection in Frigate NVR: Model: yolov8s (running entirely on Hailo-8 via the patched driver) Inference Latency: ~25–30 ms Throughput: ~24 FPS split across 9 simultaneous camera streams Stability: 0 crashes over long-term testing (previously crashed within exactly 1 second of starting vDMA operations). Conclusion A polling thread with a 1ms interval proves to be more than fast enough to handle high-throughput AI inference workloads. The performance overhead is negligible, pinning one CPU thread into a low-impact state since usleep_range leaves the CPU resting most of the time. While a kernel-level inbound ATU and DTS fix is the ideal target for Armbian/Radxa mainlines, this driver-level patch provides a completely stable workaround for anyone trying to build edge AI platforms using Allwinner chips right now. Let me know if anyone needs the raw patch files or wants to help upstream the correct ATU fixes to pci-sun6i.c!

@alexc This happens on their kernel too, I created a topic on their forum (https://forum.radxa.com/t/hailo8-pcie-fw-control-timeout-on-cubie-a7a-with-asmedia-pcie-switch/31023), I suspect that the problem is on the Allwinner side and a patch is needed not even from Radxa but from Allwinner. But yesterday I was looking at their forum and there are quite a lot of complaints about the PCIe line, but this remains unanswered, I suspect that they think this is a feature and not a bug. If you need any other help or further study of the problem, I am ready to help in any way I can.

@Nick A @alexc Sorry for being so pushy, I had some time today and was tinkering with this board (Claude helped me with this). Like all AI, it can make mistakes, but it thinks this is the root of the problem (I wasted almost 6 hours today on this and all the weekly limits lol). Anyway, here's his summary of what's wrong, but since I'm not a developer, I can neither confirm nor deny what he says. Hailo8 AI Accelerator on Radxa Cubie A7A - Full Debug Report Hardware: Board: Radxa Cubie A7A (Allwinner A733/sun60iw2, 8-core) AI HAT: Makerobo Hailo8 HAT (M.2 + FPC connector, designed for RPi5) PCIe topology: Root Port → ASMedia ASM1182e switch → Hailo-8 Kernel tested: BSP: 6.18.19-edge-sun60iw2 (NickAlilovic/build Radxa-A7A branch) Mainline BSP: 6.18.35 (alexcaoys/allwinner-bsp linux-6.18.y branch, custom build) Symptoms: Every fw_control ioctl times out with HAILO_DRIVER_TIMEOUT(87). Device loads firmware successfully, /dev/hailo0 is created, but becomes completely unusable for inference. Debug journey: First suspected power management (D3cold issues) — fixed with no_power_mode=1 parameter Suspected wrong FPC cable (RPi5 vs Radxa PIEX) — ruled out after comparing schematics, pinouts are identical Found RxErr+ on ASMedia switch ports in AER — suggested physical signal issues Root cause found: MSI interrupts not working MSI investigation results: # MSI not configured $ cat /sys/bus/pci/devices/0000:04:00.0/msi_irqs/ # empty $ lspci -vvv -s 04:00.0 | grep MSI Capabilities: [e0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 # Address zero = MSI never configured # IRQ routing broken Interrupt: pin ? routed to IRQ 482 # "?" = no INTx routing either After building custom kernel 6.18.35 (alexcaoys/allwinner-bsp): # Progress! IRQ now routes properly Interrupt: pin A routed to IRQ 482 # pcie-msi IRQ exists! 479: 1 wakeupgen 153 Level pcie-msi But MSI still not working for endpoint devices: $ cat /sys/bus/pci/devices/0000:04:00.0/msi_irqs/ # still empty $ dmesg | grep ITS ITS: No ITS available, not enabling LPIs Root cause analysis: The sunxi-pcie driver handles MSI internally via wakeupgen interrupt controller (IRQ 479, pcie-msi). However, this MSI handler is not exposed as a standard PCI msi-controller node that endpoint devices (like Hailo8) can use through the standard Linux PCI MSI API. Without a proper msi-controller, pci_alloc_irq_vectors() falls back to legacy INTx. But INTx routing through ASMedia ASM1182e PCIe switch also doesn't work properly — device shows pin ? (no routing) instead of pin A. Hailo8 requires MSI for fw_control command completion notifications. Without working interrupts, every ioctl waits 1000ms and times out. What needs to be fixed: The sunxi-pcie driver needs to register a proper msi-controller so endpoint devices behind the PCIe bus can use standard PCI MSI API OR legacy INTx routing needs to work through ASMedia switch (currently pin ?) The DTB PCIe node has interrupt-names = "sii", "msi" but the MSI interrupt is not wired to standard PCI MSI infrastructure PCIe topology for reference: 00:00.0 Root Port (1f6d:abcd) 01:00.0 ASMedia ASM1182e upstream port 02:07.0 ASMedia ASM1182e downstream port 04:00.0 Hailo-8 AI Processor (1e60:2864) Links: Forum post: https://forum.radxa.com/t/hailo8-pcie-fw-control-timeout-on-cubie-a7a-with-asmedia-pcie-switch/31023 (posted about FPC cable and MSI issue) Hailo driver: https://github.com/hailo-ai/hailort-drivers/tree/hailo8 If necessary, I can also open an issue on GitHub and bring this problem to the attention of the board developers, because the behavior is the same on the stock core.

@Nick A @alexc Update: Hailo8 AI HAT issue - Root cause found First, a quick update on the Ethernet issue — I set the board aside for a while, noticed some activity in the GitHub repository, rebuilt the firmware, and it worked. Now I'm trying to run Frigate with a Hailo8 AI HAT (marketed for Raspberry Pi 5, with an M.2 slot). The device loads firmware successfully but becomes completely unresponsive. After extensive debugging I believe I found the root cause. Problem: MSI interrupts not working bash$ cat /sys/bus/pci/devices/0000:04:00.0/msi_irqs/ # empty — MSI not configured $ lspci -vvv -s 04:00.0 | grep MSI Capabilities: [e0] MSI: Enable- Count=1/1 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 # Address is zero — MSI never configured by kernel $ cat /proc/interrupts | grep hailo # empty — no interrupt handler registered Interrupt: pin ? routed to IRQ 492 # "?" means no INTx routing either Hailo8 uses MSI interrupts to signal command completion. Without MSI, every fw_control ioctl waits 1000ms and times out. The device loads firmware successfully but becomes unusable for any actual inference. PCIe topology: 00:00.0 Root Port 01:00.0 ASMedia ASM1182e PCIe Switch (upstream) 02:07.0 ASMedia ASM1182e PCIe Switch (downstream) 04:00.0 Hailo-8 AI Processor Kernel: 6.18.19-edge-sun60iw2 (Armbian community build) It seems the sunxi PCIe driver does not support MSI for devices behind an ASMedia PCIe switch. Is this a known limitation? Is there a fix or workaround available?

Hi, @Nick A yes, of course, I extracted the archive and burned the .img image, but I burned the image using Armbian Imager. Today I tried burning the manufacturer's image to another flash drive, and it launched successfully. After that, I tried burning yours again, and everything worked on a different flash drive when burning it using BalenaEtcher! Amazing! The only thing I want to point out is that I have rev 1.10 selected, and the network card doesn't seem to be detected (wired connection). root@radxa-cubie-a7a:~# sudo lshw -class network *-network description: Wireless interface physical id: 12 logical name: wlan0 serial: 9c:04:b6:84:46:4b capabilities: ethernet physical wireless configuration: broadcast=yes driver=usb driverversion=6.18.19-edge-sun60iw2 ip=192.168.99.218 multicast=yes wireless=IEEE 802.11 root@radxa-cubie-a7a:~# I tried downloading and installing the driver from the radxa repository (the USB version). Because the dmesg output was like this. root@radxa-cubie-a7a:~# sudo dmesg | grep -i -E 'firmware|loading|failed' [ 0.000000] [ T0] psci: PSCIv1.1 detected in firmware. [ 0.000247] [ T0] sunxi:timer_sun50i:[ERR]: request bus clock failed [ 0.000252] [ T0] sunxi:timer_sun50i:[ERR]: sun50i timer of resource get failed [ 0.070642] [ T1] sunxi-iommu-v2 3900000.iommu: master probe failed with -517 [ 3.080921] [ T1] axp8191-temp-ctrl: Failed to locate of_node [id: 0] [ 3.210460] [ T1] NSI_PMU 2020000.nsi-controller: Get support-ecc failed [ 4.708335] [ T1] Loading compiled-in X.509 certificates [ 7.426931] [ T1] sunxi:VE:[WARN]: 392 ve_dvfs_get_attr(): get vf table failed, default 624MHz [ 7.459393] [ T1] sunxi:VE:[WARN]: 392 ve_dvfs_get_attr(): get vf table failed, default 624MHz [ 8.120987] [ T179] powervr 1800000.gpu: [drm] loaded firmware powervr/rogue_36.56.104.183_v1.fw [ 10.773578] [ T1] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67 [ 10.859899] [ T287] aic_load_firmware :firmware path = /lib/firmware/aic8800D80/fw_patch_table_8800d80_u02.bin [ 10.872268] [ T287] aic_load_firmware :firmware path = /lib/firmware/aic8800D80/fw_adid_8800d80_u02.bin [ 10.880698] [ T287] ### Upload fw_adid_8800d80_u02.bin firmware, @ = 201940 size=1708 [ 10.881217] [ T287] aic_load_firmware :firmware path = /lib/firmware/aic8800D80/fw_patch_8800d80_u02.bin [ 10.889530] [ T287] ### Upload fw_patch_8800d80_u02.bin firmware, @ = 1e0000 size=32192 [ 10.898148] [ T287] aic_load_firmware :firmware path = /lib/firmware/aic8800D80/fw_patch_8800d80_u02_ext0.bin [ 10.906475] [ T287] ### Upload fw_patch_8800d80_u02_ext0.bin firmware, @ = 20b43c size=13788 [ 10.934395] [ T287] aic_load_firmware :firmware path = /lib/firmware/aic8800D80/fmacfw_8800d80_u02.bin [ 10.943638] [ T287] ### Upload fmacfw_8800d80_u02.bin firmware, @ = 120000 size=349096 [ 11.028999] [ T287] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 12.141961] [ T335] sunxi:sound-mach:[ERR]: 537 simple_parse_of(): simple_dai_link_of failed [ 12.162251] [ T335] sunxi:sound-mach:[ERR]: 537 simple_parse_of(): simple_dai_link_of failed [ 12.219436] [ T9] aic_load_fw 1-1.4:1.0: probe with driver aic_load_fw failed with error -1 [ 12.219683] [ T9] aic_load_fw 1-1.4:1.1: probe with driver aic_load_fw failed with error -1 [ 12.219876] [ T9] aic_load_fw 1-1.4:1.2: probe with driver aic_load_fw failed with error -1 [ 12.344962] [ T9] AICWFDBG(LOGERROR) rwnx_load_firmware: aic_userconfig_8800d80.txt file failed to open [ 12.344978] [ T9] AICWFDBG(LOGERROR) wrong size of firmware file [ 12.392525] [ T77] sunxi:sound-ac101:[ERR]: 1725 ac101_probe(): try read ac101 5 times but failed, ac101 probe failed [ 12.413143] [ T77] sunxi-snd-mach soc@3000000:i2s0_mach: ASoC: failed to instantiate card -1 [ 12.427459] [ T77] sunxi-snd-mach soc@3000000:i2s0_mach: probe with driver sunxi-snd-mach failed with error -1 [ 12.775283] [ T1] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67 [ 13.577615] [ T1] systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67 However, updating the driver didn't help. But as far as I understand, the AIC8800 drivers are the drivers for WiFi and Bluetooth. I also tried to torment Google Gemini and ran the command it recommended, its output is like this root@radxa-cubie-a7a:~# sudo dmesg | grep -i -E 'eth|mac|realtek|stmmac' [ 0.000000] [ T0] Machine model: sun60iw2 [ 0.000000] [ T0] psci: probing for conduit method from DT. [ 0.000000] [ T0] Kernel command line: root=UUID=34b3b4ba-6c61-4aff-9fb5-d8dbaf8a9d1e rootwait rootfstype=ext4 splash plymouth.ignore-serial-consoles console=ttyS0,115200 console=tty1 consoleblank=0 loglevel=7 ubootpart=7cb3a0a1-d0c5-4814-b3bf-acf7cb5fee06 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u mac_addr= coherent_pool=2M irqchip.gicv3_pseudo_nmi=0 cgroup_enable=cpuset cgroup_memory=1 swapaccount=1 kasan=off no_console_suspend fsck.fix=yes fsck.repair=yes net.ifnames=0 cgroup_enable=memory [ 0.000000] [ T0] Unknown kernel command line parameters "splash ubootpart=7cb3a0a1-d0c5-4814-b3bf-acf7cb5fee06 mac_addr= cgroup_enable=memory cgroup_memory=1", will be passed to user space. [ 4.882846] [ T12] sunxi-drm soc@3000000:sunxi-drm: late IOMMU probe at driver bind, something fishy here! [ 7.841902] [ T1] mac_addr= [ 9.766287] [ T1] systemd[1]: systemd 257.13-1~deb13u1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE) [ 10.868628] [ T1] systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement skipped, unmet condition check ConditionSecurity=measured-uki [ 11.005686] [ T283] aic_load_firmware :firmware path = /lib/firmware/aic8800D80/fmacfw_8800d80_u02.bin [ 11.015312] [ T283] ### Upload fmacfw_8800d80_u02.bin firmware, @ = 120000 size=349096 [ 12.061513] [ T346] OF: /soc@3000000/i2s0_mach: Read of boolean property 'soundcard-mach,routing' with a value. [ 12.072296] [ T346] OF: /soc@3000000/i2s0_mach: Read of boolean property 'soundcard-mach,pin-switches' with a value. [ 12.089497] [ T346] sunxi:sound-mach:[WARN]: 372 asoc_simple_parse_ucfmt(): set data late to default [ 12.107845] [ T346] sunxi:sound-mach:[ERR]: 537 simple_parse_of(): simple_dai_link_of failed [ 12.156684] [ T346] sunxi:sound-mach:[WARN]: 372 asoc_simple_parse_ucfmt(): set data late to default [ 12.176300] [ T346] sunxi:sound-mach:[ERR]: 537 simple_parse_of(): simple_dai_link_of failed [ 12.211549] [ T78] OF: /soc@3000000/i2s0_mach: Read of boolean property 'soundcard-mach,routing' with a value. [ 12.227920] [ T78] OF: /soc@3000000/i2s0_mach: Read of boolean property 'soundcard-mach,pin-switches' with a value. [ 12.247053] [ T78] sunxi:sound-mach:[WARN]: 372 asoc_simple_parse_ucfmt(): set data late to default [ 12.260641] [ T78] sunxi:sound-mach:[ERR]: 537 simple_parse_of(): simple_dai_link_of failed [ 12.279264] [ T78] sunxi:sound-mach:[WARN]: 372 asoc_simple_parse_ucfmt(): set data late to default [ 12.345223] [ T78] OF: /soc@3000000/i2s0_mach: Read of boolean property 'soundcard-mach,routing' with a value. [ 12.345250] [ T78] OF: /soc@3000000/i2s0_mach: Read of boolean property 'soundcard-mach,pin-switches' with a value. [ 12.345271] [ T78] sunxi:sound-mach:[WARN]: 372 asoc_simple_parse_ucfmt(): set data late to default [ 12.345288] [ T78] sunxi:sound-mach:[ERR]: 537 simple_parse_of(): simple_dai_link_of failed [ 12.355471] [ T78] OF: /soc@3000000/i2s0_mach: Read of boolean property 'soundcard-mach,routing' with a value. [ 12.355526] [ T78] OF: /soc@3000000/i2s0_mach: Read of boolean property 'soundcard-mach,pin-switches' with a value. [ 12.355570] [ T78] sunxi:sound-mach:[WARN]: 372 asoc_simple_parse_ucfmt(): set data late to default [ 12.355597] [ T78] OF: /soc@3000000/i2s0_mach/soundcard-mach,cpu: Read of boolean property 'soundcard-mach,mclk-fp' with a value. [ 12.355878] [ T78] sunxi-snd-mach soc@3000000:i2s0_mach: ASoC: DAPM unknown pin HS MIC Jack [ 12.355886] [ T78] sunxi-snd-mach soc@3000000:i2s0_mach: ASoC: DAPM unknown pin HP Jack [ 12.491963] [ T78] sunxi-snd-mach soc@3000000:i2s0_mach: ASoC: failed to instantiate card -1 [ 12.500679] [ T78] sunxi-snd-mach soc@3000000:i2s0_mach: probe with driver sunxi-snd-mach failed with error -1 [ 12.696783] [ T1] systemd[1]: systemd-machine-id-commit.service - Save Transient machine-id to Disk skipped, unmet condition check ConditionPathIsMountPoint=/etc/machine-id [ 12.879365] [ T1] systemd[1]: systemd-machine-id-commit.service - Save Transient machine-id to Disk skipped, unmet condition check ConditionPathIsMountPoint=/etc/machine-id [ 12.895054] [ T1] systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement skipped, unmet condition check ConditionSecurity=measured-uki [ 13.872897] [ T1] systemd[1]: systemd-machine-id-commit.service - Save Transient machine-id to Disk skipped, unmet condition check ConditionPathIsMountPoint=/etc/machine-id [ 13.888466] [ T1] systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement skipped, unmet condition check ConditionSecurity=measured-uki [ 15.517187] [ T983] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Could it be that a different type of Ethernet is used here?

I just received a new Radxa Cubie A7A board. I decided to try flashing @Nick A firmware (https://github.com/NickAlilovic/build/releases/tag/Radxa-Cubie-A7A-A7Z-A7S-Mainline-V0.1), but the board simply wouldn't boot. I used a Netac 32 GB microSDHC card, class 10, UHS-I. I've attached the UART logs below.load.log