search

OctoPrint / OctoPrint-FirmwareUpdater

OctoPrint plugin for flashing pre-compiled firmware images to a 3D printer.
https://plugins.octoprint.org/plugins/firmwareupdater/
GNU Affero General Public License v3.0
353 stars 78 forks source link

Ender 3 v3 SE support #354

Closed KaiStarkk closed 10 months ago

KaiStarkk commented 11 months ago

Is this printer currently supported?: Creality Ender 3 v3 SE -- GD32F303RET6 ARM board

benlye commented 10 months ago

How do you currently update the board?

KaiStarkk commented 10 months ago

This one is updated with MicroSD card for the screen (load firmware onto SD card, insert into printer while powered off, then start) -- then with SD card for the main board in the same way.

benlye commented 10 months ago

Then you should be able to use the MarlinBFT method. Setting it up is a pain due to the Python dependencies. There is another open issue that should explain the workarounds - I need to get around to updating the docs.

KaiStarkk commented 10 months ago

Managed to install heatpack and marlin-binary-protocol without issue, but I might be out of luck. The reason for asking about support for this printer is that the SD slot is currently broken, seems to be a common issue.

It appears I would need to first install firmware with BINARY_FILE_TRANSFER:1 set, which I can't do without the slot being fixed. I assume the other methods like avrdude aren't applicable or would also need that flag set?

benlye commented 10 months ago

You might be able to use the lpc176x method. Your current firmware will have to expose the SD card to the host though. If it doesn't, you are in the same spot with needing to flash a new firmware to enable the required options.

github-actions[bot] commented 10 months ago

This issue has been automatically marked as stale because it has not had any recent activity. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed in 5 days.

github-actions[bot] commented 9 months ago

This issue has been automatically locked because there was no further activity after it was closed. Please open a new issue for any related problems.