Control board unknown March 16, 2020 09:14PM |
Registered: 4 years ago Posts: 3 |
Re: Control board unknown March 17, 2020 03:48PM |
Registered: 4 years ago Posts: 19 |
Re: Control board unknown March 17, 2020 07:38PM |
Registered: 4 years ago Posts: 3 |
Re: Control board unknown March 17, 2020 08:38PM |
Registered: 4 years ago Posts: 19 |
Re: Control board unknown March 17, 2020 08:43PM |
Registered: 4 years ago Posts: 19 |
Re: Control board unknown March 18, 2020 12:27AM |
Registered: 4 years ago Posts: 19 |
Re: Control board unknown March 18, 2020 06:25AM |
Registered: 4 years ago Posts: 3 |
Quote
longbeardpolymer
how did you determine that it does not run marlin? it is a 32bit board. there is a short list of firmwares that will run on it. you can change the default marlin startup screen on the LCD. you can change the icons. but you can tell sometimes because the menu is like marlin. that expansion header looks like from a duet 2 but the STM32F103 makes me think SKR. did you already try the tutorial on how to communicate with the build environment over USB for marlin 2.0? that will confirm %100 that it does not run marlin. that one is an easy test. after that you can try poking it with tools made for other firmwares. eventually you will find the bootloader or at least a UART you can send commands to start checking and uploading firmware. I googled 32bit 3d printer board firmware stm32f1. found this reprap fork. not sure that is a dead end.
[github.com]
you can go through the top 5 firmwares that run on STM32F103 and just try some kind of UART over USB. thats what I would do.
I don't know Klipper, but I will take a look.Quote
longbeardpolymer
I think I may have some useful information. if that main board was setup to work with a pi then that 40 pin connector would go to the pi. then that would be for octoprint and klipper. so maybe it is running klipper? and if so you can find the UART by looking at the pi 40 pin header. you can get the serial speed, stop bit, parity, flow control from reading the klipper source or at least one of the make files. if you can not identify the pin 1 on the 40 pin header, start looking for continuity with the USB shields that we know are the ground to the entire board. that will tell you the ground pins on that 40 pin header. then you can figure out the rest.
[github.com]