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
We have decided to use a PCIE-x1 edge connector as our standard test/debug header.
We've broken out SWD, multiple serial ports, QSPI, USB, power, etc.
Not having the time nor intimate knowledge of testing for Mbed OS, we have not put a great amount of thought into which signals and where to put them on the header
Considering what seems to be a lack of formal specification for the Arduino header, would it be beneficial to specify an alternative test/debug/expansion header for Mbed OS boards?
As of this moment we will probably be adding an Arduino header to our CI/test/debug board in order to support the current Mbed ci-test-shield over our PCIE-x1 connector.
The text was updated successfully, but these errors were encountered:
@maclobdell
We have decided to use a PCIE-x1 edge connector as our standard test/debug header.
We've broken out SWD, multiple serial ports, QSPI, USB, power, etc.
Not having the time nor intimate knowledge of testing for Mbed OS, we have not put a great amount of thought into which signals and where to put them on the header
Considering what seems to be a lack of formal specification for the Arduino header, would it be beneficial to specify an alternative test/debug/expansion header for Mbed OS boards?
As of this moment we will probably be adding an Arduino header to our CI/test/debug board in order to support the current Mbed ci-test-shield over our PCIE-x1 connector.
The text was updated successfully, but these errors were encountered: