Loading firmware on a new Mightyboard Rev E

[Wil Chung]

Hi all,

I have a Makerbot Replicator 1. The board blew out, and I was able to get a replacement from makerbot. However, it turns out, but no startup beeps came on. I suspect that the firmware isn't loaded on the board. Makerbot support has been slow about letting me know how to flash the board. So I turn to this google groups:

How do I flash the mightyboard rev E board from my laptop? What firmware should I use? Is it the mightyboard firmware(https://github.com/makerbot/MightyBoardFirmware) or the sailfish firmware(https://github.com/jetty840/Sailfish-G3Firmware), or something else? Where do I find this information?

And can you flash the firmware the first time over USB, or do you need a USB to AVR converter? I seem to have one, so if your instructions and recommendations require the AVR cable, that might work as well. 

Thanks.

Wil

https://cubehero.com

[Dan Newman]

On 22/12/2013, 9:32 AM, Wil Chung wrote:
> Hi all,
>
> I have a Makerbot Replicator 1. The board blew out, and I was able to get a
> replacement from makerbot. However, it turns out, but no startup beeps came
> on. I suspect that the firmware isn't loaded on the board. Makerbot support
> has been slow about letting me know how to flash the board. So I turn to
> this google groups:

Does anything useful appear on the LCD display? It may be a bad or missing
piezo buzzer. (MBI incorrectly uses a piezo buzzer when they meant to use
a piezo speaker for playing multi-tone tunes. So, for you EE's out there I
didn't miswrite "buzzer".)

> How do I flash the mightyboard rev E board from my laptop? What firmware
> should I use?

Question is whether or not the USB chip has its firmware and whether or
not the main processor has its bootloader.

Have you tried loading MBI's firmware from MakerWare using the normal
procedures? First see if that works. Getting the timing right on the
reset button can be a little tricky. If using a Mac, it's press the
reset button then click the final download button on the Mac. (May 1/2
sec. later.)

If the USB chip is missing its firmware and/or the main processor
is missing its firmware, then you will need an AVR ISP programmer
(2x3 pins) and avrdude to download the necessary code into the
chips. Folks here can help you with that as well. Note that your
USB to AVR converter may or may not be an AVR ISP programmer. It
may just be a USB to FTDI cable. (Those usually do not present a
6 pin female header in a 2x3 configuration. Or, nearly equivalently,
a 10 pin in a 2x5 configuration. The USB to FTDI's tend to be a
6 pin female header in a 1x6 configuration; e.g.,
http://www.adafruit.com/products/70?gclid=CLe8z92xxLsCFYqPfgodTHEA3w .)

Dan

[Wil Chung]

Thanks for the reply!

No, the LCD display just flashes on, and then it just turns off. ReplicatorG also doesn't detect the /dev/ttymodemUSB device. I had assumed this is because the board doesn't yet have the firmware flashed on to it.

I searched the web for MBI's firmware, and found their github repo. I tried compiling MBI's firmware, and I get the following error:

 > ./firmware/build_and_upload.sh 

Building latest version :

-------------------------

FORCE Cleaning up stuff :

-------------------------

done.

What board / model should we build for ?

 A) Replicator or Replicator Dual

 B) Replicator 2 (single tool) [default]

 C) Replicator 2X (dual tool)

a

What locale should we build in ('en' or 'fr') ? [en] : 

en

 - Building firmware (en) for mighty_one () ... Success

find: ./build: No such file or directory

Failure

It seems the build script is missing. I don't know if it's the build_all.sh or something else. 

Then turning to the replication firmware page, they recommend using ReplicatorG to load the firmware, which as I wrote before, ReplicatorG doesn't detect the /dev/ttymodemUSB*. I also don't see it in /dev/ when I look there.

I believe I do have an AVR ISP programmer. I had put together one of these before: http://learn.adafruit.com/usbtinyisp/overview

How would I use the AVR ISP to flash the board? There seem to be two 2x3 6 pins on the board, and I wasn't able to compile the code from the Mightboardfirmware. Thanks!

Wil

--
You received this message because you are subscribed to a topic in the Google Groups "MakerBot Operators" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makerbot/tBTVx85-hpg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to makerbot+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Wil Chung

https://cubehero.com

Blog: http://iamwilchung.wordpress.com

Twitter: http://twitter.com/iamwil

Repos: http://github.com/iamwilhelm

           http://github.com/cubehero

[Jetguy]

You are going about it the insanely hard way.

Do NOT attempt to complie the firmware.

As Dan stated, the following sequence needs followed.

Flash the 8u2 with the proper hex file from github to get the USB working using an AVR programmer plugged into the 8u2 header on the mainboard.

They even gave you the commands here and the file https://github.com/makerbot/MightyBoardFirmware/tree/master/bootloader/8U2_firmware

And this is the specific HEX for the 8u2 on a Rev E board https://github.com/makerbot/MightyBoardFirmware/blob/master/bootloader/8U2_firmware/Makerbot-usbserial.hex

O DOWNLOAD THE HEX FILE:
1. Connect the AVR ISP MKII compatible programmer to the 8U2 6 pin programming header
2. Ensure the Board is Powered
3. navigate to the directory containing the .hex file in the terminal
4. Execute the following avrdude command: avrdude -p at90usb82 -F -P usb -c avrispmkii -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
5. If unsuccessful ("Error in USB Receive"), try again.  It sometimes takes a few tries

FYI AVRDUDE is located in the tools folder of Replicator G which you should also have to make this easy to load.

I make a copy of avrdude.exe and avrdude.conf and copy them to the root of my C: drive along with the hex to make the command path easier from command line.

We can have a debate on it but you have 2 options for getting  A bootloader onto the mega1280. Both require the same AVR programmer, but one stupidly easy way is use the Arduino IDE and choose atmega1280 as board type, then choose your programmer type, then burn bootloader with the AVR programmer plugged into the 1280 header on the mainboard. (must be powered as well).

That said, they did come up with their own bootloader that is supposed to be safer and turn off the MOSFETS and so on.

You can again, use command line and AVRdude to flash this hex file https://github.com/makerbot/MightyBoardFirmware/tree/master/bootloader/1280_bootloader to the 1280 just as above and this is the "correct" bootloader.

Finally, as the last step after you have working USB and working bootloader, you can then use Replicator-G firmware update normally to get the initial firmware hex onto the machine.

After that, you are pretty much set just like anyone else.

[Dan Newman]

On 22/12/2013, 1:38 PM, Jetguy wrote:
> You are going about it the insanely hard way.
> Do NOT attempt to complie the firmware.
>
> As Dan stated, the following sequence needs followed.
>
> Flash the 8u2 with the proper hex file from github to get the USB working
> using an AVR programmer plugged into the 8u2 header on the mainboard.
> They even gave you the commands here and the file
> https://github.com/makerbot/MightyBoardFirmware/tree/master/bootloader/8U2_firmware
> And this is the specific HEX for the 8u2 on a Rev E board
> https://github.com/makerbot/MightyBoardFirmware/blob/master/bootloader/8U2_firmware/Makerbot-usbserial.hex
>
> O DOWNLOAD THE HEX FILE:
> 1. Connect the AVR ISP MKII compatible programmer to the 8U2 6 pin programming header
> 2. Ensure the Board is Powered
> 3. navigate to the directory containing the .hex file in the terminal
> 4. Execute the following avrdude command: avrdude -p at90usb82 -F -P usb -c avrispmkii -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
> 5. If unsuccessful ("Error in USB Receive"), try again. It sometimes takes a few tries
>
>
> FYI AVRDUDE is located in the tools folder of Replicator G which you should
> also have to make this easy to load.

I do not believe that the avrdude.conf in RepG has at90usb82 device. Newer 1.x
Arduino distros have it. So, I'd use the avrdude and avrdude.conf from a 1.x Ardunio package.

BTW, once you put that newer 8u2 firmware on, you can add the missing C20 (0.1 uF ceramic cap)
to the revE mightyboard. You will then never need to push the reset button again -- auto-reset
will work.

Dan

[Wil Chung]

Jetguy and Dan,

Thanks for the explicit instructions! As Dan said, the at90usb82 doesn't exist inside of the MightyBoardFirmware. Are there other parts that would work for it? Or does the mightyboard specifically use at90usb82? If so, where do I get the 1.x Arduino package? I downloaded the arduino IDE, and "showed package contents" (I'm using a mac), to see if there were tools in there, but it isn't there.

Also, which direction do you attach the 2x3 ribbon from the AVR? I assume when I look at the board "8u2 icps" right side up, the red line on the ribbon should be on the left.

Thanks again.

Wil

--
You received this message because you are subscribed to a topic in the Google Groups "MakerBot Operators" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makerbot/tBTVx85-hpg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to makerbot+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Dan Newman]

On 23/12/2013, 10:02 AM, Wil Chung wrote:
> Jetguy and Dan,
>
> Thanks for the explicit instructions! As Dan said, the at90usb82 doesn't
> exist inside of the MightyBoardFirmware. Are there other parts that would
> work for it?

Yes and no. Yes in that you could force avrdude to use the a configuration
that doesn't match. But if you do that and things are even slightly wrong,
you could brick the 8u2 to where it now needs a very specialized ("high voltage")
programmer to unbrick. (E.g., if a fuse bit gets set wrong.)

So, find an avrdude distribution which includes the correct avrdude.conf file.

> Or does the mightyboard specifically use at90usb82?

The board has two microprocessors. You need to program both of them.

> If so,
> where do I get the 1.x Arduino package?

http://www.arduino.cc

> I downloaded the arduino IDE, and
> "showed package contents" (I'm using a mac), to see if there were tools in
> there, but it isn't there.

I use a mac as well. It's there.

/Applications/Arduino.app/Contents/Resources/Java/hardware/tools/avr/bin/avrdude -C \
/Applications/Arduino.app//Contents/Resources/Java/hardware/tools/avr/etc/avrdude.conf \
-p at90usb82 -F -P usb -c usbtiny -U flash:w:XXXXXX \

-U lfuse:w:0xFF:m -U hfuse:w:0xD9:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

where I wrote "XXXXXX" supply the full, absolute path to the .hex file with the 8u2 firmware.

> Also, which direction do you attach the 2x3 ribbon from the AVR?

The way which works. You'll need to figure out which is the gnd and orient
it correctly. Also, I have the best luck with (1) the bot powered off, and (2)
the ribbon cable to the LCD display disconnected. I use an AVR ISP programmer
which supplies power to the board using the USB 0.5A power from the Mac. However,
if the LCD display is connected, it sucks down some of the power causing the voltage
to sag too low.

> I assume
> when I look at the board "8u2 icps" right side up, the red line on the
> ribbon should be on the left.

I don't honestly recall. You won't destroy anything if you get it wrong: avrdude
will simply fail to program the chip is all.

Dan

[Joseph Chiu]

Are you sure that there is not a more fundamental problem? Like maybe the lcd itself or some other wired parts are faulting the supply rail(s)?

Sorry for the "is it plugged in?", but better safe than sorry I think...

You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
To unsubscribe from this group and stop receiving emails from it, send an email to makerbot+u...@googlegroups.com.

[Gary Crowell]

Heh,  just looked at my own AVR-ICSP programmer and it's an RS-232 interface.... guess it's time for a new one.

Gary

--
----------------------------------------------
Gary A. Crowell Sr., P.E., CID+

Linkedin  Elance  KE7FIZ

[Dan Newman]

On 23/12/2013, 2:05 PM, Gary Crowell wrote:
> Heh, just looked at my own AVR-ICSP programmer and it's an RS-232
> interface.... guess it's time for a new one.

My favorite AVR ISP programmer is this one,

http://shop.tuxgraphics.org/electronic/detail_avrusb500smd2.html

It's definitely not for everyone -- pretty much requires using a breadboard.
But that's how I program all of my DIP AVRs anyway. At least until they
are in their circuit. And I always have the parts around to jumper it
to a 6 pin header.

But, like I say, this one isn't for everyone. For me, it's just been
my most versatile one. And, of course, you can take one that has
a 6pin header and use jumper wires to get the same versatility.

Dan

[Wil Chung]

I was able to successfully program the 8U2. But when I tried to program the 1280, it seemed to have bricked it. the AVR programmer doesn't seem turn on anymore, and I don't get a buzz tone when I plug the AVR in. There were two commands I executed. One to program the 8U2 (success), and one for the 1280 (failed). :/ Did I miss something? Where should I go from here? (Thanks again for everyone's help) 

This was successful:

 > /Applications/Arduino.app/Contents/Resources/Java/hardware/tools/avr/bin/avrdude -C /Applications/Arduino.app//Contents/Resources/Java/hardware/tools/avr/etc/avrdude.conf -p at90usb82 -F -P usb -c usbtiny -U flash:w:bootloader/8U2_firmware/Makerbot-usbserial.hex -U lfuse:w:0xFF:m -U hfuse:w:0xD9:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9389

avrdude: Expected signature for AT90USB82 is 1E 93 82

avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed

         To disable this feature, specify the -D option.

avrdude: erasing chip

avrdude: reading input file "bootloader/8U2_firmware/Makerbot-usbserial.hex"

avrdude: input file bootloader/8U2_firmware/Makerbot-usbserial.hex auto detected as Intel Hex

avrdude: writing flash (4064 bytes):

Writing | ################################################## | 100% 10.18s

avrdude: 4064 bytes of flash written

avrdude: verifying flash memory against bootloader/8U2_firmware/Makerbot-usbserial.hex:

avrdude: load data flash data from input file bootloader/8U2_firmware/Makerbot-usbserial.hex:

avrdude: input file bootloader/8U2_firmware/Makerbot-usbserial.hex auto detected as Intel Hex

avrdude: input file bootloader/8U2_firmware/Makerbot-usbserial.hex contains 4064 bytes

avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 6.60s

avrdude: verifying ...

avrdude: 4064 bytes of flash verified

avrdude: reading input file "0xFF"

avrdude: writing lfuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 1 bytes of lfuse written

avrdude: verifying lfuse memory against 0xFF:

avrdude: load data lfuse data from input file 0xFF:

avrdude: input file 0xFF contains 1 bytes

avrdude: reading on-chip lfuse data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...

avrdude: 1 bytes of lfuse verified

avrdude: reading input file "0xD9"

avrdude: writing hfuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 1 bytes of hfuse written

avrdude: verifying hfuse memory against 0xD9:

avrdude: load data hfuse data from input file 0xD9:

avrdude: input file 0xD9 contains 1 bytes

avrdude: reading on-chip hfuse data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...

avrdude: 1 bytes of hfuse verified

avrdude: reading input file "0xF4"

avrdude: writing efuse (1 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 1 bytes of efuse written

avrdude: verifying efuse memory against 0xF4:

avrdude: load data efuse data from input file 0xF4:

avrdude: input file 0xF4 contains 1 bytes

avrdude: reading on-chip efuse data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...

avrdude: 1 bytes of efuse verified

avrdude: reading input file "0x0F"

avrdude: writing lock (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of lock written

avrdude: verifying lock memory against 0x0F:

avrdude: load data lock data from input file 0x0F:

avrdude: input file 0x0F contains 1 bytes

avrdude: reading on-chip lock data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...

avrdude: 1 bytes of lock verified

avrdude: safemode: Fuses OK

avrdude done.  Thank you.

However, when I tried the same thing for the 1280, it seemed to have stopped responding. I changed the -p to m1280, because we're apparently loading it into the atmega1280. (and it didn't work with at80usb82). However, these were the results, and I can't get the AVR programmer to turn on again after, removing the AVR programmer, turning the board on and noting nothing happened, and then plugging the AVR programmer back in. There was a verification error:

 > /Applications/Arduino.app/Contents/Resources/Java/hardware/tools/avr/bin/avrdude -C /Applications/Arduino.app//Contents/Resources/Java/hardware/tools/avr/etc/avrdude.conf -p m1280 -F -P usb -c usbtiny -U flash:w:bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex -U lfuse:w:0xFF:m -U hfuse:w:0xD9:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9703

avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed

         To disable this feature, specify the -D option.

avrdude: erasing chip

avrdude: reading input file "bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex"

avrdude: input file bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex auto detected as Intel Hex

avrdude: writing flash (130838 bytes):

Writing | ################################################## | 100% 265.88s

avrdude: 130838 bytes of flash written

avrdude: verifying flash memory against bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex:

avrdude: load data flash data from input file bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex:

avrdude: input file bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex auto detected as Intel Hex

avrdude: input file bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex contains 130838 bytes

avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 211.55s

avrdude: verifying ...

avrdude: verification error, first mismatch at byte 0x1f000

         0x0c != 0xff

avrdude: verification error; content mismatch

avrdude: safemode: Fuses OK

avrdude done.  Thank you.

--
You received this message because you are subscribed to a topic in the Google Groups "MakerBot Operators" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makerbot/tBTVx85-hpg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to makerbot+u...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Dan Newman]

On 23/12/2013, 4:03 PM, Wil Chung wrote:
> I was able to successfully program the 8U2. But when I tried to program the
> 1280, it seemed to have bricked it.

All you did was put a bootloader onto the AVR. So, now that the 8u2 has firmware
and the 1280 has a bootloader, you should then be able to send the firmware down
using MakerWare or RepG....

HOWEVER,

> flash:w:bootloader/8U2_firmware/Makerbot-usbserial.hex -U lfuse:w:0xFF:m -U
> hfuse:w:0xD9:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

/Applications/Arduino.app/Contents/Resources/Java/hardware/tools/avr/bin/avrdude
> -C
> /Applications/Arduino.app//Contents/Resources/Java/hardware/tools/avr/etc/avrdude.conf
> -p m1280 -F -P usb -c usbtiny -U
> flash:w:bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex -U
> lfuse:w:0xFF:m -U hfuse:w:0xD9:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

You used the same fuse bits for the 1280 that you used for the 8u2. That is, you appear
to have used the 8u2 command for the 1280 assuming you could just change the .hex file and
device type. Unfortunately, that's not the case. Fuse bits are HIGHLY device specific. You
may have sent bogus fuse bits to your 1280. Doing that can seriously brick the chip.
For a 1280, you want hfuse:w:0xDA:m not 0xD9. The difference is critical as you just restricted
the boot size to smaller than 4K and the you need all 4K for the bootloader. Fortunately,
this should not have bricked the chip.

So try again, but use the correct avrdude command. It's going to be something similar to

avrdude -C /Applications/Arduino.app//Contents/Resources/Java/hardware/tools/avr/etc/avrdude.conf \
-p m1280 -F -P usb -c usbtiny -U flash:w:bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex \

-U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

I pulled that command out of the MightyBoard dist/ directory.

Dan

[Wil Chung]

Thanks again for the advice. I did find the avrdude command in the dist/ like you suggested, and was able recognize the USBtiny once I removed all other USB devices to my laptop.

I tried flashing the 1280 with the correct fuse bits and got the following:

 > /Applications/Arduino.app/Contents/Resources/Java/hardware/tools/avr/bin/avrdude -C /Applications/Arduino.app//Contents/Resources/Java/hardware/tools/avr/etc/avrdude.conf -p m1280 -F -P usb -c usbtiny -U flash:w:bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex -U lfuse:w:0xFF:m -U hfuse:w:0xDA:m -U efuse:w:0xF4:m -U lock:w:0x0F:m

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9703

avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed

         To disable this feature, specify the -D option.

avrdude: erasing chip

avrdude: reading input file "bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex"

avrdude: input file bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex auto detected as Intel Hex

avrdude: writing flash (130838 bytes):

Writing | ################################################## | 100% 267.01s

avrdude: 130838 bytes of flash written

avrdude: verifying flash memory against bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex:

avrdude: load data flash data from input file bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex:

avrdude: input file bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex auto detected as Intel Hex

avrdude: input file bootloader/1280_bootloader/ATmegaBOOT_168_atmega1280.hex contains 130838 bytes

avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 209.81s

avrdude: verifying ...

avrdude: verification error, first mismatch at byte 0x1f000

         0x0c != 0xff

avrdude: verification error; content mismatch

avrdude: safemode: Fuses OK

avrdude done.  Thank you.

So looking up the verification error on the web, I found this: http://forums.adafruit.com/viewtopic.php?f=20&t=14752 It seems like the 1280 only has 128K of memory, and USBtiny can't flash anything beyond 64K, which is the result of the verification error, I think. I did try flashing another firmware that Makerbot sent me, that's a smaller firmware Replicator_1_75.hex (113Kb), but it still has the verification error at:

avrdude: verifying ...

avrdude: verification error, first mismatch at byte 0x10000

         0x44 != 0x0c

avrdude: verification error; content mismatch

With the Replicator 1.75 firmware, I was able to get the mightyboard to play the startup tone, when I flip on the switch for the board. However, when I go to try to recognize it on ReplicatorG or Makerware, it doesn't find the USB device still. At this point, I'm a bit puzzled. with the 8U2 flashed successfully, my laptop should be able to see the mightyboard as a USB device right?

If it's the case that the 8U2 is fine, and the culprit is USBtiny when flashing the 1280, is there another AVR programmer compatible with AVRdude that you'd recommend that I can buy without having to assemble it, that's pretty cheap and can handle 128K?

Wil

--
You received this message because you are subscribed to a topic in the Google Groups "MakerBot Operators" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makerbot/tBTVx85-hpg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to makerbot+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Dan Newman]

Ignore it. It's not that unusual to have the read-back fail. What matters
is that there was no failure when writing the firmware. Can you now
download the firmware from MakerWare or RepG?

HOWEVER, I suspect that you needed a -e in that avrdude command. When it's
a never-before-used chip, you don't need it and hence why it wasn't in MBI's
dist directory. However, you may have needed it.

So, you can try the command again with the -e -- it's the "chip erase" switch.
I generally have to use it when wiping a previously used chip. However, I
wouldn't worry about the read-back verification failing.

> With the Replicator 1.75 firmware,

You must mean 7.5?

> I was able to get the mightyboard to
> play the startup tone, when I flip on the switch for the board. However,
> when I go to try to recognize it on ReplicatorG or Makerware, it doesn't
> find the USB device still.

From RepG you have to make sure that MakerWare has shutdown the Conveyor
service. (I won't even install MW on a Mac since it installed stuff
to system directories where it shouldn't have, and last time I tried at
least, the uninstall didn't remove everything and left stuff running
in the background -- left conveyor running. Beyond annoying.)

Dan

[Wil Chung]

Dan,

Thanks for the help, especially over Christmas. I did get it to work, and it's talking to Replicator G now. Thanks a bunch!

I have a different problem now, and will post in a new thread later, but just wanted to let you know that you were a lot of help. Thanks!

Wil

Dan

--
You received this message because you are subscribed to a topic in the Google Groups "MakerBot Operators" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makerbot/tBTVx85-hpg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to makerbot+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Dan Newman]

On 25/12/2013, 6:36 PM, Wil Chung wrote:
> Dan,
>
> Thanks for the help, especially over Christmas. I did get it to work, and
> it's talking to Replicator G now. Thanks a bunch!
>
> I have a different problem now, and will post in a new thread later, but
> just wanted to let you know that you were a lot of help. Thanks!

Glad to hear that you got the firmware loaded. Thanks for the followup.

Dan