Atmel Ice Driver For Mac
2021年2月15日Download here: http://gg.gg/ob8hn
Description
This package provides access to the Atmel XDMAC (Extended DMA Controller) devices. This support is not intended to expose the full functionality of these devices. It is mainly limited to supporting peripheral DMA (e.g. USART, SPI, etc.). It is currently limited to single DMA transfers.
ATMEL AVR USB DRIVER FOR MAC. Ide atmel studio studio, avr programming device. Default atmel studio, usb controller raspi. Usb device atmel firmware. Buy atmel avr usb. Download atmel studio, integrated development environment atmel. Usb circuit atmega8, read atmel avr usb, atmel avr usb. Avr jungo usb software, free download avr jungo. The firmware Atmel Studio pushes onto it gets at JTAGICE3 very close to the way the Atmel-ICE works, i.e. They changed the product ID, and implemented a completely different protocol (based on HID - everything in Windows is a ’human interface’isn’t it?). It’s not that it’s completely out of the question to implement the stuff. The ATmega16U2 is loaded with a DFU bootloader, which can be activated by connecting the solder jumper on the back of the board and then resetting the 16U2. You can then use Atmel’s FLIP software (Windows) or the DFU programmer (Mac OS X and Linux) to load a new firmware. Gatweay released a replacement utilities. Generate Harmony atmel ice data gateway Step 8: This driver is Jungo version Review the Application Code Step 6: Configure Console System Service Step 7: Here is info that is posted gateqay Microsoft about using Preview beta testing program and the reason that some programs don’t work atmel ice data gateway because of the need for updated drivers.
There is currently no cross-platform/variant standardised eCos DMA I/O interface package, since DMA features and functionality vary greatly between architectures, and event within variants of an architecture. This stand-alone device package allows common DMA support to be shared between devices that implement Atmel DMA Controllers.
The user is directed towards the relevant Atmel documentation for a full description of the XDMAC devices, and to the variant device drivers for examples of the use of this API. This documentation only gives a brief description of the functions available.
The API of this controller is designed to be compatible with that for the Atmel DMAC controller and is a drop-in replacement for it. Thus the API refers to the DMAC in its naming, not the XDMAC.
A XDMAC instance is defined by a controller number (0 or 1), and each controller has support for a number of (variant defined) channels. The API uses a simple 32-bit encoding to describe how a specific DMA channel should be used, with this package providing helper macros to combine the necessary information into a unique descriptor. These descriptors may be stored with a device driver as required.
The following are examples of how definitions can be made:
Before DMA transfers can be performed, a DMA channel must be claimed. This is done by calling atmel_dmac_chan_alloc(). The descriptor argument describes the majority of the DMA transfer configuration that will be used. As shown in the examples above the passed descriptor not only encodes the source and destination interfaces, but also the transfer sizes. Also, depending on the descriptor construction macros used, it is possible to control the direction and modification of addresses during transfers. The cb argument is used to register a client function that will be called when a requested transfer completes. The priv argument is a client specified value that will be passed to the callback function, and can be used to reference client driver specific data.
The atmel_dmac_chan_config() function is present for compatibility with the DMAC driver. It is not currently needed, but device drivers that may use both drivers may call this with not effect.
Most drivers will allocate a DMA channel object and keep it active throughout the system lifetime. However, if it is necessary to share a channel, or otherwise disable the use of a stream, the driver may call atmel_dmac_chan_free() to return a channel to an unused state. It will be necessary to call atmel_dmac_chan_alloc() before specific DMA descriptor operations can be performed again.
The register callback function has the following prototype:
The ch is the channel structure describing the transfer. The cbid argument is a completion identifier:
Table 110.1. Completion CodesCYGHWR_ATMEL_DMA_COMPLETE A valid transfer completion. The count argument should match the size passed to the atmel_dmac_start() call. CYGHWR_ATMEL_DMA_AHBERR This code indicates that the DMA Controller has detected an AHB read or write access error. This may indicate invalid memory addresses have been passed, or invalid AHB_IF mappings have been used. CYGHWR_ATMEL_DMA_DICERR For configurations where Descriptor Integrity Check support is available, and enabled, then if an error is detected in a referenced memory-based transfer structure this result will be raised.
The count argument is the number of data items successfully transferred. The data argument is the client private data registered for the callback.
A transfer is configured and started by calling atmel_dmac_start(). The ch argument describes the DMA channel, with the descriptor used when allocating the channel defining how the other arguments are used. The src argument defines the peripheral or memory address from which the transfer will be made. The dst argument supplies the peripheral or memory address to which the transfer will write. The size argument defines the number of data items to be transferred. Once this function call completes the channel is operational and will transfer data once the relevant peripheral starts triggering transfers.
When the transfer completes the registered callback is called from DSR mode.Notes:
* Since the callback function is executed as a DSR, only a subset of eCos operations are valid.
* It is expected that the client driver will perform any necessary CACHE operations within either its supplied callback handler functions, or before calling atmel_dmac_start() as required. Introduction: Atmel Startup 1: Atmel Studio and Programmer
M. A. Parker c2015
Installing Atmel Studio (AS) and a programmer embody the first steps [0] on the path to using an individual Atmel AVR Microcontroller unit MCU [1] as opposed to the MCU-on-a-board such as Arduino [2]. Here starts the journey, albeit rather short, through a series of ‘Startup’ Instructables [0] focusing on ‘getting started’ with the Atmel MCU. Along the way, the series (Startup 5) shows how to construct the ‘Lifeline’ to fix wrongly set fuse bits – a simplest of projects but useful to the expert and makes a nice gift. This initial Startup describes the setup of the Atmel Studio and Programmer and the construction of an adapter cable for connecting the programmer to an experimenter’s board. Startup 2 describes the construction of a ‘platform’ circuit on an experimenter’s breadboard used to set the internal fuse bits of the MCU. The circuit will be used for the remaining three Startup Instructables. Startups 3 and 4 use the platform to demonstrate ‘Blinky’, the blinking LED, and to describe the ‘secret’ life of the Atmel PORT, PIN and DDR registers and pull-up resistors. Atmel Ice Driver For Mac Os
**NOTE: For those wanting the PDF of this instructable, download the attached PDF using the below link rather than the one automatically generated by the website - that automation does not maintain the association of the captions with the pictures.
We began using the Atmel MCUs in the early 2000s in order to create Data Acquisition units for experiments with IC fabrication and for demonstrating a unique multichannel noise communicator. Similar to other people, we had to learn certain well published ‘secrets’ of the Atmel AVR Microcontroller including, at the most basic level, the Data Direction Register DDR, PORT versus PIN and the USART data format (inverted). Fortunately, a consulting firm supplying our MCU needs, also provided assistance for ‘getting started’ and pointers on the ‘secrets’. While planning to publish some MCU projects, it seemed reasonable to pass along the favor by providing some ‘Getting Started’ guides, although in considerably more detail, so that other interested people might benefit.
This Instructable provides an introduction to using a single Atmel MCU. Although we start with the ATTiny2313A [3], the discussion applies to the popular Atmel AVRs (8bit) such as the ATMega328p (of Arduino fame). With the single Atmel MCUs, the builder controls all the options and expends much less cash than for the larger and more expensive Arduinos [2]. The 2313A have a price of about $1 each and the budding experimenter will be much less traumatized if a couple should go up in smoke. Future articles will center on other Atmel MCUs such as the ATMega328p and the SAM line. On the other hand, the remarkable Raspberry PIs [4] run Linux with plenty of USB peripherals but uses an event driven architecture that limits real time data acquisition.
The Atmel Studio 6.2 (AS6) software provides an Integrated Development Environment (IDE) which, among other features, (i) allows the user to type programming statements, (ii) compiles the programming statements into proper MCU syntax (i.e., hex code), (iii) transfers the MCU code to a programmer usually attached to a USB port, and (iv)saves/retrieves programs from disk. AS6 will function with any of the Atmel MCUs including AVR (i.e., 8 bit) and SAM (i.e., 32bit). The programmer generates the necessary signals onto the MCU’s Serial Peripheral Interface SPI pins that engage and synchronize the MCU’s internal ‘In-System Programmer ISP’ [5]. In short, the programmer transfers the code to the MCU. Atmel Studio provides C and C++ compilers which convert programming statements into MCU syntax/Hex code.
This instructable includes notes on tools toward the end and some references for the programmer. However, the majority of the reference/tutorial links for electronic components and C/C++ will be found over the next several installations of the Startup series where they will be used.AttachmentsStep 1: Atmel Studio: Download and Install
Figure 2: Activate the Numbers option by using: Tools>Options>Text Editor> All Languages>General
Use the following items to download, install and initialize AS6 on a computer with a USB port compatible with the programmer chosen in Step 2.
*
Download Atmel Studio (free of charge) from [6]
http://www.atmel.com/tools/atmelstudio.aspx .
You will be asked to register as a guest if you don’t already have an account. Atmel has recently opened service offices around the world rather than the central office. Atmel has also initiated new (free) memberships with ‘MyAtmel’ that is worth the effort to register for downloads and assistance.
* Install AS. USB drivers will also be installed. The process can be quite slow.
*
Activate the line numbers for the coding page as follows [Figure 2]. The line numbers will be listed on the left side of the coding page so that each program line will have its own number. When the program is compiled, AS will present any syntactic errors in an ‘Error List’ along with the line number. Unfortunately, the AS menu item to enable the line numbers is always well hidden. Perform the following:
Select the Tools menu item in the AS6 top menu strip. Select Options at the bottom.
In the left hand tree, scroll down until ‘Text Editor’ becomes visible.
Left click the small “+” next to the title ‘Text Editor’.
Left click the small “+” next to “All Languages”
Select ‘General’
On the right hand side, place a check mark in the ‘Line numbers’ under the ‘Display heading’.
Click OK. Step 2: Obtain a Programmer
Figure 3: Atmel ICE (left) and AVRISP mkII (right) programmers. The Basic version for ICE includes the USB cable and the cable 2nd from the top left.
Procure a programmer already known to be compatible with AS6 such as the Atmel ICE [7]. Digikey.com as an Atmel Distributor and Mouser.com offer the ATATMEL-ICE-BASIC (~ $55) and Atmel ATATMEL-ICE (~ $96) shown in Figure 3. The ‘basic’ version does not include all the adapters of the full version [7] but it does include the 6-pin adapter needed for the present project and most other AVR projects. The Atmel-ICE can be used with either the Atmel AVR MCUs (8bit) or with the Atmel SAM (32bit) MCUs that have the ARM cores. Unfortunately, the programming cable accompanying the ICE is rather flimsy and will require care not to break the wires. Perhaps some method of securing the wires could be developed. The older Atmel ‘AVRISP mkII’ (a.k.a. AVR USB MKII) was the workhorse programmer for Atmel AVR (8bit MCUs); however, neither Digikey nor Atmel sell it although eBay might have some (Figure 3). It’s probably not a good idea to buy a look-alike unit [8-10] without being certain of its compatibility with AS. Digikey sells an Olimex unit [8] with stock number AVR-ISP-mk2 (~$30) that Olimex claims to work with AS6. We have not tried the Olimex unit. The The ICE unit works great with fewer installation problems. The AVRISP should probably be avoided.
The following two steps show how to install the Atmel-ICE programmer and the AVR-ISP mkII programmer. Step 3: Atmel ATATMEL-ICE-BASIC Installation
Figure 4: Look for the ‘Apply’ button: Tools>Device Programming.
The Atmel ICE debugger/programmer uses native Windows drivers and those loaded by AS. After installing AS6 as in Step 1 above, install the Atmel ICE as follows.
*
Close AS6 if it’s open.
*
Attach the Atmel ICE to the computer USB port using the supplied USB cable. The computer shows a status message that the Atmel ICE drivers are installing.
*
Attach the ribbon cable to the AVR side of the programmer.
*
Attach the programmer to the PC USB port.
*
Start AS6.
*
Run the Windows Device Manager on the PC by using one of the following methods. Choose the method easiest for your Windows Installation. We have tested both Windows 7 and 8.
6.A Device Manager A:
Win7: Click Start (lower left), open Control Panel, double click Device Manager
Win8: Right click Windows symbol (lower left), click Control Panel, Double click Device Manager
6.B Device Manager B:
Win7: Click ‘Start’ on the PC, right click ‘Computer’, left click ‘manage’.
Win8: Right click Windows symbol (lower left), click Device Manager.
6.C Device Manager C:
Win7: Click ‘Start’ on the PC, enter the words Device Manager into the text search box.
Win8: In Start Screen (with active tiles), Click magnifying glass (upper right) or just start typing Device Manager, and then select Device Manager.
6.D Device Manager D:
Win7 or Win8: Open AS6, then click the top menu sequence: Tools > Command Prompt; then type Device Manager.
6.E Device Manager E:
Win7 or Win8: Open windows explorer and navigate to C:WindowsSystem32. Click ‘cmd.run’ then type Device Manager.
*
Verify programmer installation
7.A In Device Manager, click the + next to ‘Human Interface Devices’ and verify the presence of the item ‘USB Input Device’. Unplugging the programmer should eliminate the relevant ‘USB Input Device’ item. Make sure to reattach the programmer.
7.B In AS, open the top menu sequence View > Available Atmel Tools and verify that the ICE programmer is listed.
*
Select the menu item ‘Tools’ and then ‘Device Programming’. Select the ‘Tool’ drop down box and make sure that the ‘Atmel ICE’ option appears. Select the ICE programmer and ISP interface. Proceed to the next step without closing the Device Programming dialog.
*
Click the ‘Apply’ button if able to do so (Figure 4) – the ‘apply’ button might not be available until loading a Solution (i.e., program). Most likely AS will want to upgrade the programmer firmware prior to its first use. Go ahead and update. Sometimes an error occurs and the programmer looks dead and the programmer no longer appears in the Tools > Device Programming drop down box and under the View > Available Atmel Tools. Don’t panic, proceed to Step 5 below. If the ‘Apply’ button was not enabled, remember to return to this step if/when the update occurs. Step 4: Obsolete: Installing Atmel AVRISP MkII
As previously mentioned, the AVRISP mkII will work with AS6.2 but it is not recommended for use here especially given that (i) it will not work with 32bit Atmel SAM MCUs, (ii) it’s price approaches that of the ICE, and (iii) the installation can be more problematic.
*
Install the drivers for the AVRISP MKII which can be found on the CD/DVD accompanying the programmer.
*
Attach the AVR USB MKII programmer to the computer USB port if not already attached. Allow any drivers to fully load.
*
Open Windows Device Manager by using one of the following methods easiest for your Windows Installation.
3.A Device Manage A:
Win7: Click Start (lower left), open Control Panel, double click Device Manager
Win8: Right click Windows symbol (lower left), click Control Panel, Double click Device Manager
3.B Device Manager B:
Win7: Click ‘Start’ on the PC, right click ‘Computer’, left click ‘manage’.
Win8: Right click Windows symbol (lower left), click Device Manager.
3.C Device Manager C:
Win7: Click ‘Start’ on the PC, enter the words Device Manager into the text search box.
Win8: In Start Screen (with active tiles), Click magnifying glass (upper right) or just start typing Device Manager, and then select Device Manager.
3.D Win7 or Win8: Open AS6, then click the top menu sequence: Tools > Command Prompt then type Device Manager.
3.E Win7 or Win8: Open windows explorer and navigate to C:WindowsSystem32. Click ‘cmd.run’ then type Device Manager.
*
The tree of items in Device Manager should have an entry called Jungo with sub-entries ‘AVRISP mkII’ and ‘WinDriver’. If you skipped item 1, then you might see the error ‘No driver found’.
*
In our case, we had to download Ria Services from Microsoft and then the computer would not load the installation package for DotfuscatorCE5.0.2500.msi. An internet search on that file name provided a solution at social.msdn.mincrosoft.com.
*
Start AS6.
*
Verify the AVRISP appears under top menu sequence View > Available Atmel Tools.
*
Select the menu item ‘Tools’ and then ‘Device Programming’. Select the ‘Tool’ drop down box and make sure that the ‘AVRISP’ option appears. Select the AVRISP programmer and ISP interface. Proceed to the next item without closing the Device Programming dialog.
*
Click the ‘Apply’ button if able to do so (Figure 4) – the ‘apply’ button might not be available until loading a Solution (i.e., program). Go ahead and update. Sometimes an error occurs and the programmer looks dead and the programmer no longer appears in the Tools > Device Programming drop down box and under the View > Available Atmel Tools. In such a
https://diarynote-jp.indered.space
Description
This package provides access to the Atmel XDMAC (Extended DMA Controller) devices. This support is not intended to expose the full functionality of these devices. It is mainly limited to supporting peripheral DMA (e.g. USART, SPI, etc.). It is currently limited to single DMA transfers.
ATMEL AVR USB DRIVER FOR MAC. Ide atmel studio studio, avr programming device. Default atmel studio, usb controller raspi. Usb device atmel firmware. Buy atmel avr usb. Download atmel studio, integrated development environment atmel. Usb circuit atmega8, read atmel avr usb, atmel avr usb. Avr jungo usb software, free download avr jungo. The firmware Atmel Studio pushes onto it gets at JTAGICE3 very close to the way the Atmel-ICE works, i.e. They changed the product ID, and implemented a completely different protocol (based on HID - everything in Windows is a ’human interface’isn’t it?). It’s not that it’s completely out of the question to implement the stuff. The ATmega16U2 is loaded with a DFU bootloader, which can be activated by connecting the solder jumper on the back of the board and then resetting the 16U2. You can then use Atmel’s FLIP software (Windows) or the DFU programmer (Mac OS X and Linux) to load a new firmware. Gatweay released a replacement utilities. Generate Harmony atmel ice data gateway Step 8: This driver is Jungo version Review the Application Code Step 6: Configure Console System Service Step 7: Here is info that is posted gateqay Microsoft about using Preview beta testing program and the reason that some programs don’t work atmel ice data gateway because of the need for updated drivers.
There is currently no cross-platform/variant standardised eCos DMA I/O interface package, since DMA features and functionality vary greatly between architectures, and event within variants of an architecture. This stand-alone device package allows common DMA support to be shared between devices that implement Atmel DMA Controllers.
The user is directed towards the relevant Atmel documentation for a full description of the XDMAC devices, and to the variant device drivers for examples of the use of this API. This documentation only gives a brief description of the functions available.
The API of this controller is designed to be compatible with that for the Atmel DMAC controller and is a drop-in replacement for it. Thus the API refers to the DMAC in its naming, not the XDMAC.
A XDMAC instance is defined by a controller number (0 or 1), and each controller has support for a number of (variant defined) channels. The API uses a simple 32-bit encoding to describe how a specific DMA channel should be used, with this package providing helper macros to combine the necessary information into a unique descriptor. These descriptors may be stored with a device driver as required.
The following are examples of how definitions can be made:
Before DMA transfers can be performed, a DMA channel must be claimed. This is done by calling atmel_dmac_chan_alloc(). The descriptor argument describes the majority of the DMA transfer configuration that will be used. As shown in the examples above the passed descriptor not only encodes the source and destination interfaces, but also the transfer sizes. Also, depending on the descriptor construction macros used, it is possible to control the direction and modification of addresses during transfers. The cb argument is used to register a client function that will be called when a requested transfer completes. The priv argument is a client specified value that will be passed to the callback function, and can be used to reference client driver specific data.
The atmel_dmac_chan_config() function is present for compatibility with the DMAC driver. It is not currently needed, but device drivers that may use both drivers may call this with not effect.
Most drivers will allocate a DMA channel object and keep it active throughout the system lifetime. However, if it is necessary to share a channel, or otherwise disable the use of a stream, the driver may call atmel_dmac_chan_free() to return a channel to an unused state. It will be necessary to call atmel_dmac_chan_alloc() before specific DMA descriptor operations can be performed again.
The register callback function has the following prototype:
The ch is the channel structure describing the transfer. The cbid argument is a completion identifier:
Table 110.1. Completion CodesCYGHWR_ATMEL_DMA_COMPLETE A valid transfer completion. The count argument should match the size passed to the atmel_dmac_start() call. CYGHWR_ATMEL_DMA_AHBERR This code indicates that the DMA Controller has detected an AHB read or write access error. This may indicate invalid memory addresses have been passed, or invalid AHB_IF mappings have been used. CYGHWR_ATMEL_DMA_DICERR For configurations where Descriptor Integrity Check support is available, and enabled, then if an error is detected in a referenced memory-based transfer structure this result will be raised.
The count argument is the number of data items successfully transferred. The data argument is the client private data registered for the callback.
A transfer is configured and started by calling atmel_dmac_start(). The ch argument describes the DMA channel, with the descriptor used when allocating the channel defining how the other arguments are used. The src argument defines the peripheral or memory address from which the transfer will be made. The dst argument supplies the peripheral or memory address to which the transfer will write. The size argument defines the number of data items to be transferred. Once this function call completes the channel is operational and will transfer data once the relevant peripheral starts triggering transfers.
When the transfer completes the registered callback is called from DSR mode.Notes:
* Since the callback function is executed as a DSR, only a subset of eCos operations are valid.
* It is expected that the client driver will perform any necessary CACHE operations within either its supplied callback handler functions, or before calling atmel_dmac_start() as required. Introduction: Atmel Startup 1: Atmel Studio and Programmer
M. A. Parker c2015
Installing Atmel Studio (AS) and a programmer embody the first steps [0] on the path to using an individual Atmel AVR Microcontroller unit MCU [1] as opposed to the MCU-on-a-board such as Arduino [2]. Here starts the journey, albeit rather short, through a series of ‘Startup’ Instructables [0] focusing on ‘getting started’ with the Atmel MCU. Along the way, the series (Startup 5) shows how to construct the ‘Lifeline’ to fix wrongly set fuse bits – a simplest of projects but useful to the expert and makes a nice gift. This initial Startup describes the setup of the Atmel Studio and Programmer and the construction of an adapter cable for connecting the programmer to an experimenter’s board. Startup 2 describes the construction of a ‘platform’ circuit on an experimenter’s breadboard used to set the internal fuse bits of the MCU. The circuit will be used for the remaining three Startup Instructables. Startups 3 and 4 use the platform to demonstrate ‘Blinky’, the blinking LED, and to describe the ‘secret’ life of the Atmel PORT, PIN and DDR registers and pull-up resistors. Atmel Ice Driver For Mac Os
**NOTE: For those wanting the PDF of this instructable, download the attached PDF using the below link rather than the one automatically generated by the website - that automation does not maintain the association of the captions with the pictures.
We began using the Atmel MCUs in the early 2000s in order to create Data Acquisition units for experiments with IC fabrication and for demonstrating a unique multichannel noise communicator. Similar to other people, we had to learn certain well published ‘secrets’ of the Atmel AVR Microcontroller including, at the most basic level, the Data Direction Register DDR, PORT versus PIN and the USART data format (inverted). Fortunately, a consulting firm supplying our MCU needs, also provided assistance for ‘getting started’ and pointers on the ‘secrets’. While planning to publish some MCU projects, it seemed reasonable to pass along the favor by providing some ‘Getting Started’ guides, although in considerably more detail, so that other interested people might benefit.
This Instructable provides an introduction to using a single Atmel MCU. Although we start with the ATTiny2313A [3], the discussion applies to the popular Atmel AVRs (8bit) such as the ATMega328p (of Arduino fame). With the single Atmel MCUs, the builder controls all the options and expends much less cash than for the larger and more expensive Arduinos [2]. The 2313A have a price of about $1 each and the budding experimenter will be much less traumatized if a couple should go up in smoke. Future articles will center on other Atmel MCUs such as the ATMega328p and the SAM line. On the other hand, the remarkable Raspberry PIs [4] run Linux with plenty of USB peripherals but uses an event driven architecture that limits real time data acquisition.
The Atmel Studio 6.2 (AS6) software provides an Integrated Development Environment (IDE) which, among other features, (i) allows the user to type programming statements, (ii) compiles the programming statements into proper MCU syntax (i.e., hex code), (iii) transfers the MCU code to a programmer usually attached to a USB port, and (iv)saves/retrieves programs from disk. AS6 will function with any of the Atmel MCUs including AVR (i.e., 8 bit) and SAM (i.e., 32bit). The programmer generates the necessary signals onto the MCU’s Serial Peripheral Interface SPI pins that engage and synchronize the MCU’s internal ‘In-System Programmer ISP’ [5]. In short, the programmer transfers the code to the MCU. Atmel Studio provides C and C++ compilers which convert programming statements into MCU syntax/Hex code.
This instructable includes notes on tools toward the end and some references for the programmer. However, the majority of the reference/tutorial links for electronic components and C/C++ will be found over the next several installations of the Startup series where they will be used.AttachmentsStep 1: Atmel Studio: Download and Install
Figure 2: Activate the Numbers option by using: Tools>Options>Text Editor> All Languages>General
Use the following items to download, install and initialize AS6 on a computer with a USB port compatible with the programmer chosen in Step 2.
*
Download Atmel Studio (free of charge) from [6]
http://www.atmel.com/tools/atmelstudio.aspx .
You will be asked to register as a guest if you don’t already have an account. Atmel has recently opened service offices around the world rather than the central office. Atmel has also initiated new (free) memberships with ‘MyAtmel’ that is worth the effort to register for downloads and assistance.
* Install AS. USB drivers will also be installed. The process can be quite slow.
*
Activate the line numbers for the coding page as follows [Figure 2]. The line numbers will be listed on the left side of the coding page so that each program line will have its own number. When the program is compiled, AS will present any syntactic errors in an ‘Error List’ along with the line number. Unfortunately, the AS menu item to enable the line numbers is always well hidden. Perform the following:
Select the Tools menu item in the AS6 top menu strip. Select Options at the bottom.
In the left hand tree, scroll down until ‘Text Editor’ becomes visible.
Left click the small “+” next to the title ‘Text Editor’.
Left click the small “+” next to “All Languages”
Select ‘General’
On the right hand side, place a check mark in the ‘Line numbers’ under the ‘Display heading’.
Click OK. Step 2: Obtain a Programmer
Figure 3: Atmel ICE (left) and AVRISP mkII (right) programmers. The Basic version for ICE includes the USB cable and the cable 2nd from the top left.
Procure a programmer already known to be compatible with AS6 such as the Atmel ICE [7]. Digikey.com as an Atmel Distributor and Mouser.com offer the ATATMEL-ICE-BASIC (~ $55) and Atmel ATATMEL-ICE (~ $96) shown in Figure 3. The ‘basic’ version does not include all the adapters of the full version [7] but it does include the 6-pin adapter needed for the present project and most other AVR projects. The Atmel-ICE can be used with either the Atmel AVR MCUs (8bit) or with the Atmel SAM (32bit) MCUs that have the ARM cores. Unfortunately, the programming cable accompanying the ICE is rather flimsy and will require care not to break the wires. Perhaps some method of securing the wires could be developed. The older Atmel ‘AVRISP mkII’ (a.k.a. AVR USB MKII) was the workhorse programmer for Atmel AVR (8bit MCUs); however, neither Digikey nor Atmel sell it although eBay might have some (Figure 3). It’s probably not a good idea to buy a look-alike unit [8-10] without being certain of its compatibility with AS. Digikey sells an Olimex unit [8] with stock number AVR-ISP-mk2 (~$30) that Olimex claims to work with AS6. We have not tried the Olimex unit. The The ICE unit works great with fewer installation problems. The AVRISP should probably be avoided.
The following two steps show how to install the Atmel-ICE programmer and the AVR-ISP mkII programmer. Step 3: Atmel ATATMEL-ICE-BASIC Installation
Figure 4: Look for the ‘Apply’ button: Tools>Device Programming.
The Atmel ICE debugger/programmer uses native Windows drivers and those loaded by AS. After installing AS6 as in Step 1 above, install the Atmel ICE as follows.
*
Close AS6 if it’s open.
*
Attach the Atmel ICE to the computer USB port using the supplied USB cable. The computer shows a status message that the Atmel ICE drivers are installing.
*
Attach the ribbon cable to the AVR side of the programmer.
*
Attach the programmer to the PC USB port.
*
Start AS6.
*
Run the Windows Device Manager on the PC by using one of the following methods. Choose the method easiest for your Windows Installation. We have tested both Windows 7 and 8.
6.A Device Manager A:
Win7: Click Start (lower left), open Control Panel, double click Device Manager
Win8: Right click Windows symbol (lower left), click Control Panel, Double click Device Manager
6.B Device Manager B:
Win7: Click ‘Start’ on the PC, right click ‘Computer’, left click ‘manage’.
Win8: Right click Windows symbol (lower left), click Device Manager.
6.C Device Manager C:
Win7: Click ‘Start’ on the PC, enter the words Device Manager into the text search box.
Win8: In Start Screen (with active tiles), Click magnifying glass (upper right) or just start typing Device Manager, and then select Device Manager.
6.D Device Manager D:
Win7 or Win8: Open AS6, then click the top menu sequence: Tools > Command Prompt; then type Device Manager.
6.E Device Manager E:
Win7 or Win8: Open windows explorer and navigate to C:WindowsSystem32. Click ‘cmd.run’ then type Device Manager.
*
Verify programmer installation
7.A In Device Manager, click the + next to ‘Human Interface Devices’ and verify the presence of the item ‘USB Input Device’. Unplugging the programmer should eliminate the relevant ‘USB Input Device’ item. Make sure to reattach the programmer.
7.B In AS, open the top menu sequence View > Available Atmel Tools and verify that the ICE programmer is listed.
*
Select the menu item ‘Tools’ and then ‘Device Programming’. Select the ‘Tool’ drop down box and make sure that the ‘Atmel ICE’ option appears. Select the ICE programmer and ISP interface. Proceed to the next step without closing the Device Programming dialog.
*
Click the ‘Apply’ button if able to do so (Figure 4) – the ‘apply’ button might not be available until loading a Solution (i.e., program). Most likely AS will want to upgrade the programmer firmware prior to its first use. Go ahead and update. Sometimes an error occurs and the programmer looks dead and the programmer no longer appears in the Tools > Device Programming drop down box and under the View > Available Atmel Tools. Don’t panic, proceed to Step 5 below. If the ‘Apply’ button was not enabled, remember to return to this step if/when the update occurs. Step 4: Obsolete: Installing Atmel AVRISP MkII
As previously mentioned, the AVRISP mkII will work with AS6.2 but it is not recommended for use here especially given that (i) it will not work with 32bit Atmel SAM MCUs, (ii) it’s price approaches that of the ICE, and (iii) the installation can be more problematic.
*
Install the drivers for the AVRISP MKII which can be found on the CD/DVD accompanying the programmer.
*
Attach the AVR USB MKII programmer to the computer USB port if not already attached. Allow any drivers to fully load.
*
Open Windows Device Manager by using one of the following methods easiest for your Windows Installation.
3.A Device Manage A:
Win7: Click Start (lower left), open Control Panel, double click Device Manager
Win8: Right click Windows symbol (lower left), click Control Panel, Double click Device Manager
3.B Device Manager B:
Win7: Click ‘Start’ on the PC, right click ‘Computer’, left click ‘manage’.
Win8: Right click Windows symbol (lower left), click Device Manager.
3.C Device Manager C:
Win7: Click ‘Start’ on the PC, enter the words Device Manager into the text search box.
Win8: In Start Screen (with active tiles), Click magnifying glass (upper right) or just start typing Device Manager, and then select Device Manager.
3.D Win7 or Win8: Open AS6, then click the top menu sequence: Tools > Command Prompt then type Device Manager.
3.E Win7 or Win8: Open windows explorer and navigate to C:WindowsSystem32. Click ‘cmd.run’ then type Device Manager.
*
The tree of items in Device Manager should have an entry called Jungo with sub-entries ‘AVRISP mkII’ and ‘WinDriver’. If you skipped item 1, then you might see the error ‘No driver found’.
*
In our case, we had to download Ria Services from Microsoft and then the computer would not load the installation package for DotfuscatorCE5.0.2500.msi. An internet search on that file name provided a solution at social.msdn.mincrosoft.com.
*
Start AS6.
*
Verify the AVRISP appears under top menu sequence View > Available Atmel Tools.
*
Select the menu item ‘Tools’ and then ‘Device Programming’. Select the ‘Tool’ drop down box and make sure that the ‘AVRISP’ option appears. Select the AVRISP programmer and ISP interface. Proceed to the next item without closing the Device Programming dialog.
*
Click the ‘Apply’ button if able to do so (Figure 4) – the ‘apply’ button might not be available until loading a Solution (i.e., program). Go ahead and update. Sometimes an error occurs and the programmer looks dead and the programmer no longer appears in the Tools > Device Programming drop down box and under the View > Available Atmel Tools. In such a
https://diarynote-jp.indered.space
コメント