E3Dv6 on Solidoodle Press (Page 9 of 21)

I used a AVR Programmer (specifically a USBtinyISP - http://www.amazon.com/Pololu-POL1300-US … 003XOHVUW/ But I also have the Arduino Branded unit too - http://www.amazon.com/Arduino-A000092-I … 0LUJYI26/) to flash mine. At the house I don't have any Windows boxes. Everything is OS X and Linux. I used my RPi to flash the Press' controller via the tiny.

It was the matter of compiling, moving the hex to the RPi and using avrdude to flash. This is mostly due to the fact that I am running OctoPrint and that RPi is already connected to the Press. This save me from moving the press from room to room to flash it.
The RPi is not required.

When I get home tonight, I'll create a Windows VM and and yank the board out of the Press, flash it and make a document. This is exactly what I wanted to avoid doing. This is the main reason why the 'If you are not familiar with flashing AVR's...' disclaimer is here and on github. But I don't want to be responsible to people breaking/bricking their printers. You guys have no idea how many email's/PMs I've gotten here, Github and thingiverse about how to flash the firmware. (Heh even threats).

No threats here!  I was just seeing if it were possible without the AVR programmer.  Mines already hooked up to the RPi but it is right next to my pc.  I think we were all assuming the bootloader method would work as described

Patient I will be. Wish I could be printing away, or helping solve this issue at hand.  But on the bright side this gives me more time to machine a hotend adapter out of aluminum versus printing one. And construct a wall mounted filament holder for the Bowden setup as well. Silver lining.

I did this with a fresh Windows XP VM.

I installed Atmel FLIP (http://www.atmel.com/tools/FLIP.aspx - FLIP 3.4.7 for Windows (Java Runtime Environement included)
Then download the HEX (https://github.com/ymilord/Solidoodle-P … re.cpp.hex)
Power off the Press (Unplugged the main power from the PSU Brick)
Placed the BOOT jumper.
Opened the HEX file with the FLIP software.
Selected the target device 'AT90USB1286.'
Then picked the USB as the connection.
The I had Blank Check, Erase & Program checked.
Click the Run Button.
After it finished unplug the USB cable.
Removed the Jumper.
Plug in main power.
Plug in the USB Cable.
Soft power the Press.
Then I connected it to RH and I was able to see the temps and Jog the printer.

I did the steps above a couple times in a row just to make sure.

I moved everything back to my RPi, Same thing I was able to see temps and jog the machine around.

i am sad to report that this isnt working for me.  windows 7 64 bit.  rebooted pc a few times just to see if that helped and no go.  i will try and install XP on a VM and report back later on.  but as of now when i get to the PICKED USB AS THE CONNECTION step, i simply get an error popping up saying that it could not open the usb device

Man, This is far, far simpler to do in linux or Mac OS X. (Not trolling. Just making a observation.)

this is my unrecognized device

and upon searching for the driver as told above, folders not there.

ill just peruse the internet to find a fix, youve spent more then enough time on this flashing business already. so dont feel obligated to shoot a response back here.

nah man.  this shit just isnt working for me.  and its becoming a pain in the ass for you i could only imagine. 

im going in device manager, going to the unknown device, update driver, manually pointing it to that USB folder on my desktop, and its just telling me that windows could not find driver software for my device. 

i assume this has nothing to do with Teensy USB being an issue somehow someway?  just got that from reading a forum post somewhere after googling ATMEL Flip USB connection issues thus why i ask

I really don't know what else to tell you. The only thing I can suggest it getting a AVR Programmer. I posted links to the models I used.

I've been so accustom to use it that I never bothered doing this method the first time around. Just plugged in the programmer. And fired a single command line. I am very hesitant to say if this is WinXP thing or not. I only used it cause thats the only Windows ISO I have (and it's mainly used for other things thats windows only i.e. some CAM packages I use)

I'll be heading home in a few. I'll poke around further.

the issue is the drivers.  far as i can tell here.  im poking around the web for answers as we speak but if nothing comes up by tonight ill be overnighting an USBTiny so this is just done with at this point.

curious, are you using a 64 bit version of windoze?  im reading that the issues, at least for me with my system, could be related to the fact that any driver i install needs to be digitally signed for windows 7 64 bit to install it.

from what im reading, im almost 99 percent certain that is our issue here. if i cant locate signed drivers i will attempt this with an install of XP on a VM i guess.