1 (edited by adrian 2013-07-08 15:33:47)

Topic: Guide to Updating Firmware on "new" (Printrboard) Motherboard (WIP)

Ok, good news... the current firmware we all use and refer to, works - if you have the latest versions.

Heres a dirty quick guide, but I can't test one crucial bit - Uploading to the actual Solidoodle/Printrboard as I can't tell you what Bootloader they have used. I'm guessing its the CDC/DFU one.. but thats what I am.. guessing...

So until I have my hardware back from the Fab, so someone else can confirm in the meantime, consider this very much a work in progress... Follow these steps at your own risk/peril/etc...

Step 1)
Download the latest Arduino IDE from http://arduino.cc . 1.0X is what you want - NOT 022!

Step 2)
Download from http://www.pjrc.com/teensy/td_download.html the appropriate OS Installer. Install the Teensy setup.

Step 3)
Download from github my beta; https://github.com/ozadr1an/Solidoodle-Marlin_v1 (This is bleeding edge, call this 'devel')
Or download Lawsy's (so lets call that 'Stable') : https://github.com/mlaws/solidoodle2-marlin

Step 4) Unpack the marlin folder into the Arduino Sketches folder (usually Documents/Arduino),

Step 5) Launch Arduino, select Tools->Board->Teensy2.0++  . Also via Tools->ComPort set it to the comport your Solidoodle installed

Step 6)and open up the Marlin sketch. Edit Configuration.h and change the line that says

#define MOTHERBOARD 62

to read

#define MOTHERBOARD 81

If you have a Solidoodle3, be sure to also set the following at the top of Configuration.h correctly.

// change to 3 for SD3 //{SD Patch}
#define SOLIDOODLE_VERSION 2 //{SD Patch}

Step 7)
Click 'Verify'... It will now compile the firmware for you. There *will* be warnings, but these can be ignored. The 'default' config of the firmware is coming in at ~62k of the 128k and will use about 3.2k of the 8k RAM.. so the board is near enough 50% used

Step 8)
Now 'Upload' to the board.

And heres where I can't help until I get some info on exactly what Bootloader Solidoodle are shipping.  However, on the plus side, you now have a .hex file you can upload via any of the methods that work - its living in your Temp directory in the most recently modified 'random' name (on windows) .. just search your OS Temp directory for .hex files (recursively!).

If anyone can figure out what bootloader is shipped - I can finish the guide.

But really the key thing here is that we have firmware that would outwardly appear to 'work' ... its just a question now of the best upload procedure... (Short of telling you to use an ICSP dongle and just blasting it that way.... which you can do if you can ! )

I stress here - this firmware compiles without error, and would otherwise appear to have the correct Pins setup if you use Teensy2.0++ and Motherboard==81...  But the above is all based on compilation and system simulation, not actually loading it anywhere. I don't get my new motherboards back from the fab-house till late july....

2

Re: Guide to Updating Firmware on "new" (Printrboard) Motherboard (WIP)

OK so I have been trying this many ways to upload new firmware so I can use my new full metal hotend. and have come up short every time. I have tried it with the new 1.0 arduino and with the 002 arduino with no luck. HID Bootloader give me and error saying. teensy loader command line version 2.0. Hope this info can help come up with some answers I just need a few more degrees out of the machine. And right now it keeps freezing up.

3

Re: Guide to Updating Firmware on "new" (Printrboard) Motherboard (WIP)

This post does not work since it was based upon CDC boorloader. Printrboard uses HID.

This tutorial works: http://wiki.solidoodle.com/update-firmware

Chuck Bittner is a quadriplegic gamer who is petitioning the major console developers to include internal button remapping in all console games. You can help.
Sign Chuck Bittners petition

4

Re: Guide to Updating Firmware on "new" (Printrboard) Motherboard (WIP)

Sticky this?

5

Re: Guide to Updating Firmware on "new" (Printrboard) Motherboard (WIP)

I have two printrboards from printrbot sitting around. Can I be of assistance in testing or are the boards likely to be too different in terms of bootloaders?

I ideally I see us having some define code in configuration.h to set either Sanguinololu, printrboard or even RAMPS such as the define solidoodle 2 or 3 code.