Jump to content

RockPi 4b 'board bring up'

chwe

By chwe
in Rockchip

 Share

Recommended Posts

Vonor

Vonor

Posted
Posted

Just building a fresh image right now.

 

BTW, this is my compile line. 

git pull && ./compile.sh docker KERNEL_ONLY=no KERNEL_CONFIGURE=no BUILD_DESKTOP=no BRANCH=dev RELEASE=bionic BOARD=rockpi-4b
[ o.k. ] Done building [ /root/armbian/output/images/Armbian_5.77_Rockpi-4b_Ubuntu_bionic_dev_4.20.13.img ]

Will test in the evening. and report back.

Vonor

Vonor

Posted
Posted
  On 3/11/2019 at 12:09 PM, Vonor said:

Will test in the evening. and report back.

Expand  

Test done. fresh build (Armbian_5.77_Rockpi-4b_Ubuntu_bionic_dev_4.20.13.img)

Nothing was changed after building the image, except for coping the files as suggested.

 

I was watching syslog (tail -f) while I waited for it to happen. But couldn't see anything unusual when it started.

Perhaps it has to do with the Fritzbox I am connecting to (5GHz) ? I'll try using an older android phone as AP to see if that makes a change.

 

If you guys have suggestions on how to debug it further to provide additional valuable info, please let me know.

 

  Reveal hidden contents

 

Vonor

Vonor

Posted
Posted
  On 3/11/2019 at 9:31 PM, Vonor said:

Perhaps it has to do with the Fritzbox I am connecting to (5GHz) ? I'll try using an older android phone as AP to see if that makes a change.

Expand  

So, makes no difference whether I'm connected to a 5GHz AP or to a 2.4GHz AP.

mitag

mitag

Posted
Posted
  On 3/11/2019 at 9:31 PM, Vonor said:

Perhaps it has to do with the Fritzbox I am connecting to (5GHz) ?

Expand  

In the FritzBox you can set two different SSIDs for 2.4GHz and 5GHz. I've done this before to force a smartphone to connect to 5GHz.

 

FritzBox SSID-2GHz4 - SSID-5GHz.png

mitag

mitag

Posted
Posted
  On 3/11/2019 at 3:09 PM, atula said:

M.2 NV SSD not work with 4.20.13.img

4.4.154 works

Expand  

Lol, I probably should have tried that one myself. :( I returned a Corsair Force MP510 240 GB NVMe PCIe M.2 SSD this morning that was delivered on Saturday and a Samsung MZ-V7S250BW SSD 970 EVO Plus 250 GB M.2 NVMe SSD that was delivered today didn't work either. I use Debian_stretch_dev_4.20.0 because otherwise it works better than the Radxa images.

chwe

chwe

Posted
  • Author
Posted
  On 3/11/2019 at 11:01 PM, mitag said:

Lol, I probably should have tried that one myself. :(

Expand  

it's wip... things don't work should be the default expectation...

 

4.4 will have some drawbacks with the rockPI, as far as I know (tested some time ago) the DT needs some fixing cause we lent it out from their kernelfork which seems to be 'slightly' different to the one armbian uses.

mitag

mitag

Posted
Posted

Something else I noticed when I shut down the system with "sudo shutdown -h now" and forget to unplug the USB C connector, then the system heats up completely. It just happened to me, so I disconnected the plug for 5 seconds and plugged it in again, so that the greeting shows the CPU temperature, 60°C! But I haven't done a test with another kernel version than Debian_stretch_dev_4.20.0 yet, I'm going to sleep now.

Vonor

Vonor

Posted
Posted

I found two more issues on this board.

 

1: USB Storage. Using the below shown adapter cable to connect a crucial bx500 ssd to the RockPi. Initial connection takes a while. As in dmesg showing that the dis is connected instantly, but showing the partition only after round about half a minute.

 

However, the real problem is, that issuing a reboot causes the neither the disk, nor the adapter cable to be seen. Physically detaching and re-attaching it brings it back. Unplugging the RockPi from the power source also works.

 

// EDIT: This is on the usb3 Ports.

// EDIT2: On the USB2 Ports the disk is available even after reboot.

 

NOTE: On the nanopi m4 the same adapter cable and ssd work without a flaw.

 

dmesg

  Reveal hidden contents

 

lsusb -vvv

  Reveal hidden contents

 

2: shutdown -h now

The OS goes down, but the system does not power off. The green LED stays on, the Ethernet LED shows activity and hdmi display looks like i smashed a hammer into the monitor.

Unfortunately I don't have a serial console adapter so I can't debug this issue.

 

// EDIT: I notice the same heat raise @mitag has mentioned. even though I have a PI-Fan connected to the 5V GPIO Pins and attached to the heat sink, which usually keeps the RockPi very cool

chwe

chwe

Posted
  • Author
Posted
  On 3/12/2019 at 9:31 PM, Vonor said:

NOTE: On the nanopi m4 the same adapter cable and ssd work without a flaw.

Expand  

 

  On 3/12/2019 at 9:31 PM, Vonor said:

Unfortunately I don't have a serial console adapter so I can't debug this issue. 

Expand  

 

there you go:

 

it's called 'The silly approach' :lol:

mitag

mitag

Posted
Posted

In my eyes an access to the serial console is absolutely necessary, if you don't want it, you should get other toys. SBC are often offered with a recommended USB-UART adapter, for a small extra charge, as an option and I have used this possibility already several times.

2012853004_USB-UARTBridge.thumb.png.2212a98f9b77e1ac14854e34764bdb7c.png
The photo probably doesn't show all USB-UART adapters I own, only those that were handy.

Vonor

Vonor

Posted
Posted

Seems like with Armbian 5.77 and kernel 5.0 wifi runs kinda stable.

 

Did the filename for the nvram txt change? See dmesg output below where it failed to load the file with radxa or rockpi-4b in the name. Despite the errors about the backplane wifi seems to run stable this time.

 

  Reveal hidden contents

 

martinayotte

martinayotte

Posted
Posted
  On 3/19/2019 at 4:42 PM, Vonor said:

Direct firmware load for brcm/brcmfmac43455-sdio.radxa,rockpi-4b.txt failed with error

Expand  

This is new in 5.0.y and normal, but if file isn't found, it fall back to normal one ...

 

dragonlost

dragonlost

Posted
Posted
  On 3/12/2019 at 12:12 AM, mitag said:

Something else I noticed when I shut down the system with "sudo shutdown -h now" and forget to unplug the USB C connector, then the system heats up completely. It just happened to me, so I disconnected the plug for 5 seconds and plugged it in again, so that the greeting shows the CPU temperature, 60°C! But I haven't done a test with another kernel version than Debian_stretch_dev_4.20.0 yet, I'm going to sleep now. 

Expand  

 

exact same problem on nanopi m4 "next" branch. Need test last armbian version.

mrsufgi

mrsufgi

Posted
Posted

Maybe it's related but after i execute 

reboot 

command,  via ssh, local or omv - reboot 

 

EDIT: 

I doesn't matter which way I try to reboot or shutdown, it just never goes back up. 

 

I also installed OMV maybe it's related?

 

The board never goes back up. Not even disconnecting from power source, and reconnecting.  only reflashing the img will boot the system back up. 

 

 Using the model 4A model with latest nightly.

 

In addition, 

Using the raxda armbian img it does not occur :(

 

 

 

EDIT 2: 

 

Freezing kernel using armbian-config after first install did the trick. <3 

 

mrsufgi

mrsufgi

Posted
Posted

I'm also expiriencing @Vonor issue, I considering upgrading. do u think I can unfreeze my kernel and pray that i would boot ? :D

mrsufgi

mrsufgi

Posted
Posted
  On 4/16/2019 at 2:08 PM, mrsufgi said:

I'm also expiriencing @Vonor issue, I considering upgrading. do u think I can unfreeze my kernel and pray that i would boot ? :D

Expand  

 

Don't, it doesn't work (tried it myself).

 

I also tried all available images (5.79 with 5.0.0 kernel), non of them works. :(

 

 

Fan KunPeng

Fan KunPeng

Posted
Posted
  On 4/25/2019 at 12:41 PM, mrsufgi said:

 

Don't, it doesn't work (tried it myself).

 

I also tried all available images (5.79 with 5.0.0 kernel), non of them works. :(

 

 

Expand  

 

I also have a ROCK Pi 4 -- MODEL A 1GB. Armbian can't boot. No hdmi output.

TonyMac32

TonyMac32

Posted
Posted

Hmmm, does anyone else have a 1 GB model?

Also can anyone provide any debug info that would aid in determining the cause?

Sent from my Pixel using Tapatalk

Fan KunPeng

Fan KunPeng

Posted
Posted
  On 5/4/2019 at 3:12 PM, TonyMac32 said:

Hmmm, does anyone else have a 1 GB model?

Also can anyone provide any debug info that would aid in determining the cause?

Sent from my Pixel using Tapatalk
 

Expand  

 

Here it is:

  Reveal hidden contents

 

Fan KunPeng

Fan KunPeng

Posted
Posted
  On 5/5/2019 at 2:17 PM, chwe said:

how long did you wait then?

 

unfortunately they're only 4b dev samples around right?

Expand  

it just stop there. Sometimes it stop earlier.

 

I have tried to replace with radxa's dtb file but failed with kernel panic.

NicoD

NicoD

Posted
Posted

Could anyone also enable kernel 5.1 for the RockPi4 dev on the Armbian build script please? 
I would love to test it out with Armbian. I'm very curious how it is.
I've just started building a dev 5.0 for the RockPi4 and saw there's now Disco. Also very curious about that. I love new things to test, and this time it doesn't cost me money :)

chwe

chwe

Posted
  • Author
Posted
  On 5/6/2019 at 9:44 PM, NicoD said:

Could anyone also enable kernel 5.1 for the RockPi4 dev on the Armbian build script please? 
I would love to test it out with Armbian. I'm very curious how it is.

Expand  

Short answer: No (or: yes you can -- > see long answer)

 

Long answer:

what do you expect to change between 5.0 and 5.1? there's not much changed for RK3399 between those two except:

 

New hardware – FriendlyELEC NanoPC-T4 and NanoPi M4, Radxa RockPi 4

 

means this patch needs to be adjusted:

https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-dev/add-board-rockpi4b.patch

 

see which patches else break as well... probably a few others, e.g. every patch modifying the makefile of all the DTS. We don't switch kernels for one board.. we switch it for the whole boardfamily.. which means here rockchip64 with: RockPi, Renegade, Firefly, NanoPis 4 (at least on mainline they share their kernel), Rock64, RockPro64 and maybe a few I forgot..

  On 5/6/2019 at 9:44 PM, NicoD said:

and this time it doesn't cost me money :)

Expand  

It doesn't cost money, but it costs time... ;)  But you can do it on your own :

  1. clone buildscript
  2. altering those lines to the 'real mainline source' (we use ayufans mainline branch which currently not switched to 5.1) go through his 60 commits on top of mainline to figure out which of those are still needed (and which need to be fixed).. then apply our ~20 patches for this kernel and fix all the regressions you'll get here..
  3. and if you really want to test something new, not only what has enhanced in the same 'drivers' you had in 5.0, you would need to adjust the config file as well to get the new stuff compiled (e.g. if you want to play around with the new scheduler --> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=81a930d3a64a00c5adb2aab28dd1c904045adf57 ).

 

NicoD

NicoD

Posted
Posted
  On 5/7/2019 at 6:08 PM, chwe said:

Short answer: No (or: yes you can -- > see long answer) 

Expand  

Thank you for your very complete answer. I'm ignorant when it comes to these things.
I saw that "new hardware : RockPi4"
So I thought it was now supported more easily with kernel 5.1. Not as simple as I thought clearly.
I'm planning a video about the NanoPi M4 and RockPi4B in some weeks. So it would have been great. I should have known it wasn't that simple... since it never is :D
I'm learning every day. Thanks

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