GUI limits you to only write a smaller section of the SIMM starting at
the beginning, but the capability should be there in the Programmer
class to add a GUI feature for writing a section in the middle.
feature. The erase capability is there, so next up comes the write.
The next step is to add a mechanism to the protocol to start writing at
a location other than 0 (although this is not needed for this particular
feature, I'd like to have it in there first). Then, I have to update
this software to use that new protocol and make sure verification still
works. I'm about 50% done I'd say.
than MainWindow. Also, I think I have verify while writing working
but I can't test it yet because I haven't implemented in in the
firmware. Bumped version number up as well.
you flash a 512 KB file to a 2 MB SIMM, it will only read back 512 KB.
I haven't tested this other change yet, but after a verify, it should now
tell you which chips are returning bad data.
I also fixed a newly-introduced bug which caused the "erasing SIMM" message
to never appear because the code path that caused it to appear wasn't being
reached after my 8 MB SIMM support change.
Also fixed a few places where I didn't close the port if an error
occurred.
Updated version number to 1.0.1, but I won't release this version
until I know the bigger SIMM works.
I had left some old code when I was changing the communication
scheme around, so I removed it. It was just commented out and
taking up space.
I also added a read me file for Mac OS X users to explain the USB
CDC modem popup message.
I manually removed any font-size styles in the about box. Unfortunately,
Qt Creator automatically puts them in, so this might be an ongoing pain
in the ass to deal with. Hopefully I won't ever have to change anything
on that screen. Anyway, as long as the sizes are left out, Qt defaults
to using whatever the system font is, which is the appropriate font for
that screen.
In order to do this, I changed the Programmer class to no longer take a
filename, but a QIODevice. It should have been done that way originally.
I also rearranged code so that I close the serial port BEFORE sending out
any signals. This was causing a problem if I tried doing something in a
slot connected to one of those signals.
I also fixed a few places where I was forgetting to close the serial
port.
steve-chamberlin
Doug Brown
Doug Brown