Wandboard U-boot (2013.07-rc3) issues

Wandboard U-boot (2013.07-rc3) issues

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 529 bytes --]

Folks,

I'm facing an issue on power-up sequence I get the below messages after
bootdelay:

mmc0 is current device
Card did not respond to voltage select!
Booting from net ...
FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2
...


This happens sporadically.


Regards,

--
*dS
Diego Sueiro

Administrador do Portal Embarcados
www.embarcados.com.br

Engenheiro de Controle e Automação
UNIVERSIDADE FEDERAL DE ITAJUBÀ

/*long live rock 'n roll*/

[-- Attachment #2: Type: text/html, Size: 1035 bytes --]

Re: Wandboard U-boot (2013.07-rc3) issues

[Fabio Estevam]

On Tue, Jul 23, 2013 at 5:42 PM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> Folks,
>
> I'm facing an issue on power-up sequence I get the below messages after
> bootdelay:
>
> mmc0 is current device
> Card did not respond to voltage select!
> Booting from net ...
> FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
> BOOTP broadcast 1
> BOOTP broadcast 2

Please try 2013.07 instead and let us know if you face issues.

Re: Wandboard U-boot (2013.07-rc3) issues

[Otavio Salvador]

On Tue, Jul 23, 2013 at 5:49 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Tue, Jul 23, 2013 at 5:42 PM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
>> Folks,
>>
>> I'm facing an issue on power-up sequence I get the below messages after
>> bootdelay:
>>
>> mmc0 is current device
>> Card did not respond to voltage select!
>> Booting from net ...
>> FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
>> BOOTP broadcast 1
>> BOOTP broadcast 2
>
> Please try 2013.07 instead and let us know if you face issues.

This is ready for use in master-next; I am using it for netboot :-)

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Wandboard U-boot (2013.07-rc3) issues

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]

Folks,

I've built the u-boot 2013-07 version and burned it onto sdcard and the
issue still happens.

Here is the console output:

U-Boot 2013.07 (Jul 23 2013 - 23:25:04)

CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
Reset cause: POR
Board: Wandboard
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Hit any key to stop autoboot:  0
mmc0 is current device
Card did not respond to voltage select!
Booting from net ...
FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5

Retry count exceeded; starting again
FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5



Abraços,

--
*dS
Diego Sueiro

Administrador do Portal Embarcados
www.embarcados.com.br

Engenheiro de Controle e Automação
UNIVERSIDADE FEDERAL DE ITAJUBÀ

/*long live rock 'n roll*/


On Tue, Jul 23, 2013 at 5:53 PM, Otavio Salvador <otavio@ossystems.com.br>wrote:

> On Tue, Jul 23, 2013 at 5:49 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Tue, Jul 23, 2013 at 5:42 PM, Diego Sueiro <diego.sueiro@gmail.com>
> wrote:
> >> Folks,
> >>
> >> I'm facing an issue on power-up sequence I get the below messages after
> >> bootdelay:
> >>
> >> mmc0 is current device
> >> Card did not respond to voltage select!
> >> Booting from net ...
> >> FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
> >> BOOTP broadcast 1
> >> BOOTP broadcast 2
> >
> > Please try 2013.07 instead and let us know if you face issues.
>
> This is ready for use in master-next; I am using it for netboot :-)
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://projetos.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>

[-- Attachment #2: Type: text/html, Size: 3341 bytes --]

Re: Wandboard U-boot (2013.07-rc3) issues

[Fabio Estevam]

On Wed, Jul 24, 2013 at 8:09 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> Folks,
>
> I've built the u-boot 2013-07 version and burned it onto sdcard and the
> issue still happens.
>
> Here is the console output:
>
> U-Boot 2013.07 (Jul 23 2013 - 23:25:04)
>
> CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
> Reset cause: POR
> Board: Wandboard
> DRAM:  1 GiB
> MMC:   FSL_SDHC: 0, FSL_SDHC: 1
> In:    serial
> Out:   serial
> Err:   serial
> Net:   FEC [PRIME]
> Hit any key to stop autoboot:  0
> mmc0 is current device
> Card did not respond to voltage select!

You should try to debug why you are getting such "voltage select" error.

> Booting from net ...
> FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3

I assume you are trying to transfer kernel via dhcp, right?

In case you want to transfer via tftp you need to do:

setenv ip_dyn no

By default, the U-boot environment variables will attempt to boot the
kernel from the SD card. Please clarify where you want to retrieve the
kernel from.

If you want to load the kernel via tftp or dhcp, then you need to set
the 'serverip' variable.

setenv serverip 192.168.0.1

setenv ipaddr 192.168.0.2 (if you want to use tftp)

You can also reset the environment variables into the default configuration:

env default -f -a

Re: Wandboard U-boot (2013.07-rc3) issues

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]

Hi Fabio,

Both kernel and rootfs are on sdcard.

Looking at boot scripts the u-boot will try network boot if it didn't find
the kernel image onto sdcard.

I'll try to use another sdcard to see if I can reproduce this.


Abraços,

--
*dS
Diego Sueiro

Administrador do Portal Embarcados
www.embarcados.com.br

Engenheiro de Controle e Automação
UNIVERSIDADE FEDERAL DE ITAJUBÀ

/*long live rock 'n roll*/


On Wed, Jul 24, 2013 at 8:45 AM, Fabio Estevam <festevam@gmail.com> wrote:

> On Wed, Jul 24, 2013 at 8:09 AM, Diego Sueiro <diego.sueiro@gmail.com>
> wrote:
> > Folks,
> >
> > I've built the u-boot 2013-07 version and burned it onto sdcard and the
> > issue still happens.
> >
> > Here is the console output:
> >
> > U-Boot 2013.07 (Jul 23 2013 - 23:25:04)
> >
> > CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
> > Reset cause: POR
> > Board: Wandboard
> > DRAM:  1 GiB
> > MMC:   FSL_SDHC: 0, FSL_SDHC: 1
> > In:    serial
> > Out:   serial
> > Err:   serial
> > Net:   FEC [PRIME]
> > Hit any key to stop autoboot:  0
> > mmc0 is current device
> > Card did not respond to voltage select!
>
> You should try to debug why you are getting such "voltage select" error.
>
> > Booting from net ...
> > FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
> > BOOTP broadcast 1
> > BOOTP broadcast 2
> > BOOTP broadcast 3
>
> I assume you are trying to transfer kernel via dhcp, right?
>
> In case you want to transfer via tftp you need to do:
>
> setenv ip_dyn no
>
> By default, the U-boot environment variables will attempt to boot the
> kernel from the SD card. Please clarify where you want to retrieve the
> kernel from.
>
> If you want to load the kernel via tftp or dhcp, then you need to set
> the 'serverip' variable.
>
> setenv serverip 192.168.0.1
>
> setenv ipaddr 192.168.0.2 (if you want to use tftp)
>
> You can also reset the environment variables into the default
> configuration:
>
> env default -f -a
>

[-- Attachment #2: Type: text/html, Size: 2899 bytes --]

Re: Wandboard U-boot (2013.07-rc3) issues

[Otavio Salvador]

On Wed, Jul 24, 2013 at 9:24 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> Hi Fabio,
>
> Both kernel and rootfs are on sdcard.
>
> Looking at boot scripts the u-boot will try network boot if it didn't find
> the kernel image onto sdcard.
>
> I'll try to use another sdcard to see if I can reproduce this.

I am using this in wandboard-dual for testing and it works  fine here.
Are you sure you did rewrite the U-Boot binary?

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Wandboard U-boot (2013.07-rc3) issues

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 845 bytes --]

On Wed, Jul 24, 2013 at 9:27 AM, Otavio Salvador <otavio@ossystems.com.br>wrote:

> On Wed, Jul 24, 2013 at 9:24 AM, Diego Sueiro <diego.sueiro@gmail.com>
> wrote:
> > Hi Fabio,
> >
> > Both kernel and rootfs are on sdcard.
> >
> > Looking at boot scripts the u-boot will try network boot if it didn't
> find
> > the kernel image onto sdcard.
> >
> > I'll try to use another sdcard to see if I can reproduce this.
>
> I am using this in wandboard-dual for testing and it works  fine here.
> Are you sure you did rewrite the U-Boot binary?
>
>
Yep. It prints on console:

U-Boot 2013.07 (Jul 23 2013 - 23:25:04)



> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://projetos.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>

[-- Attachment #2: Type: text/html, Size: 2053 bytes --]

Re: Wandboard U-boot (2013.07-rc3) issues

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]

Folks,

I used two 8GB (class 6) uSD from Samsung and this issue is reproduced
sporadically.

But for a 4GB (class 4) uSD from Kingston it booted without issues.


Abraços,

--
*dS
Diego Sueiro

Administrador do Portal Embarcados
www.embarcados.com.br

Engenheiro de Controle e Automação
UNIVERSIDADE FEDERAL DE ITAJUBÀ

/*long live rock 'n roll*/


On Wed, Jul 24, 2013 at 9:32 AM, Diego Sueiro <diego.sueiro@gmail.com>wrote:

>
> On Wed, Jul 24, 2013 at 9:27 AM, Otavio Salvador <otavio@ossystems.com.br>wrote:
>
>> On Wed, Jul 24, 2013 at 9:24 AM, Diego Sueiro <diego.sueiro@gmail.com>
>> wrote:
>> > Hi Fabio,
>> >
>> > Both kernel and rootfs are on sdcard.
>> >
>> > Looking at boot scripts the u-boot will try network boot if it didn't
>> find
>> > the kernel image onto sdcard.
>> >
>> > I'll try to use another sdcard to see if I can reproduce this.
>>
>> I am using this in wandboard-dual for testing and it works  fine here.
>> Are you sure you did rewrite the U-Boot binary?
>>
>>
> Yep. It prints on console:
>
> U-Boot 2013.07 (Jul 23 2013 - 23:25:04)
>
>
>
>> --
>>
>> Otavio Salvador                             O.S. Systems
>> http://www.ossystems.com.br        http://projetos.ossystems.com.br
>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>
>
>

[-- Attachment #2: Type: text/html, Size: 3047 bytes --]

Re: Wandboard U-boot (2013.07-rc3) issues

[Fabio Estevam]

Hi Diego,

On Wed, Jul 24, 2013 at 10:00 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> Folks,
>
> I used two 8GB (class 6) uSD from Samsung and this issue is reproduced
> sporadically.
>
> But for a 4GB (class 4) uSD from Kingston it booted without issues.

That's interesting.

If you could ship me one of this Samsung card, I will be glad to debug it.

Regards,

Fabio Estevam

Re: Wandboard U-boot (2013.07-rc3) issues

[Marek Vasut]

Dear Fabio Estevam,

> Hi Diego,
> 
> On Wed, Jul 24, 2013 at 10:00 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> > Folks,
> > 
> > I used two 8GB (class 6) uSD from Samsung and this issue is reproduced
> > sporadically.
> > 
> > But for a 4GB (class 4) uSD from Kingston it booted without issues.
> 
> That's interesting.
> 
> If you could ship me one of this Samsung card, I will be glad to debug it.

Does is also happen with 2013.04? If not, you can bisect it.

Best regards,
Marek Vasut

Re: Wandboard U-boot (2013.07-rc3) issues

[Otavio Salvador]

On Fri, Jul 26, 2013 at 1:38 AM, Marek Vasut <marex@denx.de> wrote:
> Dear Fabio Estevam,
>
>> Hi Diego,
>>
>> On Wed, Jul 24, 2013 at 10:00 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
>> > Folks,
>> >
>> > I used two 8GB (class 6) uSD from Samsung and this issue is reproduced
>> > sporadically.
>> >
>> > But for a 4GB (class 4) uSD from Kingston it booted without issues.
>>
>> That's interesting.
>>
>> If you could ship me one of this Samsung card, I will be glad to debug it.
>
> Does is also happen with 2013.04? If not, you can bisect it.

Diego,

did you try to reproduce it using old U-Boot?

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Wandboard U-boot (2013.07-rc3) issues

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 3127 bytes --]

Hi there,

I believe that v2013.04 is not using the right default environment values
because of the error message below.

U-Boot 2013.04 (Aug 07 2013 - 08:06:08)

CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
Reset cause: POR
Board: Wandboard
DRAM:  1 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Warning: FEC using MAC address from net device

Hit any key to stop autoboot:  0
mmc0 is current device
** Unrecognized filesystem type **
** Unrecognized filesystem type **
Booting from net ...
FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3

Anyone has this binary version to send me?


When trying to compile v2013.04 u-boot version I had to do
some workarounds to get it done.

Build Configuration:
BB_VERSION        = "1.19.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-12.10"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "wandboard-dual"
DISTRO            = "poky"
DISTRO_VERSION    = "1.4+snapshot-20130807"
TUNE_FEATURES     = "armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        = "master:9de0ad47462c13ac4a2d73e12e92be6c1b4e0415"
meta-oe           = "master:6b50a7d6621eba239380b11606110caab814eb51"
meta-fsl-arm      = "master-next:65779d09ca241acb23a1d018d47b55cc260cb056"
meta-fsl-arm-extra = "master-next:134324944624bf6913c8c09d7cbae2e76e0bfd24"
meta-fsl-demos    = "master-next:2c63f9ff40e940ce120f005075429ffc06bbface"


Steps:

bitbake u-boot -c devshell

git ckeckout v2013.04

export CROSS_COMPILE=arm-poky-linux-gnueabi- //Without this I get
a /bin/bash: arm-linux-gcc: command not found

export LDFLAGS  //Without this I got linker error
about unrecognized options.

make distclean

make wandboard_dl_config

make


Regards,

--
*dS
Diego Sueiro

Administrador do Portal Embarcados
www.embarcados.com.br

Engenheiro de Controle e Automação
UNIVERSIDADE FEDERAL DE ITAJUBÀ

/*long live rock 'n roll*/


On Tue, Aug 6, 2013 at 9:16 AM, Otavio Salvador <otavio@ossystems.com.br>wrote:

> On Fri, Jul 26, 2013 at 1:38 AM, Marek Vasut <marex@denx.de> wrote:
> > Dear Fabio Estevam,
> >
> >> Hi Diego,
> >>
> >> On Wed, Jul 24, 2013 at 10:00 AM, Diego Sueiro <diego.sueiro@gmail.com>
> wrote:
> >> > Folks,
> >> >
> >> > I used two 8GB (class 6) uSD from Samsung and this issue is reproduced
> >> > sporadically.
> >> >
> >> > But for a 4GB (class 4) uSD from Kingston it booted without issues.
> >>
> >> That's interesting.
> >>
> >> If you could ship me one of this Samsung card, I will be glad to debug
> it.
> >
> > Does is also happen with 2013.04? If not, you can bisect it.
>
> Diego,
>
> did you try to reproduce it using old U-Boot?
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://projetos.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>

[-- Attachment #2: Type: text/html, Size: 5655 bytes --]

Re: Wandboard U-boot (2013.07-rc3) issues

[Otavio Salvador]

On Wed, Aug 7, 2013 at 8:33 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
> Hi there,
>
> I believe that v2013.04 is not using the right default environment values
> because of the error message below.
>
> U-Boot 2013.04 (Aug 07 2013 - 08:06:08)
>
> CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
> Reset cause: POR
> Board: Wandboard
> DRAM:  1 GiB
> MMC:   FSL_SDHC: 0
> *** Warning - bad CRC, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Net:   FEC [PRIME]
> Warning: FEC using MAC address from net device
>
> Hit any key to stop autoboot:  0
> mmc0 is current device
> ** Unrecognized filesystem type **
> ** Unrecognized filesystem type **
> Booting from net ...
> FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3
>
> Anyone has this binary version to send me?

You can build it but use our branch which had the env and backports:

https://github.com/Freescale/u-boot-imx/tree/patches-2012.04.01

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Wandboard U-boot (2013.07-rc3) issues

[Otavio Salvador]

On Wed, Aug 7, 2013 at 8:49 AM, Otavio Salvador <otavio@ossystems.com.br> wrote:
> On Wed, Aug 7, 2013 at 8:33 AM, Diego Sueiro <diego.sueiro@gmail.com> wrote:
>> Hi there,
>>
>> I believe that v2013.04 is not using the right default environment values
>> because of the error message below.
>>
>> U-Boot 2013.04 (Aug 07 2013 - 08:06:08)
>>
>> CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
>> Reset cause: POR
>> Board: Wandboard
>> DRAM:  1 GiB
>> MMC:   FSL_SDHC: 0
>> *** Warning - bad CRC, using default environment
>>
>> In:    serial
>> Out:   serial
>> Err:   serial
>> Net:   FEC [PRIME]
>> Warning: FEC using MAC address from net device
>>
>> Hit any key to stop autoboot:  0
>> mmc0 is current device
>> ** Unrecognized filesystem type **
>> ** Unrecognized filesystem type **
>> Booting from net ...
>> FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
>> BOOTP broadcast 1
>> BOOTP broadcast 2
>> BOOTP broadcast 3
>>
>> Anyone has this binary version to send me?
>
> You can build it but use our branch which had the env and backports:
>
> https://github.com/Freescale/u-boot-imx/tree/patches-2012.04.01

https://github.com/Freescale/u-boot-imx/tree/patches-2013.04 , sorry.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: Wandboard U-boot (2013.07-rc3) issues

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 2444 bytes --]

The issue is still reproduced with v2013.04 patched version:

U-Boot 2013.04 (Aug 07 2013 - 11:32:45)

CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
Reset cause: POR
Board: Wandboard
DRAM:  1 GiB
MMC:   FSL_SDHC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
Warning: FEC using MAC address from net device

Hit any key to stop autoboot:  0
mmc0 is current device
Card did not respond to voltage select!
Booting from net ...
FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
BOOTP broadcast 1
BOOTP broadcast 2



Abraços,

--
*dS
Diego Sueiro

Administrador do Portal Embarcados
www.embarcados.com.br

Engenheiro de Controle e Automação
UNIVERSIDADE FEDERAL DE ITAJUBÀ

/*long live rock 'n roll*/


On Wed, Aug 7, 2013 at 8:49 AM, Otavio Salvador <otavio@ossystems.com.br>wrote:

> On Wed, Aug 7, 2013 at 8:49 AM, Otavio Salvador <otavio@ossystems.com.br>
> wrote:
> > On Wed, Aug 7, 2013 at 8:33 AM, Diego Sueiro <diego.sueiro@gmail.com>
> wrote:
> >> Hi there,
> >>
> >> I believe that v2013.04 is not using the right default environment
> values
> >> because of the error message below.
> >>
> >> U-Boot 2013.04 (Aug 07 2013 - 08:06:08)
> >>
> >> CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
> >> Reset cause: POR
> >> Board: Wandboard
> >> DRAM:  1 GiB
> >> MMC:   FSL_SDHC: 0
> >> *** Warning - bad CRC, using default environment
> >>
> >> In:    serial
> >> Out:   serial
> >> Err:   serial
> >> Net:   FEC [PRIME]
> >> Warning: FEC using MAC address from net device
> >>
> >> Hit any key to stop autoboot:  0
> >> mmc0 is current device
> >> ** Unrecognized filesystem type **
> >> ** Unrecognized filesystem type **
> >> Booting from net ...
> >> FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
> >> BOOTP broadcast 1
> >> BOOTP broadcast 2
> >> BOOTP broadcast 3
> >>
> >> Anyone has this binary version to send me?
> >
> > You can build it but use our branch which had the env and backports:
> >
> > https://github.com/Freescale/u-boot-imx/tree/patches-2012.04.01
>
> https://github.com/Freescale/u-boot-imx/tree/patches-2013.04 , sorry.
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://projetos.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>

[-- Attachment #2: Type: text/html, Size: 4036 bytes --]

Re: Wandboard U-boot (2013.07-rc3) issues

[Marek Vasut]

Dear Diego Sueiro,

> The issue is still reproduced with v2013.04 patched version:
> 
> U-Boot 2013.04 (Aug 07 2013 - 11:32:45)
> 
> CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
> Reset cause: POR
> Board: Wandboard
> DRAM:  1 GiB
> MMC:   FSL_SDHC: 0
> *** Warning - bad CRC, using default environment
> 
> In:    serial
> Out:   serial
> Err:   serial
> Net:   FEC [PRIME]
> Warning: FEC using MAC address from net device
> 
> Hit any key to stop autoboot:  0
> mmc0 is current device
> Card did not respond to voltage select!
> Booting from net ...
> FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
> BOOTP broadcast 1
> BOOTP broadcast 2
> 

Maybe your board is defective ...

Best regards,
Marek Vasut

Re: Wandboard U-boot (2013.07-rc3) issues

[Diego Sueiro]

[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]

Marek,

This could be possible, but it not happens with 2GB uSD from Kingston.

--
* dS
Diego Sueiro
Sent from my droid phone.
Em 07/08/2013 14:29, "Marek Vasut" <marex@denx.de> escreveu:

> Dear Diego Sueiro,
>
> > The issue is still reproduced with v2013.04 patched version:
> >
> > U-Boot 2013.04 (Aug 07 2013 - 11:32:45)
> >
> > CPU:   Freescale i.MX6DL rev1.1 at 792 MHz
> > Reset cause: POR
> > Board: Wandboard
> > DRAM:  1 GiB
> > MMC:   FSL_SDHC: 0
> > *** Warning - bad CRC, using default environment
> >
> > In:    serial
> > Out:   serial
> > Err:   serial
> > Net:   FEC [PRIME]
> > Warning: FEC using MAC address from net device
> >
> > Hit any key to stop autoboot:  0
> > mmc0 is current device
> > Card did not respond to voltage select!
> > Booting from net ...
> > FEC Waiting for PHY auto negotiation to complete......... TIMEOUT !
> > BOOTP broadcast 1
> > BOOTP broadcast 2
> >
>
> Maybe your board is defective ...
>
> Best regards,
> Marek Vasut
>

[-- Attachment #2: Type: text/html, Size: 1438 bytes --]