Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[T Satish Kumar]

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

due to file size constraints, i  m compressing the twothreads.x as
twothreads.bz2
kindly test it and let me know..

thanks
satish

----- Original Message -----
From: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>; <sid@sources.redhat.com>
Sent: Tuesday, September 17, 2002 12:16 PM
Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator


> Hi,
>        i m attaching the twothreads.x file..
> kindly someone test this file on the arm7t simulator, and let me know if
it
> works..
> coz, i may not able to connect to the target here..and i m not able to
find
> any reason
> for it..coz, there was no error in building any of the tools.
>
> plz kindly try it on cygwin only, coz all this i m trying onWindows 2000.
> and arm development tools are as follows:
> arm-elf-gcc version 2.95.2
> arm-elf-gdb version 5.2(insight-5.2)
> Tcl-Tk version 8.3.4
> eCos version 1.3.1
> and last weeks sid snapshot release.
>
> plz some one help me in solving this problem.
>
> thanks
> satish
>
>
> ----- Original Message -----
> From: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>
> To: "Frank Ch. Eigler" <fche@redhat.com>
> Cc: <ecos-discuss@sources.redhat.com>; <sid@sources.redhat.com>
> Sent: Tuesday, September 17, 2002 10:56 AM
> Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator
>
>
> > well, i even tried installin a new version insight-5.2..
> > and did the same check..but still i m not able to connect to the target.
> > what could be the problem..?
> >
> > satish
> >
> > ----- Original Message -----
> > From: "Frank Ch. Eigler" <fche@redhat.com>
> > To: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>
> > Cc: <ecos-discuss@sources.redhat.com>; <sid@sources.redhat.com>
> > Sent: Monday, September 16, 2002 5:36 PM
> > Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator
> >
> >
> > > Hi -
> > >
> > > On Tue, Sep 17, 2002 at 09:26:39AM -0700, T Satish Kumar wrote:
> > > > [...]
> > > > but my first step still remains unsuccessful..i m not able to
connect
> to
> > the
> > > > target.
> > > > my target settings are as follows:
> > > > Target:Remote/TCP
> > > > hostname:localhost
> > > > port:2000
> > > > and i have Tcl-Tk 8.3.4 and Insight ver-20020620 installed on my
> Windows
> > > > 2000.
> > > > i m trying all this on cygwin.
> > >
> > > I suspect something wrong with your insight build.  How about
> > > trying plain gdb (as in "gdb -nw FILE", "target remote
localhost:2000",
> > > and so on)?
> > >
> > >
> > > > P.S: i could successfully built the arm-development tools, ecos
> library
> > and
> > > > the sid.
> > >
> > > Very good.
> > >
> > >
> > > - FChE
> > >
> >
> >
>

[-- Attachment #2: twothreads.bz2 --]
[-- Type: application/octet-stream, Size: 235797 bytes --]

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[T Satish Kumar]

i m gettin a stackdump while running the command:
arm-elf-sid --board=pid7t-normalmap --gdb=2000 --tksm -EL &
 the followig is the contents of the stack dump(sid.exe.stackdump)

Exception: STATUS_ACCESS_VIOLATION at eip=610949B9
eax=6C62696C ebx=6564616F ecx=00000428 edx=6C62696C esi=10059138
edi=10058D20
ebp=0022ED34 esp=0022ED0C
program=D:\cygwin\tools\H-i686-pc-cygwin\sid\bin\sid.
xe
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022ED34  610949B9  (610A0020, 10059130, 1005290C, 0048D042)
0022ED54  6102E205  (10059130, 00000001, 1005290C, 00000000)
0022EDE4  0048D085  (10051888, 10051188, 0022F274, 004735A5)
0022F274  004735D3  (10051028, 0022F4F4, 0022F4D4, 00000004)
0022F524  0045B829  (10051028, 0022FBE4, 0022F574, 0045E41A)
0022F574  0045E435  (10051028, 0022FBE4, 0022F6B4, 00000000)
0022FC34  00461E69  (10051028, 10050C14, 0000000C, 0098F7F3)
0022FC74  0095D0CF  (10051910, 10050C14, 00000000, FFFFFFFF)
0022FD24  00996520  (10051048, 0022FE34, 10050C14, 004030ED)
0022FEB4  004031C7  (00000002, 61564D28, 10050278, 00000000)
0022FF10  61003F42  (00000000, 00000000, 00000000, 00000001)
0022FF40  61004236  (00402A24, 00000000, 82E78620, 00000000)
0022FF60  61004275  (00000000, 00000000, 82E787B0, 00000005)
0022FF90  0086E003  (00402A24, FFFFFFFF, 80430D77, 00000000)
0022FFC0  0040103D  (00000000, 00000000, 7FFDF000, 00000000)
0022FFF0  77E97D08  (00401000, 00000000, 000000C8, 00000100)
End of stack trace (more stack frames may be present)

whatz goin wrong..?
plz someone help.

satish



----- Original Message -----
From: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: <ecos-discuss@sources.redhat.com>; <sid@sources.redhat.com>
Sent: Wednesday, September 18, 2002 9:03 AM
Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator


> Hi,
>          I did the changes manually as per ur mail. and later when i try
to
> run arm-elf-gdb twothreads.x i get the following error:
> localhost:2000 Attempt toconnect timed out with out establishing a
> connection.
> GDB cannot connect to the target board using localhost:2000.
> verify that the board is securly connected and, if necessary,
> modify the port setting with debugger preferences.
>
> how shall i get this error solved.
> plz some one reply.
>
> satish
>
>
> ----- Original Message -----
> From: "Frank Ch. Eigler" <fche@redhat.com>
> To: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>
> Cc: <ecos-discuss@sources.redhat.com>; <sid@sources.redhat.com>
> Sent: Tuesday, September 17, 2002 3:09 AM
> Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator
>
>
> > Hi -
> >
> > On Tue, Sep 17, 2002 at 10:56:13AM -0700, T Satish Kumar wrote:
> > > well, i even tried installin a new version insight-5.2..
> > > and did the same check..but still i m not able to connect to the
target.
> > > what could be the problem..?
> >
> > This problem lies exclusively with gdb/insight.  It has nothing to do
with
> > how you built the simulator or your twothreads.x arm-elf program.  There
> > was a bug in gdb/insight that was likely fixed by this gdb/gdbtk change:
> >
> > 2002-07-31  Keith Seitz  <keiths@redhat.com>
> >
> >         * library/browserwin.itb (_full_funcs_combo): Remove "-modal"
> >         option from tk_messageBox call. It was redhat-local in tk8.0,
> >         but is no longer in tk8.3.
> >         * library/download.itb (download_it): Likewise.
> >         * library/interface.tcl (gdbtk_tcl_query): Likewise.
> >         (show_warning): Likewise.
> >         (set_exe): Likewise.
> >         (set_target): Likewise.
> >         * library/memwin.itb (error_dialog): Likewise.
> >         * library/srcwin.itb (fillFuncCB): Likewise.
> >         * library/util.tcl (tfind_cmd): Likewise.
> >
> > You can either hand-edit the affected gdbtk files to remove this
"-modal"
> > flag, or build a new copy of insight from a more recent gdb snapshot.
> >
> >
> > - FChE
> >
>

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[T Satish Kumar]

Hi,
         I did the changes manually as per ur mail. and later when i try to
run arm-elf-gdb twothreads.x i get the following error:
localhost:2000 Attempt toconnect timed out with out establishing a
connection.
GDB cannot connect to the target board using localhost:2000.
verify that the board is securly connected and, if necessary,
modify the port setting with debugger preferences.

how shall i get this error solved.
plz some one reply.

satish


----- Original Message -----
From: "Frank Ch. Eigler" <fche@redhat.com>
To: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>
Cc: <ecos-discuss@sources.redhat.com>; <sid@sources.redhat.com>
Sent: Tuesday, September 17, 2002 3:09 AM
Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator


> Hi -
>
> On Tue, Sep 17, 2002 at 10:56:13AM -0700, T Satish Kumar wrote:
> > well, i even tried installin a new version insight-5.2..
> > and did the same check..but still i m not able to connect to the target.
> > what could be the problem..?
>
> This problem lies exclusively with gdb/insight.  It has nothing to do with
> how you built the simulator or your twothreads.x arm-elf program.  There
> was a bug in gdb/insight that was likely fixed by this gdb/gdbtk change:
>
> 2002-07-31  Keith Seitz  <keiths@redhat.com>
>
>         * library/browserwin.itb (_full_funcs_combo): Remove "-modal"
>         option from tk_messageBox call. It was redhat-local in tk8.0,
>         but is no longer in tk8.3.
>         * library/download.itb (download_it): Likewise.
>         * library/interface.tcl (gdbtk_tcl_query): Likewise.
>         (show_warning): Likewise.
>         (set_exe): Likewise.
>         (set_target): Likewise.
>         * library/memwin.itb (error_dialog): Likewise.
>         * library/srcwin.itb (fillFuncCB): Likewise.
>         * library/util.tcl (tfind_cmd): Likewise.
>
> You can either hand-edit the affected gdbtk files to remove this "-modal"
> flag, or build a new copy of insight from a more recent gdb snapshot.
>
>
> - FChE
>

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Frank Ch. Eigler]

Hi -

On Tue, Sep 17, 2002 at 10:56:13AM -0700, T Satish Kumar wrote:
> well, i even tried installin a new version insight-5.2..
> and did the same check..but still i m not able to connect to the target.
> what could be the problem..?

This problem lies exclusively with gdb/insight.  It has nothing to do with
how you built the simulator or your twothreads.x arm-elf program.  There
was a bug in gdb/insight that was likely fixed by this gdb/gdbtk change:

2002-07-31  Keith Seitz  <keiths@redhat.com>

        * library/browserwin.itb (_full_funcs_combo): Remove "-modal"
        option from tk_messageBox call. It was redhat-local in tk8.0,
        but is no longer in tk8.3.
        * library/download.itb (download_it): Likewise.
        * library/interface.tcl (gdbtk_tcl_query): Likewise.
        (show_warning): Likewise.
        (set_exe): Likewise.
        (set_target): Likewise.
        * library/memwin.itb (error_dialog): Likewise.
        * library/srcwin.itb (fillFuncCB): Likewise.
        * library/util.tcl (tfind_cmd): Likewise.

You can either hand-edit the affected gdbtk files to remove this "-modal"
flag, or build a new copy of insight from a more recent gdb snapshot.


- FChE

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[T Satish Kumar]

well, i even tried installin a new version insight-5.2..
and did the same check..but still i m not able to connect to the target.
what could be the problem..?

satish

----- Original Message -----
From: "Frank Ch. Eigler" <fche@redhat.com>
To: "T Satish Kumar" <satish@td.idc.lsi.sanyo.co.jp>
Cc: <ecos-discuss@sources.redhat.com>; <sid@sources.redhat.com>
Sent: Monday, September 16, 2002 5:36 PM
Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator


> Hi -
>
> On Tue, Sep 17, 2002 at 09:26:39AM -0700, T Satish Kumar wrote:
> > [...]
> > but my first step still remains unsuccessful..i m not able to connect to
the
> > target.
> > my target settings are as follows:
> > Target:Remote/TCP
> > hostname:localhost
> > port:2000
> > and i have Tcl-Tk 8.3.4 and Insight ver-20020620 installed on my Windows
> > 2000.
> > i m trying all this on cygwin.
>
> I suspect something wrong with your insight build.  How about
> trying plain gdb (as in "gdb -nw FILE", "target remote localhost:2000",
> and so on)?
>
>
> > P.S: i could successfully built the arm-development tools, ecos library
and
> > the sid.
>
> Very good.
>
>
> - FChE
>

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Frank Ch. Eigler]

Hi -

On Tue, Sep 17, 2002 at 09:26:39AM -0700, T Satish Kumar wrote:
> [...]
> but my first step still remains unsuccessful..i m not able to connect to the
> target.
> my target settings are as follows:
> Target:Remote/TCP
> hostname:localhost
> port:2000
> and i have Tcl-Tk 8.3.4 and Insight ver-20020620 installed on my Windows
> 2000.
> i m trying all this on cygwin.

I suspect something wrong with your insight build.  How about
trying plain gdb (as in "gdb -nw FILE", "target remote localhost:2000",
and so on)?


> P.S: i could successfully built the arm-development tools, ecos library and
> the sid.

Very good.


- FChE

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[T Satish Kumar]

this option  "uart1:tty-uart2"stdio" when added to the --board , works fine
and  opens a console window along with the
debugger.
but my first step still remains unsuccessful..i m not able to connect to the
target.
my target settings are as follows:
Target:Remote/TCP
hostname:localhost
port:2000

and i have Tcl-Tk 8.3.4 and Insight ver-20020620 installed on my Windows
2000.
i m trying all this on cygwin.
P.S: i could successfully built the arm-development tools, ecos library and
the sid.


plz someone help me..
satish


----- Original Message -----
From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Tim Drury" <tdrury@siliconmotorsports.com>
Cc: <ecos-discuss@sources.redhat.com>; <sid@sources.redhat.com>
Sent: Monday, September 16, 2002 12:49 PM
Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Frank Ch. Eigler]

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

Hi -

On Mon, Sep 16, 2002 at 01:54:45PM -0600, Gary Thomas wrote:
> [...]
> > The "--board" processing logic allows you to configure the simulated
> > UARTs' outputs without tksm.  [...]
> 
> Can similar results be easily had using a configuration file?

You can intercept the sid configuration file built internally by the
arm-elf-sid script (use "--save-temps" for example) and see the differences
caused by various --board options.


- FChE

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

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Gary Thomas]

On Mon, 2002-09-16 at 13:49, Frank Ch. Eigler wrote:
> Hi -
> 
> On Fri, Sep 13, 2002 at 09:19:09AM -0400, Tim Drury wrote:
> > > Try running without "--tksm".  [...]
> > 
> > One problem with this solution is he won't be able to bring
> > up the UART1 console and see the output of the program.  Or
> > is there another way to see the output?  Redirected to a file
> > would be nice...
> 
> The "--board" processing logic allows you to configure the simulated
> UARTs' outputs without tksm.  Try adding something like
> "uart1:tty-uart2:stdio" to the long --board option.  "uart1:2222"
> connects it to a TCP server socket at port 2222.

Can similar results be easily had using a configuration file?

-- 
------------------------------------------------------------
Gary Thomas                  |
eCosCentric, Ltd.            |  
+1 (970) 229-1963            |  eCos & RedBoot experts
gthomas@ecoscentric.com      |
http://www.ecoscentric.com/  |
------------------------------------------------------------

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Frank Ch. Eigler]

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

Hi -

On Fri, Sep 13, 2002 at 09:19:09AM -0400, Tim Drury wrote:
> > Try running without "--tksm".  [...]
> 
> One problem with this solution is he won't be able to bring
> up the UART1 console and see the output of the program.  Or
> is there another way to see the output?  Redirected to a file
> would be nice...

The "--board" processing logic allows you to configure the simulated
UARTs' outputs without tksm.  Try adding something like
"uart1:tty-uart2:stdio" to the long --board option.  "uart1:2222"
connects it to a TCP server socket at port 2222.


- FChE

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

RE: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Robert Cragie]

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Gary Thomas
> Sent: 13 September 2002 13:33
> To: Satish Kumar
> Cc: 'Robert Cragie '; 'ijsung@csie.nctu.edu.tw ;
> 'ecos-discuss@sources.redhat.com'; 'sid@sources.redhat.com'
> Subject: RE: [ECOS] how to build an eCos library for ARM7tdmi simulator
>
>
> On Fri, 2002-09-13 at 00:16, Satish Kumar wrote:
> >
> > Hi,
> >
> >         i followed the build procedure of sid, as stated in ur mails
> > was able to finish it sucessfully. but i m not able to connect to the
> > target board. i.e initially i tried this command:
> > arm-elf-sid --board=arm7t-normalmap -gdb=2000 -EL --tksm &
> > i got a message stating 'Unknown board arm7t-normalmap'

[RCC] The original document was wrong - I posted an update.

> >
> > later i tried a different command:
> > arm-elf-sid --board=pid7t-normalmap -gdb=2000 -EL --tksm &
> > this time,i got a message stating : [1] 816

[RCC] This is what you would expect.

> > well next when i run the command
> > arm-elf-gdb twothread.x
> > the debugger window opened with the source file displyed in the source
> > window, now i clicked on Run->Connect to target. and i used the same
> > settings as stated:
> > Target: Remote/TCP.
> > Host:localHost.
> > port:2000
> >
> > set breakpoint at 'cyg_user_start'
> > and other breakpoint at the exit.
> >
> > on pressing ok, i get an Error message stating:
> > Error:bad option "-modal" : must be
> -default,-icon,-message,-parent,-title,
> > or -type..

[RCC] Sounds like you may have a Tcl/Tk compatibility issue here. What
version of Tcl/Tk are you using? On what platform? What version of Insight
are you using?

You can always use the console and enter the gdb commands explicitly:

(gdb) target remote localhost:2000
(gdb) load
(gdb) break cyg_user_start
(gdb) cont

> > and i m not able to run the program..plz kindly tell me how to run the
> > sid simulator for arm7tdmi and how to run my application programs once
> > they are compiled using the ecos library built for pid.
> >
>
> Try running without "--tksm".  This only turns on the Tk (GUI)
> configuration tool, which you can do without [at least for the start].

[RCC] This is needed for the UART output with the specified command line,
however you can send the UART output to the console by changing the --board
option in the SID command line to:

--board=pid7t-normalmap-uart1:stdio

If you do this you don't need the --tksm option.

AFAICT (by looking at configrun-sid), other options for where to send the
UART output include gdb, a socket or the serial port on the PC. If you want
the output to a file, I guess the easiest way is to use the stdio option
specified above and redirect stdout, or pipe to tee <file>.

Robert Cragie, Design Engineer
_______________________________________________________________
Jennic Ltd, Furnival Street, Sheffield, S1 4QT,  UK
http://www.jennic.com  Tel: +44 (0) 114 281 2655

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Gary Thomas]

On Fri, 2002-09-13 at 07:19, Tim Drury wrote:
> Gary Thomas wrote:
> > 
> > Try running without "--tksm".  This only turns on the Tk (GUI) 
> > configuration tool, which you can do without [at least for the start].
> > 
> 
> One problem with this solution is he won't be able to bring
> up the UART1 console and see the output of the program.  Or
> is there another way to see the output?  Redirected to a file
> would be nice...

It came out on the console when I tried it.  Have you had other
experiences?

-- 
------------------------------------------------------------
Gary Thomas                  |
eCosCentric, Ltd.            |  
+1 (970) 229-1963            |  eCos & RedBoot experts
gthomas@ecoscentric.com      |
http://www.ecoscentric.com/  |
------------------------------------------------------------

Re: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Tim Drury]

Gary Thomas wrote:
> 
> Try running without "--tksm".  This only turns on the Tk (GUI) 
> configuration tool, which you can do without [at least for the start].
> 

One problem with this solution is he won't be able to bring
up the UART1 console and see the output of the program.  Or
is there another way to see the output?  Redirected to a file
would be nice...

-tim

RE: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Gary Thomas]

On Fri, 2002-09-13 at 00:16, Satish Kumar wrote:
>  
> Hi,
> 
>         i followed the build procedure of sid, as stated in ur mails 
> was able to finish it sucessfully. but i m not able to connect to the
> target board. i.e initially i tried this command:
> arm-elf-sid --board=arm7t-normalmap -gdb=2000 -EL --tksm &
> i got a message stating 'Unknown board arm7t-normalmap'
> 
> later i tried a different command:
> arm-elf-sid --board=pid7t-normalmap -gdb=2000 -EL --tksm &
> this time,i got a message stating : [1] 816
> 
> well next when i run the command
> arm-elf-gdb twothread.x
> the debugger window opened with the source file displyed in the source 
> window, now i clicked on Run->Connect to target. and i used the same
> settings as stated:
> Target: Remote/TCP.
> Host:localHost.
> port:2000
> 
> set breakpoint at 'cyg_user_start'
> and other breakpoint at the exit.
> 
> on pressing ok, i get an Error message stating:
> Error:bad option "-modal" : must be -default,-icon,-message,-parent,-title,
> or -type..
> 
> and i m not able to run the program..plz kindly tell me how to run the 
> sid simulator for arm7tdmi and how to run my application programs once 
> they are compiled using the ecos library built for pid.
> 

Try running without "--tksm".  This only turns on the Tk (GUI) 
configuration tool, which you can do without [at least for the start].

Also, there was really no reason to quote Robert's *entire* HTML
document - it just wastes bandwidth.

-- 
------------------------------------------------------------
Gary Thomas                  |
eCosCentric, Ltd.            |  
+1 (970) 229-1963            |  eCos & RedBoot experts
gthomas@ecoscentric.com      |
http://www.ecoscentric.com/  |
------------------------------------------------------------

RE: [ECOS] how to build an eCos library for ARM7tdmi simulator

[Satish Kumar]

 
Hi,

        i followed the build procedure of sid, as stated in ur mails 
was able to finish it sucessfully. but i m not able to connect to the
target board. i.e initially i tried this command:
arm-elf-sid --board=arm7t-normalmap -gdb=2000 -EL --tksm &
i got a message stating 'Unknown board arm7t-normalmap'

later i tried a different command:
arm-elf-sid --board=pid7t-normalmap -gdb=2000 -EL --tksm &
this time,i got a message stating : [1] 816

well next when i run the command
arm-elf-gdb twothread.x
the debugger window opened with the source file displyed in the source 
window, now i clicked on Run->Connect to target. and i used the same
settings as stated:
Target: Remote/TCP.
Host:localHost.
port:2000

set breakpoint at 'cyg_user_start'
and other breakpoint at the exit.

on pressing ok, i get an Error message stating:
Error:bad option "-modal" : must be -default,-icon,-message,-parent,-title,
or -type..

and i m not able to run the program..plz kindly tell me how to run the 
sid simulator for arm7tdmi and how to run my application programs once 
they are compiled using the ecos library built for pid.


satish
 


-----Original Message-----
From: Robert Cragie
To: satishkumar@sanyo.co.in; ijsung@csie.nctu.edu.tw
Sent: 9/4/02 2:14 PM
Subject: FW: [ECOS] how to build an eCos library for ARM7tdmi simulator

Just in case you didn't get it from the mailing list...

-----Original Message-----
From: Robert Cragie [mailto:rcc@jennic.com]
Sent: 03 September 2002 16:07
To: ecos-discuss@sources.redhat.com
Subject: FW: [ECOS] how to build an eCos library for ARM7tdmi simulator


Further to my original message, I have now run through it step-by-step
doing
a clean install. There were some issues with the original text, so I
have
updated it. I am in the process of doing an SGML version.

Robert Cragie, Design Engineer
_______________________________________________________________
Jennic Ltd, Furnival Street, Sheffield, S1 4QT,  UK
http://www.jennic.com  Tel: +44 (0) 114 281 2655

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Robert Cragie
Sent: 03 September 2002 09:09
To: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] how to build an eCos library for ARM7tdmi simulator


Seeing as there is some interest in this, I am attaching the draft of my
'mini-HOWTO' on how I got it going. Note this is in draft state, and I
have
not followed it all step-by-step; the SID bits are from memory. I will
have
a go following step-by-step when I get a spare few minutes. I would also
be
interested to know how Cygwin users get on.

[snip]

<!DOCTYPE HTML PUBLIC "-//w3c//dtd html 4.0 transitional//en">

<HTML>

  <HEAD>
    <TITLE>eCos and SID on ARM PID target HOWTO</TITLE>
  </HEAD>

  <BODY>

    <H1>eCos and SID on ARM PID target HOWTO</H1>

    <P>This document describes howto set up the environments for getting
eCos
      and a target application to work with SID. By the end of this
tutorial,
      you should be able to:</P>
    <OL>
      <LI>Build a simple, multi-threaded application linked with
eCos.</LI>
      <LI>Build the SID simulator infrastucture to support a simulated
ARM
PID
        target.</LI>
      <LI>Debug and run the application using GDB (Insight) connected to
a
        simulated ARM PID target.</LI>
    </OL>

    <H2>What is eCos?</H2>

    <P>eCos is an embedded, configurable multi-threaded operating system
which
      can target many systems and CPUs.</P>

    <P>For more details see <A
HREF="http://sources.redhat.com/ecos">Redhat's
        eCos page</A>.</P>

    <H2>What is SID?</H2>

    <P>SID is a simulation environment which allows a number of
      software-defined components to be built together to provide a
target
which
      simulates a real hardware target.</P>

    <P>For more details see <A
HREF="http://sources.redhat.com/sid">Redhat's
        SID page</A>.</P>

    <H2>Assumptions</H2>

    <P>I am assuming use of the following environment:</P>
    <UL>
      <LI>Linux.</LI>
      <LI><TT>bash</TT> is used as the command shell.</LI>
      <LI>The user's user ID is 'user'.</LI>
      <LI>All created directories are based on the user's root directory
        (reached using '<TT>cd ~</TT>', or '<TT>cd
/home/user</TT>').</LI>
      <LI>Superuser access is possible.</LI>
      <LI>Tcl/Tk is installed (8.0 or later)</LI>
    </UL>

    <P>It is undoubtedly possible to get it all working using
      <A HREF="http://sources.redhat.com/cygwin">cygwin</A> on
Windows(tm),
but
      I have not done this.</P>

    <P>The following syntax indicates a command run as
<EM>user</EM>:</P>

    <P><TT>$ &lt;command&gt;</TT></P>

    <P>The following syntax indicates a command run as a superuser:</P>

    <P><TT># &lt;command&gt;</TT></P>

    <H1>Installing eCos</H1>

    <H2>Getting eCos source</H2>

    <P>I would strongly recommend getting the latest CVS version of
eCos,
and
      not to attempt to use version 1.3.1, which still seems to be being
used
      even though it is very old. The following contains extracts from
Redhat's
      <A HREF="http://sources.redhat.com/ecos/anoncvs.html">eCos
anonymous
CVS
        page</A>.</P>

    <P>Type the following command to login to the CVS server:</P>

    <P><TT>$ cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos
login</TT></P>

    <P>You will be prompted for a password which is <EM>anoncvs</EM>.
You
only
      need to perform this login the first time you access the eCos CVS
      repository. The password is saved in the file <TT>.cvspass</TT> in
your
      home directory for use in subsequent sessions.</P>

    <P>It is recommended that you use different directory trees for the
      anonymous CVS sources and for full releases of eCos. Create a new
      directory for the check out and change to that directory:</P>

    <P><TT>$ mkdir ~/ecos-cvs</TT></P>

    <P><TT>$ cd ~/ecos-cvs</TT></P>

    <P>Now type:</P>

    <P><TT>$ cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/ecos co -P
ecos</TT>
    </P>

    <P>This command should initiate a connection to the CVS server and
check
      out the latest version of eCos, including TCP/IP networking stack
and
      SNMP. It may take quite a while.</P>

    <P>If you are unable to use CVS, David Airlie of Parthus
Technologies
plc.
      <A HREF="ftp://ftp.skynet.ie/cvs">places complete CVS snapshots
here</A>;
      obtain the latest one of these and unzip it into the
<TT>ecos-cvs</TT>
      directory.</P>

    <H2>Getting eCos Configuration Tool Version 2</H2>

    <P>I would recommend using the graphical Configuration Tool as it is
      generally easier to use than trying to decipher the relatively
terse
      configuration files to change options. The following contains
extracts
      from Redhat's <A
HREF="http://sources.redhat.com/ecos/ct2.html">eCos
        Configuration Tool Version 2 page</A>:</P>

    <P>Download
      <A
HREF="ftp://sources.redhat.com/pub/ecos/ct2/configtool-2.11-i386.tar.gz"
>con
figtool-2.11-i386.tar.gz
        (3.1Mb)</A> or
      <A
HREF="ftp://sources.redhat.com/pub/ecos/ct2/configtool-2.11-i386.tar.bz2
">co
nfigtool-2.11-i386.tar.bz2
        (2.8Mb)</A></P>

    <P>Login as superuser and unarchive the tar file into a suitable
directory.
      I am assuming here that <TT>/opt/ecos/configtool</TT> is the
required
      destination directory for all files (note: <TT>configtool</TT>
does
not
      have to be installed by superuser, but it is preferable):</P>

    <P><TT>$ su</TT></P>

    <P><TT># mkdir -p /opt/ecos/configtool/bin</TT></P>

    <P><TT># cd /opt/ecos/configtool/bin</TT></P>

    <P><TT># tar xvfz /home/user/configtool-2.11-i386.tar.gz</TT> </P>

    <P>(or, if you dowloaded the bz2 version:)</P>

    <P><TT># bunzip2 -c /home/user/configtool-2.11-i386.tar.bz2 | tar
xvf -</TT></P>

    <P>As there is only one executable, it is probably easiest to create
a
      symbolic link to it:</P>

    <P><TT># ln -s /opt/ecos/configtool/configtool-2.11/bin/configtool
      /usr/bin/configtool</TT></P>

    <P>Alternatively, make sure that
<TT>/opt/ecos/configtool/configtool-2.11/bin</TT>
      is added to your PATH environment variable.</P>

    <P>The following files will be extracted to the installation
directory:</P>

    <P><TT>configtool, ecoslogo.png, rhlogo.png, about.htm, README.txt,
      license.txt, ecosplatforms.tar.gz, manual/</TT></P>

    <P>Optionally, untar the contents of ecosplatforms.tar.gz into your
home
      directory, where it will create a directory called .eCosPlatforms.
The
      information in these files isn't yet used by the Configuration
Tool,
but
      will keep the tool from generating some warnings.</P>

    <P>The executable is statically linked to the wxWindows library, but
does
      require the GTK+ 1.2, GDK 1.2 and TCL 8.x libraries to be
installed.
</P>

    <P><STRONG>Note: On SuSE Linux, there needs to be an additional
symbolic
      link to the Tcl library. Do the following:</STRONG></P>

    <P><TT># cd /usr/lib</TT></P>

    <P><TT># ln -s libtcl8.3.so libtcl.so</TT></P>

    <H2>Getting <TT>arm-elf</TT> tools</H2>

    <P>As this is a complex procedure, you need to follow the directions
      <A
HREF="http://sources.redhat.com/ecos/tools/linux-arm-elf.html">here</A>
      exactly. Once you have done this, you will have all the required
tools
      needed to build for an <TT>arm-elf</TT> target (note this does not
      include the thumb target).</P>

    <P><STRONG>Note that the link to Insight 5.0 is broken. However, I
have
      downloaded and installed
      <A
HREF="ftp://sources.redhat.com/pub/gdb/releases/insight-5.2.1.tar.bz2">I
nsig
ht
        5.2.1 (insight-5.2.1.tar.bz2)</A> instead and see that it has
some
      worthwhile bugfixes from 5.0.</STRONG></P>

    <H2>Building eCos environment for PID target</H2>

    <H3>Set the repository</H3>

    <P>Assuming you have checked out the latest version to a directory
called
      <TT>ecos-cvs</TT>, you need to set the following environment
variable
for
      the Configuration Tool to pick up where all the source is (known
as
the
      <EM>repository</EM>, not to be confused with the CVS
repository):</P>

    <P><TT>$ ECOS_REPOSITORY=/home/user/ecos-cvs/ecos/packages; export
      ECOS_REPOSITORY</TT></P>

    <P>This line should also be added to your shell initialisation
script
(<TT>.bashrc</TT>,
      or <TT>.bash_profile</TT>)</P>

    <H3>Create the <TT>ecos.ecc</TT> file</H3>

    <P>Create a new directory in your home directory and change to
it:</P>

    <P><TT>$ mkdir -p ~/ecos-targets/pid-current</TT></P>

    <P><TT>$ cd ~/ecos-targets/pid-current</TT></P>

    <H3>Run the configtool</H3>

    <P>Enter the following</P>

    <P><TT>$ configtool</TT></P>

    <P>You should see the Configuration Tool start.</P>

    <H3>Create default settings for the PID target</H3>

    <P>Select the <EM>Build-&gt;Templates...</EM> menu item. In the
<EM>Hardware</EM>
      combo box, select <EM>ARM development board (PID)</EM>, and press
'OK'.</P>

    <P>Change the following options:</P>

    <P><EM>eCos HAL-&gt;ROM Monitor support-&gt;Work with a ROM
Monitor</EM>
      to disabled (unchecked)</P>

    <P><EM>eCos HAL-&gt;Platform-independent HAL options-&gt;Route
diagnostic
      output to debug channel</EM> to disabled (unchecked)</P>

    <P>Now save the file as <TT>ecos.ecc</TT> using the
<EM>File-&gt;Save
      as...</EM> menu item</P>

    <H3>Build the tree</H3>

    <P>To build the tree for the PID development board, select the
<EM>Build-&gt;Generate
      Build Tree</EM> menu item. You will see three directories:
<TT>ecos_build</TT>,
      <TT>ecos_install</TT> and <TT>ecos_mlt</TT></P>

    <H3>Make the libraries</H3>

    <P><TT>$ cd ecos_build</TT></P>

    <P><TT>$ make</TT></P>

    <P>This will place all the required files for an application in
<TT>ecos_install</TT>.
    </P>

    <H3>Create the 'two threads' example</H3>

    <P><TT>$ cd ../ecos_install</TT></P>

    <P><TT>$ mkdir examples</TT></P>

    <P><TT>$ cd examples</TT></P>

    <P><A
HREF="http://sources.redhat.com/ecos/docs-latest/tutorials/arm/ecos-tuto
rial
.13.html#pgfId=1982019">Get
        the two threads source code from here</A>. Copy it into a file
called
      <TT>twothreads.c</TT>.</P>

    <P>Build this as follows</P>

    <P><TT>$ arm-elf-gcc -g -I../include twothreads.c -L../lib -o
twothreads.x
      -Ttarget.ld -nostdlib</TT></P>

    <P>There should be no errors. You now have the executable
(<TT>twothreads.x</TT>)
      which you can download, debug and run on the SID target using
Insight,
or
      gdb.</P>

    <H1>Installing SID</H1>

    <H2>Getting SID source</H2>

    <P><STRONG></STRONG>The following contains extracts from Redhat's
      <A HREF="http://sources.redhat.com/sid">SID page</A>.</P>

    <P>Type the following command to login to the CVS server:</P>

    <P><TT>$ cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/src
login</TT></P>

    <P>You will be prompted for a password which is <EM>anoncvs</EM>.
You
only
      need to perform this login the first time you access the SID CVS
      repository. The password is saved in the file <TT>.cvspass</TT> in
your
      home directory for use in subsequent sessions.</P>

    <P>It is recommended that you use different directory trees for the
      anonymous CVS sources and for full releases of SID. Create a new
directory
      for the check out and change to that directory:</P>

    <P><TT>$ mkdir ~/sid-cvs</TT></P>

    <P><TT>$ cd ~/sid-cvs</TT></P>

    <P>Now type:</P>

    <P><TT>$ cvs -z 9 -d :pserver:anoncvs@sources.redhat.com:/cvs/src co
sid</TT>
    </P>

    <P>This command should initiate a connection to the CVS server and
check
      out the latest version of SID. It may take quite a while.</P>

    <P>If you are unable to use CVS, automated CVS snapshots are
available
      <A HREF="ftp://sources.redhat.com/pub/sid/snapshots">here</A>;
obtain
the
      latest one of these and unzip it into the <TT>sid-cvs</TT>
directory.</P>

    <H2>Building SID</H2>

    <P>Having checked out the source, you should see a single
<TT>src</TT>
      subdirectory in the <TT>sid-cvs</TT> directory. Create a
<TT>build</TT>
      directory alongside this:</P>

    <P><TT>$ mkdir build</TT></P>

    <P><TT>$ cd build</TT></P>

    <P>Login as superuser and run <TT>configure</TT> to produce the
build
      tree. I am assuming here that <TT>/opt/sid</TT> is the required
      destination directory for all files:</P>

    <P><TT>$ su</TT></P>

    <P><TT># ../src/configure --prefix=/opt/sid --exec-prefix=/opt/sid
2&gt;&amp;1
      | tee configure.out</TT></P>

    <P>You will need the additional
      <A
HREF="http://sources.redhat.com/ml/sid/2002-q3/msg00036.html">patch
        submitted by Robert Cragie on 03-Sep-02</A>:</P>

    <P><TT># cd ~/sid-cvs/src/cgen/cpu</TT></P>

    <P><TT># patch -p0 &lt; arm7.cpu.patch</TT></P>

    <P><TT># cd ~/sid-cvs/build/sid/component/cgen-cpu/arm7t</TT></P>

    <P><TT># make cgen-all</TT></P>

    <P>Now make all the files and install them:</P>

    <P><TT># cd ~/sid-cvs/build</TT></P>

    <P><TT># make all install</TT></P>

    <P>Note that this may take a <EM>very</EM> long time (hours).</P>

    <P>Add the executable directory to the path:</P>

    <P><TT>$ export PATH=/opt/sid/bin:$PATH</TT></P>

    <P>This line should also be added to your shell initialisation
script
(<TT>.bashrc</TT>,
      or <TT>.bash_profile</TT>)</P>

    <H1>Running a sample session </H1>

    <P>Change back to where the twothreads executable is:</P>

    <P><TT>$ cd
~/ecos-targets/pid-current/ecos_install/examples</TT></P>

    <P>Run SID with the following options:</P>

    <P><TT>$ arm-elf-sid --board=pid7t-normalmap --gdb=2000 -EL --tksm
&amp;</TT></P>

    <P>What this actually does is run a script file called
<TT>arm-elf-sid</TT>.
      This in turn runs a more complex Perl script called
<TT>configrun-sid</TT>,
      which builds the complex configuration file needed for SID on the
fly,
and
      then runs it.</P>
    <UL>
      <LI>The <TT>--board=pid7t</TT> option is a <TT>configrun-sid</TT>
        option which specifies that the configuration file for the PID7T
target
        should be constructed. The additional <TT>-normalmap</TT> option
        ensures that the remapping operations done at startup by eCos do
not
        affect the board.</LI>
      <LI>The <TT>--gdb=2000</TT> option is also a
<TT>configrun-sid</TT>
        option which specifies that the configuration file should also
include a
        stub to allow GDB connection to the PID7T target via TCP/IP
using
port
        2000.</LI>
      <LI>The -EL option specifies little-endian mode</LI>
      <LI>The <TT>--tksm</TT> option is also a <TT>configrun-sid</TT>
option
        which specifies that the configuration file should also include
an
        experimental GUI interface which can show the 'innards' of the
target.
        This is needed to see the output from the UART.</LI>
      <LI><TT>&amp;</TT> simply runs it as a background task.</LI>
    </UL>

    <P>Select the experimental GUI window titled 'System Monitor' and
      left-click and hold on 'uart1' in the left hand column. Select
'GUIs'
and
      then 'tk tty'. You should see an empty window called
'hw-uart-ns16550
      uart1' come up.</P>

    <P>Run GDB (I am assuming you are using Insight):</P>

    <P><TT>$ arm-elf-gdb twothreads.x</TT></P>

    <P>Connect to the target by selecting the <EM>Run-&gt;Connect to
target</EM>
      menu item. Initially, you will get a dialog box; select the
following
      options in the combo boxes on the left hand side:</P>
    <TABLE WIDTH="50%" BORDER="1">
      <TR>
        <TD WIDTH="80"><EM>Target</EM></TD>
        <TD WIDTH="129">Remote/TCP</TD>
      </TR>
      <TR>
        <TD WIDTH="80"><EM>Hostname</EM></TD>
        <TD WIDTH="129">localhost</TD>
      </TR>
      <TR>
        <TD WIDTH="80"><EM>Port</EM></TD>
        <TD WIDTH="129">2000</TD>
      </TR>
    </TABLE>

    <P>Enable (check) the <EM>Set breakpoint at</EM> checkbox, and enter
      'cyg_user_start' in the edit box to the right.</P>

    <P>Disable (uncheck) the <EM>Display download Dialog</EM>
checkbox.</P>

    <P>Click on OK. You should see a dialog saying 'Successfully
connected';
      press OK on this dialog to dismiss it. Note that on Insight 5.2.1
these
      settings are remembered on further connections to the target.</P>

    <P>Download the code to the target by selecting the
<EM>Run-&gt;Download</EM>
      menu item.You should see a blue bar in the status bar showing the
download
      progress.</P>

    <P>Run the code by selecting the <EM>Run-&gt;Run</EM> menu item. You
      should see the code run up to the breakpoint specified at
      'cyg_user_start'.</P>

    <P>Continue the execution by selecting the
<EM>Control-&gt;Continue</EM>
      menu item. You will see it hit another breakpoint at the end of
'main',
      and another at 'exit'; ignore these and continue the execution
further
by
      selecting the <EM>Control-&gt;Continue</EM> menu item in each
case.</P>

    <P>Select the 'hw-uart-ns16550 uart1' window. You should already see
the
      following text:</P>

    <P><TT>Entering twothreads' cyg_user_start() function<BR>
       Beginning execution, thread data is 0<BR>
       Beginning execution, thread data is 1</TT></P>

    <P>Wait patiently. After a while, you should see something like the
      following:</P>

    <P><TT>Thread 0: and now a delay of 239 clock ticks<BR>
       Thread 1: and now a delay of 230 clock ticks</TT></P>

    <P>You are now running a fully multi-thread application using eCos
running
      on a simulated real target board (i.e. one which actually exists
in
real
      life).</P>

    <H1>Finishing the sample session </H1>

    <P>To finish, simply exit GDB as usual, and kill SID by typing:</P>

    <P><TT>$ killall -9 sid</TT></P>

    <H1>Further issues</H1>

    <P>The main problem with the simulation is that the timer tick seems
to
be
      running much slower than it would do in real life. This needs to
be
looked
      at. If the delays are reduced in <TT>twothreads.c</TT> then the
above
      will run quicker.</P>

    <P>SID is a complex package, and modifying it for other targets will
      require a very good understanding of how it all works and fits
together.
      It may also require additional components to be written. This is
not a
      trivial task.</P>
  </BODY>
</HTML>