Xref: utzoo comp.sys.mips:1730 comp.sys.dec:6015
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.sys.mips,comp.sys.dec
Subject: Re: risc development environment
Message-ID: <22443@cbmvax.commodore.com>
Date: 14 Jun 91 06:07:13 GMT
References: <25406@well.sf.ca.us>
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Distribution: comp
Organization: Commodore, West Chester, PA
Lines: 27

In article <25406@well.sf.ca.us> gregs@well.sf.ca.us (Greg Strockbine) writes:
> 
> We are just gearing up to do development using an IDT risc chip.  Our
> target is a laser controller board.  We just bought a DEC 5500 machine
> but we there seems to be some pieces missing, the list file does not
> supply addresses, there is no utility to convert to S record format.
> IDT thinks we should buy a mips workstation, they say all the tools are
> there, they also say almost no one is developing for a risc target
> system using a DEC risc machine.  Did we buy the right machine?

You may have added a bit of extra work to your project, since there is
no explicit Ultrix support for generating standalone, while MIPS may
provide a package intended to support MIPS chip level software and
hardware development.

On the other hand, it is usually not a very large task to take a linked
object file and put out s-records or some similar format.

> Also the DEC machine is little endian but everyone recommends our target
> system be big endian.  Why?

Mostly a question of going along with the crowd. 

-- 
George Robbins - now working for,     uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing:   domain: grr@cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)