From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17588 invoked by alias); 23 Nov 2001 12:30:51 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 17491 invoked from network); 23 Nov 2001 12:30:39 -0000 Date: Wed, 14 Nov 2001 00:14:00 -0000 From: "Frank Ch. Eigler" To: Mathieu Lacage Cc: sid@sources.redhat.com Subject: Re: running eCos under sid Message-ID: <20011123073029.A9819@redhat.com> References: <1006507910.9301.40.camel@mathieu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1006507910.9301.40.camel@mathieu>; from mathieu_lacage@realmagic.fr on Fri, Nov 23, 2001 at 10:31:45AM +0100 X-SW-Source: 2001-q4/txt/msg00025.txt.bz2 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1814 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... :=20 : 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 :=20 : 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=3D0x8048 : [...] 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=3Dpid7t" 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 --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 232 -----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----- --ew6BAiZeqk4r7MaW-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Frank Ch. Eigler" To: Mathieu Lacage Cc: sid@sources.redhat.com Subject: Re: running eCos under sid Date: Fri, 23 Nov 2001 04:30:00 -0000 Message-ID: <20011123073029.A9819@redhat.com> References: <1006507910.9301.40.camel@mathieu> X-SW-Source: 2001-q4/msg00042.html Message-ID: <20011123043000.Krio86dpe__5aWvEeZZCK-Cj_TmU_gL4Qw2wGxnaIi0@z> 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-----