-
-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Image | Orange Pi Zero 2W #6827
Comments
I tried making my own distribution, following the guide, however, I couldn't get the created image working on the device. I can only connect headlessly over wifi to the device, so this may have been the overall issue 😅 Looking at the specs between the OPi Zero 3 and the OPI Zero 2W there's a lot of similar components used, I've just flashed the Zero 3 image to my device and it seems to be working ok so far... 🤞 and the wifi definitely works – due to my reliance on headless setup.
Are there any other board features that we should care about that might affect the usage of the Zero 3 image on the Zero 2W? On paper they look pretty similar, the only difference really being their form factor and the Zero 3 having some additional physical I/O, like ethernet. Edit: it seems like there's already a lot discussion over in #6594 Edit 2: (5 Jan 2024) I've been using the Orange Pi Zero 3 image successfully for a week now with no issues. It's only connected via WiFi. I have successfully been using software like Tailscale, NFS network drive etc with it. |
I'm also using the I changed the Governor to max out at 1008Mhz (down from 1502Mhz) and that seems to have stabilised the system. |
@MichaIng it doesn't seem to. Running this from an OPi Zero 2W it returns Are there any quick workaround to selecting the correct device tree during the bootload (or after the fact)? |
Try the following: G_CONFIG_INJECT 'fdtfile=' 'fdtfile=allwinner/sun50i-h616-orangepi-zero2w.dtb' /boot/dietpiEnv.txt
reboot |
Thanks for the quick response! That makes sense, I'll be away from my OPi for a couple of weeks. If someone else can confirm in the interim, go ahead! |
G_CONFIG_INJECT said I didn't have permissions, when I prefixed with sudo command wasn't found. So applied the change with sudo nano and rebooted.
One thing I noticed is that with this Zero2 W booted with the proper config my dual nic carrier board doesn't work properly (nics light up, but don't work, stay lit after disconnecting Ethernet). Reverting dietpiEnv.txt and rebooting restores function of the nics. The carrier board connects via 4 pogo pins to the middle USB port (visible around green led) As an aside, the following message is present regardless which dtb is used
|
Back in business 💼 Following @MichaIng's instruction
The device on boot now reports the correct device tree:
|
I still don't get why the carrier board (which is a usb hub connected over pogo pins) would work fine out of the box with the OrangePi Zero 3 device tree but not work at all with the OrangePi Zero 2 W tree. |
Hmm, that is nasty indeed 🤔. |
Can confirm the Orange Pi Zero 3 image DOES technically work on the Zero 2W, however I can't get GPIO serial to work. I'm trying to use the Zero 2W as an Octoprint board in my Prusa, and can't get it working on any of the 5 GPIO serial connections. No issue with DietPi-Software or any of the typical usage stuff, but for the life of me I can't get communication working. |
Some someone else test/verify this: https://dietpi.com/forum/t/manually-install-wifi-package-or-firmware-file/13182/21?u=michaing
|
Reckon I can give this a test this week. Do you have any example tests / commands I can use to verify? I'm not experienced with testing these things and don't currently have a bluetooth use-case, I'm just a user who just happens to own the hardware and have some time to chip in. |
I installed the Orange Pi Zero 3 image on my Zero 2W and when running i2c-detect over the ports (should be i2c-1 on zero 2w so im checking i2c-3 on the zero3) my device isn't connected. I have went ahead and checked all other ports (0 and 1 are present when checking Also, when modifying |
I have the same issue, I ran Michael command as recommended, and after reboot i can no longer ssh into the device. As mentioned the zero2w dtb files does not exist in the dtb directory Since this device uses the same chip as zero3 , it would be nice to have a universal image for it |
Orange Pi supplies a Debian image here. Im going to install that and then install DietPi using these docs. Hopefully, that works better. |
I think the issue with a universal issue is that they have different IOs and bus-to-pin layouts. I'm not super knowledgeable on the DietPi system though, so I may be wrong here. |
Without a matching device tree, most hardware features won't work, simple as that. And indeed, the latest kernel build does not contain a Zero 2W device tree anymore: Not sure why it was present in the first place. Mainline Linux 6.6 does not contain it either: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/allwinner?h=linux-6.6.y There is already a draft at Armbian to add support based on this DTB: armbian/build#6451 Allwinner edge kernel builds with Armbian are still Linux 6.7, otherwise we would not need to wait for the PR: https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi64_common.inc I just started builds based on this PR: |
Is there is an Image I can test with? I don't see any artifacts under those builds unless I'm just blind lol. |
There is no image yet. |
These were kernel and bootloader builds. I triggered an image build here: https://github.com/MichaIng/DietPi/actions/runs/8491738902/job/23264002541 It can be found here once done: https://dietpi.com/downloads/images/testing/ |
Thank you, I will test that out after its done and report back |
Btw, the SBC has no GPIO header exposed by default, but it can be soldered onto the PCB to be usable? I.e. does it make sense to enable a UART console by default, and e.g. expose the SPI toggle we added for Orange Pi Zero 3? Or does it support USB UART on one of the USB ports in OTG/gadget mode? |
Not sure about the latter part but yes, it includes a 2x20 header set that I had to solder on the SBC. I think UART console should be left the same as the OPI Zero3 because people are already prompted to disable it if they aren't using it. I also thing its supported over USB but regardless, prob just leave it on. |
Yes, I forgot to move the bootloader package in place. It is rerunning. Okay, I'll enable |
Hi @MichaIng, I'm fighting with OPi Zero 2w and migration from the original OrangePi firmware. Unfortunately, I can't make BT running:
Once started (somehow):
I tried Does BT work for Zero 2W today? EDIT: Turning it on/off also ends up with segfault:
|
So this module seems to have the same as Strange is, that the command and line which throws the segmentation fault of your last log is not loading modprobe bluetooth
modprobe bnep
modprobe btbcm
modprobe rfcomm
modprobe hidp
modprobe hci_uart This is from old times, and I actually don't think that any of this is still required, but modules are usually loaded on demand, in all cases but this particular ls /etc/modules-load.d/dietpi-enable_bluetooth.conf Has this file been created in your case, or was the script aborted at the segmentation faul? If the file does not exist, please create it: echo 'sprdbt_tty' > /etc/modules-load.d/dietpi-enable_bluetooth.conf Then reboot and see whether the Bluetooth service does now start up: journalctl -u bluetooth |
I applied the following workaround to make it working:
Do you know why |
Ah right, I remember some Orange Pi's require this HCI-UART attach blob. Generally some SBCs have Bluetooth internally attached to one of the UART devices. Same on RPi, the Same is true for Orange Pi 3B, and I guess for Zero 3 as well then. I'll implement this for all 3 of them. Is the
|
Hey, I moved forward and stopped at configuring i2s on OPi Zero 2w. Let me cross-post the issue here:
Has anyone successfully connected the sound card using regular pins? |
Like so many other things, it works when using the Zero 3 device tree (assuming that your HAT/DAC uses the same native analogue audio form GPIO pins) 😄: https://dietpi.com/forum/t/no-sound-card-detected-for-opi-zero-2w/20133 Not sure why, but the Zero 2W device tree seems to be a mess. While the Zero 3 one just worked OOTB, with just minor GPIO related limitations, the Zero 2W one hat a lot of issues, and obviously, not all of them have been solved yet. If anyone has enough experience and time+mood, it could make a lot of sense to rebuild that device tree, using the Zero 3 ones as basis. EDIT: Ah, not sure which kernel sources/builds you use, but here is the PR at Armbian, including DTS patch, which enabled this support for H616/H618 chips, just not functional with the Zero 2W device tree they and us use: armbian/build#6694 |
Yeah, I saw this post or rather the idea, but I'm not sure how to sort out my case:
I'm on:
|
With this commit, there was no overlay needed anymore, as said, it worked just OOTB (as far as I understood, and since I gave instructions to remove the overlay). As far as I understood, this HAT uses an onboard sound chip, just exposed via GPIO pins.
Ah okay, then things are likely different. The Armbian kernel provides overlays to enable I2C 0-4: Hence requires an |
Thanks for bringing this up. Actually, I need i2s not i2c :) |
Ah right sorry, of course I2S, which is also why the guy from the forum tried an own overlay he found online. |
Hello mtojek and Micha What i know is that the i2s0 is reserved for HDMI on the main board and the expansion board use direct output from the H618 on pin G19 and G20 via the 24 pin connector for the jack connector like you mtojek i want to use i2s for a pcm5102 via the 40 pin HAT connector Have you try to write your overlay with the i2s3 map cordialy |
I'm afraid that there is an issue with 6.6 kernel. I managed to get i2s0 working for orangepi-xunlong image with 6.1 kernel using this dts. My hunch is that dts is correctish.. but the driver may not be stable. |
This would be very good news because the pins of the i2s0 correspond to the same pin as the rpi hat and I have several compatible dac hat to test, I would like your image to test just in the back of the dts file the mention of hdmi "off" |
AFAIR some pins i2s0 are in conflict with HDMI |
Hi I try after work, just a question, when you tested it under orangepi image, have you the image via HDMI, and sound via i2s hat pin ? |
Maybe an off-topic question, but is there a complete map of the current GPIO pinout of the OPi Zero 2W that works correctly? |
hello mtojek It works with a modified dtb file With this dtb also the wifi and ethernet via official expansion board I test it with Dietpi, LMS, Squeezelite and a PCM5102a Hope it helps |
That sounds great. Could you create a diff to the DTS we currently ship, at best even open a PR to adjust the patch which adds this DTS? |
Hello Micha
If the global dts file it's ok for you i can easely make a diff i think |
Hello Micha I'm back home of holiday tomorrow , i took a look to fork the build repository at home I fail to do that for now in my holiday's place I have this message "fetch-pack: unexpected disconnect while reading sideband packet" I tell you |
Hello Micha and others I go further in the tree of the opi zero 2w, it's work perfectly with a dac like PCM5102a with the i2s0 patch But for a dac like PCM5122 or a toslink output with WM8804 we need to activate the i2c0 or i2c1 capabilities Y try with -fdtoverlay --input zero2w.dtb --output zero2w-essai3.dtb i2c1-pi.dtbo : don't work too with an error message The fdtoverlay works with the official dtb and dtbo of the orangepi os but this dtb doesn't work with dietpi Many question i know, excuse me If someone have an idea it's be helpfull |
I came to a similar conclusion, and I would look into kernel changes between these versions. |
Hello mtojek Reflexion frommy running this morning In the dtb file i see "" compatible = "xunlong,orangepi-zero2w\0allwinner,sun50i-h618"; "" and in the dtbo file "" compatible = "allwinner,sun50i-h616"; "" perhaps this is the problem i try tonight and tell you |
I'm running an Orange Pi Zero 2W 1GB, and the image (downloaded from the website on July 29th), keeps showing 2GB RAM. Is there any way I can fix this? |
There was an update to armbian-firmware available that I didn't notice. That seems to have fixed it. |
I was wrong.
It now shows 1GB RAM sometimes, and 2GB other times after booting. Seems to be completely random. |
Creating an image request
Formal device information
Is the SBC officially supported by the Debian installer?
If not, is a reliable 3rd party Debian image available for this SBC?
If not, are there install instructions for Debian available?
I see previous issues that requested an Orange Pi image had been closed. If this is still the case, feel free to close this issue 🙇
The text was updated successfully, but these errors were encountered: