I am the hardware team. I don't do SW. Especially for other
peoples products. I suggest you contact the developer and maker of
this product. It is not beagleboard.org.
Gerald
On Wed, Oct 23, 2013 at 7:56 AM, Micka <mickamus...@gmail.com> wrote:
> Is it your Gerald, that is responsible of this code ?
>
>
> Micka,
>
>
> On Wed, Oct 23, 2013 at 2:30 PM, Micka <mickamus...@gmail.com> wrote:
>
>> Seriously ? No one care ? who is in charge of this change ? Who should I
>> contact ?
>>
>> Micka,
>>
>>
>> On Tue, Oct 22, 2013 at 5:18 PM, Micka <mickamus...@gmail.com> wrote:
>>
>>> A correction to my mail, normally it should be 0x154, which was the case
>>> before :
>>>
>>> bone_lcd7_cape_keys_00A3_pins: pinmux_bone_lcd7_cape_keys_00A3_pins {
>>> pinctrl-single,pins = <
>>> 0x040 0x2f /* KEY_LEFT gpmc_a0.gpio1_16, INPUT | PULLDIS | MODE7 */
>>> 0x044 0x2f /* KEY_RIGHT gpmc_a1.gpio1_17, INPUT | PULLDIS | MODE7 */
>>> 0x04c 0x2f /* KEY_UP gpmc_a3.gpio1_19, INPUT | PULLDIS | MODE7 */
>>> 0x198 0x2f /* KEY_DOWN mcasp0_axr0.gpio3_16, INPUT | PULLDIS | MODE7 */
>>> *0x154 0x2f /* KEY_ENTER spi0_d0.gpio0_3, INPUT | PULLDIS | MODE7 */*
>>> >;
>>> };
>>>
>>>
>>>
>>>
>>> On Tue, Oct 22, 2013 at 4:45 PM, Micka <mickamus...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I wanted to signal an error ( or not, but I double checked ) :
>>>>
>>>>
>>>> The Key ENTER of the LCD7 cap Rev A3 is connected to the GPIO0_3
>>>> =>
>>>> https://github.com/CircuitCo/BeagleBone-LCD7-RevA3/blob/master/BeagleBone-LCD7-RevA3-schematic.pdf?raw=true
>>>>
>>>> But In the last updated version of the file BB-BONE-LCD7-01-00A3.dts ,
>>>> I got :
>>>>
>>>>
>>>>
>>>> 0x040 0x2f /* KEY_LEFT gpmc_a0.gpio1_16, INPUT | PULLDIS | MODE7 */
>>>> 0x044 0x2f /* KEY_RIGHT gpmc_a1.gpio1_17, INPUT | PULLDIS | MODE7 */
>>>> 0x04c 0x2f /* KEY_UP gpmc_a3.gpio1_19, INPUT | PULLDIS | MODE7 */
>>>> 0x198 0x2f /* KEY_DOWN mcasp0_axr0.gpio3_16, INPUT | PULLDIS | MODE7 */
>>>> *0x070 0x2f /* KEY_ENTER gpmc_wait0.gpio0_3, INPUT | PULLDIS | MODE7 */
>>>> *
>>>>
>>>>
>>>>
>>>> Which is normally 0x954 and not 0x070 ( 0x070 is for GPIO0_30 )
>>>>
>>>>
>>>> So, am I right or wrong ? If I'm wrong, why in june, july, ... the
>>>> address of uart4_rx was 0x070, which is GPIO0_30 ?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Micka,
>>>>
>>>
>>>
>>
>
--
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
