Taking Pictures with a DRAM Chip
translate.google.com
translate.google.com
Did this hack together with my brother twenty years ago (look at the file dates)!
Strange to see my 1994 hack at #1 on hacker news twenty years later..
It was done with 64kBit DRAMs in a ceramic package. Descrambling the physical chip layout was a pain..
My main questions are:
1) how far from the RAM should I put the lens?
and 2) is the lens I mentioned in my comment going to be an adequate lens?
Keep in mind that the resolution was only 64x256 pixel (we used one of four physical separate 64x256 bit arrays on the chip) so the lens quality did not really matter.
I have about four RasPis lying around doing doing things which where very much unaccessible for a hobbyist then. Just look at my current blog at http://µc.net to see a few (it's in german alas, maybe google translate can help here too..).
I look forward to the insightful discussions and sharing of unique ideas/perspectives, this is how innovation is born!
"The ramera was first developed by the Robotics group at Case Western Reserve University in Cleveland Ohio, in 1978."
Apparently they wrote up their work in the Sensor Group Journal. They had used a 4008 which was only 64 x 64 pixels.
Not surprisingly this work was the basis for early optical mice which use what is a DRAM circuit as an imager to detect motion of the mouse in two directions without using a rolling ball. This led to a number of roboticists hacking their optical mice into simple cameras (which was much easier than popping the lid on an increasingly hard to find DRAM chip). That practice was then replaced by using CMOS imagers that had been pretty cheap by the early 2000's and of course these days you can get a camera module for a phone very inexpensively (see the PiCAM for $29 for example)
I have been told that a quick way to reverse engineer the scrambling is to shine a circular pattern onto the physical dram, then read out the data and test common scramblings until the logical data shows the same circle.
Edit: just remembered - he worked out that if you used a high power camera flash and fired it 20-30 times it had the same effect.
- An IC (the one he used seems to be http://www.ebay.com/itm/5-Rare-Vintage-GOLD-NEC-044-D4164D-4...)
- A small lens to place over the IC (http://www.ebay.com/itm/MTV-6MM-CCTV-IR-Lens-For-Security-IP...)
- A parallel to USB cord if you don't have a computer with a parallel port (http://www.ebay.com/itm/USB-to-PRINTER-DB25-25-Pin-Parallel-...)
Please correct me if I'm wrong about any of these parts - I haven't tried to build one myself.
Here's my rudimentary understanding of the pin connection: (to connect it yourself, use https://upload.wikimedia.org/wikipedia/commons/b/b3/Pin_numb..., https://upload.wikimedia.org/wikipedia/commons/e/e0/Parallel..., and https://upload.wikimedia.org/wikipedia/commons/e/e1/25_Pin_D... as guides)
IC-Parallel
2-1
3-14
4-16
5-8
6-4
7-3
8-18
9-9
10-7
11-6
12-5
13-2
14-12
15-17
16-25
Last time I looked at the spec for those, it supported send-byte-to-printer-with-IEEE-1284-handshaking as a primitive (the USB interface saw data bytes, not instructions to set, clear, and read control lines). The parallel ports that attached to ISA (or inside PCI multi-I/O chips) connect each pin to a bit of an I/O address in compatibility mode[], which connect-a-chip-to-parallel-port hacks tend to use.
"Modern" gui usually provide this too - For example in KDE I have a nice "extract > extract here, autodetect subfolder" menu in Dolphin (the file manager)
The concept behind the term 'tarbomb', (I had to look it up) speaks most about user laziness and disorganization. Why should a zip or tar archive contain anything other than the files it's advertised to contain? If they are nested in a folder, that just makes more work for me, since it's unlikely I'm going to be happy with the folder name as is, so have to rename it. Or more likely, move the files back up to the folder I extracted the whole thing into, then delete the now empty superfluous folder.
"You are included in the Settlements if:
You are a person or business that purchased DRAM or a device containing DRAM;Your purchase was made anytime from January 1, 1998 through December 31, 2002;Your purchase was made in the United States including Puerto Rico, the Northern Mariana Islands, and the territories or from a seller located in the United States, including Puerto Rico, the Northern Mariana Islands, and the territories and;Your DRAM purchase was not made directly from any of the DRAM manufacturers."
Guess this is the reason some of you mentioned why the price was so high? well I'll be damned, submit your claims!
Interesting to look at the sourcecode of the Kuckoo program (before the widespread adoption of UTF-8!) and how it uses High Dynamic Range tricks to read off the image at different exposures.
With much faster RAM and smaller cells nowadays maybe one could do something cool with very fast photography, but of course the faster/smaller the RAM the more trouble interfacing with it and calibrating the light intake.
" DRAM is a widely used form of computer memory that is found in many products including personal computers, servers, and MP3 players. Regardless of the brand name, most of these types of products produced between 1998 and 2002 contained DRAM chips.
“This price-fixing wrongly forced consumers and state agencies to pay more for computers and other high-tech products containing DRAM chips,” Attorney General Bob Ferguson said Tuesday. “This settlement will provide some monetary relief for affected consumers.”
The total multi-state settlement is $310 million. The amount of money returned to Washington state consumers depends on how many claims are filed and the types of products they purchased, Ferguson said."
price fixing?! interesting.
Byte September / October 1983 Steve Ciarcia: "Build the Micro D-Cam Solid-State Video Camera"
ftp://164.41.45.4/pub/electronics/circuit_cellar/BYTE_Projects/D-Cam2.pdf