On Wed, 25 Mar 2015 19:09:06 +0300 Andrew Kosteltsev <[email protected]> wrote:
> Hello All, > > Please advise some test image which can be boot on my Cubietruck to check > is my Cubietruck hardware ok and has no PCB layout issues. > > > Thanks a lot in advice. > Andrey K. Thanks for moving here from google+ and posting the detailed information about your setup. > Problem description: > ------------------- > On the Cubietruck I have unexpected system crash (reboot) without reports > when run the lima-memspeed: > > $ ./lima-memspeed gpu_copy It is better to use the 'lima-memtester' program, because it is designed to test DRAM settings (and hardware) reliability. While the 'lima-memspeed' program is designed for something else. > Also I have unexpected reboots when the qt4, qt5 tests are running. > > On the Cubieboard1 I have no problems (all qt5 examples works fine > including WebGL rendering by webbrowser [http://threejs.org/examples/] > ). > > Memtester: https://github.com/ssvb/lima-memtester > > U-Boot repository: https://github.com/linux-sunxi/u-boot-sunxi > U-Boot revision: ea1ac32bf76eb60baef474c2516fc431b381d952 This repository is now obsolete. It is better to use the mainline U-Boot. Some instructions are available here: http://linux-sunxi.org/Mainline_U-boot > FEX script: > http://svn.radix.pro/wsvn/platform/trunk/boot/u-boot/A20/20141124/fex/script.fex.in At least the name of this file looks wrong. The fex files are not SoC specific, but device specific. So it should have 'Cubietruck' in its name. Also a collection of up to date and know to work fex files is stored in the https://github.com/linux-sunxi/sunxi-boards repository. For the Cubietruck you need to use https://raw.githubusercontent.com/linux-sunxi/sunxi-boards/master/sys_config/a20/cubietruck.fex > Kernel repository: https://github.com/linux-sunxi/linux-sunxi > Kernel revision: 9a1cd034181af628d4145202289e1993c1687db6 Looks good, at least for the mainline u-boot in the old kernel compatibility mode. But trying the stage/sunxi-3.4 branch may be a good idea too. > kernel_config: > http://svn.radix.pro/wsvn/platform/trunk/boot/kernel/A20/3.4-20141014/cb3x.config When troubleshooting, please try the default 'sun7i_defconfig' first. And if you want to store your own config somewhere, please run make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- savedefconfig after compiling the kernel and pick the resulting 'defconfig' file. That would be a distilled version of the config without all the bloat. > libUMP version: r3p0-04rel0 > libMali binary: > https://github.com/linux-sunxi/sunxi-mali-proprietary/tree/1c5063f43cdc9de341c0d63b2e3921cab86c7742/r3p0/armhf/x11 > libdri2 repository: https://github.com/robclark/libdri2 > libdri2 revision: 4f1eef3183df2b270c3d5cbef07343ee5127a6a4 All these files are not necessary for running lima-memtester. Yes, they are needed for Qt5, but you can start worrying about getting it up and running later (after the lima-memtester program stops deadlocking/rebooting or reporting memory corruption). Once you have your system setup more aligned with what the other people use, I would pay attention to the following things: * MBUS clock speed. The old u-boot is using the FAST_MBUS flag and sets the 400MHz MBUS speed. The mainline u-boot still uses 300MHz MBUS and may be more reliable on your hardware. * The dcdc3 voltage. After the sunxi-3.4 kernel is booted, you can run "dmesg | grep buck" to see the dcdc3 voltage. Normally it should be 1.3V on the Cubietruck. * Double check the fex file (use the one from the sunxi-boards repository) * Use the sun7i_defconfig * Maybe try a different power supply or power cable just in case, these might be sometimes responsible for reliability problems too -- Best regards, Siarhei Siamashka -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
