Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I got a few Rock64 boards on discount and have been playing around with them. These are buggy factory seconds, but at least one of them is turning out to be quite reliable. Anyway, here are some fresh kernel packages in case anyone wants to upgrade:
However, that is almost 2 months old. All of my recent attempts to build a new image for this board result in a non-booting image, black screen at boot, zero error messages, similar to what we were seeing on the Pinebook. Maybe a similar issue?
I think you said you have one of these boards, so you can check for yourself if you like. Mine is a v2 (bad ethernet, etc), is yours a v2 or v3? Just curious...
switched ATF to original project, now everything works.
Code:
U-Boot TPL 2020.07-rk3328 (Aug 13 2020 - 20:12:29)
LPDDR3, 800MHz
BW=32 Col=11 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=4096MB
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2020.07-rk3328 (Aug 13 2020 - 20:12:29 +0300)
Trying to boot from MMC1
NOTICE: BL31: v2.3():v2.3
NOTICE: BL31: Built : 20:12:03, Aug 13 2020
NOTICE: BL31:Rockchip release version: v1.2
U-Boot 2020.07-rk3328 (Aug 13 2020 - 20:15:21 +0300)
Model: Pine64 Rock64
DRAM: 4 GiB
PMIC: RK8050 (on=0x50, off=0x01)
MMC: mmc@ff500000: 1, mmc@ff520000: 0
Loading Environment from MMC... *** 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!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
1485 bytes read in 4 ms (362.3 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
51 bytes read in 4 ms (11.7 KiB/s)
52005 bytes read in 8 ms (6.2 MiB/s)
23982592 bytes read in 1043 ms (21.9 MiB/s)
8925542 bytes read in 391 ms (21.8 MiB/s)
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 8925478 Bytes = 8.5 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 fc6a0000, end fcf23126 ... OK
Loading Device Tree to 00000000fc62a000, end 00000000fc69ffff ... OK
Starting kernel ...
=======================================================================
if you want to transfer the system to SD card to internal memory (eMMC or NAND),
follow setup
login: root
password: password
=======================================================================
Slackware GNU/Linux (ttyS2)
Kernel 5.7.15 (aarch64)
rock64 login:
Ok, I tried both of these, and I cannot boot either of my spare Rock64 boards. There is definitely a firmware issue, when the card starts to boot, the red and white activity lights on the board start blinking intermittently and sporadically. The red light seems to blink rhythmically, but the white light is all over the place, sometimes getting extremely bright. Both lights are usually steady and non-blinking on my stable image. Nothing is ever put out to HDMI, and I still do not have UART of any kind (soon though). I do not think it makes it to the u-boot stage.
I am guessing there is a voltage issue, somehow. You did not notice it on your boards? I tested it on two identical boards here, got the same result.
I tried to shoot video of the crazy lights, but my camera is not good enough to show the detail, the lights get washed out.
I will try a few other things, but I am pretty sure these need different ATF, possibly.
thanks.
Last edited by shelldweller; 08-16-2020 at 06:24 PM.
Ok, I tried both of these, and I cannot boot either of my spare Rock64 boards. There is definitely a firmware issue, when the card starts to boot, the red and white activity lights on the board start blinking intermittently and sporadically. The red light seems to blink rhythmically, but the white light is all over the place, sometimes getting extremely bright. Both lights are usually steady and non-blinking on my stable image. Nothing is ever put out to HDMI, and I still do not have UART of any kind (soon though). I do not think it makes it to the u-boot stage.
So, I checked, after writing to the card at the first start, there was a problem all the indicators lit up and nothing was output to HDMI. after the reset button, the booting always took place normally with the output to HDMI.
a red led indicates that the loading has gone further u-boot, this is a hearbeat. the white led is reading data from the SDcard, the more intense the brighter. Apparently, you boot normally, it is not clear why it does not display on the screen, try disconnecting and reconnecting the HDMI cable during boot.
also tell me the revision of your boards.
So, I checked, after writing to the card at the first start, there was a problem all the indicators lit up and nothing was output to HDMI. after the reset button, the booting always took place normally with the output to HDMI.
a red led indicates that the loading has gone further u-boot, this is a heartbeat. the white led is reading data from the SDcard, the more intense the brighter. Apparently, you boot normally, it is not clear why it does not display on the screen, try disconnecting and reconnecting the HDMI cable during boot.
also tell me the revision of your boards.
Okay, finally had a short break from work... I tried pressing the reset button (I tried all three buttons actually), and it does reset, but the same erratic white blinking starts and nothing is ever put out to HDMI. This is true even if I reset the unit multiple times. I also tried disconnecting/reconnecting the HDMI cable. The monitor sees a device, but gets no output signal.
My board is revision v2.0, just like yours. I have two v2.0 boards I am testing with actually, and both give the same results. I actually have four of these: two are identical, one has a working ethernet (even though most v2.0 ethernet does not work), and one was completely DOA and would only spit out error messages no matter what I tried to boot. Maybe I will try out the third one with the working ethernet, but that runs full time as a mini-server, so I would rather not disturb it. I might though, if I get curious enough.
I tested my working image: both boards boot and NONE of the lights EVER blink. I just verified that right now. Even the red light stays solid. So if it supposed to be a heartbeat, it is not beating on the working image for some reason.
Maybe something went wrong with the SD card, I will try writing the image to it again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
