You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over the past couple of weeks, I've been eagerly watching #12894, #12895, and #13011 and very excited to see support for ST's controller added to Marlin 2.0.x. I've had one of these boards for a couple years now and never could get Marlin4ST to work correctly. Nice work @Bob-the-Kuhn and @thinkyhead!
I wish I would have caught this a couple weeks ago, but while trying to figure out some compilation errors, it hit me that this board actually uses a STM32F103CBT6 processor, not the STM32F4. I've validated this visually on my board and in the BOM published by ST.
I plan to go through the commits above to see if I can get it working, but probably won't get time to do this until later this week.
Thanks!
Wes
The text was updated successfully, but these errors were encountered:
I just pulled down the BOM & schematic from the ST site. They show both a STM32F401VET6 and a STM32F103CBT6. The 401 is the main CPU and is on page 6 of the schematic. The 103 is on page 7 which is labelled STLINK V2.
There's some bugs in the current 2.0.x. See PRs #12 (for the library) and #13011 (for 2.0.x).
Hello!
Over the past couple of weeks, I've been eagerly watching #12894, #12895, and #13011 and very excited to see support for ST's controller added to Marlin 2.0.x. I've had one of these boards for a couple years now and never could get Marlin4ST to work correctly. Nice work @Bob-the-Kuhn and @thinkyhead!
I wish I would have caught this a couple weeks ago, but while trying to figure out some compilation errors, it hit me that this board actually uses a STM32F103CBT6 processor, not the STM32F4. I've validated this visually on my board and in the BOM published by ST.
I plan to go through the commits above to see if I can get it working, but probably won't get time to do this until later this week.
Thanks!
Wes
The text was updated successfully, but these errors were encountered: