Jump to content

Armbian for RK3399

balbes150

By balbes150
in General Chat

 Share

Recommended Posts

amirul

amirul

Posted
Posted
  On 6/29/2019 at 5:12 AM, amirul said:

Wlan works on Armbian_5.86_Rk3399-tv_Ubuntu_bionic_default_4.4.154_desktop_20190517. What has changed between the versions?

 

dtbs are identical

lots of lines in dmesg [WLAN_RFKILL]: wifi turn on power. -1

Expand  

replaced /lib/frmware/brcm in 5.88 from that in 5.86 -> wireless networks detected but can't connect yet

 

connected to wlan with gnome-keyring-daemon running :-)

fixed Armbian_5.89_Rk3399-tv_Ubuntu_bionic_default_4.4.154_desktop_20190627 as well

1
amirul

amirul

Posted
Posted
  On 7/1/2019 at 1:49 AM, amirul said:

replaced /lib/frmware/brcm in 5.88 from that in 5.86 -> wireless networks detected but can't connect yet

 

connected to wlan with gnome-keyring-daemon running :-)

fixed Armbian_5.89_Rk3399-tv_Ubuntu_bionic_default_4.4.154_desktop_20190627 as well

Expand  

After latest update of armbian-firmware, wlan works out of the box

amirul

amirul

Posted
Posted

Magicsee-n6-max Armbian_5.89_Rk3399-tv_Ubuntu_bionic_default_4.4.154_desktop_20190627

Bluetooth paired with my phone, played youtube on the phone -> n6 locked up requiring reboot. Now can't detect phone anymore. Think I'll turn off bluetooth, don't need it.

amirul

amirul

Posted
Posted

/var/log/syslog and dmesg has a whole bunch of these messages:

wl_run_escan: LEGACY_SCAN sync ID: nnn, bssidx: 0

where nnn incerments by one

 

Is this normal when wi-fi is enabled?

jeanrhum

jeanrhum

Posted
Posted

Hi,

I tested latest dev image (5.91 4.4.167) changing to edgev dtb and it seems to work well. Ethernet works but not wifi (as expected). The usb3 port works, but not the usb2 port (up to the usb-c charging port).

Here the output of armbianmonitor -u: http://ix.io/1Ofx

balbes150

balbes150

Posted
  • Author
Posted
  On 7/12/2019 at 12:38 PM, jeanrhum said:

I tested latest dev image (5.91 4.4.167) changing to edgev dtb and it seems to work well. Ethernet works but not wifi (as expected). The usb3 port works, but not the usb2 port (up to the usb-c charging port).

Here the output of armbianmonitor -u: http://ix.io/1Ofx

Expand  

For WIFi on the core 4 you need to install firmware.

What is the problem with USB 2 ?

jeanrhum

jeanrhum

Posted
Posted
  On 7/12/2019 at 1:32 PM, balbes150 said:

What is the problem with USB 2 ?

Expand  

I tested again and was able to use my keyboard and mouse with this port (the keyboard has an internal hub and the mouse is connected to it), but I have to first connect my keyboard and then connect my mouse otherwise it won't work (no light or blinking light on the mouse). I suppose that there is not enough current via this port for the initialization of all these devices at the same time (keyboard, usb hub and mouse) since I don't observe this behavior on the usb3 port.

 

I installed the full firmware package, but wifi is not activated. After looking at dmesg, I saw that the firmware files were not present. So I downloaded from a github repo fw_bcm4359c0_ag.bin, nvram_ap6398s.txt and BCM4359C0.hcd and copy them to /lib/firmware/brcm/. I am now able to use wlan0.

 

Here is the current dmesg output:

  Reveal hidden contents

 

balbes150

balbes150

Posted
  • Author
Posted
  On 7/12/2019 at 2:45 PM, jeanrhum said:

I installed the full firmware package, but wifi is not activated. After looking at dmesg, I saw that the firmware files were not present. So I downloaded from a github repo fw_bcm4359c0_ag.bin, nvram_ap6398s.txt and BCM4359C0.hcd and copy them to /lib/firmware/brcm/. I am now able to use wlan0.

Expand  

EDGE uses its own version of firmware (it is not in the official Linux packages).

amirul

amirul

Posted
Posted (edited)

1.7 & 2.2 is the upper limit perhaps

 

Screenshot_2019-09-11_14-37-47.png.3949181e89537aa6b43a87392394d408.png

...but it crashed after a while :-(

Edited by amirul
update
amirul

amirul

Posted
Posted

Wifi device not ready fix by copying from previous version fw_bcm4356a2_ag.bin & nvram_ap6356.txt into /lib/firmware/brcm

balbes150

balbes150

Posted
  • Author
Posted

The new version of the images for RK3399 5.96_20190920.

Added support for NanoPC T4.

Added items for priority use of big cores.

1
amirul

amirul

Posted
Posted
  On 9/20/2019 at 10:42 AM, balbes150 said:

The new version of the images for RK3399 5.96_20190920.

Added support for NanoPC T4.

Added items for priority use of big cores.

Expand  

Magicsee N6 Max stable with 

MIN_SPEED=600000
MAX_SPEED=2208000
GOVERNOR=interactive
for /etc/default/cpufrequtils

 

balbes150

balbes150

Posted
  • Author
Posted

Add image NEXT 5.98 kernel 5.4.0-rc2

 

By the way, when switching to the screen resolution in the settings on 1920x1080, I have sound working through HDMI. :)

balbes150

balbes150

Posted
  • Author
Posted
  On 10/7/2019 at 3:54 PM, amirul said:

I'll stick with the default, coz dev does not have magicsee dtb in them

Expand  

I checked the latest DEV and NEXT images on N6. The system starts and works with dtb rock-pi-4.  :)

Only need to wait 4-5 minutes until the system starts (a picture will appear on the screen).

 

By the way, I just checked, on N6 starts LE with 5 core, but you need to wait more than 5 minutes until the setup wizard starts. :)

 

1
balbes150

balbes150

Posted
  • Author
Posted

New version 20191011 of Armbian and Libreelec with support to run from USB media on RK3399. :)

 

It makes it easy to test different systems without using SD card, using normal USB flash drives. Tested on EDGE. How to use USB start-up. There are two ways to use. Test, for the overall evaluation of the launch with USB on new models of TV boxes or SBC. You need to write a new image to the SD card (if necessary, configure the correct dtb), check the system startup on the device from the SD card. If everything works from an SD card, you need to write a test image of another system to a USB drive. i.e. if on an Armbian SD card, you need to write LE to a  USB system (if necessary, configure the correct dtb) or Vice versa. This is due to the peculiarities of testing, in real use there will be no such restriction. Connect both the SD card and USB flash drive to the device and turn on the power. After a few minutes, the system should start with a USB flash drive. If the system starts from the SD card, you need to check the USB flash drive connection to all available USB ports on the device in turn and check the start. On EDGE, only the USB 2.0 ports are working for now. For those who have the option, it would be interesting to check the operation of the USB launcher on other devices with RK3399.

balbes150

balbes150

Posted
  • Author
Posted
  On 9/21/2019 at 2:39 PM, amirul said:

Magicsee N6 Max stable with 

Expand  

I checked the system startup from USB to N6, everything starts and works. :)

To start you need to use the USB port which is to the right of the microSD card.

 

 

On EDGE, I checked the installation of new Armbian and LE versions in eMMC (with USB startup support). Everything works. :) Now I have a stable version of LE in eMMC and I can quickly and easily check new versions of Armbian and LE using regular cheap USB flash drives. I no longer need to look for many different SD cards (and having a card reader on a PC to write to) to quickly test different systems. :)

amirul

amirul

Posted
Posted
  On 10/11/2019 at 11:22 AM, balbes150 said:

I checked the system startup from USB to N6, everything starts and works. :)

To start you need to use the USB port which is to the right of the microSD card.

 

Expand  

Armbian_5.98_Rk3399-tv_Ubuntu_bionic_next_5.4.0-rc2-next-20191009_desktop runs from sdcard on the N6 - no wifi though

NicoD

NicoD

Posted
Posted

@balbes150 
I've tried with next bionic desktop and default bionic desktop. Both on an sd-card, but used a usb3 sd-card reader for one.  Changed the background to see the difference.
On the RockPi4. Both images work(hdmi works, no wifi in default). When having default in the RockPi4 it always boots the default, no matter where I put the sd-card reader with next.
With next in the rockpi4 and the sd-card reader in the bottom left usb3 port nothing seems to boot. The sd-reader turns on and flashes(doesn't do that in other ports). It doesn't seem to boot, display doesn't turn on. Flashing of sd-card reader stops after a few seconds, led stays on. 

With the NanoPi M4V2 there's no .dtb file for the NanoPi M4(also not in Buster) in default. I've copied the one from NEXT. It seems to boot, but without hdmi(as that other person said in the M4V2 thread). 
So I had the same behaviour as with the RockPi4. Only with next it seemed to boot from the sd-card reader. It even kept flashing as if it was booted. But since hdmi doesn't work on the default image I'm now not sure if it booted or just was stuck like the RockPi4.
I also tried with LE on the M4V2. That didn't boot into KODI. It did it reseize, rebooted. But stayed at the screen of just enough os for kodi without going further. 
That also didn't seem to boot from USB. And also with LE in the M4V2 it didn't boot Armbian from USB. 

I hope you're something with this information. It only made me more confused the longer I tried. 
Great job. Very cool to be able to run from USB. And also great to be able to use the same image on different boards. You make the compatibillity so much better with this. Cheers.

1
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept