Announcing MikroE Click Library Port

We're thrilled to announce the launch of our new MikroE Library port! This port brings a wealth of benefits to the Particle platform, opening up new avenues for your creativity and development.

With this port, you can now connect your Particle devices to an even larger array of microcontroller platforms and interfaces. This means you get access to a wider range of high-quality development boards and accessories, making your projects more versatile and powerful.

One of the standout features of this port is the faster time-to-market it offers. The compatibility with MikroE Click boards allows you to quickly and easily add functionality to your projects, accelerating the development process and getting your ideas off the ground faster than ever before.

Check out the new MikroE Library port and start expanding the horizons of your Particle projects!


we are attempting to use the Micro shields with the Boron. I'm following this instructions for integrating the ADC18. There is an include file "mcu_definitions.h" missing. Can you point me to where this is or what might be in it?


Hey, I see that adc18.h includes spi_specifics.h and this file can be commented out since the port relies on device OS for SPI implementation. I ran through the porting procedure using the same library with that line commented out and everything compiles on my end. Give that a shot and let me know if that works for you!

So commenting this out seemed to work for me.

But, I'm also trying to get the boost-inv-3 working with the Feather Click Shield. I have the ADC18 in MikroBus 1 and the boost-inv-3 in the MikroBus 2. When the setup() runs in my app using the init from the example app, it fails on the boostinv3_default_cfg ( &boostinv3 ).

The setup looks like this:
boostinv3_cfg_setup( &boostinv3_cfg );
if ( I2C_MASTER_ERROR == boostinv3_init( &boostinv3, &boostinv3_cfg ) )

The setup and init of comms doesn't error, but when executing the default_cfg it fails.

Thanks for your help. Any insight on this issue would be helpful.

I'd like to say the Mikro stuff is exactly what we've been looking for. We are trying to get these tested with the Boron to replace our current field deployments.

Thanks for all this work.

1 Like

I picked up 2 MikroE Click boards for a SBC purchase a couple of weeks ago. I've since fried that board...micocontrollers dev boards are more resilient / robust for those in the early phases of learning. lol

Regardless, I am curious if I am able to use these Click boards with my Photon 2? Is it considered the same type of "Feather Form Factor"? Or no? If so, that's huge for me and I'll need to pick up a shield asap.

If not, I might have to check out the Boron when I get the extra cash.

Edit: Looks like it does. :heart_eyes: And it seems like I have the libraries for the boards as well: MIC 2 Click and RS485 CLICK 3.3V

1 Like

Hi @jim3 yes, you can use those Click boards with our devices and it seems like you came to that conclusion already!

1 Like

Hello @erik.fasnacht!

I am attempting to use two Mikroe click boards: the thunder click and gps3 click. I am using the two click boards in combination with a Particle Boron (BRN404X), and connecting the click boards to the Boron through a Feather Click Shield from Mikroe.

Image of configuration:

I have tried programming the thunder click on the Particle Web IDE with the AS3935 library already available, but the program has been very unreliable and finicky, especially when trying to calibrate the thunder click with the Lightning Emulator Shield (SEN-39002) from PlayingWithFusion. It's either all noise or disturbed and I cannot seem to get a positive "lightning strike" indication.

Lightning Emulator:

I have been trying to get the example program and libraries Mikroe has for the thunder click to work, but I haven't had too much luck. Here is my GitHub repo for the project thus far. Any help or suggestions would be appreciated!

Hi @Calhouners welcome to the Community!

I am not sure if any of the MikroE libraries will work with the Web IDE, I've only tested using Workbench.

I would start by referring to this document (if you haven't reviewed already) and make the modifications per the document in a project in Workbench.