05-20-2020, 04:55 PM
(05-20-2020, 03:05 PM)devrtz Wrote: You are very welcome (:
@Djhg2000
I'm still trying to figure out how to u-boot can be used to set command line arguments for the kernel (for memset).
Haven't found the location yet where this could be done.
After giving this some thought, maybe it is a better idea to leave u-boot as it is, and instead build the kernel with
the necessary command line baked into it.
On my RockPro64, in the days when I compiled kernels for it you would get an additional option in extlinux.conf - if selected then it boots directly into memtest. It is probably the purest test but I think the "problem" is not so subtle and I can now easily reproduce by installing memtester which will run as an application.
If I boot my BraveHeart with stock Mobian, or patched with your 600 or even 588 u-boots then the following in a King's Cross terminal session will quickly fail
Code:
echo performance |sudo tee /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
sudo memtester 1G 1
memtester will try use 1Gb of memory and run for 1 pass, which takes about 30 minutes to successful completion (it says OK or done or similar). If your system is unstable typically phosh crashes and after entering your PIN your terminal session has vanished.
I passed this sequence (indeed even memtester 1G 4 which ran for about 2 hours) at 576 but still feel my phone is not 100% stable.
- ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Arch (6.2 kernel, Openbox desktop) for general purpose daily PC.
- PinePhone Pro Explorer Edition, daily driver, rk2aw & U-boot on SPI, Arch/SXMO & Arch/phosh on eMMC
- PinePhone BraveHeart now v1.2b 3/32Gb, Tow-boot with Arch/SXMO on eMMC