Re: Problems with pyhBoard-Wega-AM335x
Hello Florian, On Tue, 8 Jul 2014, Teresa Gamez wrote: Hello Florian, I guess you having the default kit WEGA, which does have 256MB RAM. The mainline supported phyCORE Kit does have 512MB. Thats probably why it does not start up. I'll have a look at it. Teresa I'm not 100% sure, but I can imagine that the should also appear when the SDRAM configuration is not correct. But nevertheless the correct SDRAM setting is important. Maybe, you can check the SDRAM setting of your previous barebox-2013.11. I assume, the old barebox was running properly, wasn't it? Sorry but I have no idea which information I can send you to help me with my problem... Florian, could you please check the size of your 1st stage bootloader (MLO) binary? It must not exceed 111616 byte! Otherwise it will not boot. You can shrink the size by removing all unnecessary stuff from the barebox_mlo configuration. Best regards, Rolf ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Problems with pyhBoard-Wega-AM335x
Hello Rolf, after I apply the Patch from Teresa I got the . Yes the last barebox worked. Yesterday I configured the new barebox in the same way as the old one and got the the size of my image is only 93260 bytes so it should work but it do not work. So I will spend no more time with the phyWega and wait for the phyCore Kit and start there my next try. Thanks for your helping Florian Am 09.07.2014 08:47, schrieb Rolf Evers-Fischer: Hello Florian, On Tue, 8 Jul 2014, Teresa Gamez wrote: Hello Florian, I guess you having the default kit WEGA, which does have 256MB RAM. The mainline supported phyCORE Kit does have 512MB. Thats probably why it does not start up. I'll have a look at it. Teresa I'm not 100% sure, but I can imagine that the should also appear when the SDRAM configuration is not correct. But nevertheless the correct SDRAM setting is important. Maybe, you can check the SDRAM setting of your previous barebox-2013.11. I assume, the old barebox was running properly, wasn't it? Sorry but I have no idea which information I can send you to help me with my problem... Florian, could you please check the size of your 1st stage bootloader (MLO) binary? It must not exceed 111616 byte! Otherwise it will not boot. You can shrink the size by removing all unnecessary stuff from the barebox_mlo configuration. Best regards, Rolf ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
[PATCH] ARM: am335x Phytec phyCORE: Enable ethernet
With an update of the am33xx.dtsi (commit 9313920df6) the mdio and mac
nodes are not enabled on default any more. Enable them explicit
in the board dts now.
Signed-off-by: Teresa Gámez t.ga...@phytec.de
---
arch/arm/dts/am335x-phytec-phycore.dts |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/dts/am335x-phytec-phycore.dts
b/arch/arm/dts/am335x-phytec-phycore.dts
index 6196eb3..63debd2 100644
--- a/arch/arm/dts/am335x-phytec-phycore.dts
+++ b/arch/arm/dts/am335x-phytec-phycore.dts
@@ -214,6 +214,7 @@
davinci_mdio {
pinctrl-names = default;
pinctrl-0 = davinci_mdio_default;
+ status = okay;
};
phy_sel {
@@ -236,6 +237,7 @@
pinctrl-names = default;
pinctrl-0 = emac_rmii1_pins;
dual_emac = 1;
+ status = okay;
};
gpmc {
--
1.7.0.4
___
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
Re: AM335x MLO images broken
On Wed, Jul 09, 2014 at 05:50:12PM +0200, Teresa Gamez wrote: Hello Sascha, since commit d1ec6fb0c9bb66939e85964c2f5214b117c78ecf Author: Sascha Hauer s.ha...@pengutronix.de Date: Mon Jul 7 14:13:14 2014 +0200 ARM: OMAP: Do not show MLO/SPI image options with OMAP_MULTI_BOARDS the creation of a proper MLO image is not working any more. When I run make am335x_mlo_defconfig make I get: .. images built: barebox-am33xx-phytec-phycore.img barebox-am33xx-beaglebone.img instead of the expected barebox-am33xx-phytec-phycore-mlo.img barebox-am33xx-beaglebone-mlo.img and they also won't work. Looks like a side effect of: | commit d1ec6fb0c9bb66939e85964c2f5214b117c78ecf | Author: Sascha Hauer s.ha...@pengutronix.de | Date: Mon Jul 7 14:13:14 2014 +0200 | | ARM: OMAP: Do not show MLO/SPI image options with OMAP_MULTI_BOARDS | | The MLO/SPI image options have no effect with OMAP_MULTI_BOARDS | enabled, so do not show them. | | Signed-off-by: Sascha Hauer s.ha...@pengutronix.de I haven't looked whether there's a better solution than reverting the commit. Sascha -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
