EVAL-ADPAQ3029 - Hardware setup
The EVAL-ADPAQ3029 evaluation kit mainly consists of below 2 parts.
1. ADPAQ Development module
The ADPAQ development module, allows us to build applications on ADuCM3029 microcontroller from Analog Devices that is compatible with the Moduware development platform. The ADuCM3029 has the following features/resources-
ARM Cortex-M3 processor with a Memory Protection Unit (MPU)
Operating frequency upto 26
MHz with serial wire debug interface
256 KB of embedded flash memory with Error Correcting Code (ECC)
64 KB of configurable system
SRAM with parity
Hardware cryptographic accelerator supporting AES-128, AES-256, and SHA-256
-
-
Serial Port (
SPORT) for natively interfacing with converters and radios
Programmable GPIOs
3 general-purpose timers with PWM support
RTC and FLEX_
RTC with SensorStrobe and time stamping
12-bit, 8 channel SAR ADC
The ADPAQ module is as shown in the figure below. It mainly consists of 3 evaluation headers namely P1, P2 and P3, a debug connector, an ADT7410 IC (it is a temperature sensor) and a Moduware connector.
The schematics of the ADPAQ module can be viewed from the link. It gives more details about the hardware of the module.
The pin description of the evaluation headers is as shown below:
2. Moduware gateway (Mini-Dev board)
Setup
The ADPAQ module is inserted onto the gateway with the pins facing inward as shown in the image.
Power the gateway by connecting the
USB cable to the Power
USB slot.
Once the hardware setup is complete, setting up software toolchain is explained
here.
In addition to above setup, in order to debug/flash the firmware, debugger (EVAL-ADPAQ3029EBZ-DBG) must be connected between PC and ADPAQ Dev module.

The ADPAQ module is connected to the debugger via a 10 pin arm debugger cable and the debugger is then powered on through the Power
USB port as shown in the figure below.

Once the hardware is set up as described above, the device appears as DAPLINK
.
Make sure that the gateway is powered first with the ADPAQ module already inserted on it and then connect it to the debugger. Otherwise the device manager shows MAINTENANCE
instead of DAPLINK
.