[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Problem in using PPP & Ethernet Interface, together, with TCP/IP



Hi,

It seems that it is must to add a loopback interface along with the Ethernet interface. After adding the loopback interface the code works fine without any problem.

Thanks & Regards,

Viral Shah

-----Original Message-----
From: rtems-users-bounces at rtems.org [mailto:rtems-users-bounces at rtems.org] On Behalf Of rtems-users-request at rtems.org
Sent: Monday, March 07, 2011 2:50 PM
To: rtems-users at rtems.org
Subject: rtems-users Digest, Vol 54, Issue 8

Send rtems-users mailing list submissions to
        rtems-users at rtems.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://www.rtems.org/mailman/listinfo/rtems-users
or, via email, send a message with subject or body 'help' to
        rtems-users-request at rtems.org

You can reach the person managing the list at
        rtems-users-owner at rtems.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of rtems-users digest..."


Today's Topics:

   1. NFS timeouts without optimization (Peter Dufault)
   2. Re: Problem in using PPP & Ethernet Interface, together, with
      TCP/IP (Sebastian Huber)
   3. Re: Embedded Scripting (Chris Johns)
   4. rtems application tutorial (Domenico Di Leo)
   5. gdb+qemu+rtems: Problem #2 in offset computation (Domenico Di Leo)
   6. Problem building RTEMS4.10 (Shah, Viral)


----------------------------------------------------------------------

Message: 1
Date: Sun, 6 Mar 2011 15:21:18 -0500
From: Peter Dufault <dufault at hda.com>
To: "rtems-users at rtems.org List" <rtems-users at rtems.org>
Subject: NFS timeouts without optimization
Message-ID: <958CDC1B-A629-4262-9EBD-C616B61A1F60 at hda.com>
Content-Type: text/plain; charset=us-ascii

I'm putting together an embedded web server on an MPC55xxevb (MPC5554 Phytec) system.  After I got the basics working I put the HTTP on NFS for ease of development.  I started getting NFS timeouts whenever a browser tried to load the RTEMS .jpg file:

[/] # mongoose document_root /data/http listening_ports 80 stacksize 0xc000
Loading filesystem image...
Mongoose 3.0 started on port(s) [80], serving directory [/data/http]
[/] # NFS (proc 6) - RPC: Timed out
[/] # ls -l data/http/rtems_logo.jpg
-rw-rw-r--  1 500  500  14586 Mar  6  2011 data/http/rtems_logo.jpg
[/] #

On a hunch I rebuilt with -O2 back on (I'd turned it off a while ago for debugging) and now it works fine.

This isn't a bug report, obviously, it's a "has anyone else seen this?" question.  The ethernet driver is one I brought up, the smc91111, which I think had previously only been used on Sparc.  I'm going to ignore the issue today unless it comes back with the optimization on.

Peter
-----------------
Peter Dufault
HD Associates, Inc.      Software and System Engineering




------------------------------

Message: 2
Date: Mon, 07 Mar 2011 08:24:01 +0100
From: Sebastian Huber <sebastian.huber at embedded-brains.de>
To: rtems-users at rtems.org
Subject: Re: Problem in using PPP & Ethernet Interface, together, with
        TCP/IP
Message-ID: <4D748811.6050107 at embedded-brains.de>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

can you please add the loop back interface and try our test again?  In RTEMS
4.9.4 you can add the loop back interface like this:

int rtems_bsdnet_loopattach(struct rtems_bsdnet_ifconfig *, int);

static struct rtems_bsdnet_ifconfig loopback_config = {
    "lo0",                          /* name */
    rtems_bsdnet_loopattach,        /* attach function */
    NULL,                           /* link to next interface */
    "127.0.0.1",                    /* IP address */
    "255.0.0.0",                    /* IP net mask */
};

Have a nice day!

--
Sebastian Huber, embedded brains GmbH

Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone   : +49 89 18 90 80 79-6
Fax     : +49 89 18 90 80 79-9
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine gesch?ftliche Mitteilung im Sinne des EHUG.


------------------------------

Message: 3
Date: Mon, 07 Mar 2011 18:30:49 +1100
From: Chris Johns <chrisj at rtems.org>
To: Sebastien Bourdeauducq <sebastien at milkymist.org>
Cc: "rtems-users at rtems.org" <rtems-users at rtems.org>
Subject: Re: Embedded Scripting
Message-ID: <4D7489A9.8000105 at rtems.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 5/03/11 3:31 AM, Sebastien Bourdeauducq wrote:
>
> Python is a bit messy as it requires dynamic loading of code.

Typically this is what Python does. On the RTEMS port a user creates a
single C file that references the required modules and they get linked
in. No code loading was needed.

You cannot use Python's build system. It is broken from cross-compiling.
Once built I found Python embedded well. Its libraries allowed me to
create powerful applications.

> At the
> Milkymist project we successfully ran small Lua and Ruby interpreters
> without much trouble.

Nice. The more choice the better for RTEMS users.

Chris


------------------------------

Message: 4
Date: Mon, 07 Mar 2011 09:03:09 +0100
From: Domenico Di Leo <domenico.dileo at unina.it>
To: rtems-users at rtems.com
Subject: rtems application tutorial
Message-ID: <4D74913D.5070500 at unina.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi,
can you point me out any tutorial on how to write and execute an
application from the scratch for RTEMS.
I already checked the  Application C user guide, it is a good reference,
but it doesn't
help me to understand how to compile the application (what compiler
should I use?  is there any specific rule for the Makefile?)
Any suggestion is welcome.
Domenico

--
Domenico Di Leo, PhD student, Universit? degli Studi di Napoli Federico II
Ph:     +39 081 676770
Fax:    +39 081 676574
Web:http://wpage.unina.it/domenico.dileo  (WP)



------------------------------

Message: 5
Date: Mon, 07 Mar 2011 09:08:14 +0100
From: Domenico Di Leo <domenico.dileo at unina.it>
To: rtems-users at rtems.com
Subject: gdb+qemu+rtems: Problem #2 in offset computation
Message-ID: <4D74926E.4040405 at unina.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi
I have experienced the same problem.
My solution was really simple, since I started RTMES with qemu (on a
Fedora virtual machine)
with the command qemu -m 128  -boot a ...
I removed the "m" flag -> qemu -boot a ...  and it worked :)
Hope this helps other users.
D.

--
Domenico Di Leo, PhD student, Universit? degli Studi di Napoli Federico II
Ph:     +39 081 676770
Fax:    +39 081 676574
Web: http://wpage.unina.it/domenico.dileo (WP)



------------------------------

Message: 6
Date: Mon, 7 Mar 2011 14:50:10 +0530
From: "Shah, Viral" <viral.ashah at patni.com>
To: "rtems-users at rtems.org" <rtems-users at rtems.org>
Subject: Problem building RTEMS4.10
Message-ID:
        <8313536A4C022142955C41A106615B2873467D8210 at EXCHSPZMAIL.patni.com>
Content-Type: text/plain; charset="us-ascii"

Hi All,

I am trying to build RTEMS 4.10 for m68k target. Below are the details of the tool chain

1)       gcc-4.4.5.tar.bz2
2)       binutils-2.20.1.tar.bz2 with patch binutils-2.20.1-rtems4.10-20100826.diff
3)       newlib-1.18.0.tar.gz with patch newlib-1.18.0-rtems4.10-20110114.diff

I have configured the rtems with following options which works correctly.

../rtems-4.10.0/configure --target=m68k-rtems4.10 --disable-posix --disable-itron --enable-rtemsbsp=m5484FireEngine --prefix=/opt/rtems-4.10


When I do make all, I get error `Configuration_POSIX_API' undeclared (first use in this fun
ction). Has anyone faced similar problem? Can someone tell me what causes to give this error?

Please see the logs below..

../.././m5484FireEngine/lib/include   -mcfv4e -Wa,-memac -O2 -g -fomit-frame-poi
nter  -Wall -Wimplicit-function-declaration -Wstrict-prototypes -Wnested-externs
 -MT bspstart.o -MD -MP -MF .deps/bspstart.Tpo -c -o bspstart.o `test -f 'startu
p/bspstart.c' || echo '../../../../../../../../rtems-4.10.0/c/src/lib/libbsp/m68
k/genmcf548x/'`startup/bspstart.c
../../../../../../../../rtems-4.10.0/c/src/lib/libbsp/m68k/genmcf548x/startup/bs
pstart.c: In function `bsp_start':
../../../../../../../../rtems-4.10.0/c/src/lib/libbsp/m68k/genmcf548x/startup/bs
pstart.c:277: error: `Configuration_POSIX_API' undeclared (first use in this fun
ction)
../../../../../../../../rtems-4.10.0/c/src/lib/libbsp/m68k/genmcf548x/startup/bs
pstart.c:277: error: (Each undeclared identifier is reported only once
../../../../../../../../rtems-4.10.0/c/src/lib/libbsp/m68k/genmcf548x/startup/bs
pstart.c:277: error: for each function it appears in.)
make[6]: *** [bspstart.o] Error 1
make[6]: Leaving directory `/cygdrive/e/RTEMS_10/tools/build-rtems/m68k-rtems4.1
0/c/m5484FireEngine/lib/libbsp/m68k/genmcf548x'
make[5]: *** [all-recursive] Error 1
$
0/c/m5484FireEngine/lib/libbsp/m68k'
$
make[4]: Leaving directory `/cygdrive/e/RTEMS_10/tools/build-rtems/m68k-rtems4.1
0/c/m5484FireEngine/lib/libbsp'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/cygdrive/e/RTEMS_10/tools/build-rtems/m68k-rtems4.1
0/c/m5484FireEngine/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/cygdrive/e/RTEMS_10/tools/build-rtems/m68k-rtems4.1
0/c/m5484FireEngine'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/cygdrive/e/RTEMS_10/tools/build-rtems/m68k-rtems4.1
0/c'
make: *** [all-recursive] Error 1





Thanks & Regards,

Viral Shah
Specialist(Software) - Product Engineering Services,
Patni Computer Systems Ltd,
IT1/IT2 Patni Knowledge Park (PKP),
Block C, 2nd Floor, Wing A (C2A),
Thane Belapur Road, Airoli,
Navi Mumbai 400 708.
Tel: +91 22 3917 2000 Ext 4203
Tel (Direct): +91 22 3917 4203
Patni Link Line: 9-625-4403


________________________________
Information contained and transmitted by this e-mail is confidential and proprietary to Patni Computer Systems Ltd and its affiliates (hitherto referred as Patni Computers) and is intended for use only by the recipient. If you are not the intended recipient , you are hereby notified that any dissemination, distribution, copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or netadmin at patni.com. Patni Computers does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of Patni Computers. Patni Computers is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While Patni Computers has taken every reasonable precaution to minimise this risk, we!
  cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about Patni Computers please visit www.patni.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rtems.org/pipermail/rtems-users/attachments/20110307/0bec86de/attachment.html>

------------------------------

_______________________________________________
rtems-users mailing list
rtems-users at rtems.org
http://www.rtems.org/mailman/listinfo/rtems-users


End of rtems-users Digest, Vol 54, Issue 8
******************************************

Information contained and transmitted by this e-mail is confidential and proprietary to Patni Computer Systems Ltd and its affiliates (hitherto referred as Patni Computers) and is intended for use only by the recipient. If you are not the intended recipient , you are hereby notified that any dissemination, distribution,  copying or use of this e-mail is strictly prohibited and you are requested to delete this e-mail immediately and notify the originator or netadmin at patni.com. Patni Computers does not enter into any agreement with any party by e-mail. Any views expressed by an individual do not necessarily reflect the view of Patni Computers. Patni Computers is not responsible for the consequences of any actions taken on the basis of information provided, through this email. The contents of an attachment to this e-mail may contain software viruses, which could damage your own computer system. While Patni Computers has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening an attachment. To know more about Patni Computers please visit www.patni.com.