When programming a microcontroller, there are some physical limitations that you’ll come across much earlier than programming a modern computer, whether that’s program size or even processor speed. To make the most use of a small chip, we can easily dig into the assembly language to optimize our code. On the other hand, modern processors in everyday computers and smartphones are so fast and have so much memory compared to microcontrollers that this is rarely necessary, but on the off-chance that you really want to dig into the assembly language for ARM, [Uri Shaked] has a tutorial to get you started.
The tutorial starts with a “hello, world” program for Android written entirely in assembly. [Uri] goes into detail on every line of the program, since it looks a little confusing if you’ve never dealt with assembly before. The second half of the program is a walkthrough on how to actually execute this program on your device by using the Android Native Deveolpment Kit (NDK) and using ADB to communicate with the phone. This might be second nature for some of us already, but for those who have never programmed on a handheld device before, it’s worthwhile to notice that there are a lot more steps to go through than you might have on a regular computer.
If you want to skip the assembly language part of all of this and just get started writing programs for Android, you can download an IDE and get started pretty easily, but there’s a huge advantage to knowing assembly once you get deep in the weeds especially if you want to start reverse engineering software or bitbanging communications protocols. And if you don’t have an Android device handy to learn on, you can still learn assembly just by playing a game.
We will have all picked up something from a junk pile or swap meet in our time that caught our eye not because we needed it but because it looked cool. [Quinn Dunki] did just that with an irresistible set of 1980s air traffic control headphones. What did she do with them? Turn them into a set of Bluetooth headphones of course!
The ‘phones in question are particularly interesting, as they turned out upon inspection to be a two-way radio in disguise. Cracking them open revealed a radio board and a logic board, and what makes them particularly interesting to this Hackaday scribe’s eye is their choice of frequency. She finds a crystal with a VHF airband frequency multiplier and concludes that they must operate there, but a look at the photos reveals all the ingredients of a classic AM or low HF receiver. There is a ferrite rod antenna and a variable capacitor, if we didn’t know that these were very high-end professional ‘phones we’d almost suspect they were a novelty AM radio from Radio Shack. If any readers can shed any light on the frequency and purpose of this device, we’re all ears.
The conversion involved a Sparkfun Bluetooth module breakout board paired with a little audio power amplifier. The original drivers were high-impedance and one of them had died, so she replaced them with a modern pair of identical size. The control buttons were mounted in the headphone’s external housing, after a wrong turn into attempting to create a custom enclosure. The result is a rather novel but high-quality set of ‘phones, and one we rather wish we’d found ourselves.
Since its launch in March 2009, the Kepler Space Telescope has provided us with an incredible amount of data about exoplanets within our galaxy, proving these worlds are more varied and numerous than we could ever have imagined. Before its launch we simply didn’t know how common planets such as ours were, but today we know the Milky Way contains billions of them. Some of these worlds are so hot they have seas of molten rock, others experience two sunsets a day as they orbit a pair of stars. Perhaps most importantly, thousands of the planets found by Kepler are much like our own: potentially playing host to life as we know it.
Kepler lived a fruitful life by any metric, but it hasn’t been an easy one. Too far into deep space for us to repair it as we did Hubble, hardware failures aboard the observatory nearly brought the program to a halt in 2013. When NASA announced the spacecraft was beyond hope of repair, most assumed the mission would end. Even by that point, Kepler was an unqualified success and had provided us with enough data to keep astronomers busy for years. But an ingenious fix was devised, allowing it to continue collecting data even in its reduced capacity.
Leaning into the solar wind, Kepler was able to use the pressure of sunlight striking its solar panels to steady itself. Kepler’s “eyesight” was never quite the same after the failure of its reaction wheels, and it consumed more propellant than originally intended to maintain this careful balancing act, but the science continued. The mission that had already answered many of our questions about our place in the galaxy would push ahead in spite of a failure which should have left it dead in space.
As Kepler rapidly burned through its supply of propellant, it became clear the mission was on borrowed time. It was a necessary evil, as the alternative was leaving the craft tumbling through space, but mission planners understood that the fix they implemented had put an expiration date on Kepler. Revised calculations could provide an estimate as to when the vehicle would finally run its tanks dry and lose attitude control, but not a definitive date.
For the last several months NASA has known the day was approaching, but they decided to keep collecting data until the vehicle’s thrusters sputtered and failed. So today’s announcement that Kepler has at long last lost the ability to orient itself came as no surprise. Kepler has observed its last alien sunset, but the search for planets, and indeed life, in our corner of the galaxy doesn’t end today.
Continue reading “Kepler Closes Eyes After a Decade of Discovery”
The biggest news this week comes from Apple. There’s a new Mac Mini (the press copy says it makes a great digital signage platform but we’ll stick to our Raspberry Pis), a gigantic iPad that costs $1900, and the MacBook Air gets a display with more than 900 pixels of horizontal resolution. It’s big news, but this isn’t the biggest news from Cupertino. [Aki-Baidya] reports Apple is bringing back the old-school rainbow logo to t-shirts sold in the Apple Park visitor center. The move follows Apple’s trademark renewal of the rainbow logo earlier this year.
The O.G. rainbow Apple logo was not Apple’s first logo — this honor belongs to the ‘Newton woodcut’ logo designed by [Jobs] and [Ronald Wayne] in 1976. [Wayne] is best known for selling his 10% stake in Apple for $800. The ‘rainbow Apple’ appeared in 1977 after [Jobs] commissioned [Rob Janoff] to design a logo based on the Apple itself. Newton is of course missing from this logo but his contributions to the sciences — the laws of motion and optics — are alluded to with the rainbow apple.
The rainbow Apple logo was phased out in 1998 with the release of the original Bondi Blue iMac and gradually replaced the logo on all four of Apple’s computer lines. The rainbow logo was last seen on Apple laptops with the Wall Street II / PDQ Powerbook, replaced by the Lombard PowerBook in May, 1999. On desktops, the last rainbow logo was found on the beige G3 tower, replaced with the Blue and White G3 in January, 1999.
Despite being discontinued twenty years ago, the rainbow Apple logo has remained one of the most loved corporate logos of all time. To this day, you can still find rainbow Apple logo stickers on the back of old Volvos and pinned to the windows of offices. It is a staple of 80s and 90s-era design. The Rainbow Apple logo t-shirt is available exclusively at the Apple Park Visitor Center gift shop, price is $40.
There are only so many ways to generate music with a computer, and by far the most popular method is MIDI. It’s been around for thirty-five years, and you don’t get to be a decades-old standard for no reason. That said, turning MIDI into audio is a pain, but this project in the Musical Instrument Challenge for the Hackaday Prize makes it easy. It’s a Fluxamasynth Module that turns MIDI into something you can hear.
The key to this build is a single chip that takes MIDI data in and spits out audio, according to the 128 general MIDI sounds. This might not sound like much, but if you’ve ever tried to turn MIDI into sound, you’ll find your options are limited. There is exactly one chip that can do this and is easily obtainable: the SAM2695 from Dream Sound Synthesis. This chip was originally designed for cheap toy keyboards, but if you have a chip, you can do anything with it.
The Fluxamasynth Modules are inspired by the original Fluxamasynth, an Arduino shield that is basically a breakout board for the SAM chip. There’s a MIDI in, and an 1/8″ jack for output, and not much else. The Fluxamasynth Modules extend the capability by adding more support, including stereo output, reverb, chorus, flange, and delay effects, and digs down deep into the configurable parameters for tuning.
The hardware is basically an audio appliance for the Arduino, Raspberry Pi, and the ESP32, and allows for generative music through code. You can see an example of this project in the video below.
Continue reading “Wavetable General MIDI For Everyone”
Like any complex topic, electromagnetic theory has its own vocabulary. When speaking about dielectrics we may refer to their permittivity, and discussions on magnetic circuits might find terms like reluctance and inductance bandied about. At a more practical level, a ham radio operator might discuss the impedance of the coaxial cable used to send signals to an antenna that will then be bounced off the ionosphere for long-range communications.
It’s everyday stuff to most of us, but none of this vocabulary would exist if it hadn’t been for Oliver Heaviside, the brilliant but challenging self-taught British electrical engineer and researcher. He coined all these terms and many more in his life-long quest to understand the mysteries of the electromagnetic world, and gave us much of the theoretical basis for telecommunications.
Continue reading “Oliver Heaviside: Rags to Recognition, to Madness”
There’s a school of thought that says that to fully understand something, you need to build it yourself. OK, we’re not sure it’s really a school of thought, but that describes a heck of a lot of projects around these parts.
[Tim] aka [mitxela] wrote kiloboot partly because he wanted an Ethernet-capable Trivial File Transfer Protocol (TFTP) bootloader for an ATMega-powered project, and partly because he wanted to understand the Internet. See, if you’re writing a bootloader, you’ve got a limited amount of space and no device drivers or libraries of any kind to fall back on, so you’re going to learn your topic of choice the hard way.
[Tim]’s writeup of the odyssey of cramming so much into 1,000 bytes of code is fantastic. While explaining the Internet takes significantly more space than the Ethernet-capable bootloader itself, we’d wager that you’ll enjoy the compressed overview of UDP, IP, TFTP, and AVR bootloader wizardry as much as we did. And yes, at the end of the day, you’ve also got an Internet-flashable Arduino, which is just what the doctor ordered if you’re building a simple wired IoT device and you get tired of running down to the basement to upload new firmware.
Oh, and in case you hadn’t noticed, cramming an Ethernet bootloader into 1 kB is amazing.
Speaking of bootloaders, if you’re building an I2C slave device out of an ATtiny85¸ you’ll want to check out this bootloader that runs on the tiny chip.