gnupic: gpasm-0.18.1
Subject:
Re: gpasm-0.18.1
From:
Matthew Bowles ####@####.####
Date:
28 Feb 2000 05:31:55 -0000
Message-Id: <38BA0678.530925BD@dsp.com.au>
Scott Dattalo wrote:
>
> On Mon, 28 Feb 2000, Matthew Bowles wrote:
>
> >
> > >
> > > b) The 16C8xx devices (and in particularly the 16c877) are now supported.
> > > This is an over statement somewhat, because all I've done is allowed the
> > > instantiation of the devices, but have not provided the unique features
> > > they offer (the 10-bit A/D , flash , and extended ram sizes are not
> > > supported)
> > >
> >
> > Scott,
> > up until now, whenever you said 16C877 I just assumed there was a
> > different product I hadn't heard of, but now i am convinced that all the
> > time you were meaning the 16F877. You threw me for a while.. so
> > basically, there's no 16c877. but thanks for adding features for the
> > 16F877, or at least up and coming features.
>
> oops. At least it's an F877 in gpsim.
>
> I just added EEPROM support to the 16F874/16F877. It's in CVS, but I
> didn't make a tarball...
>
> I'll be adding the program memory flash read/write next.
>
> Ralf - Are you up to writing a program memory object viewer? I was
> thinking of something based on gtksheet again, just program memory would
> be displayed instead of register memory.
>
> Modifying program memory is going to have impact on the other windows.
> Perhaps we should add xrefs to he object browser and source browser that
> get invoked when program memory is changed. In the object browser, we
> could update the window to reflect the new changes - perhaps highlighting
> the modified locations with a unique color. For the source browser, I'm
> not sure what we should do...
>
> Does anyone have any suggestions on how 1) to present the contents of
> program memory 2) to convey changes in the program memory?
>
> Scott
>
Show adjusted program memory values in a new colour, and perhaps have an
option available to auto-scroll the window to show the memory block
containing the recently adjusted memory location. obivously you can't
display all at once ,but can we select multiple and not neccessarily
adjacent blocks of memory to display.. that would be useful, for
instance, when picc locates some code around the reset vector and some
near 7FFh and some more at the end of the memory bank (1FFFh for the
16F877)....
don't know if this is hard... but suggestions are suggestions as my late
uncle used to say.
kidding.
matt
