In the past, for small jobs I used the 32u4 based boards. For beefier jobs, I used the ESP32 boards. This is a great replacement for all projects you might use a 32u4 board and many projects you may have used the ESP32. Lots of ram and flash, super fast ADC, DMA transfers and excellent price point, the Artemis rocks.

My only gripe is the pad to pin conversion in Arduino is confusing and different between the various boards.

It works as advertised, and is really easy to program. My only complaint is that some of the breakouts and accessory boards that are available need to have their libraries updated for the Artemis. It acts more like a DUO and the software libraries need to reflect that difference.

The similar layout served as a good drop in replacement for me. I had a few projects were I need some extra speed or memory. Looking forward to developing down into the artemis further.

I like that it has 384K of RAM and 1M of Flash, a 48/96 MHz Cortex M4 with hardware floating point, a real hardware debug port, and lots of hardware SPI and I2C IO. But mostly, I like the fact that when it is running real code at 48 MHz, it draws about as much power as a typical "power on" indicator LED. This board is a great way to get started using the Artemis ecosystem. I have not used the Bluetooth capabilities yet, but I have written a number of FreeRTOS applications that make heavy use of the Ambiq SDK library. I found the Ambiq library to be well-written and quite usable. There are a number of development environments available, but I use Segger Studio with a J-Link for hardware JTAG debugging. It is a very effective development environment. My first Redboard had a hard life involving getting some of its traces cut to see how low I could get the deep-sleep power levels (1.63uA FYI). After all that, I retired it to serve as the controller for my reflow solder machine. The reflow software was written using the Artemis Arduino development system, so that works too. I know that a Redboard is way overkill for a reflow controller, but I couldn't resist: now my old Artemis Redboard enables me to construct my new projects based on bare Artemis modules.

I bought this because I wanted to add Bluetooth capabilities to a project that's currently using a RedBoard.
The first problem I ran into is that the uploader fails 99% of the time on recent macOS versions. I finally installed a custom CH340 driver alongside the built-in one and that seemed to make it work. The second problem is that ArduinoBLE is not actually supported (using Core v2.0.2). The examples show up under an "INCOMPATIBLE" submenu, and the bluetooth start method always fails. The third problem appears when trying to use this with mBed Studio: you can't actually debug the thing. You have to build and then run try to run a python-based uploader (but the python script has a syntax error). I'm on the fence between sending it back or trying to get it working via JTAG.

I wanted to do several A/D data logging and write to an SD card. The standard Uno crapped out as the SD card FAT filesystem takes up to much FLASH so my app. couldn't run with out crashing. This board has 384K and a ton of RAM to run, so I moved over fairly easily. The Arduino IDE works well and the CPU brings hardware fast floating point for my calculations. All in all a great board to work with for a dirt cheap price!!!

I got the RedBoard Artemis for a BLE project I had in mind. Plugged into USB-C and did fairly straightforward Arduino BLE programming and everything works! (I did encounter one issue, the Arduino BLE library crashes if many of the objects are referenced as globals but other than that it works.)

So, I thought this would be a great board to play with and learn, but several of the example projects in the Arduino IDE do not work yet and getting support on them has been rather slow. It has a lot of potential, but it isn't quite there yet.

If you intend to use analogWrite, it will not work with 2.0.3. I've been waiting for months for just a simple reply in sparkfun support to address this.

I've tried using the Apollo3 analogWrite example with no luck.

I really want to like this board, because specs wise and price wise it seems great. But.. trying to program this, everything has just been a nightmare. Things I've run into:

• attachInterrupt works ok with RISING and FALLING, but "CHANGE" never seems to register?
• analogRead just does not seem to work. If I do analogRead(A0) it reads from A4. If I try to print out all the pin name -> number, it's totally busted: A0->16, A1->17, A2->17, A3->17, A4->17, A5->17. Wtf? Shouldn't reading from the analog channels be basic functionality? I feel like the software for this wasn't tested at all.
• Some of my QWICC sensors that work with the Uno perfectly fine just do not work with this board at all. No idea why.