-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do I compile this for STM32F103CBT6? #59
Comments
try to use UART+ch340(or ftdi ft232) instead of USB by removing the definition USEUSB))) |
Maple Mini has dedicated hardware for manipulating USB pull-up. This logic is necessary to perform re-initialization of the USB connection with host after flashing new firmware without need to perform physical disconnect/connect of USB cable. This logic might conflict with raw Bluepill firmware and leave USB in the state which does not allow host to perform proper USB initialization. Take a look into Maple booltoader code for all relevant details. My guess that it will be enough to make small update to Grbl code and leave pull-up in some predictable state. I don't remember exact value out of top of my head, but in worst case it will take only two experiments to find correct value. |
Yes, maple mini use PB9 to control USB 1.5k pull-up resistor. |
I got it to run just fine on STM32F103C8T6 (bluepill), but when I change the device to STM32F103CBT6 (Maple Mini) and compile it, nothing seems to happen. Blue pill shows up as a STM32 Virtual Com Port, but Maple Mini doesn't seem to do anything. It doesn't even show up as an unidentified USB device.
What do I need to do?
The text was updated successfully, but these errors were encountered: