Search the Community

Well I can confirm that the 155 image @igor provided works on my 4gb rock64, also. I admit that I only did the most basic of testing, loging in, running nano, ps and ls etc. Is there a specific command or test I should run to confirm all is as expected?

Is it simply not pingable, or is it just plain not booting? Can you give me the age of the Rock64 and the part number of the Ethernet chip? Power domains, time to reset/bring up the SD card might not be waiting long enough either (I think it simply waits default 10 ms, might need a little longer) Can everyone involved please give me the exact SD cards being used, or even pictures of them?

Hi everybody, I have experienced something very similar on my rock64. The HDMI output isn't working -- is this normal with the headless armbian? Also when starting the rock64 (most times on a soft reboot) with the armbian image, which is connected via ethernet -- it dosen't seem to use the ethernet connection. The rock is not pingable. Sometimes I have to hard reset the rock and/or to unplug the ethernet cable and replug it. Then it is pingable and I can connect via SSH. This behaviour is very annoying and I am running out of ideas. I am thankful for every idea. best regards

No worries, my rock64 is happy with all of my cards and various images, so I have a hard time verifying... And yes, I confused the boards, but the patches are to the dtsi, so should affect both builds equally. I noticed late last night the added clocks for rk3328 dw-mmc controller had one that I believe to be a typo (ciu-drv instead of ciu-drive), which is corrected in the Renegade dts. It involves phase correction/adjustment, I didn't think much of it since Rock64 doesn't have UHS capabilities to my knowledge and I thought the phase adjustments wouldn't be fooled with. I'll see if my board is complaining about it, fix it, and post it. (Should push to Ayufan)

I guess you mean in my Renegade, since I don't have a Rock64. Bad news is that today I traveled and won't be back home until Sunday. Will do then, G.w.

Hey there! I too am trying to get my 4gb rock64 to "work". I am willing to be added to the sample set. :) Thus, should I use this image? New image: https://dl.armbian.com/rock64/archive/test/Armbian_5.59_Rock64_Debian_stretch_default_4.4.155.7z

@Vin New image: https://dl.armbian.com/rock64/archive/test/Armbian_5.59_Rock64_Debian_stretch_default_4.4.155.7z

I didn't get any feedback on you about the HDMI hotplug, however on some favorable testing on a Renegade I've pushed a patch into the build system to set the drive levels on the SD to 8mA, up from 4mA. I don't have a failuyre to boot issue with my SD cards, supply and Rock64, however a sample size of 1 is not representative, and my conclusion was that bumping all rk3328 devices to 8mA was advisable. At @Igor's discretion this can be built for nightly or test.

Hi Thanks. Sorry for my typo on 3329. I mean 3399. Great to know about SOM204. But it will be long time to wait till 2019. Do you know how the performance of 3328 Boards like Rock64 for USB 3.0 Data? Regards.

Hello, Each time I'm booting the Rock64, it starts on Jan, 21 of 2016 but the filesystem has a superblock on Jan,28 of 2018, so in the future. It's inconsistant and the filesystem is checking each time and I'm waiting a few seconds. How can I avoid this trouble ? Here is the screen shot of logs through the tty/usb console. I'm booting from the spi flash and a sd-card with Ubuntu 18.04.1.

For the "Recover" button -> https://github.com/ayufan-rock64/linux-u-boot/commit/ea6efecdfecc57c853a6f32f78469d1b2417329b

Thank you very much for reply. I personally more biased with RockChip than Allwinner. However, I did checked the prices of CPU's but 3329 is very expensive and it gets exceed or target BoM cost that's why I am more like to use 3328. But surely I agree 3329 in current trend and resource, support is more rich. How will be to use 3328 you think and If I consider my development based on Pine64's Rock64 or Firefly's ROC-RK3328-CC? Regards.

@Igor if you've the time to humor the topic some more, the patch below is changing the pin drive levels to 8 mA from 4. I'm building a rock64 image now to test, of course I have the old board, I don't know if anything besides the ethernet has changed. I'll see if I can force modes and observe errors. kernel-rockchip64-default.patch

Hello All. I am fairly new in Embedded Linux and in this forum. I need to develop a small size IoT ARM Quad Core Board. I like to have some advise on my project's proper development path. First let me share my target needs of the project: -1. ARM CPU (run Linux) - I think for my project, Quad-Core is more than enough -2. RAM 1GB/2GB -3. eMMC 16GB for OS Boot -4. SD Card for file storage (up-to 512GB) -5. Two USB2.0 (One Host Mode and One Device Mode) and one USB3.0 (Only Host Mode is Ok. Its for faster file transfer to connected external Portable HDD) -6. Capacitive Touchscreen 3.5 Inch (as we will run some Python based GUI App) -7. Sensor connection via GPIO, UART, I2C, SPI (Sensors are Ambient Light, Sound, Motion PIR, 9-Axis MEMS Accelerometer, Gyro, Magnetometer) -8. Wireless including GPS, WiFi and Bluetooth 5.0 -9. Small Form factor (if find any Core CPU Module is great, else need to do custom PCB design) -10. Less heat generation Now based on the above spec USB 3.0 feature makes my choice very narrow as there are very few CPU supports USB 3.0. So far I am thinking about RK3328 or Allwinner H6. RK3339 will be great and more powerful but its very costly so don't wanted to use it. My ques are: - Based on my online research for start development I can use Orange Pi Lite 2 (in case of Allwinner H6) or Rock64 (for RK3328). But which one will be best choice for my project? In terms of implement features, easy of development, available online resource ... etc? - is there any Open Hardware project which I can consider as base of my study. All the available SBC's are open source and only Schematic is available. - Anyone know any small Core CPU Module (SMT or DPI) based on the H6 or RK3328)? Thanks. Looking forward your guideline. Regards.

Kernel changed back to the one used in that OMV image. https://dl.armbian.com/rock64/archive/test/Armbian_5.59_Rock64_Debian_stretch_default_4.4.154.7z

What about doing just this - back to "latest stable" according to Ayufan? --- a/config/sources/rockchip64.conf +++ b/config/sources/rockchip64.conf @@ -42,7 +42,7 @@ fi case $BRANCH in default) KERNELSOURCE='https://github.com/ayufan-rock64/linux-kernel' - KERNELBRANCH='tag:4.4.138-1094-rockchip-ayufan' + KERNELBRANCH='tag:4.4.132-1072-rockchip-ayufan' KERNELDIR='linux-rockchip64' KERNEL_USE_GCC='> 7.0' ;;

wrote the image on two different cards, waited approx. more than 5 Minutes for each and let the Rock64 run for the last try (more than 30 Minutes) how do i add this line, files are write protected, also cannot extract the iso

Try this one: https://dl.armbian.com/rock64/archive/test/Armbian_5.59_Rock64_Debian_stretch_default_4.4.154.7z

I am running the exact same image and its working fine. My Rock64 is also 4Gb version ... The only suspicious things are those two patches which might be absent in OMV since we add them recently: https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-default/enable-1392mhz-opp.patch https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-default/enable-1512mhz-opp.patch I can provide you test image if you like to try?

Yes I assumed its based on the Debian armbian image, but this makes it also very odd since its booting up on the same hardware setup. I used the current images from https://dl.armbian.com/rock64/ Armbian_5.59_Rock64_Debian_stretch_default_4.4.152_desktop Armbian_5.59_Rock64_Ubuntu_bionic_default_4.4.152 OMV Image stretch-openmediavault-rock64-0.7.8-1061-arm64.img Used the same HDMI, LAN and Power supply cable, yes

Which is made on top of Armbian. Almost all images are tested and networking is always checked. My report confirms that it is working: https://github.com/armbian/testings/blob/master/rock64-default.report Are you always use the same cables? Which is a version of your images? Which kernel is used in OMV, which on Armbian ...

Hello everybody, bought a Rock64 4 GB recently and I´m not able to boot it with any provided armbian Debian/Ubuntu image. With the Ubuntu Image ethernet doesnt seem to be initialized and with Debian there is activity on the eth port, but no connection, neither of the images show any output on the screen. Also i tried various SD-Cards and different image burning programs. Openmediavault works flawlessly, so I can exclude Hardware issues.

I am trying to build an Image for the Rockpro but i am allways getting an Error when it comes to compile U-boot (did not make any Changes so far): Displaying message: Preparing host info Displaying message: Build host OS release bionic info Displaying message: Syncing clock host info ## BUILD SCRIPT ENVIRONMENT Repository: https://github.com/armbian/build Version: 46340a24 Host OS: bionic Host arch: amd64 Host system: Linux ek-desktop 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Virtualization type: none ## Build script directories Build directory is located on: TARGET SOURCE FSTYPE AVAIL /home /dev/sda1 ext4 319,9G Build directory permissions: # file: /home/ek/build # owner: ek # group: ek user::rwx group::rwx other::r-x Temp directory permissions: # file: /home/ek/build/.tmp # owner: root # group: root user::rwx group::rwx other::r-x ## BUILD CONFIGURATION Build target: Board: rockpro64 Branch: default Desktop: yes Kernel configuration: Repository: https://github.com/ayufan-rock64/linux-kernel Branch: tag:4.4.138-1094-rockchip-ayufan Config file: linux-rockchip64-default U-boot configuration: Repository: https://github.com/ayufan-rock64/linux-u-boot Branch: branch:rockchip-master Config file: rockpro64-rk3399_defconfig Partitioning configuration: Root partition type: ext4 Boot partition type: (none) User provided boot partition size: 0 Offset: 16 CPU configuration: 600000 - 1900000 with ondemand Displaying message: Downloading sources info Displaying message: Checking git sources u-boot-rockchip64 rockchip-master info Displaying message: Checking out Displaying message: Checking git sources linux-rockchip64 4.4.138-1094-rockchip-ayufan info Displaying message: Up to date Displaying message: Checking git sources arm-trusted-firmware-rockchip64 rockchip info Displaying message: Up to date Displaying message: Checking git sources sunxi-tools master info Displaying message: Up to date Displaying message: Checking git sources rkbin-tools master info Displaying message: Up to date Displaying message: Checking git sources marvell-tools A3700_utils-armada-17.10 info Displaying message: Up to date Displaying message: Checking git sources odroidc2-blobs master info Displaying message: Up to date Displaying message: Checking git sources testing-reports master info Displaying message: Up to date Displaying message: Cleaning output/debs for rockpro64 default info Displaying message: Cleaning arm-trusted-firmware-rockchip64/rockchip info Displaying message: Compiling ATF info Displaying message: Compiler version aarch64-linux-gnu-gcc 6.4.1 info Displaying message: Started patching process for atf rockchip64-rockpro64-default info Displaying message: Looking for user patches in userpatches/atf/atf-rockchip64 info Displaying message: * [\e[32ml\e[0m][\e[35mb\e[0m] add-trust-ini.patch info Displaying message: Cleaning u-boot-rockchip64/rockchip-master info Displaying message: Compiling u-boot 2017.09 info Displaying message: Compiler version aarch64-linux-gnu-gcc 7.2.1 info Displaying message: Checking out sources Displaying message: Cleaning u-boot-rockchip64/rockchip-master info Displaying message: Started patching process for u-boot rockchip64-rockpro64-default info Displaying message: Looking for user patches in userpatches/u-boot/u-boot-rockchip64-default info Displaying message: * [\e[32ml\e[0m][\e[32mc\e[0m] add_fdtfile_dt_overlays.patch info Displaying message: ERROR in function compile_uboot compilation.sh:185 err Displaying message: U-boot file not found idbloader.bin err Displaying message: Process terminated info Trying to build an Image for the PineH64 does not work either: Displaying message: Preparing host info Displaying message: Build host OS release bionic info Displaying message: Syncing clock host info Displaying message: ERROR in function source main.sh:188 err Displaying message: No kernel branch selected err Displaying message: Process terminated info

Maybe... I have found out on this thread that the RTC is not located inside the CPU but in a RK805 This RTC has neither a battery nor a crystal, so it cannot be used while the board is off, as I read on this page: So I would need an external RTC if I wanted to use rtcwake with off or suspend-to-disk options. Still, in suspend-to-ram, the LEDs turned on again, so apparently, the RTC works in suspend-to-ram mode. In the log it says Sep 2 12:32:25 nextcloudplus kernel: [ 1.431242] rk808-rtc rk808-rtc: rtc core: registered rk808-rtc as rtc0 Sep 2 12:32:25 nextcloudplus kernel: [ 1.432090] rk3x-i2c ff160000.i2c: Initialized RK3xxx I2C bus at ffffff8009bf8000 so the on-board RTC is at least registered somewhere. I don't know whether 'nextcloudplus kernel' is the linux kernel in disguise, but apparently, it handles the RTC. Maybe I will have to see what happens if I have a monitor connected to my rock64.

Show command output on PC "fdisk -l" to SD card with the image xenial-minimal-rock64-0.5.15-136-arm64.img Have you tried to move the boot loader from SD card xenial-minimal-rock64-0.5.15-136-arm64 to SD card with Armbian 5.59 ?