[Oliver] had an old NES controller laying around, and without any other use for it, he decided to repurpose it as a portable storage device.

He gutted most of the controller, removing the plastic standoffs, leaving the D-pad and remaining buttons intact. He crammed a 32 GB flash drive inside, along with the guts from an SD card reader. Using a Dremel he cut several openings into the controller, one for the flash drive and SD card reader’s USB ports, as well as for the SD card itself. When the physical modifications were finished, he installed a small Linux distro on the flash drive, which can be run by any PC that supports booting from USB.

While some might argue, we think it’s a neat way to reuse an old gaming peripheral that he might have otherwise thrown out. The portable OS is something that would certainly come in handy, though we can’t wait until the Raspberry Pi is finished – it would be awesome to have a complete computer packed in there too.

This naked speaker is the basis for [MaoMakMaa's] newest project called the Wavedrone. He plans on using the autonomous and cable-less device during street performances. You can hear the effect of some stretched jazz cords being played on it in the video clip after the break. The sound is kind of an ethereal background noise that observers might not immediately realize is there.

You can see the 9V battery which serves as the power source clinging to the frame of the speaker. A 7805 linear regulator tames that battery and feeds the two IC’s on the circuit board seen to the right. The ATtiny85 is reading music from an SD card and playing it back in mono (obviously) with the help of an LM386 audio amplifier chip. The trimpots that go into the high pass and low pass filters in between the microcontroller and amplifier allow for a bit of sound manipulation, but we’re more impressed with the quality of the sound this is getting when properly trimmed.

Console hacker [techknott] has a skill set that is quite possibly second to none. We do love [Ben Heck] and think that his portable consoles are beyond awesome, but you’ve got to check out this portable GameCube [techknott] put together.

While the construction details are pretty sparse, the video below shows off the bulk of the portable ‘Cube’s best features. Far smaller than his Flip-Top GameCube or Dreamcast portables we’ve featured in the past, his new handheld sports a wider screen and is completely disc-less. While the legality of booting backup copies of games from an SD card is something we won’t delve into, we do like the concept.

The console itself is probably only about one and a half times the width of a standard GameCube controller, and while it doesn’t sport an internal battery pack, we wouldn’t turn one down. Besides, who wants to play GameCube outside? With one of these in hand, we are more than happy to keep our pasty selves indoors, thank you very much.

The only complaint we have here is the lack of build details. [techknott’s] handheld consoles are pretty amazing – we just wish that we could see how the magic was made!

Be sure to check out the video below to see the console in action.

[Thanks, Dave]

[kgsws] just finished his Game Boy upgrade that allows him to load games from an SD card. Loading a game off an SD card has been done before, but [kgsws] decided to not to use a cartridge-based device. In the end, he threw out all the stops and finished his project by having the Game Boy access an SD card directly.

[kgsws] his project trying to figure out how to put some GPIO pins on a game cartridge, but figured that this would take too much hardware. After looking at the specs of the link port, he realized that it was the wrong polarity. Not to be deterred, [kgsws] realized that there was something like a general-purpose I/O on the Game Boy – the joypad input.

After figuring out the logic of accessing the SD card through the joypad, [kgsws] set to work building a FAT32 parser and a simple BIOS on an EEPROM. The entire system runs off an ATmega32, and he was kind enough to include the schematics and all the code. The end result is really neat – it can load and save 512kB Game Boy ROMs and save data, read .txt files. As an added bonus [kgsws] put in a custom boot logo to replace the top-scrolling Nintendo logo.

While the joypad buttons don’t work when the SD card is being accessed, and the battery draw is larger than the already power-hungry DMG-001, we’re amazed by [kgsws]‘s hardware hackery. Check out the video of [kgsws]‘s hack below.

Sometimes your project needs a lot of non-volatile ROM, right on cue [Matthew] let us know how to not only connect, interface, read, and write to SD cards with a PIC over serial, but also how to do the above mentioned with an old PATA HDD. For those without a PIC/serial connection don’t fret, [nada] let us know about his Bus Pirate SD card hack, of which our personal favorite part is the creative use of an old 5.25″ floppy connector as the SD card socket.

[Jose Torres] sent in his latest attempt at creating a custom Gameboy game cartridge. We’ve featured his projects before, and he’s come a lot closer over the last 2 years. He’s aiming to create an easy interface for homebrewers that doesn’t require any other special equipment. In this revision, he’s using a PIC and a memory controller to interface between an SD card and the Gameboy. The cart also has USB support for uploading files to the SD card and reprogramming the PIC. Because it’s just USB mass storage, it will work on almost any modern OS. He’s currently testing the device, but hopes to be selling them soon for $40.

4D  Systems micro drive provides both raw and FAT level access to microSD cards. The module contains a dedicated host controller that transforms what may be an otherwise intimidating card spec into a group of simple serial commands. With a wide supply range of 3.6-5.5 and .1″ lead spacing, this should be cake walk to tinker with. The device doesn’t support FAT32 yet. According to the GOLDELOX-DOS command set page 9, “FAT32 is currently not supported, if you mount a FAT32 formatted disk, you will not be able to access it at all, both FAT and RAW commands will fail”. At the moment the device seems limited at 2GB FAT16 partitions. This sure does seem like cheating after implementing SPI and Nibble mode SD card protocols.

[via Electronics-Lab.Com thanks mozzwald]

[Ben Heck] has just completed one of his more unique laptop game consoles. This time around it’s a Commodore 64, which he’s been attempting since 2006. Recently he scrapped everything and started fresh on what turned out to be the fastest build yet. While it certainly looks similar to his other laptops, he put in a lot of effort to give it the appearance of an 80′s computer from the beige color to the texture. He used an original C64C motherboard since it was the final and smallest revision and coupled that with an original keyboard. A 1541-III-DTV allows use of an SD card as a floppy device. Just drag any disk image onto the card and it’s ready to go. Check out a video of it in use below.

Former Hack a Day contributor [Will] has been using a Eye-Fi SD card to automate his photo transfers. Unfortunately this requires using Eye-Fi’s software and talking to their servers. He used [Jeff Tchang]‘s replacement server written in Python to recieve the images from the card. [Will] manages his own online photo gallery using Gallery 2. To get the images uploaded, he added a call to GUP. Now all of his photos are transfered just as easily as with the standard Eye-Fi but without all of the middleman.

[photo: Eye-Fi teardown]

A coworker approached us today with a corrupted SD card. It was out of her digital camera, and when plugged in, it wasn’t recognized. This looked like the perfect opportunity to try out [Christophe Grenier]‘s PhotoRec. PhotoRec is designed to recover lost files from many different types of storage media. We used it from the command line on OSX, but it works on many different platforms.

It’s a fairly simple program to use. We plugged in the card and launched PhotoRec. We were prompted to select which volume we wanted to recover. We selected “Intel” as the partition table. PhotoRec didn’t find any partitions, so we opted to search the “Whole disk”. We kept the default filetypes. It then asked for filesystem type where we chose “Other” because flash is formatted FAT by default. We then chose a directory for the recovered files and started the process. PhotoRec scans the entire disk looking for known file headers. It uses these to find the lost image data. The 1GB card took approximately 15 minutes to scan and recovered all photos. This is really a great piece of free software, but hopefully you’ll never have to use it.

SD cards add cheap persistent memory to your project, but the holder takes a lot of board space. A smaller option is the microSD flash format. MicroSD cards are compatible with regular SD cards, and most come with a free adapter. We looked at four holders for our mini web server. Which should you choose? Read about our experience below.

Here’s a breakdown of the microSD card holders illustrated above:

Alps SCHA1B0100 $1.27 – Can you see pins through the holes in the first holder? They ‘re hard to see, and almost inaccessible. We didn’t find this holder very useful for prototyping.

JAE ST6S008V4AR1500 $1.46 – This is another model with pins located at the front, but these are further forward for easier access. It’s still going to be a pain to solder, avoid if possible.

SparkFun PRT-00127 $3.95 – Finally, a holder with pins at the back. This is a fairly easy-to-solder part, but it’s not ideal. The soldering tabs are very small and slightly recessed under the shield. It’s also the most expensive microSD holder we’ve seen. SparkFun has a Cadsoft Eagle footprint for this part in their library. We think Molex 538-502702-0891 ($3.58) is probably very similar. We used this holder with the mini web server.

Alps SCHA2B0300 – $1.27 – The long pins along both sides of this holder are easy to solder. The holder is reversed, meaning the card inserts upside-down. Reversed holders seem weird on an all surface mount board, but they fit nicely in through-hole designs. There’s no Eagle footprint yet, but we’ll send an SCHA2B0300 to the first person who makes one; here’s the datasheet (pdf).

Check out our previous parts posts: 0.1uF decoupling capacitors, the LM317 adjustable regulator, and tactile switches.

This mini web server is slightly smaller than a business card. There are a lot of tiny one-board servers out there, but this is probably the smallest you can etch and solder at home. Unlike many embedded web servers, files are stored on a PC-readable SD card, not in a difficult-to-write EEPROM. Read on for the web server design, or catch up on PIC 24F basics in the previous article: Web server on a business card (part 1).

Concept overview

The goal of this project is to build a web server on a business card that serves web pages and files from a FAT formatted SD card. The server is based on a PIC 24F that connects to a TCP/IP network using the ENC28J60 ethernet MAC/PHY. Network layers and low-level services, such as DNS and DHCP, are handled by the Microchip TCP/IP stack. A FAT 12/16/32 formatted SD card contains web pages and files. A very simple HTTP server ties everything together by handling page requests on port 80, searching the SD card for requested, and serving them with the correct content type.

Hardware

(full size schematic .png)

Microcontroller (Microchip PIC 24FJ64GA002)

The brain of the server is a 16-bit PIC 24FJ64GA002 (IC1), a 28pin microcontroller available in several hobbyist friendly packages. Check out our PIC 24F introduction for more about working with this chip.

PIC 24Fs operate between 2 and 3.8volts, which is perfect because the ethernet chip (IC2) and SD card both run at 3.3volts. This chip has 8K of RAM, plenty for the TCP/IP stack and a few K for working with a full FAT file system. The 24FJ64 has two SPI modules, so the SD card and ethernet IC each get a dedicated data bus.

The PIC processor core operates at 2.5volts, and requires a 10uF capacitor (C2) for the on-chip voltage regulator. The datasheet specifies a tantalum capacitor, but we used a low-ESR electrolytic in a prototype without incident. Every power pin needs a 0.1uF decoupling capacitor (C4,5).

The internal 8MHz oscillator provides a 32MHz clock source with the 4x PLL multiplier enabled. We’re also using an external 32.768KHz crystal (Q1) with 2 x 27pF capacitors (C17,18) to enable the real time clock calendar.

Programming connections are brought to a header (SV1). We chose to use programming pin pair three (PGx3). The master clear and reset (MCLR) function is enabled with a 2K resistor (R1) from V+ to the MCLR pin. Optionally, add a button (S1) from MCLR to ground for a manual reset switch.

Ethernet connection (ENC28J60)

An ENC28J60 (IC2) handles the network physical connection (PHY) and MAC layer. The ENC28J60 needs a number of support parts beyond the typical 0.1uF decoupling capacitors (C6,7,9,10). A 25MHz crystal (Q2) and 2 x 27pf capacitors (C15,16) provide a clock signal. The internal core voltage regulator requires a 10uF tantalum capacitor (C1), but an electrolytic capacitor also worked fine. Two LEDs (LED1,2) with 330ohm resistors (R2,3) display link and data status.

A bias resistor (R12) is required; the value will depend on the ENC28J60 version you’re using. Current chips should be B5 (PDF) or B7 (PDF), and require a 2.32K 1% resistor.

The PHY I/O portion specifies 4 x 49.9ohm 1% resistors (R8-11), and a ferrite bead (L1).

The most difficult-to-find part for the ENC28J60 is the correct RJ-45 jack with integrated magnetics (RJ1). We used a J1006F21 PulseJack from Pulse Engineering. Be sure to check the pin configuration and connections if you use a different jack, they will probably be different than ours. A Cadsoft Eagle part library for the JP1006F21 is included in the project archive. This was a $4 part, but it’s gone up to $7. If you know of other jacks that work we’ll add them here.

microSD card

We used a microSD/transflash card in this design because SD cards waste a lot of board space under the holder. microSD cards are smaller versions of SD cards with the same data interface, and most come with an adapter for use in standard SD card readers. The card needs a holder (SD1) and a 0.1uF decoupling capacitor (C8).

If you want to use a full-size SD card, take a look at our version one prototype in the project archive. We used Alps SD card holder #SCDA1A0901. Unfortunately, this part is has been discontinued and we’ve yet to find a suitable replacement. Don’t try #SCDA5A0201, that’s for sure. If you have a favorite, we’ll add it here. Sparkfun has one, and a matching Cadsoft Eagle part library.

Power supply

An adjustable LM317 voltage regulator (IC3) is set to 3.3volts using a 390ohm (R6) and 240ohm (R7) resistor. We considered several 3.3volt regulators, but nothing was cheaper than a LM317 and two resistors. There’s a 0.1uF decoupling capacitor (C13,14) and a 10uF capacitor (C3,19) on both sides to help support the power hungry Ethernet transceiver. The LM317 will output 3.3volts from an input of 5 to 20volts+, but it gets really hot with greater than 9volts supply. The specified input capacitor is only rated 16volts, so consider an upgrade if you plan to use a supply greater than about 9volts.

For the first time ever, we incorporated a power jack (J1) into a design. A jack with a 2.1mm diameter internal pin seems to be the most common DC connector. We used a cheap through-hole DC power jack, like SparkFun #PRT-00119 or Mouser #163-7620-E. It mates with a plug like Mouser #1710-0721.

Circuit board

The PCB (full size placement .png) was designed in Cadsoft Eagle 5.0. Freeware versions are available for all major platforms. Renderings were done with Eagle3D, beta version. Schematic and board files are included in the project archive (ZIP).

We designed the project with large SOIC chips and 0805 surface mount (SMD) parts, but haters can rest assured that chips are available in a through-hole package. We prefer to use SMD parts because the resulting circuit boards are smaller, cheaper, and faster to produce. 0805 parts are dirt cheap, and easy to solder with a normal iron. Don’t expect this project to work on a breadboard, there’s probably too much capacitance for this circuit.

We took full advantage of the PIC’s programmable pin placement to get the simplest trace routings possible. Just four jumper wires are needed on an otherwise single-sided board.

The traces are large and clean, DIY toner transfer boards should be easy. We made our PCB using an inkjet printer transparency mask over an UV sensitive circuit board.

In addition to the final design, the project archive contains our v1 prototype design. The prototype uses a full size SD card (SCDA1A0901) and all electrolytic 10uF capacitors. We also put the RJ45 Ethernet jack on a daughterboard to better accommodate different pinouts.

Partslist

Firmware

Three firmware examples are included in the project archive [zip]. The examples compile with Microchip’s demonstration C30 compiler. Learn more about working with the PIC 24F in our previous article: Web server on a business card (part 1). MPLAB isn’t great about project portability, you may need to locate all the project files again if your path doesn’t match the ‘c:wsbc’ format that we used.

FAT12/16/32 disk library

Our first step was to get the FAT library reading from a SD card. FAT 12/16/32 are simple disk storage formats that work with PCs, MACs, digital cameras, music players, and other electronics. Here’s our favorite FAT tutorial/teardown (PDF).

Microchip’s FAT 12/16/32 library gives us simple functions for working with SD cards. The included demo application creates some files and directories to demonstrate each function. Here’s how we configured it to work on our custom hardware, you can find these changes by searching for the tag ‘HACKADAY’ in the code:

• HardwareProfile.h assigns actual PIC hardware to generic references in the code library. For the SD card this is an SPI interface, and pins for chip select and card detect. First, we deleted all the unused hardware profiles to make the code more manageable. Next, we configured the FAT library to communicate with the SD card using an SPI module (line 132). Finally, we defined the SPI pin assignments (line 152). Pin setup is shown in the table below.
  

  Pin	Port
  Chip select	B0
  SD card detect	A2
  SPI clock	B2
  SPI MOSI	B1
  SPI MISO	B3

• Demonstration.c. On line 48 we set a custom oscillator fuse configuration, as described in our PIC 24F introduction. This is also the logical place to configure pin assignments with peripheral pin select (line 63).
• FSConfig.h. This file enables various components of file system library, affecting the amount of memory and program space used. A read-only library is very small, a full write configuration is bigger. We didn’t have to make any changes for the demonstration, but this is an important file to note.

At first, the library failed to recognize our SD card. It only supports disks with a master boot record (MBR). Windows XP formats SD cards as a DOS disk: a single partition with no MBR. To verify this, open a Windows-formatted disk with a utility like HxD and inspect sector 0 of the physical disk. Byte 446 should be the location of the first MBR partition entry, but instead it’s the NTLDR executable code.

To format the disk in the ‘correct’ FAT format, use a digital camera’s format function or a utility like Panasonic’s SD card formatter. We also considered using a different FAT library that reads DOS disks, like DOSFS, or adding similar features to the Microchip firmware.

TCP/IP stack

Microchip’s free TCP/IP stack performs the convoluted configuration and networking functions needed to run a web server. You can read all about the stack in various application notes and documentation. Wikipedia is our favorite TCP/IP learning resource; we wrote our first TCP/IP stack using only Wikipedia.

Microchip’s TCP/IP stack used to be messy and confusing. Now it’s just confusing. The last few versions of have improved considerably in code clarity and structure. Here’s what we did to to configure the base TCP/IP stack example for our hardware, you can find these changes by searching for the tag ‘HACKADAY’ in the code:

• HardwareProfile.h assigns actual PIC hardware resources to generic references in the code library. We added our custom oscillator configuration (line 68), and configured the server status LED to use the LED attached to PORTB7 (line 83).  We defined the SPI interface to the ENC28J60 as follows (line 116):
  

  Pin	Port
  Reset	B8
  Chip select	B9
  SPI clock	B10
  SPI MOSI	B11
  SPI MISO	B12
  Wake on lan	B13
  Interrupt	B14

• MainDemo.c. We eliminated a bunch of unused code, and added the peripheral pin select configuration code to the InitializeBoard() function (line 332).
• TCPIPConfig.h defines the TCPIP stack components included in a compile. We’ve enabled DNS, DHCP, the IP announcer, and the ping server (line 56):

#define STACK_USE_DNS            // Domain Name Service Client
#define STACK_USE_DHCP_CLIENT    // Get DNS automagically
#define STACK_USE_ANNOUNCE       // Microchip Ethernet Device Discoverer
#define STACK_USE_ICMP_SERVER    // Enable the PING server

After loading this firmware, we’re ready to connect the server to a network for the first time. During initialization, the TCP/IP stack negotiates with the network router for an IP address using DHCP. We need to know this address to communicate with the device. If the device had a screen we could display the IP address, but instead we use the MCHPDetect.exe utility from Microchip.

When the TCP/IP stack finishes initializing, it broadcasts an announcement packet to port 30303 of all locally connected computers. MCHPDetect extracts the IP address from these packets. A new announce packet is sent on every PIC reset.

It’s also possible to read the IP address directly from memory with a debugger. The address is stored in the AppConfig.MyIPAddr variable, the .byte form follows the standard x.x.x.x IP notation.

Once we have the IP address, we can ping the server and test its responsiveness.

If ping shows high latency or malformed packets, you can use Wireshark to inspect network traffic at the byte level. Unless you’re in Germany, because it might be criminal.

Building the custom HTTP server

The custom web server looks for requested files on the SD card, and sends them with the correct content type. We used the Microchip HTTP example server v1 (HTTP.c) as a base for our FAT file server (FATHTTP.c).

Microchip’s HTTP server used a simple file system called MPFS to index web pages on an EEPROM chip. We replaced calls to MPFS functions with calls to functions in the FAT library (see the HTTPProcess and Sendfile functions in FATHTTP.c). Our changes demonstrate the concept as simply as possible, without adding confusing pointers and other handy C obfuscations. The code leaves a ton of room for improvements, have at it. File writes are disabled in the default compilation, but there’s enough program space to enable them if you want to write to the SD card (see FSConfig.h).

It’s necessary to registered our custom FATHTTP server with the rest of the TCP/IP stack. We did a search and replace for the original HTTP server components, and added calls to our new FATHTTP server as needed. That turned out to be these places:

• TCPIPConfig.h. First we inserted some definitions that enable the FATHTTP server (line 70), and added a TCP socket for the FATHTTP server (line 248).
• TCPIP.h. Next, we added FATHTTP to the list of services that require the TCP/IP stack (line 170) and then included the necessary headers (line 351).
• StackTSK.c. We added the FATHTTP server initialization (line 138) and processing (line 340) functions to the list of TCP/IP stack tasks.
• Helpers.c. We also needed to include a few helper functions for working with URLs (line 259).

At long last, it’s time to put some files on an SD card and test this thing. Make sure your files follow the 8.3 file name format. The project archive contains a sample website with a test image and zip file.

After grabbing the server’s IP address with MCHPDetect, we pointed a browser at it. The IP address entered alone will redirect the browser to index.htm, whether or not it exists. Web pages and images stored on the SD card display in the browser, but unknown binary types trigger a download prompt.

Taking it further

We see a lot of potential projects using this tiny web platform.

• Add hooks in the FATHTTP.c source for special URLs that trigger events or configure pins.
• Build a remotely accessible data logger. Use the extra pins to read sensors and log data to the SD card. Logs are retrievable from a web browser, or directly from the FAT readable SD card.
• Get remote access to an ancient serial terminal or BBS, optionally log the console output. Use two external pins as a serial port, and forward commands from the Internet using Microchip’s Telnet server and Ethernet-to-serial bridge examples.
• Your suggestions?

Next time, we’ll use the mini server to make an Internet connected, electronic indoor graffiti wall. This will be an interactive project where everyone can contribute graffiti and animations on-line.

Schematic, board, and firmware files are included in the project archive (ZIP). Use the freeware version of Cadsoft Eagle to view the schematic and PCB. The firmware is written in C, and compiled with the Microchip demonstration C30 compiler.

GpsPasSion forum member [Ospray] has released a new version of MioPocket. For those of you that don’t know, MioPocket is a great unlock kit for GPS units. It basically unlocks the hidden potential of your GPS so you can access the built-in functionality of a PDA as well as retaining the GPS software. This means you can play music, watch video, play games, read and write office documents, and many other things with the once single-purpose device.

Originally written for Mio brand devices, it has been successfully used on a couple other brands. We’ve seen it on a Navigon 2100 using a modified install. This software can run directly off the SD card, so it can easily be updated or removed.

The fun part is fiddling with the scripts to get the newest releases to work on the Navigon and Magellan devices.