search

dgtaheno / artillery-Genius-Genius_Pro-X1-Marlinfw

Marlin 2.1.2.1 Firmware + TFT firmware for Artillery Genius 3D printer
GNU General Public License v3.0
37 stars 5 forks source link

Flashing a GeniusPro Problems #34

Closed jmfloyd closed 3 months ago

jmfloyd commented 3 months ago

Discussed in https://github.com/dgtaheno/artillery-Genius-Genius_Pro-X1-Marlinfw/discussions/33

Originally posted by **jmfloyd** May 7, 2024 Hello, Thanks for this work. I am running a Genius Pro, but am having troubles re-flashing the main board. I get "no printer attached" on the TFT after re-flashing. I could only run an re-flash using STM32CubeProg, using the BOOT jumper, other methods did not work for me. Now I have tried to revert it back to the stock artillery firmware with similar results. In all this I have varied the printer baud rates at the TFT, powered the system up and down ... with no success. I had updated the TFT earlier to the latest artillery version you provided, and it was communicating with the original firmware that came with the printer (eg showing current bed and head temperatures. etc). Now temps are all 0/0. Any suggestions? Do you know if there is something special that needs to be set in the STM32CubeProg flashing (it is the one common activity in all my experiments)? I havent been able to find any thing to help. I seem to be following all the published descriptions. It sounds like a flashing problem to me - there are no errors from the STM32 software, it says it copied all the firmware down. I am running it on a linux system, and the DFU port comes up nicely, and is recognized as such. Extra info, when I attempt to flash the motherboard using STM32CubeProg, I get messages (?fatal?) that sector xxxx does not exist during flashing. xxxx is 0 to 5. Is this relevant? It sounds like something else is corrupted. At the monent the GeniusPro is totally bricked. After powering on after flashing, there is no usb serial connection available on the board's USB port (assuming that is whats supposed to happen). This is similar to the TFT not seeing the printer through its serial link. Would eeprom be initialised straight after flashing in this case as I cant issue the reset gcodes. Any suggestion would be appreciated. My last attempt was to undertake a full build from the latest release of Marlin and tried to flash that. Same non response. Cheers John
jmfloyd commented 3 months ago

This issue has now been solved. I switched to using dfu-utils (on Linux) to write the firmware. Success, everything is working. Could reset the eeprom using the usb port on the motherboard.

Still not sure what happened using STM32CubeProg!!

Thank you for the updates you have provided.

John