Use the Bolt device with a SAMD21 board


So I have an industriuno Proto and IND/IO Industruino board with a ATSAMD21G18 MCU board. It doesn’t not like the softwareserial reference in the Bolt helper .h file I guess because all the . Is there some way a version of the Bolt helper file could be revised or ported over to be compatible with this processor? I’d do it, but I’m not that smart, i’m just a mechanical engineer. :slight_smile: I did find this that appears to be a porting of such of the Softwareserial, can I use this and point to these files in the directory somehow?


So I posed the same question in the Industruino forum and their support person has this response to the workaround. I add this as I understand this is the same board/processor as the Arduino Zero MkR board. Maybe this will be off help to someone.

“Now indeed the SoftwareSerial library is not available for D21G (same MCU as Arduino M0) because the idea is that there are enough hardware serials. But your library requires the softwareserial library to be present. It’s fairly easy to bypass that requirement:

  1. in helper.h comment out line 14 (the include)
  2. in helper.cpp comment out lines 25,26,27 (the only references to softwareserial)

When i do that, the example sketch compiles.”


Hi @keltra,
Thank you for taking an interest and posting this solution. We will look into updating the library such that people do not need to do this hack.


That would be great! I guess if I modify these files, I’ll have to change them back when I do something with a mega or an Uno to compile them if I need to use software serial.


Hi @keltra

You do not need to change them in any way to make the code compile. But you will have to change them back if you want to use softwareserial.


Hi @ksprayberry,

Was this project by you?

Amazing work.


Yes! That was me. I’ve been working on this project for about a year. Originally, I had it setup with an Arduino Mega and a ESP8266 WiFi board. It took me a day or so of reading and reflashing the 8266 to get it working right and then a little finagling to get it to talk to Thingspeak. The BoltIOT cut that back to about 15-30 minutes to have it flying and reporting data to the Bolt cloud. Very helpful.