Skip to content
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

Perhaps an issue with PB3, PB4, PA15 #57

Open
mstrens opened this issue Oct 8, 2018 · 1 comment
Open

Perhaps an issue with PB3, PB4, PA15 #57

mstrens opened this issue Oct 8, 2018 · 1 comment

Comments

@mstrens
Copy link

mstrens commented Oct 8, 2018

In order to use those pins, the code has to ask a remap of pin and to activate a clock (RCC_APB2Periph_AFIO).

Therefore in main.c you currently have
RCC_APB2PeriphClockCmd(RCC_APB2Periph_USART1 | RCC_APB2Periph_GPIOA | RCC_APB2Periph_AFIO, ENABLE);

Still this line is active only if you are using UART1 instead of USB.
Quite similar line of code exist for "limits" and "controls" files but not in stepper.c
So I expect (but not tested it), that it will not be possible to use those pins for step, dir or enable stepper when USB is used instead of uart1.
It would be better to add a line in main.c in order to ALWAYS activate RCC_APB2Periph_AFIO

@Alfrederson
Copy link

They're currently used for flood and mist control. I can confirm they do not work with the current code because those pins are used for JTAG debugging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants