MAX32660EVSYS
Overview
The MAX32660 evaluation system offers a compact development platform that provides access to all the features of the MAX32660 in a tiny, easy to use board. A MAX32625PICO-based debug adapter comes attached to the main board. It can be snapped free when programming is complete. The debug module supports an optional 10-pin Arm® Cortex® debug connector for DAPLink functionality. Combined measurements are 0.65in x 2.2in, while the main board alone measures 0.65in x 0.95in. External connections terminate in a dual-row header footprint compatible with both thru-hole and SMT applications. This board provides a powerful processing subsystem in a very small space that can be easily integrated into a variety of applications.
The Zephyr port is running on the MAX32660 MCU.
Hardware
MAX32660 MCU:
High-Efficiency Microcontroller for Wearable Devices
Internal Oscillator Operates Up to 96MHz
256KB Flash Memory
96KB SRAM, Optionally Preserved in Lowest Power Backup Mode
16KB Instruction Cache
Memory Protection Unit (MPU)
Low 1.1V VCORE Supply Voltage
3.6V GPIO Operating Range
Internal LDO Provides Operation from Single Supply
Wide Operating Temperature: -40°C to +105°C
Power Management Maximizes Uptime for Battery Applications
85µA/MHz Active Executing from Flash
2µA Full Memory Retention Power in Backup Mode at VDD = 1.8V
450nA Ultra-Low Power RTC at VDD=1.8V
Internal 80kHz Ring Oscillator
Optimal Peripheral Mix Provides Platform Scalability
Up to 14 General-Purpose I/O Pins
Up to Two SPI
I2S
Up to Two UARTs
Up to Two I2C, 3.4Mbps High Speed
Four-Channel Standard DMA Controller
Three 32-Bit Timers
Watchdog Timer
CMOS-Level 32.768kHz RTC Output
Benefits and Features of MAX32660-EVSYS:
DIP Breakout Board
100mil Pitch Dual Inline Pin Headers
Breadboard Compatible
Integrated Peripherals
Red Indicator LED
User Pushbutton
MAX32625PICO-Based Debug Adapter
CMSIS-DAP SWD Debugger
Virtual UART Console
Supported Features
The max32660evsys board supports the hardware features listed below.
- on-chip / on-board
- Feature integrated in the SoC / present on the board.
- 2 / 2
-
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files. -
vnd,foo -
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.
max32660evsys/max32660 target
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M4F CPU1 |
|
Clock control |
on-chip |
MAX32 Global Control1 |
|
on-chip |
|||
Counter |
on-chip |
ADI MAX32 counter3 |
|
on-chip |
ADI MAX32 compatible Counter RTC1 |
||
DMA |
on-chip |
ADI MAX32 DMA1 |
|
Flash controller |
on-chip |
MAX32XXX flash controller1 |
|
GPIO & Headers |
on-chip |
MAX32 GPIO1 |
|
I2C |
on-chip |
ADI MAX32 I2C2 |
|
Interrupt controller |
on-chip |
ARMv7-M NVIC (Nested Vectored Interrupt Controller)1 |
|
LED |
on-board |
Group of GPIO-controlled LEDs1 |
|
MTD |
on-chip |
Flash node1 |
|
Pin control |
on-chip |
MAX32 Pin Controller1 |
|
PWM |
on-chip |
ADI MAX32 PWM3 |
|
Serial controller |
on-chip |
||
SPI |
on-chip |
ADI MAX32 SPI2 |
|
SRAM |
on-chip |
Generic on-chip SRAM description4 |
|
Timer |
on-chip |
ARMv7-M System Tick1 |
|
on-chip |
ADI MAX32 timer3 |
||
Watchdog |
on-chip |
MAX32XXX watchdog1 |
Programming and Debugging
Flashing
An Arm® debug access port (DAP) provides an external interface for debugging during application development. The DAP is a standard Arm CoreSight® serial wire debug port, uses a two-pin serial interface (SWDCLK and SWDIO), and is accessed through 10-pin header (J4).
Once the debug probe is connected to your host computer, then you can simply run the
west flash command to write a firmware image into flash.
Note
This board uses OpenOCD as the default debug interface. You can also use
a Segger J-Link with Segger’s native tooling by overriding the runner,
appending --runner jlink to your west command(s). The J-Link should
be connected to the standard 2*5 pin debug connector (J3) using an
appropriate adapter board and cable.
Debugging
Please refer to the Flashing section and run the west debug command
instead of west flash.