On Sun, 21 Dec 2014 17:00:46 -0300 Emilio López emilio@elopez.com.ar wrote:
Hi Hans,
El 20/12/14 a las 15:27, Hans de Goede escibió:
Hi All,
There are 3 topics which I would like to cover in this mail:
- Switching over to upstream u-boot for the linux-sunxi project
(...)
Here are some example instructions on how to build upstream u-boot for the Cubietruck:
git clone git://git.denx.de/u-boot.git cd u-boot make -j4 CROSS_COMPILE=arm-linux-gnu- Cubietruck_defconfig # If you want to use an upstream kernel the next steps can be skipped (*) make -j4 CROSS_COMPILE=arm-linux-gnu- menuconfig # select "ARM architecture" -> "Enable workarounds for booting old kernels" # exit & save make -j4 CROSS_COMPILE=arm-linux-gnu- spl/menuconfig # select "ARM architecture" -> "Enable workarounds for booting old kernels" # exit & save # skip to here if you're using an upstream kernel make -j4 CROSS_COMPILE=arm-linux-gnu-
And now you will have a u-boot-sunxi-with-spl.bin to dd to your sdcard as usual.
(...)
So I thought it'd be a good idea to move over to mainline uboot, but it doesn't seem to be working at all on Cubietruck. When applying power to the board, all I get is
U-Boot SPL 2015.01-rc3-00163-gd8bec60 (Dec 21 2014 - 16:43:41) DRAM:Timeout initialising DRAM
resetting ...
U-Boot SPL 2015.01-rc3-00163-gd8bec60 (Dec 21 2014 - 16:43:41) DRAM:Timeout initialising DRAM
resetting ...
...ad infinitum.
The hardware itself is fine, the NAND bootloader runs OK and I used the board with an old uboot-sunxi some days back. Any ideas on what may be going on?
Thanks for reporting this.
First of all, please ensure that there is no obvious misconfiguration. For example, whether you have really configured u-boot for Cubietruck.
If everything is configured correctly, then it would help a lot to identify which of the await_bits_set() or await_bits_clear() calls is failing in 'arch/arm/cpu/armv7/sunxi/dram_sun4i.c' by adding some extra debugging prints.