I decided to separate this thread from thread (Redirecting to Google Groups) I had commented earlier on as I felt the different versions just confused the issue.
Prior to upgrading to 3.8.13bone70, I was running Debian 3.8.13bone50 on Beaglebone black (RevC) together with LCD4 (BB-BONE-LCD4-01) and CircuitCo’s Audio cape Rev B1. From the beginning, I had issues with the audio dts file in that it grabbed exclusive use of gpio1_18 and gpio1_19, commenting these pins out and recompiling solved the problem.
When moving to 3.8.13bone70, I also had to rename the BB-BONE-AUDI-02-00A0 file to BB-BONE-AUDI-03-00A0 file so as to not load the kernel supplied device overlay.
Now it appears there is a pretty serious “bust” between LCD and Audio cape that I don’t know how to resolve (I say bust in inverted commas as I may be doing something wrong).
To me it appears that there is a conflict and I assume that the kernel supplied LCD’s dts is different to what was previously used.
After renaming the audio device overlay and manually loading (etc BB-BONE-AUDI-03 > …) which seemed to work, running aplay -l shows audio device but when trying to play a wav file all I hear is a ‘click’ noise and no music.
Using 3.8.13bone70
After manually loading BB-BONE-AUDI-03 cape, dmesg shows following error(s) with configuration:
[ 323.427162] pinctrl-single 44e10800.pinmux: pin 44e10998 already requested by gpio_keys.13; cannot claim for 48038000.mcasp [ 323.439210] pinctrl-single 44e10800.pinmux: pin-102 (48038000.mcasp) status -22 [ 323.447022] pinctrl-single 44e10800.pinmux: could not request pin 102 on device pinctrl-single [ 323.492148] davinci-mcasp 48038000.mcasp: pins are not configured from the driver
Rebooting with LCD cape enabled and AUDIO cape disabled, pin mux shows use of pin 102.
`
pin 16 (44e10840): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins
pin 17 (44e10844): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins
pin 19 (44e1084c): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins
pin 30 (44e10878): gpio-leds-cape-lcd4.12 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_led_00A1_pins group pinmux_bone_lcd4_cape_led_00A1_pins
…
pin 97 (44e10984): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins
pin 102 (44e10998): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins
pin 105 (44e109a4): panel.14 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_lcd_pins group pinmux_bone_lcd4_cape_lcd_pins
`
With LCD4 disabled (in /boot/uEnv.txt) and AUDIO cape enabled, you can see use of pin 102 - a conflict?
`
pin 100 (44e10990): 48038000.mcasp (GPIO UNCLAIMED) function pinmux_bone_audio_cape_audio_pins group pinmux_bone_audio_cape_audio_pins
pin 101 (44e10994): 48038000.mcasp (GPIO UNCLAIMED) function pinmux_bone_audio_cape_audio_pins group pinmux_bone_audio_cape_audio_pins
pin 102 (44e10998): 48038000.mcasp (GPIO UNCLAIMED) function pinmux_bone_audio_cape_audio_pins group pinmux_bone_audio_cape_audio_pins
pin 103 (44e1099c): 48038000.mcasp (GPIO UNCLAIMED) function pinmux_bone_audio_cape_audio_pins group pinmux_bone_audio_cape_audio_pins
pin 104 (44e109a0): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 105 (44e109a4): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 106 (44e109a8): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 107 (44e109ac): 48038000.mcasp (GPIO UNCLAIMED) function pinmux_bone_audio_cape_audio_pins group pinmux_bone_audio_cape_audio_pins
`
Using 3.8.13bone50
Running pinmux on 3.8.13bone50 setup shows pinmux below, no mention of pin 102.
callin@BioChargerNG011:~$ sudo grep lcd $PINMUX pin 16 (44e10840): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins pin 17 (44e10844): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins pin 19 (44e1084c): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins pin 30 (44e10878): gpio-leds-cape-lcd4.12 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_led_00A1_pins group pinmux_bone_lcd4_cape_led_00A1_pins ... pin 59 (44e108ec): panel.14 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_lcd_pins group pinmux_bone_lcd4_cape_lcd_pins pin 85 (44e10954): gpio_keys.13 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_keys_00A2_pins group pinmux_bone_lcd4_cape_keys_00A2_pins pin 105 (44e109a4): panel.14 (GPIO UNCLAIMED) function pinmux_bone_lcd4_cape_lcd_pins group pinmux_bone_lcd4_cape_lcd_pins
It seems that there has been changes to LCD4-01 in that mention is made of adding pwm for backlight vs gpio. I am not sure when that change took place but there does seem to be a change with relation to pin 102 which appears to be conflicting pin and a pretty important pin for the audio cape and a non-essential pin for lcd functionality.
I am not sure how to proceed as I don’t think it’s possible to manually load my own BB-BONE-LCD4-01 cape - if there is I’d love to know how and see if this is the issue.
Help VERY much appreciated!