Go to homepage
16 / 33
Jun 2016
23 days later
20 days later

Yes, actually!

Now, I’m not sure whether or not this will work using the USB method, but if you get an AVR programmer this should definitely work.

AVRDUDE has the ability to read the flash, the eeprom, and the fuses of an AVR chip.

The firmware is stored in flash memory, so you can use AVRDUDE to export the flash memory into a .hex file. I haven’t done this myself, though, so you’ll have to find out the specific command line yourself.

Though I think the Qidi firmware is a derivative of the makerbot firmware, so it may not be fully necessary; but I guess better safe than sorry!

2 months later

The programmer appears plugged in correctly to me.

As for the AVR studio 4, I’m afraid you’re on your own on that front. I’ve used only AVRDUDE and ATMEL Studio.

Ah no problem. I’m going to use AVRDUDE. I have some help from another person who went through it and gave me the hex files. I guess what I need to know now is how to use AVRDUDE such as making sure the connector I bought even works. I’ll come back and update.

8 days later

Hi there and thanks again for replying. I have an programmer now and am familiar with avrdude. Do you have the commands I need to flash to the motherboard in order to get this working?

Right now I’m using:

avrdude -p m1280 -F -P usb -c usbasp -U flash:w:/Makerbot-usbserial.hex \ -U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

and

avrdude -p m1280 -F -P usb -c usbasp -U flash:w:/atmega1280.hex \ -U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

to the 8u2 ICSP port but to no avail. Avrdude says it completed but had a verification error. Also I see no com6 in repG

Okay, to make troubleshooting easier, could you try again with a verbose output and funnel the command’s output to a text document?

To do that, use this command:

avrdude -v -v -v -p m1280 -F -P usb -c usbasp -U flash:w:/Makerbot-usbserial.hex \ -U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m > Troubleshoot.txt

That should output all the command’s response into a .txt file that can be used for troubleshooting.

Will do. Just so I’m clear. I was flashing the atmega1280.hex to the 1280 header and the usbserial.hex to the 8u2 ICSP. Is this correct?

avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D9
avrdude: safemode: efuse reads as F4
avrdude: safemode: lfuse reads as FF
avrdude: safemode: hfuse reads as D9
avrdude: safemode: efuse reads as F4

Wait, the 8u2 chip on the motherboard…? You’re talking about the separate chip on the motherboard?

You… shouldn’t have touched that…

That chip has nothing to do with the firmware flashing, it’s all in the ATMEGA1280 chip.

The fuses you need to adjust are in that chip too as far as I’m aware.

That firmware does NOT belong in the atmega8u2 chip, that’s something else entirely…

I really, really hope you backed up the flash and fuse settings for that chip, or at least can find them online.

If not, you really did brick your printer if it isn’t starting up right now.

That chip at least doesn’t use the “-p m1280” setting in AVRDUDE, so maybe you didn’t break it…

EDIT: for fixing the atmega8u2, this link has some info:

https://groups.google.com/forum/m/?fromgroups#!topic/makerbot/-S01iIYO2E8 2

Okay, okay. Still so confused and someone else had posted on here with what I believe was incorrect information.

There is the 1280 ICSP port. The 1280.hex goes on that, correct?

The command would be: avrdude -p m1280 -F -P usb -c usbasp -U flash:w:/Makerbot-usbserial.hex \ -U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

There is an 8u2 ICSP port. The makerbot usb hex goes on that, also correct?

The command would be: avrdude -p at90usb82 -F -P usb -c usbasp -U flash:w:Makerbot-usbserial.hex -U lfuse:w:0xFF:m -U hfuse:w:0xD9:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

You had mentioned flashing the firmware directly and avoiding repG altogether. I can do that to the 1280 ICSP port, right?

If you look in this thread, I have a post giving simple instructions on uploading the firmware.

To be brief, flash the firmware (with the fuse settings) to the 1280 icsp port.

The 8u2 does control the usb, but you really shouldn’t have messed with that in the first place, the flash memory that was already on it was fine.

That response I gave you yesterday linking to that thread should have the information regarding reseting the 8u2’s flash memory back to defaults.

Thanks so much. I was in a bind so I was taking advice from the wrong people. I will give it a shot tonight. Thanks again.

FIXED! Okay I didn’t bother with the 8u2 and I don’t think it ever got messed up. I ended up having to install WinAVR and reran the same commands. I think I had too old of a version of AVRDUDE? Anyway, I had a blank screen still and same problem after reflashing the Atmega1280.hex to the 1280 port but after then flashing Sailfish 7.1 hex for a Replicator 1 Dual it started beeping!

Now my issue is that when I home axes the X axis buzzes like crazy like it is going to tear the printer apart. I noticed the back left stop switch red light isn’t coming on, is that the problem?

The light isn’t coming on? Seems that either the motherboard is no longer recognizing the switch or the switch itself is encountering some kind of mechanical failure. Either way, if the switch isn’t working the printer will keep trying to home until something breaks. The only thing I can think of off the top of my head is that maybe you bumped a plug or wire when working on flashing the printer? Check the connections and wires related to that switch. Otherwise, I’m not too sure on that front.

At least you got it functioning, that’s good. I knew that the motherboard was closer to a Replicator 1 Dual then a Replicator 2x, were you trying the 2x’s firmware?

As for upgrading past sailfish 7.1, people say it has to do with the fuses, but I haven’t tried any of that myself.

What happens is that when I home the axes, the X axis moves as if it is still printing. Back and forth, vibrating in a pattern like seizure. If I push the Print head along the x axis it helps it along and looks like it is printing. What could be the cause of this?

I only tried 7.1 because that was the first one I had handy. I can try other versions for sure.