Search the Community

Hello everyone! I will teach you how to install WiringOP on Armbian. It's not the most practical method, but it works. First, we download the repository from the original website. $ apt-get update $ apt-get install -y git $ git clone https://github.com/orangepi-xunlong/wiringOP.git Then, we proceed to look for the name of our board that is associated with Armbian. $ cat /etc/armbian-release | grep "BOARD=" | awk -F'=' '{print $2}' The previous command will give us the name of the board, which is the following: root@armbian:~# cat /etc/armbian-release | grep "BOARD=" | awk -F'=' '{print $2}' orangepi-r1plus-lts Now, we proceed to go to the WiringOP folder downloaded from Git, and we will modify the "build" file by adding the name of the board in 2 sections. $ sudo nano wiringOP/build Inside the "build" file, we will look for the following variable: boards=("orangepir1" "orangepizero" "orangepizero-lts" "orangepipc" "orangepipch5" "orangepipcplus" "orangepiplus2e" "orangepione" "orangepioneh5" "orangepilite" "orangepiplus" "orangepizeroplus2h3" "orangepizeroplus" "orangepipc2" "orangepiprime" "orangepizeroplus2h5" "orangepiwin" "orangepiwinplus" "orangepi3" "orangepi3-lts" "orangepilite2" "orangepioneplus" "orangepi4" "orangepi4-lts" "orangepirk3399" "orangepi800" "orangepizero2" "orangepizero2-lts" "orangepizero2-b" "orangepizero3" "orangepir1plus-lts" "orangepir1plus"} At the end of this variable, we add the board ID that we obtained before. It will look like this after adding the board ID: boards=("orangepir1" "orangepizero" "orangepizero-lts" "orangepipc" "orangepipch5" "orangepipcplus" "orangepiplus2e" "orangepione" "orangepioneh5" "orangepilite" "orangepiplus" "orangepizeroplus2h3" "orangepizeroplus" "orangepipc2" "orangepiprime" "orangepizeroplus2h5" "orangepiwin" "orangepiwinplus" "orangepi3" "orangepi3-lts" "orangepilite2" "orangepioneplus" "orangepi4" "orangepi4-lts" "orangepirk3399" "orangepi800" "orangepizero2" "orangepizero2-lts" "orangepizero2-b" "orangepizero3" "orangepir1plus-lts" "orangepir1plus" "orangepi-r1plus-lts") #<- Here, the board ID was added. Now, further down in the "Build" file, we will look for the following: if [[ -f /etc/orangepi-release ]]; then source /etc/orangepi-release elif [[ -f /etc/armbian-release ]]; then source /etc/armbian-release [[ $BOARD == orangepi-r1 ]] && BOARD=orangepir1 [[ $BOARD == orangepi-rk3399 ]] && BOARD=orangepirk3399 [[ $BOARD == orangepizeroplus2-h3 ]] && BOARD=orangepizeroplus2h3 [[ $BOARD == orangepizeroplus2-h5 ]] && BOARD=orangepizeroplus2h5 #----->Here new board<--------------- else In the brand section of the code above, we will place the following code. Replace [board_id_goes_here] with the actual board ID that we obtained at the beginning of the tutorial. [[board_id_goes_here]] && BOARD=orangepir1plus-rk3328 After making the modifications, it will look like this: if [[ -f /etc/orangepi-release ]]; then source /etc/orangepi-release elif [[ -f /etc/armbian-release ]]; then source /etc/armbian-release [[ $BOARD == orangepi-r1 ]] && BOARD=orangepir1 [[ $BOARD == orangepi-rk3399 ]] && BOARD=orangepirk3399 [[ $BOARD == orangepizeroplus2-h3 ]] && BOARD=orangepizeroplus2h3 [[ $BOARD == orangepizeroplus2-h5 ]] && BOARD=orangepizeroplus2h5 [[ $BOARD == orangepi-r1plus-lts ]] && BOARD=orangepir1plus-rk3328 else The last parameter can be modified with a different board, in case of using other versions of OrangePi. You just need to look for the corresponding one in the same "build" file, and replace only the board ID. Now we can close the file and proceed to apply ./build clean and ./build. However, the current version of OrangePi r1+LTS officially has a problem that we will also fix next. $ sudo nano wiringOP/wiringPi/OrangePi.h Inside the file, some #define statements need to be added to resolve the conflicts they are causing. Hopefully, Xunlong will fix this issue in the future. For now, we will apply a patch as I haven't been able to find where to obtain these GPIO_BASE. Inside the file "Orangepi.h," we will look for the following //csy 2019.1.8 /*********** OrangePi R1PLUS *************/ #if CONFIG_ORANGEPI_R1PLUS #define GPIO2_BASE 0xff230000 #define GPIO3_BASE 0xff240000 #define GPIO_NUM (0x40) #define GPIO_SWPORTA_DR_OFFSET 0x00 #define GPIO_SWPORTA_DDR_OFFSET 0x04 #define GPIO_EXT_PORTA_OFFSET 0x50 #define GRF_BASE 0xff100000 #define GRF_GPIO2A_IOMUX_OFFSET 0x20 #define GRF_GPIO2BL_IOMUX_OFFSET 0x24 #define GRF_GPIO2BH_IOMUX_OFFSET 0x28 #define GRF_GPIO2CL_IOMUX_OFFSET 0x2c #define GRF_GPIO2CH_IOMUX_OFFSET 0x30 #define GRF_GPIO2D_IOMUX_OFFSET 0x34 #define GRF_GPIO3AL_IOMUX_OFFSET 0x38 #define GRF_GPIO3AH_IOMUX_OFFSET 0x3c #define GRF_GPIO3BL_IOMUX_OFFSET 0x40 #define GRF_GPIO3BH_IOMUX_OFFSET 0x44 #define GRF_GPIO3C_IOMUX_OFFSET 0x48 #define GRF_GPIO3D_IOMUX_OFFSET 0x4c We will modify this to make it look like the following: #endif /* CONFIG_ORANGEPI_RK3399 */ //csy 2019.1.8 /*********** OrangePi R1PLUS *************/ #if CONFIG_ORANGEPI_R1PLUS #define GPIO2_BASE 0xff230000 #define GPIO3_BASE 0xff240000 #define GPIO_NUM (0x40) #define GPIOL_BASE (0x0) #New lines added. #define GPIO_BASE_MAP (0x0) #New lines added. #define GPIO_SWPORTA_DR_OFFSET 0x00 #define GPIO_SWPORTA_DDR_OFFSET 0x04 #define GPIO_EXT_PORTA_OFFSET 0x50 #define GRF_BASE 0xff100000 #define GRF_GPIO2A_IOMUX_OFFSET 0x20 #define GRF_GPIO2BL_IOMUX_OFFSET 0x24 #define GRF_GPIO2BH_IOMUX_OFFSET 0x28 #define GRF_GPIO2CL_IOMUX_OFFSET 0x2c #define GRF_GPIO2CH_IOMUX_OFFSET 0x30 #define GRF_GPIO2D_IOMUX_OFFSET 0x34 #define GRF_GPIO3AL_IOMUX_OFFSET 0x38 #define GRF_GPIO3AH_IOMUX_OFFSET 0x3c #define GRF_GPIO3BL_IOMUX_OFFSET 0x40 #define GRF_GPIO3BH_IOMUX_OFFSET 0x44 #define GRF_GPIO3C_IOMUX_OFFSET 0x48 #define GRF_GPIO3D_IOMUX_OFFSET 0x4c #define CRU_BASE 0xff440000 #define CRU_CLKGATE_CON16_OFFSET 0x0240 //bit 7 8 9 10 9877 We save the changes and apply build clean and build. The result is: root@armbian:~/wiringOP# gpio readall +------+-----+----------+------+---+ R1 Plus +---+---+--+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | | | 5V | | | 1 || 2 | | | GND | | | | 89 | 0 | SDA.0 | ALT2 | 1 | 3 || 4 | 1 | ALT2 | SCK.0 | 1 | 88 | | 100 | 2 | TXD.1 | ALT5 | 1 | 5 || 6 | 1 | ALT5 | RXD.1 | 3 | 102 | | | | | | | 7 || 8 | | | | | | | | | | | | 9 || 10 | 1 | ALT3 | GPIO3_C0 | 4 | 112 | | 103 | 5 | CTS.1 | ALT5 | 1 | 11 || 12 | 1 | ALT5 | RTS.1 | 6 | 101 | | 66 | 7 | GPIO2_A2 | IN | 1 | 13 || 14 | | | | | | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+ R1 Plus +---+---+--+----------+-----+------+ root@armbian:~/wiringOP#

Hi, how can I check the serial number of the RK3328 chip? with the distro from orangepi I can use cat /sys/devices/platform/board/info and with ArmBian ? thanks

Hi everyone! I'm new to the armbian world (but not to linux in general). I have two Orange PI R1+ LTS. After the last update, if I try to execute another update, using apt update && apt upgrade I have the following result: The following packages have been kept back: linux-dtb-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-orangepi-r1plus-lts-current The systems are: Armbian 23.8.1 Bullseye with Linux 5.15.93-rockchip64 This happens after the last update, I've never had this issue before Thanks

Hello, I would like to know how they reduce the size of the images and then, when the microSD cards are inserted into a card, they expand to fill the entire space. In other words, the same thing that Armbian images do when we use them for the first time: they are small, and then they occupy all the storage space.

What gives with the Armbian website links? Links to all previous versions Armbian for the OrangePi R1 Plus LTS have been removed. The links to SHA hash and PGP signature do nothing. I was hoping to use an image that was based on Debian Bullseye, but that link has been recently removed. It is possible to create my image, but I would spend my time working on my code, not wading through the options to create an image.

I've installed pluseaudio, mpg123 and attached pin 7, 8 with pin 2 to an external speakers(left using pin 7 and right using pin 8). However, when running mpg123 test.mp3, the file was played successfully but no audio was heard. Any means of debugging what could have gone wrong?

Hello guys, you know that armbian has a problem that sometimes when the system boots, the ethernet interfaces fail. The led turns on indicating that it detected the interface but it is totally blocked. It does not work, no method of restarting the interface. The only solution is to restart the computer...

Hi guys, I need to be able to see the pins on my board. In the official distribution of Orange Pi, I was able to install the Xunlong WiringOP script. I know I can use /sys/class/gpio/ to define the pins and use them, but that's not what I want. I would like to be able to use something like the "gpio readall" command.

Hi guys, when I installed Armbian on my system, it gave me a different MAC address than the one physically assigned to my hardware. How can I restore the original MAC address of the hardware without having to manually set it?

I'm attempt to do two simple switches via GPIO on OrangePi R1 LTS Plus using RK3328 using .Net Core and here my code snippet. GpioController ioc = new GpioController(PinNumberingScheme.Logical, new RockchipDriver(gpioRegisterAddresses: new uint[] { 0xFF21_0000, 0xFF22_0000, 0xFF23_0000, 0xFF24_0000 })); int iPin=RockchipDriver.MapPinNumber(???) // where do I find the information to do logical pin number mapping? ioc.OpenPin(iPin); ioc.SetPinMode(iPin, PinMode.InputPullUp); PinValue v=ioc.Read(iPin); Thanks for reading and any suggestion is appreciated.

Hi guys, in my job they bought a orangepi r1+LTS. i trying install armbian any version (last Debian and Ubuntu) but this don’t work. When boot system nothing happens… the led red still off and port Ethernet freezing(two lights on). Already installed Debian and Ubuntu of the official page orangepi, and system working without problems im using good sd card and official charger of the raspberrypi 4 How to solve this problem? In internet I don’t found much information thank u for read me

Hi Guys, My Orange Pi Zero LTS H5 had a short circuit and no longer power up. worst that it seems that i cannot find any replacement for it as market is full of H2 & H3 variants but non is H5. Perhaps its time to upgrade Armbian & Hardware by inserting the SD card in one of the below boards: - Orange Pi Zero 2 1GB RAM with Allwinner H616 - Orange Pi R1 Plus LTS 1GB RAM RK3328 -Nanopi NEO3 Mini RK3328 (though not Orange pi but seems very similar) Though i'm not sure OS would boot on different CPU / board, (i remember doing such upgrade from h3 to 5h or zero 2 to lts) I would like to avoid re-building the OS with my programs and configurations. Would it be possible to make such upgrade? and what i will need to do in such case. Many thanks

Just started with creating custom images for an Orange Pi R1+ LTS board. In my build I'd like to compile some custom C++ applications using CMake, then install them onto the root file system to run on the board. Couldn't find much on this on the docs, though maybe I haven't looked hard enough! A couple of questions: I noticed the customize-image.sh script in the build repository - would amending this script be the intended method for this kind of functionality or is there another, better way? How would I provide CMake the relevant info to compile correctly for the board. Thanks in advance.

Hi ! Is there any chance to flash an armbian to the 16MB SPI Flash-Chip? regards, volker.

@Contributor/Maintainer AR-1172 - fix complete 08 May 2022 There is was a bug in the 5.15, 5.16 and 5.17 kernel r8152 driver that affected RTL8153b Gigabit USB Ethernet (LAN0) on the Orange Pi R1plus LTS and other boards. The bug only presents on high load and I can trigger it reliably with bidirectional high load on Orange Pi R1plus LTS. The bug kills the RX interface and it requires power down to reset. I assume that it also affects the Orange Pi R1plus, and there are reports of it affecting NanoPi R2S. I would assume that other boards could be impacted. My proposed fix is to revert the driver back to the version used in 5.10 kernel (and to disable TX offload by default). This driver works reasonably well if TX offload is disabled (but with TX offload enabled, another bug is triggered on load). The reason for this post is to alert other board maintainers and to inquire if you are okay with this proposal. The driver from kernel-5.10 (v2.15.0 (2021/04/15)) can be used with 5.15 and 5.16 with minor tweaks. Edit: While researching options for disabling TX ofload, I found a thread on the forums for Helios that talked about xhci trb quirk in rockchip64-current. I followed it to this commit, https://github.com/armbian/build/commit/8eece74eb581367625e6ebcc12ee5c6f4f44617c The quirk is currently funcional for dwc3 xhci usb on rockchip64 and activated for rk3399. It appears that the quirk may not have been applied to rk3328 in the past, so I tried including it in rk3328.dtsi, and it worked very well with the mainline driver on 5.15, 5.16 and 5.17. This means that it is not necessary to revert the driver to the one in 5.10. I have modified AR-1172 and submitted a PR. PR has been merged and fix will be in the new release.