search

iamthesoy / Tronxy-Marlin-FW

Marlin Firmware for all TRONXY printers
GNU General Public License v3.0
13 stars 4 forks source link

X5SA400-2E - Boot Loop #1

Open Tukamok opened 1 year ago

Tukamok commented 1 year ago

When flashing on my X4SA400-2E, the flash appears to complete successfully, but the system boot loops.

It appears that I have a slightly different chip than the STM32F4XX/STM32F446ZET referenced in the defaults.

My info screen shows S4TM46Z and this is on the CXY-V6-11921 board. I'm not in a place at the moment where I can get the actual chip ID from the board itself, but I have an old picture which shows it partially, as it's covered by a QA sticker. The value is STM32_____T6, if that helps. I'll crack the thing open over the weekend and pull the sticker off if needed.

Do we know what jiggery-pokery needs to be done to reference this chip?

iamthesoy commented 1 year ago

If you can get the full chip name, it should be possible to port things over. I’ll also send an email to my contact at tronxy and see if they have the info needed to port over. On 3 Nov 2022 at 11:03 PM +0800, Tukamok @.***>, wrote:

When flashing on my X4SA400-2E, the flash appears to complete successfully, but the system boot loops. It appears that I have a slightly different chip than the STM32F4XX/STM32F446ZET referenced in the defaults. My info screen shows S4TM46Z and this is on the CXY-V6-11921 board. I'm not in a place at the moment where I can get the actual chip ID from the board itself, but I have an old picture which shows it partially, as it's covered by a QA sticker. The value is STM32_____T6, if that helps. I'll crack the thing open over the weekend and pull the sticker off if needed. Do we know what jiggery-pokery needs to be done to reference this chip? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Tukamok commented 1 year ago

Sorry for the delay. Looks like the answer is:

STM32F446ZET6

iamthesoy commented 1 year ago

I’ve just had a chat look back through my steps I did when flashing klipper to my old X5SA. I ended up having to flash the stock chitu firmware from tronxy to overwrite factory firmware before flashing anything new. Factory firmware seems to have a bug that will cause other firmware to boot loop without first flashing the tronxy firmware. The firmware should be available on the (unofficial) tronxy discord. https://discord.gg/g3sZYd6S If it’s not, you’ll need to reach out to tronxy support via email to get it. Your chip is the same as the chip referenced in the firmware, (STM32F446ZET6  is the same as STM32F4XX/STM32F446ZET) so I’m fairly confident that it should work.

if flashing stock firmware first doesn’t help, let me know and I’ll try to get a fix. On 8 Nov 2022 at 1:59 AM +0800, Tukamok @.***>, wrote:

Sorry for the delay. Looks like the answer is: STM32F446ZET6 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

Tukamok commented 1 year ago

I have the stock v2.11 & 2.15, and with either of those on there initially I still end up with the bootloop.

iamthesoy commented 1 year ago

Can you try flashing using STM cube? It looks like some versions of the board with that CPU don’t like reading .bin files off the SD. On 8 Nov 2022 at 12:02 PM +0800, Tukamok @.***>, wrote:

I have the stock v2.11 & 2.15, and with either of those on there initially I still end up with the bootloop. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>