[U-Boot] FW: u-boot v2016 vs v2013

[Mehmet Ali İPİN]

Dear Estevam,

I am (in fact hardware engineer developed the PCB)  not an experienced u-boot/linux developer, therefore sorry for my complex questions.
I will check the forum, and google for this message, but you may help me to start the right path.

May be, according to your experience you can advise me to check some (phy/mac) register, pin status, clock values, 
Or give the name of threads in u-boot or nxp imx6 forum which is about similar dhcp events, if you remember.

Since its a new PCB board, so we did not load/run the linux yet.

Thanks and best regards.

Mehmet Ali



-----Original Message-----
From: Fabio Estevam [mailto:festevam at gmail.com] 
Sent: Wednesday, January 24, 2018 2:59 PM
To: Mehmet Ali İPİN <mehmet.ipin at pavotek.com.tr>
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] FW: u-boot v2016 vs v2013

On Wed, Jan 24, 2018 at 9:57 AM, Mehmet Ali İPİN <mehmet.ipin at pavotek.com.tr> wrote:
> Dear Estevam,
>
> Thank you very much; With your helps managed to use u-boot 2018, gcc 
> 7.2 and SPL, generated u-boot.img image and downloaded into board.
>
> SD card and e-MMC working well. Ethernet Phy is also answering mii info as shown below:
>
> => mii info
> PHY 0x05: OUI = 0x0885, Model = 0x21, Rev = 0x01,  10baseT, HDX => 
> setenv ipadr 10.0.0.10 => dhcp FEC Waiting for PHY auto negotiation to 
> complete......... TIMEOUT !
> Could not initialize PHY FEC
> BOOTP broadcast 1
> BOOTP broadcast 2
> .
> .
> .
> BOOTP broadcast 17
>
> Retry time exceeded; starting again.
>
> I would be grateful, if you Have any idea how can I test and solve the dhcp command?

It's hard to understand what could be wrong without seeing your code nor schematics.

Are you able to get Ethernet working in Linux?