Benutzer:Robomu: Unterschied zwischen den Versionen
Robomu (Diskussion | Beiträge) (→Build avrdude with USB support from sources and configure udev to allow it access to AVRISP mkII) |
Robomu (Diskussion | Beiträge) (→Build avrdude with USB support from sources and configure udev to allow it access to AVRISP mkII) |
||
Zeile 11: | Zeile 11: | ||
To use the ATMEL USB programmer AVRISP mkII avrdude requires libusb support. Here is how to build it from sources: | To use the ATMEL USB programmer AVRISP mkII avrdude requires libusb support. Here is how to build it from sources: | ||
− | + | # Make sure that libusb and libusb-dev is installed on your system <br> | |
− | + | # Make sure that flex (substitute for lex) and bison (substitute for yacc) are installed on your system <br> | |
− | + | # Download source package (avrdude-5.10.tar.gz) from savannah.nongnu.org and transfer it to a local install folder and unpack it with tar -xvf <br> | |
− | + | # cd to your extracted avrdude-5.10 folder and run ./configure <br> | |
− | + | # check config.log and if no errors reportet run make and make config to install avrdude to /usr/local/bin/avrdude <br><br> | |
Since avrdude does not run under root during normal development you need to make sure that it is allowed to access the USB device associated to the AVRISP mkII. <br><br> | Since avrdude does not run under root during normal development you need to make sure that it is allowed to access the USB device associated to the AVRISP mkII. <br><br> | ||
− | + | # First use the command <em>lsusb</em> to identify the usb device associated to the Programmer showing it's name and the VendorID of ATMEL (03eb) and the Device ID of the AVRISP mkII (2104) | |
<pre> | <pre> | ||
Bus 002 Device 001: ID 0000:0000 | Bus 002 Device 001: ID 0000:0000 | ||
Zeile 23: | Zeile 23: | ||
Bus 001 Device 002: ID 03eb:2104 Atmel Corp. AVR ISP mkII | Bus 001 Device 002: ID 03eb:2104 Atmel Corp. AVR ISP mkII | ||
Bus 001 Device 001: ID 0000:0000 | Bus 001 Device 001: ID 0000:0000 | ||
+ | </pre> | ||
+ | |||
+ | Then identify the usb devices by issuing <em>ls -al /dev/usb*</em>: | ||
+ | <pre> | ||
+ | crw-rw---- 1 root root 254, 0 2010-02-05 16:30 /dev/usbdev1.1_ep00 | ||
+ | crw-rw---- 1 root root 254, 1 2010-02-05 16:30 /dev/usbdev1.1_ep81 | ||
+ | crw-rw---- 1 root root 254, 4 2010-02-05 16:30 /dev/usbdev1.2_ep00 | ||
+ | crw-rw---- 1 root root 254, 6 2010-02-05 16:30 /dev/usbdev1.2_ep02 | ||
+ | crw-rw---- 1 root root 254, 5 2010-02-05 16:30 /dev/usbdev1.2_ep82 | ||
+ | crw-rw---- 1 root root 254, 7 2010-02-05 16:30 /dev/usbdev1.3_ep00 | ||
+ | crw-rw---- 1 root root 254, 8 2010-02-05 16:30 /dev/usbdev1.3_ep81 | ||
+ | crw-rw---- 1 root root 254, 2 2010-02-05 16:30 /dev/usbdev2.1_ep00 | ||
+ | crw-rw---- 1 root root 254, 3 2010-02-05 16:30 /dev/usbdev2.1_ep81 | ||
</pre> | </pre> |
Version vom 5. Februar 2010, 20:21 Uhr
Ethersex Development using Eclipse Ganymede on Ubuntu 8.04 LTS
Eclipse may be used on Ubuntu 8.04 to work with the Ethersex Source Tree and even to directly flash the target from within Eclipse. However make menuconfig has to be run outside Eclipse since Eclipse does not provide a terminal window for running external tools. This article shows installation and configuration of
- avrdude with USB support for Atmel AVRISP mkII
- Eclipse Ganymede
and reports operating experiance.
Build avrdude with USB support from sources and configure udev to allow it access to AVRISP mkII
To use the ATMEL USB programmer AVRISP mkII avrdude requires libusb support. Here is how to build it from sources:
- Make sure that libusb and libusb-dev is installed on your system
- Make sure that flex (substitute for lex) and bison (substitute for yacc) are installed on your system
- Download source package (avrdude-5.10.tar.gz) from savannah.nongnu.org and transfer it to a local install folder and unpack it with tar -xvf
- cd to your extracted avrdude-5.10 folder and run ./configure
- check config.log and if no errors reportet run make and make config to install avrdude to /usr/local/bin/avrdude
Since avrdude does not run under root during normal development you need to make sure that it is allowed to access the USB device associated to the AVRISP mkII.
- First use the command lsusb to identify the usb device associated to the Programmer showing it's name and the VendorID of ATMEL (03eb) and the Device ID of the AVRISP mkII (2104)
Bus 002 Device 001: ID 0000:0000 Bus 001 Device 003: ID 0e0f:0002 Bus 001 Device 002: ID 03eb:2104 Atmel Corp. AVR ISP mkII Bus 001 Device 001: ID 0000:0000
Then identify the usb devices by issuing ls -al /dev/usb*:
crw-rw---- 1 root root 254, 0 2010-02-05 16:30 /dev/usbdev1.1_ep00 crw-rw---- 1 root root 254, 1 2010-02-05 16:30 /dev/usbdev1.1_ep81 crw-rw---- 1 root root 254, 4 2010-02-05 16:30 /dev/usbdev1.2_ep00 crw-rw---- 1 root root 254, 6 2010-02-05 16:30 /dev/usbdev1.2_ep02 crw-rw---- 1 root root 254, 5 2010-02-05 16:30 /dev/usbdev1.2_ep82 crw-rw---- 1 root root 254, 7 2010-02-05 16:30 /dev/usbdev1.3_ep00 crw-rw---- 1 root root 254, 8 2010-02-05 16:30 /dev/usbdev1.3_ep81 crw-rw---- 1 root root 254, 2 2010-02-05 16:30 /dev/usbdev2.1_ep00 crw-rw---- 1 root root 254, 3 2010-02-05 16:30 /dev/usbdev2.1_ep81