-
-
Notifications
You must be signed in to change notification settings - Fork 19
rte/v1.1.0/specification.md: Describe GPIO pins purpose #1012
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
We will have some duplication with: https://docs.dasharo.com/unified-test-documentation/generic-testing-stand-setup/ Maybe we should link from generic test setup to the document you have just modified? Especially that you are adding now info on power LED, which is not yet covered in generic test setup at all I think. |
Ohh didn't know that it is already described elsewhere. But still the generic testing stand does not include all the pre-defined OC GPIOs. It is a duplication to some extent, however not entirely.
Sounds like a good idea.
It is not covered, but it should be. I will update the PR. |
@macpijan Now that I look at it again, we have swapped RST and PWR_BTN pins. Per schematics (and my changes in the PR): PWR_BTN is pin 6 and RST is pin 5, while we use the following in the testing stand setup: J11 pin 5 PWR_ON# Per the config https://github.com/3mdeb/RteCtrl/blob/master/config/RteCtrl.cfg#L69 we also have the RST first (409 / GPB1) the PWR_BTN (410 / GPB2). osfv_cli seems to use good pins, because it uses IDs as in RteCtrl.cfg: Now I wonder how many setups got it wrong... |
Signed-off-by: Michał Żygowski <[email protected]>
Signed-off-by: Michał Żygowski <[email protected]>
Signed-off-by: Michał Żygowski <[email protected]>
No description provided.