-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flash firmware su mks dlc32 v.2.1 #111
Comments
Il firmware originale e FluidNC riesco a caricarlo senza problemi, la scheda funziona perfettamente. Quale sarebbe la procedura corretta? |
quale versione (e con quali impostazioni) dovrei caricare il firmware generato da web build? |
Hi, I can't load grblhal firmware on mks dlc32, the card is not seen by lightburn The procedure is as follows... I generate the firmware with the web build for ESP32 and MKS. Before loading the new firmware I formatted the card with mks esp32 download tools Then I load the firmware, downloaded from Web Build, with version 3.6.5 with these parameters.. Lightburn doesn't recognize the card at the end. It's been a long time since I formatted the card and I seem to remember that the procedure was this... Where am I wrong? The original firmware and FluidNC I can load it without any problems, the board works perfectly. What would be the correct procedure? Which version (and with what settings) should I load the firmware generated by Web Build? |
I do not know the MKS download tool, when I erase then download with the ESP32 download tool I can connect with ioSender. I do not have a LightBurn license so cannot check that. If you connect with a terminal program such as PuTTY what output do you get and does the controller respond to commands? |
Eccomi, rifaccio da zero la procedura e genero il firmware (oggi) con solo LB cluster attivato. Stavolta utilizzo soltanto lo strumento esp 3.6.5, sia per cancellare che per il flash Spengo la scheda e riavvio eseguo il flash con le impostazioni in foto spengo e riaccendo ne Lightburn ne iosender riconoscono la scheda scarico Putty (la prima volta che lo scarico e non lo so usare) e apro la connessione seriale COM4 115200 e l'unica cosa che posso fare nel terminale seriale è il comando "?" e ottengo come da foto, non accetta ad esempio $i ecc.. accetta soltanto il "?" rieseguo la cancellazione del firmware sempre con lo strumento esp 3.6.5 spengo la scheda e riaccendo Spengo e riaccendo Sia Lightburn che lasergrbl vedono tranquillamente la scheda Con il firmware del 6/09/23 non riesco ad accedere ne con iosender ne con putty ma accedo con Lightburn e lasergrbl Ecco la discussione del firmware di settembre #77 |
Try shorting the feed hold pin to ground - Grbl/grblHAL does not accept any command when in |
This? And please translate comments to english before posting, I do not read italian. |
I redid the erase procedure (with sda+gnd together), I switch to flash again with the jumper...Lightburn doesn't see the card, iosender 2 times out of 10, putty nothing and lasergrbl sees it this way, first marks at the top errors, does not accept the "?" but accept $$ and $i, this doesn't seem normal to me. |
I guess I have to buy a MKS board in order to determine what is going wrong. If you connect with a terminal can you interact with the controller? With a fresh Web Builder version:
|
-If you connect with a terminal can you interact with the controller? $I give an answer? ?Also? So what? - The behavior of the terminal is described in the previous steps where with the new firmware only $i and no "?", sometimes nothing, but everything with error messages when opening the connection. I don't know what mks wants to have the correct flash but the one generated in September accepts it without problems |
So you get "Hold" state even with the SDA pin shorted to ground when sending
It is a edge version, also referenced in the sender Wiki.
0.9g is the Web Builder version itself, the generated firmware is currently 20240619: |
I may have found the reason. SDA is connected to GPIO0 (BOOT) and the september firmware is built with an older version of the ESP-IDF framework and the two versions of the ESP32 dev boards I have behave differently - one works correctly and one not. So it may be a combination of chip revision (or board design), framework version and the use of GPIO0 that causes the issue. Or not... Anyway, I will remove feed hold support and post a build for you to try. |
ok, thanks, I'll wait for the new firmware to try then. |
Here you go: |
Salve, in futuro verrà aggiunta qualche opzione su web build per generare il firmware con il problema risolto? |
Hi, I saw the new build and changelog, where my problem for esp32 is mentioned. I generate the firmware but it doesn't load it, same procedure as before |
Somehow the commit did not make it through - should be ok now. |
Salve, non riesco a caricare il firmware grblhal su mks dlc32, la scheda non viene vista da lightburn
![image](https://private-user-images.githubusercontent.com/52679577/337641438-c92cf40f-af95-469b-a9ce-51cba89520a0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwMDEzMzksIm5iZiI6MTcyNDAwMTAzOSwicGF0aCI6Ii81MjY3OTU3Ny8zMzc2NDE0MzgtYzkyY2Y0MGYtYWY5NS00NjliLWE5Y2UtNTFjYmE4OTUyMGEwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE4VDE3MTAzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI0NzlmMzFjZmRhYzBmMGY3NjBiMWRkYjg5ODdjZjViYWQ2ZmI5YzY0ZTY0YjBmMDdiYWVkYzU3MDk3MTNmZTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.tgwhlD_kuKlcDhHTXubeiqprCzhMIdbjhTMqmbOrQa4)
![image](https://private-user-images.githubusercontent.com/52679577/337641679-dab56114-bdd6-462d-a151-10a191b03b3e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwMDEzMzksIm5iZiI6MTcyNDAwMTAzOSwicGF0aCI6Ii81MjY3OTU3Ny8zMzc2NDE2NzktZGFiNTYxMTQtYmRkNi00NjJkLWExNTEtMTBhMTkxYjAzYjNlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE4VDE3MTAzOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc4MzBlM2MzYzg1YTg1YTcyNjYxNjRmZjIzMDcyMjEzM2Q4MTQyNTcyMWYxYjVlMjZiNWVhZDY2NjNkNGJmMjUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.TqXJHv5fBO6pJK11nj1lo1SeEihoUEkRMTak8ugqwGY)
la procedura è la seguente...genero il firmware con il web build per esp32 e mks.
Prima di caricare il nuovo firmware ho formatto la scheda con mks esp32 download tools
successivamente carico il firmware, scaricato da web build, con la versione 3.6.5
con questi parametri..
Alla fine lightburn non riconosce la scheda..
è da tanto che non formatto la scheda e mi sembra di ricordare che la procedura era questa...dove sbaglio?
The text was updated successfully, but these errors were encountered: