Hi,
On 17-03-16 22:53, Michael Haas wrote:
On 03/17/2016 11:52 AM, Hans de Goede wrote:
Hi,
There are 3 things which would be interesting to save and compare
with a boot which does have the problem:
1) The gmc clk register, to do this download mmio_dump from:
Working GBit:
01c20164: 00000c06
Broken GBit:
tomorrow :)
2) The pmic settings for various ldo-s, etc. as root run:
i2cdump -f -y 0 0x34
And record the output. You may need to
install i2c-tools (or the deb. alternative) and
do "modprobe i2c_dev"
I had to download the Debian kernel package on another box, extract the
.ko, transfer and insmod it. Now I'm getting:
~ # /mnt/usr/sbin/i2cdump -f -y 0 0x34
No size specified (using byte-data access)
Error: Could not open file `/dev/i2c-0': No such device
I did mknod the devices, but I'm getting the same error msg:
~ # ls -al /dev/i2c-*
crw-r--r-- 1 root root 89, 0 Mar 17 21:31 /dev/i2c-0
crw-r--r-- 1 root root 89, 1 Mar 17 21:31 /dev/i2c-1
~ #
Module Size Used by
i2c_dev 7087 0
i2c_sun6i_p2wi 3664 0
dm_mod 98419 0
md_mod 121938 0
jfs 175313 0
crc32c_generic 1862 1
btrfs 1068047 0
xor 4846 1 btrfs
zlib_deflate 20354 1 btrfs
raid6_pq 87885 1 btrfs
vfat 10249 0
fat 55086 1 vfat
ext4 552524 2
crc16 1274 1 ext4
mbcache 9623 1 ext4
jbd2 96157 1 ext4
usb_storage 45523 0
ahci_sunxi 2851 0
libahci_platform 6430 1 ahci_sunxi
libahci 23066 2 libahci_platform,ahci_sunxi
libata 182871 3 libahci,libahci_platform,ahci_sunxi
scsi_mod 188073 2 usb_storage,libata
realtek 2711 0
dwmac_sunxi 2431 0
stmmac_platform 3302 1 dwmac_sunxi
stmmac 74687 3 stmmac_platform,dwmac_sunxi
ohci_platform 4658 0
ohci_hcd 38045 1 ohci_platform
ehci_platform 5398 0
ehci_hcd 63999 1 ehci_platform
usbcore 190581 5
usb_storage,ohci_platform,ohci_hcd,ehci_hcd,ehci_platform
usb_common 3195 1 usbcore
phy_sun4i_usb 7858 8
extcon 10436 1 phy_sun4i_usb
sunxi_mmc 11288 0
leds_gpio 3606 0
I also loaded i2c_sun6i_p2wi for good measure. Any idea what's missing
here?
Maybe i2c-mv64xxx is a module with the Debian kernel ? That would be
bad because that would mean that we cannot communicate to the pmic
until the i2c-mv64xxx module is loaded. OTOH not having a pmic
driver talking to the pmic may explain why things work on this
particular sdcard :)
To check if that module is loaded and initialized do:
ls /sys/bus/i2c/devices
You should see at least a i2c-0 there. After the modprobe
of that driver, check dmesg for any axp messages if you're
getting some then the loading of the driver causes the pmic
driver to talk to the device (iow the pmic driver is present
already) if this happens, I would double check the gbit, because
the loading of the pmic driver may change things.
Regards,
Hans
3) The phy settings, unfortunately I do not know of
a way to dump these, so lets just forget about these
and focus on the other 2.
I might even look at the data sheet tomorrow if time permits.
Michael
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
