Custom Board w/ STM32G0B1CEU6 - 512K

[syph3rd]

Hey Guys,

I have a custom board using an STM32G0B1CEU6, I have tried to flash Katapult viaan ST Link but the board refuses to operate and i need to hold it to ground while connecting in via SWD to get the chip in a useable state.

being that the chip is 512K vs 128K would this cause issues?

Thanks

[Arksine]

I don't think the amount of onboard flash should matter. As a general rule Katapult runs a subset of MCUs supported by Klipper....so one can always try to see if it will run Klipper first, then see if Katapult is supported.

If Klipper runs successfully but Katapult does not then the only other advice I can provide for a custom design is to use a debugger to see what is going on when the application is loaded.

Edit: one thing you could try is to build using Debian bullseye or bookworm. The tools change over time, and its possible that a newer version is introducing an issue.

[syph3rd]

Thanks Eric, I spent some time with it and have it functional. Thank you for your response. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Eric Callahan ***@***.***> Sent: Thursday, May 30, 2024 10:19:55 PM To: Arksine/katapult ***@***.***> Cc: Nathan Vlotis ***@***.***>; Author ***@***.***> Subject: Re: [Arksine/katapult] Custom Board w/ STM32G0B1CEU6 - 512K (Issue #123) I don't think the amount of onboard flash should matter. As a general rule Katapult runs a subset of MCUs supported by Klipper....so one can always try to see if it will run Klipper first, then see if Katapult is supported. If Klipper runs successfully but Katapult does not then the only other advice I can provide for a custom design is to use a debugger to see what is going on when the application is loaded. — Reply to this email directly, view it on GitHub<#123 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMLTJICFLOQ455YJXFWJTZ3ZE4KOXAVCNFSM6AAAAABIQKBU4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZGQZTGMBUGA>. You are receiving this because you authored the thread.Message ID: ***@***.***>