Intel(r) Quark(tm) micrcontroller D2000 based Environmental sensors board

pics-D2000 - Assembled Board 2 (1)-600

Sergey Kiselev designed and built an Intel Quark D2000 micrcontroller based Environmental sensors board:

This is a fairly small (51 x 51 mm) board, equipped with a low power Intel Quark D2000 microcontroller, and several sensors (accelerator, temperature, humidity, atmospheric pressure), as well as a mikroBUS compatible header and a Grove compatible connectors, that can be used to connect additional sensors, memory, or radio modules. The board can be used to monitor the environment conditions, and store or transmit the data to a remote system for further processing.

More details at Sergey’s Projects page.

Join the Conversation


  1. After reading the D2000 data sheet, all I can say is: wow, he is brave, how many people are really using this chip?

    Well worth a read, I tell you. The D2000 has 19 comparators! 19! Why?! But the comparators are quite limited feature-wise, the thinking is mostly software-centric.

    The data sheet reads much like an SoC data sheet, after reading it, you will think that Microchip’s PIC data sheets are remarkably well laid out. Its interrupt response clocks is worrying, it works like a CPU, not an MCU. Plenty of don’t-do-this-for-X-clocks things all over the place, this is usual for folks writing device drivers, but not for MCUs. You’d think they’d have experience using good modern MCUs before designing their Quarks… but, hmmm.

    I’m going to read the Intel Quark SE C1000 data sheet now, frankly, I don’t have high hopes. But well, I would consider using Intel Quarks for hobby projects if Intel gives me a bucket of free chips, working compilers, and lots and lots of sample code.

    1. Oh, gotta say this after reading one more of their data sheet: the Intel Quark SE C1000 is supposed to be a 32MHz MCU but the data sheet talks to me like it’s a big SoC. Either the folks have no budget to do much other than their normal work-style or they can’t write tech docs any other way — the data sheet is talking to a device driver developer, not an MCU user.

      Utter fail. If they are serious about an MCU niche, the question of competence comes to mind. Don’t be sorry for Intel if they are a market failure.

Leave a comment

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.