I have seen many problems with the Rock64 v3 in the last few days.
Many customers have told me that existing Rock64 images suddenly no longer boot in v3.
We have verified this and found that apparently v3 can not cope with many SD cards. The booting of eMMC goes without problems.
If a customer has bought a new v3 and nothing works, contact us, we will send you an emmc card for the purchase price without any profit.
markus@humberg.de
Stickied and being looked into. How many others are experiencing issues?
05-08-2019, 09:49 AM
(This post was last modified: 05-16-2019, 01:21 AM by Leapo.)
From what I've heard, the issue is that GPIO0_D6 (SDMMC0_PWREN) is left floating by current Linux devicetree configurations, but needs to be set to high or low in order to select an appropriate SDCard voltage.
You can solder a connection between test pad 2302 and 3.3v to revert your Rev3 board's SD-Card slot to Rev2 behavior, which should work with all cards.
If you have a UHS-capable MicroSD card, you can solder a connection between test pad 2303 and ground to force the slot into UHS mode.
Edit: The test pad can be located on the back of the PCB, near the center. I've highlighted it in this drawing, in red: https://i.imgur.com/F9BCSkj.png
Issue has been identified and solved. New images from mrfixit2001 and ayufan will have the fix.
(05-10-2019, 06:03 AM)Luke Wrote: Issue has been identified and solved. New images from mrfixit2001 and ayufan will have the fix.
I have upload the mrfixit200 debian image that works with Rock64 v3 to file server and here is the download link: http://files.pine64.org/os/ROCK64/v3/roc...9_2.img.xz
(05-12-2019, 03:22 PM)tllim Wrote: (05-10-2019, 06:03 AM)Luke Wrote: Issue has been identified and solved. New images from mrfixit2001 and ayufan will have the fix.
I have upload the mrfixit200 debian image that works with Rock64 v3 to file server and here is the download link: http://files.pine64.org/os/ROCK64/v3/roc...9_2.img.xz
My bootlog with this image, after the loading kernel message it sits flashing the power LED twice per second and no more output or network activity.
Have tried a few different SD cards from 16GB to 64GB, all Class 10/UHS1.
Code: DDR version 1.13 20180428
ID:0x805 N
In
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
Boot1 Release Time: Feb 2 2018 15:41:39, version: 2.46
ChipType = 0x11, 143
SdmmcInit=2 0
BootCapSize=0
UserCapSize=0MB
FwPartOffset=2000 , 0
SdmmcInit=0 0
BootCapSize=0
UserCapSize=60952MB
FwPartOffset=2000 , 0
StorageInit ok = 24000
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=0xa3d00
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):9d3f591
NOTICE: BL31: Built : 14:39:02, Jan 17 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2017.09 (May 09 2019 - 11:48:17 -0400)
Model: Rockchip RK3328 EVB
DRAM: 4 GiB
Sysmem: init
Relocation Offset is: fed15000
I2c speed: 400000Hz
PMIC: RK8050 (on=0x02, off=0x01)
vdd_logic 1100000 uV
vdd_arm 1100000 uV
MMC: rksdmmc@ff500000: 1, rksdmmc@ff520000: 0
*** Warning - bad CRC, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Rockchip RK3328 EVB
switch to partitions #0, OK
mmc1 is current device
Unknown command 'rkimgtest' - try 'help'
Card did not respond to voltage select!
mmc_init: -95, time 9
Unknown command 'rknand' - try 'help'
Unknown command 'rksfc' - try 'help'
Unknown command 'rksfc' - try 'help'
Bootdev: mmc 0
CLK: (sync kernel. arm: enter 600000 KHz, init 600000 KHz, kernel 0N/A)
apll 400000 KHz
dpll 1572000 KHz
cpll 1200000 KHz
gpll 491009 KHz
npll 600000 KHz
armclk 600000 KHz
aclk_bus 150000 KHz
hclk_bus 75000 KHz
pclk_bus 75000 KHz
aclk_peri 150000 KHz
hclk_peri 75000 KHz
pclk_peri 75000 KHz
Net:
Warning: ethernet@ff540000 (eth0) using random MAC address - e2:b5:61:c5:27:cc
eth0: ethernet@ff540000
Hit key to stop autoboot('CTRL+C'): 0
Unknown command 'boot_android' - try 'help'
Unknown command 'bootrkp' - try 'help'
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
351 bytes read in 4 ms (85 KiB/s)
1: ROCK64
Retrieving file: /Image
reading /Image
22226952 bytes read in 1006 ms (21.1 MiB/s)
append: console=tty1 rw root=PARTUUID=deedbeef-02 rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr= eth1addr= serial=c3d9b8674f4b94f6 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 video=HDMI-A-1:1920x1080@60 loglevel=3
Retrieving file: /rk3328-rock64.dtb
reading /rk3328-rock64.dtb
72924 bytes read in 8 ms (8.7 MiB/s)
## Flattened Device Tree blob at 08300000
Booting using the fdt blob at 0x8300000
Loading Device Tree to 00000000f6eed000, end 00000000f6f01cdb ... OK
Adding bank: 0x00200000 - 0xff000000 (size: 0xfee00000)
Total: 4576.971 ms
Starting kernel ...
DDR version 1.13 20180428
ID:0x805 N
In
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
Boot1 Release Time: Feb 2 2018 15:41:39, version: 2.46
ChipType = 0x11, 144
SdmmcInit=2 0
BootCapSize=0
UserCapSize=0MB
FwPartOffset=2000 , 0
SdmmcInit=0 0
BootCapSize=0
UserCapSize=60952MB
FwPartOffset=2000 , 0
StorageInit ok = 23989
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=0xa3d00
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):9d3f591
NOTICE: BL31: Built : 14:39:02, Jan 17 2018
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2017.09 (May 09 2019 - 11:48:17 -0400)
Model: Rockchip RK3328 EVB
DRAM: 4 GiB
Sysmem: init
Relocation Offset is: fed15000
I2c speed: 400000Hz
PMIC: RK8050 (on=0x02, off=0x01)
vdd_logic 1100000 uV
vdd_arm 1100000 uV
MMC: rksdmmc@ff500000: 1, rksdmmc@ff520000: 0
*** Warning - bad CRC, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Rockchip RK3328 EVB
switch to partitions #0, OK
mmc1 is current device
Unknown command 'rkimgtest' - try 'help'
Card did not respond to voltage select!
mmc_init: -95, time 9
Unknown command 'rknand' - try 'help'
Unknown command 'rksfc' - try 'help'
Unknown command 'rksfc' - try 'help'
Bootdev: mmc 0
CLK: (sync kernel. arm: enter 600000 KHz, init 600000 KHz, kernel 0N/A)
apll 400000 KHz
dpll 1572000 KHz
cpll 1200000 KHz
gpll 491009 KHz
npll 600000 KHz
armclk 600000 KHz
aclk_bus 150000 KHz
hclk_bus 75000 KHz
pclk_bus 75000 KHz
aclk_peri 150000 KHz
hclk_peri 75000 KHz
pclk_peri 75000 KHz
Net:
Warning: ethernet@ff540000 (eth0) using random MAC address - e2:b5:61:c5:27:cc
eth0: ethernet@ff540000
Hit key to stop autoboot('CTRL+C'): 0
Unknown command 'boot_android' - try 'help'
Unknown command 'bootrkp' - try 'help'
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
reading /extlinux/extlinux.conf
345 bytes read in 4 ms (84 KiB/s)
1: ROCK64
Retrieving file: /Image
reading /Image
22226952 bytes read in 1007 ms (21 MiB/s)
append: console=tty1 rw root=/dev/mmcblk1p2 rootwait rootfstype=ext4 panic=10 init=/sbin/init coherent_pool=1M ethaddr= eth1addr= serial=c3d9b8674f4b94f6 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 video=HDMI-A-1:1920x1080@60 loglevel=3
Retrieving file: /rk3328-rock64.dtb
reading /rk3328-rock64.dtb
72924 bytes read in 8 ms (8.7 MiB/s)
## Flattened Device Tree blob at 08300000
Booting using the fdt blob at 0x8300000
Loading Device Tree to 00000000f6eed000, end 00000000f6f01cdb ... OK
Adding bank: 0x00200000 - 0xff000000 (size: 0xfee00000)
Total: 4577.812 ms
Starting kernel ...
(05-08-2019, 09:49 AM)Leapo Wrote: From what I've heard, the issue is that GPIO0_D6 (SDMMC0_PWREN) is left floating by current Linux devicetree configurations, but needs to be set to high or low in order to select an appropriate SDCard voltage.
You can solder a connection between test pad 2302 and 3.3v to revert your Rev3 board's SD-Card slot to Rev2 behavior, which should work with all cards.
If you have a UHS-capable MicroSD card, you can solder a connection between test pad 2303 and ground to force the slot into UHS mode.
Edit: The test pad can be located on the back of the PCB, near the center. I've highlighted it in this drawing, in red: https://i.imgur.com/F9BCSkj.png
It works! I couldn't get it to work connecting it to 3.3V (I'm using UHS cards) but only to ground.
Yup, just confirmed that the hardware fix works on my new v3 as well.
(05-06-2019, 10:04 AM)Humberg Wrote: I have seen many problems with the Rock64 v3 in the last few days.
Many customers have told me that existing Rock64 images suddenly no longer boot in v3.
We have verified this and found that apparently v3 can not cope with many SD cards. The booting of eMMC goes without problems.
If a customer has bought a new v3 and nothing works, contact us, we will send you an emmc card for the purchase price without any profit.
markus@humberg.de
Hi,
As I was just about to order me one rock64 board, I came across this post. So the obvious question is, can I order one now and have no problem with it or should I wait a little bit? I don't want to mess around with the hardware.
Thanks
(05-27-2019, 12:33 PM)Leapo Wrote: Yup, just confirmed that the hardware fix works on my new v3 as well.
Did you mean SW fix?
|
Rock64 v3 and SD-Cards
