d1f80fe9c5
Added AVR Studio project file for SIMM Programmer firmware
2016-04-25 13:48:59 -07:00
c10a164359
Merge pull request #25 from jpluimers/master
...
Wiki updates (images, links); added README.md to master branch; added downloads branch.
2015-10-11 13:26:40 -07:00
1200bcae06
README as a starting point to the repositories and other documentation.
2015-10-10 17:30:55 +02:00
e2963070bc
Added ability to tell programmer firmware to selectively unlock chips.
2013-07-04 12:10:18 -07:00
0ebb9d2281
Finished implementing protocols for reading/writing portions of the SIMM
2012-10-17 21:31:00 -07:00
bf583bf65b
Fixed a couple of bugs -- first, I was reading the wrong datasheet.
...
Second, I was doing a bitwise AND when I was trying to do a modulo.
The firmware is now tested for erasing only a portion of the SIMM.
2012-10-16 21:25:15 -07:00
69f644e5ce
Fixing programmer protocol enum I left out
2012-10-16 18:52:59 -07:00
3252f66749
Added untested support for erasing a specific portion of the SIMM
...
(in 256 KB increments). Won't be able to test it until I implement it in
the control software as well, but I think it should work.
2012-10-16 18:36:55 -07:00
7bbfc23c1a
Added untested support for erasing a specific portion of the SIMM
...
(in 256 KB increments). Won't be able to test it until I implement it in
the control software as well, but I think it should work.
2012-10-15 22:00:29 -07:00
d484d126e5
Got rid of my weird "inverse data" hack for verification and turned on
...
the pull-up resistors on every read instead. That's a better technique
and also makes other things more consistent -- e.g. reading back 0xFF
if a chip identification is attempted when a chip isn't installed.
2012-09-30 20:58:07 -07:00
2c8e7e7184
Fixed the problem that caused no chip present to verify OK after a write
...
The problem was that the data bus would "remember" the last data I wrote
to it if a chip was not driving the data bus on a read, so it would
think that the chip had returned the correct data. I fixed it by writing
the opposite data to the data bus before a verification read.
2012-09-30 16:27:01 -07:00
667c2c5a2d
Added verify during write. It seems to mostly work except when the chip
...
is completely removed from the SIMM -- in that case, the verification
still passes for some reason. I'm still debugging this one. Maybe the
data I had just written is still essentially on the bus because of the
floating pins and it reads it too fast? Maybe turning on pull-ups would
help with that?
2012-09-30 14:41:22 -07:00
ff1f213b6f
Fixed maximum chip size allowed by firmware for compatibility with new
...
8 MB SIMM
2012-09-14 18:13:19 -07:00
7acb3ffcc3
Added support for (untested yet) 8 MB ROM SIMM with chips that expect a
...
slightly different programming protocol.
2012-09-02 15:56:49 -07:00
533813e949
Added LED toggle to write/read modes.
...
Read is so fast that you can't even see the blinking, but oh well.
I also added an "led.h" header file that I should have done long ago.
2012-05-27 15:41:16 -07:00
4b2533b69f
Added GPL license text file.
2012-05-25 22:41:15 -07:00
145487d388
Added GPL header to all of my source files.
2012-05-25 20:21:04 -07:00
ec2237ee21
Updated to LUFA 120219 (with later CDC deadlock patch too)
2012-05-25 19:20:38 -07:00
e9da0905f0
Changed USB vendor/product IDs to use the ones I got.
2012-05-21 19:52:49 -07:00
40cc81446a
Added one-second delay when switching between programmer and bootloader.
...
Just makes me feel better to ensure the "OK" confirmation arrives at the
computer.
2012-05-19 23:07:22 -07:00
7d1888dab8
Added provisions to communication protocol for specifying readback size.
2012-05-19 22:58:17 -07:00
6f24f97df5
Got rid of a few magic numbers, cleaned up more code
2012-05-13 17:48:35 -07:00
d0b50e15c9
Removed old dead code from external_mem.c
2012-05-13 17:06:57 -07:00
f41d8f193a
Electrical status "OK" reply is now sent immediately. Before, it was
...
being buffered, so we didn't get any immediate feedback until the
entire test was finished.
2012-05-13 09:40:04 -07:00
522ded0973
Added .bin file generation for firmware upload
2012-03-04 17:28:15 -08:00
c681547026
Fixed bug that screwed up reading after doing an electrical test.
2012-03-04 12:03:02 -08:00
7f69cb476d
Tried to do some better commenting in usb_serial.c, also tried to do a better job of documenting the protocol in programmer_protocol.h
2012-01-26 20:42:42 -08:00
147c2bfda3
Did some more splitting of responsibilities in the code
2011-12-26 15:02:39 -08:00
e8999cfc54
Moved the programmer protocol to a different file in preparation for sharing it across all the various programs (bootloader, programmer, control program)
2011-12-26 11:31:45 -08:00
258fb187ad
Added extra commands for moving back and forth between the bootloader and the actual program.
...
Disabled the flash erase capability on the main program while I'm working on the bootloader...
2011-12-24 20:09:39 -08:00
035e7cce28
Updated fusebits to prepare for bootloader.
2011-12-20 21:50:14 -08:00
e38269f879
Optimized the SIMM electrical test, fixed a few small bugs I had introduced in the previous commit. Added comments where necessary. Seems to work great now.
2011-12-18 14:55:08 -08:00
a1ca591d60
The same short is never repeated twice with the same 2 pins now. However -- if there's a short between 1, 2, and 3 -- it will still show a short between 1 and 2, 1 and 3, and 2 and 3, even though that info is somewhat redundant. But the host software can iron all that out.
2011-12-18 14:18:49 -08:00
9333b65cde
Fixed a tiny mistake -- forgot to say the name of one of my enums after the typedef.
...
Finished making the electrical test work -- I had failed to realize that I have to ignore the ground shorts once they have been found -- otherwise they reappear against EVERY tested pin (because they are always low and I'm testing for low pins -- duh!). Anyway, it was showing way too many shorts, and that's why. Now I independently can find shorts between separate pins without getting flooded with the ground shorts too. Only thing that's missing is the VCC shorts, but I can't do that without pullups (to my knowledge)
2011-12-18 12:00:22 -08:00
beae025d1a
Oops, I was counting too many errors
2011-12-18 10:19:57 -08:00
9054aaff0f
Started implementing electrical test that tells what pins are shorted to what
2011-12-18 10:18:30 -08:00
52d33e077f
Broke out the SPI read/write into a single routine. Less code repetition -- easier to read and smaller.
2011-12-17 13:43:12 -08:00
540e04331a
Fixed the ordering of the chips -- I had the bytes reversed. Now, when I write/read a continuous stream of data, the bytes will correspond with the correct chips.
2011-12-17 11:18:56 -08:00
b052bb62f8
Fixed a bug with how many bytes I was allowing to be written. It mostly works but it writes the chips in reverse...oops
2011-12-17 10:32:40 -08:00
ca84a1d562
Kept working on the USB protocol
2011-12-16 20:13:34 -08:00
4f0d1a894c
Optimized some of my routines and fixed a nasty, nasty bug that was causing the board to crash because of multiple things being outputs simultaneously.
2011-12-13 21:56:20 -08:00
4adb0c4980
Started working on more optimizations, but something weird is happening and it's crashing...not sure why yet.
2011-12-11 21:48:26 -08:00
1c07518ab0
Added electrical test option to my temporary command line.
...
Also experimented with skipping the SPI -- I left my test code in there, commented out, in case I want to do some more speed testing.
2011-12-11 15:52:04 -08:00
7099218bf1
Added some optimization to remove the 1us delay on the write pulse, but I'm not sure that it matters much.
2011-12-11 13:45:17 -08:00
b4eb6c3ddc
Started getting writing working, as well as the ability to restrict to a specific set of chips to write to
2011-12-11 13:28:32 -08:00
e0977a9339
Created read and write cycle functions, along with a block read function. I think this will look better...
...
I also changed the port module so it doesn't needlessly update the data direction register over SPI if it's being told to set the same value it had before.
2011-12-11 10:12:22 -08:00
f45cc2c4d6
Started writing more command handling
2011-12-11 08:35:53 -08:00
651c3a4be7
Finished testing the new functions I made for chip identification. It works well
2011-12-10 18:57:17 -08:00
8865d0c00f
I got the device identification working, and I'm in the middle of breaking it into its own set of functions for write cycles, read cycles, unlock sequence, etc.
2011-12-10 18:40:30 -08:00
1540bcadd1
Tested reading the entire SIMM contents back to the computer (it works)
2011-12-10 13:53:43 -08:00
steve-chamberlin
Doug Brown
Jeroen Pluimers