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
Key point I want to make: PB12 connects to TGT_SWDIO with an 100R resistor, PB14directly connects to TGT_SWDIO.
In ARMmbed/DAPLink, by IO_config.h, the out pin is PB14 and the in pin is PB12.
So if we use the firmware directly on either board:
PB14 as output is connected TGT_SWDIO, meaning if the DAPLink decides to pull HIGH but the target board decides to pull LOW (like in a buggy or target-board-broken situation), something is going to fry.
PB12 is already in input mode so already high-impedence. Adding 100R doesn't make a change?
Any chance the two pins are accidentally swapped somehow? Or I have missed something trivial (not professional in embedding)? Thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm not sure whether
mbed-HDK-Eagle-Projects is synced with
ARMmbed/DAPLink
at all. So maybe I'm simply holding a wrong assumption to start with...But if they are supposed in sync, something confuses me:
PB12
connects toTGT_SWDIO
with an 100R resistor,PB14
directly connects toTGT_SWDIO
.ARMmbed/DAPLink
, by IO_config.h, the out pin isPB14
and the in pin isPB12
.So if we use the firmware directly on either board:
PB14
as output is connectedTGT_SWDIO
, meaning if the DAPLink decides to pull HIGH but the target board decides to pull LOW (like in a buggy or target-board-broken situation), something is going to fry.PB12
is already in input mode so already high-impedence. Adding 100R doesn't make a change?Any chance the two pins are accidentally swapped somehow? Or I have missed something trivial (not professional in embedding)? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions