5 5
matteobp

Rock64 nightly image

Recommended Posts

34 minutes ago, MunkeyBalls said:

Armbian_5.42_Rock64_Debian_stretch_default_4.4.124_desktop


That image 100% works: http://ix.io/17uH If you have troubles, https://docs.armbian.com/User-Guide_Getting-Started/

 

35 minutes ago, MunkeyBalls said:

I think the log I posted was from the latest nightly, want me to retry with the one from the main download page?


Nightly images are not subject of a support. Nobody but developers care if they work or not.

Share this post


Link to post
Share on other sites
34 minutes ago, Igor said:


That image 100% works: http://ix.io/17uH If you have troubles, https://docs.armbian.com/User-Guide_Getting-Started/

 


Nightly images are not subject of a support. Nobody but developers care if they work or not.

 

The one reason I tried the nightly is because the first image wouldn't boot for me.

I've tried the guide before coming here, but there's probably still something I'm missing.

 

Could it be that this has something to do with it?

rock64@rock64:/boot$ ls -l
total 25536
-rw-r--r-- 1 root root  4492973 Oct 12 09:15 System.map-4.4.77-rockchip-ayufan-136
-rw-r--r-- 1 root root   143541 Oct 12 09:15 config-4.4.77-rockchip-ayufan-136
lrwxrwxrwx 1 root root       49 Apr 10 19:00 dtb -> dtbs/4.4.77-rockchip-ayufan-136/rk3328-rock64.dtb
lrwxrwxrwx 1 root root       49 Apr 10 19:00 dtb-4.4.77-rockchip-ayufan-136 -> dtbs/4.4.77-rockchip-ayufan-136/rk3328-rock64.dtb
drwxr-xr-x 4 root root     4096 Apr 10 18:56 dtbs
drwxr-xr-x 4 root root    16384 Jan  1  1970 efi
-rw-r--r-- 1 root root     7491 Sep  8  2017 filesystem.packages
-rw-r--r-- 1 root root        1 Sep  8  2017 filesystem.packages-remove
-rw-r--r-- 1 root root  2866287 Apr 10 19:00 initrd.img-4.4.77-rockchip-ayufan-136
-rwxr-xr-x 1 root root 18606088 Oct 12 09:15 vmlinuz-4.4.77-rockchip-ayufan-136
rock64@rock64:/boot$ uname -a
Linux rock64 4.4.120-rockchip-ayufan-209 #1 SMP Mon Apr 2 16:05:07 UTC 2018 aarch64 GNU/Linux

This was after already removing linux-image-4.4.120-rockchip-ayufan-209 and reinstalling linux-image-4.4.77-rockchip-ayufan-136 and rebooting

rock64@rock64:/boot$ sudo apt-get remove 4.4.120-rockchip-ayufan-209
[sudo] password for rock64:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'linux-headers-4.4.120-rockchip-ayufan-209' for regex '4.4.120-rockchip-ayufan-209'
Note, selecting 'linux-image-4.4.120-rockchip-ayufan-209-dbg' for regex '4.4.120-rockchip-ayufan-209'
Note, selecting 'linux-image-4.4.120-rockchip-ayufan-209' for regex '4.4.120-rockchip-ayufan-209'
Note, selecting 'linux-debug-4.4.120-rockchip-ayufan-209' for regex '4.4.120-rockchip-ayufan-209'
Note, selecting 'linux-modules-4.4.120-rockchip-ayufan-209' for regex '4.4.120-rockchip-ayufan-209'
Note, selecting 'linux-firmware-image-4.4.120-rockchip-ayufan-209' for regex '4.4.120-rockchip-ayufan-209'
Note, selecting 'linux-image-4.4.120-rockchip-ayufan-209' instead of 'linux-modules-4.4.120-rockchip-ayufan-209'
Note, selecting 'linux-image-4.4.120-rockchip-ayufan-209-dbg' instead of 'linux-debug-4.4.120-rockchip-ayufan-209'
Package 'linux-firmware-image-4.4.120-rockchip-ayufan-209' is not installed, so not removed
Package 'linux-headers-4.4.120-rockchip-ayufan-209' is not installed, so not removed
Package 'linux-image-4.4.120-rockchip-ayufan-209' is not installed, so not removed
Package 'linux-image-4.4.120-rockchip-ayufan-209-dbg' is not installed, so not removed
The following packages were automatically installed and are no longer required:
  debsums libfile-fnmatch-perl u-boot-rock64
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
rock64@rock64:/boot$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  debsums libfile-fnmatch-perl u-boot-rock64
0 upgraded, 0 newly installed, 3 to remove and 2 not upgraded.
After this operation, 1237 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 86722 files and directories currently installed.)
Removing u-boot-rock64 (0.6.31) ...
Removing debsums (2.2.2) ...
Removing libfile-fnmatch-perl (0.02-2+b3) ...
Processing triggers for man-db (2.7.6.1-2) ...
rock64@rock64:/boot$ sudo reboot now
Using username "rock64".
rock64@192.168.2.101's password:
Send automatic password
                _     __   _  _
 _ __ ___   ___| | __/ /_ | || |
| '__/ _ \ / __| |/ / '_ \| || |_
| | | (_) | (__|   <| (_) |__   _|
|_|  \___/ \___|_|\_\\___/   |_|

Linux rock64 4.4.120-rockchip-ayufan-209 #1 SMP Mon Apr 2 16:05:07 UTC 2018 aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

 

Share this post


Link to post
Share on other sites
34 minutes ago, Igor said:


You are not using our images. 

 

I was trying to but they weren't working. Now I'm trying to figure out why it's not working but I'm a bit of a noob and could use some help. :)

From windows I've formatted the SDCard Sandisk 10 with SDFormatter, then downloaded, checked the hash of and flashed the image you say 100% WORKS with etcher, then tried booting it but it did not work (numerous times I've repeated this).

 

I noticed with my above problem that no matter which image I try the kernel seems to be stuck at 4.4.120-rockchip-ayufan-209, even with the old images. (after numerous reboots)

Then I removed the eMMC and the kernel changed.

Now gonna retry flash with armbian and try the whole process again to see if it also fixes my problem booting armbian.

 

EDIT: Removing the emmc did the trick, it's working for me now. Knew it was something stupid I was missing.

Share this post


Link to post
Share on other sites

So after doing apt-get update and apt-get upgrade it installed a new kernel and went back to the same behaviour as previously

 

root@rock64:~# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libicu57 libnss-myhostname libpam-systemd libssl-dev libssl1.0.2 libssl1.1 libsystemd0 libudev1 openssl systemd systemd-sysv thunderbird tzdata udev
14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 54.0 MB of archives.
After this operation, 142 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://security.debian.org stretch/updates/main arm64 libssl1.0.2 arm64 1.0.2l-2+deb9u3 [907 kB]
Get:10 http://security.debian.org stretch/updates/main arm64 libssl-dev arm64 1.1.0f-3+deb9u2 [1,375 kB]
Get:2 http://cdn-fastly.deb.debian.org/debian stretch-updates/main arm64 libsystemd0 arm64 232-25+deb9u3 [240 kB]
Get:3 http://cdn-fastly.deb.debian.org/debian stretch-updates/main arm64 libnss-myhostname arm64 232-25+deb9u3 [101 kB]
Get:4 http://cdn-fastly.deb.debian.org/debian stretch-updates/main arm64 libpam-systemd arm64 232-25+deb9u3 [168 kB]
Get:11 http://security.debian.org stretch/updates/main arm64 libssl1.1 arm64 1.1.0f-3+deb9u2 [1,112 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian stretch-updates/main arm64 systemd arm64 232-25+deb9u3 [2,139 kB]
Get:12 http://security.debian.org stretch/updates/main arm64 libicu57 arm64 57.1-6+deb9u2 [7,550 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian stretch-updates/main arm64 udev arm64 232-25+deb9u3 [1,056 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian stretch-updates/main arm64 libudev1 arm64 232-25+deb9u3 [115 kB]
Get:8 http://cdn-fastly.deb.debian.org/debian stretch-updates/main arm64 systemd-sysv arm64 232-25+deb9u3 [81.1 kB]
Get:9 http://cdn-fastly.deb.debian.org/debian stretch-updates/main arm64 tzdata all 2018d-0+deb9u1 [266 kB]
Get:13 http://security.debian.org stretch/updates/main arm64 openssl arm64 1.1.0f-3+deb9u2 [697 kB]
Get:14 http://security.debian.org stretch/updates/main arm64 thunderbird arm64 1:52.7.0-1~deb9u1 [38.2 MB]
Fetched 54.0 MB in 2s (21.4 MB/s)
Preconfiguring packages ...
(Reading database ... 96979 files and directories currently installed.)
Preparing to unpack .../libsystemd0_232-25+deb9u3_arm64.deb ...
Unpacking libsystemd0:arm64 (232-25+deb9u3) over (232-25+deb9u2) ...
Setting up libsystemd0:arm64 (232-25+deb9u3) ...
(Reading database ... 96979 files and directories currently installed.)
Preparing to unpack .../libnss-myhostname_232-25+deb9u3_arm64.deb ...
Unpacking libnss-myhostname:arm64 (232-25+deb9u3) over (232-25+deb9u2) ...
Preparing to unpack .../libpam-systemd_232-25+deb9u3_arm64.deb ...
Unpacking libpam-systemd:arm64 (232-25+deb9u3) over (232-25+deb9u2) ...
Preparing to unpack .../systemd_232-25+deb9u3_arm64.deb ...
Unpacking systemd (232-25+deb9u3) over (232-25+deb9u2) ...
Preparing to unpack .../udev_232-25+deb9u3_arm64.deb ...
Unpacking udev (232-25+deb9u3) over (232-25+deb9u2) ...
Preparing to unpack .../libudev1_232-25+deb9u3_arm64.deb ...
Unpacking libudev1:arm64 (232-25+deb9u3) over (232-25+deb9u2) ...
Setting up libudev1:arm64 (232-25+deb9u3) ...
Setting up systemd (232-25+deb9u3) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
(Reading database ... 96979 files and directories currently installed.)
Preparing to unpack .../0-systemd-sysv_232-25+deb9u3_arm64.deb ...
Unpacking systemd-sysv (232-25+deb9u3) over (232-25+deb9u2) ...
Preparing to unpack .../1-tzdata_2018d-0+deb9u1_all.deb ...
Unpacking tzdata (2018d-0+deb9u1) over (2018c-0+deb9u1) ...
Preparing to unpack .../2-libssl1.0.2_1.0.2l-2+deb9u3_arm64.deb ...
Unpacking libssl1.0.2:arm64 (1.0.2l-2+deb9u3) over (1.0.2l-2+deb9u2) ...
Preparing to unpack .../3-libssl-dev_1.1.0f-3+deb9u2_arm64.deb ...
Unpacking libssl-dev:arm64 (1.1.0f-3+deb9u2) over (1.1.0f-3+deb9u1) ...
Preparing to unpack .../4-libssl1.1_1.1.0f-3+deb9u2_arm64.deb ...
Unpacking libssl1.1:arm64 (1.1.0f-3+deb9u2) over (1.1.0f-3+deb9u1) ...
Preparing to unpack .../5-libicu57_57.1-6+deb9u2_arm64.deb ...
Unpacking libicu57:arm64 (57.1-6+deb9u2) over (57.1-6+deb9u1) ...
Preparing to unpack .../6-openssl_1.1.0f-3+deb9u2_arm64.deb ...
Unpacking openssl (1.1.0f-3+deb9u2) over (1.1.0f-3+deb9u1) ...
Preparing to unpack .../7-thunderbird_1%3a52.7.0-1~deb9u1_arm64.deb ...
Unpacking thunderbird (1:52.7.0-1~deb9u1) over (1:52.6.0-1~deb9u1) ...
Processing triggers for mime-support (3.60) ...
Setting up libnss-myhostname:arm64 (232-25+deb9u3) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up tzdata (2018d-0+deb9u1) ...

Current default time zone: 'Etc/UTC'
Local time is now:      Tue Apr 10 21:09:22 UTC 2018.
Universal Time is now:  Tue Apr 10 21:09:22 UTC 2018.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

Setting up systemd-sysv (232-25+deb9u3) ...
Setting up libicu57:arm64 (57.1-6+deb9u2) ...
Setting up thunderbird (1:52.7.0-1~deb9u1) ...
Setting up libssl1.0.2:arm64 (1.0.2l-2+deb9u3) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Setting up udev (232-25+deb9u3) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
insserv: Service mountkernfs has to be enabled to start service udev
Setting up libssl1.1:arm64 (1.1.0f-3+deb9u2) ...
Setting up openssl (1.1.0f-3+deb9u2) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for dbus (1.10.26-0+deb9u1) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Setting up libpam-systemd:arm64 (232-25+deb9u3) ...
Setting up libssl-dev:arm64 (1.1.0f-3+deb9u2) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.4.124-rk3328
update-initramfs: Converting to u-boot format
Processing triggers for libc-bin (2.24-11+deb9u3) ...
root@rock64:~# sudo reboot now

Ill restart minicom (still haven't figured out how to do this without rebooting the whole machine) and run it with an output to file so I can show you the log.

 

EDIT: Working again after taking power off, time to do some testing :)

Share this post


Link to post
Share on other sites
11 hours ago, MunkeyBalls said:

and could use some help.

 

Not possible. You are not listening and reading what is written. Everything you claim, it is not working, works.  If you are a noob why are you installing a kernel that is not fully compatible? Where did we put such instructions? If you are using armbian, you should only use kernels we prepare ... of course you can use other (compatible) kernels, but in that case, you have to understand what you are doing.

This forum is support for armbian builds, anything else is ignored. We don't support any 3rd party kernels since supporting own creations is already expensive enough. All this is written in the documentation, which is written with a reason that we don't waste time repeating things over and over again.

 

Again.  This is your first start: https://docs.armbian.com/

Share this post


Link to post
Share on other sites
1 minute ago, Igor said:

 

Thanks for your answer.

 

My intention is to build a custom version of those images. Those images are tested, so I know that they boot, now I would like to know how to build exactly that image so I can add my own userpatches/customize-image.sh as I have done in the past with the odroid HC1.

 

I probably need the armbian repo commit that builds those images (I am interested in the Stretch one), and also the build parameters, for instance


 

BOARD=rock64
BRANCH=default
KERNEL_ONLY=no
KERNEL_CONFIGURE=no
RELEASE=stretch
BUILD_DESKTOP=no

I could not find this information, I apologize if I it's there somewhere and I haven't seen it.

 

Thanks

 

Share this post


Link to post
Share on other sites
1 minute ago, nachoparker said:

I could not find this information, I apologize if I it's there somewhere and I haven't seen it.


This image is officially still WIP/testing phase. Add parameter EXPERT=yes 

Share this post


Link to post
Share on other sites
2 hours ago, Igor said:

 

Not possible. You are not listening and reading what is written. Everything you claim, it is not working, works.  If you are a noob why are you installing a kernel that is not fully compatible? Where did we put such instructions? If you are using armbian, you should only use kernels we prepare ... of course you can use other (compatible) kernels, but in that case, you have to understand what you are doing.

This forum is support for armbian builds, anything else is ignored. We don't support any 3rd party kernels since supporting own creations is already expensive enough. All this is written in the documentation, which is written with a reason that we don't waste time repeating things over and over again.

 

Again.  This is your first start: https://docs.armbian.com/

 

I read the guide, didn't install any kernels only tried booting another image to try out and figure what was going wrong.

The reason the image didn't boot was because I still had the emmc card in the Rock64 and somehow even though it boots the image from the SDCard it uses the kernel from the emmc.

I'm sorry if this is common knowledge but I still can't find that anywhere in the docs, I thought it was possible to dual boot on the device.

Share this post


Link to post
Share on other sites
1 hour ago, MunkeyBalls said:

The reason the image didn't boot was because I still had the emmc card in the Rock64 and somehow even though it boots the image from the SDCard it uses the kernel from the emmc.


Aha. This is a problem of a system which is on eMMC. 

This device is not officially supported yet so you won't find a lot of specifics information yet. I tried eMMC install (with our general install tool  called nand-sata-install or from armbian-config) and it is broken, but boot from SPI works ...

 

There are rough edges and that's why we keep this image labeled WIP.

Share this post


Link to post
Share on other sites
29 minutes ago, Igor said:


Aha. This is a problem of a system which is on eMMC. 

This device is not officially supported yet so you won't find a lot of specifics information yet. I tried eMMC install (with our general install tool  called nand-sata-install or from armbian-config) and it is broken, but boot from SPI works ...

 

There are rough edges and that's why we keep this image labeled WIP.

 

I know it's a WIP and it's ok to run into problems, but try and keep that in mind when people run into problems. You came off as a bit hostile while I'm only trying to see if someone with more experience had an idea what was going on.

I appreciate the work you guys put into making this for the community for free, keep it the awesome work!

Share this post


Link to post
Share on other sites

No problem, at least we find the source of troubles. My hostile reaction was due to the fact you were technically not running Armbian at all, claiming it doesn't run and asking for help even we actually dont provide any support for this kind of builds. :)

Wrote on mobile

Share this post


Link to post
Share on other sites
4 minutes ago, q-bert said:

Is AES / crypto enabled?

 

btw. We have some special features on our site called: SEARCH

search.jpg.5549006196a9e503c95455e89ff022a5.jpg

 

an amazing tool to find informations about the things you search for... ;) 

 

Share this post


Link to post
Share on other sites
18 minutes ago, chwe said:

 

btw. We have some special features on our site called: SEARCH

search.jpg.5549006196a9e503c95455e89ff022a5.jpg

 

an amazing tool to find informations about the things you search for... ;) 

 

 

18 minutes ago, chwe said:

 

btw. We have some special features on our site called: SEARCH

search.jpg.5549006196a9e503c95455e89ff022a5.jpg

 

an amazing tool to find informations about the things you search for... ;) 

 

 

Quote

 

 

Share this post


Link to post
Share on other sites

I should have been more specific: Is AES/Crypto enabled and what are the CPU and RAM clock rates using Armbian's latest nightly Rock images?
I used the search functionality and read the quoted threads weeks ago. But I also tried several of Ayufan's and also Dietpi Rock64 images and with some AES/Crypto was disabled... I did not ask if this board supports it or not.

Share this post


Link to post
Share on other sites
18 minutes ago, q-bert said:

I should have been more specific: Is AES/Crypto enabled and what are the CPU and RAM clock rates using Armbian's latest nightly Rock images?


I would need to download and burn the image to be sure I am telling you correct info, but you can do that on your own as well.
 

18 minutes ago, q-bert said:

But I also tried several of Ayufan's and also Dietpi Rock64 images and with some AES/Crypto was disabled


Waste of time. Dietpi is a BASH creation on top of Ayufan image. 

 

Download Armbian and see what's in and what's missing. If something is missing and only need to be enabled ... no problem. Submit a patch (to this file) and the very next day this feature is enabled in a (beta/nightly) repository.

Share this post


Link to post
Share on other sites

As far as I see, AES should be enabled by default no matter which kernel you use (dev or default). 

 

https://github.com/armbian/build/blob/1034f68ff0f4e6f4c864f2f53958ca65aa6d693e/config/kernel/linux-rk3328-dev.config#L4778

https://github.com/armbian/build/blob/1034f68ff0f4e6f4c864f2f53958ca65aa6d693e/config/kernel/linux-rk3328-default.config#L5737

 

but as Igor suggested, testing might be much faster than waiting until someone has confirmed it. Especially when you have tested other images the efforts to test Armbians nightly is a minor effort.. 

 

 

 

Share this post


Link to post
Share on other sites
9 minutes ago, Igor said:


I would need to download and burn the image to be sure I am telling you correct info, but you can do that on your own as well.
 


Waste of time. Dietpi is a BASH creation on top of Ayufan image. 

 

Download Armbian and see what's in and what's missing. If something is missing and only need to be enabled ... no problem. Submit a patch (to this file) and the very next day this feature is enabled in a (beta/nightly) repository.

Thanks Igor. I was hoping someone already did that and would share his experience in this thread.

Share this post


Link to post
Share on other sites
1 minute ago, chwe said:

As far as I see, AES should be enabled by default no matter which kernel you use (dev or default). 

 

https://github.com/armbian/build/blob/1034f68ff0f4e6f4c864f2f53958ca65aa6d693e/config/kernel/linux-rk3328-dev.config#L4778

https://github.com/armbian/build/blob/1034f68ff0f4e6f4c864f2f53958ca65aa6d693e/config/kernel/linux-rk3328-default.config#L5737

 

but as Igor suggested, testing might be much faster than waiting until someone has confirmed it. Especially when you have tested other images the efforts to test Armbians nightly is a minor effort.. 

 

 

 

Thanks, that helps me a lot. Where do you set CPU and RAM clock speeds for you build process / images? Is that set in the bootloader / uboot?

Share this post


Link to post
Share on other sites
On 11.4.2018 at 3:37 PM, Igor said:


This device is not officially supported yet so you won't find a lot of specifics information yet. I tried eMMC install (with our general install tool  called nand-sata-install or from armbian-config) and it is broken, but boot from SPI works ...

 

Hi Igor, I can confirm this issue.

last week I had to reinstall armbian and it won't start. After installing to eMMC from an SD card via armbian-config, removing the card and rebooting - there was apparently nothing.

A ping to the Rock64 was possible, but nothing else.

 

I tried a lot, even some more images I had downloaded earlier. 

The first one (out of my downloads) that worked was Armbian_5.32.170919_Rock64_Ubuntu_xenial_default_4.4.77.img

armbian-config wasn't supplied, but was automatically installed when calling the command 

sudo armbian-config

After moving to eMMC and removing the SD-Card all worked well, even all updates and upgrades.

 

Hope this may help a little on searching (and finding) the reason for it.

 

EDIT:

I was told that installing the image directly to the eMMC using an USB-to-eMMC Adapter will produce a bootable Armbian

 

Greets

Rainer

Share this post


Link to post
Share on other sites

Hi Igor,

On 14.4.2018 at 7:58 PM, Igor said:

Will show up in next nightly update.

Thank you, in Armbian_5.43.180415_Rock64_Debian_stretch_dev_4.16.0-rc6.img it works again!

 

Greetz

Rainer

Share this post


Link to post
Share on other sites

Yesterday I downloaded the latest "Debian desktop" image (it should be 5.42) linked here
https://www.armbian.com/rock64/

but I'm still having the error reported below.

 

I have never been able to run a version of Armbian on my Rock 64 (1GB version) :( .

I'm currently using Armbian (Debian) on an Orange Pi+ without any problem.

 

What's the problem? Can someone help me please?

 

Welcome to minicom 2.7.1

OPTIONS: I18n                                                                
Compiled on Aug 13 2017, 15:25:34.                                           
Port /dev/ttyUSB0, 20:57:55                                                  
                                                                             
Press CTRL-A Z for help on special keys                                      
                                                                             
DDR version 1.06 20170424                                                    
In                                                                           
LPDDR3                                                                       
786MHz                                                                       
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB          
ddrconfig:1                             
OUT                                     
                                        
U-Boot SPL 2017.09-g5a90a9a (Jan 12 2018 - 11:06:01)
setup_ddr_param  1                      
booted from SPI flash                   
Trying to boot from SPI
NOTICE:  BL31: v1.3(release):f947c7e
NOTICE:  BL31: Built : 11:06:00, Jan 12 2018
NOTICE:  BL31:Rockchip release version: v1.3


U-Boot 2017.09-g5a90a9a (Jan 12 2018 - 11:06:15 +0000), Build: jenkins-linux-build-rock-64-177

Model: Pine64 Rock64
DRAM:  1022 MiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
*** Warning - bad CRC, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=55524b503039303038000000000d2b11
serial=ea6ec868699cad5
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
mmc_init: -95, time 9
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2960 bytes read in 27 ms (106.4 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
112 bytes read in 21 ms (4.9 KiB/s)
"Synchronous Abort" handler, esr 0x96000210
ELR:     3ff77944
LR:      3ff75eb0
x0 : 000000003df2e9b0 x1 : 0000000044000000
x2 : 0000000000000070 x3 : 0000000000000000
x4 : 0000000000000070 x5 : 000000000000000e
x6 : 0000000000000000 x7 : 0000000000000000
x8 : 0000000000000000 x9 : 0000000000000008
x10: 000000003df2e9c0 x11: 000000003df13b70
x12: 0000000000000000 x13: 0000000000000200
x14: 000000003df04bfc x15: 00000000ffffffff
x16: 0000000060df18a6 x17: 0000000070a12210
x18: 000000003df0ce08 x19: 0000000000000000
x20: 0000000000000070 x21: 0000000044000000
x22: 000000003df2e9b0 x23: 000000003ffa0118
x24: 0000000000000000 x25: 0000000000000000
x26: 000000000000000a x27: 0000000000000001
x28: 0000000000000000 x29: 000000003df02b10

Resetting CPU ...

DDR version 1.06 20170424
In
SRX
LPDDR3
786MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
ddrconfig:1
OUT

U-Boot SPL 2017.09-g5a90a9a (Jan 12 2018 - 11:06:01)
setup_ddr_param  1
booted from SPI flash
Trying to boot from SPI
NOTICE:  BL31: v1.3(release):f947c7e
NOTICE:  BL31: Built : 11:06:00, Jan 12 2018
NOTICE:  BL31:Rockchip release version: v1.3


U-Boot 2017.09-g5a90a9a (Jan 12 2018 - 11:06:15 +0000), Build: jenkins-linux-build-rock-64-177

Model: Pine64 Rock64
DRAM:  1022 MiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
*** Warning - bad CRC, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=55524b503039303038000000000d2b11
serial=ea6ec868699cad5
normal boot
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
mmc_init: -95, time 9
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2960 bytes read in 28 ms (102.5 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
112 bytes read in 22 ms (4.9 KiB/s)
"Synchronous Abort" handler, esr 0x96000210
ELR:     3ff77944
LR:      3ff75eb0
x0 : 000000003df2e9d0 x1 : 0000000044000000
x2 : 0000000000000070 x3 : 0000000000000000
x4 : 0000000000000070 x5 : 000000000000000e
x6 : 0000000000000000 x7 : 0000000000000000
x8 : 0000000000000000 x9 : 0000000000000008
x10: 000000003df2e9e0 x11: 000000003df13b70
x12: 0000000000000000 x13: 0000000000000200
x14: 000000003df04bfc x15: 00000000ffffffff
x16: 0000000060df18a6 x17: 0000000070a12210
x18: 000000003df0ce08 x19: 0000000000000000
x20: 0000000000000070 x21: 0000000044000000
x22: 000000003df2e9d0 x23: 000000003ffa0118
x24: 0000000000000000 x25: 0000000000000000
x26: 000000000000000a x27: 0000000000000001
x28: 0000000000000000 x29: 000000003df02b10

Resetting CPU ...

 

Share this post


Link to post
Share on other sites

finally had some time to flash Armbian_5.43.180423_Rock64_Debian_stretch_dev_4.16.0-rc6:

 

root@rock64:/share# openssl speed -elapsed -evp aes-256-cbc

 

type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes

aes-256-cbc      82888.98k   235948.63k   427434.41k   550766.25k   600880.47k   604788.05k

 

 

Share this post


Link to post
Share on other sites

Hi guys,  same problem here as matteobp 2 messages up, Rock64 1GB in boot loop ( same output found on UART )

I tried 2 1GB Rock64 devices, both same problem.

 

Believe me, I know how to install Armbian on Banana/Orange pi and loving it :-). using etcher etc.

I have over 20+ running using Docker, TvHeadEnd, SATIP, NodeRed MySQL servers, etc etc.

 

The Pine bionic-minimal-rock64-0.6.44-239-armhf.img works

The Pine OMV from works ( nice and fast file transfer, 80MBps, and with usb 3.0 hub, got my 4 HDD NAS working.)

 

But I want Armbian naturally on all Pis ( OK not Raspberry, I understand and agree )

 

I tried 8 Armbian images so far, but all failed.

Coming days I can try more if not all ;-( to see if one does work )

 

I see above, that Igor says, the standard images work for him, but perhaps he is not using the 1GB Rock64 ?

Could that be the problem ? I had 2 times, that minicom stopped after "DRAM" and no size, but stopped.

 

Is there newer / older hardware ? My board says : Rock64 V2.0 2017-0713

no eMMC fitted, no jumper ( tried with, no success either)

 

I tried the current images (https://www.armbian.com/rock64/) and Armbian_5.46.180602_Rock64_Debian_stretch_dev_4.17.0-rc6.img and a few others

No succes.

 

Please dont get me using Rock64 without Armbian ;-)

 

Share this post


Link to post
Share on other sites
3 hours ago, Set3 said:

I see above, that Igor says, the standard images work for him, but perhaps he is not using the 1GB Rock64 ?


Mine has 4GB. 

If I understand correctly, there is a problem already before u-boot? But Xenial image with kernel 4.4.y works?

Share this post


Link to post
Share on other sites

Hi Igor, It was late yesterday, so just to be sure I was not dreaming, I did a restart :

I use Rock64 to replace Orange Pi 2E Plus as headless server with Docker as a platform for multiple applications, and looking at memory usage before, I saw no need for more than 1GB to be honest.


I use 5V2A and 5V3A supply, a few Samsung 16GB Evo+, etcher, that work fine with OrangePi

I have 2 Rock64 1GB, and used the current images from https://www.armbian.com/rock64/

 

None of these 3 work on either of the 2 sbc-s :

1. Armbian_5.42_Rock64_Debian_stretch_default_4.4.124_desktop

2. Armbian_5.42_Rock64_Ubuntu_xenial_default_4.4.124.img

3. Armbian_5.44.180515_Rock64_Ubuntu_bionic_dev_4.17.0-rc3.img

 

After testing with Armbian, I used the Pine64 bionic-minimal-rock64-0.6.44-239-armhf.img on the same SD card, sbc, supply, and that boots and seems to work fine on HDMI and ssh.

 

Let me know if you need more info / testing.

 

Results :

So I see "Found U-Boot script /boot/boot.scr" but before that there are also errors/warnings, but I am not sure if that is supposed to be like that.

 

I think the output is the same, but for completeness :

1.

Spoiler

DDR version 1.06 20170424
In
SRX
LPDDR3
786MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
ddrconfig:1
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, 189
emmc reinit
emmc reinit
SdmmcInit=2 20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=15304MB
FwPartOffset=2000 , 0
StorageInit ok = 49256
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xa4cf8
RunBL31 0x10000
NOTICE:  BL31: v1.3(debug):f947c7e
NOTICE:  BL31: Built : 18:38:03, Mar 12 2018
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initialized
INFO:    Using rkfiq sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

 

U-Boot 2017.09-armbian (Mar 28 2018 - 17:14:43 +0200)

Model: Pine64 Rock64
DRAM:  1022 MiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
*** Warning - bad CRC, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=xxx
serial=xxx
normal boot
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
mmc_init: -95, time 9
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2960 bytes read in 27 ms (106.4 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
112 bytes read in 21 ms (4.9 KiB/s)
"Synchronous Abort" handler, esr 0x96000210
ELR:     3ff77168
LR:      3ff75700
x0 : 000000003df2d9d0 x1 : 0000000044000000
x2 : 0000000000000070 x3 : 0000000000000000
x4 : 000000000000000e x5 : 0000000000000070
x6 : 0000000000000000 x7 : 0000000000000000
x8 : 0000000000000044 x9 : 0000000000000008
x10: 000000003df2d9e0 x11: 000000003df12b70
x12: 0000000000000000 x13: 0000000000000200
x14: 000000003df03bfc x15: 00000000ffffffff
x16: 000000008d1bcd85 x17: 00000000605202c9
x18: 000000003df0be08 x19: 0000000000000000
x20: 0000000044000000 x21: 000000003df2d9d0
x22: 000000003ff9f7b0 x23: 0000000000000000
x24: 0000000000000000 x25: 000000000000000a
x26: 0000000000000001 x27: 0000000000000070
x28: 0000000000000000 x29: 000000003df01b10

Resetting CPU ...


and repeats

2.

Spoiler


DDR version 1.06 20170424
In
SRX
LPDDR3
786MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
ddrconfig:1
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, 188
emmc reinit
emmc reinit
SdmmcInit=2 20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=15279MB
FwPartOffset=2000 , 0
StorageInit ok = 49099
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0xa4cf8
RunBL31 0x10000
NOTICE:  BL31: v1.3(debug):f947c7e
NOTICE:  BL31: Built : 18:38:03, Mar 12 2018
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initialized
INFO:    Using rkfiq sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

 

U-Boot 2017.09-armbian (Mar 28 2018 - 17:14:43 +0200)

Model: Pine64 Rock64
DRAM:  1022 MiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
*** Warning - bad CRC, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=xxx
serial=xxx
normal boot
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
mmc_init: -95, time 10
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2960 bytes read in 34 ms (85 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
112 bytes read in 28 ms (3.9 KiB/s)
"Synchronous Abort" handler, esr 0x96000210
ELR:     3ff77168
LR:      3ff75700
x0 : 000000003df2d9d0 x1 : 0000000044000000
x2 : 0000000000000070 x3 : 0000000000000000
x4 : 000000000000000e x5 : 0000000000000070
x6 : 0000000000000000 x7 : 0000000000000000
x8 : 0000000000000044 x9 : 0000000000000008
x10: 000000003df2d9e0 x11: 000000003df12b70
x12: 0000000000000000 x13: 0000000000000200
x14: 000000003df03bfc x15: 00000000ffffffff
x16: 000000008d1bcd85 x17: 00000000605202c9
x18: 000000003df0be08 x19: 0000000000000000
x20: 0000000044000000 x21: 000000003df2d9d0
x22: 000000003ff9f7b0 x23: 0000000000000000
x24: 0000000000000000 x25: 000000000000000a
x26: 0000000000000001 x27: 0000000000000070
x28: 0000000000000000 x29: 000000003df01b10

Resetting CPU ...

 

and repeats

3.

Spoiler

DDR version 1.06 20170424
In
SRX
LPDDR3
786MHz
Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB
ddrconfig:1
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, 189
emmc reinit
emmc reinit
SdmmcInit=2 20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=15279MB
FwPartOffset=2000 , 0
StorageInit ok = 49100
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0x97af0
RunBL31 0x10000
NOTICE:  BL31: v1.3(debug):f947c7e
NOTICE:  BL31: Built : 18:38:03, Mar 12 2018
NOTICE:  BL31:Rockchip release version: v1.3
INFO:    ARM GICv2 driver initialized
INFO:    Using rkfiq sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe
INFO:    BL31: Initializing runtime services
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

 

U-Boot 2018.01-rc2-armbian (May 14 2018 - 20:13:51 +0200)

Model: Pine64 Rock64
DRAM:  1022 MiB
MMC:   rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
*** Warning - bad CRC, using default environment

In:    serial@ff130000
Out:   serial@ff130000
Err:   serial@ff130000
Model: Pine64 Rock64
Net:   eth0: ethernet@ff540000
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
mmc_init: -95, time 10
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2958 bytes read in 34 ms (85 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
113 bytes read in 28 ms (3.9 KiB/s)
"Synchronous Abort" handler, esr 0x96000210
ELR:     25e348
LR:      25c994
x0 : 000000003df3bc80 x1 : 0000000044000000
x2 : 0000000000000071 x3 : 0000000000000000
x4 : 000000000000000e x5 : 0000000000000070
x6 : 0000000000000048 x7 : 000000003ffa2560
x8 : 0000000000000044 x9 : 0000000000000008
x10: 000000003df3bc80 x11: 000000003df20d70
x12: 0000000000000000 x13: 0000000000000200
x14: 000000003df130bc x15: 00000000ffffffff
x16: 000000008d1bcd85 x17: 00000000605202c9
x18: 000000003df1ae10 x19: 0000000000000000
x20: 0000000044000000 x21: 000000003df3bc80
x22: 000000003ffa43f8 x23: 0000000000000000
x24: 0000000000000000 x25: 000000000000000a
x26: 0000000000000001 x27: 0000000000000071
x28: 0000000000000000 x29: 000000003df10fd0

Resetting CPU ...

 

and repeats

 

Share this post


Link to post
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
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.

Loading...
5 5