Skip to content
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

document OC_OUT1-3 / GPIO404-406 #5

Open
orangecms opened this issue Mar 1, 2021 · 2 comments
Open

document OC_OUT1-3 / GPIO404-406 #5

orangecms opened this issue Mar 1, 2021 · 2 comments
Assignees

Comments

@orangecms
Copy link

orangecms commented Mar 1, 2021

The datasheet at https://cloud.3mdeb.com/index.php/s/HArgg8jrDmASWGp refers to the following (section "SPI header"):

OC pin GPIO pin function
OC_OUT1 GPIO406 enable SPI VCC
OC_OUT2 GPIO405 set SPI VCC to 3.3V
OC_OUT3 GPIO404 enable SPI lines

The schematics show the J11 header, which lists OC_OUT6 (pin 1), OC_OUT5 (pin 2), OC_OUT4 (pin 3). It seems like something is mixed up here.

@miczyg1
Copy link
Member

miczyg1 commented Mar 1, 2021

These signals are controlled with E_GPA{4,5,6} which correspond to GPIO{404,405,406} seen in the Linux. The only error I see here is the first column which incorrectly states these are OC pins (which was probably true for older RTE revisions), but they are not, they are simply GPIOs from the I/O expander. @pkonkol could you please change the datasheet first column to something like this?

Signal
E_GPA6
E_GPA5
E_GPA4

@pietrushnic pietrushnic assigned TomaszAIR and unassigned pkonkol Oct 5, 2021
@pietrushnic
Copy link
Member

@macpijan I'm not sure if we rev-up datasheet, but at least we should have that fixed in official documentation: https://docs.dasharo.com/transparent-validation/rte/introduction/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants