Re: [U-Boot] [PATCH] Add CONFIG_GMAC_TX_DELAY=4 for OlinuXino Lime2
On 03/18/2016 08:02 PM, Karsten Merker wrote:
The installer supports a number of systems that can only load images of limited size, therefore the installer includes only an installation-related subset of all the kernel modules and i2c-mv64xxx currently isn't among those. This hasn't been a practical problem up to now, but being able to talk to the pmic is indeed something that should be possible even in the installer. I'll try to address that in the next days. Regards, Karsten
Just an anecdote: I loaded i2c-mv64xx.ko which I had extracted from the deb and the olinuxino locked up.
So now I'm trying to reproduce broken GBit, which is harder than expected. I managed to do it once right after the lockup in u-boot: tftp was slow and ran into timeouts. Then I typed 'reset' in the u-boot shell. u-boot started again and GBit was working again.
Weird.
On 03/18/2016 08:06 PM, Michael Haas wrote:
On 03/18/2016 08:02 PM, Karsten Merker wrote:
The installer supports a number of systems that can only load images of limited size, therefore the installer includes only an installation-related subset of all the kernel modules and i2c-mv64xxx currently isn't among those. This hasn't been a practical problem up to now, but being able to talk to the pmic is indeed something that should be possible even in the installer. I'll try to address that in the next days. Regards, Karsten
Just an anecdote: I loaded i2c-mv64xx.ko which I had extracted from the deb and the olinuxino locked up.
Just for the record: loading i2c-mv64xx.ko reproducibly hangs my Debian Jessie install with the 4.3.0-0.bpo.1-armmp-lpae kernel. This happens only on u-boot 2016.01; both Debian stable 2014.10 and my own build of 2016.03 + patches work fine!
So no problem since it's fixed on newer builds. Just a note for those playing along at home and wondering why their olinuxino does not come up anymore with 2016.01.
So now I'm trying to reproduce broken GBit, which is harder than expected. I managed to do it once right after the lockup in u-boot: tftp was slow and ran into timeouts. Then I typed 'reset' in the u-boot shell. u-boot started again and GBit was working again.
Weird. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Hi,
I am not 100% sure, but I remember trying first to disable the PMIC in uboot to cure this problem, see my post on archlinux arm forum there : https://archlinuxarm.org/forum/viewtopic.php?f=33&t=9911#p50946 But eventually I think this is this patch http://lists.denx.de/pipermail/u-boot/2016-March/248923.html which got it right (no need of disabling pmic). My guess is the board failed to activate the Ethernet PHY via pmic due to incompatible config (the failure was just after the pmic i2c registering by the kernel).
Regards,
participants (3)
-
François-David Collin -
Michael Haas -
Michael Haas