Hallo Leute, mit einem Raspberry wollte ich ein MKII Board von myAVR programmieren (als Übung). Beim aufspielen eines simplen Testprogrammes aus dem www meldet sich der PI mit dem folgenden Fehler: pi@raspberrypi:~ $ avrdude -c avrispmkii -p m8 -U flash:w:test_leds.hex avrdude: usbdev_open(): did not find any USB device "usb" (0x03eb:0x2104) avrdude done. Thank you. Mir scheint aber, das der PI die USB Komponenten alle richtig erkennt: pi@raspberrypi:~ $ lsusb Bus 001 Device 007: ID 0461:4d20 Primax Electronics, Ltd HP Optical Mouse Bus 001 Device 010: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light Bus 001 Device 005: ID 04f2:0116 Chicony Electronics Co., Ltd KU-2971/KU-0325 Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@raspberrypi:~ $ dmesg | tail [ 3220.024478] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 3220.024566] cp210x 1-1.4:1.0: device disconnected [ 3221.793142] usb 1-1.4: new full-speed USB device number 10 using dwc_otg [ 3221.903285] usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60 [ 3221.903314] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3221.903332] usb 1-1.4: Product: myAVR - mySmartUSB MK2 [ 3221.903348] usb 1-1.4: Manufacturer: Silicon Labs [ 3221.903364] usb 1-1.4: SerialNumber: mySmartUSB2-0001 [ 3221.906284] cp210x 1-1.4:1.0: cp210x converter detected [ 3221.906765] usb 1-1.4: cp210x converter now attached to ttyUSB0 Nach 2Std suchen und "rumprobieren" sehe ich wahrscheinlich den Wald vor lauter Bäumen nicht mehr. Hat jemand von Euch noch eine Idee warum ich die Fehlermeldung bekomme?? Besten Dank Gruß
da1l6 schrieb: > Hallo > > Der mySmartUSB MK2 ist kein AVRISPMKii ! > > da1l6 Danke für die Antwort Und weißt Du auch was es dann ist. In der Liste bin ich nach dem Namem von Board gegangen Danke Gruß
da1l6 schrieb: > Hallo > > Der mySmartUSB MK2 ist kein AVRISPMKii ! > > da1l6 Vielleicht meldet sich auch das Board falsch. Weil ich das hier gekauft habe: http://shop.myavr.de/Systemboards%20und%20Programmer/myAVR%20Board%20MK2,%20best%C3%BCckt.htm?sp=article.sp.php&artID=40 Gruß
Kuckst du hier im Wiki https://www.mikrocontroller.net/articles/AVRDUDE#mysmartUSB_V2.11_und_ATtiny_13 Grüße,
nicht"Gast" schrieb: > Kuckst du hier im Wiki > > https://www.mikrocontroller.net/articles/AVRDUDE#m... > > Grüße, Sorry aber das verstehe ich leider nicht Das Board hat meines Wissens nach einen ATMEGA8 drauf und ich habe ein Linux System. Wo kann ich in der Wiki dort Hilfe finden...? Danke Gruß
Nun, weil da in der ersten Zeile im passenden Absatz folgendes zu finden ist: mysmartUSB V2.11 verlangt -cavr910 als Programmer. Ist das jetzt so schwer, sich mal den Text durchzulesen?
nicht"Gast" schrieb: > Nun, weil da in der ersten Zeile im passenden Absatz folgendes zu > finden > ist: > > mysmartUSB V2.11 verlangt -cavr910 als Programmer. > > Ist das jetzt so schwer, sich mal den Text durchzulesen? D.h., mein AVR MK2 Board meldet sich als "mysmartUSB V2.11"....das verstehe ich nicht...habe ich so auch noch nicht im www gelesen Nun bekomme ich die folgenden Fehlermeldung: pi@raspberrypi:~ $ avrdude -cavr910 -p m8 -U flash:w:test_leds.hex avrdude: ser_open(): can't open device "/dev/ttyS0": No such file or directory avrdude done. Thank you.
Laut deinem diese ist das Teil ja als ttyUSB in /dev und nicht als ttySO Gruß JackFrost
>can't open device "/dev/ttyS0
steht doch im klartext da. dein port heißt /dev/ttyUSB0 !
Hans B. schrieb: > Nun bekomme ich die folgenden Fehlermeldung: > pi@raspberrypi:~ $ avrdude -cavr910 -p m8 -U flash:w:test_leds.hex > avrdude: ser_open(): can't open device "/dev/ttyS0": No such file or > directory > avrdude done. Thank you. Hans B. schrieb: > [ 3221.903332] usb 1-1.4: Product: myAVR - mySmartUSB MK2 > [ 3221.903348] usb 1-1.4: Manufacturer: Silicon Labs > [ 3221.903364] usb 1-1.4: SerialNumber: mySmartUSB2-0001 > [ 3221.906284] cp210x 1-1.4:1.0: cp210x converter detected > [ 3221.906765] usb 1-1.4: cp210x converter now attached to ttyUSB0 Ich weiß, ich könnte es auch gleich sagen und es ist so nicht die feine, nette Art. Fällt dir ein Unterschied auf? Hinweis: Den Port kann man mit -P beim avrdude angeben.
Ihr werdet mich bestimmt jetzt alle Erschlagen....ich probier es trotzdem mal Um ehrlich zu sein...ich stehe total aufm Schlauch (bin aber auch ein Newbie) pi@raspberrypi:~ $ avrdude -P usb -cavr910 -p m8 -U flash:w:test_leds.hex avrdude: ser_open(): can't open device "usb": No such file or directory avrdude done. Thank you.
Hoffnungslos^^ gibt statt "-P usb" als Port doch bitte mal "-P /deb/ttyUSB0" an. Verabschiede dich von dem Gedanken, dass du ein USB Programmer hast. Da ist nur ein USB-Seriell Wandler drauf, der einen virtuellen Com Port auf deinem Rechner erzeugt. Das Ding kommuniziert über eine RS232.
Das ist der Output
pi@raspberrypi:~/Desktop $ avrdude -P /dev/ttyUSB0 -cavr910 -p m8 -U
flash:w:test_leds.hex
Found programmer: Id = "AVR ISP"; type = S
Software Version = 2.5; Hardware Version = 2.0
Programmer supports auto addr increment.
Programmer supports buffered memory access with buffersize = 512 bytes.
Programmer supports the following devices:
Device code: 0x01 = (unknown)
Device code: 0x02 = (unknown)
Device code: 0x03 = (unknown)
Device code: 0x04 = (unknown)
Device code: 0x05 = (unknown)
Device code: 0x06 = (unknown)
Device code: 0x07 = (unknown)
Device code: 0x08 = (unknown)
Device code: 0x09 = (unknown)
Device code: 0x0a = (unknown)
Device code: 0x0b = (unknown)
Device code: 0x0c = (unknown)
Device code: 0x0d = (unknown)
Device code: 0x0e = (unknown)
Device code: 0x0f = (unknown)
Device code: 0x10 = (unknown)
Device code: 0x11 = (unknown)
Device code: 0x12 = (unknown)
Device code: 0x13 = AT90S1200
Device code: 0x14 = (unknown)
Device code: 0x15 = (unknown)
Device code: 0x16 = (unknown)
Device code: 0x17 = (unknown)
Device code: 0x18 = (unknown)
Device code: 0x19 = (unknown)
Device code: 0x1a = (unknown)
Device code: 0x1b = (unknown)
Device code: 0x1c = (unknown)
Device code: 0x1d = (unknown)
Device code: 0x1e = (unknown)
Device code: 0x1f = (unknown)
Device code: 0x20 = ATtiny43u
Device code: 0x21 = (unknown)
Device code: 0x22 = (unknown)
Device code: 0x23 = (unknown)
Device code: 0x24 = (unknown)
Device code: 0x25 = (unknown)
Device code: 0x26 = (unknown)
Device code: 0x27 = (unknown)
Device code: 0x28 = AT90S4414
Device code: 0x29 = (unknown)
Device code: 0x2a = (unknown)
Device code: 0x2b = (unknown)
Device code: 0x2c = (unknown)
Device code: 0x2d = (unknown)
Device code: 0x2e = (unknown)
Device code: 0x2f = (unknown)
Device code: 0x30 = AT90S4433
Device code: 0x31 = (unknown)
Device code: 0x32 = (unknown)
Device code: 0x33 = (unknown)
Device code: 0x34 = AT90S2333
Device code: 0x35 = (unknown)
Device code: 0x36 = (unknown)
Device code: 0x37 = (unknown)
Device code: 0x38 = AT90S8515
Device code: 0x39 = (unknown)
Device code: 0x3a = ATmega8515
Device code: 0x3b = (unknown)
Device code: 0x3c = (unknown)
Device code: 0x3d = (unknown)
Device code: 0x3e = (unknown)
Device code: 0x3f = (unknown)
Device code: 0x40 = (unknown)
Device code: 0x41 = ATmega103
Device code: 0x42 = (unknown)
Device code: 0x43 = ATmega128
Device code: 0x44 = (unknown)
Device code: 0x45 = ATmega64
Device code: 0x46 = (unknown)
Device code: 0x47 = (unknown)
Device code: 0x48 = (unknown)
Device code: 0x49 = (unknown)
Device code: 0x4a = (unknown)
Device code: 0x4b = (unknown)
Device code: 0x4c = AT90S2343
Device code: 0x4d = (unknown)
Device code: 0x4e = (unknown)
Device code: 0x4f = (unknown)
Device code: 0x50 = (unknown)
Device code: 0x51 = (unknown)
Device code: 0x52 = (unknown)
Device code: 0x53 = (unknown)
Device code: 0x54 = (unknown)
Device code: 0x55 = ATtiny12
Device code: 0x56 = ATtiny15
Device code: 0x57 = (unknown)
Device code: 0x58 = (unknown)
Device code: 0x59 = (unknown)
Device code: 0x5a = (unknown)
Device code: 0x5b = (unknown)
Device code: 0x5c = (unknown)
Device code: 0x5d = (unknown)
Device code: 0x5e = ATtiny4313
Device code: 0x5f = (unknown)
Device code: 0x60 = ATmega161
Device code: 0x61 = (unknown)
Device code: 0x62 = (unknown)
Device code: 0x63 = ATmega162
Device code: 0x64 = ATmega163
Device code: 0x65 = (unknown)
Device code: 0x66 = (unknown)
Device code: 0x67 = (unknown)
Device code: 0x68 = AT90S8535
Device code: 0x69 = ATmega8535
Device code: 0x6a = (unknown)
Device code: 0x6b = (unknown)
Device code: 0x6c = AT90S4434
Device code: 0x6d = (unknown)
Device code: 0x6e = (unknown)
Device code: 0x6f = (unknown)
Device code: 0x70 = (unknown)
Device code: 0x71 = (unknown)
Device code: 0x72 = ATmega32
Device code: 0x73 = (unknown)
Device code: 0x74 = ATmega6450
Device code: 0x75 = ATmega6490
Device code: 0x76 = ATmega8
Device code: 0x77 = (unknown)
Device code: 0x78 = ATmega169
Device code: 0x79 = (unknown)
Device code: 0x7a = (unknown)
Device code: 0x7b = (unknown)
Device code: 0x7c = (unknown)
Device code: 0x7d = (unknown)
Device code: 0x7e = (unknown)
Device code: 0x7f = (unknown)
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100%
0.05s
avrdude: Device signature = 0x1e9307
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be
performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "test_leds.hex"
avrdude: input file test_leds.hex auto detected as Intel Hex
avrdude: writing flash (260 bytes):
Writing | ################################################## | 100%
0.38s
avrdude: 260 bytes of flash written
avrdude: verifying flash memory against test_leds.hex:
avrdude: load data flash data from input file test_leds.hex:
avrdude: input file test_leds.hex auto detected as Intel Hex
avrdude: input file test_leds.hex contains 260 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100%
0.21s
avrdude: verifying ...
avrdude: 260 bytes of flash verified
avrdude: safemode: Fuses OK (E:FF, H:D9, L:FF)
avrdude done. Thank you.
Thread beobachten
Seitenaufteilung abschaltenBitte melde dich an um einen Beitrag zu schreiben. Anmeldung ist kostenlos und dauert nur eine Minute.
Bestehender Account
Schon ein Account bei Google/GoogleMail? Keine Anmeldung erforderlich!
Mit Google-Account einloggen
Mit Google-Account einloggen
Noch kein Account? Hier anmelden.