Stephen Graf

Further to the bluetooth intermittent startup issue, I tried it on the Zunlong image by moving the image to the USB drive and bluetooth works. Attached is the dmesg from the Zunlong boot on USB drive. Note that the dmesg starts at time 0. dmesg_Zunlong_HD.txt

I am still experiencing problems with getting bluetooth to start with the new image from @Gunjan Gupta. On the initial boot after flash to SD it worked. I then used armbian-config to move the system to a USB drive and bluetooth did not start on the first boot of the USB drive. Then I went back to the SD and bluetooth started on the first boot. After a reboot it did not start. The symptom of the failure is the lack of bluetooth in /sys/class. Attached are dmesg files from 3 startups, initial after SD card flash, first boot on USB drive and a subsequent failure and working on the SD card. Why do the dmesg outputs not start at time 0? . dmesg_SD_working.txt dmesg_hd.txt dmesg_SD_reboot.txt dmesg_initial_boot.txt

@pixdrift, @Gunjan Gupta I built an image by getting a repository: git clone https://github.com/viraniac/armbian_build.git. The image works with HDMI using my brand new cable that arrived less than an hour ago. I will test more later. Is this a good way to produce an image? I'm not quite sure.

4. i2c testing on @pixdrift image on zero3. To make i2c work I had to set the i2c3 device to okay and add the pins to the device in the dtb. Normally I think enabling an i2c device could be done via armbian-config hardware toggle but this does not work as the config item does not show any devices. The pins are defined in the dtb but there is no link to them in the i2c definition. See attached dtb excerpt. There seem to be 2 internal i2c devices when looking at /dev. All the other ic2 devices in the dtb are disabled. When I enabled i2c3 in the dtb using the armbian-config edit dtb option, and after a reboot there were 3 i2c devices in /dev: crw-rw---- 1 root i2c 89, 0 Dec 29 10:16 i2c-0 crw-rw---- 1 root i2c 89, 1 Dec 29 10:16 i2c-1 crw-rw---- 1 root i2c 89, 2 Dec 29 10:16 i2c-2 So what is labelled in the drawings and dtb as i2c3 becomes i2c-2 in the system. I connected a temperature humidity sensor to this device and ran some rust code that I had written and it worked. dtb_excerpt.txt

3. GPIO testing on @pixdrift image on zero3. I thought this would be trivial and it almost was. I plugged in a cable on pins PC5 and PC6 on the 26 pin header, and connected them together. Using gpioset and gpioget I was able to change the output on one pin and see it reflected on the other. Then I tried to reboot my system and nothing - no output on the console. I had to look at the schematic to discover that PC5 and 6 are used as a signal for SPI flash boot. See the first page on the upper left corner. One pin is tied high and the other low. The fine print says these pins are used for SPI flash flags. The lesson is if you want to boot from SPI flash it is not advisable to use these two pins!

2.USB testing Again on image from @pixdrift, zero3, I was able to patch together some wires and test on USB2 which appears on the 13 pin header. It works at 2.0 speed without any problems.

I have some testing results from the last few days. I am testing the build from @pixdrift. @Gunjan GuptaI will try to build you image later today. I am not very experienced with git and would appreciate a detailed command list to clone your test repository so I can build it on my system. 1. Bluetooth My original test worked but then I went back later and found a problem. My setup boots from SPI Flash directly to a USB hard drive. On my original test I tested on the first boot after flashing the image to the hard drive. A few days later I looked at the bluetooth again and it did not work. The bluetooth entry in /sys/class was not there and so bluetoothctl complained and would not start. I repeated the image flash procedure and bluetooth works on the initial boot (bluetooth in /sys/class) but not on subsequent powerdown or reboots. I then flashed the Armbian image to an SD chip and retested bluetooth. From the SD card there were intermittent failures. On some boots bluetooth was created in /sys/class and other times it was not. Attached are dmesg files from an hd drive reboot with bluetooth failure and from a Zunlong image were bluetooth works. dmesg_from_hd_system.txt dmesg_from_Zunlong.txt

@pixdrift I just built and loaded the latest from your repo. Something to look into for the HDMI, on startup I get this message: Waiting for system to finish booting ... /usr/lib/armbian/armbian-firstlogin: line 337: /sys/class/graphics/fb0/virtual_size: No such file or directory Welcome to Armbian-unofficial! It is easy to miss because a big blue screen comes right after this. @fizban Did you test the usb ports on the expansion board also?

@pixdriftI tested with your image and bluetooth worked. I was able to pair with my cellphone. I have been getting the following error on all my builds and also from your recent image. This happens for about 5 different pins. Are you getting it also and on zero2? From dmesg: [ 1.644799] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 1.652819] sun50i-h616-pinctrl 300b000.pinctrl: initialized sunXi PIO driver [ 1.653318] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 1.653525] sun50i-h616-r-pinctrl 7022000.pinctrl: initialized sunXi PIO driver [ 1.653722] sun50i-h616-pinctrl 300b000.pinctrl: request() failed for pin 224 [ 1.653731] sun50i-h616-pinctrl 300b000.pinctrl: pin-224 (5000000.serial) status -517 [ 1.653740] sun50i-h616-pinctrl 300b000.pinctrl: could not request pin 224 (PH0) from group PH0 on device 300b000.pinctrl [ 1.653750] dw-apb-uart 5000000.serial: Error applying setting, reverse things back Also from dmesg: [ 1.654472] debugfs: Directory '1100000.mixer' with parent 'regmap' already present! [ 1.654499] debugfs: Directory '1100000.mixer' with parent 'regmap' already present!

I doubt that @Gunjan Gupta provided any patches for zero3 and so I would expect the dtsi patches would be sufficient.

@pixdrift Attached is the decompiled dtb from the zero3 build for wifi. I do not not have a breakdown of the patches that went into it as I just ran the build using the framework from @Gunjan Gupta. current.dts

The comment in mmc0 is in the original dts from linux and has not caused any problems that I know of so far.

I have been able to use @Gunjan Gupta repository to build the wifi changes for orangepi zero3. It works on both 2.4 and 5Ghz bands. I am also experiencing the higher load reported by @pixdrift.

Both the wifi and HDMI work should be common to both the zero2 and zero3 and possibly the zero2w. Would it be possible to work in an environment that supports both?

Thank you @Gunjan Gupta for your update. I would suggest that going forward that any proposed changes for either zero2 or 3 be tested on both boards and that questions and posts for either be tagged somehow for both. The more people working together, the merrier!

There are a number of people working on getting the orangepi zero3 to work with Armbian. The zero3 is almost identical to the zero2 which is a supported board. The differences between the two have been taken into account by upstream Linux and u-boot changes in at least Linux-6.6 to the point where it is possible to build a working zero3 Armbian image. Everything else in theory should be identical between the two boards. Any changes should apply to both zero2 and 3. My question is, what capabilities are supported by Armbian on the zero2. What is working and tested? - wifi -Bluetooth -HDMI -sound -gpio -i2c, spi It would be helpful to know what works today on zero2 to avoid duplicating efforts on zero3. Any changes being developed for zero3 should also be tested on zero2.

Video device from ls /dev crw-rw---- 1 root tty 7, 70 Dec 11 22:14 vcsu6 crw------- 1 root root 10, 137 Dec 11 22:14 vhci crw-rw---- 1 root video 81, 0 Dec 11 22:14 video0 crw------- 1 root root 10, 130 Dec 11 22:14 watchdog crw------- 1 root root 247, 0 Dec 11 22:14 watchdog0

I also seem to have a video device. Unfortunately I am still waiting delivery of a micro HDMI adapter.

This is from the stock build without patches for gpu. sysadmin@orangepizero3:~$ lsmod Module Size Used by rfkill 24576 1 sunrpc 290816 1 lz4hc 12288 0 lz4 12288 0 sunxi_cedrus 49152 0 v4l2_mem2mem 28672 1 sunxi_cedrus videobuf2_dma_contig 20480 1 sunxi_cedrus videobuf2_memops 16384 1 videobuf2_dma_contig videobuf2_v4l2 20480 2 sunxi_cedrus,v4l2_mem2mem videodev 221184 3 sunxi_cedrus,videobuf2_v4l2,v4l2_mem2mem polyval_ce 12288 0 videobuf2_common 45056 5 sunxi_cedrus,videobuf2_dma_contig,videobuf2_v4l2,v4lmemops polyval_generic 12288 1 polyval_ce mc 57344 5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_commo zram 28672 3 binfmt_misc 20480 1 fuse 126976 1 dm_mod 131072 0 motorcomm 24576 1 dwmac_sun8i 24576 0 mdio_mux 12288 1 dwmac_sun8i sysadmin@orangepizero3:~$

I have been able to build images for the orange-pi zero3 using the Arabian build system. I spend the last few weeks helping to test u-boot on this board and the final patches have been put into u-boot v2024.01-rc5 which should be released Dec 18. I used rc4 and imported the u-boot patches when building Arabian. There was one patch that failed while building under rc4 but since it did not relate to zero3 I just removed the patch. There is one u-boot patch for emac timing that I had trouble with getting into the patch system. Without this patch the Ethernet port only works at 100Mhz. This patch is a kernel patch to the dts that is supposed to eventually come from linux. I did manage to hack the patch in very inelegantly and got the port to run at 1Ghz. A lot of stuff does not work on this image, but it runs. Come Dec 18 and the release of u-boot v2024.01-rc5 we can at least build Armbian images and start working from there. ___ ____ _ _____ _____ / _ \| _ \(_) |__ /___ _ __ ___|___ / | | | | |_) | | / // _ \ '__/ _ \ |_ \ | |_| | __/| | / /| __/ | | (_) |__) | \___/|_| |_| /____\___|_| \___/____/ Welcome to Armbian-unofficial 24.2.0-trunk Bookworm with bleeding edge Linux 6.6.6-edge-sunxi64 No end-user support: built from trunk System load: 8% Up time: 4 min Memory usage: 13% of 919M IP: 192.168.1.32 CPU temp: 34°C Usage of /: 12% of 15G RX today: 2.1 KiB [ 0 security updates available, 18 updates total: apt upgrade ] Last check: 2023-12-11 18:06