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

Mehmet Ali İPİN mehmet.ipin at pavotek.com.tr
Mon Jan 15 13:24:49 UTC 2018


Dear Estevam,

Thank you very much for your answer.
I downloaded u-boot 2018.01. Its make file required gcc 6.0 or later. Then I downloaded gcc 7.2.
Building it.

Do you know is there a yocto version which is stable with u-boot 2018?

Thanks and best regards.



-----Original Message-----
From: Fabio Estevam [mailto:festevam at gmail.com] 
Sent: Friday, January 12, 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 Fri, Jan 12, 2018 at 4:00 AM, Mehmet Ali İPİN <mehmet.ipin at pavotek.com.tr> wrote:
>
>
> From: Mehmet Ali İPİN
> Sent: Friday, January 12, 2018 8:39 AM
> To: 'u-boot at lists.dex.de' <u-boot at lists.dex.de>
> Subject: u-boot v2016 vs v2013
>
> Dear Sir/Madam,
>
> Hello,
>
> We have an i.mx6dl board which was referenced to sabreauto kit, except 
> we use KSZ9021 as phy chip instead of AR8031. We installed the krogoth 
> and jethro versions of yocto; as result u-booth 2016 and 2013 versions 
> were installed accordingly. When downloaded the code
> 2013 u-boot version controlled the phy chip, even we did not touch the ethernet-phy related files.
>
> But for u-boot 2016, even we modified the config and source files according to KSZ9021, even MDO and MDCLK pins are not activated.
>
> I would be very grateful, if anybody knows a solution about this problem and/or give me a direction.

Please try 2018.01 instead.

Another suggestion is to do a similar changes in your board file like this:
http://git.denx.de/?p=u-boot.git;a=commitdiff;h=dac09fc10b71045ac261a9b8a05d34029ebec2ae;hp=0f7c6cdc8143d6cf0577a84bf27bdaadd6229ff4

Regards,

Fabio Estevam


More information about the U-Boot mailing list