Jump to content

Firfly-rk3399 have not been booting up reasent images from Armbian

denni_isl

By denni_isl
in Beginners

 Share

Recommended Posts

denni_isl

denni_isl

Posted
  • Author
Posted
  On 11/19/2020 at 7:19 PM, piter75 said:

Both look perfectly well except for the fact that the latest one does not boot :(

 

Can you also try one of the v20.02.7 images available in the archive? https://archive.armbian.com/firefly-rk3399/archive/

I'd like to find the most precise point where it stopped working.

Expand  

 

This image Armbian_20.02.7_Firefly-rk3399_bullseye_legacy_4.4.213  - legacy did work.  Will try current next.  

And this is the messages from the serial output from ttyFIQ0

 

  Reveal hidden contents

 

Current - Armbian_20.02.7_Firefly-rk3399_buster_current_5.4.28_desktop is not working,

this is the output.

 

  Reveal hidden contents

 

Perhaps some issues with the dtb file with the current kernel as balbes150 did suggest.  

 

 

0
balbes150

balbes150

Posted
Posted

As an assumption, it is possible that u-boot specifies the name of the DTB file, which is not suitable for recent kernels. You can try to force the use of a different DTB (via armbianuEnv.txt) and try to check other DTB options. Sometimes there are "miracles" and someone else's DTB can work.

1
denni_isl

denni_isl

Posted
  • Author
Posted
  On 11/20/2020 at 11:10 AM, balbes150 said:

As an assumption, it is possible that u-boot specifies the name of the DTB file, which is not suitable for recent kernels. You can try to force the use of a different DTB (via armbianuEnv.txt) and try to check other DTB options. Sometimes there are "miracles" and someone else's DTB can work.

Expand  

 

This did it!  Did add - device_tree=/boot/dtb/rockchip/firefly-rk3399.dtb in armbianEnv.txt and start 20.02.7 kernel 5.4.28 from Mars 28

 

  Reveal hidden contents

 

But it was not sufficient to bring up Armbian_20.08.1_Firefly-rk3399_focal_current_5.8.6.img

( do always clean the SD between the attempts with - dd if=/dev/zero of=/dev/sdc bs=4096 status=progress) 

 

This is a good reading about dtb and overlays - https://www.raspberrypi.org/documentation/configuration/device-tree.md

 

 

 

0
denni_isl

denni_isl

Posted
  • Author
Posted

This is the error message from - Armbian_20.05.1_Firefly-rk3399_focal_current_5.4.43.img.xz

It hangs on -

[    3.197491] rk808-rtc rk808-rtc: registered as rtc0                                                     
[    3.198558] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!                              
[    3.199193] fan53555-reg: supplied by vcc_sys                              

 

  Reveal hidden contents

 

And u-boot printenv

 

  Reveal hidden contents

 

0
denni_isl

denni_isl

Posted
  • Author
Posted

Side node;

this is  a perfect image for firefly-rk3399 - Armbian_20.02.7_Firefly-rk3399_bullseye_legacy_4.4.213.img - (debian 11 and kernel 4.4.213) - then after apt update && apt upgrade; apt install tasksel - tasksel - xfce4 - arbian-config,

install full firmware and bluetooth support, apt install gnome-bluetooth - 

 

 

 

0
denni_isl

denni_isl

Posted
  • Author
Posted
  On 2/11/2021 at 6:23 AM, balbes150 said:

Without exact data (UART log, settings of the DTB used , exact image name) no one will help you.

Expand  

 

The image is Armbian_20.05.1_Firefly-rk3399_focal_curent_5.4.43 - the with rk3399-firefly.dtb - and I did work - but not now ?

Armbian bullseye 4.4.213 and rk3399-firefly.dtb does always work - and is just fine image for this board.  

Just experimenting with newer kernel.

 

This is where it halts - votages and RTL

 

  Quote

[    3.176916] SWITCH_REG1: supplied by vcc3v3_sys                              
[    3.177620] SWITCH_REG2: supplied by vcc3v3_sys                              
[    3.181586] rk808-rtc rk808-rtc: registered as rtc0                          
[    3.182638] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!   
[    3.183271] fan53555-reg: supplied by vcc_sys                                

 

Expand  

 

UART

 

  Reveal hidden contents

 

0
denni_isl

denni_isl

Posted
  • Author
Posted

This is strange - "and totally easy going ".

After starting the board with bullseye 4.4.213 SD card

and then right away starting with fresh 5.4.43-rockchip64 SD card then it all of a sudden did boot up.

 

Then armbian-config - sytem - boot and flash to emmc - but 5.4.43 does not boot now from emmc- same UART messages as from the SD card.  

Edit:

Did boot from 4.4.213 sd card, shut down, remove sd card, reset button, stop u-boot - run bootcmd_mmc1, and 5.4.43 did boot up from emmc.  apt update; apt upgrde and reboot now and reboots so it is working.

 

  Reveal hidden contents

 

-------------------------------------------

There are always 3 small boot partitions on the mmc and some u-boot there - Boot1: 2019-03-14, version: 1.19

 

Is it possible to wipe those partitions clean without bricking the firefly-rk3399 board?

 

  Quote

mmcblk1boot0 179:64   0     4M  1 disk                                          
mmcblk1boot1 179:96   0     4M  1 disk                                          
mmcblk1rpmb  179:128  0     4M  0 disk

Expand  

 

0
balbes150

balbes150

Posted
Posted
  On 2/11/2021 at 1:48 PM, denni_isl said:

The image is Armbian_20.05.1_Firefly-rk3399_focal_curent_5.4.43 - the with rk3399-firefly.dtb - and I did work - but not now ?

Expand  

 Show the UART log when starting the system with eMMC (when no external SD\USB media is connected)

What system is installed in eMMC ?

 

  On 2/11/2021 at 2:13 PM, denni_isl said:

Is it possible to wipe those partitions clean without bricking the firefly-rk3399 board?

Expand  

You can completely erase all eMMC if you run any version of Armbian that sees eMMC when running from an external media. 

0
denni_isl

denni_isl

Posted
  • Author
Posted
  On 2/12/2021 at 6:59 AM, balbes150 said:

 Show the UART log when starting the system with eMMC (when no external SD\USB media is connected)

What system is installed in eMMC ?

 

You can completely erase all eMMC if you run any version of Armbian that sees eMMC when running from an external media. 

Expand  

 

Now it boots  Armbian 21.02.1 Focal with Linux 5.10.12-rockchip64 successfully every time from emmc.

 

To those of consern about /dev/mmcblk2boot0 and /dev/mmcblk2boot1 and RPMB partitiones.

This is http://trac.gateworks.com/wiki/MMC some info about hardware partitions on some emmc.   "man mmc-utils" and  "sudo dpkg -L mtd-utils"  and man mmc

 

UART

 

  Reveal hidden contents

 

0
balbes150

balbes150

Posted
Posted

Show the UART log of the attempt to launch the last Armbian image (which is not working for you). Important. You should not change anything on the SD card after recording. You should not stop the u-boot startup process, I need a "clean" u-boot log when trying to start. And show the content armbianEnv.txt a system that does not start.

0
denni_isl

denni_isl

Posted
  • Author
Posted
  On 2/12/2021 at 2:19 PM, balbes150 said:

I'm not asking you about eMMC, but about launching from external media.

Expand  

 

ArmbianEnv.txt

  Quote

verbosity=7
bootlogo=false
overlay_prefix=rockchip
rootdev=UUID=76c21c43-8ec8-4c56-a741-6fd8602eed2e
rootfstype=ext4

Expand  

 

mainline focal 5.10.y from https://www.armbian.com/firefly-rk3399/

sd card boot up does not get any further than - starting kernel.......

 

UART:

  Reveal hidden contents

 

 

Screenshot_2021-02-12_17-09-09.png

0
denni_isl

denni_isl

Posted
  • Author
Posted

 

Vondering if this has something to do with AppArmor or the hardware partitions

 

grep APPARMOR /boot/config-*                           
CONFIG_SECURITY_APPARMOR=y                                                      
CONFIG_SECURITY_APPARMOR_HASH=y                                                 
CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y                                         
# CONFIG_SECURITY_APPARMOR_DEBUG is not set                                     
CONFIG_DEFAULT_SECURITY_APPARMOR=y

 

This is from successful Armbian 21.02.1 Focal with Linux 5.10.12-rockchip64 emmc boot

 

Screenshot_2021-02-12_17-50-32.png

0
denni_isl

denni_isl

Posted
  • Author
Posted
  Reveal hidden contents

 

 

Trying to boot legacy Armbian_20.11.10_Firefly-rk3399_bionic_legacy_4.4.213_desktop

0
denni_isl

denni_isl

Posted
  • Author
Posted
  On 2/15/2021 at 3:47 PM, balbes150 said:

fdtfile=rockchip/rk3399-firefly.dtb

Expand  

 

  Quote

verbosity=7
bootlogo=false
overlay_prefix=rockchip
fdtfile=rockchip/rk3399-firefly.dtb
rootdev=UUID=e4ee432b-e6cf-43d2-aca5-c26b7fca040e
rootfstype=ext4

Expand  

 

 

  Reveal hidden contents

 

0
denni_isl

denni_isl

Posted
  • Author
Posted
  On 2/16/2021 at 6:40 AM, balbes150 said:

Try using other dtbs (roc-pc-plus, roc-mezzanine, rock-pi-4b etc)

Expand  

 

Some progress,  rk3399-nanopi-m4.dtb does bring everyting up exept hdmi - the others on the list did just end at Starting kernel .....

rk3399-orangepi-4.dtb does also bring up the board.

 

  Quote

verbosity=7
bootlogo=false
overlay_prefix=rockchip
#fdtfile=rockchip/rk3399-firefly.dtb
#fdtfile=rockchip/rk3399-roc-pc-plus.dtb
#fdtfile=rockchip/rk3399-roc-pc.dtb
#fdtfile=rockchip/rk3399-rock-pi-4b.dtb
#fdtfile=rockchip/rk3399-rockpro64.dtb
#fdtfile=rockchip/rk3399-roc-pc-mezzanine.dtb
fdtfile=rockchip/rk3399-nanopi-m4.dtb
#fdtfile=rockchip/rk3399-orangepi-4.dtb
rootdev=UUID=e4ee432b-e6cf-43d2-aca5-c26b7fca040e
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

Expand  

 

  Reveal hidden contents

 

But no hdmi connection - just UART

 

  Quote

^C                                                                              
root@firefly-rk3399:~# ls                                                       
root@firefly-rk3399:~# uname -a                                                 
Linux firefly-rk3399 5.10.12-rockchip64 #21.02.1 SMP PREEMPT Wed Feb 3 20:55:02x
root@firefly-rk3399:~# cat /etc/os-release                                      
NAME="Ubuntu"                                                                   
VERSION="20.04.2 LTS (Focal Fossa)"                                             
ID=ubuntu                                                                       
ID_LIKE=debian                                                                  
PRETTY_NAME="Armbian 21.02.1 Focal"                                             
VERSION_ID="20.04"                                                              
HOME_URL="https://www.ubuntu.com/"                                              
SUPPORT_URL="https://help.ubuntu.com/"                                          
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"                             
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-pol"
VERSION_CODENAME=focal                                                          
UBUNTU_CODENAME=focal                                                           
root@firefly-rk3399:~#

Expand  

 

apt update - apt upgrade

and the new image boots up

 

  Quote

[   44.293412] rockchip-i2s ff8a0000.i2s: Fail to set mclk -22                  
[   44.293904] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk2
                                                                                
denni@firefly-rk3399:~$ [   49.359286] rockchip-i2s ff8a0000.i2s: Fail to set m2
[   49.359820] rockchip-i2s ff8a0000.i2s: ASoC: error at snd_soc_dai_set_sysclk2
^C                                                                              
denni@firefly-rk3399:~$ ls                                                      
Desktop                                                                         
denni@firefly-rk3399:~$ ls                                                      
Desktop                                                                         
denni@firefly-rk3399:~$ uname -a                                                
Linux firefly-rk3399 5.10.16-rockchip64 #21.02.2 SMP PREEMPT Sun Feb 14 21:35:0x
denni@firefly-rk3399:~$

 

Expand  

 

 

Screenshot_2021-02-16_11-18-07.png

Screenshot_2021-02-16_11-49-26.png

0
denni_isl

denni_isl

Posted
  • Author
Posted

And the legacy kernel that does always boot up - mbian 21.02.1 Bullseye with Linux 4.4.213-rk3399.

 

  Reveal hidden contents

 

0
balbes150

balbes150

Posted
Posted
  On 2/16/2021 at 11:08 AM, denni_isl said:

But no hdmi connection - just UART

Expand  

I expected this, the reason is not correct (not correct) data for DTB. To solve the problem, I need to have the test equipment. I sent a request to Fyrefly, but for now it's the New Year in China and the response will be after it.

1
luuray

luuray

Posted
Posted

Hi there,

with current 21.02.01_focal_current_5.10.12 image, I was update armbianEnv.txt and boot.scr to enable earlycon, set verbosity to 7 and add fdtfile=rockchip/rk3399-firefly.dtb, then use rkdeveloptool write image to emmc, after u-boot stage, the "Starting kernel" stage was hanged with this message output
  

Found U-Boot script /boot/boot.scr
3184 bytes read in 16 ms (194.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
153 bytes read in 13 ms (10.7 KiB/s)
15339358 bytes read in 1494 ms (9.8 MiB/s)
28582400 bytes read in 2737 ms (10 MiB/s)
76162 bytes read in 40 ms (1.8 MiB/s)
2698 bytes read in 30 ms (86.9 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    15339294 Bytes = 14.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to f507d000, end f5f1df1e ... OK
   Loading Device Tree to 00000000f5002000, end 00000000f507cfff ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.10.12-rockchip64 (root@beast) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #21.02.1 SMP PREEMPT Wed Feb 3 20:55:02 CET 2021
[    0.000000] Machine model: Firefly-RK3399 Board
[    0.000000] earlycon: uart0 at MMIO32 0x00000000ff1a0000 (options '1500000n8')
[    0.000000] printk: bootconsole [uart0] enabled

 

also i have changed fdtfile to rk3399-nanopi-m4, rk3399-roc-pc and other dtbs, there was not any changed but hanged with same message.

 

My board is CORE-3399-JD4(http://wiki.t-firefly.com/en/Core-3399-JD4/started.html) "core board" with "mother board", it similar with AIO-3399-JD4(http://wiki.t-firefly.com/en/AIO-3399J/started.html)

 

Let me known if need more info :)

0
balbes150

balbes150

Posted
Posted
  On 2/19/2021 at 4:07 AM, luuray said:

current 21.02.01_focal_current_5.10.12 image,

Expand  

Write the full name of the image.

 

  On 2/19/2021 at 4:07 AM, luuray said:

My board is CORE-3399-JD4

Expand  

This is a completely different device than the one discussed in this topic. As far as I know, this module is intended for use as part of other equipment , you did not specify which equipment it is used as part of. You did not provide a description of what happens to the main hardware that contains this module. Perhaps in the image that you are trying to disable further output to the UART console, I recommend trying the ArmbianTV image, there the output to the UART console is not disabled and there should be full information about the startup process.

0
balbes150

balbes150

Posted
Posted

I received Fyrefly samples today, including Firefly-rk3399. The first tests showed. Yes, indeed, the official images for this model from the official download page (I have only checked the main kernel so far) do not work, i.e., as described earlier, u-boot starts, transfers control to the kernel, and that's the end of it. But there is also good news, I checked the image from Firefly-Station P1 and it worked perfectly without any additional settings. I.e. I wrote the image to the SD card, connected the SD card to Firefly-rk3399, turned on the power and the system automatically started. Works LAN HDMI Wifi HDMI sound. BT does not work and instead of shutting down, the system restarts. I briefly checked the system with the 4.4 kernel (for P1), the main components work, including analog sound. I checked the launch of Libreelec - the system starts and works with HW.   :)

0
adzio

adzio

Posted
Posted

Thanks denni_isl for diligently checking builds and reporting your experiences and balbes150 et al. for support.

I also ran into the same issue of Armbian_21.02.3_Firefly-rk3399_focal_current_5.10.21.img.xz not booting from SD.

 

FYI There is a problem with some PCIe kernel bits (resulting in error -110 in dmesg and preventing normal bus operation) in older kernels which is reported as fixed sometime in 5.8 so 4.4 doesn't work for me - I need a more recent build 5.9+ to be able to use my M.2 device. It would be great if the issue(s) behind those more recent builds not booting is/are found/fixed so that the PCIe fix can be confirmed.

0

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
Reply to this topic...

×   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.

×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept