[ECOS] Debug session

[ECOS] Debug session

[Xavier]

arm-elf-gdb redboot.elf
GNU gdb 5.3 (eCosCentric)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf"...
(gdb) target rdi /dev/ttyS0
JEENI (ADP, ARM7TDI) Rev 2.0
Rebuilt on Oct 18 1999 at 18:31:13
SN=0101J107 ENET=00:80:CF:00:0C:68 IP=192.168.72.88 (255.255.255.0)
Serial Rate:   9600
Connected to ARM RDI target.
(gdb) list set_debug_comm
255
256         CYG_ASSERT(__comm_id >= CYGNUM_CALL_IF_SET_COMM_ID_MANGLER
257                    && __comm_id < CYGNUM_HAL_VIRTUAL_VECTOR_NUM_CHANNELS,
258                    "Invalid channel");
259
260         switch (__comm_id) {
261         case CYGNUM_CALL_IF_SET_COMM_ID_QUERY_CURRENT:
262             if (__selected_id > 0)
263                 res = __selected_id-1;
264             else if (__selected_id == 0)
(gdb) list 271
266             else
267                 res = __selected_id;
268             break;
269
270         case CYGNUM_CALL_IF_SET_COMM_ID_EMPTY:
271             CYGACC_CALL_IF_DEBUG_PROCS_SET(0);
272             __selected_id = __comm_id;
273             break;
274
275         case CYGNUM_CALL_IF_SET_COMM_ID_MANGLER:
(gdb) break 271
Breakpoint 1 at 0x5764: file /usr/local/ecos/ecos-2.0/packages/hal/common/v2_0/src/hal_if.c, line 271.
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y

Starting program: /home/xavier/project/ecos/lpc2294/redboot.elf

Breakpoint 1, set_debug_comm (__comm_id=-536707060)
    at /usr/local/ecos/ecos-2.0/packages/hal/common/v2_0/src/hal_if.c:271
271             CYGACC_CALL_IF_DEBUG_PROCS_SET(0);
(gdb) info local
__selected_id = 22356
__chan = (volatile CYG_ADDRWORD (*)[8]) 0x84
interrupt_state = -2130696852
res = 252
update = 16
(gdb) step
272             __selected_id = __comm_id;
(gdb) info local
__selected_id = 22356
__chan = (volatile CYG_ADDRWORD (*)[8]) 0x40000070
interrupt_state = -2130696852
res = 252
update = 16
(gdb) step
RDI_setbreak: data abort, no memory at specified address?
RDI_execute: prefetch abort, execution ran into unmapped memory?
RDI_read: data abort, no memory at specified address?
RDI_read: data abort, no memory at specified address?
Error accessing memory address 0xfffffffe: Resource temporarily unavailable.
RDI_setbreak: data abort, no memory at specified address?
Warning:
Cannot insert breakpoint 0.
Error accessing memory address 0x5e20: Input/output error.
The same program may be running in another process.
(gdb)

Any suggestions as to which way to go from here?


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

[ECOS] Redboot Server address problem

[Vijay Jayaraman]

Hello friends,
 I am working with Redboot and I am trying to compile with Redboot having
the following setup.
IP ADDRESS - 192.168.0.5
GATEWAY - 192.168.0.1
DNS - 192.168.0.1
Subnet Mask - 255.255.255.0
Server IP (as in ip_address -h) - 192.168.0.2

I have managed to set all the above in the ecos.ecc file and they work
perfectly fine. But, everytime
I need to specigy the Server IP using

REDBOOT> ip_address -h 192.168.0.2

Is there a way I could change that too?? I could not find an option to
change it in the ecos.ecc file.
Is the host address same as the DNS???

Any help is appreciated.

Thanks,
-Vijay



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

[ECOS] Redboot make tests fails.

[Vijay Jayaraman]

Guys,
 I created a ecos.ecc file using
1. ecosconfig new pc redboot
2. edited it to accomodate the IP address changes.
3. Did make which worked fine I have a bin image. for floppy.
4. But when I tried make tests, It failed giving me the following error, can
any one tell me why it failed??

make[1]: Leaving directory `/home/vijay/rbaddress/hal/i386/generic/v2_0'
make -r -C hal/i386/pc/v2_0 tests
make[1]: Entering directory `/home/vijay/rbaddress/hal/i386/pc/v2_0'
make[1]: Nothing to be done for `tests'.
make[1]: Leaving directory `/home/vijay/rbaddress/hal/i386/pc/v2_0'
make -r -C hal/i386/pcmb/v2_0 tests
make[1]: Entering directory `/home/vijay/rbaddress/hal/i386/pcmb/v2_0'
make[1]: Nothing to be done for `tests'.
make[1]: Leaving directory `/home/vijay/rbaddress/hal/i386/pcmb/v2_0'
make -r -C io/pci/v2_0 tests
make[1]: Entering directory `/home/vijay/rbaddress/io/pci/v2_0'
i386-elf-gcc -g -nostdlib -Wl,--gc-sections -Wl,-static -L/home/vijay/rbaddr
ess/install/lib -Ttarget.ld -o
/home/vijay/rbaddress/install/tests/io/pci/v2_0/tests/pci1 tests/pci1.o
/home/vijay/rbaddress/install/lib/libtarget.a(redboot_main.o): In function
`bist':
/opt/ecos/ecos-2.0/packages/redboot/v2_0/src/main.c:625: multiple definition
of `cyg_start'
tests/pci1.o:/opt/ecos/ecos-2.0/packages/io/pci/v2_0/tests/pci1.c:448: first
defined here
/opt/ecos/gnutools/i386-elf/bin/../lib/gcc-lib/i386-elf/3.2.1/../../../../i3
86-elf/bin/ld: Warning: size of symbol `cyg_start' changed from 38 to 615 in
/home/vijay/rbaddress/install/lib/libtarget.a(redboot_main.o)
collect2: ld returned 1 exit status
make[1]: *** [/home/vijay/rbaddress/install/tests/io/pci/v2_0/tests/pci1]
Error 1
make[1]: Leaving directory `/home/vijay/rbaddress/io/pci/v2_0'
make: *** [tests] Error 2

Thanks for any help in advance.
-Vijay




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

Re: [ECOS] Redboot Server address problem

[Andrew Lunn]

On Sun, Sep 12, 2004 at 08:14:05PM -0600, Vijay Jayaraman wrote:
> Hello friends,
>  I am working with Redboot and I am trying to compile with Redboot having
> the following setup.
> IP ADDRESS - 192.168.0.5
> GATEWAY - 192.168.0.1
> DNS - 192.168.0.1
> Subnet Mask - 255.255.255.0
> Server IP (as in ip_address -h) - 192.168.0.2
> 
> I have managed to set all the above in the ecos.ecc file and they work
> perfectly fine. But, everytime
> I need to specigy the Server IP using
> 
> REDBOOT> ip_address -h 192.168.0.2
> 
> Is there a way I could change that too?? I could not find an option to
> change it in the ecos.ecc file.
> Is the host address same as the DNS???

Nope its different. Are your sources up to date? If so you can use
CYGDAT_REDBOOT_DEFAULT_BOOTP_SERVER_IP_ADDR

        Andrew

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

Re: [ECOS] Redboot make tests fails.

[Andrew Lunn]

On Sun, Sep 12, 2004 at 08:20:24PM -0600, Vijay Jayaraman wrote:
> Guys,
>  I created a ecos.ecc file using
> 1. ecosconfig new pc redboot
> 2. edited it to accomodate the IP address changes.
> 3. Did make which worked fine I have a bin image. for floppy.
> 4. But when I tried make tests, It failed giving me the following error, can
> any one tell me why it failed??

The redboot configuration is special and cannot be used for the
tests. Use a normal configuration for building the tests.

        Andrew

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

Re: [ECOS] Redboot Server address problem

[Vijay Jayaraman]

Andrew,
 Thanks for the help. I had been using the old sources until you told me.
Now I am using the current version and can locate the
CYGDAT_REDBOOT_DEFAULT_BOOTP_SERVER_IP_ADDR and I can change it.

 I did the following with my updated ecos repository and got this error. I
have split it with '----' for easy reading...

vijay@linux:~/tmp>
ecosconfig --srcdir=/home/vijay/ecos_latest/ecos/packages/ new pc redboot
U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
U CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK, new inferred value 0
----
vijay@linux:~/tmp> echo $ECOS_REPOSITORY
/opt/ecos/ecos-2.0/packages
vijay@linux:~/tmp> ECOS_REPOSITORY2="/home/vijay/ecos_latest/ecos/packages"
vijay@linux:~/tmp> echo $ECOS_REPOSITORY2
/home/vijay/ecos_latest/ecos/packages
----
vijay@linux:~/tmp>
ecosconfig --srcdir=/home/vijay/ecos_latest/ecos/packages/ import
${ECOS_REPOSITORY2}/hal/i386/pc/current/misc/redboot_FLOPPY.ecm
U CYGHWR_HAL_I386_FPU_SWITCH_LAZY, new inferred value 0
vijay@linux:~/tmp> ls
ecos.ecc
vijay@linux:~/tmp> ecosconfig --srcdir=~/ecos_latest/ecos/packages tree
vijay@linux:~/tmp> ls
devs  ecos.ecc  hal  infra  install  io  isoinfra  language  makefile
redboot  services
vijay@linux:~/tmp> make
make -r -C hal/i386/arch/current headers
make[1]: Entering directory `/home/vijay/tmp/hal/i386/arch/current'
make[1]: Leaving directory `/home/vijay/tmp/hal/i386/arch/current'
make -r -C hal/i386/generic/current headers
make[1]: Entering directory `/home/vijay/tmp/hal/i386/generic/current'
make[1]: Leaving directory `/home/vijay/tmp/hal/i386/generic/current'
make -r -C hal/i386/pc/current headers
make[1]: Entering directory `/home/vijay/tmp/hal/i386/pc/current'
make[1]: Leaving directory `/home/vijay/tmp/hal/i386/pc/current'
make -r -C hal/i386/pcmb/current headers
make[1]: Entering directory `/home/vijay/tmp/hal/i386/pcmb/current'
make[1]: Leaving directory `/home/vijay/tmp/hal/i386/pcmb/current'
make -r -C io/pci/current headers
make[1]: Entering directory `/home/vijay/tmp/io/pci/current'
make[1]: Leaving directory `/home/vijay/tmp/io/pci/current'
make -r -C devs/eth/intel/i82559/current headers
make[1]: Entering directory `/home/vijay/tmp/devs/eth/intel/i82559/current'
make[1]: Leaving directory `/home/vijay/tmp/devs/eth/intel/i82559/current'
make -r -C devs/eth/i386/pc/i82559/current headers
make[1]: Entering directory
`/home/vijay/tmp/devs/eth/i386/pc/i82559/current'
make[1]: Leaving directory `/home/vijay/tmp/devs/eth/i386/pc/i82559/current'
make -r -C hal/common/current headers
make[1]: Entering directory `/home/vijay/tmp/hal/common/current'
make[1]: Leaving directory `/home/vijay/tmp/hal/common/current'
make -r -C infra/current headers
make[1]: Entering directory `/home/vijay/tmp/infra/current'
make[1]: Leaving directory `/home/vijay/tmp/infra/current'
make -r -C redboot/current headers
make[1]: Entering directory `/home/vijay/tmp/redboot/current'
make[1]: Leaving directory `/home/vijay/tmp/redboot/current'
make -r -C isoinfra/current headers
make[1]: Entering directory `/home/vijay/tmp/isoinfra/current'
make[1]: Leaving directory `/home/vijay/tmp/isoinfra/current'
make -r -C language/c/libc/string/current headers
make[1]: Entering directory `/home/vijay/tmp/language/c/libc/string/current'
make[1]: Leaving directory `/home/vijay/tmp/language/c/libc/string/current'
make -r -C services/crc/current headers
make[1]: Entering directory `/home/vijay/tmp/services/crc/current'
make[1]: Leaving directory `/home/vijay/tmp/services/crc/current'
make -r -C io/eth/current headers
make[1]: Entering directory `/home/vijay/tmp/io/eth/current'
make[1]: Leaving directory `/home/vijay/tmp/io/eth/current'
headers finished
make -r -C hal/i386/arch/current build
make[1]: Entering directory `/home/vijay/tmp/hal/i386/arch/current'
make[1]: *** No rule to make target `src/hal_misc.o.d', needed by
`libtarget.a.stamp'.  Stop.
make[1]: Leaving directory `/home/vijay/tmp/hal/i386/arch/current'
make: *** [build] Error 2
vijay@linux:~/tmp>
----

Should I try removing my ecos v2.0 completely and try setting my
ECOS_REPOSITORY to the latest version? Am I missing some critical step
here...
Thanks in advance,
-Vijay




----- Original Message ----- 
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu>
Cc: <ecos-discuss@ecos.sourceware.org>
Sent: Monday, September 13, 2004 12:37 AM
Subject: Re: [ECOS] Redboot Server address problem


> On Sun, Sep 12, 2004 at 08:14:05PM -0600, Vijay Jayaraman wrote:
> > Hello friends,
> >  I am working with Redboot and I am trying to compile with Redboot
having
> > the following setup.
> > IP ADDRESS - 192.168.0.5
> > GATEWAY - 192.168.0.1
> > DNS - 192.168.0.1
> > Subnet Mask - 255.255.255.0
> > Server IP (as in ip_address -h) - 192.168.0.2
> >
> > I have managed to set all the above in the ecos.ecc file and they work
> > perfectly fine. But, everytime
> > I need to specigy the Server IP using
> >
> > REDBOOT> ip_address -h 192.168.0.2
> >
> > Is there a way I could change that too?? I could not find an option to
> > change it in the ecos.ecc file.
> > Is the host address same as the DNS???
>
> Nope its different. Are your sources up to date? If so you can use
> CYGDAT_REDBOOT_DEFAULT_BOOTP_SERVER_IP_ADDR
>
>         Andrew
>
> -- 
> 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

Re: [ECOS] Redboot Server address problem

[Andrew Lunn]

On Mon, Sep 13, 2004 at 01:43:54AM -0600, Vijay Jayaraman wrote:
> Andrew,
>  Thanks for the help. I had been using the old sources until you told me.
> Now I am using the current version and can locate the
> CYGDAT_REDBOOT_DEFAULT_BOOTP_SERVER_IP_ADDR and I can change it.
> 
>  I did the following with my updated ecos repository and got this error. I
> have split it with '----' for easy reading...
> 
> vijay@linux:~/tmp>
> ecosconfig --srcdir=/home/vijay/ecos_latest/ecos/packages/ new pc redboot
> U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
> U CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK, new inferred value 0
> ----
> vijay@linux:~/tmp> echo $ECOS_REPOSITORY
> /opt/ecos/ecos-2.0/packages
> vijay@linux:~/tmp> ECOS_REPOSITORY2="/home/vijay/ecos_latest/ecos/packages"
> vijay@linux:~/tmp> echo $ECOS_REPOSITORY2
> /home/vijay/ecos_latest/ecos/packages
> ----
> vijay@linux:~/tmp>
> ecosconfig --srcdir=/home/vijay/ecos_latest/ecos/packages/ import
> ${ECOS_REPOSITORY2}/hal/i386/pc/current/misc/redboot_FLOPPY.ecm
> U CYGHWR_HAL_I386_FPU_SWITCH_LAZY, new inferred value 0
> vijay@linux:~/tmp> ls

You should start from an empty directory and do all the steps, not
just an import.

        Andrew

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

Re: [ECOS] Redboot Server address problem

[Vijay Jayaraman]

Andrew,
 I dont quite understand what you mean by ALL the steps. I thought that
ecosconfig new xyz
add module (if needed)
ecosconfig tree
ecosconfig check
ecosconfig resolve (if needed)
make
make tests

were the complete set of steps. I didnt know there was a superset of steps.
Can you guide me to it??
Thanks,
-Vijay
[FYI, I am using a normal pc and doing a RAM based load of redboot.]

----- Original Message ----- 
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu>
Cc: <ecos-discuss@ecos.sourceware.org>
Sent: Monday, September 13, 2004 1:52 AM
Subject: Re: [ECOS] Redboot Server address problem


> On Mon, Sep 13, 2004 at 01:43:54AM -0600, Vijay Jayaraman wrote:
> > Andrew,
> >  Thanks for the help. I had been using the old sources until you told
me.
> > Now I am using the current version and can locate the
> > CYGDAT_REDBOOT_DEFAULT_BOOTP_SERVER_IP_ADDR and I can change it.
> >
> >  I did the following with my updated ecos repository and got this error.
I
> > have split it with '----' for easy reading...
> >
> > vijay@linux:~/tmp>
> > ecosconfig --srcdir=/home/vijay/ecos_latest/ecos/packages/ new pc
redboot
> > U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
> > U CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK, new inferred value 0
> > ----
> > vijay@linux:~/tmp> echo $ECOS_REPOSITORY
> > /opt/ecos/ecos-2.0/packages
> > vijay@linux:~/tmp>
ECOS_REPOSITORY2="/home/vijay/ecos_latest/ecos/packages"
> > vijay@linux:~/tmp> echo $ECOS_REPOSITORY2
> > /home/vijay/ecos_latest/ecos/packages
> > ----
> > vijay@linux:~/tmp>
> > ecosconfig --srcdir=/home/vijay/ecos_latest/ecos/packages/ import
> > ${ECOS_REPOSITORY2}/hal/i386/pc/current/misc/redboot_FLOPPY.ecm
> > U CYGHWR_HAL_I386_FPU_SWITCH_LAZY, new inferred value 0
> > vijay@linux:~/tmp> ls
>
> You should start from an empty directory and do all the steps, not
> just an import.
>
>         Andrew
>



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

Re: [ECOS] Redboot Server address problem

[Andrew Lunn]

On Mon, Sep 13, 2004 at 09:18:54AM -0600, Vijay Jayaraman wrote:
> Andrew,
>  I dont quite understand what you mean by ALL the steps. I thought that
> ecosconfig new xyz
> add module (if needed)
> ecosconfig tree
> ecosconfig check
> ecosconfig resolve (if needed)
> make
> make tests

Thats fine, so long as you don't use the redboot template and what to
build the tests. Your previous post did use redboot, so make tests
will not work.

        Andrew

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

[ECOS] zImage Help.

[Vijay Jayaraman]

Hi Friends,

I have done the following
- Redboot up and running with proper IP addresses.
- all the tests under 'ecosconfig new pc' works fine when loaded from the
/tftpboot folder via ethernet

1)
I want to load the kernel onto the pc. I have found a lot of posts on
RedBoot> load -r -b 0x8c210000 zImage  or so... but none where it specifies
how to create a zImage.
I would appreciate it if any one can tell me how to create a basic zImage so
that I can
load the kernel onto the pc. I could not find it in the ecos users guide. My
apologies if
I had missed it.

2)
I also remember reading somewhere that ecos programs dont need the kernel to
run. Is this correct?

Any help is greatly appreciated.
Thanks in advance,
-Vijay


----- Original Message ----- 
From: "Andrew Lunn" <andrew@lunn.ch>
To: "Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu>
Cc: "Andrew Lunn" <andrew@lunn.ch>; <ecos-discuss@ecos.sourceware.org>
Sent: Monday, September 13, 2004 12:48 PM
Subject: Re: [ECOS] Redboot Server address problem


> On Mon, Sep 13, 2004 at 09:18:54AM -0600, Vijay Jayaraman wrote:
> > Andrew,
> >  I dont quite understand what you mean by ALL the steps. I thought that
> > ecosconfig new xyz
> > add module (if needed)
> > ecosconfig tree
> > ecosconfig check
> > ecosconfig resolve (if needed)
> > make
> > make tests
>
> Thats fine, so long as you don't use the redboot template and what to
> build the tests. Your previous post did use redboot, so make tests
> will not work.
>
>         Andrew
>
> -- 
> 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

Re: [ECOS] zImage Help.

[Vijay Jayaraman]

Apologies, I meant, I want to load the kernel onto the target (pc). not the
pc as in 'host pc'.

-Vijay


----- Original Message ----- 
From: "Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@ecos.sourceware.org>
Sent: Tuesday, September 14, 2004 1:33 AM
Subject: [ECOS] zImage Help.


> Hi Friends,
>
> I have done the following
> - Redboot up and running with proper IP addresses.
> - all the tests under 'ecosconfig new pc' works fine when loaded from the
> /tftpboot folder via ethernet
>
> 1)
> I want to load the kernel onto the pc. I have found a lot of posts on
> RedBoot> load -r -b 0x8c210000 zImage  or so... but none where it
specifies
> how to create a zImage.
> I would appreciate it if any one can tell me how to create a basic zImage
so
> that I can
> load the kernel onto the pc. I could not find it in the ecos users guide.
My
> apologies if
> I had missed it.
>
> 2)
> I also remember reading somewhere that ecos programs dont need the kernel
to
> run. Is this correct?
>
> Any help is greatly appreciated.
> Thanks in advance,
> -Vijay
>
>
> ----- Original Message ----- 
> From: "Andrew Lunn" <andrew@lunn.ch>
> To: "Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu>
> Cc: "Andrew Lunn" <andrew@lunn.ch>; <ecos-discuss@ecos.sourceware.org>
> Sent: Monday, September 13, 2004 12:48 PM
> Subject: Re: [ECOS] Redboot Server address problem
>
>
> > On Mon, Sep 13, 2004 at 09:18:54AM -0600, Vijay Jayaraman wrote:
> > > Andrew,
> > >  I dont quite understand what you mean by ALL the steps. I thought
that
> > > ecosconfig new xyz
> > > add module (if needed)
> > > ecosconfig tree
> > > ecosconfig check
> > > ecosconfig resolve (if needed)
> > > make
> > > make tests
> >
> > Thats fine, so long as you don't use the redboot template and what to
> > build the tests. Your previous post did use redboot, so make tests
> > will not work.
> >
> >         Andrew
> >
> > -- 
> > 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
>



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

Re: [ECOS] zImage Help.

[Andrew Lunn]

On Tue, Sep 14, 2004 at 01:36:00AM -0600, Vijay Jayaraman wrote:
> Apologies, I meant, I want to load the kernel onto the target (pc). not the
> pc as in 'host pc'.

Download the kernel from ftp.us.kernel.org
make menuconfig
make dep
make zImage

        Andrew 

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

Re: [ECOS] zImage Help.

[Nick Garnett]

"Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu> writes:

> Hi Friends,
> 
> I have done the following
> - Redboot up and running with proper IP addresses.
> - all the tests under 'ecosconfig new pc' works fine when loaded from the
> /tftpboot folder via ethernet
> 
> 1)
> I want to load the kernel onto the pc. I have found a lot of posts on
> RedBoot> load -r -b 0x8c210000 zImage  or so... but none where it specifies
> how to create a zImage.
> I would appreciate it if any one can tell me how to create a basic zImage so
> that I can
> load the kernel onto the pc. I could not find it in the ecos users guide. My
> apologies if
> I had missed it.

What exactly are you trying to do? zImage is for Linux. If you want to
boot Linux on the PC use LILO or GRUB. There is no support in RedBoot
for running Linux.

If you have indeed run all the tests, then you have successfully
loaded and run eCos. Just build your application as described in the
documentation and load it in exactly the same way.

> 
> 2)
> I also remember reading somewhere that ecos programs dont need the kernel to
> run. Is this correct?

eCos programs need the eCos kernel to run. You can configure eCos down
to eliminate the kernel -- RedBoot is an example of this -- however,
most program do need the kernel.



-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


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

Re: [ECOS] zImage Help.

[Vijay Jayaraman]

Nick,
 I am just trying to figure out where to go next after configuring Redboot
and successfully testing all the tests from a normal ecosconfig new pc
build. I had this notion that I need to install the kernel into the hard
disk some how (or run it from memory) so that I can run my custom program on
it. I didnt realize that all you need to do is write your code compile it
and then load it via tftpboot. (Please correct me if I am wrong, This is
just my guess from reading the posts online...)

 Also, one more question, when I wanted to write the ip_address configured
Redboot onto a bootable floppy, I need to import a file called Floppy.ecm
file or so. If I did not do that, all I get is an elf image and I am unable
to boot with that. I thought elf images were some sort of linux executables.
I dont know why they cannot be used to boot from floppy... So I suppose one
needs to import the .ecm file everytime he wants to create a Redboot.bin
file.

Thanks,
-Vijay

----- Original Message ----- 
From: "Nick Garnett" <nickg@ecoscentric.com>
To: "Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu>
Cc: "Andrew Lunn" <andrew@lunn.ch>; <ecos-discuss@ecos.sourceware.org>
Sent: Tuesday, September 14, 2004 3:45 AM
Subject: Re: [ECOS] zImage Help.


> "Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu> writes:
>
> > Hi Friends,
> >
> > I have done the following
> > - Redboot up and running with proper IP addresses.
> > - all the tests under 'ecosconfig new pc' works fine when loaded from
the
> > /tftpboot folder via ethernet
> >
> > 1)
> > I want to load the kernel onto the pc. I have found a lot of posts on
> > RedBoot> load -r -b 0x8c210000 zImage  or so... but none where it
specifies
> > how to create a zImage.
> > I would appreciate it if any one can tell me how to create a basic
zImage so
> > that I can
> > load the kernel onto the pc. I could not find it in the ecos users
guide. My
> > apologies if
> > I had missed it.
>
> What exactly are you trying to do? zImage is for Linux. If you want to
> boot Linux on the PC use LILO or GRUB. There is no support in RedBoot
> for running Linux.
>
> If you have indeed run all the tests, then you have successfully
> loaded and run eCos. Just build your application as described in the
> documentation and load it in exactly the same way.
>
> >
> > 2)
> > I also remember reading somewhere that ecos programs dont need the
kernel to
> > run. Is this correct?
>
> eCos programs need the eCos kernel to run. You can configure eCos down
> to eliminate the kernel -- RedBoot is an example of this -- however,
> most program do need the kernel.
>
>
>
> -- 
> Nick Garnett                    eCos Kernel Architect
> http://www.ecoscentric.com/     The eCos and RedBoot experts
>



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

Re: [ECOS] zImage Help.

[Nick Garnett]

"Vijay Jayaraman" <Vijay.Jayaraman@Colorado.edu> writes:

> Nick,
>  I am just trying to figure out where to go next after configuring Redboot
> and successfully testing all the tests from a normal ecosconfig new pc
> build. I had this notion that I need to install the kernel into the hard
> disk some how (or run it from memory) so that I can run my custom program on
> it. I didnt realize that all you need to do is write your code compile it
> and then load it via tftpboot. (Please correct me if I am wrong, This is
> just my guess from reading the posts online...)

You compile your application against the set of headers supplied by
eCos and then link it with the ecos library to generate an ELF
executable, which includes all of eCos kernel and all. This is then
loaded directly by GDB or can be converted to a binary or S-Record
image for loading in RedBoot.

> 
>  Also, one more question, when I wanted to write the ip_address configured
> Redboot onto a bootable floppy, I need to import a file called Floppy.ecm
> file or so. If I did not do that, all I get is an elf image and I am unable
> to boot with that. I thought elf images were some sort of linux executables.
> I dont know why they cannot be used to boot from floppy... So I suppose one
> needs to import the .ecm file everytime he wants to create a Redboot.bin
> file.

You must always use the .ecm file for generating RedBoot. 


I think you need to go back and read the documentation again.


-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


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