On Mon, Aug 05, 2002 at 09:25:07AM +1000, Tony Nixon wrote:
> Byron A Jeff wrote:
> >
> > On Fri, Aug 02, 2002 at 01:19:05PM +1000, Tony Nixon wrote:
> > > Byron A Jeff wrote:
> > > > Maybe it may be worth thinking about writing a piece of Perl that will
> > > > automate those conversions. Let's start generating another list:
> > > >
> > > > * Change the CBLOCK (I hope the code uses a CBLOCK!) from 0x1c to 0x20
> > > > * Turn off the comparitors
> > > > * Change the include file
> > > > * Change the processor in the LIST/device line
> > > > * Update the config line.
> > >
> > > Done!
> > >
> > > Windows though :-)
> > >
> > > http://www.bubblesoftonline.com/projects/f62xconv.zip
> >
> > Does yours do anything that not listed above?
>
> Changes CBLOCK
> Changes #Include directive
> Changes LIST directive
> Updates the CONFIG
> One problem here is that the 16F628 does not have RC mode, so if this is
> found to be enabled in the 16X8X then a message is issued above to the
> 16F62x CONFIG directive.
>
> Turns OFF Comparators
> A problem here is that the software can not analyse the source code.
> Therefore it places the code to disable the comparators at the start of
> the code and places a commented message there to describe what is
> happening. It also generates a compiler error to highlight the need to
> insert this code.
>
> EEPROM read/writes are different RAM pages.
> Again the program doesn't analyse the flow of the code, so whereever it
> finds EEADR or EEDATA in the code it forces a compiler error to get the
> code writer to check the RAM page bits.

Cool.

Any chance that you might consider Open Sourcing it so that Scott, Ralf, myself
and the other gputils folks can include it in the package?

BAJ

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu