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

Pin Mux Error on P8_40 #34

Closed
jadonk opened this issue Apr 25, 2018 · 1 comment
Closed

Pin Mux Error on P8_40 #34

jadonk opened this issue Apr 25, 2018 · 1 comment
Assignees

Comments

@jadonk
Copy link
Sponsor Member

jadonk commented Apr 25, 2018

From @magicroomy on October 8, 2015 15:29

Hi,
I stumbled about something that I would regard as an error in the pin-mux definition of P8_40

In bone.js, i can find the section for it.
{
"name": "GPIO2_13",
"gpio": 77,
"mux": "lcd_data7",
"eeprom": 52,
"key": "P8_40",
"muxRegOffset": "0x0bc",
"options": [
"lcd_data7",
"gpmc_a7",
"pr1_edio_data_in7",
"eqep2_strobe",
"pr1_pru1_pru_r30_7",
"pr1_pru_pru1_r30_7",
"pr1_pru1_pru_r31_7",
"gpio2_13"
]
},

The following lines indicate the modes for mode 4-6
"pr1_pru1_pru_r30_7",
"pr1_pru_pru1_r30_7",
"pr1_pru1_pru_r31_7",

I think it should be
"pr1_edio_data_out_7",
"pr1_pru1_pru_r30_7",
"pr1_pru1_pru_r31_7",

Could you please check ?

Copied from original issue: jadonk#110

@vaishnavachath
Copy link

@jadonk i looked at : http://www.ti.com/lit/ds/symlink/am3358.pdf , Page No:32 and found that the pin-mux definition of P8_40 should be as per the suggestion.Was the reference material the correct one , should i have looked for the information somewhere else?

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

No branches or pull requests

2 participants