Closed terjeio closed 4 months ago
I see usb_cdc is set to 0 for the Nucleo boards, the F756 I have support both USB <> UART via the ST-link interface and native USB and the F7 does as well?
It does yes, presume I can have the drop-down enabled but leave the ST-link UART as default?
New is is number of i2c_ports, I have set this to 1 at the driver level, if a board has a connector for I2C it should be added at the board level as well.
Thanks, I was thinking of adding SPI and I2C headers to my board - just for tinkering. For I2C, would it be better to use a different port than the one already in use for the EEPROM?
It does yes, presume I can have the drop-down enabled but leave the ST-link UART as default?
This is what I do.
Thanks, I was thinking of adding SPI and I2C headers to my board - just for tinkering. For I2C, would it be better to use a different port than the one already in use for the EEPROM?
Not really. The only reason for not would be that some external device might hang the bus. I have added level shifters on my boards to allow the use of 5V devices:
J16 is the header layout I and Phil Barret use. QWIIC is another option but that does not have a pin for the strobe input.
Thanks, merged..
I see usb_cdc is set to 0 for the Nucleo boards, the F756 I have support both USB <> UART via the ST-link interface and native USB and the F7 does as well?
New is is number of i2c_ports, I have set this to 1 at the driver level, if a board has a connector for I2C it should be added at the board level as well.