Welcome to the SeeMeCNC Community

Posted: **Sat Nov 04, 2017 3:55 am**

I recently upgraded my Rostock Max V3 to an E3D V6 hotend and had it running/extruding fine until I accidentally blew the small 5A fuse.

I replaced the fuse as I have before and now my printer is stuck on the boot/firmware screen and I can't seem to figure out where my issue is.

The printer shows up fine in mattercontrol and isn't throwing any errors in the console.

I can clear the Eeprom but when I try to flash the firmware, the Arduino console throws some errors about FAST_CWD pointer?

Either way, the whip is still configured and wired exactly the same as it was before I blew the fuse, so I have mostly ruled out a probe wiring error ect.

If anyone has any ideas I would be very grateful.

Posted: **Sat Nov 04, 2017 10:41 am**

Make sure you're using version 1.6.0 of the Arduino IDE.

g.

Posted: **Sat Nov 04, 2017 7:24 pm**

geneb wrote:Make sure you're using version 1.6.0 of the Arduino IDE.

g.

I am using 1.6.0 and experiencing the same "FAST_CWD pointer" error in the Arduino console when I compile the eeprom_clear too.

I can still flash the firmware and the clear still works, but it goes back to being stuck in the boot screen again when I reflash.

Posted: **Sun Nov 05, 2017 8:16 pm**

Can you list the line number where the error occurred, and which firmware you are using please?

FWIW, here is one solution:

http://forum.arduino.cc/index.php?topic=303355.0

Posted: **Mon Nov 06, 2017 1:51 am**

rootboy wrote:Can you list the line number where the error occurred, and which firmware you are using please?

FWIW, here is one solution:

http://forum.arduino.cc/index.php?topic=303355.0

I am using the firmware version linked to in the installation instructions: https://github.com/seemecnc/Firmware

I will edit with the line numbers when I get home.

Posted: **Mon Nov 06, 2017 7:10 am**

rootboy wrote:Can you list the line number where the error occurred, and which firmware you are using please?

FWIW, here is one solution:

http://forum.arduino.cc/index.php?topic=303355.0

This is what I am returning when I try to upload the eeprom_clear example:

0 [main] avr-g++ 10712 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 6808 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
5 [main] avr-gcc 6120 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-gcc 8740 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-gcc 6432 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-gcc 5852 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
12 [main] avr-gcc 3640 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-gcc 9668 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-gcc 4892 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 12600 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 4392 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 11128 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 12248 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 8600 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 5620 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 4668 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 10180 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 952 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 13052 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 4108 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 10952 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 1404 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
17 [main] avr-g++ 7188 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 10164 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 13640 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-g++ 11940 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 9676 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 10588 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 14056 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 10012 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
6 [main] avr-ar 9324 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 5388 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 6244 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 6748 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 3844 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 3376 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 9436 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 1780 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 3020 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 10148 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 10832 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 8740 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 4392 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 4764 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 7216 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 13488 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 14220 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 10220 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
11524 [main] avr-ar 10052 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-ar 13808 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-gcc 12884 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-objcopy 7328 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]
0 [main] avr-objcopy 8088 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]

Sketch uses 1,268 bytes (0%) of program storage space. Maximum is 253,952 bytes.
Global variables use 10 bytes (0%) of dynamic memory, leaving 8,182 bytes for local variables. Maximum is 8,192 bytes.
0 [main] avrdude 8952 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to
the public mailing list [email protected]

Posted: **Mon Nov 06, 2017 8:33 am**

I would try uninstalling and re-installing the Arduino IDE. That's not a firmware issue, it's an internal compiler error.

g.

Posted: **Mon Nov 06, 2017 11:44 am**

Yeah, I would try that too. It looks like something that Arduino borrowed from the cygwin folks is throwing up.

Posted: **Mon Nov 06, 2017 8:52 pm**

geneb wrote:I would try uninstalling and re-installing the Arduino IDE. That's not a firmware issue, it's an internal compiler error.

g.

I've tried this multiple times, and used newer versions of the IDE

Posted: **Tue Nov 07, 2017 12:11 am**

I'm using 1.8.4 and it created my firmware just fine, so I'm not convinced about the version limitations. What firmware and version are you trying to build? I'll see if I can compile it and send it back to you. If you want to do this, please upload a copy of your Configuration.h and I'll use that in the build.

The PC that I'm on is a 64-bit one, but I keep 32-bit ones alive just for these situations. I'll try the 64-bit one first, and then the 32-bit one if need be.

Posted: **Tue Nov 07, 2017 7:21 am**

Have you tried reloading the firmware without the whip plugged in?

Posted: **Tue Nov 07, 2017 9:05 am**

It WILL crash on 1.8.4. that being said, since you don't have the HE280 and it's associated features enabled, you're not pushing the available resources as hard as the HE280 code tends to do..

The problem being reported by the compiler is an internal compiler error (which is why the user is being asked to send a report to the developers of the compiler) and has nothing to do with the firmware - especially if it's choking on the EEPROM_CLEAR. Google result show a lot of hits for this, but very little regarding the Arduino IDE unfortunately.

g.

Posted: **Sat Nov 11, 2017 2:59 am**

geneb wrote:It WILL crash on 1.8.4. that being said, since you don't have the HE280 and it's associated features enabled, you're not pushing the available resources as hard as the HE280 code tends to do..

The problem being reported by the compiler is an internal compiler error (which is why the user is being asked to send a report to the developers of the compiler) and has nothing to do with the firmware - especially if it's choking on the EEPROM_CLEAR. Google result show a lot of hits for this, but very little regarding the Arduino IDE unfortunately.

g.

rootboy wrote:I'm using 1.8.4 and it created my firmware just fine, so I'm not convinced about the version limitations. What firmware and version are you trying to build? I'll see if I can compile it and send it back to you. If you want to do this, please upload a copy of your Configuration.h and I'll use that in the build.

The PC that I'm on is a 64-bit one, but I keep 32-bit ones alive just for these situations. I'll try the 64-bit one first, and then the 32-bit one if need be.

So I tried to flash the firmware on a different computer and it clears, compiles and flashes everything fine. The printer still gets stuck on the boot screen.

Any ideas?

Posted: **Sat Nov 11, 2017 8:45 am**

Unplug the whip from the hot end, then turn on the printer. Is it still stuck? If yes, then you might have bricked your Rambo's I2C bus. If it works, then you've got an issue with you're wiring or hot end board

Posted: **Sat Nov 11, 2017 9:09 pm**

pouncingiguana wrote:Unplug the whip from the hot end, then turn on the printer. Is it still stuck? If yes, then you might have bricked your Rambo's I2C bus. If it works, then you've got an issue with you're wiring or hot end board

Yeah I started her up without the whip and still experienced the boot loop.

I have a new Rambo on the way from SeeMeCNC so hopefully once that arrives across the ocean that should solve my issue.

Posted: **Sun Nov 12, 2017 3:43 am**

Do the Rambo boards use the bootloader? You could try re-writing that back into the chip. Pin 30 is the reset, but that goes to the switch and nothing else. I can't imagine that being the problem.

But I think that you're right, it's going to need a new board.

Posted: **Sun Nov 12, 2017 6:35 am**

rootboy wrote:Do the Rambo boards use the bootloader? You could try re-writing that back into the chip. Pin 30 is the reset, but that goes to the switch and nothing else. I can't imagine that being the problem.

But I think that you're right, it's going to need a new board.

Takes a week or so to get here from the US, but I'll post when I have it and let you guys know if it solves my problem.

Thanks for your help!

Posted: **Sun Nov 12, 2017 7:22 am**

No problem, sorry it didn't get you going.

Posted: **Sun Nov 12, 2017 9:20 am**

The bootloader isn't the issue as he can upload the eeprom_clear program..

g.

Posted: **Sun Nov 12, 2017 10:03 pm**

Most likely, but as a last ditch attempt to save it, I would burn the bootloader. At this point there is nothing to lose...

Posted: **Mon Nov 13, 2017 8:50 am**

*swaps tires after blowing engine* Nope, still won't start.

g.

Posted: **Mon Nov 13, 2017 10:48 am**

You're probably right, but that got me thinking. These are Arduinos after all. I would try loading the "Blink" sketch and see if that runs.

Welcome to the SeeMeCNC Community

Stuck on boot screen

Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen

Re: Stuck on boot screen