Most people are still on the 3.8 kernel.
Gerald
On Fri, Feb 21, 2014 at 2:07 AM, <quikcj...@gmail.com> wrote:
> Is there really nobody interested in using the GPMC on the BeagleBone
> Black?
>
>
> Am Dienstag, 18. Februar 2014 11:35:06 UTC+1 schrieb quik...@gmail.com:
>
>> I seems that what you are trying to do is to setup GPMC access on the
>> BeagleBone Black using kernel 3.12.x. The steps to do this are as follows:
>>
>> (1) You must boot using an external micro SDHC card because the internal
>> eMMC must be disabled
>> (2) Disable eMMC and HDMI in uEnv.txt by adding optargs=capemgr.disable_
>> partno=BB-BONE-EMMC-2G,BB-BONELT-HDMI,BB-BONELT-HDMIN
>> (3) After booting cape manager will still load both capes. The must be
>> removed manually.
>> (4) In the sources of kernel 3.12.x we must modify
>> /arch/arm/boot/dts/am335x-boneblack.dts to free up the reset pin for the
>> eMMC device. This is done by changing status from "ok" to disabled in
>> section &mmc2
>> (5) It should now be possible to load your custom .dts file without any
>> warnings
>>
>> Unfortunately, the GPMC is still not working in kernel 3.12. I have
>> tested this using 3.12.8 and 3.12.10. I cannot see any activity on the GPMC
>> signals. The same procedure is working in kernel 3.8.13.
>>
>>
>>
>> Am Freitag, 17. Januar 2014 17:55:11 UTC+1 schrieb Drew Moore:
>>>
>>> Thanks for responding..
>>>
>>> I did
>>> grep clkout2 *.dts
>>> in both directories and found that clkout2 didn't show up in the 3.8 but
>>> did show up in 3.12
>>> in 3.12 it shows up in am335x-evm.dts and also am335x-evmsk.dts.. (and
>>> dove-cubox.dts but I don't think that is related)
>>>
>>> I also just noticed that it also shows up in am335x-bone-common.dtsi,
>>> (3.12) which now seems more likely to be the beaglebone related file.
>>>
>>> Here's that chunk from my device tree file..
>>>
>>> fragment@0 {
>>> target = <&am33xx_pinmux>;
>>> __overlay__ {
>>> gpmc_pins: pinmux_gpmc_pins {
>>> pinctrl-single,pins = <
>>> /* 0x20 = Fast, RX_enabled, pullup, pullup_enable,
>>> mode 0 */
>>> 0x000 0x20 /* gpmc_ad0.gpmc_ad0 MODE0 | INPUT |
>>> PULLUP */
>>> 0x004 0x20 /* gpmc_ad1.gpmc_ad1 MODE0 | INPUT |
>>> PULLUP */
>>> 0x008 0x20 /* gpmc_ad2.gpmc_ad2 MODE0 | INPUT |
>>> PULLUP */
>>> 0x00C 0x20 /* gpmc_ad3.gpmc_ad3 MODE0 | INPUT |
>>> PULLUP */
>>> 0x010 0x20 /* gpmc_ad4.gpmc_ad4 MODE0 | INPUT |
>>> PULLUP */
>>> 0x014 0x20 /* gpmc_ad5.gpmc_ad5 MODE0 | INPUT |
>>> PULLUP */
>>> 0x018 0x20 /* gpmc_ad6.gpmc_ad6 MODE0 | INPUT |
>>> PULLUP */
>>> 0x01C 0x20 /* gpmc_ad7.gpmc_ad7 MODE0 | INPUT |
>>> PULLUP */
>>> 0x020 0x20 /* gpmc_ad8.gpmc_ad8 MODE0 | INPUT |
>>> PULLUP */
>>> 0x024 0x20 /* gpmc_ad9.gpmc_ad9 MODE0 | INPUT |
>>> PULLUP */
>>> 0x028 0x20 /* gpmc_ad10.gpmc_ad10 MODE0 | INPUT |
>>> PULLUP */
>>> 0x02C 0x20 /* gpmc_ad11.gpmc_ad11 MODE0 | INPUT |
>>> PULLUP */
>>> 0x030 0x20 /* gpmc_ad12.gpmc_ad12 MODE0 | INPUT |
>>> PULLUP */
>>> 0x034 0x20 /* gpmc_ad13.gpmc_ad13 MODE0 | INPUT |
>>> PULLUP */
>>> 0x038 0x20 /* gpmc_ad14.gpmc_ad14 MODE0 | INPUT |
>>> PULLUP */
>>> 0x03C 0x20 /* gpmc_ad15.gpmc_ad15 MODE0 | INPUT |
>>> PULLUP */
>>>
>>> 0x078 0x04 /* gpmc_ben1.gpmc_dir MODE4 | OUTPUT */
>>> 0x080 0x00 /* gpmc_cscn1.gpmc_cscn1 MODE0 |
>>> OUTPUT */
>>> 0x08C 0x00 /* gpmc_clk.gpmc_clk MODE0 | OUTPUT */
>>> 0x090 0x00 /* gpmc_advn_ale.gpmc_advn_ale MODE0 |
>>> OUTPUT */
>>> 0x094 0x00 /* gpmc_oen_ren.gpmc_oen_ren MODE0 |
>>> OUTPUT */
>>> 0x098 0x00 /* gpmc_wen.gpmc_wen MODE0 | OUTPUT */
>>> 0x09C 0x00 /* gpmc_ben0_cle.gpmc_ben0_cle MODE0 |
>>> OUTPUT */
>>> 0x1b4 0x03 /* xdma_event_intr1.clkout2 MODE3 |
>>> OUTPUT */
>>> >;
>>> };
>>> };
>>> };
>>>
>>> I used BB-BONE-CAM3 as a starting point but yes, I'm mostly guessing at
>>> what this stuff means.
>>> My next guess is that the last line above is in the wrong section..
>>> clkout2 is not a gpmc pin.
>>>
>>> I don't have any /include/ lines in my file.. just
>>> compatible = "ti,beaglebone", "ti,beaglebone-black";
>>> from the CAM3 file I modified.
>>>
>>>
>>>
>>> --
> 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.
>
--
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.
