All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander Vermin <sander@vermin.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Uboot (AT91 tree) macb in MII mode
Date: Mon, 14 Apr 2008 11:52:13 +0200	[thread overview]
Message-ID: <4803294D.6010205@vermin.nl> (raw)
In-Reply-To: <1208166096.6399.51.camel@galileo>

Stelian Pop schreef:
> Le lundi 14 avril 2008 ? 11:19 +0200, Sander Vermin a ?crit :
>
>   
>>> Do you have a working Linux kernel with a working network interface ? 
>>> The Linux and U-Boot macb driver and PIO configuration is very close,
>>> and if you manage to make it work under Linux you'll probably have
>>> little trouble finding out the problem.
>>>   
>>>       
>> Are all settings of uboot overwritten by linux?
>>     
>
> Almost all the settings are overwritten, yes.
>
>   
Oke, olimex has a demo linux with working ethernet.. I can try to put 
this on my board with my current uboot.
>>  I am not to comfortable 
>> hacking in the Linux kernel and I had the focus on Uboot.
>>     
>
> So you do not have a working Linux kernel. This was my question.
>
>   
>>>> Olimex was kind enough to make Uboot nandflash build working with there 
>>>> board, And deliver sources I cant compile, due to an error: Hardware 
>>>> float vs software float. But I want a dataflash version because I am 
>>>> using a BGA chip with nandflash bug.
>>>>     
>>>>         
>>> I don't see what NAND has to do with ethernet here.
>>>   
>>>       
>> The AT91SAM9260 BGA chip has a bug, that booting from NAND has problems.
>>     
>
> Ok, but this has nothing to do with the Ethernet, right ? If the
> ethernet is supposed to work with their U-Boot version, it will probably
> work as well if you configure U-Boot to boot from dataflash instead of
> NAND flash.
>
>   
>>> Also, what cross chain are you using ? I have seen strange network
>>> errors when using recent compilers which after investigation were -Os
>>> optimisation errors. (using the latest CodeSourcery toolchain for
>>> example).
>>>   
>>>       
>> I am using the compilers from buildroot.
>>     
>
> This doesn't learn us anything about the gcc version you're using.
>
> The official toolchain for U-Boot is the DENX ELDK:
> http://www.denx.de/wiki/DULG/ELDK . I don't really think this is your
> issue, but when nothing works it may make sense to put yourself in a
> well known configuration.
>
>   
Is there some pre compiled  arm version?
>> Olimex has indeed, but that is a old version of uboot, the old ETHER 
>> driver and not the new. I inspected the initialization code on the ARM 
>> side, that was the same. The rest of te code is completely different, so 
>> spotting differences is difficult.
>>     
>
> Ah, I understand. However, there must be a difference somewhere. I'm not
> sure about this board, but on the SAM boards a software reset has to be
> performed once the PHY address is configured to activate the PHY (look
> into at91sam9260.c). Maybe your board needs something equivalent ?
>
>   
Currently I am using the at91sam9260ek config with the options above edited.

Sander

  reply	other threads:[~2008-04-14  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14  8:10 [U-Boot-Users] Uboot (AT91 tree) macb in MII mode Sander Vermin
2008-04-14  9:08 ` Stelian Pop
2008-04-14  9:19   ` Sander Vermin
2008-04-14  9:41     ` Stelian Pop
2008-04-14  9:52       ` Sander Vermin [this message]
2008-04-14 11:28         ` Stelian Pop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4803294D.6010205@vermin.nl \
    --to=sander@vermin.nl \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.