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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: