[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [dsdp-tm-dev] WR Boardfile Descriptions
|
Thanks for the pointer, Kang.
Does anybody on this list have an idea how this relates
to SPIRIT and the hardware descriptions we have at
Wind River (boardfiles) or ATI/Mentor?
Could anybody have a look at it so we can discuss it in Toronto?
Thanks,
Martin
--
Martin Oberhuber - WindRiver, Austria
+43(662)457915-85
> -----Original Message-----
> From: dsdp-tm-dev-bounces@xxxxxxxxxxx
> [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of kang shuo
> Sent: Tuesday, February 14, 2006 3:00 AM
> To: Target Management developer discussions
> Subject: Re: [dsdp-tm-dev] WR Boardfile Descriptions
>
> I guess there is a open source project about simulator we can
> refer to.
> SkyEye (http://www.skyeye.org) , is a mutil-architecure simulator that
> can run linux. It has a config file that maybe meet the definition of
> various embedded hadrwares. like the following:
>
> cpu: arm720t
> mach: ep7312
> mem_bank: map=M, type=RW, addr=0x00000000, size=0x00400000
> mem_bank: map=I, type=RW, addr=0x80000000, size=0x00010000
> mem_bank: map=M, type=RW, addr=0xc0000000, size=0x00200000
> mem_bank: map=M, type=RW, addr=0xc0200000, size=0x00600000,
> file=./initrd_old.img
> mem_bank: map=M, type=RW, addr=0xc0800000, size=0x00800000
> net: type=rtl8019, mac=0:4:3:2:1:f, ethmod=tuntap, hostip=10.0.0.1
> lcd:type=ep7312,mod=gtk
>
>
>
>
> On 2/8/06, Spear, Aaron <aaron_spear@xxxxxxxxxx> wrote:
> > Martin et al,
> >
> > A while back you posted this, and I would like to pick the
> discussion
> > back up. Is this a topic that others would like to discuss
> at the TM
> > meeting in Toronto? I have had the intention since you originally
> > posted of contributing documentation and some samples of the target
> > definition files we use as food for thought as well. I will try and
> > post them in the next week or sp. I have personally spent many mind
> > numbing hours transcribing data sheets that someone at the
> semi's spent
> > many mind numbing hours creating, and would really like to
> see something
> > happen. (anything! please!)
> >
> > Are there any hardware folks on this thread that can speak to the
> > existence of relevant standards in the EDA world? I am
> sure they have
> > standards for specifying to the N'th degree what sorts of access and
> > timing restrictions there are for a memory mapped peripheral for
> > example, but are there "system level" hardware descriptions
> that would
> > could fit the needs of debugger vendors? (or could be extended)
> >
> > Information such as:
> > -cores on a target, scan chain id's etc
> > -native registers in the core (access restrictions, sizes, processor
> > modes that they are visible in, etc)
> > -address spaces
> > -memory maps for those address spaces (access restrictions on given
> > regions, e.g. flash versus RAM)
> > -memory mapped peripherals (location in memory space, registers it
> > contains)
> > etc
> >
> > regards,
> > Aaron
> >
> > --
> > Aaron Spear
> > Debug Tools Architect
> > Accelerated Technology a Mentor Graphics Division
> > aaron_spear@xxxxxxxxxx
> > 303-679-8457
> >
> >
> > -----Original Message-----
> > From: dsdp-tm-dev-bounces@xxxxxxxxxxx
> > [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of
> Oberhuber, Martin
> > Sent: Monday, December 19, 2005 9:20 AM
> > To: Target Management developer discussions
> > Subject: [dsdp-tm-dev] WR Boardfile Descriptions
> >
> > Hello,
> >
> > In the TM session of the DSDP meeting in Chicago, we came to a point
> > where we noticed that TM wants to provide a common platform for
> > describing the targets (hardware) we are working on.
> >
> > Currently, every vendor is doing their own hardware descriptions,
> > typically by XML or some other files... they all have to
> read the specs
> > from silicon vendors, and create their own file formats.
> > That's a lot of wasted work.
> >
> > We are hoping that at some point it might be possible to create a
> > uniform "standard" file format, or at least provide some converters
> > between various file formats. Ideally, then silicon vendors could
> > provide their specifications in the uniform format (or something
> > convertible). Silicon vendors could become the "experts"
> for hardware
> > descriptions, users could get patches/updates directly from them...
> > lifting off a lot of work from tool vendors like us.
> >
> > As a first step, I'm attching a sample and description of
> the board file
> > specification that Wind River is currently using.
> >
> > I'd hope that other companies could follow and put their samples or
> > descriptions to the table, such that we can get a feeling of what
> > features are required from a "unified" format, and find out
> future steps
> > to take.
> >
> > Thanks,
> > Martin
> > --
> >
> ---------------------------------/()\-------------------------
> ----------
> > DI Martin Oberhuber
> mailto:martin.oberhuber@xxxxxxxxxxxxx
> > Member of Technical Staff Phone (UTC +1h): +43
> (662) 457915-85
> > Wind River Systems (Salzburg) GmbH Fax: +43
> (662) 457915-6
> > Jakob-Haringer-Str.8, A-5020 Salzburg, Austria
> http://www.windriver.com
> > ----------------------- How Smart Things Think
> -------------------------
> >
> > _______________________________________________
> > dsdp-tm-dev mailing list
> > dsdp-tm-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
> >
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
>
