From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27439 invoked by alias); 23 Nov 2001 12:53:43 -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 27421 invoked from network); 23 Nov 2001 12:53:41 -0000 Subject: Re: running eCos under sid From: Mathieu Lacage To: "Frank Ch. Eigler" Cc: sid@sources.redhat.com In-Reply-To: <20011123073029.A9819@redhat.com> References: <1006507910.9301.40.camel@mathieu> <20011123073029.A9819@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution/0.99.2 (Preview Release) Date: Wed, 14 Nov 2001 03:43:00 -0000 Message-Id: <1006520035.9233.48.camel@mathieu> Mime-Version: 1.0 X-SW-Source: 2001-q4/txt/msg00026.txt.bz2 le ven 23-11-2001 =E0 13:30, Frank Ch. Eigler a =E9crit : > 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=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. 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 ? >=20 > 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...=20 /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 >=20 > - FChE --=20 Mathieu Lacage #p: +33 1 69 19 61 97 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Lacage To: "Frank Ch. Eigler" Cc: sid@sources.redhat.com Subject: Re: running eCos under sid Date: Fri, 23 Nov 2001 04:53:00 -0000 Message-ID: <1006520035.9233.48.camel@mathieu> References: <1006507910.9301.40.camel@mathieu> <20011123073029.A9819@redhat.com> X-SW-Source: 2001-q4/msg00043.html Message-ID: <20011123045300.-q3RrdxOyWx5anmxhSa2nM75mhwDDKgTB4WGRozfj6k@z> 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 #p: +33 1 69 19 61 97