PINE64
rock64, compile problems "illegal instruction", "memory fault" -> ddr_333Mhz? - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: General Discussion on ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=86)
+--- Thread: rock64, compile problems "illegal instruction", "memory fault" -> ddr_333Mhz? (/showthread.php?tid=14343)



rock64, compile problems "illegal instruction", "memory fault" -> ddr_333Mhz? - klausfelix - 07-02-2021

Hello,

 Since owning my rock64 (4GB version)  I had always problems compiling larger projects on the device itself.

I tried many things like an other ac-adapter, different micro-sdcards, compiling on USB, different host-images, compiling only on two cores than
one core, gcc-5, 6, 7, swap on,  nothing helped.

The compiler always runs in errors like "illegal instruction" or "memory fault" that were temporal as they disappeared at the next
try.

After playing around with the rockchip boot flow on the rockpro64 I got the idea to check the driver for the external memory interface.
All host-images I tried on the rock64 use the same driverfile "rk3328_ddr_786MHz_v1.13.bin", so I gave the rock64 an other try with
rk3328_ddr_333MHz_v1.13.bin at offset 0x8800 on the boot device.

After reboot I compiled the ayufan-kernel on the device itself with 4 cores on internal sdcard. Worked, no error like before.

Yesterday I took an external USB-HD with the source of palemoon compiled from USB, wrote the objectfiles to the internal sdcard, 4 cores, swap on. It took the whole night, but the build completed successfully. No error like before.

Can someone tell me the negative implications when using the 333MHz-version of this driver?
______________________
First Motion Products