1.. zephyr:board:: max32690fthr 2 3Overview 4******** 5 6The MAX32690FTHR is a rapid development platform to help engineers quickly 7implement ultra low-power wireless solutions using MAX32690 Arm© Cortex®-M4F 8and Bluetooth® 5.2 Low Energy (LE). The board also includes the MAX77654 PMIC 9for battery and power management. The form factor is a small 0.9in x 2.6in 10dual-row header footprint that is compatible with Adafruit Feather Wing 11peripheral expansion boards. 12 13Hardware 14******** 15 16- MAX32690 MCU: 17 18 - Ultra-Efficient Microcontroller for Battery-Powered Applications 19 20 - 120MHz Arm Cortex-M4 Processor with FPU 21 - 7.3728MHz and 60MHz Low-Power Oscillators 22 - External Crystal Support (32MHz required for BLE) 23 - 32.768kHz RTC Clock (Requires External Crystal) 24 - 8kHz Always-On Ultra-Low Power Oscillator 25 - 3MB Internal Flash, 1MB Internal SRAM (832kB ECC ON) 26 - 85 μW/MHz ACTIVE mode at 1.1V 27 - 1.8V and 3.3V I/O with No Level Translators 28 - External Flash & SRAM Expansion Interfaces 29 30 - Bluetooth 5.2 LE Radio 31 32 - Dedicated, Ultra-Low-Power, 32-Bit RISC-V Coprocessor to Offload 33 Timing-Critical Bluetooth Processing 34 - Fully Open-Source Bluetooth 5.2 Stack Available 35 - Supports AoA, AoD, LE Audio, and Mesh 36 - High-Throughput (2Mbps) Mode 37 - Long-Range (125kbps and 500kbps) Modes 38 - Rx Sensitivity: -97.5dBm; Tx Power: +4.5dBm 39 - Single-Ended Antenna Connection (50Ω) 40 41 - Multiple Peripherals for System Control 42 43 - 16-Channel DMA 44 - Up To Five Quad SPI Master (60MHz)/Slave (48MHz) 45 - Up To Four 1Mbaud UARTs with Flow Control 46 - Up To Two 1MHz I2C Master/Slave 47 - I2S Master/Slave 48 - Eight External Channel, 12-bit 1MSPS SAR ADC w/ on-die temperature sensor 49 - USB 2.0 Hi-Speed Device 50 - 16 Pulse Train Engines 51 - Up To Six 32-Bit Timers with 8mA High Drive 52 - Up To Two CAN 2.0 Controllers 53 - Up To Four Micro-Power Comparators 54 - 1-Wire Master 55 56 - Security and Integrity 57 58 - ChipDNA Physically Un-clonable Function (PUF) 59 - Modular Arithmetic Accelerator (MAA), True Random Number Generator (TRNG) 60 - Secure Nonvolatile Key Storage, SHA-256, AES-128/192/256 61 - Secure Boot ROM 62 63Supported Features 64================== 65 66Below interfaces are supported by Zephyr on MAX32690FTHR. 67 68+-----------+------------+-------------------------------------+ 69| Interface | Controller | Driver/Component | 70+===========+============+=====================================+ 71| NVIC | on-chip | nested vector interrupt controller | 72+-----------+------------+-------------------------------------+ 73| SYSTICK | on-chip | systick | 74+-----------+------------+-------------------------------------+ 75| CLOCK | on-chip | clock and reset control | 76+-----------+------------+-------------------------------------+ 77| GPIO | on-chip | gpio | 78+-----------+------------+-------------------------------------+ 79| UART | on-chip | serial | 80+-----------+------------+-------------------------------------+ 81| I2C | on-chip | i2c | 82+-----------+------------+-------------------------------------+ 83| SPI | on-chip | spi | 84+-----------+------------+-------------------------------------+ 85| Flash | on-chip | flash | 86+-----------+------------+-------------------------------------+ 87 88Programming and Debugging 89************************* 90 91Flashing 92======== 93 94The MAX32690 MCU can be flashed by connecting an external debug probe to the 95SWD port. SWD debug can be accessed through the Cortex 10-pin connector, J4. 96Logic levels are fixed to VDDIO (1.8V). 97 98Once the debug probe is connected to your host computer, then you can run the 99``west flash`` command to write a firmware image into flash. Here is an example 100for the :zephyr:code-sample:`hello_world` application. 101 102.. zephyr-app-commands:: 103 :zephyr-app: samples/hello_world 104 :board: max32690fthr/max32690/m4 105 :goals: flash 106 107.. note:: 108 109 This board uses OpenOCD as the default debug interface. You can also use a 110 Segger J-Link with Segger's native tooling by overriding the runner, 111 appending ``--runner jlink`` to your ``west`` command(s). The J-Link should 112 be connected to the standard 2*5 pin debug connector (J4) using an 113 appropriate adapter board and cable. 114 115Debugging 116========= 117 118Once the debug probe is connected to your host computer, then you can run the 119``west debug`` command to write a firmware image into flash and start a debug 120session. Here is an example for the :zephyr:code-sample:`hello_world` application. 121 122.. zephyr-app-commands:: 123 :zephyr-app: samples/hello_world 124 :board: max32690fthr/max32690/m4 125 :goals: debug 126 127References 128********** 129 130- `MAX32690 product page`_ 131 132.. _MAX32690 product page: 133 https://www.analog.com/en/products/max32690.html 134