problems with the Arduino Due

Official Hardware Mega Due
1

greetings

i just started messing around with an arduino board, and i think i broke it :frowning:

i tested the "blink" example and it worked fine, now i can't work with it anymore
everytime i want to upload something, this happens:
avrdude: stk500_getsync(): not in sync: resp=0x00

upon trying to install a bootloader, this happens:
avrdude: usbdev_open(): did not find any USB device "usb"

the drivers are installed, the right port and board are selected, programmer: AVRISP mk II
and the board appears in the windows hardware monitor

the "L" LED is glowing
EDIT: when i upload a sketch, the RX LED right next to the programming USB port flashes 2 times

here are some examples of how i might have broken it:
-after i tested the "blink" sketch, i pressed "erase" and then "reset" to clear the flash
(but since i read that all the important stuff is hardcoded and not affected by erase, i don't think that's it, is it?)
-i plugged and unplugged LEDs while the board was connected to the PC :confused:

could someone help me to fix it? is it fixable?!

kaetzer

2

If you are using an avrisp mk2 I'm guessing you have loaded the blink sketch onto the avr rather than the Arm chip?

Or are you loading into the arm core via one of the usb ports? Have you tried using the other usb port on the board?

3

using the other (the "native") usb port results in the same error

i dont quite know how i could have loaded something on AVR or Arm chip :confused: i thought there was only one type of flash memory on the board, i'll see if i can find some info on that
and LED did blink like expected

EDIT: ok, so i just found out, the biggun is the ARM and ATMEGA16U2 is the AVR, i didn't know you could upload to both of the

4

Maybe try pressing reset just after clicking upload?

5

And the board is definitely set to due? I only ask because I don't think it should be using Avrdude when the due is selected...

6

Definitely should not be using AVRdude on the Due.

There is an auxiliary AVR chip on the Due board that handles the non-native
USB socket IIRC. Programming that wrong will brick the Due (the correct firmware
for it is somewhere in the sources though, called something like
"Arduino-DUE-usbserial-prod-firmware-2013-02-05.hex", I've never had to deal with this though as I just select Due programming port and upload a sketch).

The Due chip itself (SAM3X8E) has a hard-coded bootloader than you cannot
damage, its in ROM. The "bossac" utility is used to talk to the Due bootloader.

7

hey, thanks for all your answers, sorry for the kinda late reply, been sick for a few days

my boss gave me a new one, a UNO, cause i already have a book about those, and he tested the DUE and it works just fine, i guess it was a user error, sorry -.-
maybe it was indeed the avrdude-problem mentioned by dragonax and MarkT
or maybe my work PC was just acting stupid, dunno, does it all the time

anyway, thanks a bunch, i'll stick around :wink: