Hi,

I got that message this morning. Context:

• Atmel Studio 6.1
• VisualMicro latest official version
• Programmer USBTinyISP
• the board is Sparkfun Mega Pro Mini 3.3 V

I came across this post of the same subject http://www.visualmicro.com/forums/YaBB.pl?num=1375386337

I tried with the Arduino IDE: no complaint from the IDE, but has been running for 5 minutes, and still running  .

I found this page http://learn.adafruit.com/usbtinyisp/avrdude tried this command avrdude -c usbtiny -p m8 and got that:

Quote:
Looks like that -p is to identify the board, I don't know.

The Mega Pro mini 3.3 V does not need a reflash of the bootloader, but I practice with this one because I will get my own boards that are clones of the Mega Pro Mini 3.3 V.

Thanks

Arduino version 1.0.5.

C:\Program Files (x86)\Arduino 1.0\hardware\mega-pro-3.3V\boards.txt:

# beerware, SparkFun Electronics 2011
# This file adds the Mega Pro 3.3V board to Arduino device list
# compatible with the Mega Pro 3.3V  and Mega Pro Mini 3.3V

###################################################################
mega2560v.name=Mega Pro 2560V 3.3V

mega2560v.upload.protocol=stk500v2
mega2560v.upload.maximum_size=258048
mega2560v.upload.speed=57600

mega2560v.bootloader.low_fuses=0xE2
mega2560v.bootloader.high_fuses=0xD4
mega2560v.bootloader.extended_fuses=0xFD
mega2560v.bootloader.path=
mega2560v.bootloader.file=MegaPro3.3V-8MHz-57600.hex
mega2560v.bootloader.lock_bits=0xCF

mega2560v.build.mcu=atmega2560
mega2560v.build.f_cpu=8000000L
mega2560v.build.core=arduino
mega2560v.build.variant=mega
################################################################### 

The .hex file is C:\Program Files (x86)\Arduino 1.0\hardware\mega-pro-3.3V\bootloaders\MegaPro3.3V-8MHz-57600.hex

Haha, mega2560v.bootloader.path= is empty  Is bootloader.tool needed.

I tried burning the bootloader from Arduinos's IDE, the board looks bricked  .

Thanks

Thanks Giles this is fixed in the next release. There is a workaround if you want it but it really only applies to the sparkfun board as far as I am aware.

The workaround is as follows and will work with the arduino ide:-

1) create a sub folder below \hardware\mega-pro-3.3V\bootloaders. call it anything, for example \hardware\mega-pro-3.3V\bootloaders\megapro

2) copy the MegaPro3.3V-8MHz-57600.hex bootloader into the new megapro sub folder

3) change this board property from

mega2560v.bootloader.path= 

to

mega2560v.bootloader.path=megapro 

This is how the directories are organised for the core Arduino boards so it makes sense anyway. but the next version of vm will support the sparkfun default.

Re-start the ide or click tools>visual micro>reload tools chains

Tim

Yes you are right the path just specified the sub folder below bootloaders in both 1.0.x and 1.5.x. 

I'll add support for wiring sometime because it supports boards like this but it's confusing for users when Wiring also includes support Arduino boards but with an older static tool chain.

I hope your board isn't bricked. Was your programmer able to upload previous to burning the bootloader?

Switch on tools>options>vm>compiler>verbose that should give a more detailed output after upload attempt. 

If the upload tool (avrdude) hangs Visual Micro will force it to timeout after 95 seconds.

Hmm, sparkfun docs say it is compatible with Arduino 1.0x so they should help you fix it or replace it. 

In a way I am pleased that Visual Micro refused to burn the bootloader because it uses the same tool as the arduino ide and in theory will produce the same result. 

It would have been more difficult when you speak with sparkfun if you had said you used Visual Micro to burn the bootloader. This is because sparkfun don't know that Visual Micro does what the Arduino ide does. I know this doesn't help but an interesting observation to keep in mind in the future 

Thanks for all the recent forum help.

I finally was able to edit the boards.txt file... but got the same result: the IDE hangs and nothing is written in the bottom window.

Looks like something is wrong either with the IDE or with the USBTinyISP ?!?

Tim,

About the Beta version, I prefer to install a new version once it's officially released. I will contact SparkFun and look at the Arduino forums.

Thanks

Hi Tim,

I finally got it to work.. well sort of. I had an issue with the driver, but it's now solved.

So I tried again this morning, and got this from avrdude:

avrdude: Expected signature for ATmega32U4 is 1E 95 87
         Double check chip, or use -F to override this check. 

I think it comes from the definition of the board which is included with the IDE:

promicro8.build.mcu=atmega32u4

Looks lile the IDE uses it's definition, but VisualMicro uses the definition that was added under hardware, and my opinion is that your way is the right one !

I tried again with VisualMicro (AtmelStudio) and this time got:

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at processing.app.debug.AvrdudeUploader.burnBootloader(Board boardPreferences, String programmerName) 

Looks like for now my only way would be to use Arduino's IDE till the new version of VisualMicro is published. I will contact SparkFun about that problem.

Thanks

Tim,

Yesterday I picked the wrong board, wich has a ATmega32U4  .

So I tried with the right one, which is the Mega Pro 2560V 3.3V. I am getting closer, but after a while I get

avrdude: verification error, first mismatch at byte 0x3f800
         0x11 != 0xff
avrdude: verification error; content mismatch 

I tried with an old Arduino Mega, I get the same error message, but with a different address. What's interesting is that the number to the right of = is 0xff again. I will contact adafruit.

Thanks

This is the question I asked adafruit  .

Tim,

looks like that (&**"/!/! programmer does not work with 2560 MCUs  .

SparkFun suggested I tried to upload blink.ino with the adapter. Since that does not seem, possible in the Arduino's IDE, I tried from AtmelStudio with VisualMicro... I got that message for minutes:

Quote:

Looks frozen  .

Tim,

some more information.

SparkFun support person suggested I try to upload blink.ino to the board using the programmer. Her theory is that the TinyUSB may not have enough memory to upload the bootloader for the Meg Pro Mini. Well I succeed in uploading blink.ino. I then tried to upload my own program, about 24 K, but didn't succeed. I also ask her which programmer they use to burn the bootloader to these board, and was told it's the AVRISP mkII.

So I got an AVRISP mkII this afternoon. Plugged it in and the driver automatically installed. All is fine I thought... no so  . I tried to burn the bootloader with Arduino's IDE and I am told no USB device found (can't recall the exact message).

I had a looked in Device Manager and found out under Jungo AVRISP mkII. I rebooted the computer, same error message. As far as I understand, all the programmer would use the same driver, libusb.

Tomorrow I will try to upload my program from AtmelStudio withe the AVRISP mkII, hoping it's going to work.

To you best knowledge, is there anything that needs to be installed for that programmer to work in AtmelStudio ? I got a CD with tools for AtmelStudio up to V 5, so I didn't install anything.

One more question: when uploading a program with a programmer, is there a need for a specific bootloader in the MCU ?

Gee, I never thought it would that completed to use a programmer  .

Thanks

If I get you right:

(1) I should remove the jungo driver
(2) Remove any libusb driver installed for the USBTinyISP programmer
(3) Install the libusb for AVRISP mkII (there seems to be only one kind of libusb driver ?!?)

Then I should be able to burn the bootloader with either Arduino's IDE and AtmelStudio+VisualMicro ?

I fear that next time I plug in the mkII, the jungo driver will be installed automatically.

Thanks

Tim,

still a nightmare  . I haven't succeded in getting rid of jungo. I deleted the mkII under jungo, and when I reconnect the mkII, the driver reinstalls. I found out here http://avrstudio5.wordpress.com/2011/12/02/setting-up-the-avr-jungo-usb-driver-m... instructions on how to remove jungo with wdreg (they6 use their own installer .) I rebooted, connected the mkII and again the jungo re-installed. Since I am not able to get rid of it, I de-activated mkII under Jungo connectivity. No cure...

I tried burning the bootloader form the IDE after I removed mkII under jungo, and got:

Quote:

I tried with the mkII unplugged, and got the same.

So since I found out the libusb drivers for mkII, I tried to install: all I got is a cmd window that promptly disappears as it would not work.

You seems to say that the libusb installer would prompt for the programmer type. Where did you get that installer ?

Thanks

From http://avrstudio5.wordpress.com/2011/12/02/setting-up-the-avr-jungo-usb-driver-m...

in a cmd prompt I typed "wdreg.exe –inf windrvr6.inf uninstall". Maybe it's not enough. How do you remove jungo ???

I read somewhere that in control pannel > Program and Features that there should be an entry7 called "AVR Jungo", haven't found it.

Tim,

some news.

Robert tested on a different computer. He cleaned it up from AtmelStudio, installed Arduino's IDE and the libusb driver for mkII.

Uploading blink.ino wqith the mkII worked fine... but trying to burn the bootloader, he got the "no usb found" message. Looks like the IDE does not address the programmer the same way when uploading a program and burning the bootloader.

No one is going to uninstall AtmelStudio and VisualMicro from my computer  .

About Jungo, when deleting it, the check box says "remove that driver" and permanently is not shown. But I have a French Windows, maybe some dropped the word when translating.

The message is:

usbdev_open(): did not find any USB device "usb".

We get the same message when we try with the USBTinyUSP, for which the libusb driver is also installed.

But the IDE finds it (mkII) when it uploads a program.

I was able to try to burn the bootloader with the USBTinyISP. But there is a difference: I run Arduino 1.0.5 and Robert runs 1.0.5 r2 (added support Windows 8 and 8.1... and a bug ?).

Not in Windows, but is it possible that in 1.0.5 r2, they introduced a bug ?

VisualMicro is not on Robert computer, because when AtmelStudio is installed, Jungo comes in.

I tried something on my computer. I plugged in the mkII, the /!/!"""% jungo driver installed, then I right-clicked it, and replaced by the lisbusb driver. Unplugged the mkII, plusg it again, it's now under lib-usb win32 devices  .

If I try to upload blink.ino in VisualStudio+VisualMicro, no error message but « Uploading to I/O board using 'avrispmkii' » till the ends of time.

AtmekStudio is not frozen, afterwards I ask to burn the bootloader and get:

System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at processing.app.debug.AvrdudeUploader.burnBootloader(Board boardPreferences, String programmerName)

I closed AtmelStudio, reloaded it and fisrt thing I asked to burn the bootloader: same message from .Net.

The I did another test, with IDE 1.0.5 and mkII:

• I was able to upload blink.ino
• Then I ask to burn the bootloader. No complain about the usb device... but got an error in verification:

Quote:

This time right at first byte.

Looks like I went over my device driver/talking issues, but burning the bootloader fails for still unknown reasons  .

And looks like it proves my point about  abug in 1.0.5 r2 ?!?

The SparkFun Pro Micro 3.3 v. You told me previously that the board definition is not per Arduino standard. When I tried first to burn the bootloader, VisualMicro told that the board does support bottloader burning - or something like this.

Tim,

burning the bootloader with Arduino's IDE, I set verbose mode and copied to a .txt file that I read afterwards:

• Step 1, burning the fuses, everything is fine
• Step 2, writing to the flash. The .hex file is 4,973 bytes long but avrdude reports that it's 261,842 bytes long (the size of the Flash memory)  . Then it writes the flash, can't tell how many bytes, but not that much. Then it reads to verify, all of the Flash memory (why ?), and verify is Ok.
• Step 3, the lock bit. I see 'reading input file "0xCF" (what is that ?) and the verify fails.

But the bootloader is correctly burned. I know because I tried uploading my program to a second board I haven't burned the bootloader to, no success. I burned the bootloader and afterwards was able to upload the program.

SparkFun told me how they proceed to burn the bottloader. They use stk500.exe to burn the bootloader. Looking at the log I see this:
Quote:

I know that stk500 is a protocol. Is STK500V2 a different protocol that stk500 (maybe slightly) that would trigger an error at the lock bit ? Do you what's the use of the lock bit ? Wiring talks about stk500 and stk500 v2 as two kinds of bootloader. It's really confusing  .

Thanks

Hi Gilles.

1)
Thanks for the email which says that the programmers menu is mostly disabled.

Please copy the programmers.txt from hardware\arduino\avr to your custom hardware folder then click tools>reload toolchains

2)

The file you sent contained two verbose outputs from bootloader upload shown below.

The first reported it worked correctly the 2nd report an error. the first did not contain a bootloader.hex file but the 2nd did.

In what order did you add these two outputs and from which ide's were they produced.

Thanks

C:\Program Files (x86)\Arduino 1.0\hardware/tools/avr/bin/avrdude -CC:\Program Files (x86)\Arduino 1.0\hardware/tools/avr/etc/avrdude.conf -v -v -v -v -patmega2560 -cstk500v2 -Pusb -e -Uefuse:w:0xFD:m -Uhfuse:w:0xD4:m -Ulfuse:w:0xE2:m
 

C:\Program Files (x86)\Arduino 1.0\hardware/tools/avr/bin/avrdude -CC:\Program Files (x86)\Arduino 1.0\hardware/tools/avr/etc/avrdude.conf -v -v -v -v -patmega2560 -cstk500v2 -Pusb -Uflash:w:C:\Program Files (x86)\Arduino 1.0\hardware\mega-pro-3.3V\bootloaders\Megapro3-3\MegaPro3.3V-8MHz-57600.hex:i -Ulock:w:0xCF:m
 

the commands look identical to me? I will need to look at the arduino source to see if there is a pause Visual Micro is missing. 

So to be clear. The first email you sent was from the arduino ide and the second was visual micro?

Thanks

Oh thanks didn't see the name on the end.