Re: [U-Boot] Clearfog Base PCI-E not working
On Sat, Mar 16, 2019 at 8:07 PM Chris Packham wrote:
>
> On Fri, Mar 15, 2019 at 6:56 PM Stefan Roese wrote:
> >
> > On 14.03.19 17:37, Влад Мао wrote:
> > > I found mismatched entries in DTS:
> > >
> > > In armada-388-clearfog.dts:
> > >
> > > pcie-controller {
> > > status = "okay";
> > >
> > > But in armada-385.dtsi we have:
> > >
> > > pciec: pcie {
> > > compatible = "marvell,armada-370-pcie";
> > >
> > > After fixing it, PCIE does show up as expected.
> >
> > Thanks for spotting this. Could you please send a proper patch to
> > fix this to the list?
> >
>
> These other boards seem similarly affected.
>
> armada-385-turris-omnia.dts
> armada-388-gp.dts
> armada-385-amc.dts
> armada-38x-controlcenterdc.dts
>
> I think I must have missed them when I did the last sync with Linux.
I've sent a patch for the armada-38x boards. It also appears that the
armada-xp boards have a similar problem (unrelated to my syncing).
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Clearfog Base PCI-E not working
On Fri, Mar 15, 2019 at 6:56 PM Stefan Roese wrote:
>
> On 14.03.19 17:37, Влад Мао wrote:
> > I found mismatched entries in DTS:
> >
> > In armada-388-clearfog.dts:
> >
> > pcie-controller {
> > status = "okay";
> >
> > But in armada-385.dtsi we have:
> >
> > pciec: pcie {
> > compatible = "marvell,armada-370-pcie";
> >
> > After fixing it, PCIE does show up as expected.
>
> Thanks for spotting this. Could you please send a proper patch to
> fix this to the list?
>
These other boards seem similarly affected.
armada-385-turris-omnia.dts
armada-388-gp.dts
armada-385-amc.dts
armada-38x-controlcenterdc.dts
I think I must have missed them when I did the last sync with Linux.
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Re: [U-Boot] Clearfog Base PCI-E not working
On 14.03.19 17:37, Влад Мао wrote:
I found mismatched entries in DTS:
In armada-388-clearfog.dts:
pcie-controller {
status = "okay";
But in armada-385.dtsi we have:
pciec: pcie {
compatible = "marvell,armada-370-pcie";
After fixing it, PCIE does show up as expected.
Thanks for spotting this. Could you please send a proper patch to
fix this to the list?
Thanks,
Stefan
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] Clearfog Base PCI-E not working
I found mismatched entries in DTS:
In armada-388-clearfog.dts:
pcie-controller {
status = "okay";
But in armada-385.dtsi we have:
pciec: pcie {
compatible = "marvell,armada-370-pcie";
After fixing it, PCIE does show up as expected.
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
[U-Boot] Clearfog Base PCI-E not working
Hello. I have trouble with pci-e on Clearfog Base board. In PCI-E slot inserted video card. In linux its work and detect perfectly. But in U-boot command pci shows nothing. Comands to reproduce: make CROSS_COMPILE=/opt/gcc-linaro-7.1.1-2017.08-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- ARCH=arm O=../build clearfog_defconfig make -j2 CROSS_COMPILE=/opt/gcc-linaro-7.1.1-2017.08-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- ARCH=arm O=../build cp ../build/u-boot-spl.kwb u-boot-spl.kwb ../build/tools/kwboot -p -t -b ./u-boot-spl.kwb -B 115200 /dev/ttyUSB0 Log attached: Sending boot message. Please reboot the target...- Sending boot image... 0 % [..] 1 % [..] 3 % [..] 5 % [..] 6 % [..] 8 % [..] 9 % [..] 11 % [..] 13 % [..] 14 % [..] 16 % [..] 18 % [..] 19 % [..] 21 % [..] 23 % [..] 24 % [..] 26 % [..] 28 % [..] 29 % [... U-Boot SPL 2019.04-rc2 (Mar 13 2019 - 08:46:43 +0300) High speed PHY - Version: 2.0 Detected Device ID 6828 board SerDes lanes topology details: | Lane # | Speed | Type | | 0| 3 | SATA0 | | 1| 0 | SGMII1 | | 2| 5 | PCIe1 | | 3| 5 | USB3 HOST1 | | 4| 5 | PCIe2 | | 5| 0 | SGMII2 | :** Link is Gen1, check the EP capability PCIe, Idx 1: remains Gen1 PCIe, Idx 2: detected no link High speed PHY - Ended Successfully mv_ddr: mv_ddr-armada-18.09.2 DDR3 Training Sequence - Switching XBAR Window to FastPath Window mv_ddr: completed successfully ...] 31 % [..] 33 % [..] 34 % [..] 36 % [..] 38 % [..] 39 % [..] 41 % [..] 43 % [..] 44 % [..] 46 % [..] 48 % [..] 49 % [..] 51 % [..] 53 % [..] 54 % [..] 56 % [..] 58 % [..] 59 % [..] 61 % [..] 63 % [..] 64 % [..] 66 % [..] 68 % [..] 69 % [..] 71 % [..] 73 % [..] 74 % [..] 76 %
