I got it to work on Windows 8.1. Windows 7 still has issues recognizing the device, etc. The sketch I'm working with is fairly large: about 21.4K. It takes the IDE a while to compile, so by the time it gets to uploading the bootloader is no longer active. If I wait to push the reset button, it works.

I still think the device recognition is flaky, particularly in Win7, but this *may* work.

Hiya, we did all our development/testing (about 3 months worth) on windows 7 x64 so we dont think its a native win7 issue. We're always listening to customer support/refunds/returns for fairly new products to see if there's issues. So we are keeping an eye on this!

Each Pro Trinket is checked for enumeration during test, but it may be a computer/os/cable combination issue. If you are not able to get your Pro Trinkets going, email support@adafruit and they'll refund your order

If your compile time is longer than the bootloader timeout, click upload then press the reset button after a second or two

Alternatively, you can always use an FTDI Friend/Cable to upload! The bootloader will autodetect FTDI uploads and FTDI uploads will autoreset right before uploading, like an Uno :)

Sooo I should upload my code and then hit the reset button after the error?

No. as Rick said, let it start compiling and press the button before it uploads. This can be a pain, because at least on my system, reset causes the USB connection to go away and reconnect--you need enough time for that process to complete before it starts uploading.

Possibly, but I've used multiple cables on 3 OSs on 2 computers. It only works consistently with Ubuntu. The Windows machines have inconsistent device recognition, but I can now get it to work if I fuss with it.

BTW, the error message from AVRDUDE on Ubuntu is much more informative ("connection timeout") than Windows (paraphrasing: "eeeeeK! screwup number blah blah! your device is trashed!").

Possibly, but I've used multiple cables on 3 OSs on 2 computers. It only works consistently with Ubuntu. The Windows machines have inconsistent device recognition, but I can now get it to work if I fuss with it.

BTW, the error message from AVRDUDE on Ubuntu is much more informative ("connection timeout") than Windows (paraphrasing: "eeeeeK! screwup number blah blah! your device is trashed!").

Thanks for sticking with us on this.

Thx, we'll keep an eye on it. If the pro trinket is/are not working out for you, please email support@adafruit to get a full refund! An Arduino Micro w/o Headers is similar size/shape/capability and may be a good alternative :)

chasirish wrote:I'm pretty sure I am. It's for an audio visualizer, so I tested it to music and the leds flashed accordingly. I then unplugged it, left and when I came back later to plug it in, it lost the code

That really can't happen. The code is loaded into flash memory - the same stuff used on flash drives. It just can't go away like that.When you plug it back in, you'll have to wait for 10 seconds or so before your code will start executing - it won't start up right away.