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
When checking the hardware with a scope however, PC1 state does not change (it's constantly high due to external pullup). PC1 is the only pin showing this behavior - all others work fine. I ran a similar sketch that toggles all pins (apart from those used for SWD and crystal), but still, PC1 seems to be completely inaccessible.
When not using Arduino core and only HAL libraries (compiled in Atollic TrueStudio), this does not happen, PC1 works exactly as expected, so it's most likely not a hardware issue or blown pin.
Any pointers to what could be the cause would be greatly appreciated. I tried removing all alternate functions from PC1 in PeripheralPins.c, but this seems to have had no effect.
The text was updated successfully, but these errors were encountered:
Any pointers to what could be the cause would be greatly appreciated. I tried removing all alternate functions from PC1 in PeripheralPins.c, but this seems to have had no effect.
About that, this is normal as AF is not used for basic GPIO usage.
Hi,
I came across a strange issue. On STM32L452RE, the following code should toggle PC1 high and low:
When checking the hardware with a scope however, PC1 state does not change (it's constantly high due to external pullup). PC1 is the only pin showing this behavior - all others work fine. I ran a similar sketch that toggles all pins (apart from those used for SWD and crystal), but still, PC1 seems to be completely inaccessible.
When not using Arduino core and only HAL libraries (compiled in Atollic TrueStudio), this does not happen, PC1 works exactly as expected, so it's most likely not a hardware issue or blown pin.
Any pointers to what could be the cause would be greatly appreciated. I tried removing all alternate functions from PC1 in PeripheralPins.c, but this seems to have had no effect.
The text was updated successfully, but these errors were encountered: