STM32 NUCLEO boards with Ethernet connector: solve conflict with D11 arduino pin #4272
Conversation
|
Looks fine to me. What about The idea about config is that a target provides default config, in this case setting D11 to a default configuration. A user can easily find out the default configuration, read the description what it does, and overwrite it if needed. Based on this, I would expect this as a target configuration. |
…arduino pin If you are using Ethernet, and not SPI Arduino pins: => keep your board with the default configuration If you are using SPI Arduino pins, and not Ethernet: => you should remove the JP6 bridge on the front side of the board If you need SPI Arduino and Ethernet: => you have to patch the NUCLEO board on the back side: set solder bridge SB121 to off, and SB122 to on => D11 is no more connected to PA_7 but to PB_5 => overwrite d11_configuration config value in json file
jeromecoutant
force-pushed
the
PR_F429_D11
branch
from
fcd6b30
to
0016306
Compare
|
Hi @0xc0170 Please, check the new commit |
|
@jeromecoutant Thanks for the update, LGTM |
|
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
0xc0170
added
ready for merge
release-version: 5.4.6
and removed
needs: CI
ready for merge
labels
Description
STM32 NUCLEO boards with Ethernet connector are:
If you are using Ethernet, and not SPI Arduino pins:
=> keep your board with the default configuration
If you are using SPI Arduino pins, and not Ethernet:
=> you should remove the JP6 bridge on the front side of the board
If you need SPI Arduino and Ethernet:
=> you have to patch the NUCLEO board on the back side: set solder bridge SB121 to off, and SB122 to on
=> D11 is no more connected to PA_7 but to PB_5
=> enable ETHERNET_SPI_D11_CONFLICT macro in mbed_app.json file
Status
READY