background image

On Linux machines, the CDC will enumerate and appear as 

/dev/ttyACM#

.

On MAC machines, the CDC will enumerate and appear as 

/dev/tty.usbmodem#

. Depending on

which terminal program is used, it will appear in the available list of modems as 

usbmodem#

.

Info: 

 On older Windows systems, a USB driver is required for CDC. This driver is included in

MPLAB X and Atmel

®

 Studio installations.

3.1.1.2 

Limitations

Not all UART features are implemented in the on-board debugger CDC. The constraints are outlined
here:

Baud rate

 must be in the range 1200 bps to 500 kbps. Any baud rate outside this range will be set to

the closest limit, without warning. Baud rate can be changed on-the-fly.

Character format

: Only 8-bit characters are supported.

Parity

: Can be odd, even, or none.

Hardware flow control

: Not supported.

Stop bits

: One or two bits are supported.

3.1.1.3 

Signaling

During USB enumeration, the host OS will start both communication and data pipes of the CDC interface.
At this point, it is possible to set and read back the baud rate and other UART parameters of the CDC, but
data sending and receiving will not be enabled.

When a terminal connects on the host, it must assert the DTR signal. This is a virtual control signal
implemented on the USB interface, but not in hardware in the on-board debugger. Asserting DTR from
the host will indicate to the on-board debugger that a CDC session is active, will enable its level shifters
(if available) and start the CDC data send and receive mechanisms.

Deasserting the DTR signal will not disable the level shifters but disable the receiver so no further data
will be streamed to the host. Data packets that are already queued up for sending to the target will
continue to be sent out, but no further data will be accepted.

Remember: 

 Enable to set up your terminal emulator to assert the DTR signal. Without it, the

on-board debugger will not send or receive any data through its UART.

3.1.1.4 

Advanced Use

CDC Override Mode

In normal operation, the on-board debugger is a true UART bridge between the host and the device.
However, under certain use cases, the on-board debugger can override the basic operating mode and
use the CDC pins for other purposes.

Dropping a text file (with extension 

.txt

) into the on-board debugger’s mass storage drive can be used

to send characters out of the CDC TX pin. The text file must start with the characters:

CMD:SEND_UART=

The maximum message length is 50 characters - all remaining data in the frame are ignored.

 ATtiny1607 Curiosity Nano

Curiosity Nano

©

 2019 Microchip Technology Inc.

 User Guide

DS50002897A-page 7

Summary of Contents for ATtiny1607 Curiosity Nano

Page 1: ...d by Atmel Studio Microchip MPLAB X Integrated Development Environment IDE the kit provides easy access to the features of the ATtiny1607 to explore how to integrate the device into a custom design Th...

Page 2: ...et Regulator 10 3 3 2 External Supply 11 3 3 3 VBUS Output Pin 11 3 4 Target Current Measurement 12 3 5 Disconnecting the On Board Debugger 13 4 Hardware User Guide 15 4 1 Connectors 15 4 1 1 ATtiny16...

Page 3: ...7 5 Getting Started with IAR 26 The Microchip Website 29 Product Change Notification Service 29 Customer Support 29 Microchip Devices Code Protection Feature 29 Legal Notice 30 Trademarks 30 Quality M...

Page 4: ...stable Target Voltage MIC5353 LDO regulator controlled by the on board debugger 1 8 5 1V output voltage limited by USB input voltage 500 mA maximum output current limited by ambient temperature and ou...

Page 5: ...icrochip microcontrollers and digital signal controllers It is called an Integrated Development Environment IDE because it provides a single integrated environment to develop code for embedded microco...

Page 6: ...are The on board debugger controls a Power and Status LED marked PS on ATtiny1607 Curiosity Nano The table below shows how the LED is controlled in different operation modes Table 3 1 On Board Debugge...

Page 7: ...tual control signal implemented on the USB interface but not in hardware in the on board debugger Asserting DTR from the host will indicate to the on board debugger that a CDC session is active will e...

Page 8: ...T12 file system that has a number of limitations partly due to the nature of FAT12 itself and optimizations made to fulfill its purpose for its embedded application The CURIOSITY drive is USB Chapter...

Page 9: ...mory mapped fuse values Disabling UPDI will render the debugger unable to contact the target device an external programmer capable of 12V UPDI activation will be required 3 2 Curiosity Nano Standard P...

Page 10: ...ower consumer P3V3 DEBUGGER Power converter DEBUGGER Regulator VUSB Target Regulator Power Supply strap Adjust Level shifter VLVL VREG I O I O GPIO straps I O On Off Measure On Off ID system VOFF PTC...

Page 11: ...pin is shorted to ground GND the on board debugger firmware disables the target regulator and it is safe to apply an external voltage to the VTG pin WARNING Applying an external voltage to the VTG pin...

Page 12: ...connected from the on board power supply and VTG pin through a 100 mil pin header cut Target Power strap marked with POWER in silkscreen J101 To measure the power consumption of the ATtiny1607 and oth...

Page 13: ...Ttiny1607 Curiosity Nano The signal names shown in Figure 3 1 are printed in silkscreen on the bottom side of the board Figure 3 6 On Board Debugger Connections to the ATtiny1607 DEBUGGER TARGET Level...

Page 14: ...r short circuit them with tin solder to reconnect any cut signals Figure 3 7 Kit Modifications GPIO straps bottom side Power Supply strap top side ATtiny1607 Curiosity Nano Curiosity Nano 2019 Microch...

Page 15: ...7 PA7 GND GND PC5 PC5 PC4 PC4 SW0 ATtiny1607 CURIOSITY NANO Analog Debug I2C SPI UART Shared pinout Peripheral Port PWM Power Ground 4 1 2 Using Pin Headers The edge connector footprint on ATtiny1607...

Page 16: ...istor is enabled on pin PC4 Table 4 2 Mechanical Switch ATtiny1607 Pin Description Shared Functionality PC4 User switch SW0 Edge connector 4 2 3 On Board Debugger Implementation ATtiny1607 Curiosity N...

Page 17: ...y1607 RX line Edge connector PB2 CDC RX UART TX ATtiny1607 TX line Edge connector UPDI DBG0 UPDI PB7 DBG1 GPIO Edge connector PC4 DBG2 GPIO Edge connector UPDI DBG3 RESET J202 not connected by default...

Page 18: ...is the revision The boards with limited space have a sticker with only a QR code containing the product identifier revision and the serial number The serial number string has the following format nnnn...

Page 19: ...es not have the Target Power strap described in 3 4 Target Current Measurement Instead the current can be measured across the Power Supply strap as described in 3 5 Disconnecting the On Board Debugger...

Page 20: ...6 Document Revision History Doc rev Date Comment A 06 2019 Initial document release ATtiny1607 Curiosity Nano Document Revision History 2019 Microchip Technology Inc User Guide DS50002897A page 20...

Page 21: ...terface CDC TX CDC RX UART RX UART TX VTG 1 8V 5 5V VOFF ID_SYS ID_SYS VOFF 2 2uF C205 GND TARGET BULK PC4_SW0 PB7_LED0 VBUS PB3_RXD PC5 PA0_UPDI GND CDC RX 3 CDC TX 4 DBG1 5 DBG2 6 0 TX 7 1 RX 8 2 SD...

Page 22: ...TARGET ADJUSTABLE REGULATOR SRST 100n C104 GND SRST VCC_P3V3 GND Testpoint Array 1 2 3 4 5 6 7 8 9 10 TCK TDO TMS Vsup TDI GND TRST SRST VTref GND J102 SWCLK DEBUGGER TESTPOINTs DBG2_CTRL VOFF CDC_RX...

Page 23: ...0 2 0 1 C O J 1 0 2 P A J 1 0 5 0 1 1 P A J 1 0 5 0 1 0P A J 1 0 5 0 8 P A J 1 0 5 0 9 P A J 1 0 5 0 7 P A J 1 0 5 0 6 P A J 1 0 5 0 1 P A J 1 0 5 0 2 P A J 1 0 5 0 3 P A J 1 0 5 0 4 P A J 1 0 5 0 5 P...

Page 24: ...1607 CURIOSITY NANO Analog Debug I2C SPI UART Shared pinout Peripheral Port PWM Power Ground 1 AN PWM RST INT CS RX SCK TX MISO SCL MOSI SDA 3 3V 5V GND GND 2 AN PWM RST INT CS RX SCK TX MISO SCL MOSI...

Page 25: ...ely used Therefore the on board debugger will not interfere with any external debug tools Figure 7 5 Connecting the MPLAB PICkit 4 In Circuit Debugger Programmer to ATtiny1607 Curiosity Nano 2 3 4 5 6...

Page 26: ...R is a proprietary high efficiency compiler which is not based on GCC Programming and debugging of ATtiny1607 Curiosity Nano is supported in IAR Embedded Workbench for AVR using the Atmel ICE interfac...

Page 27: ...ally select the UPDI frequency Info If the selection of Debug Port mentioned in step 4 is grayed out the interface is preselected and the user can skip this configuration step Figure 7 7 Select Target...

Page 28: ...Figure 7 8 Select Debugger Figure 7 9 Configure Interface ATtiny1607 Curiosity Nano Appendix 2019 Microchip Technology Inc User Guide DS50002897A page 28...

Page 29: ...Representative Local Sales Office Embedded Solutions Engineer ESE Technical Support Customers should contact their distributor representative or ESE for support Local sales offices are also available...

Page 30: ...logo MOST MOST logo MPLAB OptoLyzer PackeTime PIC picoPower PICSTART PIC32 logo PolarFire Prochip Designer QTouch SAM BA SenGenuity SpyNIC SST SST Logo SuperFlash Symmetricom SyncServer Tachyon TempT...

Page 31: ...rein are property of their respective companies 2019 Microchip Technology Incorporated Printed in the U S A All Rights Reserved ISBN 978 1 5224 4662 0 Quality Management System For information regardi...

Page 32: ...7252 China Xiamen Tel 86 592 2388138 China Zhuhai Tel 86 756 3210040 India Bangalore Tel 91 80 3090 4444 India New Delhi Tel 91 11 4160 8631 India Pune Tel 91 20 4121 0141 Japan Osaka Tel 81 6 6152 7...

Reviews: