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

X15 RevA2 Schematic, ETH_RESETn connection ambiguity #3

Open
stevenj opened this issue Feb 19, 2016 · 2 comments
Open

X15 RevA2 Schematic, ETH_RESETn connection ambiguity #3

stevenj opened this issue Feb 19, 2016 · 2 comments

Comments

@stevenj
Copy link

stevenj commented Feb 19, 2016

The schematic shows ETH_RESETn connected to GPIO3_17 on ball U3
According to datasheet U3 can only be GPIO5_17
GPIO3_17 is AF6
AF6 is shown on schematic as GPIO3_17 also, but as N/C

Which is correct?
ETH_RESETn connected to U3 and GPIO5_17
or
ETH_RESETn connected to AF6 and GPIO3_17

@Chester-Gillon
Copy link

Looking at the BeagleBoard-X15_RevA2.brd file the ETH_RESETn net is connected to ball U3, so the schematic appears to show the correct ball U3 but gives the wrong label GPIO3_17. Agree that from the AM5728 datasheet ball U3 is for gpio5_17.

I also note that the ETH_RESETn net is connected to the KSZ9031RNX devices U14 and U15 via resistors R316 and R317. The BeagleBoard-X15_RevA2.pdf schematic and BeagleBoard-X15_RevA2B_BOM.pdf both show that R316 and R317 are "DO NOT INSTALL". i.e. by default the ETH_RESETn net is not connected in a RevA2.

The RevA2 schematic shows that the RESET_N input on the KSZ9031RNX devices is connected to the ENET_PORZ net.

I think the end result is that the KSZ9031RNX devices are only reset by a power-on reset, which would also reset the AM5728. Did you have a need to reset the KSZ9031RNX devices from a GPIO pin?

@stevenj
Copy link
Author

stevenj commented Oct 10, 2016

No, its a quality comment is all, I know its difficult keeping track of this many IO on a device and easy to get wrong. So I wanted to make a comment so the schematic could be updated to reflect reality at some future revision.

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

2 participants