running eCos under sid

running eCos under sid

[Mathieu Lacage]

hi all,

Because I am trying to avoid launching my vmware/win2k/arm simulator, I
decided to try to use sid to run a hello-world with eCos...

I built an eCos kernel for the INTEGRATOR ARM development card. Then, I
built a hello world with:
arm-elf-gcc -I/infinite/ecos/ecos/test_install/include
-L/infinite/ecos/ecos/test_install/lib -Ttarget.ld main.c -o main

I got a 1.3 MB elf binary which I tried to run in sid (yesterday's CVS)
with:
arm-elf-sif main
which gave:
bash$ arm-elf-sid -EL main
Fault (memory, 0x1a000004) pc=0x8048

I am not really experienced with such embedded systems. I can imagine
twenty thing which went wrong. (such as wrong start address,
incompatible libc, etc...). So, I tried to run a gdb thing in sid:
arm-elf-sif -EL --gdb=1024 main 
which seems to get into an infinite loop because sid never returns.

So, I tried to connect my gdb to this gdb stub with:
bash$ arm-elf-gdb main
GNU gdb 5.0
Copyright 2000 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 cisco localhost:1024
which also seems to hang into a loop.


Any comments are welcome.

Mathieu
-- 
Mathieu Lacage <mathieu_lacage@realmagic.fr>
#p: +33 1 69 19 61 97

Re: running eCos under sid

[Frank Ch. Eigler]

[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]

Hi -

On Fri, Nov 23, 2001 at 10:31:45AM +0100, Mathieu Lacage wrote:
: [...]
: Because I am trying to avoid launching my vmware/win2k/arm simulator, I
: decided to try to use sid to run a hello-world with eCos...
: 
: I built an eCos kernel for the INTEGRATOR ARM development card. Then, I
: built a hello world with:
: arm-elf-gcc -I/infinite/ecos/ecos/test_install/include
: -L/infinite/ecos/ecos/test_install/lib -Ttarget.ld main.c -o main
: 
: I got a 1.3 MB elf binary which I tried to run in sid (yesterday's CVS)
: with:
: arm-elf-sif main
: which gave:
: bash$ arm-elf-sid -EL main
: Fault (memory, 0x1a000004) pc=0x8048
: [...]

Right.  This happens because the simulator was not asked to configure
itself for a model of the "Integrator" board.  By default, it provides
a simple process model, with little in the way of simulated hardware
peripherals.  The SID component (model) library includes parts for
several ARM flavour peripherals: they were built to model the old
ARM PID development board.  To the extent that this "Integrator" board
is similar, you may make use of the components by "--board=pid7t" and
related options.  Simulation for different boards involves assembling
models for all the required parts, and configuring sid to use them:
this can be a small or big job.

For a taste, try running
	sid arm-pid-redboot-tksm.conf
(find named file under $prefix/share/sid; it explains its own origins)
then telnet to localhost:5000 (or connect gdb to localhost:5000; can
upload a RAM-startup eCos program).  This configuration brings up
the PID board simulation, preloads an older RedBoot ROM image.
RedBoot shows a command line on uart1, which is connected to TCP
port 5000.  A little tcl/tk gui also appears, so you can
monitor/interact-with the simulation as it's proceeding.

- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: running eCos under sid

[Mathieu Lacage]

le ven 23-11-2001 à 13:30, Frank Ch. Eigler a écrit :

> Right.  This happens because the simulator was not asked to configure
> itself for a model of the "Integrator" board.  By default, it provides

I was suspecting something in the like...

> a simple process model, with little in the way of simulated hardware
> peripherals.  The SID component (model) library includes parts for
> several ARM flavour peripherals: they were built to model the old
> ARM PID development board.  To the extent that this "Integrator" board
> is similar, you may make use of the components by "--board=pid7t" and
> related options.  Simulation for different boards involves assembling
> models for all the required parts, and configuring sid to use them:
> this can be a small or big job.

If I understood how sid works, this means writing the components not
available for the new board and writing a configuration file for the
board connecting the relevant pieces together ?

> 
> For a taste, try running
> 	sid arm-pid-redboot-tksm.conf
> (find named file under $prefix/share/sid; it explains its own origins)
> then telnet to localhost:5000 (or connect gdb to localhost:5000; can
> upload a RAM-startup eCos program).  This configuration brings up
> the PID board simulation, preloads an older RedBoot ROM image.
> RedBoot shows a command line on uart1, which is connected to TCP
> port 5000.  A little tcl/tk gui also appears, so you can
> monitor/interact-with the simulation as it's proceeding.

hrm, sounds cool.

I'll try this later. As a side note, I do not even own an Integrator
board and my target system has nothing to do with traditional boards so
I'll have to hack together a simulation environment myself anyway... 

/me wished there was another poor soul in his company to do it :)


thanks a lot for your quick answer,

I'll keep you updated if I can manage to release some GPL code of our
(not-yet-written) modules.


best regards,
Mathieu

> 
> - FChE
-- 
Mathieu Lacage <mathieu_lacage@realmagic.fr>
#p: +33 1 69 19 61 97

Re: running eCos under sid

[Frank Ch. Eigler]

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

Hi -

On Fri, Nov 23, 2001 at 01:53:55PM +0100, Mathieu Lacage wrote:
: [...]
: If I understood how sid works, this means writing the components not
: available for the new board and writing a configuration file for the
: board connecting the relevant pieces together ?

That's right.


: [...]
: I'll try this later. As a side note, I do not even own an Integrator
: board 

(Then you might find eCos' "pid" platform a more comfortable fit for
sid's provided components & configurations.)

: and my target system has nothing to do with traditional boards so
: I'll have to hack together a simulation environment myself anyway... 

Good - you may find the sid manuals of use.

: [...]
: I'll keep you updated if I can manage to release some GPL code of our
: (not-yet-written) modules.

Even if you simply end up using some peculiar configurations of
existing models, it would be good to hear of them.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: running eCos under sid

[Frank Ch. Eigler]

Hi -

On Fri, Nov 23, 2001 at 01:53:55PM +0100, Mathieu Lacage wrote:
: [...]
: If I understood how sid works, this means writing the components not
: available for the new board and writing a configuration file for the
: board connecting the relevant pieces together ?

That's right.


: [...]
: I'll try this later. As a side note, I do not even own an Integrator
: board 

(Then you might find eCos' "pid" platform a more comfortable fit for
sid's provided components & configurations.)

: and my target system has nothing to do with traditional boards so
: I'll have to hack together a simulation environment myself anyway... 

Good - you may find the sid manuals of use.

: [...]
: I'll keep you updated if I can manage to release some GPL code of our
: (not-yet-written) modules.

Even if you simply end up using some peculiar configurations of
existing models, it would be good to hear of them.


- FChE
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7/kjMVZbdDOm/ZT0RAlkgAJ0dgykI1mdBarsGsqDBX0wjoVgGrACff+6n
Gi+hZcdzLmXl00ZagRuhaSc=
=xek7
-----END PGP SIGNATURE-----

Re: running eCos under sid

[Mathieu Lacage]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]

le ven 23-11-2001 à 13:30, Frank Ch. Eigler a écrit :

> Right.  This happens because the simulator was not asked to configure
> itself for a model of the "Integrator" board.  By default, it provides

I was suspecting something in the like...

> a simple process model, with little in the way of simulated hardware
> peripherals.  The SID component (model) library includes parts for
> several ARM flavour peripherals: they were built to model the old
> ARM PID development board.  To the extent that this "Integrator" board
> is similar, you may make use of the components by "--board=pid7t" and
> related options.  Simulation for different boards involves assembling
> models for all the required parts, and configuring sid to use them:
> this can be a small or big job.

If I understood how sid works, this means writing the components not
available for the new board and writing a configuration file for the
board connecting the relevant pieces together ?

> 
> For a taste, try running
> 	sid arm-pid-redboot-tksm.conf
> (find named file under $prefix/share/sid; it explains its own origins)
> then telnet to localhost:5000 (or connect gdb to localhost:5000; can
> upload a RAM-startup eCos program).  This configuration brings up
> the PID board simulation, preloads an older RedBoot ROM image.
> RedBoot shows a command line on uart1, which is connected to TCP
> port 5000.  A little tcl/tk gui also appears, so you can
> monitor/interact-with the simulation as it's proceeding.

hrm, sounds cool.

I'll try this later. As a side note, I do not even own an Integrator
board and my target system has nothing to do with traditional boards so
I'll have to hack together a simulation environment myself anyway... 

/me wished there was another poor soul in his company to do it :)


thanks a lot for your quick answer,

I'll keep you updated if I can manage to release some GPL code of our
(not-yet-written) modules.


best regards,
Mathieu

> 
> - FChE
-- 
Mathieu Lacage <mathieu_lacage@realmagic.fr>
#p: +33 1 69 19 61 97

Re: running eCos under sid

[Frank Ch. Eigler]

Hi -

On Fri, Nov 23, 2001 at 10:31:45AM +0100, Mathieu Lacage wrote:
: [...]
: Because I am trying to avoid launching my vmware/win2k/arm simulator, I
: decided to try to use sid to run a hello-world with eCos...
: 
: I built an eCos kernel for the INTEGRATOR ARM development card. Then, I
: built a hello world with:
: arm-elf-gcc -I/infinite/ecos/ecos/test_install/include
: -L/infinite/ecos/ecos/test_install/lib -Ttarget.ld main.c -o main
: 
: I got a 1.3 MB elf binary which I tried to run in sid (yesterday's CVS)
: with:
: arm-elf-sif main
: which gave:
: bash$ arm-elf-sid -EL main
: Fault (memory, 0x1a000004) pc=0x8048
: [...]

Right.  This happens because the simulator was not asked to configure
itself for a model of the "Integrator" board.  By default, it provides
a simple process model, with little in the way of simulated hardware
peripherals.  The SID component (model) library includes parts for
several ARM flavour peripherals: they were built to model the old
ARM PID development board.  To the extent that this "Integrator" board
is similar, you may make use of the components by "--board=pid7t" and
related options.  Simulation for different boards involves assembling
models for all the required parts, and configuring sid to use them:
this can be a small or big job.

For a taste, try running
	sid arm-pid-redboot-tksm.conf
(find named file under $prefix/share/sid; it explains its own origins)
then telnet to localhost:5000 (or connect gdb to localhost:5000; can
upload a RAM-startup eCos program).  This configuration brings up
the PID board simulation, preloads an older RedBoot ROM image.
RedBoot shows a command line on uart1, which is connected to TCP
port 5000.  A little tcl/tk gui also appears, so you can
monitor/interact-with the simulation as it's proceeding.

- FChE
-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7/kFlVZbdDOm/ZT0RAmYrAJ92yAK6SaaEf1nxGuAnC45xYb8qDgCfQEn+
VQOOxF/5VgRCspvzuqvVC/U=
=dcIy
-----END PGP SIGNATURE-----

running eCos under sid

[Mathieu Lacage]

hi all,

Because I am trying to avoid launching my vmware/win2k/arm simulator, I
decided to try to use sid to run a hello-world with eCos...

I built an eCos kernel for the INTEGRATOR ARM development card. Then, I
built a hello world with:
arm-elf-gcc -I/infinite/ecos/ecos/test_install/include
-L/infinite/ecos/ecos/test_install/lib -Ttarget.ld main.c -o main

I got a 1.3 MB elf binary which I tried to run in sid (yesterday's CVS)
with:
arm-elf-sif main
which gave:
bash$ arm-elf-sid -EL main
Fault (memory, 0x1a000004) pc=0x8048

I am not really experienced with such embedded systems. I can imagine
twenty thing which went wrong. (such as wrong start address,
incompatible libc, etc...). So, I tried to run a gdb thing in sid:
arm-elf-sif -EL --gdb=1024 main 
which seems to get into an infinite loop because sid never returns.

So, I tried to connect my gdb to this gdb stub with:
bash$ arm-elf-gdb main
GNU gdb 5.0
Copyright 2000 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 cisco localhost:1024
which also seems to hang into a loop.


Any comments are welcome.

Mathieu
-- 
Mathieu Lacage <mathieu_lacage@realmagic.fr>
#p: +33 1 69 19 61 97