How'd I managed to build such that console.log() doesn't work?

I just tried this firmware image http://drazzy.com/espruino/espruino_1v63­_espruino_1r3_bigram.bin (the one I posted when v63 came out), and console.log gives function not found:

(this example from connecting with the IDE):

>echo(0);
ERROR: Function not found! Skipping. at line 1 col 8
console.log("<<"+"<<<"+JSON.stringify(pr­ocess.env)+">>>"+">>...
        ^
=undefined
>

All I changed in the build was the makefile and EspruinoBoard.py to use the full 64k of ram.

Console.log works with the wiznet version though!

http://drazzy.com/espruino/espruino_1v63­_espruino_1r3_wiznet_bigram.bin

Any thoughts on what I might have screwed up to break console.log? It's a rather important function!

I only have one Espruino down here, so I haven't checked it against a second one, so I don't know if the problem happens on my other Espruino.

The plot thickens - reset(); fixes it!

reset(); followed by save(); fixed the issue. Any thoughs on what might have happened?

It could be the way you're programming the board - the normal bootloader will only erase 256kB of flash (that's all it thinks it has!), but if Espruino writes saved code into something above that then it won't get erased when you re-flash.

That's normally not a problem, in fact it's kind of handy - but if anything changes internally in the Espruino code then it may get confused by the 'old' code from Flash. That's probably what happened I guess...