4 Hardware Implementation

4.1 32.768 kHz Crystal

The AVR32SD32 Curiosity Nano Board has a 32.768 kHz crystal mounted. The crystal is connected to the AVR32SD32 by default. The GPIO pins are disconnected from the edge connector to avoid contention and to remove excessive capacitance on the lines. Disconnecting the crystal from the AVR32SD32 and using the pins for other purposes requires some hardware modifications.

Figure 4-1. 32.768 kHz Crystal Block Diagram

Note: The 32.768 kHz crystal implementation on the AVR32SD32 Curiosity Nano is added for use and testing with the AVR32SD32 External 32.768 kHz Crystal Oscillator configured in High-Power mode.

Table 4-1 4-2. Crystal Connections
AVR32SD32 Pin	Function	Shared Functionality
PF0	XTAL32K1	Edge connector
PF1	XTAL32K2	Edge connector

Warning: Disconnect the USB or any external power supply before doing any hardware modifications.

How to Disconnect the Crystal from the AVR32SD32

Disconnect the two I/O lines routed to crystal by cutting the two cut straps on the top side of the board, J111 and J112.
Connect the two I/O lines to the edge connector by soldering on a blob on each circular solder point on the bottom of the board, J109 and J110. These are marked PF0 and PF1 in the silkscreen.

Figure 4-2. 32.768 kHz Crystal Overview

Info: The 0Ω series resistor, R116, may be replaced by any suitable resistor to limit the drive strength of the crystals. If no resistor is required, leave the resistor in place.

The 32.768 kHz crystal has a cut strap (J113), which can be used to measure the oscillator safety factor, and is done by cutting the strap and adding a 0402 SMD resistor across the strap. The AN2648 application note from Microchip contains more information about oscillator allowance and safety factors.

4.2 20 MHz Crystal

The AVR32SD32 Curiosity Nano Board has a 20 MHz crystal mounted. The crystal is connected to the AVR32SD32 by default. The GPIO pins are disconnected from the edge connector to avoid contention and to remove excessive capacitance on the lines. Disconnecting the crystal from the AVR32SD32 and using the pins for other purposes requires some hardware modifications.

Figure 4-3. 20 MHz Crystal Block Diagram

Note: The 20 MHz crystal implementation on the AVR32SD32 Curiosity Nano is added for use and testing with the AVR32SD32 External High-Frequency Crystal Oscillator configured for FRQRANGE 32 MHz.

Table 4-1 4-2. Crystal Connections
AVR32SD32 Pin	Function	Shared Functionality
PA0	XTALHF1	Edge connector
PA1	XTALHF2	Edge connector

Warning: Disconnect the USB or any external power supply before doing any hardware modifications.

How to Disconnect the Crystal from the AVR32SD32

Disconnect the two I/O lines routed to crystal by cutting the two cut straps on the top side of the board, J114 and J115.
Connect the two I/O lines to the edge connector by soldering on a blob on each circular solder point on the bottom of the board, J107 and J108. These are marked PA0 and PA1 in the silkscreen.

Figure 4-4. 20 MHz Crystal Overview

Info: The 0Ω series resistor, R117, may be replaced by any suitable resistors to limit the drive strength of the crystal. If no resistor is required, leave the resistor in place.

The 20 MHz crystal has a cut strap (J116), which can be used to measure the oscillator safety factor and is done by cutting the strap and adding a 0402 SMD resistor across the strap. The AN2648 application note from Microchip contains more information about oscillator allowance and safety factors.

4.3 Multi-Voltage I/O

The AVR32SD32 features one Multi-Voltage I/O (MVIO) domain powered by V_DDIO2. Pins PC0 through PC3 are connected to the MVIO feature and are only powered by the additional V_DDIO2 pin. If no power is supplied to this power pin, the associated I/O pins will not function.

On the AVR32SD32 Curiosity Nano board, VCC_TARGET supplies V_DDIO2 by default. Removing the 0Ω resistor R109 disconnects the default power connection. After the removal, an external power supply can power the MVIO pins through the 1x2-100mil footprint (J119). The block diagram below details the connections to the V_DDIO2 power domain.

Tip: The V_DDIO2 supply voltage can go below the device’s minimum V_DD of 2.7V, with a minimum voltage of 1.71V.

Figure 4-5. MVIO Block Diagram

Figure 4-6. V_DDIO2 Connections

Warning: Before any hardware modifications, ensure the board is disconnected from the USB or external power.

Disconnecting V_DDIO2 from VCC_TARGET:

Disconnect V_DDIO2 from VCC_TARGET by removing resistor R109.
Connect a new power supply to V_DDIO2 and ground at J119.

Warning: J119 does not have reverse polarity protection. Applying voltage to the wrong pin may cause permanent damage to the board.

Warning: Applying an external voltage to V_DDIO2 without removing the resistor may cause permanent damage to the board!

4.4 LED

One yellow user LED is available on the AVR32SD32 Curiosity Nano board. Either GPIO or PWM can control it. Driving the connected I/O line to GND can also activate the LED.

Figure 4-7 4-10. AVR32SD32 Curiosity Nano LED0 Block Diagram

Table 4-3 4-4. LED Connection
AVR32SD32 Pin	Function	Shared Functionality
PD2	Yellow LED0	Edge connector

4.5 Heartbeat LED

The AVR32SD32 may be configured to output a heartbeat signal on an I/O pin to monitor if the controller detects an error. The heartbeat signal oscillates as a square wave when no error is detected. If an error is detected, the heartbeat signal stops oscillating, and the I/O pin is tri-stated.

On the AVR32SD32 Curiosity Nano, a dual-color LED (D101) is mounted to display the heartbeat signal status. This dual-color LED, consisting of one red and one green LED, is connected to pin PF5 on the AVR32SD32. This circuit functions such that only one of the two LEDs lights up at a time. Since pin PF5 is pulled high through a pull-up resistor, D101 will shine red by default and green when the pin is pulled low.

When the heartbeat feature is enabled and set to output to pin PF5, the heartbeat status can be visualized by the dual-color LED. When enabled and while no error is detected, the heartbeat signal will oscillate, toggling the LEDs inversely to each other, causing them to blend into a third color, yellow. If an error is detected, pin PF5 will be tri-stated, causing the red LED to shine.

Figure 4-8. Heartbeat LED Block Diagram

Figure 4-9. Heartbeat LED Overview

4.6 Mechanical Switch

The AVR32SD32 Curiosity Nano board has one mechanical switch - a generic user-configurable switch. Pressing it will connect the I/O pin to ground (GND).

Figure 4-7 4-10. AVR32SD32 Curiosity Nano SW0 Block Diagram

Tip: There is no externally connected pull-up resistor on the switch. Enable the internal pull-up resistor on Pin PF2 to use it.

Table 4-3 4-4. Mechanical Switch Connection
AVR32SD32 Pin	Description	Shared Functionality
PF2	User switch (SW0)	Edge connector, On-board debugger

4.7 Power Supply

The USB port powers the board. The VBUS net is limited to a 2 V/ms slew rate and is current limited to 500 mA by U202 (MIC2008).

Tip: Changing the values for C206 and R211 can alter the slew rate and current limit set by U202.

The power supply consists of two LDO regulators, one to generate 3.3V for the on-board debugger and an adjustable LDO regulator for the target AVR32SD32 microcontroller and its peripherals. The voltage from a USB connector can vary between 4.4V and 5.25V (according to the USB specification) and will limit the maximum voltage supplied to the target. The figure below shows the entire power supply system on the AVR32SD32 Curiosity Nano.

Figure 4-11 4-13. Power Supply Block Diagram

4.7.1 Cut Straps

All power and debugging signals are connected to the target by default. The following cut straps are available to take measurements or separate the debugger from the target:

Target Power Strap (J201)
Power Supply Strap (J200)
Debugger Pins (J101, J102, J103, J104, J105, J106)

Figure 4-12. Common Curiosity Nano Cut Straps

4.7.2 Target Regulator

The target voltage regulator is a MIC5353 variable output LDO. The on-board debugger can adjust the voltage output supplied to the board target section by manipulating the MIC5353’s feedback voltage. The hardware implementation is limited to an approximate voltage range from 1.7V to 5.1V. Additional output voltage limits are configured in the debugger firmware to ensure that the output voltage never exceeds the hardware limits of the AVR32SD32 microcontroller. The voltage limits configured in the on-board debugger on AVR32SD32 Curiosity Nano are 2.7–5.5V.

Info: The factory default target voltage is 5.0V. The project properties in MPLAB® X IDE can change it. Any change to the target voltage is persistent, even after a power toggle. The resolution is less than 5 mV but may be limited to 10 mV by the adjustment program.

Info: The voltage settings setup in MPLAB® X IDE is not applied immediately to the board. Like clicking the Refresh Debug Tool Status button in the project dashboard tab or programming/reading program memory, the new voltage setting is applied to the board when accessing the debugger.

Info: There is an easy option to adjust the target voltage with a drag-and-drop command text file to the board, which supports a set of commonly used target voltages. See section Special Commands for further details.

MIC5353 supports a maximum current load of 500 mA. It is an LDO regulator in a small package placed on a small printed circuit board (PCB) and can reach the thermal shutdown condition at lower loads than 500 mA. The maximum current load depends on the input voltage, the selected output voltage, and the ambient temperature. The figure below shows the safe operating area for the regulator, with an input voltage of 5.1V and an ambient temperature of 23°C.

Figure 4-11 4-13. Target Regulator Safe Operation Area

The voltage output of the target regulator is continuously monitored (measured) by the on-board debugger. An error condition will be flagged - and the target voltage regulator will be switched off, detecting and handling any short-circuit conditions if it is more than 100 mV over/under the set device voltage. It will also detect and handle if an external voltage, which causes V_CC_TARGET to move outside the voltage setting monitoring window of ±100 mV, is suddenly applied to the VTG pin without setting the V_OFF pin low.

Info: The on-board debugger has a monitoring window of V_CC_TARGET±100 mV, and the status LED will blink rapidly if the external voltage is under this limit. The on-board debugger status LED will continue to shine if the external voltage surpasses this limit. When removing the external voltage, the status LED will start blinking rapidly until the on-board debugger detects the new situation and turns the target voltage regulator back on.

4.7.3 External Supply

Instead of the on-board target regulator, an external voltage can power the AVR32SD32 Curiosity Nano. When shorting the Voltage Off (VOFF) pin to the ground (GND) pin, the on-board debugger firmware disables the target regulator, and it is safe to apply an external voltage to the VTG pin.

It is also safe to apply an external voltage to the VTG pin when no USB cable is plugged into the DEBUG connector on the board.

The VOFF pin can be tied low/let go at any time, which will be detected by a pin-change interrupt to the on-board debugger, which controls the target voltage regulator accordingly.

Warning: Applying an external voltage to the VTG pin without shorting VOFF to GND may cause permanent damage to the board.

Warning: Do not apply any voltage to the VOFF pin. Let the pin float to enable the power supply.

Warning: The absolute maximum external voltage is 5.5V for the on-board level shifters, and the standard operating condition of the AVR32SD32 is 2.7–5.5V. Applying a higher voltage may cause permanent damage to the board.

Info: The on-board debugger monitors the voltage supplied to the board. If VOFF is not pulled low and the external power supplied differs by more than ±100 mV from the target regulator setting, the on-board debugger will shut off the target regulator and begin blinking the status LED rapidly, indicating an error condition. Once the input voltage returns within ±100 mV of the target regulator setting, the on-board debugger will switch on the target regulator and stop blinking the status LED.

Programming, debugging, and data streaming are still possible with an external power supply. The USB cable will power the debugger and signal level shifters. Both regulators, the debugger, and the level shifters are powered down when the USB cable is removed.

Info: In addition to the power consumed by the AVR32SD32 and its peripherals, approximately 100 µA will be drawn from any external power source to power the on-board level shifters and voltage monitor circuitry when plugging a USB cable into the DEBUG connector on the board. When a USB cable is unplugged, some current is used to supply the level shifter’s voltage pins, having a worst-case current consumption of approximately 5 µA. Typical values may be as low as 100 nA.

4.7.4 Power Supply Exceptions

This section summarizes most issues that can arise with the power supply.

Target Voltage Shuts Down

Not reaching the set target voltage can happen if the target section draws too much current at a given voltage, causing the thermal shutdown safety feature of the MIC5353 regulator to kick in. To avoid this, reduce the current load of the target section.

Target Voltage Setting is Not Reached

The USB input voltage (specified to be 4.4-5.25V) limits the maximum output voltage of the MIC5353 regulator at a given voltage setting and current consumption. If a higher output voltage is needed, use a USB power source with a higher input voltage or use an external voltage supply on the VTG pin.

Target Voltage is Different From Setting

An externally applied voltage to the VTG pin without setting the VOFF pin low can cause this. If the target voltage fluctuates by over 100 mV over/under the voltage setting, the on-board debugger will detect it, and the internal voltage regulator will shut down. To fix this issue, remove the applied voltage from the VTG pin, and the on-board debugger will enable the on-board voltage regulator when the new condition is detected. Note that the PS LED will blink rapidly if the target voltage is below 100 mV of the setting but will ordinarily turn on when it is more than 100 mV above it.

No, or Very Low Target Voltage and PS LED is Blinking Rapidly

A full or partial short circuit can cause this and is a particular case of the issue above. Remove it, and the on-board debugger will re-enable the on-board target voltage regulator.

No Target Voltage and PS LED is Lit 1

This situation occurs if the target voltage is set to 0.0V. To fix this, set the target voltage to a value within the specified voltage range for the target device.

No Target Voltage and PS LED is Lit 2

This situation can be an issue when cutting power jumper J200 and/or J201 and setting the target voltage regulator to a value within the specified voltage range for the target device. To fix this, solder a wire/bridge between the pads for J200/J201 or add a jumper on J201 if a pin header is mounted.

V_BUS Output Voltage is Low or Not Present

If the VBUS output voltage is low or missing, the reason is probably a high-current drain on V_BUS, and the current limit set by U202 (MIC2008) is tripped and has cut off V_BUS completely. Reduce the current consumption on the VBUS pin to fix this issue.

4.7.5 Low-Power Measurement

Power to the AVR32SD32 comes from the on-board power supply and VTG pin through a 100 mil pin header marked with “POWER” in silkscreen (J201). To measure the power consumption of the AVR32SD32 and other peripherals connected to the board, cut the Target Power strap (J201) on the bottom side and connect an ammeter across it.

Tip: A 100-mil pin header can be soldered into the Target Power strap (J201) footprint for a simple connection of an ammeter. Place a jumper cap on the pin header once the ammeter is no longer needed.

To measure the lowest possible power consumption, follow these steps:

Cut the POWER strap with a sharp tool.
Solder a 1x2 100 mil pin header in the footprint.
Connect an ammeter to the pin header.
Write firmware that:
1. Tri-states any I/O connected to the on-board debugger.
2. Sets the microcontroller in its lowest Power sleep mode.
Program the firmware into the AVR32SD32.

Info: The on-board level shifters will draw a small amount of current even when unused. Each level shifter has a maximum of 2 μA leakage current. Therefore, the worst-case maximum current draw for the five on-board level shifters is 10 μA. Prevent leakage current through an I/O pin connected to a level shifter by keeping the I/O pin tri-stated. All I/Os connected to the on-board debugger are listed in On-Board Debugger Connections. The on-board level shifters can be completely disconnected, preventing leakage, as described in Disconnecting the On-Board Debugger.

4.7.6 VBUS Output Pin

AVR32SD32 Curiosity Nano has a VBUS output pin that can be used to power external components that need a 5V supply. The VBUS output pin is protected by the same start-up delay with a slew rate and current limiter as the rest of the power supply. A side effect is a voltage drop on the VBUS output with higher current loads. The chart below shows the VBUS output voltage versus the current load of the VBUS output.