Hi,

On 14/03/18 22:06, Martin Lucina wrote:
> On Wednesday, 14.03.2018 at 16:09, Martin Lucina wrote:
>> On Wednesday, 14.03.2018 at 15:51, Martin Lucina wrote:
>>> I've now done a full cross debootstrap on the host to work around the
>>> kernel BUG, adding the kernel modules from 4.16-rc5 manually to the rootfs.
>>> Interestingly, U-boot or the kernel don't seem to see the ethernet device
>>> at all. Also, the ATF is complaining about setting up the PMIC which may be
>>> related?
>>
>> ... this appears to be random: on a cold boot I now get a "NOTICE:  PMIC:
>> setup successful", however "modprobe dwmac-sun8i" still gets me no network
>> interface.
> 
> And a further data point: I've taken the SD card containing kernel
> 4.16-rc5, stretch rootfs used in my tests so far, replaced U-boot 2018.03
> and the dtb with the Pine64+ versions and successfully booted on a PINE
> A64-LTS board a friend lent me. There are no instances of the "BUG: bad
> page state in process ..." and I also see the Ethernet device in U-boot and
> the kernel.
> 
> In summary the above plus my testing so far with two separate Olimex
> A64-oLinuXino boards points to the Olimex board support and/or hardware
> in general being the cause of the problem.

So that might be a DRAM issue then.
Can you try to lower the frequency?
Just set CONFIG_DRAM_CLK in your U-Boot .config (or _defconfig) to 648
for a start, or try lower values in 24MHz steps. The default value for
A64 boards is 672 MHz.
And somewhat related: Can you please check the actual DRAM chips? Find
the actual name on them (and add them to the linux-sunxi wiki [1] on the
way), ideally also find a data sheet?
The DRAM setup code in U-Boot assumes certain chips, also has some
assumptions about PCB specific values, so the board might need more
adjustment here.

Cheers,
Andre.

[1] http://linux-sunxi.org/Olimex_A64-OLinuXino

-- 
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.

Reply via email to