Thanks john. I had a feeling it was something like that but i still don't understand why some overlays change direction on some pins. Its tough to find much information on writing overlays out there.
In the TI pinmux tool when you define the mcasp pins default is all set to input but there is a checkbox to set them as outputs. Some of the clock pins are I/O but i don't see that being set anywhere either. I also don't like the fact that if there is an error when compiling an overlay it doesn't spit out a line number where said error is. It's rather non verbose. On 4/29/2016 5:47 AM, John Syne wrote: > The pinmux input/output setting are only relevant when using GPIO. > When using a peripheral like McASP, the input/output are defined by > the pin function. Also, the serializers directions are defined by: > > serial-dir = < /* 0: INACTIVE, 1: TX, 2: RX */ > 2 0 1 0 > 0 0 0 0 > 0 0 0 0 > 0 0 0 0 > >; > > Regards, > John > > > > >> On Apr 28, 2016, at 9:43 PM, evilwulfie <[email protected] >> <mailto:[email protected]>> wrote: >> >> Not much help >> there is a file i have found BB-BONE-AUDI-03-00A0.dts >> that have other settings >> >> fragment@0 { >> target = <&am33xx_pinmux>; >> __overlay__ { >> >> bone_audio_cape_audio_pins: >> pinmux_bone_audio_cape_audio_pins { >> pinctrl-single,pins = < >> 0x1ac 0x20 /* mcasp0_ahclkx, INPUT | MODE0 */ >> 0x19c 0x22 /* mcasp0_axr2, INPUT | MODE2 */ >> 0x194 0x20 /* mcasp0_fsx, INPUT | MODE0 */ >> 0x198 0x08 /* mcasp0_axr0, OUTPUT | MODE0 */ >> 0x190 0x20 /* mcasp0_aclkx, INPUT | MODE0 */ >> >; >> }; >> }; >> }; >> >> seems closer but still backwards in my eye >> >> >> On 4/28/2016 9:39 PM, William Hermans wrote: >>> I really hate when gmail does that crap . . . >>> >>> pinctrl-single,pins = < >>> 0x190 (*PIN_INPUT_PULLDOWN* | MUX_MODE0) /* >>> mcasp0_aclkx.mcasp0_aclkx */ >>> 0x194 (*PIN_INPUT_PULLDOWN* | MUX_MODE0) /* >>> mcasp0_fsx.mcasp0_fsx, INPUT */ >>> 0x198 (*PIN_INPUT_PULLDOWN* | MUX_MODE0) /* >>> mcasp0_axr0.mcasp0_axr0 */ >>> 0x19c (*PIN_INPUT_PULLDOWN* | MUX_MODE2) /* >>> mcasp0_ahclkr.mcasp0_axr2 */ >>> 0x1ac (*PIN_INPUT_PULLDOWN* | MUX_MODE0) /* >>> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */ >>> >; >>> >>> On Thu, Apr 28, 2016 at 9:38 PM, William Hermans <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> pinctrl-single,pins = < >>> 0x190 (*PIN_INPUT*_PULLDOWN | MUX_MODE0) /* >>> mcasp0_aclkx.mcasp0_aclkx */ >>> 0x194 (*PIN_INPUT*_PULLDOWN | MUX_MODE0) /* >>> mcasp0_fsx.mcasp0_fsx, INPUT */ >>> 0x198 (*PIN_INPUT*_PULLDOWN | MUX_MODE0) /* >>> mcasp0_axr0.mcasp0_axr0 */ >>> 0x19c (*PIN_INPUT*_PULLDOWN | MUX_MODE2) /* >>> mcasp0_ahclkr.mcasp0_axr2 */ >>> 0x1ac (*PIN_INPUT*_PULLDOWN | MUX_MODE0) /* >>> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */ >>> >; >>> >>> On Thu, Apr 28, 2016 at 9:24 PM, evilwulfie >>> <[email protected]> wrote: >>> >>> Ok I am slightly confused her on the pinmux signal directions. >>> >>> In the BB-BONE-AUDI-02-00A0.dts file we have all pins set to >>> inputs >>> >>> fragment@0 { >>> target = <&am33xx_pinmux>; >>> __overlay__ { >>> bone_audio_cape_audio_pins: >>> pinmux_bone_audio_cape_audio_pins { >>> pinctrl-single,pins = < >>> 0x190 (PIN_INPUT_PULLDOWN | MUX_MODE0) /* >>> mcasp0_aclkx.mcasp0_aclkx */ >>> 0x194 (PIN_INPUT_PULLDOWN | MUX_MODE0) /* >>> mcasp0_fsx.mcasp0_fsx, INPUT */ >>> 0x198 (PIN_INPUT_PULLDOWN | MUX_MODE0) /* >>> mcasp0_axr0.mcasp0_axr0 */ >>> 0x19c (PIN_INPUT_PULLDOWN | MUX_MODE2) /* >>> mcasp0_ahclkr.mcasp0_axr2 */ >>> 0x1ac (PIN_INPUT_PULLDOWN | MUX_MODE0) /* >>> MCASP0_AHCLKX -> MCASP0_AHCLKX (I2S_MCLK_OUT)- in */ >>> >; >>> }; >>> }; >>> }; >>> >>> Am i missing something here ? All pins should be outputs >>> except the >>> audio input on axr0.mcasp0 which should be an input. >>> >>> On the UARTS the signal directions are correct. >>> >>> Is there some black magic that i am missing ? >>> >>> >>> --- >>> This email has been checked for viruses by Avast antivirus >>> software. >>> https://www.avast.com/antivirus >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the >>> Google Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails >>> from it, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> >>> https://groups.google.com/d/msgid/beagleboard/89a7327f-23fc-3b59-958a-1d4b741575c9%40gmail.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> To unsubscribe from this group and stop receiving emails from it, >>> send an email to [email protected] >>> <mailto:[email protected]>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/CALHSORqcCXzPcuMnNTJN%2By0pV9v%3DRxqAiK-M%2B_k-%3DAeV_6U2KA%40mail.gmail.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon> >> Virus-free. www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link> >> >> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google >> Groups "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, >> send an email to [email protected] >> <mailto:[email protected]>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/cb866526-71c1-1990-bb56-206b1a67940a%40gmail.com >> <https://groups.google.com/d/msgid/beagleboard/cb866526-71c1-1990-bb56-206b1a67940a%40gmail.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google > Groups "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/520B6C22-7B34-4393-AF83-BA255E7B4700%40gmail.com > <https://groups.google.com/d/msgid/beagleboard/520B6C22-7B34-4393-AF83-BA255E7B4700%40gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ac1b9c37-2760-020f-de94-74179d2bc8f9%40gmail.com. For more options, visit https://groups.google.com/d/optout.
