What’s The Deal With Atmel And Microchip?

October 18, 2016 by Brian Benchoff 75 Comments

It’s been nearly a year since Microchip acquired Atmel for $3.56 Billion. As with any merger, acquisition, or buyout, there has been concern and speculation over what will become of the Atmel catalog, the Microchip catalog, and Microchip’s strategy for the coming years.

For the Hackaday audience, this is a far more important issue than Intel’s acquisition of Altera, On Semi and Fairchild, and even Avago’s purchase of Broadcom in the largest semiconductor deal in history. The reason Microchip’s acquisition of Atmel is such an important issue is simply due to the fact the Hackaday community uses a lot of their parts. This was a holy war, and even changing the name of a line of chips to ‘MCMega’ would result in a consumer rebellion, or at least a lot of very annoying tweets.

For the record, I’ve tried my best to figure out what’s going on with Microchip’s acquisition of Atmel for the last few months. I’ve talked to a few Microchip reps, a few Atmel reps, and talked to a few ‘out of band’ connections – people who should know what’s going on but aren’t directly tied to either Atmel or Microchip. The best I’ve come up with is a strange silence. From my perspective, it seems like something is going on, but no one is saying anything.

Take the following with several grains of salt, but Microchip recently got in touch with me regarding their strategy following their Atmel acquisition. In a few thousand words, they outlined what’s going on in casa Microchip, and what will happen to the Atmel portfolio in the future.

Broad Strokes

In broad strokes, the Microchip PR team wanted to emphasize a few of the plans regarding their cores, software, and how Microchip parts are made obsolete. In simple, bullet point terms, this is what Microchip passed on to me, to pass on to you:

Microchip will continue their philosophy of customer-driven obsolescence. This has historically been true – Microchip does not EOL parts lightly, and the state of the art from 1995 is still, somewhere, in their catalog.
We plan to support both Atmel Studio 7 and MPLAB^® X for the foreseeable future.
Microchip has never focused on “one core”, but rather on the whole solution providing “one platform.” This is also true. A year ago, Microchip had the MIPS-based PIC-32 cores, a few older PIC cores, and recently Microchip has released a few ARM cores. Atmel, likewise, has the family tree of 8 and 32-bit AVR cores and the ARM-based SAM cores.
We will continue to support and invest in growing our 8-bit PIC^® and AVR MCU product families.

Specifics

In addition to the broad strokes outlined above, Microchip also sent along a few questions and answers from Ganesh Moorthy, Microchip’s President and COO. These statements dig a little bit deeper into what’s in store for the Microchip and Atmel portfolios:

How will the 32-bit products complement each other? Atmel has a few 32-bit microcontrollers, like the SAM and AT32 series. Microchip has the PIC-32. The answer to this question is, “Many of the 32-bit MCU products are largely complementary because of their different strengths and focus. For example, the SAM series has specific families targeting lower power consumption and 5 volts where PIC32 has families more optimally suited for audio and graphics solutions. We plan to continue investing in both SAM and PIC32 families of products.”

Will Atmel’s START support 8-bit AVRs? “Yes, although it is too early to commit to any specific dates at this stage, we consider modern rapid prototyping tools, such as START and the MPLAB Code Configurator, strategic for the our customers to deliver innovative and competitive solutions in this fast-paced industry.”

Now that Microchip has a complete portfolio of low-power, inexpensive 32-bit microcontrollers, will the focus on 8-bit product be inevitably reduced? “No, we see that in actual embedded control applications there is still a large demand for the type of qualities that are uniquely provided by an 8-bit product such as: ease-of-use, 5V operation, robustness, noise immunity, real-time performance, long endurance, integration of analog and digital peripherals, extremely low-static power consumption and more. We don’t think that the number of bits is an appropriate / sufficient way to classify a complex product such as the modern microcontroller. We believe that having the right peripherals is actually what matters most.”

Security, Memories, WiFi, and Analog products. For both Atmel and Microchip, the most visible products in each of their portfolios is the lineup of microcontrollers. This isn’t the limit of their portfolios, though: Atmel has space-grade memories, Microchip has some very useful networking chips, and both companies have a number of security and crypto chips. In the statements given by Moorthy, very little will change. The reason for this is the relative lack of overlap in these devices. Even in segments where there is significant overlap, no EOLs are planned, circling back to the, “philosophy of customer-driven obsolescence.” In other words, if people keep buying it, it’s not going away.

The Takeaway

What is the future of Microchip post-Atmel acquisition? From what I’m seeing, not much. Microchip is falling back on their philosophy of ‘customer-driven obsolescence’. What does that mean? Any non-biased assessment of Microchip’s EOL policy is extremely generous. The chip found in the Basic Stamp 1, from 1993, is still available. It’s not recommended for new designs, but you can still buy it. That’s impressive any way you look at it.

The one thing we’re not getting out of this pseudo press release is information about what Atmel will be called in a few years. Will the Atmel mark be subsumed by a gigantic letter ‘M’? Will the company retain two different trademarks? There is no public information about this.

Yes, I know this post is a nearly verbatim copy of a pseudo press release. I’m not particularly happy this information was presented to me this way, but then again, the Atmel/Microchip ecosystem has been impressively secretive. This is the only information that exists, though, and I’m glad to have it in any event.

That said, there are a lot of people in the Hackaday community that want to know what the deal is with Microchip and Atmel. Short of pulling Jerry Seinfeld out of retirement, this is the best we’re going to get for now. Of course, if you have any info or speculation, the comments below are wide open.

Monstrous Suit Of Power Armor 3D Printed Over 140 Days

October 18, 2016 by Donald Papp 36 Comments

[hirocreations] printed an entire suit of enormous Fallout power armor on his Monoprice Maker Select 3D printer, which took some 140 days and over 120 pounds of IC3D PLA filament. Happily, [hirocreations] was able to arrange a sponsorship with IC3D for the build – who would be crazy enough to use so much filament over so long for an entire 7+ foot tall suit, right? Over those 140 days, the belts on the printer needed to be replaced twice but it otherwise chugged right along.

Most of the parts were printed at 0.46 mm layer height. Individual parts were welded (melted) together using what is essentially a soldering iron with a flat tip; many parts were too thin for any kind of joints or fixtures to be practical. Parts were smoothed with drywall spackle, lots of filler primer, and painted. Some of the parts – like the chest armor – are mounted on a frame made from PVC tubing. [hirocreations] may have gone through 120 pounds of filament, but the end result doesn’t weigh that much; the suit itself weighs in at 85-90 lbs, the rest of it went to support material, skirts, and print failures.

It was known from the start that weight could become a serious issue, so [hirocreations] went for a very light infill (10%) and 3-4 perimeter layers; he also extruded at a high temperature (~230C) which he said seemed to provide a very strong layer bond with the settings and filament he was using. So far, he says it’s taken some very hard knocks and nothing has broken or cracked. He has a short video series documenting the assembly, and you can see some of the raw armor parts before any finishing in one of the videos, embedded below.

Continue reading “Monstrous Suit Of Power Armor 3D Printed Over 140 Days” →

Hackaday Prize Entry: Tongue Computer Interface

October 17, 2016 by Brian Benchoff 20 Comments

The Hackaday Prize is a celebration of the greatest hardware put together by the greatest hackers on the planet. If you go over the entries, you’ll find user interfaces for everything. Need a wheelchair controlled by eye gaze? That won last year. A foot controlled mouse? Done. Need a device to talk to the Internet while you’re in a lucid dream? We’ve seen that.

We’ve seen a lot of really cool, really strange stuff in the Hackaday Prize. We haven’t seen anything like Pallette, a finalist for the Assistive Technologies portion of this year’s prize. It’s a tongue-computer interface. You put Pallette in your mouth, like a retainer, and you can control a computer. Telekinesis with a tongue.

At its most basic level, Pallette is a Bluetooth mouse, hidden away behind the lower jaw. Infrared sensors triangulate the position of the tongue, and a microphone detects the tongue tapping on Pallette. Everything you can do with a mouse can be done with Pallette.

At first glance, Pallette seems to be just a little bit absurd. This idea changes when you see the video the Pallette team produced for the Hackaday Prize finals. Some people can’t use their arms, and for this, Pallette is a godsend. With this, anyone can use a computer, control a Sphero, or fly a drone. It’s a completely novel device that can be used for anything, and an excellent example of what we’re looking for in the Hackaday Prize.

Continue reading “Hackaday Prize Entry: Tongue Computer Interface” →

Rotating Frame Will Change Your View Of Vertical Images

October 17, 2016 by Kristina Panos 28 Comments

[Tim] was tired of compromising his portrait-oriented digital photos by shoehorning them into landscape-only frames. Unable to find a commercial solution, he built his own rotating digital photo frame from a 27″ LCD TV.

It uses a Raspi 3 to find [Tim]’s pictures on a giant SD card. He originally wanted to have the Pi pull pictures from Google Photos and display them randomly, but the API doesn’t work in that direction. Instead, a Python script looks at the pictures on the SD card and determines whether each is landscape or portrait-oriented. If a picture was taken in portrait-mode, the display will rotate 90 degrees. Rotation is handled with an Arduino, a stepper motor, and some 3D-printed herringbone gears. The first version was a bit noisy, so [Tim] re-printed the motor mount and the pinion gear out of flexible filament.

[Tim] designed the mount and frame himself and laser-cut the pieces out of birch plywood. We like that he accounted for the front-heaviness and that he covered the high voltage circuitry with acrylic to mitigate the risk of shock. All the code and design files are available on his project page. Make the jump to see a brief demonstration followed by a walk-through and stay for the six-minute slide show.

Continue reading “Rotating Frame Will Change Your View Of Vertical Images” →

This Miniscule IR To HID Keyboard Hides In A Key Cap

October 17, 2016 by Mike Szczys 22 Comments

Shards of silicon these days, they’re systematically taking what used to be rather complicated and making it dead simple in terms of both hardware and software. Take, for instance, this IR to HID Keyboard module. Plug it into a USB port, point your remote control at it, and you’re sending keyboard commands from across the room.

To do this cheaply and with a small footprint used to be the territory of bit-banging software hacks like V-USB, but recently the low-cost lines of microcontrollers that are anything but low-end have started speaking USB in hardware. It’s a brave new world.

In this case we’re talking about the PIC18F25J50 which is going to ring in at around three bucks in single quantity. The other silicon invited to the party is an IR receiver (which demodulates the 38 kHz carrier signal used by most IR remotes) with a regulator and four passives to round out the circuit. the board is completely single-sided with one jumper (although the IR receiver is through-hole so you don’t quite get out of it without drilling). All of this is squeezed into a space small enough to be covered by a single key cap — a nice touch to finish off the project.

[Suraj] built this as a FLIRC clone — a way to control your home-built HTPC from the sofa. Although we’re still rocking our own HTPC, it hasn’t been used as a front-end for many years. This project caught our attention for a different reason. We want to lay down a challenge for anyone who is attending SuperCon (or not attending and just want to show off their chops).

This is nearly the same chip as you’ll find on the SuperCon badge. That one is a PIC18LF25K50, and the board already has an IR receiver on it. Bring your PIC programmer and port this code from MikroC over to MPLAB X for the sibling that’s on the badge and you’ll get the hacking cred you’ve long deserved.

[via Embedded Lab]

A DIY, Visual Alexa

October 17, 2016 by Al Williams 21 Comments

Talking to computers is all the rage right now. We are accustomed to using voice to communicate with each other, so that makes sense. However, there’s a distinct difference between talking to a human over a phone line and conversing face-to-face. You get a lot of visual cues in person compared to talking over a phone or radio.

Today, most voice-enabled systems are like taking to a computer over the phone. It gets the job done, but you don’t always get the most benefit. To that end, [Youness] decided to marry an OLED display to his Alexa to give visual feedback about the current state of Alexa. It is a work in progress, but you can see two incarnations of the idea in the videos below.

A Raspberry Pi provides the horsepower and the display. A Python program connects to the Alexa Voice Service (AVS) to understand what to do. AVS provides several interfaces for building voice-enabled applications:

Speech Recognition/Synthesis – Understand and generate speech.
Alerts – Deal with events such as timers or a user utterance.
AudioPlayer – Manages audio playback.
PlaybackController – Manages playback queue.
Speaker – Controls volume control.
System – Provides client information to AVS.

We’ve seen AVS used to create an Echo clone (in a retro case, though). We also recently looked at the Google speech API on the Raspberry Pi.

Continue reading “A DIY, Visual Alexa” →

Design And Hacking Drilldown: SuperCon Badge

October 17, 2016 by Voja Antonic 18 Comments

One can imagine a political or business conference without an interactive badge — but not a hacker conference. Does this make the case for hackers being a special breed of people, always having something creative to show for their work? Yes, I think it does.

Following the Hackaday Belgrade conference in April of this year, we met at the Supplyframe offices to discuss the badge for the Hackaday SuperConference that will happen in Pasadena on 5+6th of November. The Belgrade conference badge (which was fully documented if you’re curious) was surprisingly popular, and I was asked to design the new one as well.

I was prepared to come up with something completely new, but [Mike Szczys] suggested keeping with the same basic concept for the project: “No reason to change anything, we have a badge that works”. To which I responded: “Well, the next one will also work”. But then I realized that “works” does not stand for “being functional”. The key is that it was embraced by visitors who played with it, coded on it, and solved a crypto challenge with it.

The World Doesn’t Have Enough LEDs

Fast forward six months — here are the modifications made to the basic concept. First, the existing LED matrix, which was composed of two compact 8×8 blocks, was replaced by 128 discrete SMD LEDs. It was a much needed change to help scale down the dimensions and clunkiness, but also to avoid another painful experience of trying to purchase and have the matrix displays shipped, which seriously threatened the production of the previous badge.

It’s a long story which I discussed in my Belgrade talk — it turned out we did not manage to get enough common anode (CA) displays from all distributors in the whole world. We had a plan B, which also fizzled, leaving us with the plan C which actually included two “C”s: Common Cathode. We cleaned up all the supplies at five distributors, and managed to get 122 CA red, 340 CC red and 78 CA green displays (enough for only 270 badges) — the entire world supply. After that, you couldn’t get any 38 mm Kingbright’s display for months! The only problem was that there were two different versions of PCBs, one for CA and the other for CC displays, but luckily only one version of software, as it could autodetect the display type.

Motion and Expansion

So, what else was new in the concept? In the Belgrade version, the badge supported an accelerometer module and included an unpopulated footprint in case you decided to install it, but now the badge has the MEMS chip LIS3 as an integral part. There are nine pads (with five I/O ports, driven directly from the MCU) to which you can add a 9-pin expansion connector. There will be a number of these connectors at the Design Lab, so that anyone can expand their badge for their convenience, on the spot.

The Visual Design

The biggest change was in the visual design. What we came up with ended up being a fair bit smaller, lighter, with a more convenient shape, and less than half the thickness of the previous one. After we had scrapped quite a few ideas during the development process (including stylized skull, frog, etc), we were left with a couple of options which you can see on the image below. The wireframe drawing on the left hand side is the Belgrade badge, shown here for a size comparison. At this point the locale and date of the conference weren’t yet definitive, which is why you see San Francisco written on the images.

Design number 4 prevailed, so the PCB layout could begin. I don’t like autorouted PCBs, so I was in for quite a rough time trying to solve the routing manually having only 2 layers on the board at my disposal.

Routing a Compact LED Matrix

The LED matrix is so dense that there was virtually no room on the LED layer, so most of the tracks on the component layer had to be routed as if it was a single layer PCB. To make matters worse, the LED layer is routed as a matrix, with a bunch of horizontal and vertical tracks, otherwise a good reason to use a 4-layer PCB. To stay inside the budget, everything had to be placed on 2 layers, and that’s why the final result seems so confusing at the populated area between batteries:

Continue reading “Design And Hacking Drilldown: SuperCon Badge” →