Jan Wante made this gorgeous Wifi Radio with a modern look. It is based on my original Wifi Radio tutorials.

Not content to simply duplicate my work, he added a few creative twists of his own, including a custom handmade case made of alucobond, MDF, and real wood veneer that gives his finished radio a nice, modern look. Inside, a hacked WL-520gU wireless router running OpenWrt runs the show and an ATmega microcontroller programmed with BASCOM interfaces with a rotary encoder and graphical LCD display.

The very impressive result is shown in this video:

Nice work, Jan!

Thanks to John, of the ATX Hackerspace, who loaned me his Arduino for testing, the HV Rescue Shield now works with the Arduino Mega.

I had to create new byte read/write functions for digital lines 0-7 because they are implemented very “differently” (and I don’t mean that in a good way) in the hardware for the Mega.  If you’re interested in how I did this, check out the new version 2.12 Arduino sketch and the new mega_data_read and mega_data_write functions.

To use the HV Rescue Shield with the Arduino, first download the revised sketch here.  Set the MEGA #define to 1 and compile/upload the sketch to your board.  Make sure you have the Arduino Mega selected in the Arduino Board menu, or the sketch won’t compile.

The Mega has more pin headers than the Rescue Shield, so be sure to install the shield all the way to the left, as shown here:

If you experience any problems with the HV Rescue Shield and the Arduino Mega, please report them in the support forum.

I have good news.  The latest and greatest version of the HV Rescue Shield is now available!

Version 2.1 contains a new and improved 12V switching circuit that resolves an issue reading/writing to parts with certain startup timer settings.  This issue affects all previous versions of the Rescue Shield kit.

I have kits in stock and ready to ship this week.  If you have been waiting for the new release, you can place an order now.

Note to HV Rescue Shield 2.0 customers: Because the startup timer issue was identified so quickly after version 2.0 was released, I am offering a free upgrade for all customers who purchased a version 2.0 kit.  Please contact me to arrange for a replacement.  This offer only applies to HV Rescue Shield 2.0 customers.

About a week ago, I completed testing on a new switching circuit that allows me to leave the DC-DC converter on full-time and switch the RESET signal very quickly (risetimes in the microseconds).   Now there shouldn’t be any more  issues getting parts with zero SUT to enter HVSP/HVPP mode.

It’s taken a lot longer than I expected to get to this point, but the results look very good. I have had 100% success reading/writing all parts I have tested.

PCBs are on order and due to ship by the end of the week.  Assuming the layout is good and I didn’t just order a large batch of stylish (but small) coasters, I should have kits in stock again by the end of next week.

Watch here for updates, and my apologies to everyone who has been waiting on a kit – new and improved kits should be available soon.

Update 2/1: PCBs came in while I was away last week, and are currently being held at my local Fedex office, which is closed due to the power outages that are affecting Austin today.  Apparently Austin does not handle prolonged sub-freezing temperatures very well.   As soon as I can get my hands on the boards, it should only be a day or two before kits are available again.

Version 2.0 of the HV Rescue Shield (I decided to drop the ‘AVR’ from the name) will add support for high voltage serial programming (HVSP) and 8-pin parts like the ATtiny13A.

Boards are due back next week, components are on order, but there is still code to write.

Back to work!

Today, it seems to be working.  I can talk to the AVRISP with avrdude and program devices.  Cool!

I’m not sure what I changed.  I’m using Virtualbox 3.2.10 r66523, running on a Windows 7 64-bit host.  The VM/client OS is Ubuntu 10.10.  I created a USB filter for the AVRISP in the Virtual Machine settings; it doesn’t seem to work without it.  That might be what I was missing before.

To avoid having to run avrdude with root priveledges, I created the file /etc/udev/rules.d/10-avrisp2.rules with the contents:

SUBSYSTEM=="usb", SYSFS{idVendor}=="03eb", SYSFS{idProduct}=="2104", GROUP="adm", MODE="0666"

Pretty simple.

Oh, I should add that there is no guarantee other combinations of host/client OS will work.   If you’re getting different results, leave a comment.

Mitch Altman and I are in the process of writing a book about Making Cool Things with Microcontrollers (for people who know nothing.)

The book features several DIY projects that use AVR microcontrollers.  We’re aiming to teach absolute beginners how to solder, basic electronics, and the process of turning a cool idea into reality by using microcontrollers.

I wrote these instructions about setting up a working avr-gcc environment in Windows, Mac OS X, or Linux.  Mitch and I felt that they could use some beta testing in the real world before bring included in the book, so we decided to make them available here.  We also felt that they might help some people get started with AVRs before the book is available.

We want to make the process of writing and compiling code for the AVR simple and accessible, so we’re not using any fancy IDEs (eg. no AVR Studio).  We also wanted to use the same software on all three operating systems, so Windows-only tools were out.  Instead, we’re using avr-gcc, the compiler behind WinAVR, CrossPack, and Arduino.

I would appreciate any feedback on these instructions.

Here they are:

Windows

Mac OS X

Linux

Update: I totally rewrote this post after getting feedback that I didn’t properly identify my target audience and explain why I chose avr-gcc.  Sorry!

Newark has hard to find ATmega32U2′s in stock?!  Yippee!

<click!>

Hey, wait a minute…

Bad Newark!

And no, they didn’t “just sell the last one.”

I’m happy to report that the AVR HV Rescue Shield has been tested and works with the new Arduino Uno.

This isn’t too much of a surprise, but it’s always good to check that seemingly innocent changes to a hardware platform don’t cause unexpected problems in existing applications.  (That is the voice of experience talking, can you tell?)