piter75
Members-
Posts
306 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by piter75
-
20.08 upgrade with 5.7.15 will not boot on RockPro64
piter75 replied to David Pottage's topic in Pine RockPro64
Yup. When you boot 5.7 or 5.8 from eMMC there is not much to see in the logs. I would like to see eMMC initialisation while you boot from SD and have eMMC and possibly NVMe connected. This may (possibly) shed some light at why you cannot boot with eMMC. -
20.08 upgrade with 5.7.15 will not boot on RockPro64
piter75 replied to David Pottage's topic in Pine RockPro64
Can you try to capture the verbose bootlog once again while booting from SD but with eMMC still inserted? I checked your previous logs but they were probably captured without eMMC module. You will most probably have to break the boot sequence at u-boot (just hit space bar around the time that Model: RockPro64 is printed) and run the following commands at u-boot prompt: setenv devnum 1 run mmc_boot -
It certainly requires some additional patching before building. This patch is for sure missing in our kernel for ROCK Pi S: https://github.com/radxa/kernel/commit/70a0bbccf001a06ae08f1dd4855059c2966dbe8b I remember omitting it because of lack of interest in Bluetooth. I may get back to that... Contributions are also welcome
-
Yeah, I did ignore it too...
-
We need to work a bit on our download page for ROCK Pi 4 boards as I see you used 4B images - and these are the only ones easily accessible on the download page (CC: @Igor) For current use the images from here: https://dl.armbian.com/rockpi-4c/archive/ - all USB ports should work there. In legacy they will not work right now. I have it on my TODO list so it is possible that with the next point release all USB ports will work in legacy too.
-
Switching SUNXI-DEV to 5.9.y (h3-h5-h6/megous)
piter75 replied to dolphs's topic in Advanced users - Development
I did exactly that. Only for rtl8189fs, though, as rtl8189es still needs it. -
Switching SUNXI-DEV to 5.9.y (h3-h5-h6/megous)
piter75 replied to dolphs's topic in Advanced users - Development
rtl8189fs was patched "upstream": https://github.com/jwrdegoede/rtl8189ES_linux/commit/0ba46e2434eec6f67d0712ed119a4ef8e05ccf91 I removed rtl8189fs from our patches for rockchip64 yesterday and propagated the change to other families about an hour ago. -
20.08 upgrade with 5.7.15 will not boot on RockPro64
piter75 replied to David Pottage's topic in Pine RockPro64
It wasn't. Can you attach it? Was it boot from SD (v20.08) with eMMC inserted? Can you try to boot it this way? I would like to see eMMC initialisation logs. -
20.08 upgrade with 5.7.15 will not boot on RockPro64
piter75 replied to David Pottage's topic in Pine RockPro64
I have tested both fresh v20.08 (Armbian_20.08_Rockpro64_bionic_current_5.7.15.img.xz) as well as v20.05.2 (Armbian_20.05.2_Rockpro64_bionic_current_5.4.43.img.xz) + upgrade to v20.08 and my unit boots fine in both scenarios It is however not the first report about it so there may be something to it... Please provide more verbose logs as Igor suggested. -
As suggested by Werner get rid of recovery GPT partition table from your SD. This is a known interoperability issue between Xunlong's images and Armbian. Below you can find instructions. Also, did you short TP50265 to the ground for booting from SD according to the download page instructions? The first part of your log seems like booting from eMMC.
-
Last four, but you need to divide them by 2 so it is 333MHz.
-
This was really missing in your opening message... I thought you were simply referring to what you found in Arch ;-) Yes. When I wrote "we have DMC enabled" I meant "in Armbian". It's not available in mainline. This most probably means your memory is staying at 333MHz all the time. One more way to verify this would be to use: grep ddr /sys/kernel/debug/clk/clk_summary Did you try to build yourself a "dev" image for Renegade from Armbian master and see if the boot problem exists here too?
-
The current plan regarding legacy u-boot for rockchip64 is to get rid of it for v20.11: https://armbian.atlassian.net/browse/AR-350 https://armbian.atlassian.net/browse/AR-351 I will add a separate issue for Renegade to not forget it in the process ;p I believe we could try to enable it. Current Rockchip's DDR loaders are also limited to 333MHz but we have DMC enabled in mainline kernels for rk3328 and higher frequencies should be used. What do you see when you run the following command? cat /sys/class/devfreq/dmc/trans_stat EDIT: Rock64 boots fine with 5.8.x and u-boot v2017.09: http://ix.io/2uyG so the issue might be isolated to Renegade...
-
For me it usually takes no more than few hours of memtester (apt install memtester) running to see first failures with M4V2 in mainline. You can run it this way as root (for 4GB board). For 2GB the value of memory reservation for testing should be lower. memtester 3280M 2>&1 | tee memtester.log
-
AFAIK it is non functional yet... Did you test your RK3399V2 SOM for stability in mainline? M4V2 has some known stability issues that I currently attribute (maybe wrongly) to memory / design used. RK3399V2 SOM uses the same RAM chips and I wonder if it shares the same issues.
-
Is it with legacy or current/dev? Legacy should probably work as it is based on FA kernel code directly and DTS differences between the two boards are minimal. With current/dev it might be a whole different story though... I can do that in the "mean time" ;-)
-
All RK3399 boards officially support only Gen1 but Gen2 seems to work well with them. In Armbian Gen1 is enabled by default (safety first). Adventurous users can enable Gen2 with pcie-gen2 overlay.
-
Looking at the device tree differences between SOM RK3399v2 and M4v2 I would say the possibility of booting SOM (v2) with M4v2 image is pretty high but... you never know until you try.
-
RockPro64 kernel v5.4 doesn't boot on eMMC (while kernel v4.4 does)
piter75 replied to Baptiste's topic in Pine RockPro64
This is a known issue with rk3399 boards using mainline kernel and it was mitigated for all other boards using mainline u-boot some time ago. RockPro64 is the last one that is uses u-boot v2017.09 but I am planning to switch it to mainline for the next Armbian release (v20.11). For now you need to either be patient or stay with 4.4.y. -
This a known issue. If Rockchip's loader finds GPT partition table (in this case the recovery one) it tries to boot using the GPT partition layout which Armbian does not use. At this point to quickly recover the SD card after Xunlong's image you need to erase last 33 sectors holding a GPT recovery partition table and before writing Armbian image.