One heads up on a mistake I made that Zachary Thorson debugged for me, and 
explained:
https://groups.google.com/forum/#!searchin/beagleboard/Zacharary$20Thorson/beagleboard/ZLSuKKM9Im4/bKqP9-Eu0NEJ

You could possibly have conflict with Adafruits Python BBIO.ADC module with:

        target = <&ocp>;
        __overlay__ {
            test_helper: helper {

Thw ADC module which will put a file helper.* in /sys/devices/ocp.* For me, 
it is:

/sys/devices/ocp.3/helper.15

This could conflict with your driver interface file. You might consider 
renaming 
                        test_helper: helper {
to something like:
                        test_mycape:mycape {
-Bit Pusher


On Sunday, May 26, 2013 1:53:01 PM UTC-4, [email protected] wrote:
>
> I'd like to find a good and detailed source of information on how to 
> create a well-integrated BBB Cape design.  I have put together a bare-bones 
> cape which is just an EEPROM chip running off the BBB's 3.3v line.  The 
> EEPROM contains my correctly formatted data and does indeed appear to be 
> recognised in the output from *dmesg*.  However, I am now a bit stuck.
>
> Following a couple of articles on the web I managed to bodge together a 
> working ".dtbo" file and this appears to work.  My prototype board does 
> show up in `cat /sys/devices/bone_capemgr.9/slots` after a reboot, which is 
> great :).
>
> But I'm at a bit of a loss as to what I should do next.  I'd like to put 
> an ATMega microcontroller onto my shield (running from the BBB's 3.3v rail) 
> and have it talk to the BBB using two IO pins to form a simple TX/RX uart. 
>  The ATMega side of this is no problem, I've done this many times, but the 
> BBB side is unknown to me.
>
> Here's my wpbbb.dts file so far, although I don't really know how it works 
> to be honest (it's a lightly modified version of Jason Kridner's example). 
>  WPBBB is the name of my experimental cape...
>
> /dts-v1/;
> /plugin/;
>
> / {
>     compatible = "ti,beaglebone-black";
>
>     /* identification */
>     part-number = "WPBBB-Experiment";
>
>     fragment@0 {
>         target = <&am33xx_pinmux>;
>         __overlay__ {
>             wpbbb_test: wpbbb_test_pins {
>                 pinctrl-single,pins = <
>                     0x164 0x07              /* P9_42 muxRegOffset, OUTPUT 
> | MODE7 */
>                 >;
>             };
>         };
>     };
>
>     fragment@1 {
>         target = <&ocp>;
>         __overlay__ {
>             test_helper: helper {
>                 compatible = "bone-pinmux-helper";
>                 pinctrl-names = "default";
>                 pinctrl-0 = <&wpbbb_test>;
>                 status = "okay";
>             };
>         };
>     };
> };
>
>
> How would I adapt this to enable a pair of BBB pins to talk to the ATMega 
> chip on the cape?  How do I get the BBB to automatically load a custom 
> device driver for my cape?  I realise I'll have to write the custom driver 
> myself and also the microcontroller code to talk to the driver.
>
> I don't have any particular functionality goal in mind for this cape.  I 
> simply want to use it as a way to learn more about he BBB's architecture 
> and system structure.  I'd be grateful for any and all advice that would 
> let me get a bit further with this.
>
> Anyway, many thanks for reading.
>
> Cheers.
>
>

-- 
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].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to