Re: [U-Boot] [PicoZed] Error in NET and SD Card

2016-10-13 Thread Oscar Gomez Fuente 
Hi Jaehoon,

I fixed the problem.

I had to add this patch to the file /arch/arm/dts/zynq-picozed.dts

diff --git a/arch/arm/dts/zynq-picozed.dts b/arch/arm/dts/zynq-picozed.dts
index 3408df8..a6b12b2 100644
--- a/arch/arm/dts/zynq-picozed.dts
+++ b/arch/arm/dts/zynq-picozed.dts
@@ -26,3 +26,23 @@
u-boot,dm-pre-reloc;
status = "okay";
 };
+
+ {
+status = "okay";
+phy-mode = "rgmii-id";
+phy-handle = <_phy>;
+
+ethernet_phy: ethernet-phy@0 {
+reg = <0>;
+};
+};
+
+ {
+u-boot,dm-pre-reloc;
+status = "okay";
+};
+
+ {
+u-boot,dm-pre-reloc;
+status = "okay";
+}

So the problem was due to an incomplete dts file.

Could you fix this issue in the following release? Or How could I send
this request
to u-boot?


Best regards.

Oscar Gomez Fuente

On 13 October 2016 at 11:49, Oscar Gomez Fuente 
wrote:

> Hi Jaehoon,
>
>
> I've tried to add the #define CONFIG_MMC_TRACE in the file
> include/configs/zynq-common.h
>
> But after compiled and boot u-boot, It doesn't appear any messages:
>
> ---
> U-Boot 2016.11-rc1-00139-gf5fd45f-dirty (Oct 13 2016 - 11:33:25 +0200)
>
> Model: Zynq PicoZed Board
> Board: Xilinx Zynq
> DRAM:  ECC disabled 1 GiB
> MMC:
> Using default environment
>
> In:serial@e0001000
> Out:   serial@e0001000
> Err:   serial@e0001000
> Model: Zynq PicoZed Board
> Board: Xilinx Zynq
> Net:   No ethernet found.
> ** Bad device mmc 0 **
> Checking if uenvcmd is set ...
> Hit any key to stop autoboot:  0
> Zynq> mmcinfo
> No MMC device available
> Zynq>
> ---
>
> I think I'm doing something wrong. Any suggestion?
>
> As you know it doesn't work the ethernet as well as the SD Card, so I've
> decided to get from the u-boot.dtb the u-boot.dts, and I've just realised
> that the two ethernet ports have the status disabled, as well as the sdhci,
> so I think is something related to the way the dtb file is generated.
>
> To get the u-boot-dtb file, I had to configure:
>
> > Device Tree Control  Provider of DTB for DT control > (X) Separate DTB
> for DT control
>
> I usually use the mode  (X ) Embedded DTB for DT control, because a use
> the application bootgen from Xilinx and I need to have the dtb embedded,
> but I used this way only to get the dts file.
>
> This is the u-boot.dts file I got:
>
> ---
> /dts-v1/;
>
> / {
> #address-cells = <0x1>;
> #size-cells = <0x1>;
> compatible = "xlnx,zynq-picozed", "xlnx,zynq-7000";
> model = "Zynq PicoZed Board";
>
> chosen {
> };
>
> aliases {
> serial0 = "/amba/serial@e0001000";
> };
>
> memory {
> device_type = "memory";
> reg = <0x0 0x4000>;
> };
>
> cpus {
> #address-cells = <0x1>;
> #size-cells = <0x0>;
>
> cpu@0 {
> compatible = "arm,cortex-a9";
> device_type = "cpu";
> reg = <0x0>;
> clocks = <0x1 0x3>;
> clock-latency = <0x3e8>;
> cpu0-supply = <0x2>;
> operating-points = <0xa2c2b 0xf4240 0x51616 0xf4240>;
> };
>
> cpu@1 {
> compatible = "arm,cortex-a9";
> device_type = "cpu";
> reg = <0x1>;
> clocks = <0x1 0x3>;
> };
> };
>
> pmu {
> compatible = "arm,cortex-a9-pmu";
> interrupts = <0x0 0x5 0x4 0x0 0x6 0x4>;
> interrupt-parent = <0x3>;
> reg = <0xf8891000 0x1000 0xf8893000 0x1000>;
> };
>
> fixedregulator@0 {
> compatible = "regulator-fixed";
> regulator-name = "VCCPINT";
> regulator-min-microvolt = <0xf4240>;
> regulator-max-microvolt = <0xf4240>;
> regulator-boot-on;
> regulator-always-on;
> linux,phandle = <0x2>;
> phandle = <0x2>;
> };
>
> amba {
> u-boot,dm-pre-reloc;
> compatible = "simple-bus";
> #address-cells = <0x1>;
> #size-cells = <0x1>;
> interrupt-parent = <0x3>;
> ranges;
>
> adc@f8007100 {
> compatible = "xlnx,zynq-xadc-1.00.a";
> reg = <0xf8007100 0x20>;
> interrupts = <0x0 0x7 0x4>;
> interrupt-parent = <0x3>;
> clocks = <0x1 0xc>;
> };
>
> can@e0008000 {
> compatible = "xlnx,zynq-can-1.0";
> status = "disabled";
> clocks = <0x1 0x13 0x1 0x24>;
> clock-names = "can_clk", "pclk";
> reg = <0xe0008000 0x1000>;
> interrupts = <0x0 0x1c 0x4>;
> interrupt-parent = <0x3>;
> tx-fifo-depth = <0x40>;
> rx-fifo-depth = <0x40>;
> };
>
> can@e0009000 {
> compatible = "xlnx,zynq-can-1.0";
> status = "disabled";
> clocks = <0x1 0x14 0x1 0x25>;
> clock-names = "can_clk", "pclk";
> reg = <0xe0009000 0x1000>;
> interrupts = <0x0 0x33 0x4>;
> interrupt-parent = <0x3>;
> tx-fifo-depth = <0x40>;
> rx-fifo-depth = <0x40>;
> };
>
> gpio@e000a000 {
> compatible = "xlnx,zynq-gpio-1.0";
> #gpio-cells = <0x2>;
> #interrupt-cells = <0x2>;
> clocks = <0x1 0x2a>;
> gpio-controller;
> interrupt-controller;
> interrupt-parent = <0x3>;
> interrupts = <0x0 0x14 0x4>;
> reg = <0xe000a000 0x1000>;
> };
>
> i2c@e0004000 {
> compatible = "cdns,i2c-r1p10";
> status = "disabled";
> clocks = <0x1 0x26>;
> interrupt-parent = <0x3>;
> interrupts = <0x0 0x19 0x4>;
> reg = <0xe0004000 0x1000>;
> #address-cells = <0x1>;
> #size-cells = <0x0>;
> };
>
> i2c@e0005000 {
>

Re: [U-Boot] [PicoZed] Error in NET and SD Card

2016-10-13 Thread Jaehoon Chung 
On 10/13/2016 06:49 PM, Oscar Gomez Fuente wrote:
> Hi Jaehoon,
> 
> 
> I've tried to add the #define CONFIG_MMC_TRACE in the file 
> include/configs/zynq-common.h
> 
> But after compiled and boot u-boot, It doesn't appear any messages:
> 
> ---
> U-Boot 2016.11-rc1-00139-gf5fd45f-dirty (Oct 13 2016 - 11:33:25 +0200)
> 
> Model: Zynq PicoZed Board
> Board: Xilinx Zynq
> DRAM:  ECC disabled 1 GiB
> MMC:   
> Using default environment
> 
> In:serial@e0001000
> Out:   serial@e0001000
> Err:   serial@e0001000
> Model: Zynq PicoZed Board
> Board: Xilinx Zynq
> Net:   No ethernet found.
> ** Bad device mmc 0 **
> Checking if uenvcmd is set ...
> Hit any key to stop autoboot:  0 
> Zynq> mmcinfo
> No MMC device available
> Zynq> 
> ---
> 
> I think I'm doing something wrong. Any suggestion?

It seems the can't get the bootdevice...maybe it seems nothing to do for mmc/sd 
driver..so seems it can't find any block devices.

I added one comment on below...

> 
> As you know it doesn't work the ethernet as well as the SD Card, so I've 
> decided to get from the u-boot.dtb the u-boot.dts, and I've just realised 
> that the two ethernet ports have the status disabled, as well as the sdhci, 
> so I think is something related to the way the dtb file is generated.
> 
> To get the u-boot-dtb file, I had to configure: 
> 
>> Device Tree Control  Provider of DTB for DT control > (X) Separate DTB for 
>> DT control
> 
> I usually use the mode  (X ) Embedded DTB for DT control, because a use the 
> application bootgen from Xilinx and I need to have the dtb embedded, but I 
> used this way only to get the dts file.
> 
> This is the u-boot.dts file I got:
> 
> ---
> /dts-v1/;
> 
> / {
> #address-cells = <0x1>;
> #size-cells = <0x1>;
> compatible = "xlnx,zynq-picozed", "xlnx,zynq-7000";
> model = "Zynq PicoZed Board";
> 
> chosen {
> };
> 
> aliases {
> serial0 = "/amba/serial@e0001000";
> };
> 
> memory {
> device_type = "memory";
> reg = <0x0 0x4000>;
> };
> 
> cpus {
> #address-cells = <0x1>;
> #size-cells = <0x0>;
> 
> cpu@0 {
> compatible = "arm,cortex-a9";
> device_type = "cpu";
> reg = <0x0>;
> clocks = <0x1 0x3>;
> clock-latency = <0x3e8>;
> cpu0-supply = <0x2>;
> operating-points = <0xa2c2b 0xf4240 0x51616 0xf4240>;
> };
> 
> cpu@1 {
> compatible = "arm,cortex-a9";
> device_type = "cpu";
> reg = <0x1>;
> clocks = <0x1 0x3>;
> };
> };
> 
> pmu {
> compatible = "arm,cortex-a9-pmu";
> interrupts = <0x0 0x5 0x4 0x0 0x6 0x4>;
> interrupt-parent = <0x3>;
> reg = <0xf8891000 0x1000 0xf8893000 0x1000>;
> };
> 
> fixedregulator@0 {
> compatible = "regulator-fixed";
> regulator-name = "VCCPINT";
> regulator-min-microvolt = <0xf4240>;
> regulator-max-microvolt = <0xf4240>;
> regulator-boot-on;
> regulator-always-on;
> linux,phandle = <0x2>;
> phandle = <0x2>;
> };
> 
> amba {
> u-boot,dm-pre-reloc;
> compatible = "simple-bus";
> #address-cells = <0x1>;
> #size-cells = <0x1>;
> interrupt-parent = <0x3>;
> ranges;
> 
> adc@f8007100 {
> compatible = "xlnx,zynq-xadc-1.00.a";
> reg = <0xf8007100 0x20>;
> interrupts = <0x0 0x7 0x4>;
> interrupt-parent = <0x3>;
> clocks = <0x1 0xc>;
> };
> 
> can@e0008000 {
> compatible = "xlnx,zynq-can-1.0";
> status = "disabled";
> clocks = <0x1 0x13 0x1 0x24>;
> clock-names = "can_clk", "pclk";
> reg = <0xe0008000 0x1000>;
> interrupts = <0x0 0x1c 0x4>;
> interrupt-parent = <0x3>;
> tx-fifo-depth = <0x40>;
> rx-fifo-depth = <0x40>;
> };
> 
> can@e0009000 {
> compatible = "xlnx,zynq-can-1.0";
> status = "disabled";
> clocks = <0x1 0x14 0x1 0x25>;
> clock-names = "can_clk", "pclk";
> reg = <0xe0009000 0x1000>;
> interrupts = <0x0 0x33 0x4>;
> interrupt-parent = <0x3>;
> tx-fifo-depth = <0x40>;
> rx-fifo-depth = <0x40>;
> };
> 
> gpio@e000a000 {
> compatible = "xlnx,zynq-gpio-1.0";
> #gpio-cells = <0x2>;
> #interrupt-cells = <0x2>;
> clocks = <0x1 0x2a>;
> gpio-controller;
> interrupt-controller;
> interrupt-parent = <0x3>;
> interrupts = <0x0 0x14 0x4>;
> reg = <0xe000a000 0x1000>;
> };
> 
> i2c@e0004000 {
> compatible = "cdns,i2c-r1p10";
> status = "disabled";
> clocks = <0x1 0x26>;
> interrupt-parent = <0x3>;
> interrupts = <0x0 0x19 0x4>;
> reg = <0xe0004000 0x1000>;
> #address-cells = <0x1>;
> #size-cells = <0x0>;
> };
> 
> i2c@e0005000 {
> compatible = "cdns,i2c-r1p10";
> status = "disabled";
> clocks = <0x1 0x27>;
> interrupt-parent = <0x3>;
> interrupts = <0x0 0x30 0x4>;
> reg = <0xe0005000 0x1000>;
> #address-cells = <0x1>;
> #size-cells = <0x0>;
> };
> 
> interrupt-controller@f8f01000 {
> compatible = "arm,cortex-a9-gic";
> #interrupt-cells = <0x3>;
> interrupt-controller;
> reg = <0xf8f01000 0x1000 0xf8f00100 0x100>;
> linux,phandle = <0x3>;
> phandle = <0x3>;
> };
> 
> cache-controller@f8f02000 {
> compatible = "arm,pl310-cache";
> reg = <0xf8f02000 0x1000>;
> interrupts = <0x0 0x2 0x4>;
> arm,data-latency = <0x3 0x2 0x2>;
> arm,tag-latency = <0x2 0x2 0x2>;
> cache-unified;
> cache-level = <0x2>;
> };
>

Re: [U-Boot] [PicoZed] Error in NET and SD Card

2016-10-13 Thread Oscar Gomez Fuente 
Hi Jaehoon,


I've tried to add the #define CONFIG_MMC_TRACE in the file
include/configs/zynq-common.h

But after compiled and boot u-boot, It doesn't appear any messages:

---
U-Boot 2016.11-rc1-00139-gf5fd45f-dirty (Oct 13 2016 - 11:33:25 +0200)

Model: Zynq PicoZed Board
Board: Xilinx Zynq
DRAM:  ECC disabled 1 GiB
MMC:
Using default environment

In:serial@e0001000
Out:   serial@e0001000
Err:   serial@e0001000
Model: Zynq PicoZed Board
Board: Xilinx Zynq
Net:   No ethernet found.
** Bad device mmc 0 **
Checking if uenvcmd is set ...
Hit any key to stop autoboot:  0
Zynq> mmcinfo
No MMC device available
Zynq>
---

I think I'm doing something wrong. Any suggestion?

As you know it doesn't work the ethernet as well as the SD Card, so I've
decided to get from the u-boot.dtb the u-boot.dts, and I've just realised
that the two ethernet ports have the status disabled, as well as the sdhci,
so I think is something related to the way the dtb file is generated.

To get the u-boot-dtb file, I had to configure:

> Device Tree Control  Provider of DTB for DT control > (X) Separate DTB
for DT control

I usually use the mode  (X ) Embedded DTB for DT control, because a use the
application bootgen from Xilinx and I need to have the dtb embedded, but I
used this way only to get the dts file.

This is the u-boot.dts file I got:

---
/dts-v1/;

/ {
#address-cells = <0x1>;
#size-cells = <0x1>;
compatible = "xlnx,zynq-picozed", "xlnx,zynq-7000";
model = "Zynq PicoZed Board";

chosen {
};

aliases {
serial0 = "/amba/serial@e0001000";
};

memory {
device_type = "memory";
reg = <0x0 0x4000>;
};

cpus {
#address-cells = <0x1>;
#size-cells = <0x0>;

cpu@0 {
compatible = "arm,cortex-a9";
device_type = "cpu";
reg = <0x0>;
clocks = <0x1 0x3>;
clock-latency = <0x3e8>;
cpu0-supply = <0x2>;
operating-points = <0xa2c2b 0xf4240 0x51616 0xf4240>;
};

cpu@1 {
compatible = "arm,cortex-a9";
device_type = "cpu";
reg = <0x1>;
clocks = <0x1 0x3>;
};
};

pmu {
compatible = "arm,cortex-a9-pmu";
interrupts = <0x0 0x5 0x4 0x0 0x6 0x4>;
interrupt-parent = <0x3>;
reg = <0xf8891000 0x1000 0xf8893000 0x1000>;
};

fixedregulator@0 {
compatible = "regulator-fixed";
regulator-name = "VCCPINT";
regulator-min-microvolt = <0xf4240>;
regulator-max-microvolt = <0xf4240>;
regulator-boot-on;
regulator-always-on;
linux,phandle = <0x2>;
phandle = <0x2>;
};

amba {
u-boot,dm-pre-reloc;
compatible = "simple-bus";
#address-cells = <0x1>;
#size-cells = <0x1>;
interrupt-parent = <0x3>;
ranges;

adc@f8007100 {
compatible = "xlnx,zynq-xadc-1.00.a";
reg = <0xf8007100 0x20>;
interrupts = <0x0 0x7 0x4>;
interrupt-parent = <0x3>;
clocks = <0x1 0xc>;
};

can@e0008000 {
compatible = "xlnx,zynq-can-1.0";
status = "disabled";
clocks = <0x1 0x13 0x1 0x24>;
clock-names = "can_clk", "pclk";
reg = <0xe0008000 0x1000>;
interrupts = <0x0 0x1c 0x4>;
interrupt-parent = <0x3>;
tx-fifo-depth = <0x40>;
rx-fifo-depth = <0x40>;
};

can@e0009000 {
compatible = "xlnx,zynq-can-1.0";
status = "disabled";
clocks = <0x1 0x14 0x1 0x25>;
clock-names = "can_clk", "pclk";
reg = <0xe0009000 0x1000>;
interrupts = <0x0 0x33 0x4>;
interrupt-parent = <0x3>;
tx-fifo-depth = <0x40>;
rx-fifo-depth = <0x40>;
};

gpio@e000a000 {
compatible = "xlnx,zynq-gpio-1.0";
#gpio-cells = <0x2>;
#interrupt-cells = <0x2>;
clocks = <0x1 0x2a>;
gpio-controller;
interrupt-controller;
interrupt-parent = <0x3>;
interrupts = <0x0 0x14 0x4>;
reg = <0xe000a000 0x1000>;
};

i2c@e0004000 {
compatible = "cdns,i2c-r1p10";
status = "disabled";
clocks = <0x1 0x26>;
interrupt-parent = <0x3>;
interrupts = <0x0 0x19 0x4>;
reg = <0xe0004000 0x1000>;
#address-cells = <0x1>;
#size-cells = <0x0>;
};

i2c@e0005000 {
compatible = "cdns,i2c-r1p10";
status = "disabled";
clocks = <0x1 0x27>;
interrupt-parent = <0x3>;
interrupts = <0x0 0x30 0x4>;
reg = <0xe0005000 0x1000>;
#address-cells = <0x1>;
#size-cells = <0x0>;
};

interrupt-controller@f8f01000 {
compatible = "arm,cortex-a9-gic";
#interrupt-cells = <0x3>;
interrupt-controller;
reg = <0xf8f01000 0x1000 0xf8f00100 0x100>;
linux,phandle = <0x3>;
phandle = <0x3>;
};

cache-controller@f8f02000 {
compatible = "arm,pl310-cache";
reg = <0xf8f02000 0x1000>;
interrupts = <0x0 0x2 0x4>;
arm,data-latency = <0x3 0x2 0x2>;
arm,tag-latency = <0x2 0x2 0x2>;
cache-unified;
cache-level = <0x2>;
};

memory-controller@f8006000 {
compatible = "xlnx,zynq-ddrc-a05";
reg = <0xf8006000 0x1000>;
};

serial@e000 {
compatible = "xlnx,xuartps", "cdns,uart-r1p8";
status = "disabled";
clocks = <0x1 0x17 0x1 0x28>;
clock-names = "uart_clk", "pclk";
reg = <0xe000 0x1000>;
interrupts = <0x0 0x1b 0x4>;
};

serial@e0001000 {
compatible = "xlnx,xuartps", "cdns,uart-r1p8";
status = "okay";
clocks = <0x1 0x18 0x1 0x29>;
clock-names = "uart_clk", "pclk";
reg = <0xe0001000 0x1000>;
interrupts = <0x0 0x32 0x4>;
u-boot,dm-pre-reloc;
};

spi@e0006000 {
compatible = "xlnx,zynq-spi-r1p6";
reg = <0xe0006000 0x1000>;
status = "disabled";

Re: [U-Boot] [PicoZed] Error in NET and SD Card

2016-10-12 Thread Jaehoon Chung 
On 10/12/2016 05:36 PM, Oscar Gomez Fuente wrote:
> Hi Jaehoon,
> 
> 
> How can I enable the CONFG_MMC_TRACE? I couldn't find this option in the 
> menuconfig.
> 
> Is it enough to add "CONFIG_MMC_TRACE=y" in the .config file?

Yes..CONFIG_MMC_TRACE=y or add the CONFIG_MMC_TRACE in your config file.

Best Regards,
Jaehoon Chung

> 
> 
> Best regards.
> 
> Oscar Gomez Fuente.
> 
> On 12 October 2016 at 06:46, Jaehoon Chung  > wrote:
> 
> Hi
> 
> On 10/11/2016 11:08 PM, Oscar Gomez Fuente wrote:
> > Hi everyone,
> >
> > I've just compiled u-boot for a picoZed platform with
> > the zynq_picozed_defconfig, and I've realised that the NET and SD Card
> > aren't recognised. In the init I see these messages:
> >
> > I boot from the SD Card and I see these messages from my uart terminal:
> >
> > -
> > U-Boot 2016.11-rc1-00139-gf5fd45f (Oct 11 2016 - 15:48:54 +0200)
> >
> > Model: Zynq PicoZed Board
> > Board: Xilinx Zynq
> > DRAM:  ECC disabled 1 GiB
> > MMC:
> > Using default environment
> >
> > In:serial@e0001000
> > Out:   serial@e0001000
> > Err:   serial@e0001000
> > Model: Zynq PicoZed Board
> > Board: Xilinx Zynq
> > Net:   No ethernet found.
> > ** Bad device mmc 0 **
> > Checking if uenvcmd is set ...
> > Hit any key to stop autoboot:  0
> > -
> >
> > So, I think something has broken. Could anyone chek this issue?
> 
> Could you enable the CONFIG_MMC_TRACE? then we can see more information.
> And which config do you use?
> 
> Best Regards,
> Jaehoon Chung
> 
> >
> >
> > Thank you very much. Best regards.
> >
> > Oscar Gomez Fuente
> > ___
> > U-Boot mailing list
> > U-Boot@lists.denx.de 
> > http://lists.denx.de/mailman/listinfo/u-boot 
> 
> >
> >
> >
> 
> 

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PicoZed] Error in NET and SD Card

2016-10-12 Thread Oscar Gomez Fuente 
Hi Jaehoon,


How can I enable the CONFG_MMC_TRACE? I couldn't find this option in the
menuconfig.

Is it enough to add "CONFIG_MMC_TRACE=y" in the .config file?


Best regards.

Oscar Gomez Fuente.

On 12 October 2016 at 06:46, Jaehoon Chung  wrote:

> Hi
>
> On 10/11/2016 11:08 PM, Oscar Gomez Fuente wrote:
> > Hi everyone,
> >
> > I've just compiled u-boot for a picoZed platform with
> > the zynq_picozed_defconfig, and I've realised that the NET and SD Card
> > aren't recognised. In the init I see these messages:
> >
> > I boot from the SD Card and I see these messages from my uart terminal:
> >
> > -
> > U-Boot 2016.11-rc1-00139-gf5fd45f (Oct 11 2016 - 15:48:54 +0200)
> >
> > Model: Zynq PicoZed Board
> > Board: Xilinx Zynq
> > DRAM:  ECC disabled 1 GiB
> > MMC:
> > Using default environment
> >
> > In:serial@e0001000
> > Out:   serial@e0001000
> > Err:   serial@e0001000
> > Model: Zynq PicoZed Board
> > Board: Xilinx Zynq
> > Net:   No ethernet found.
> > ** Bad device mmc 0 **
> > Checking if uenvcmd is set ...
> > Hit any key to stop autoboot:  0
> > -
> >
> > So, I think something has broken. Could anyone chek this issue?
>
> Could you enable the CONFIG_MMC_TRACE? then we can see more information.
> And which config do you use?
>
> Best Regards,
> Jaehoon Chung
>
> >
> >
> > Thank you very much. Best regards.
> >
> > Oscar Gomez Fuente
> > ___
> > U-Boot mailing list
> > U-Boot@lists.denx.de
> > http://lists.denx.de/mailman/listinfo/u-boot
> >
> >
> >
>
>
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PicoZed] Error in NET and SD Card

2016-10-11 Thread Jaehoon Chung 
Hi

On 10/11/2016 11:08 PM, Oscar Gomez Fuente wrote:
> Hi everyone,
> 
> I've just compiled u-boot for a picoZed platform with
> the zynq_picozed_defconfig, and I've realised that the NET and SD Card
> aren't recognised. In the init I see these messages:
> 
> I boot from the SD Card and I see these messages from my uart terminal:
> 
> -
> U-Boot 2016.11-rc1-00139-gf5fd45f (Oct 11 2016 - 15:48:54 +0200)
> 
> Model: Zynq PicoZed Board
> Board: Xilinx Zynq
> DRAM:  ECC disabled 1 GiB
> MMC:
> Using default environment
> 
> In:serial@e0001000
> Out:   serial@e0001000
> Err:   serial@e0001000
> Model: Zynq PicoZed Board
> Board: Xilinx Zynq
> Net:   No ethernet found.
> ** Bad device mmc 0 **
> Checking if uenvcmd is set ...
> Hit any key to stop autoboot:  0
> -
> 
> So, I think something has broken. Could anyone chek this issue?

Could you enable the CONFIG_MMC_TRACE? then we can see more information.
And which config do you use?

Best Regards,
Jaehoon Chung

> 
> 
> Thank you very much. Best regards.
> 
> Oscar Gomez Fuente
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
> 
> 
> 

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot