ValdikSS

JEB05DFC esd0402-6
https://www.jjm.com/profhqj4/
TVS Diode Array
ESD protective components are TVS arrays specially used for small-signal ESD protection or surge protection and are mostly used for multi-channel protection. It has the advantages of a small package size and high integration.

95% of companies work only with and for their customers. Their customers are other companies which use their chips to manufacture the finished device.
The customers receive code and support from the chip manufacturer.
The end users, as well as community/hobby projects like Armbian, are not the customers for chip companies. It is a very tiny market compared to the embedded/retail use.
 
Rockchip does not make consumer chips, they make specialized chips: for Android smartphones, for cameras, for vehicles, etc.
The customers of Rockchip use Android, RTOSes, custom Linux-based OSes.
 
Consumer chip companies, such as Intel and AMD, contribute to Linux because their customers use mainline Linux.
 
PC operating systems are supplied by third parties that are not part of the computer manufacturer, motherboard or processor vendor. All component manufacturers must write drivers for Windows, certify them with Microsoft, and make sure that their device works properly ideally on any computer. You, the user, buy (or obtain) a copy of the operating system from the operating system company.
 
The operating system for an appliance (smartphone) comes with the appliance itself (as a bundle), and is supplied by the appliance manufacturer, not by operating system manufacturer. The manufacturer of electronic components does not need to contact the creators of the operating systems, they write a driver for Android kernel (yes, for Android kernel, with all its wakelock subsystems and such in mind) and gives it to the manufacturer of the appliance directly (and sometimes only supplies hardware, and the driver must be made by the manufacturer of the appliance).

The current image is broken due to incorrect GPT header.
https://github.com/armbian/build/issues/10647
 
I had the same issue and somehow when I flashed the image the first attempt, the bootloader detected *something* and tried to boot *something*, but the console never appeared.
The subsequent writes, after wiping the start and the end of MicroSD, failed at the bootloader (the bootloader did not see the partition table, just as Linux both times).
 
So my guess is that even if the bootloader uses backup partition table somehow, the Linux kernel does not and fails to mount rootfs.
 
The fix is to set Number of partition entries in array = 16. See the ticket. The image successfully boots after that.

It's and old Allwinner chip, ARMv7-based. GPU is PowerVR SGX544MP1, which is not supported in Mesa and will not work in Armbian.
Wi-Fi is AP6212, a Broadcom/Synaptics SYN43436S chip, should work fine.
Armbian build for M3 is community-supported, by @AaronNGray. Maybe they'll shed more light on this board.

In case anyone wondering, AIC8800D80 found in Raxda Zero 3W and Radxa Cubie A5E (aic8800 driver) supports WPA3 SAE, but not GCMP/GCMP-256 ciphers.
 
root@radxa-zero3:~# iw phy Wiphy phy0 wiphy index: 0 max # scan SSIDs: 3 max scan IEs length: 200 bytes max # sched scan SSIDs: 0 max # match sets: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device supports AP-side u-APSD. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CMAC (00-0f-ac:6) * WPI-SMS4 (00-14-72:1) Available Antennas: TX 0 RX 0 Supported interface modes: * managed * AP * AP/VLAN * monitor * mesh point * P2P-client * P2P-GO * P2P-device …  
> get_capability pairwise CCMP TKIP > get_capability group CCMP TKIP WEP104 WEP40 > get_capability key_mgmt NONE IEEE8021X WPA-EAP WPA-PSK WPA-EAP-SUITE-B OWE DPP FT-PSK FT-EAP > get_capability proto RSN WPA > get_capability auth_alg OPEN SHARED LEAP SAE  

In case anyone wondering, AIC8800D80 found in Raxda Zero 3W and Radxa Cubie A5E (aic8800 driver) supports WPA3 SAE, but not GCMP/GCMP-256 ciphers.
 
root@radxa-zero3:~# iw phy Wiphy phy0 wiphy index: 0 max # scan SSIDs: 3 max scan IEs length: 200 bytes max # sched scan SSIDs: 0 max # match sets: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device supports AP-side u-APSD. Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP-128 (00-0f-ac:4) * CMAC (00-0f-ac:6) * WPI-SMS4 (00-14-72:1) Available Antennas: TX 0 RX 0 Supported interface modes: * managed * AP * AP/VLAN * monitor * mesh point * P2P-client * P2P-GO * P2P-device …  
> get_capability pairwise CCMP TKIP > get_capability group CCMP TKIP WEP104 WEP40 > get_capability key_mgmt NONE IEEE8021X WPA-EAP WPA-PSK WPA-EAP-SUITE-B OWE DPP FT-PSK FT-EAP > get_capability proto RSN WPA > get_capability auth_alg OPEN SHARED LEAP SAE