Compiled 3.5.3 MK3S Firmware not working
Hello,
i try to compile und run firmware but its not working. When flashing my own firmware lcd shows random chars and nothing works. When flashing back stock firmware all is good again.
I working according the readme. workflow:
- installed Arduino Windows 1.6.8 and turned it to portal version
- installed Rambo Board
- modified platform.txt like descriped
- got firmware source from download (3.5.3) and as second try git version
- copied variants/1_75mm_MK3S-EINSy10a-E3Dv6full.h to configuration_prusa.h
- no more changes!
- compiling works, upload via arduino and alternativ as hex with xloader
--> all tests ending in random chars on lcd, not working
Can you please help me?
Thanks,
Steffen
Re: Compiled 3.5.3 MK3S Firmware not working
Hello,
is nobody out there who could help me? I need to recompile the firmware without the z-axis-always-on option.
Steffen
Re: Compiled 3.5.3 MK3S Firmware not working
Have you deleted (or renamed) the Liquidcrystal folder in the libraries for the Arduino IDE? It seems if you don't do this it messes up the display by displaying random characters. Hope this helps. Theres a slightly more in-depth description here: https://zaribo.com/blog/how-to-compile-and-modify-prusa-firmware-part-i-setting-up-the-environment/
Re: Compiled 3.5.3 MK3S Firmware not working
Edit config.h
The end of it must be changed to primary language support or you will get random chars as you describe despite successful compilation. Prusa keeps the default state of the file in a stupidly non-usable state.
//LANG - Multi-language support
#define LANG_MODE 0 // primary language only
//#define LANG_MODE 1 // sec. language support
#define LANG_SIZE_RESERVED 0x2f00 // reserved space for secondary language (12032 bytes)
#endif //_CONFIG_H
Also, you should have no need to delete the liquid crystal file unless you have a special display board installed.
The Prusa compilation instructions are quite cryptic for first time compilers. I have some alternative instructions that may be more clear. Just use the desired firmware branch instead of my 0.9 degree motor branch.