FTDI Drivers Break Fake Chips, Again

February 1, 2016 by Brian Benchoff 322 Comments

Just over a year ago, FTDI, manufacturers of the most popular USB to serial conversion chip on the market, released an update to their drivers that bricked FTDI clones. Copies of FTDI chips abound in the world of cheap consumer electronics, and if you’ve bought an Arduino for $3 from a random online seller from China, you probably have one of these fake chips somewhere in your personal stash of electronics.

After a year, we have the latest update to FTDI gate. Instead of bricking fake chips, the latest FTDI drivers will inject garbage data into a circuit. Connecting a fake FTDI serial chip to a computer running the latest Windows driver will output “NON GENUINE DEVICE FOUND!”, an undocumented functionality that may break some products.

FTDI gate mk. 1 merely bricked fake and clone chips, rendering them inoperable. Because fakes and clones of these chips are extremely common in the supply chain, and because it’s very difficult to both tell them apart and ensure you’re getting genuine chips, this driver update had the possibility to break any device using one of these chips. Cooler heads eventually prevailed, FTDI backed down from their ‘intentional bricking’ stance, and Microsoft removed the driver responsible with a Windows update. Still, the potential for medical and industrial devices to fail because of a random driver update was very real.

The newest functionality to the FTDI driver released through a Windows update merely injects unwanted but predictable data into the serial stream. Having a device spit out “NON GENUINE DEVICE FOUND!” won’t necessarily break a device, but it is an undocumented feature that could cause some devices to behave oddly. Because no one really knows if they have genuine FTDI chips or not – this undocumented feature could cause problems in everything from industrial equipment to medical devices, and of course in Arduinos whose only purpose is to blink a LED.

Right now, the only option to avoid this undocumented feature is to either use Linux or turn off Windows Update. Since the latter isn’t really a great idea, be prepared constantly roll back the FTDI driver to a known good version.

Rumors Of Xilinx Sale Abound

February 1, 2016 by Brian Benchoff 28 Comments

The companies that design and build the chips we all use – Atmel, Texas Instruments, Microchip, NXP, Freescale, Intel, Altera, Avago, Broadcom, and On Semi are all buying each other, merging, and slowly becoming two or three gigantic semiconductor companies. The question on everyone’s mind is, ‘which company will be next?’ The answer might be Xilinx, inventors of the FPGA and designers of some really cool parts.

The Wall Street Journal and Barron’s reported a few regulatory filings from Xilinx last week. This could signal an acquisition or merger of the company When this could happen is anyone’s guess, but rumors are flooding the Internet over who would buy Xilinx.

Until recently, Xilinx’s largest competitor in the FPGA market was Altera. That is, until Intel came by with a check for $16.7 Billion. The revenue, size, and market cap of both Xilinx and Altera aren’t too different, leading the question of who would have the money to buy Xilinx and isn’t Intel. Aren’t rumors fun?

Xilinx’s portfolio include high performance, mid-range and low-cost FPGAs as well as interesting hybrid devices. One such hybrid is Zynq, an FPGA and fast ARM Cortex A9 processor in the same package. All these chips will be made for years to come in one form or another. The only question is if Xilinx will make these chips, or will the company continue on under some new branding.

New Research Sheds Light On 3D Printing Fumes

February 1, 2016 by Elliot Williams 28 Comments

A few years back, there were some studies on the chemical and particle emissions coming out of the hotends of 3D printers. Although they galvanized a lot of people in the community, the science wasn’t entirely conclusive — one paper made it sound like you needed a hazmat suit for 3D printing, and the other suggested that cooking a meal in a kitchen was worse for you. That’s because they were measuring different things.

This new research paper on the emissions of 3D printers covers all the bases. They examined a variety of different materials printed in different printers. They also measured both chemical emissions and Ultrafine Particles (UFP) which can be hazardous even when the material itself is not.

We read the paper (PDF) so that you don’t have to. Here’s our takeaways:

There was no significant variation across brands of 3D printers. (Duh?)
ABS and similar materials outgas styrene at levels you should probably be worrying about if you’re running your printer for a few hours a day in an unventilated office.
PLA emitted significantly less overall, and most of it was a non-hazardous chemical, lactide. PLA doesn’t look like a problem.
All of the materials resulted in increased UFP exposure. These levels are above normal household background levels, but lower than certain “microclimates” which (if you follow the references) include principals’ offices with carpet, automobiles, restaurants, and rooms with burning candles or running hair dryers. In short, the UFP exposure doesn’t look like it’s going to be a big deal unless you’re sitting right next to the printer and running it continually.

So what would we do? It now looks like it’s prudent to print ABS only in a well-ventilated room. Or enclose the printer in a box and vent whatever you can outside — which can also help prevent breezes cooling the piece down unevenly and adding to ABS’s warping problems. Or just stick to PLA. It looks essentially harmless.

Thanks [Jim Scheitel] for the tip!

London Tries Smart Cities

January 31, 2016 by Al Williams 4 Comments

What’s a smart city? According to Wikipedia, a smart city uses ICT (information and communication technologies) to enhance quality, performance, and interactivity of urban services while reducing costs and resource consumption. Hackers have been using technology to enhance all sorts of things for years.

London is joining forces with cities across Europe to demonstrate smart city technology, mostly in the Royal Borough of Greenwich. The project is in conjunction with the EU Horizon 2020 project, which is still soliciting proposals for funding. It seems like some Hackaday readers–especially in the EU–ought to have some ideas worth funding.

Continue reading “London Tries Smart Cities” →

ESP8266 Killer?

January 30, 2016 by Elliot Williams 47 Comments

We’ve seen rumors floating around the Twittersphere about a new integrated microprocessor and WiFi SOC: the NL6621 from Nufront. Details are still scarce, but that doesn’t seem to be because the chip is vaporware: you could buy modules on Taobao.com and eBay right now for between two-and-a-half and three bucks, and Nufront’s website says they’ve produced a million modules since 2013.

The NL6621 WiFi SOC is powered by a 160 MHz ARM Cortex-M3 with 448 KB of RAM, and everything else is integrated in the SOC. The module has 32 GPIOs, SPI, I2C, I2S digital audio, and most of the peripherals that you’d expect. They say they have a completely open source SDK, but we can’t find a link to it anywhere. An English-language forum has sprung up in anticipation of the next new thing, and they say that they’ve contacted Nufront about the SDK, so that’s probably as good a place as any to lurk around if you’re interested. With an ARM core, it shouldn’t be long before someone gets GCC working on these things anyway.

It’s also worth noting that we’ve announced ESP8266 killers before, and it hasn’t come to pass. The mixture of community and official support that (eventually) came out of Espressif seems to be the main factor determining the ESP8266’s success, and we don’t see that yet with the NL6621. So take the question mark in the title seriously, but if this turns out to be the next big thing, remember where you heard it first, ok?

Thanks [David Hunt] for the tip!

Warbots: Is It Already Too Late?

January 28, 2016 by Al Williams 53 Comments

In 1971, a non-profit formed that holds the World Economic Forum each year. The Forum claims it “Engages the foremost political, business and other leaders of society to shape global, regional and industry agendas.” This year, the Forum hosted a session: What If: Robots Go To War? Participants included a computer science professor, an electrical engineering professor, the chairman of BAE, a senior fellow at the Vienna Center for Disarmament and Non-Proliferation, and a Time magazine editor.

Continue reading “Warbots: Is It Already Too Late?” →

Bye-bye ATmega328P, Hello 328PB!

January 26, 2016 by Elliot Williams 114 Comments

We never have enough peripherals on a microcontroller. Whether it’s hardware-driven PWM channels, ADCs, or serial communication peripherals, we always end up wanting just one more of these but don’t really need so many of those. Atmel’s new version of the popular ATmega328 series, the ATmega328PB, seems to have heard our pleas.

We don’t have a chip in hand, but the datasheet tantalizes. Here’s a quick rundown of the new features:

Two more 16-bit timer/counters. This is a big deal when you’re writing code that’s not backed up by an operating system and relies on the hardware for jitter-free timing.
Two of each USART, SPI, and I2C serial instead of one of each. Good when you use I2C devices that have limited address spaces, or when you need to push the bits out really fast over SPI.
Ten PWM channels instead of six. This (along with the extra 16-bit timers) is good news for anyone who uses PWM — from driving servos to making music.
Onboard capacitive sensing hardware: Peripheral Touch Controller. This is entirely new to the ATmega328PB chip, and looks like it’ll be interesting for running capacitive sense buttons without additional ICs. It relies on Atmel’s QTouch software library, though, so it looks like it’s not a free-standing peripheral as much as an internal multiplexer with maybe some hardware-level filtering. We’ll have to look into this in detail when we get our hands on one of the chips.

So what does this mean for you? A quick search of the usual suspects shows the chips in stock and shipping right now, and there’s an inexpensive dev kit available as well. If you write your own code in C, taking advantage of the new features should be a snap. Arduino folks will have to wait until the chips (and code support) work their way into the ecosystem.

Thanks [Peter van der Walt] for the tip!