headers
io in | 1 Jun 2003 09:31
Picon
Favicon

Building SID

Hello,

I am new to the world of eCos and embedded systems. I
would be very 
grateful if any one can answer the following queries -

Q1. I am sure most of the experts in this group have
come across 
building problems with SID. I am trying to build SID
for CYGWIN environment. 
But it fails with a error message saying "unable to
find tcl header" 
while "configuring testsuites". I have correctly
followed the steps for 
building SID given in the "FAQ-o-matic", but still the
problem persists. 
Kindly clarify the my mistake.

Q2. I want to run ecos applications on the CYGWIN
environment as the 
synthetic target. How do I go about buiding the
library and the tests 
using the windows based configtool ? Which gcc
compiler should I uses? I 
see the Linux-synthetic target under the templates.
But I was unable to 
build using it. Kindly point out my mistake.

Thank you very much.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Tim michals | 1 Jun 2003 11:13
Picon
Favicon

Re: mips IDT334 help

Several ways:
-During the boot process redboot displays if it found
the Network card.  If you neeed to generate more
diagnostics you can select an option under PCI using
the configuration tool.  This displays all of the
information during PCI scanning.
- If you wish to download programs and the Ethernet
card is not found, use the serial download option in
redboot for example: load -m xmodem <name of
program>.elf
Consult the redboot manual for more commands:
http://sources.redhat.com/ecos/docs-2.0/ref/redboot.html

--- "Avinash S." <avinash.s <at> inspiretech.com> wrote:
> hi,
> my sdram size is 16 mB with 8MB on each bank, i made
> a mistake while 
> typing that out in the last mail(sorry!). anyway i
> managed to get redboot 
> work. The problem it seems was in the srec file.
> Apparently the mipsisa-
> elf-objcopy convert to srec doesnt seem to run on
> the board from bootrom, 
> i however used sde-conv (algorithmics convert) and
> it worked fine...dont 
> know where exactly the problem could be tho!
> 
> Now that i have a redboot running how do i check if
> it has detected my 
> ethernet card(82599) and how do i get it to run the
(Continue reading)

Permalink | Reply | 0 comments |
headers
F.T.Nilsson | 1 Jun 2003 13:37
Picon
Picon
Favicon

confusion regarding ROM build for e7t

Hi All,

I posted a question a week ago about building a target application that 
would run at start up (ROM). I however got a bit confused. 1 answerer told 
me to look at the how RedBoot is generated and use this to generate the 
check sum needed for angel. Is this still needed if I will load the 
application with RedBoot? If I have RedBoot installed all I should have to 
do is change the memory layout? (MLT) if I am right about this could anyone 
point me to any documentation about changing the mlt?

If I cannot get the ROM start up to work is there any way that I could use 
the RAM start-up to demonstrate the application, without using gdb?

Any help appreciated.

Fred

         ---------------------------------------------------
            --------------- F R E D D A N---------------
                ------------------------------------
                      ------------------------
________________________________________________________________

DISCLAIMER:

This e-mail and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom it is addressed.  If you are not the intended recipient
you are prohibited from using any of the information contained
in this e-mail.  In such a case, please destroy all copies in
(Continue reading)

Permalink | Reply | 1 comment |
headers
Gary D. Thomas | 1 Jun 2003 13:43
Picon
Favicon

Re: confusion regarding ROM build for e7t

On Sun, 2003-06-01 at 05:37, F.T.Nilsson <at> hw.ac.uk wrote:
> Hi All,
> 
> I posted a question a week ago about building a target application that 
> would run at start up (ROM). I however got a bit confused. 1 answerer told 
> me to look at the how RedBoot is generated and use this to generate the 
> check sum needed for angel. Is this still needed if I will load the 
> application with RedBoot? If I have RedBoot installed all I should have to 
> do is change the memory layout? (MLT) if I am right about this could anyone 
> point me to any documentation about changing the mlt?
> 
> If I cannot get the ROM start up to work is there any way that I could use 
> the RAM start-up to demonstrate the application, without using gdb?

Of course & it'll be much simpler.

Just create a RAM startup application (this is the default).
Then use RedBoot to download the application into memory and type 'go'.

For example, if you have a network setup, you can:
  RedBoot> load -m tftp application
  RedBoot> go

-- 
Gary D. Thomas <gary.thomas <at> mind.be>

--

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael A. Purwoadi | 2 Jun 2003 05:25
Picon

Any port to SH-1 (7032) on LCEVB-SH1 platform ?

Hi ,

I`ve seen in
http://sources.redhat.com/cgi-bin/cvsweb.cgi/ecos/packages/hal/sh/?cvsroot=ecos
that eCos had not been ported to the microcontroller yet.  However, I
wonder if someone is trying to do that and it is not included yet in cvs
server. 

The platform includes a ROM emulation that I can connect from
configtool.The emulator can perform ¨High-level C debugging capability
with SYSROF User Target Program¨. How can I build eCos in Sysrof format
using gcc ?

If (in the worst case) I must compile eCos in MS Windows environment
(they give me the cross-compiler and development environment for
Windows), which files I have to pick up in order to build really the
strict-necessary of RTOS (Context-switching, Scheduler, Interruption 
handling, WatchDog).

Regards,
Michael A. Purwoadi 

--

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Permalink | Reply | 0 comments |
headers
Rick Davis | 2 Jun 2003 05:40
Picon

RAW Ethernet I/O

I am working on a project that will be receiving IP packets via an RS-422
serial link. The packets will then be transmitted over Ethernet. I would
like to use the Raw Packet interface but it doesn't look like eCos fully
supports the raw packet interface line Linux does. I need to be able to keep
the received source MAC address when transmitting the data over Ethernet as
well as change the source MAC address to some predefined value or the value
of the receiver. I also don't need the IP stack because the entire packet is
good to go as is and needs no massaging by the IP stack. I have done this on
Linux but I am a newbie to eCos and was wondering how I can attach to the
Ethernet driver directly or is there another way. Eventually the project
will go bi-directional and will also need to be able to receive RAW Ethernet
for transmission over RS-422 serial.

	Thanks in advance.
	Rick Davis

--

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
Permalink | Reply | 3 comments |
headers
Gregg C Levine | 2 Jun 2003 06:22
Picon

Re: RAW Ethernet I/O

Hello from Gregg C Levine
Can you be some what more specific? This is a subject that interests me, as
regards to Linux, and its interfaces, and to eCos, and to its.

What platform is your setup going to be running on, for example. That would
be a big help. Otherwise, you've got a good foundation there, for everyone
else to ask questions.
Gregg C Levine drwho8 <at> worldnet.att.net
"Oh my!" The Second Doctor's nearly favorite phrase.
----- Original Message -----
From: "Rick Davis" <rickdavisjr <at> comcast.net>
To: <ecos-discuss <at> sources.redhat.com>
Sent: Sunday, June 01, 2003 11:40 PM
Subject: [ECOS] RAW Ethernet I/O

> I am working on a project that will be receiving IP packets via an RS-422
> serial link. The packets will then be transmitted over Ethernet. I would
> like to use the Raw Packet interface but it doesn't look like eCos fully
> supports the raw packet interface line Linux does. I need to be able to
keep
> the received source MAC address when transmitting the data over Ethernet
as
> well as change the source MAC address to some predefined value or the
value
> of the receiver. I also don't need the IP stack because the entire packet
is
> good to go as is and needs no massaging by the IP stack. I have done this
on
> Linux but I am a newbie to eCos and was wondering how I can attach to the
> Ethernet driver directly or is there another way. Eventually the project
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrew Lunn | 2 Jun 2003 09:27
Picon
Favicon

Re: Building SID

On Sun, Jun 01, 2003 at 12:31:55AM -0700, io in wrote:
> Hello,
>  
> I am new to the world of eCos and embedded systems. I
> would be very 
> grateful if any one can answer the following queries -
>  
> Q1. I am sure most of the experts in this group have
> come across 
> building problems with SID. I am trying to build SID
> for CYGWIN environment. 
> But it fails with a error message saying "unable to
> find tcl header" 
> while "configuring testsuites". I have correctly
> followed the steps for 
> building SID given in the "FAQ-o-matic", but still the
> problem persists. 
> Kindly clarify the my mistake.

I've never tried building SID. I suppose the first thing to check is,
do you have tcl installed? Is it in the usual place? Do you need to pass parameters like --with-tcl=/usr
-with-tcl=8.3 etc.

> Q2. I want to run ecos applications on the CYGWIN
> environment as the 
> synthetic target. How do I go about buiding the
> library and the tests 
> using the windows based configtool ? Which gcc
> compiler should I uses? I 
> see the Linux-synthetic target under the templates.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrew Lunn | 2 Jun 2003 10:00
Picon
Favicon

Re: RAW Ethernet I/O

On Sun, Jun 01, 2003 at 11:40:36PM -0400, Rick Davis wrote:
> I am working on a project that will be receiving IP packets via an RS-422
> serial link. The packets will then be transmitted over Ethernet. I would
> like to use the Raw Packet interface but it doesn't look like eCos fully
> supports the raw packet interface line Linux does. I need to be able to keep
> the received source MAC address when transmitting the data over Ethernet as
> well as change the source MAC address to some predefined value or the value
> of the receiver. I also don't need the IP stack because the entire packet is
> good to go as is and needs no massaging by the IP stack. I have done this on
> Linux but I am a newbie to eCos and was wondering how I can attach to the
> Ethernet driver directly or is there another way. Eventually the project
> will go bi-directional and will also need to be able to receive RAW Ethernet
> for transmission over RS-422 serial.

If you don't need the IP stack, you could leave it out. This then
leaves free the interface the stack uses.

Probably the simplest code to understand is the interface the lwip stacks
uses. Have a look at 

packages/io/eth/current/src/lwip/eth_drv.c

You need to write something similar so you can send/receive packets.

Alternatively, you could add in the BPF code to the stack. Anthony
Massa's says this is possible. If you do do this, please let us
know. It would be nice to make this part of the main sources.

      Andrew
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Lidsten | 2 Jun 2003 11:00

RE: bug in sprintf

Hi,

I can see the same problem with printf and fprintf i.e. i cant print negative interger values. Is the below
change a recomended fix (remove the line?)

Regards, Daniel Lidsten

> -----Original Message-----
> From: Knud Wöhler [mailto:woehler <at> ossi.fho-emden.de] 
> Sent: den 30 maj 2003 17:34
> To: ecos-discuss <at> sources.redhat.com
> Subject: [ECOS] bug in sprintf
> 
> 
> Hi
> 
> The sprintf() function can not handle negative integer 
> values. I have tested 
> it on the xscale plattform. The problem is in vfnprintf.cxx. 
> The compiler 
> (arm-elf-gcc 3.2) generates wrong code for line 2 (it removes 
> the sign). If I 
> remove line 1 the generated code is ok. 
> 
> #define SARG() \
>         (flags&QUADINT ? va_arg(arg, cyg_int64) : \
>             flags&LONGINT ? va_arg(arg, long) : \
>             flags&SHORTINT ? (long)(short)va_arg(arg, int) : \
>             flags&SIZET ? va_arg(arg, size_t) : \  <-- 1
>             (long)va_arg(arg, int))  <-- 2
(Continue reading)

Permalink | Reply | 2 comments |

Gmane