gnupic@linuxhacker.org

gnupic@linuxhacker.org


Subject: Re: Microchip dev files
From: Craig Franklin
Date: 02 Jul 2003 21:53:10 -0500

On Wed, 2003-07-02 at 02:45, Gabor Kiss [Bitman] wrote:
> > > > Last month, Charles Lepple suggested using device files distributed with
> > > > MPLAB to generate the C header files for SDCC.  These are text files
> > > > which describe each part. Currently, a script uses the .inc files in
> > > > gputils to generate the C header files.  The .inc method mostly works,
> > > > but the device file method would be better.
> > >
> > >     It definetely would be better, but as I have mentioned in earlier messages
> > > there is a problem with the .dev files. The names for the configuration bits are
> > > missing. Actually Microchip uses specific names suitable for their MPLAB
> > > GUI interface. If you can take a look into the .dev files. I have send twice
> > > a message with this problem.
> 
> > Beyond SDCC, I have heard one "maybe" with regard to using .dev files.  I
> > am starting to think that this will be more work than it is worth.  Is your
> > new conversion tool close to being complete?  Are you writing it as a
> > generic front end, to simplify reuse for other applications?
> 
> Folks,
> 
> Why don't we define a new extensible format of device description files?
> It could contain any info reqired by various applications.
> (Assemblers, linkers, programmers, etc.)
> Let's start project GRUPID. (GRand Unified PIc Descriptor ;-)
> 

I haven't heard any major complaints about the file format.  A few
things would be have to be added to make everyone happy, but its basic
structure isn't bad.

I think the reason people aren't signing up is a lot simpler. Many
applications are already at least partially functional.  Changing to a
common device description would require significant work.  For 
applications that are mostly complete, there would be little benefit.  

Using it would be best for new applications.  I don't have any idea how
many are in the works.  Many developers keep quiet until they have
something worth showing, that would almost be too late.

I would try to convince several people to use your files before starting
the new project.  It would be a shame to do all the work and have no one
use it.

> Gabor
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gnupic-unsubscribe@linuxhacker.org
> For additional commands, e-mail: gnupic-help@linuxhacker.org
> 


gnupic@linuxhacker.org