Atmega32u4 Breakout Board Leonardo Driver Issues

[bigmessowires]

Has anyone sucessfully downloaded an arduino sketch w/o it BSoD-ing? If so, then it's a matter of searching for the offending library. If not, I'll dig into the initialization code.

Yes. At first I programmed the Blink example from the Mac, and verified that it was working by hooking up an external LED. When I then brought the board back to the PC, I got a bluescreen BAD_POOL_CALLER crash every time, just like you described. I then reburned the Arduino 1.0 RC2 Leonardo bootlader a second time, and now it seems to work fine on my PC. I successfully programmed the Blink example from the PC, as well as the USB keyboard example. I wish I could explain what I did that seems to have fixed it, but honestly I don't know.

[toddkrein]

Well, that's hopeful...

have you been able to download other sketches, or the blinky again? If so, it sounds like a problem getting to a known state. If not, then there's something else going on. Perhaps some initialization cruft.

The bummer is that with the BSoD, I can't do development during staff meetings... :-}

[royco]

BSODs are now gone.. Dont know how/why.

I just connected it to another PC(same 64bit) installed driver, program ran fine. Uploaded another sketch still ok. Went back to PC with BSODs and it now works AOK. WHa????

It could have been nice to know what caused the BSODs.

[royco]

BSOD is back. but... on one particular USB port only. All other ports are good. So you might want to try those other USB ports if you are having BSODs.

For now all is well. Thanks!

[bigmessowires]

Using a different USB port will probably cause it to be assigned a different COM number, so maybe that's it?

You can force it to be assigned a specific COM number in the Device Manager, under Properties->Advanced if I recall.

[toddkrein]

Windoze installs a new version of the driver for each different port that you plug a device into. Crazy, but there you have it. So I"m guessing that it has to do with the driver that's attached to that port's instance of the 32u4. That seems consistant (if anythign is consistant) with the wierdness of having to multiply re-install the same driver to get it to work.

Under Windoze 7, in the device manager you can select "Show Hidden Devices", and then look under the COM & LPT, and see all the drivers. It would be *great* to compare what's loaded and configed for the port that's failing vs. the port that works. Should give us some good information.

Not sure how you do it under XP, if that's what you're running...

[royco]

So I did some more testing last night and here's what I found out on that particular offending USB port.

Changing COM ports - still BSOD
Removing Drivers/re-install -still BSOD
Loaded sketch via AVRISPmkii -still BSOD

I think the BSODs have something to do with the Human interface Devices , when the chip is bootloading the HID says Arduino Leonardo Bootloader, when the program runs it is changed to USB input device in the Device Manager. This change is where the BSOD happens. If I load the sketch without the boot loader then connect it to the PC I could see the USB input device being added then BSOD right away.

Anyway, i'll just mark this usb port for now and start playing with this thing.

[bigmessowires]

Royco, are you getting BSOD even after burning the most recent Leonardo bootloader from Git?

If I load the sketch without the boot loader then connect it to the PC I could see the USB input device being added then BSOD right away.

That sounds strange. If you loaded the sketch using the AVR ISP mkII, then that should have completely erased the bootloader, right? If so, then plugging in the board to your PC shouldn't enumerate a USB device or do anything at all, unless the sketch you're running is one that uses USB itself (like the mouse and keyboard samples).

[royco]

Yes, Im using the latest boot loader already. and even without the boot loader it still does BSOD on that particular USB port(using blink sketch). Somehow I see the USB device added under the HID category even without the boot loader. I dont know if that one USB port is faulty or something but on my other PC all USB ports work ok.

Thanks

[db4476]

Is there a solution to this issue yet? The world awaits....

[tadpole]

Hi again,
So I was asked to post replies here, along with a screen shot. Mind you this is all on a german language OS, so I hope it isn't too confusing. The device shows up under "unknown devices", and driver isn't recognised. I don't have any way of putting a new bootloader on it, and was wondering if I should still send it back? Postage would run be about $12, and I wonder if there is some other deal we could work out? If there isn't I will send it back, it is just a bit of a pain.

Untitled-2.jpg (115.91 KiB) Viewed 2015 times

[vtluu]

tadpole, did you try the driver install procedure bigmessowires posted earlier in this thread? viewtopic.php?f=19&t=24141#p125471

The relevant .inf (driver) file needed is linked in the Downloads section at the bottom of this page: http://ladyada.net/products/atmega32u4breakout/

That got the driver installed for me. Unfortunately I still get the "Could not start" error. I don't have an ISP box so re-flashing the board isn't an option unless/until I get one (which I might do anyway). Too bad, I'd really been hoping to spend some time this holiday weekend hacking on this device.

[tadpole]

Thanks Vtluu,
I had tried that method (as well what seems like 100 others), but didn't have any luck. The only way I got any sort of progress was to change the driver so that the VID and PID matched the ones that showed up on my system as the corrosponding hardware IDs. That however led to the famous error 10. I ordered this with the belt kit, and was actually expecting it to simply work. lol.

[adafruit]

Thanks Vtluu,
I had tried that method (as well what seems like 100 others), but didn't have any luck. The only way I got any sort of progress was to change the driver so that the VID and PID matched the ones that showed up on my system as the corrosponding hardware IDs. That however led to the famous error 10. I ordered this with the belt kit, and was actually expecting it to simply work. lol.

Hi, we've posted in this thread
viewtopic.php?f=19&t=24141&p=125500#p125500
for anyone still having problems, and unable to burn AVRs on their own, they can contact us for a replacement 32u4 with the latest bootloader on it.

[bigmessowires]

I had tried that method (as well what seems like 100 others), but didn't have any luck. The only way I got any sort of progress was to change the driver so that the VID and PID matched the ones that showed up on my system as the corrosponding hardware IDs.

Strange. Can you describe what exactly happens when you tried the driver install method from my earlier post? Does it report some kind of error?

What VID and PID are showing up on your computer? The VID should be 2341. It looks like the PID was changed from 32 to 34 in the November 9th Leonardo bootloader update.