[ECOS] Axiom CMD561 (was - RE: [ECOS] MPC 555/565 Status)

[Ian Gilmour <ian dot gilmour at ffei dot co dot uk>]

OK my Axiom CMD561 just turned up. And no-one replied to my initial email -
so I'm assuming I need to perform the port myself.

Looking at the CME555 description it looks as though I'm going to have to
massage the existing CME555 port to get it working on a CMD561 (For one, the
CMD561 doesn't have the internal flash, which the CME555 port appears to
use).

As I don't yet have a BDM debugger any tips on how to go about getting
started with this in the mean time would be much appreciated?

I'm still slightly confused as to how you go about getting going with a port
to a new target board.

Once I've got the appropriate cmd561 directories setup and populated in my
ECOS_REPOSITORY and I've updated ecos.db, should,

   ecosconfig new cmd561 redboot 
   ecosconfig tree
   make

give me a simple ROM-based monitor? 
Do I need to massage the ecos.ecc file before generating the tree and
performing the make? 
Or should I be specifying some other (more basic) configuration initially?

i.e. What's the minimum config that gives my something out on the serial
port to prove it's working?

Host M/C - Linux (so I've got configtool if required).
PS. Anyone else finding configtool crashes fairly regularily? 
Would having access to the MS-Windows GUI tool make things simpler?

Thanks in advance for any tips.


cheers,


Ian 

> -----Original Message-----
> From: Ian Gilmour 
> Sent: Friday, December 06, 2002 9:43 AM
> To: 'Bob Koninckx'; Henning Baldersheim
> Cc: ecos-discuss@sources.redhat.com
> Subject: RE: [ECOS] MPC 555/565 Status
> 
> 
> 
> Hi,
> 
> On a similar thread. 
> 
> Is anyone working on an ECOS port to the Axiom CMD561 board?
> 
> Anyone know if the CME555 port will just run - as is?
> 
> Or what needs to be changed, if not?
> 
> 
> cheers,
> 
> 
> Ian
> 
> 
> > -----Original Message-----
> > From: Bob Koninckx [mailto:bob.koninckx@mech.kuleuven.ac.be]
> > Sent: Friday, December 06, 2002 9:11 AM
> > To: Henning Baldersheim
> > Cc: ecos-discuss@sources.redhat.com
> > Subject: Re: [ECOS] MPC 555/565 Status
> > 
> > 
> > On Thu, 2002-12-05 at 16:22, Henning Baldersheim wrote:
> > > Hi
> > > 
> > > I have been looking around for OS with MPC 555/565 support. 
> > ECOS seem to 
> > > have the basic stuff. I have downloaded and got it up and 
> > running on my 
> > > Phytec MPC555 card. So far so good. However I have a couple 
> > of questions.
> > > 
> > > 1 - I find an ec555extras.epk file, but I get some errors. 
> > > (xxx/ecos/packages/pkgadd.txt : missing) and 
> > > (io/ioencoder/v0_1/include/encoderconfig_keys.h : 
> > permission denied). How 
> > 
> > I do not know how to solve that. Never used the epk as I have the
> > original code myself.
> > 
> > > do I solve that ? Is this soon to be added to cvs ? Is it 
> > possible to 
> > > ignore the errors so I can have a look at the code.
> > 
> > I do not think it will ever appear into cvs. If you do not manage to
> > have a look at the code, I can send you a copy of what is missing.
> > Basically it is a device driver for reading out incremental emcoders
> > using the TPU devices.
> > 
> > > 2 - I see that both the ec555 and cme555 boards have 
> > different serial 
> > > drivers. Is that necessary ? Should there not be a 555/565 
> > common package 
> > > containing all those drivers.
> > 
> > That's something you could argue about. You could say that the
> > integrated peripherals of the 555/565 processors are part of the
> > processor architecture. You could also say that the cme555 and ec555
> > boards use the same serial devices.
> > 
> > I am more in favor of this last approach since motorola 
> > integrates lots
> > of their peripherals into other processors as well.
> > 
> > Maybe the cleanest way to go would be to split the driver in 
> > a "device"
> > part and a "board part". Look at how the cs8900a ethernet controller
> > (the device part) is used on multiple boards as a example.
> > 
> > I suppose Gary or Jifl can comment on this as well ?
> > 
> > 
> > > 3 - I want to make a package for the phytec 555 and 565 
> > cards. Should they 
> > > be organized the same way as the ec and cme package ? I 
> > would hope common 
> > > stuff could go in a common place.
> > 
> > See my comment above. The cs8900a ethernet driver is probably 
> > an example
> > of the cleanest approach.
> > 
> > > 4 - From the previous mails I see that there might be a 
> > patch coming soon. 
> > > What is contained and when will it be available ?
> > 
> > That patch is ready. It does not change anything major, 
> just some bug
> > fixes for serial debugging (ctrl-c stuff) and some documentation. It
> > however also contains redboot images for the ec555 and cme555 
> > boards, so
> > it became an email with a "big" attachment. That's the reason 
> > why it did
> > not appear on the patches-list. The eCos maintainers got it 
> though. If
> > you want, I can send you a copy as well. I can not guarantee that it
> > will ever make it into the cvs tree though.
> > 
> > 
> > I'll post the patch without the images to the patches list this WE.
> > 
> > > 
> > > Henning 
> > 
> > Bob
> > 
> > -- 
> > 
> ----------------------------------------------------------------------
> > ir. Bob Koninckx
> > Katholieke Universiteit Leuven       
> > Division Production Engineering,                   tel.  
> +32 16 322535
> > Machine Design and Automation                      fax.  
> +32 16 322987
> > Celestijnenlaan 300B                  
> bob.koninckx@mech.kuleuven.ac.be
> > B-3001 Leuven Belgium               
> http://www.mech.kuleuven.ac.be/pma
> > 
> ----------------------------------------------------------------------
> > 
> > 
> > -- 
> > Before posting, please read the FAQ: 
> > http://sources.redhat.com/fom/ecos
> > and search the list archive: 
> http://sources.redhat.com/ml/ecos-discuss
> > 
> 

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss