Open yu3000 opened 8 months ago
Greetings. It should work in theory, because in fact only TX/RX and power management are used. The chipset itself is the same - esp8266.
OK, I will have a try and give a feedback then. Thanks very much
I couldn't find my esp-01 and find a nodemcu(esp32), I have finished mdifying codes wireless_klipper_sta and patching klipper and finished a compile to get a klipper's hex file ,please see my attachment later. Actually, my printer's mcu is mks gen 2.1,which is based on mega2560, I don't know where to put the klipper's hex file , node mcu or printer's mcu and how to flash it?
I use “socat pty,link=/tmp/ttyS0,raw,echo=0 tcp:espip:8888" to create virtual serial port 。 make flash FLASH_DEVICE=/tmp/ttyS0 with above commond, the hex will be flashed to my esp wifi mcu? However ,I think the device flashed should be my printer's mcu?
Greeting. It seems to me that for the firmware MKS Gen I v.2.1 everything should be a little different. See https://github.com/makerbase-mks/Klipper-for-MKS-Boards/tree/main/MKS%20Gen%20l
Hi, yu3000
I admit that I was wrong. I didn't know that it was possible to upload the mcu firmware not via an sdcard.
I've looked through the documentation and code - I'll try to integrate into the existing ecosystem. I must say right away - downloading via a virtual serial port (via socat) will not work.
Thanks for your share, I only have a esp-01,can I use it without modifing the firmware codes?