Jump to content
  • 0

Orange pi 4


Jack953
 Share

Question

Recommended Posts

Armbian Linux community supported weekly builds download

  • 0
On 3/15/2020 at 10:44 PM, gounthar said:

Thanks for the tip, but this was a new SDCard.

 

How do you put the image on the card? And how do you format the SD card before? I format it on Linux Mint as FAT32 and then write it. But that could be also great with Belena Etcher. And do you have the Orange Pi 4 with eMMC or without?

 

I think with the eMMC because you say it boots the onboard Android. Flashing to eMMC is described in this manual. https://drive.google.com/file/d/1wko5XfiFaw8qpB2uKXpdIYjiwlVFq4QG/view?usp=sharing

Link to comment
Share on other sites

  • 0
On 3/17/2020 at 3:51 PM, martinayotte said:

You don't need to format any SDCard before writing an image ... The image is providing the formatting ...

 

Strange enough do i got troubles when i format it before in EXT3 of EXT4 and write the image. When i format it before as FAT32 it works ok.

Link to comment
Share on other sites

  • 0

Hi, everybody.

What kind of Wiring library can I use on this board? I want to use it to connect to GPIO.

I plan to connect the fan control for cooling at high temperature.

On the Orange Pi, I used WiringOP, but this is a different chip.

 

Now I have installed Armbian_20 .02.5_Orangepi4_buster_current_5.4.26_desktop on the Board. It works relatively stable. The image on the monitor is via HDMI, the sound is via USB DAC PCM2704C.

 

 

IMG_20200321_135337.thumb.jpg.9e3edb709e2dad917c926bb857ee28f9.jpg

Link to comment
Share on other sites

  • 0

 

Today, wireless Internet access is permanently disabled.

OS: Armbian 20.02.5 Orangepi4 buster current 5.4.26

~$ uname -a
Linux orangepi4 5.4.26-rockchip64 #20.02.5 SMP PREEMPT Thu Mar 19 21:39:46 CET 2020 aarch64 GNU/Linux

dmesg:

Spoiler


[ 3344.000640] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
[ 3348.079896] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3348.083190] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3348.083317] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3350.640180] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3350.643458] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3350.643586] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3350.643607] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 3353.200383] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3353.203683] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3353.203831] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3355.760704] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3355.764085] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3355.764264] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3355.764285] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 3358.320962] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3358.324334] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3358.324511] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3360.881233] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3360.884612] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3360.884789] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3360.884810] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 3363.441523] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3363.444907] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3363.445086] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3366.001786] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3366.005097] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3366.005226] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3366.005246] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 3368.562040] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3368.565311] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3368.565438] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3371.122304] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3371.125582] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3371.125709] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3371.125730] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 3373.682567] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 3373.685740] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 3373.685814] brcmfmac: dongle trap info: type 0x4 @ epc 0x001aba9a
                 cpsr 0x6000019f spsr 0x600001bf sp 0x0025ff18
                 lr   0x001aba97 pc   0x001aba9a offset 0x25fec0
                 r0   0x0000002e r1   0x18000300 r2 0x00000001 r3 0x00000000
                 r4   0x00259e20 r5   0x7bff21c0 r6 0x001987c4 r7 0x0025ffe8
[ 3376.242887] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 3376.242905] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 3378.803141] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 3381.363406] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 3381.363424] ieee80211 phy0: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 3383.923682] ieee80211 phy0: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 3386.483958] ieee80211 phy0: brcmf_proto_bcdc_

 

 

Only this helps:

sudo rmmod brcmfmac
sudo insmod /lib/modules/5.4.26-rockchip64/kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko

How can I fix it?

I noticed another error when loading the brcmfmac driver:

brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.rockchip,rk3399.txt failed with error -2

I had to create a symbolic link in /lib/firmware/brcm. 

This error disappeared. But WiFi is still unstable.

Link to comment
Share on other sites

  • 0

I built the Far Manager (Linux port of FAR v2) deb package for аarch64.

 

Spoiler

Far2l.thumb.png.a9bc051c5684a605701cf52915ed0d65.png

 

far2l defaults to run as GUI app based on wxWidgets toolkit. You can run far2lс to get console support.

 

Installation with dependencies:

sudo apt install ./far2l_arm64.deb

Or:

sudo dpkg -i far2l_arm64.deb
sudo apt-get install -f

Depends:

libglib2.0-dev, libwxgtk3.0-dev, libgtkmm-3.0-dev, uuid-dev, libssl-dev, libsecret-1-dev, sshfs, gvfs-libs, gvfs-backends, gvfs-fuse, libssh-dev, libsmbclient-dev, libnfs-dev

Far2l sources.

 

far2l_arm64.deb

Link to comment
Share on other sites

  • 0
20 hours ago, martinayotte said:

In my case, I got it working by disabling NetworkManager and used the "old school" /etc/network/interfaces.

 

The driver crashes. It works for a while, and then it falls down again.

:~$ dmesg
[ 1485.667595] ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed

And again have to lift it manually:

# rmmod brcmfmac
# insmod /lib/modules/5.4.26-rockchip64/kernel/drivers/net/wireless/broadcom/brcm80211/brcmfmac/brcmfmac.ko

 

Link to comment
Share on other sites

  • 0

 

Again I and again with a problem. This time with GPIO.  I have this in /boot/armbianEnv.txt:

overlays=w1-gpio

When I boot the board, I see this in dmesg:

:~$ dmesg | grep gpio
[   72.674888] rk808-regulator rk808-regulator: there is no dvs0 gpio
[   72.676163] rk808-regulator rk808-regulator: there is no dvs1 gpio
[   73.755528] input: gpio-keys as /devices/platform/gpio-keys/input/input2
[   75.240702] gpiod_get_value: invalid GPIO (errorpointer)
[   75.240706] gpiod_set_raw_value: invalid GPIO (errorpointer)
[   75.262584] gpio-36 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file
[   75.262603] OF: /onewire@0: could not get #gpio-cells for /pinctrl/pcfg-pull-up
[   75.262607] w1-gpio onewire@0: gpio_request_one (ext_pullup_enable_pin) failed
[   75.262617] w1-gpio: probe of onewire@0 failed with error -22
~$ uname -a
Linux orangepi4 5.4.26-rockchip64 #20.02.5 SMP PREEMPT Thu Mar 19 21:39:46 CET 2020 aarch64 GNU/Linux

 

Any ideas?  I'm using the rockchip-w1-gpio.dtbo that was installed with the system.

 

 

armbian-hardware-monitor.log

Link to comment
Share on other sites

  • 0

Tried the latest buster desktop image from download area and it takes ~90 secs to boot (boot time will be shorter with the next release) but it works on my OrangePi 4B unit:

root@orangepi4:~# uname -a
Linux orangepi4 5.4.26-rockchip64 #20.02.5 SMP PREEMPT Thu Mar 19 21:39:46 CET 2020 aarch64 GNU/Linux

 

54 minutes ago, martinayotte said:

Change verbosity=7 in /boot/armbianEnv.txt and redo a capture of the serial log ...

I am more and more inclined to change the default to be 7 and let people lower it at will ;-)

Link to comment
Share on other sites

  • 0

So initially I had some trouble booting the Armbian images even the one I built locally.
I'm certain this was because I had not properly wiped the MicroSD card after trying out the images from Orange Pi (I ended up using gparted to create an new msdos partition table) .
Anyway I got around to testing some of the images and though I'd post the state of those as well:

 

1. Armbian_19.11.9_Orangepi4_buster_current_5.4.16_minimal.img
This was the image found here on Page 3 posted by @piter75
It seemed to boot fine. eth0 and WLAN exist but I did not get connectivity (this was an issue with my router)
https://asciinema.org/a/313413

2. Armbian_20.02.6_Orangepi4_bionic_current_5.4.27_minimal.img
Downloaded from https://www.armbian.com/orange-pi-4/#kernels-archive-all
Some issues seen during booting, but eventually it boots.
eth0 and WLAN exist but I did not get connectivity due to my router
https://asciinema.org/a/313424

3. Armbian_20.05.0-trunk_Orangepi4_bionic_current_5.4.27_minimal.img
Image built locally using the docker guide.
Kernel seems to take a bit longer to boot and there is no output from it as before.
eth0 and WLAN exist, after messing with router eth0 works as expected.
https://asciinema.org/a/313427
Image available at https://mega.nz/#!jgZmzAzb!yp-g2viNrXAjO-rpM_25meDVBNSxOo2I8gOqD6t-p7g

4. Armbian_20.05.0-trunk_Orangepi4_bionic_dev_5.5.13_minimal.img
Image built locally using the docker guide.
Kernel seems to take a bit longer to boot and there is no output from it as before.
eth0 and WLAN exist, after messing with router eth0 works as expected.
https://asciinema.org/a/313445
Image available at https://mega.nz/#!LpIinS5I!MzscJ_tS5S4_5pcxpz5CZXKUeFxf3LdeE8IBIfORl-A


All images flashed with Etcher
MicroSD was Samsung Evo Select 64GB
Board was OrangePi 4 4GB v1.3 without eMMC (cheapest config for this RAM)
PSU was the USB barrel connector to a known good phone charger.

 

I also tried out the mPCIe adapter with a mPCIe SATA card (ASM1061). The speeds were disappointing at max 210mb/s considering the card can definitely do 350mb/s+ in my laptop.

I had hoped the newest os/kernel version would solve this, but it does not appear to do so. Maybe my testing methodology is wrong but I am doubting this after trying 2 different cards and multiple OSs.

Another thing to note is that this board runs hot at ~75*C even with a small heatsink (no fan was used) and little going on.

 

If anyone has something they'd like me to try then please ask.

Edited by magixx256
Link to comment
Share on other sites

  • 0
2 hours ago, magixx256 said:

Anyway I got around to testing some of the images and though I'd post the state of those as well:

Nice summary ;-)

 

IMHO all versions tested by you boot in similar time - somewhere around 1:45 you get the prompt. They are all equipped with the patch that sets the CPU clock properly in u-boot - otherwise it would take at least 40-60 secs longer.

Most of that time is taken to resize the filesystem on the SD card. In first two you can see that root fs is mounted ~6-7 seconds into the kernel boot.

Subsequent boots should be faster but without RTC (I think there is no port for it) it will also take some time to fsck the rootfs because of "superblock write time in the future" check ;-)

Link to comment
Share on other sites

  • 0

Some strange behaviour of the ethernet port

 

Just for  information: I got an Orange PI4 and it run very unstable (kernel panics, even more oops (spinlock, ...)  - I tried various images (including an "official" ubuntu from the orange Pi - site), all the same problem.

 

I also noticed that the ethernet port was unstable - some (not all) kernel messages were related to problems with the ethernet port.

 

I trried various power supply (5V 8A in parallel to OPi Plus 2; 5V 2,5A and 5V 4A) and two different SD cards (that I know to be reliable with OPi Plus 2) - the effect was always the same: Kernel crashes after some minutes.

 

The OPi 4 was connected to a 100 MBit Switch (some simple TP-Link 8 Port 100MBit switch).

Then I also tried to fix the ethernet speed to 100Mbit (100baseTx-FD) with `mii-tool` and this seemed to be  more stable. However, the network connection failed after a while and also the system crashed once.

 

Today I got a new Gigabit-Switch - and everything seems fine now  (negotiated 1000baseT-F): The OPi run an hour with the "original" image and since then (5 hours now) with Armbian Bionic minimal 5.4 kernel (`Linux IA216_OPI4 5.4.27-rockchip64 #20.02.6 SMP PREEMPT Tue Mar 24 23:43:02 CET 2020 aarch64 aarch64 aarch64 GNU/Linux`)

 

 

Did anybody else noted this somehow weird problem with the ethernet chip?

 

Link to comment
Share on other sites

  • 0

@IanHI am connected wireless (only), due to lacking ethernet in the living room. I still get some crashes on ethernet in dmesg.

I am running:

uname -a Linux orangepi4 4.4.213-rk3399 #15 SMP Thu Mar 19 21:33:44 CET 2020 aarch64 GNU/Linux
(Armbian_20.02.5_Orangepi4_buster_legacy_4.4.213)

 

I wonder if anyone knows how to get the Gyrfalcon Lightspeeur 2801S running in armbian?
Also want to make the RPI monitor look nice, including core voltages, does anyone knows which voltage regulators go where?
I found four regulators with suspected cpu voltages, but have no clue on how they are connected

/sys/devices/platform/vdd-log/regulator/regulator.8/microvolts

/sys/devices/platform/ff3c0000.i2c/i2c-0/0-001b/regulator/regulator.9/microvolts

/sys/devices/platform/ff3c0000.i2c/i2c-0/0-001b/regulator/regulator.10/microvolts

/sys/devices/platform/ff3c0000.i2c/i2c-0/0-0041/regulator/regulator.24/microvolts

opi4.png

Link to comment
Share on other sites

  • 0

hi guys,

 

i m on opi4 with armbian 20.02.6 buster image , upgraded with desktop thru armbian-config. mostly everything s fine but sounds. obviously it works in the board, vu meters are active etc but nothing is coming out , from any outputs ( jack n hdmi ). i m pretty sure that my speakers wires etc are working fine , i ve already had sound with my opi with official orange pi 4 images. can someone provide me some help , i ve tried hard to resolve this by myself but ain't succeed, seems that google it doesn't provide many information to work on..

 

 

someone have any idea on this ? tx

 

ps : i m beginner and not used to go on this forum , don't hesitate to tell me how to ask , if i m no respecting rules etc

Link to comment
Share on other sites

  • 0

may be it will help i havent asound.conf in /etc/ , i have several sound card installed or detected ( correct me if necessary ) 0 : dummy   1: loopback  2: realtek 5651co with armbian 20.02.06 , if i stay on sound , default sink, a file appears and i can see that the 3 built- in are " state : suspended"

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...