Armbian Download Orange Pi One
Bethany Pensis
Download Orange Pi OS Ubuntu or Debian from their website -and-support/Orange-pi-5.html unzip the 7z file to get the .img file and flash it to your sd card with your preferred flasher i.e balenaetcher. Once flashed put it into orange pi 5 and boot from sd card first
7. Put the same Orange Pi OS image you used in step 1 in any directory on your orange pi making sure it is unzipped and is in .img format. I just used the web browser in orange pi os to redownload from the website which for me put it in directory /home/orangepi/Downloads
Try to format the disk so you've got 1 ext4 partition and install with armbian-install. Choose no when it asks if you want to install/update the bootloader to MTD. Check if you've got the overlay sata in /boot/dtb/rockchip/overlay
Since the armbian image updates require re-installation I have created a set of Ansible roles that can do what the guide describes in steps 3 to 5. I used ubuntu-desktop-minimal to avoid installing libre office etc.
Last update, I got it to work, so here are a few pointers for the next one reading this. The issue is that I edited armbianEnv.txt correctly, but somehow the dtb file was missing (most likely due to being merged with the one in use, despite this work being WIP and not working for the emmc/wifi). I read a little about dts/dtb, this is a good resource, but TLDR dts stands for device tree source and dtb for device tree blob. The former compiles into the latter, and armbianEnv.txt wants the blob, not the source (could compile on demand? who am I to judge). The dts for the 5b is somewhere out there to be compiled into the dtb, but since I knew I had the orangePI debian working, I searched for the dtb there first, and found it. I copied is over to a freshly compiled image, pointed the boot record to it, and was able to make it all work. Here are a few commands.
I use win10 to copy the "rockchip/rk3588s-orangepi-5b.dts" which copy from orange pi official image to F:\[/boot]\dtb\rockchip\ and F:\dtb-5.10.110-rockchip-rk3588\rockchip two directories. After .dts copied, I modified armbianEnv.txt with royk sir's comment.
I was pointed to this as a fix for the 5b's wifi not working.
What I have tried worked on debian but is not working on armbian. And I prefer to use Armbian because I find it superior in every other way.
The thing I tried that made it work in debian but not armbian is to copy the dtbo file for the ap6275p wifi module into the overlays directory in boot. Then add a line in the armbianenv.txt file that reads "overlays=wifi-ap6275p". I see how that file removes the prefix on the file name. Original filename was rk3588-wifi-ap6275p.dtbo and it was located in boot directory of the debian install I tried. I copied it to boot/rockchip/overlays and renamed it to rockchip-rk3588-wifi-ap6275p.dtbo then added the overlays line to the env.txt. After reboot nothing happens. BUT this exact procedure made it work on Debian.
So now here I am wondering what to do. Was pointed here. Will further modification from the procedures discussed here help me? Because I am lost at this point.
For anyone else here's what worked for me.
1. Download latest armbian image from here
-5/
2. Follow the instructions at the youtube video below to install the image to EMMC. Ensure you use the armbian image. This image won't load as mentioned above
3. Burn the same image to sdcard and install sdcard in pi 5b. I used Rufus on Win11 ( )
4. Boot up. SD card boots as default
5. Edit the armbianEnv.txt file in the /boot folder and replace the line:
I have the same issue on the OPi Zero 3. I used the Armbian image in the leeboy/armbian repository and followed the instructions on updating the dtb and bin file for the 4gig variant and it works. however WIFI does not and I can't connect at all. I see that there was an issue that was fixed earlier this week regarding the Orange Pi Wifi drivers and xradio not working. I think if someone was to pull the latest armbian and build the kernel it might work (I'm very new to all this, otherwise I would!).
Oh, I hadn't realized it was so closely related to the Orange Pi 2G-IOT. Out of curiosity I'll take a look at that, but since it may not make it to an armbian supported board my interest may fade quickly. I like my armbian systems. :-)
I have an orangepi i96 (without the 2G). In theory, it would be a great board that performs some task (GPIO), connects with wifi, uses commodity accessories (USB power, serial) and is very cost effective at that (is it?).
If it's not difficult, could you tell me how to install the server properly. Where to get an image. Maybe there is somewhere a full "how to" wiki for this case. I read the classic guide how to install OMV on SBC, it says install via armbian...Closed circle.
While in theory writing to NAND should still be possible using armbian-installer, this requires running a very old 3.4.y kernel which Armbian as dropped support for several years ago. Therefore this feature is to be considered as deprecated and no support for either 3.4.y systems or NAND installations will be provided.
Not sure how many people would be interested in mycroft on an armbian OS without desktop - I find armbian works well and you can get very really powerful pi devices that blow rpi3 out of the water on specs for 1/2 the price
I do everything according to the instructions, put wiringOP, go to armbian-config, turn on spi-spidev1 and for some reason CE.1 pin is in the OFF state, not ALT2 like all other spi pins. Please help, I changed the system several times, tried different versions, so far without successenter image description here
so i recently bought a orange pi zero 3 and tried nearly every supported firmware around h618 but it is not working i try to ping it and nothing happens i try to ssh into it but it says connection timed out
Orange pi 3 is not as popular as raspberry sbc , online report of testing of those in a daw context is sparse if not nonexisting...
Bare with me,i am not a coder, not a pro musician ,but a long time linux user ,arm is a new toy..
note; here red text = [s]strikethrough text[/s] which do not work here....... so , its autumn all year ....
-Orange pi 3 2gb ram 8gb emmc
-hdmi to tv.
-Tested Armbian_22.11.0-trunk_Orangepi3_kinetic_edge_6.0.5_xfce_desktop.img
-Armbian_22.08.2_Orangepi3-lts_jammy_current_5.15.69_xfce_desktop.img
-from armbian-config,
Update kernel to 5.19.??6.06
Removed Libreoffice,Gimp,firefox-esr,transmission , space is needed.
-no compiling at all
-Apt-get install muse (4.1) ,yoshimi (?latest)
-install 2 of x42-plugins(from arm64 binary)
-avl drum ,ok ,setbfree,ok. Those got fancy gui for a not so fancy guy, xfce too when used to jwm...
-EDIT- 29-09-22;
-apt-get install python3-pyqt5,for muse midi script
-audio recording works here with Beringher uma25s usb audio input with pulseaudio ootb,but lag.less a little on kinetic
-i have not yet manage audio recording with jack...
-midi is more responsive using jack then pulseaudio.
-EDIT- 29-10-22;
-install from repo pipewire-pulse ,now i can record from uma25s usb audio,
-got to retest if pipewire-pulse is the solution in kinetic and pulseaudio/midi or alsa/ pulseaudio/midi?? is as much responsive as jack .
(a lot of armbian packages for this sbc do throw a a problem occur,report or not with details but still work,)
-hdmi audio,here with pulseaudio and jack.
-muse, sequencing with lv2 plugin
-very reasonnable cpu usage
edit at 6 instances(parts) of yoshimi + effects+avl drum i do get xrun,
i should maybe use a bigger heatsink on the orange pi 3...at least there is one.
Got my hand on Orange pi 4 /rk3399 first gen.
this sbc is way more decent for the job.
armbian_22.11.0-trunk_Orangepi4_kinetic_edge_6.0.8.img
I can confirm ,this kinetic img now come with pipewire installed ,still got to install pipewire-pulse,wireplumber(replacing session one),pipewire-jack(muse/latency is almost as as good for both,jack or pulseaudio with pipewire) .
I wont start a topic on Opi4 .
If you did not assign a static IP address via a DHPC reservation on yourrouter in step 4, you should configure your Pi for a static IP address now. Youcan do so by running sudo armbian-config and entering Network settings, asshown below.
I am trying to setup the ADXL345 on my orange pi lite 2 (arm64) on which Klipper is running and would need help with the settings since all the examples are related to an external RPI/MCU but could not figure out how I would define the connection/pins to the local ADXL345 connected over the CON12 connector SPI pins.
Did you ever get this sorted as I have it running on a OrangePi 4 running armbian, followed by klipper installation via KIAUH installer.
I did go through downloading several libraries to trick the software into thinking it was running on a Rpi,( WiringPi and OPi.GPIO, but they didnt help).
The missing piece was SPI-DEV , heres a useful installation Guide for armbian :- Orange Pi I2C & SPI Setup (Orange Pi I2C & SPI Setup neonaut)
Klipper on orangepi 4 using Kiauh, documentation of changes needed . work in progress - GitHub - benjjyman/klipper-orangepi4-Kiauh: Klipper on orangepi 4 using Kiauh, documentation of changes neede...
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes
Change the "PermitRootLogin yes" to "PermitRootLogin no"
Save this by hitting "ctr+x", Y(es) and hit enter (don't change the name of the file!)
Restart SSH by typing:
"sudo service ssh restart"
Log off, and try to login with "root", if you changed this correctly it wil give you a error now.
"Access denied".
Login with your 2nd account now, in my case it's "orangepi" and you're done!