[David] bought the iPod with a dead battery, so when he opened the iPod to get the old battery out, he noticed there was enough space to fit a USB-C connector. The original Apple 30 pin connector runs USB 2.0 through four of the pins, so [David] used the original USB cable and identified the appropriate pins and traces with a continuity tester. The connector was destructively removed with side cutters, ripping off all but one of the pads in the process. A hot air station might have made things easier, but we assume he did not have one on hand. The USB-C connector was scavenged from a cheap USC-C to USB Micro adaptor and mounted by soldering the housing directly to the PCB’s ground plane. The three remaining terminals were soldered to the traces with enamel wire.
With the new battery installed, [David] confirmed that both charging and data transfer worked. The IC that handles the button and scroll pad interfered slightly with the new connector, so he filed away some of the IC’s excess. Any open pads close to the new connector was covered with Kapton tape to avoid shorts. The large hole in the enclosure for the 30 pin connection was partly filled in with five-minute epoxy. The final assembled product looks almost factory produced and works as it’s supposed to, so we call this a win.
Flash storage was a pretty big deal back in the mid ’00s, although the storage sizes that were available at the time seem laughable by today’s standards. For example, having an iPod that didn’t have a spinning, unreliable hard drive was huge even if the size was measured in single-digit gigabytes, since iPods tended to not be treated with the same amount of care as something like a laptop. Sadly, these small iPods aren’t available anymore, and if you want one with more than 8GB of storage you’ll have to upgrade an old one yourself.
This build comes to us from [Hugo] who made the painstaking effort of removing the old NAND flash storage chip from an iPod Nano by hand, soldering 0.15mm enameled magnet wire to an 0.5mm pitch footprint to attach a breakout board. Once the delicate work was done, he set about trying to figure out the software. In theory the iPod should have a maximum addressable space of 64 GB but trying to get custom firmware on this specific iPod is more of a challenge and the drives don’t simply plug-and-play. He is currently using the rig for testing a new 8GB and new 16GB chip though but it shows promise and hopefully he’ll be able to expand to that maximum drive size soon.
[Labpacks] wanted to build a robot car controlled by his phone. As a Hackaday reader, of course you probably can imagine building the car. Most could probably even write a phone application to do the control. But do you want to? In most cases, you are better off focusing on what you need to do and using something off the shelf for the parts that you can. In [Labpacks’] case, he used Visuino to avoid writing ordinary code and RemoteXY to handle the smartphone interface.
RemoteXY is a website that allows you to easily build a phone interface that will talk to your hardware over Bluetooth LE, USB, or Ethernet (including WiFi). One thing of interest: even though the interface builder is Web-based, the service claims that the interface structure stays on the controller. There’s no interaction with the remote servers when operating the user interface so there is no need for an external Internet connection.
We didn’t think we’d see another hack involving the aging iPod Classic here on Hackaday again, yet [Franklin Wei] surprises us with a brand new port of Quake for the sixth-generation iPod released some thirteen years ago. Is Quake the new 90s FPS that’ll get put into every device hackers can get their hands on?
The port works on top of RockBox, a custom firmware for the iPod and other portable media players. This isn’t the first game on the device. A source port of Doom has been available for years. [Franklin] decided to use Simple DirectMedia Layer (SDL) to make his job easier. That doesn’t mean this was an easy task though, as [Franklin] describes very interesting bugs that kept him from finishing his work for about two years.
The first problem was that the GCC compiler he was using was apparently not optimizing time-critical sound mixing routines. [Franklin] decided enough was enough and dug into ARM assembly to re-write those parts of the code by hand. He managed to squeeze out a speed increase of about 60%. Even better, he ran into a prime example of a bug that would get triggered by a very specific sound sample length running through his code. Thankfully, with all of that sorted, the port is now released and we can all enjoy cramping our hands around tiny screens to frag some low-poly monsters.
Apple has for a very long time been a company that ploughs its own furrow when it comes to peripherals, with expensive proprietary hardware being the order of the day over successive generations of its products. One of its current line of proprietary interfaces is the Lightning connector, best thought of as an Apple-only take on the same ideas that the rest of the world knows as USB-C. There are a whole host of white dangly peripherals that can be hung from your iDevice’s Lightning port, including a pair of display adaptors that allow them to drive an HDMI or VGA monitor. [Lisa Braun] has subjected one that had failed to a teardown, and her analysis gives some insight into the way Apple creates its peripherals.
Where you might expect these to contain mostly the equivalent of a graphics card, in fact they have a fully-fledged SoC of their own that runs its own OS with the same Darwin kernel as its host. Unexpectedly this is not held upon the adapter itself, instead it is shipped with iOS and loaded dynamically. Thus the file containing it can be retrieved from iOS and unpacked, leading to some interesting analysis. In a fascinating twist for those of us unused to Lightning’s internals, it’s revealed that the device can be driven from a USB port with the appropriate cobbled-together adapter, allowing a full-size MacOS device to interrogate it. This many not be news to readers with a long memory though, we’ve told you in the past about reverse engineering the Lightning connector.
[Mike Harrison] produces so much quality content that sometimes excellent material slips through the editorial cracks. This time we noticed that one such lost gem was [Mike]’s reverse engineering of the 6th generation iPod Nano display from 2013, as caught when the also prolific [Greg Davill] used one on a recent board. Despite the march of progress in mobile device displays, small screens which are easy to connect to hobbyist style devices are still typically fairly low quality. It’s easy to find fancier displays as salvage but interfacing with them electrically can be brutal, never mind the reverse engineering required to figure out what signal goes where. Suffice to say you probably won’t find a manufacturer data sheet, and it won’t conveniently speak SPI or I2C.
After a few generations of strange form factor exploration Apple has all but abandoned the stand-alone portable media player market; witness the sole surviving member of that once mighty species, the woefully outdated iPod Touch. Luckily thanks to vibrant sales, replacement parts for the little square sixth generation Nano are still inexpensive and easily available. If only there was a convenient interface this would be a great source of comparatively very high quality displays. Enter [Mike].
This particular display speaks a protocol called DSI over a low voltage differential MIPI interface, which is a common combination which is still used to drive big, rich, modern displays. The specifications are somewhat available…if you’re an employee of a company who is a member of the working group that standardizes them — there are membership discounts for companies with yearly revenue below $250 million, and dues are thousands of dollars a quarter.
Fortunately for us, after some experiments [Mike] figured out enough of the command set and signaling to generate easily reproduced schematics and references for the data packets, checksums, etc. The project page has a smattering of information, but the circuit includes some unusual provisions to adjust signal levels and other goodies so try watching the videos for a great explanation of what’s going on and why. At the time [Mike] was using an FPGA to drive the display and that’s certainly only gotten cheaper and easier, but we suspect that his suggestion about using a fast micro and clever tricks would work well too.
It turns out we made incidental mention of this display when covering [Mike]’s tiny thermal imager but it hasn’t turned up much since them. As always, thanks for the accidental tip [Greg]! We’re waiting to see the final result of your experiments with this.
It can be disheartening when a favoured device begins to break-down. Afflicted by an all-but-dead battery and a fritzing-out hard drive, Redditor [cswimc] sensed the imminent doom creeping up on their 6th generation iPod, and responded by reviving and upgrading the decrepit device instead!
It’s no easy task to crack open one of these things, so they found themselves taking their time and carefully wedging the pry tool between the front and back covers, working their way around the exterior. Once separated, gingerly disconnecting the few ribbon cables allowed the iPod to be opened fully. From there, they turned to swapping out the original hard drive for an iFlash dual SD card board — one of the cards turned out to be a dud, but 128GB is still a step up from 80GB — and a new 3000mAh battery. Combined with replacing the power-hungry HDD, the battery life has been overwhelmingly increased over the original’s 650mAh capacity!