From just_abhi22@yahoo.co.in  Wed Oct  3 18:09:00 2012
From: just_abhi22@yahoo.co.in (abhishek srivastava)
Date: Wed, 03 Oct 2012 18:09:00 -0000
Subject: [ECOS] what amount of RAM is must in target board for eCos
Message-ID: <1349287737.59969.YahooMailNeo@web193201.mail.sg3.yahoo.com>



hi all
i am going to purchase my target processor for eCos as ARM Cortex M3, so a bit worried about its RAM and ROM size requirement when used with eCos.ya, i know,its more application dependent.
lets say, as per my application, i want to play eCos fullest (while learning eCos) and as main objective, i want to interface graphical LCD (colored) with board (eCos installed) and if possible some GUIs would also go along.
now for such kind of application, what size of RAM and ROM should be required as i have already tried to do this with LPC2148 with 32K RAM which let me down in past.....as much i? know, eCos requires 10K of RAM space as bare minimum.Is it so?


please suggest me some suitable board also which is well supported by eCos, possibly ARM.

Thank you



regards

Abhishek

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


From Richard.Morris@lifetech.com  Wed Oct  3 18:33:00 2012
From: Richard.Morris@lifetech.com (Morris, Richard)
Date: Wed, 03 Oct 2012 18:33:00 -0000
Subject: [ECOS] what amount of RAM is must in target board for eCos
In-Reply-To: <1349287737.59969.YahooMailNeo@web193201.mail.sg3.yahoo.com>
References: <1349287737.59969.YahooMailNeo@web193201.mail.sg3.yahoo.com>
Message-ID: <5B1F0BC3-A987-43F5-854E-B6319E329F3D@lifetech.com>

We use the ST Micro STM3240G EVAL board and find it quite capable.  It has 1M Flash and 192K RAM in two banks 128K + 64K.  The address spaces are not adjacent.

The STM32F4 processor family has very flexible timers, better than many other ARM uCs.


On Oct 3, 2012, at 11:08 AM, abhishek srivastava <just_abhi22@yahoo.co.in> wrote:

> 
> 
> hi all
> i am going to purchase my target processor for eCos as ARM Cortex M3, so a bit worried about its RAM and ROM size requirement when used with eCos.ya, i know,its more application dependent.
> lets say, as per my application, i want to play eCos fullest (while learning eCos) and as main objective, i want to interface graphical LCD (colored) with board (eCos installed) and if possible some GUIs would also go along.
> now for such kind of application, what size of RAM and ROM should be required as i have already tried to do this with LPC2148 with 32K RAM which let me down in past.....as much i  know, eCos requires 10K of RAM space as bare minimum.Is it so?
> 
> 
> please suggest me some suitable board also which is well supported by eCos, possibly ARM.
> 
> Thank you
> 
> 
> 
> regards
> 
> Abhishek
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 


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


From mario.pozner@gmail.com  Thu Oct  4 09:43:00 2012
From: mario.pozner@gmail.com (Mario Pozner)
Date: Thu, 04 Oct 2012 09:43:00 -0000
Subject: [ECOS] Translation of the web page done
Message-ID: <20cf3074b1ba58251104cb38965e@google.com>

Hello,

Was a pleasure to translate this publication  
(http://ecos.sourceware.org/fom/ecos)! It's related to my professional  
interests, so I thought - why not, if the author allows to do so.

If you don't mind can you publish a link with a text (please point me as  
Gmail Archive, it's important for me):

Ukraine translation by <a href="http://stoodio.org/">Gmail Archive</a> - <a  
href="http://www.stoodio.org/gmail-archive-ecos">http://www.stoodio.org/gmail-archive-ecos</a>.

Thanks!

---
Thanks,
Mario Pozner

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


From kenkyee@excite.com  Fri Oct  5 01:43:00 2012
From: kenkyee@excite.com (Ken Yee)
Date: Fri, 05 Oct 2012 01:43:00 -0000
Subject: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
Message-ID: <20121004214326.27851@web003.roc2.bluetie.com>

Ilija Kocho wrote:
> This may be example you are looking for:
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001623

Got decently far with this angle of changes.
We created a new startup type, and fiddled with most of the options for RAM/ROM in the .cdl file.  But from doing this, it's glaringly obvious that eCos does *NOT* support this setup; a ROM app run from Redboot, at least on the AT91, has to do a hybrid of the ROM and RAM startup types.  The Redboot documentation should clearly state that only apps built in the RAM startup type are supported IMHO.

Anyways, simple test apps seem to run, but one this we hit was that anything that does diag_printf gets stuck in the IF_IN_PUTC call...it just deep spaces (runs until it hits that) there in the debugger.  Single stepping into assembly doesn't even work if you put a breakpoint before that so we can't see where that goes (whether it's to a bad driver, etc.).  The simplest app like this:
void cyg_user_start(void)
{
    diag_printf("\r\nHello world!\r\n");
}
does the hang when compiled as an APPROM (that's what we called it instead of Flash as yours is called...maybe RBROMAPP for RedBootROMApp might be a better acronym?).

Did you hit this problem in your setup at all?  i.e., did you try diag_printf on your kinetis board?

 thanks,

 ken
-------------- next part --------------
An embedded message was scrubbed...
From: Ilija Kocho <ilijak@siva.com.mk>
Subject: Re: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
Date: Wed, 26 Sep 2012 22:49:24 +0200
Size: 3132
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20121005/ddeb66aa/attachment.eml>
-------------- next part --------------
-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

From ilijak@siva.com.mk  Fri Oct  5 10:21:00 2012
From: ilijak@siva.com.mk (Ilija Kocho)
Date: Fri, 05 Oct 2012 10:21:00 -0000
Subject: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
In-Reply-To: <20121004214326.27851@web003.roc2.bluetie.com>
References: <20121004214326.27851@web003.roc2.bluetie.com>
Message-ID: <506EB4AA.3040407@siva.com.mk>

On 05.10.2012 03:43, Ken Yee wrote:
> Ilija Kocho wrote:
>> This may be example you are looking for:
>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001623
> Got decently far with this angle of changes.
> We created a new startup type, and fiddled with most of the options for RAM/ROM in the .cdl file.  But from doing this, it's glaringly obvious that eCos does *NOT* support this setup; a ROM app run from Redboot, at least on the AT91, has to do a hybrid of the ROM and RAM startup types.  The Redboot documentation should clearly state that only apps built in the RAM startup type are supported IMHO.

True, you won't find for ROM startup in standard RedBoot. FLASH startup
is [my] experiment for testing the concept. It seems to work, but it's
still experimental. Your tests are valuable, thanks.

>
> Anyways, simple test apps seem to run, but one this we hit was that anything that does diag_printf gets stuck in the IF_IN_PUTC call...it just deep spaces (runs until it hits that) there in the debugger.  Single stepping into assembly doesn't even work if you put a breakpoint before that so we can't see where that goes (whether it's to a bad driver, etc.).  The simplest app like this:

It's true for break points. The target code being in Flash, rather than
RAM, needs hardware break points that are not supported by RedBoor/eCos
GDB stubs at present.

> void cyg_user_start(void)
> {
>     diag_printf("\r\nHello world!\r\n");
> }
> does the hang when compiled as an APPROM (that's what we called it instead of Flash as yours is called...maybe RBROMAPP for RedBootROMApp might be a better acronym?).
>
> Did you hit this problem in your setup at all?  i.e., did you try diag_printf on your kinetis board?

Yes I have.

Try the real (instead of diagnostic) serial driver.

Ilija


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


From kenkyee@excite.com  Fri Oct  5 18:19:00 2012
From: kenkyee@excite.com (Ken Yee)
Date: Fri, 05 Oct 2012 18:19:00 -0000
Subject: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
Message-ID: <20121005141943.18945@web007.roc2.bluetie.com>

> It's true for break points. The target code being in Flash, rather than
> RAM, needs hardware break points that are not supported by RedBoor/eCos
> GDB stubs at present.

I'm actually using a Segger JLink for debugging...not using Redboot's gdb support.
That's why I'm puzzled...I should be able to look at the code behind that macro or single step through the assembly code but I can't do anything w/ that IF_PUTC function.


> Try the real (instead of diagnostic) serial driver.

Is there a way to get "diag_printf" to use the real serial driver?  Interesting that you hit the same issue...I always thought the diag_driver just used the same serial port but with interrupts disabled.
I can't remove all the diag_printf calls in the networking stack in configtool...tried turning off all the debug stuff but on startup, the networking code seems to always print out those "Init: %s[%d]" lines.  I guess I could just change all the ecos code that does this and recompile...

 thanks,

ken
-------------- next part --------------
An embedded message was scrubbed...
From: Ilija Kocho <ilijak@siva.com.mk>
Subject: Re: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
Date: Fri, 05 Oct 2012 12:21:30 +0200
Size: 4014
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20121005/7cfe81f0/attachment.eml>
-------------- next part --------------
-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

From ilijak@siva.com.mk  Fri Oct  5 18:57:00 2012
From: ilijak@siva.com.mk (Ilija Kocho)
Date: Fri, 05 Oct 2012 18:57:00 -0000
Subject: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
In-Reply-To: <20121005141943.18945@web007.roc2.bluetie.com>
References: <20121005141943.18945@web007.roc2.bluetie.com>
Message-ID: <506F2D7F.5080102@siva.com.mk>

On 05.10.2012 20:19, Ken Yee wrote:
>> It's true for break points. The target code being in Flash, rather than
>> RAM, needs hardware break points that are not supported by RedBoor/eCos
>> GDB stubs at present.
> I'm actually using a Segger JLink for debugging...not using Redboot's gdb support.
> That's why I'm puzzled...I should be able to look at the code behind that macro or single step through the assembly code but I can't do anything w/ that IF_PUTC function.

Then I'm afraid I can't help you much. I would check whether the GDB
server is set for hardware break points.

>
>> Try the real (instead of diagnostic) serial driver.
> Is there a way to get "diag_printf" to use the real serial driver?  Interesting that you hit the same issue...I always thought the diag_driver just used the same serial port but with interrupts disabled.
Yes, enable the respective tty<n> driver and set it as a console
(default is ttydiag).

But, actually you may have hardware problem (does it print  barebone?).
If you power Kwikstik from it's own USB connector there is a voltage
drop on serial diode (I don't recal whether it was D6 or D7) that
hinders RS232.

Ilija


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


From kenkyee@excite.com  Mon Oct  8 22:40:00 2012
From: kenkyee@excite.com (Ken Yee)
Date: Mon, 08 Oct 2012 22:40:00 -0000
Subject: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
Message-ID: <20121008184025.14616@web006.roc2.bluetie.com>

Iliya wrote:
> Yes, enable the respective tty<n> driver and set it as a console
> (default is ttydiag).
> But, actually you may have hardware problem (does it print barebone?).

Yes, it prints barebone (i.e., run as RAM startup type w/ Redboot).  These are only issues w/ trying to get it to run as a Redboot Flash app (the new Redboot ROM app startup type instead of the existing eCos ROM startup type).

FYI, for the diag_printf issue of it going into space on the IF_COMM_PUTC, the problem was the app didn't have "claim comms virtual vectors" checked under the configtool under eCos HAL, the ROM monitor support.  We got a lot further after checking off "claim virtual vector table entries by default", "claim reset virtual vectors", "claim delay_us virtual vectors", "claim data virtual vectors", and "claim comms virtual vectors".  It's interesting that the app's ecos config had to be set to do that instead of letting it use the Redboot vectors automatically, so it seems like we missed a section define somewhere that tells the RAM startup type to use the redboot virtual vector table...

So next issue we've hit is JFFS doesn't read the Redboot FIS table properly so it can't figure out where the internal flash partition is that it's supposed to use...it's progress at least :-)
-------------- next part --------------
An embedded message was scrubbed...
From: Ilija Kocho <ilijak@siva.com.mk>
Subject: Re: [ECOS] not possible to have a ROM app that's started by system w/ Redboot?
Date: Fri, 05 Oct 2012 20:57:03 +0200
Size: 3370
URL: <http://sourceware.org/pipermail/ecos-discuss/attachments/20121008/48562ac8/attachment.eml>
-------------- next part --------------
-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

From a@awn.dk  Thu Oct 11 08:51:00 2012
From: a@awn.dk (Allan Nielsen)
Date: Thu, 11 Oct 2012 08:51:00 -0000
Subject: [ECOS] Select break?
Message-ID: <CANdC7UEPLnJkji3CocX+V5H8h1pv-+w1CB14fiTr6Ft0iCB-Jw@mail.gmail.com>

Hi,

Is there any way I can wakeup a select call from an other thread?

I'm using eCos threads (not posix threads), so sending a signal using
pthread_kill does not seem to be an option.

I would have guessed that I could create a file descriptor pair using
pipe, or socketpair, include this in the select list, and write some
dummy data. But since eCos does not implement either pipe or
socketpair, this does not seem to be an option either.

I have tried to use the cyg_selrecord and the cyg_selwakeup functions,
but they only cause the select function to poll the file descriptors
again.

So how can this be done using eCos threads?

Best regards
Allan W. Nielsen

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


From grant.b.edwards@gmail.com  Thu Oct 11 13:14:00 2012
From: grant.b.edwards@gmail.com (Grant Edwards)
Date: Thu, 11 Oct 2012 13:14:00 -0000
Subject: [ECOS] Re: Select break?
References: <CANdC7UEPLnJkji3CocX+V5H8h1pv-+w1CB14fiTr6Ft0iCB-Jw@mail.gmail.com>
Message-ID: <k56gnh$3um$1@ger.gmane.org>

On 2012-10-11, Allan Nielsen <a@awn.dk> wrote:

> Is there any way I can wakeup a select call from an other thread?

You used to be able to call cyg_select_abort(), which would wake up
any thread that was blocking in cyg_select_with_abort() -- which had
the same semantics as select() except it could be aborted.  It was a
great feature that I found exactly fit my needs.  But, that feature
disappeared.

Now the only practical solution I've found is to always use a timeout
when you call select() and just poll the abort condition.  No, it's
not very elegent, it wastes CPU, and in introduces a lot of latency.

-- 
Grant Edwards               grant.b.edwards        Yow! Give them RADAR-GUIDED
                                  at               SKEE-BALL LANES and
                              gmail.com            VELVEETA BURRITOS!!


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


From jay@systech.com  Thu Oct 11 15:24:00 2012
From: jay@systech.com (Jay Foster)
Date: Thu, 11 Oct 2012 15:24:00 -0000
Subject: [ECOS] Select break?
In-Reply-To: <CANdC7UEPLnJkji3CocX+V5H8h1pv-+w1CB14fiTr6Ft0iCB-Jw@mail.gmail.com>
References: <CANdC7UEPLnJkji3CocX+V5H8h1pv-+w1CB14fiTr6Ft0iCB-Jw@mail.gmail.com>
Message-ID: <5076E4A6.2070302@systech.com>

Just because eCos does not have a pipe or socketpair feature does not 
mean that you cannot use an additional pair of sockets.  Add another 
socket (UDP on the loopback interface) to listen on in your select() 
call.  Add another socket (UDP) to send messages to it using sendto().  
You can bind the listening socket to the loopback interface with any 
port number (0) and use the getsockname() function to retrieve the 
actual bound socket address.  This address can be used in the sendto() 
calls.

Jay

On 10/11/2012 1:51 AM, Allan Nielsen wrote:
> Hi,
>
> Is there any way I can wakeup a select call from an other thread?
>
> I'm using eCos threads (not posix threads), so sending a signal using
> pthread_kill does not seem to be an option.
>
> I would have guessed that I could create a file descriptor pair using
> pipe, or socketpair, include this in the select list, and write some
> dummy data. But since eCos does not implement either pipe or
> socketpair, this does not seem to be an option either.
>
> I have tried to use the cyg_selrecord and the cyg_selwakeup functions,
> but they only cause the select function to poll the file descriptors
> again.
>
> So how can this be done using eCos threads?
>
> Best regards
> Allan W. Nielsen
>

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


From pme.neratec@gmx.ch  Fri Oct 12 14:30:00 2012
From: pme.neratec@gmx.ch (Philipp Meier)
Date: Fri, 12 Oct 2012 14:30:00 -0000
Subject: [ECOS] cyg_drv_mutex_lock combine with while loop?
Message-ID: <50782975.1090904@gmx.ch>

I see in some driver code the following statements:
     while(!cyg_drv_mutex_lock(&any_lock));

And I wonder if this might be the source of a deadlock or even the 
source of a stack overflow.

Is it a good/secure idea to stay in a while loop when 
cyg_drv_mutex_lock() returns false? Or should this be handled as an 
exceptional state?

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


From kenkyee@excite.com  Mon Oct 15 21:37:00 2012
From: kenkyee@excite.com (Ken Yee)
Date: Mon, 15 Oct 2012 21:37:00 -0000
Subject: [ECOS] ping only works on local subnet w/ FreeBSD stack?
Message-ID: <20121015173750.24565@web006.roc2.bluetie.com>

Longshot, but has anyone ever seen this behavior?
ICMP pings only work to localhost or machines on the same subnet.  If you try to ping any other machines out on the network, you get these diag messages:
recvfrom: Operation timed out

Tried this over PPP over a serial port and you can see the reply packets arrive back at the wire, but it never makes it back to the ecos app.

Max sockets are cranked up to 32 in the configtool and file descriptors are up to 64, so I shouldn't be out of resources.

Haven't tried the LwIP stack yet because that's supposed to be a lot bugger from what I've dug up (our initial testing of it showed it used a lot of CPU resources)...

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


From J.Lambrecht@TELEVIC.com  Tue Oct 16 14:53:00 2012
From: J.Lambrecht@TELEVIC.com (=?iso-8859-1?Q?Lambrecht_J=FCrgen?=)
Date: Tue, 16 Oct 2012 14:53:00 -0000
Subject: [ECOS] how does ecos build its routing tables?
Message-ID: <507D74EB.90001@televic.com>

Hello,

We cannot set our routing tables correct!
We use the freeBSD network stack.

We configure it with a fixed IP adress (172.24.0.0/13) with netmask 
255.248.0.0.
But always in the routing table the netmaskk 255.255.0.0 is present??
How is this possible?

Here the result of a print of the routing tables (I use functions that 
you can find back on the ecos mailing list):
-----------------------------------------------------------------
Televic telnet shell. Welcome.

$> ifconfig

Routing tables
Destination     Gateway         Mask            Flags    Interface
127.0.0.0       127.0.0.1       255.0.0.0       UG       lo0
127.0.0.1       127.0.0.1                       UH       lo0
172.24.0.0      172.24.0.0      255.255.0.0     U        eth0
Interface statistics
eth0    IP: 172.24.0.11, Broadcast: 172.31.255.255, Netmask: 255.248.0.0
         UP BROADCAST RUNNING MULTICAST MTU: 1500, Metric: 0
         Rx - Packets: 44, Bytes: 3660, Tx - Packets: 23, Bytes: 2090
lo0     IP: 127.0.0.1, Broadcast: 127.0.0.1, Netmask: 255.0.0.0
         UP LOOPBACK RUNNING MULTICAST MTU: 16384, Metric: 0
         Rx - Packets: 0, Bytes: 0, Tx - Packets: 0, Bytes: 0
-----------------------------------------------------------------
Our RedBoot uses the 255.255.0.0 netmask, could that explain it?

And when we add the correct route and then delete the wrong route, our 
network connection goes away - a ping fails..

Any help is appreciated!

Kind regards,
J?rgen

-
J?rgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk

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


From J.Lambrecht@TELEVIC.com  Wed Oct 17 16:10:00 2012
From: J.Lambrecht@TELEVIC.com (=?iso-8859-1?Q?Lambrecht_J=FCrgen?=)
Date: Wed, 17 Oct 2012 16:10:00 -0000
Subject: [ECOS] how does ecos build its routing tables?
In-Reply-To: <507D74EB.90001@televic.com>
References: <507D74EB.90001@televic.com>
Message-ID: <507ED856.5070406@televic.com>

On 10/16/2012 04:53 PM, Lambrecht J?rgen wrote:
> Hello,
>
> We cannot set our routing tables correct!
> We use the freeBSD network stack.
>
> We configure it with a fixed IP adress (172.24.0.0/13) with netmask
> 255.248.0.0.
> But always in the routing table the netmaskk 255.255.0.0 is present??
> How is this possible?
We also have a network with netmask 248.0.0.0, and then in the routing 
table the netmask 255.0.0.0 is present.
So I think the freeBSD network stack only can set the netmask in the 
routing table per byte.
Can somebody confirm this?
Any solution?

Regards,
J?rgen
> Here the result of a print of the routing tables (I use functions that
> you can find back on the ecos mailing list):
> -----------------------------------------------------------------
> Televic telnet shell. Welcome.
>
> $>  ifconfig
>
> Routing tables
> Destination     Gateway         Mask            Flags    Interface
> 127.0.0.0       127.0.0.1       255.0.0.0       UG       lo0
> 127.0.0.1       127.0.0.1                       UH       lo0
> 172.24.0.0      172.24.0.0      255.255.0.0     U        eth0
> Interface statistics
> eth0    IP: 172.24.0.11, Broadcast: 172.31.255.255, Netmask: 255.248.0.0
>           UP BROADCAST RUNNING MULTICAST MTU: 1500, Metric: 0
>           Rx - Packets: 44, Bytes: 3660, Tx - Packets: 23, Bytes: 2090
> lo0     IP: 127.0.0.1, Broadcast: 127.0.0.1, Netmask: 255.0.0.0
>           UP LOOPBACK RUNNING MULTICAST MTU: 16384, Metric: 0
>           Rx - Packets: 0, Bytes: 0, Tx - Packets: 0, Bytes: 0
> -----------------------------------------------------------------
> Our RedBoot uses the 255.255.0.0 netmask, could that explain it?
>
> And when we add the correct route and then delete the wrong route, our
> network connection goes away - a ping fails..
>
> Any help is appreciated!
>
> Kind regards,
> J?rgen
>
> -
> J?rgen Lambrecht
> R&D Associate
> Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
> http://www.televic-rail.com
> Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
> Company number 0825.539.581 - RPR Kortrijk
>


-- 
J?rgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk

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


From listmaster@carel.org  Thu Oct 18 08:19:00 2012
From: listmaster@carel.org (Le Carel)
Date: Thu, 18 Oct 2012 08:19:00 -0000
Subject: [ECOS] French course + internship
Message-ID: <689b0556d7decc4d1f464f93d4cbd2f3@www.carel.org>

*If you cannot view* this *email properly*, *please click here*
<http://www.carel.org/lists/lt.php?id=ZEgECVAEDlRVHwtQUEQMAARXAw%3D%3D>
 for online version

 Combine your Intensive French course at CAREL with a professional
internship
<http://www.carel.org/lists/lt.php?id=ZEgECVAEDlRVHwtQUEQMAARXAw%3D%3D>
!

 Enhance your CV
<http://www.carel.org/lists/lt.php?id=ZEgECVAEDlRVHwtQUEQMAARXAw%3D%3D>
 with our 
combo
 

 offer! 

 <http://www.carel.org/lists/lt.php?id=ZEgECVAEDlRSHwtQUEQMAARXAw%3D%3D>



--
Conform?ment aux articles 27 et 34 de la loi n? 78-17 du 6 janvier 1978
relative ? l'informatique, aux fichiers et aux libert?s, nous tenons ? vous
pr?ciser que les informations demand?es seront uniquement trait?es par les
services internes du CAREL. Vous pouvez ? tout moment acc?der aux
informations personnelles vous concernant, demander leur modification ou
leur suppression?aupr?s?du Service?Commercial - 48 Boulevard Franck Lamy -
Place Jean-No?l de Lipkowski - BP 219C - 17205 Royan cedex.

Pour vous d?sabonner de cette liste, cliquez sur
http://www.carel.org/lists/lt.php?id=ZEgECVAEDlRTHwtQUEQMAARXAw%3D%3D

Pour faire suivre ce message, cliquez sur
http://www.carel.org/lists/lt.php?id=ZEgECVAEDlRQHwtQUEQMAARXAw%3D%3D


--
powered by phpList, www.phplist.com --



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


From a@awn.dk  Tue Oct 23 16:27:00 2012
From: a@awn.dk (Allan Nielsen)
Date: Tue, 23 Oct 2012 16:27:00 -0000
Subject: [ECOS] SO_BINDTODEVICE for eCos?
Message-ID: <CANdC7UFuh0V5C-B_QjpUepRDbphhCb6hczJXBt=ktwkKr83N1g@mail.gmail.com>

Hi,

When transmitting an packet on a socket, how can I then explicit
define which interface to transmit the packet on?

This is in linux done by using the SO_BINDTODEVICE option, but this
options does not seem to be available in eCos (i'm using the bsd IP
stack).

I would expect that the DHCP server need to do this, but I can not
figure out how it is done.

Best regards
Allan W. Nielsen

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


From jifl@eCosCentric.com  Sun Oct 28 21:00:00 2012
From: jifl@eCosCentric.com (Jonathan Larmour)
Date: Sun, 28 Oct 2012 21:00:00 -0000
Subject: [ECOS] sources.redhat.com no longer valid for eCos
Message-ID: <508D9D01.1070005@eCosCentric.com>

For a long time now, we've been telling people to use ecos.sourceware.org for
everything to do with the eCos project, whether for the mailing lists,
website, CVS, and so on.  Years ago, it used to be sources.redhat.com.

But a recent change means that the sources.redhat.com name no longer points to
ecos.sourceware.org (or sourceware.org).

Anyone who has been using old address book entries for sending mail to the
eCos mailing lists will find it won't work, and obviously you should update
your address book to use ecos.sourceware.org instead. Also anyone who has had
a CVS source tree checked out from when it was sources.redhat.com will find
they can no longer update it.

For anyone with an existing CVS tree, open a bash prompt (using cygwin if on
Windows), change directory to the base of the checked out tree and type:

  cat CVS/Root

and if the output is:

:pserver:anoncvs@sources.redhat.com:/cvs/ecos

then you will need to fix your CVS source tree with the following command from
the same directory:

find . -path \*/CVS/Root -exec sh -c "echo
:pserver:anoncvs@ecos.sourceware.org:/cvs/ecos > {}" \;

(that must be all on one line).

Contact ecos-discuss@ecos.sourceware.org if you have any problems.

Jifl

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


From pme.neratec@gmx.ch  Wed Oct 31 11:44:00 2012
From: pme.neratec@gmx.ch (Philipp Meier)
Date: Wed, 31 Oct 2012 11:44:00 -0000
Subject: [ECOS] STM32 LSI calibration
Message-ID: <50910F1C.2030604@gmx.ch>

Has anybody done LSI calibration for eCos (as described in STM32 
reference manual revision 14 in chapter 7.2.5 "LSI clock") using TIM5 
channel4 and TIM5 Capture/compare?

I guess Cyg_WallClock::init_hw_seconds (in file stm32_wallclock.cxx) 
would be the function where to implement it (if it needs to be done once 
at system startup).

Thank's for any help.

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


From kenkyee@excite.com  Wed Oct 31 20:27:00 2012
From: kenkyee@excite.com (Ken Yee)
Date: Wed, 31 Oct 2012 20:27:00 -0000
Subject: [ECOS] Getting number of open file descriptors or sockets per thread?
Message-ID: <20121031162738.12590@web002.roc2.bluetie.com>

Is this possible in eCOS?

I'm basically trying to do this for checking leaks since an RTOS is more sensitive to this.
I'd ideally like to do something like this:
  http://www.cyberciti.biz/tips/linux-procfs-file-descriptors.html
then run some code in a loop while checking the descriptor used count to make sure it doesn't grow like crazy.

Ideally, I'd also like to do this with the sockets, mbufs, etc. as well.

I've used cyg_thread_measure_stack_usage to check stack usage per thread successfully.
And I've used mallinfo to check for memory leaks.

Hoping something like this exists for file descriptors and sockets, but if not, it'd be a very useful API to add :-)

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