public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tapio Koskinen <tapio.koskinen@tut.fi>
To: Jiri Gaisler <jiri@gaisler.com>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Re:  Leon3 compatible with LAN91C111?
Date: Thu, 29 Mar 2007 16:12:00 -0000	[thread overview]
Message-ID: <460BE1E3.2000107@tut.fi> (raw)
In-Reply-To: <45FD90E4.6040400@gaisler.com>

Hi Jiri,

Yes, I have been using ecos-rep-1.0.7.tar.gz. However I only found
support for Greth and Openeth, not Lan91C111 (in configtool
Build->Templates).

Tapio


Jiri Gaisler wrote:
> LEON3 support for LAN91C111 is available in the patched eCos version
> available from Gaisler Research:
> 
> ftp://gaisler.com/gaisler.com/ecos/src
> 
> This version of eCos also support SMP for LEON3. We have not succeeded
> in pushing our modifications into the main tree yet ...
> 
> Some basic info is also available here:
> 
> http://www.gaisler.com/cms4_5_3/index.php?option=com_content&task=view&id=149&Itemid=31
> 
> Jiri.
> 
> Tapio Koskinen wrote:
>> Hi all,
>>
>> I am using a Leon3 processor on Altera's Nios II Development Kit, Stratix Edition. The board has a LAN91C111 Ethernet controller and I am trying to get server_test.c working. There was no target for such a configuration, so I made a new target to ecos.db and added the following packages to it:
>> CYGPKG_HAL_SPARC
>> CYGPKG_HAL_SPARC_LEON3
>> CYGPKG_DEVS_ETH_SMSC_LAN91CXX
>> CYGPKG_DEVS_ETH_SPARC_LEON3
>>
>> When trying to run the program it said "No 91Cxx signature found". It seems there was an endianess problem, and after removing all calls to CYG_CPU_TO_LE16 and CYG_LE16_TO_CPU in devs/eth/smsc/lan91cxx/current/src/if_lan91cxx.c and smsc_lan91cxx.h it found the signature.
>>
>> However it prints "auto-negotiation failed" even though "link ok" led is lit in the controller after aneg-bit is written to RPCR-register. Also there is a yellow balloon tip in Windows saying 10Mbps link established.
>>
>> After lan91cxx_start completes these lines are printed:
>> lan91cxx_can_send
>> lan91cxx_can_send: ENGINE RESTART: tcr 0x0000
>> lan91cxx_poll
>> lan91cxx_TxEvent
>> lan91cxx_TxEvent:START: fifo 0000 ints 3100
>> lan91cxx_TxEvent: ENGINE RESTART: tcr 0x0000 eph 0x0000 ints 0x3100
>> lan91cxx_TxEvent:END: fifo 0000 ints 3302
>> lan91cxx_isr
>> lan91cxx_TxEvent
>> lan91cxx_TxEvent:START: fifo 0000 ints 3100
>> lan91cxx_TxEvent: ENGINE RESTART: tcr 0x0000 eph 0x0000 ints 0x3100
>> lan91cxx_TxEvent:END: fifo 0000 ints 3302
>> lan91cxx_TxEvent
>>
>>
>> So it keeps executing lan91cxx_TxEvent over and over. TXENA-bit can't stay up but there is no error in EPH_STATUS-register. And what is the server_test/eCos trying to send anyways? Server_test should just wait for a connection. I have set a static IP address so DHCP shouldn't be in use. I also tried unloading DNS-package but it didn't help. What should I try to do next?
>>
>> I have tried using versions 1.19 and 1.20 of 91C111's drivers, although in 1.20 calls to CYGACC_CALL_IF_DELAY_US(x) couldn't be linked even if I added "#include <cyg/hal/hal_if.h>" to if_lan91cxx.c. So I had to change those calls back to HAL_DELAY_US(x).
>>
>> Thanks in advance
>>
>> Tapio


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2007-03-29 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-18 19:19 Jiri Gaisler
2007-03-19 14:06 ` HASAN HÜSEYIN YILMAZ
2007-03-29 16:12 ` Tapio Koskinen [this message]
2007-03-29 16:23   ` Jiri Gaisler
2007-03-29 23:32     ` Tapio Koskinen
2007-03-30  6:27       ` Jiri Gaisler
2007-04-13 11:36         ` Tapio Koskinen

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=460BE1E3.2000107@tut.fi \
    --to=tapio.koskinen@tut.fi \
    --cc=ecos-discuss@sourceware.org \
    --cc=jiri@gaisler.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).