Enroll to Review the ADI Bluetooth®︎ 5 MCU Board with a 6-axis accel/gyro

Table of contents

A rapid development platform to help engineers quickly implement battery optimized Bluetooth® 5 solutions


The MAX32666FTHR board is a rapid development platform to help engineers quickly implement battery optimized Bluetooth® 5 solutions with the MAX32666 Arm® Cortex®-M4 processor with FPU. The board also includes the MAX1555 1-Cell Li+ battery charger for battery management. The form factor is a small 0.9in by 2.0in dual-row header footprint that is compatible with breadboards and off-the-shelf peripheral expansion boards. The board also includes a variety of peripherals, such as a micro SD card connector, 6-axis accelerometer/gyro, RGB indicator LED, and pushbutton. This platform provides power-optimized flexible for quick proof-of-concepts and early software development to enhance time to market.


  • Connected Home
  • Gaming Devices
  • Hearables
  • Industrial Sensors
  • Payment/Fitness/Medical Wearables
  • Telemedicine

Community Discussion on this Product

Click here for discussion



  • Eval Board MAX32666 and accessories

Roadtester Instructions

Working with the documentation, open the box and test the out of the box experience of the eval kit.
Show the reader of this review what you discovered about the eval kit through text, images, videos, and/or any other media, so the reader understands what is involved in using the product.


Important Dates

Begin enrollment Feb 12 2024
End enrollment Mar 19 2024
Select roadtesters Mar 19 2024
Ship kit to roadtester TBD
Begin testing TBD
element14 follow up TBD
Post roadtest review by TBD

About Analog Devices

Every day, electronic devices are becoming smarter with greater integration. Body sensors can monitor our health. Cars can drive themselves. Networked homes can power up when needed. At Analog Devices, we’re solving engineering problems and empowering design innovation, enabling our customers to create products that shape our world. We invent highly integrated solutions that make technology seamless. Our innovative and high-performance analog and mixed-signal products and technologies make systems smaller and smarter, with enhanced security and increased energy efficiency. We channel our collective expertise to stretch the limits of technology, understand your needs, and help you get to market faster.

Terms and Conditions

See the attached file below for the terms and conditions.

Comment List
  • I just applied for this RoadTest review. I just submitted my first road test here and this is my 2nd application for my road test journey!

  • Thank you for your response. I'm concerned the knowledge pool is fairly deep on this. I am not a programmer by trade. Establishing a development environment and then attempting to program the device is a daunting task for my skill set.

    I appreciate the candid advice. I want to set a realistic expectation for myself and the product vendor. I feel it would be a struggle. The time and effort investment to complete the RoadTest would be considerable. As a hobbyist I don't see a path to transition the hard earned knowledge from this project.

    I can play hockey but at this point in my life it is much safer for me to watch hockey. It disappointing but I'm going to sit this one out. 

  • it was eclipse environment in history and Eclipse is still supported but prefered IDE is vscode nowdays. But it is Makefile script, so you can use whatever you want. Maxim offers examples and prepared VS code configs. They also offers C SDK: https://github.com/analogdevicesinc/msdk with some addditonal prepared easily-integratable libraries. It is the same SDK you can install using intall wizzard from Maxim (ADI) website. Installer installs some additional tools for you (compiler, Eclipse, openocd, ...). Examples are in Examples folder in the SDK.

  • If I'm thinking of reviewing a microcontroller I've not used before then I'd start as if I had one and see what's required. Before submitting an application I'd read the quick start guide and other documentation. I'd probably download the IDE and get as far as I can without the hardware.

    It could well be that the experiences of a newbie to working with Analog devices is what the manufacturer wants to know. I'd say that if you're interested then it's worth applying. Don't over promise. State what you plan to do and feel you can achieve. If that's what's needed then you may get selected. If it turns out you have problems, then that's a valid road test and a genuine documentation of your experience.

  • Today I believe it would require using an Eclipse-based development environment/SDK. I searched for Arduino and mbed, but didn't find anything conclusive. 

    I think it's steep going from Arduino to Eclipse though. But worth pulling off the plaster and trying it sometime if you feel you wish to, because many microcontrollers are programmed using an Eclipse environment.

    The PDF guide here shows how to install, and then there are two paths.

    The first, if in luck, is that there may well already be example code that sends accelerometer data, so you could tweak that or use it unmodified.

    Otherwise, the second path would be to search for the closest example code for one of the items of functionality you require (for instance, any example code that sends values via BLE), and any example for another functionality, e.g. code that shows how to read data from the accelerometer, and manually combine code, which would require touching code (sometimes just slight modification) in perhaps half a dozen files.

    I think it may require downloading/installing the SDK to see what examples there are (I couldn't find online documentation that lists the examples).

    At the other end of the connection, again there will be example code out there (but again will require searching for the closest to what you're looking for, e.g. to dump to a file, so you can chart it with Excel etc). 

    One way to simplify would be to avoid the BLE if you're uncomfortable with that (or cannot find examples), and then read the data later using say UART. The device has a ton of internal RAM, in simple use it could capture for (say) 10 seconds or even a minute.

    More advanced coding could automatically capture at time of impact (and before) but that's not feasible for a first initial proof-of-concept. At least the potential is there for more advanced things over time, since there is a ton of memory inside it; maybe enough for an entire game! (with more advanced coding - again, not a first version of code).

    In summary, it all hinges on if you're comfortable/prepared to use that Eclipse environment and the code examples.

  • Can someone share their experience with this device. How is this device programmed?

    I have experience programming Arduino and using python on Raspberry Pi. I would like to try and use the onboard accelerometer to record a hockey stick slap shot. Did you know a proper hockey slap shot the stick hits and flexes before making contact with a puck. I would like to try and record some data. 

    What would a person, having no experience with the device, need to have in order to create a simple measurement device?

  • This roadtest will close the enrollment next Tuesday. If you are interested in roadtesting this product, please complete an application. Thanks.


  • This could be perfect for the baby toss game I was helping with durring the 2024 global game jam

  • It is MAX32625PICO which is designed as a DAPLink SWD programmer because MAX32666FTHR has no on-board programmer.

    It has not BLE so you are out of luck here, but you can reuse it as standalone tiny evaluation of board of different Maxim MCU (basically you get two different MCU kits). I did this few years ago and wrote review for this tiny board (and its MCU) as part of different RoadTest:  MAX31343SHLD RoadTest | Review of MAX32625 MCU and MAX32625PICO board