Devicetree with IoT Images 4.4.36

[Fohnbit]

Hello,

I setup a new BBB with the image IoT 4.4.36.

But there I miss the /sys/devices/bone_capemgr.9/slots folder.

I need some Uarts and some inputs/outputs at the GPIO

Is in this firmware different?

Thank you!

[William Hermans]

With the 4.x kernels the path has changed to: /sys/devices/platform/bone_capemgr/slots

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c2685330-b9cb-4715-941e-d46efa50adfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[jmelson]

On Sunday, January 22, 2017 at 7:29:18 AM UTC-6, William Hermans wrote:

With the 4.x kernels the path has changed to: /sys/devices/platform/bone_capemgr/slots

Yes, I found this.  But, when I do the command :
 
echo BB-BONE-SWI:00A0 > /sys/bus/platform/devices/bone_capemgr/slots

I get this error :
sh: echo: I/O error

Any suggestions what I'm doing wrong?  All the online info seems to have the old syntax.

Thanks,

Jon

[jmelson]

On Saturday, May 27, 2017 at 2:12:05 PM UTC-5, jmelson wrote:

 
echo BB-BONE-SWI:00A0 > /sys/bus/platform/devices/bone_capemgr/slots

 /sys/bus/platform/devices/bone_capemgr/slots or

 /sys/devices/platform/bone_capemgr/slots seem to be the same dir via a ln, and give the same error.

Jon

[William Hermans]

Yes,

echo BB-BONE-SWI:00A0

needs to change to:

echo BB-BONE-SWI

--

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+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c9a27a9f-da38-4755-9776-d57ddae3a9e7%40googlegroups.com.

[jmelson]

On Saturday, May 27, 2017 at 2:20:53 PM UTC-5, William Hermans wrote:

Yes,

echo BB-BONE-SWI:00A0

needs to change to:

echo BB-BONE-SWI

Well, I still get the
 sh: echo: I/O error
message.


Here's the dts file :
______________________________
/dts-v1/;
/plugin/;

/ {
  compatible = "ti,beaglebone", "ti,beaglebone-black";

  part-number = "BB-BONE-SWI";
  version = "00A0";

  exclusive-use =
    "P8.25",
    "P8.24",
    "P8.5",
    "P8.6",
    "P8.23",
    "P8.22",
    "P8.3",
    "P8.4",
    "P8.12",
    "P8.11",
    "P8.16",
    "P8.15";

  fragment@0 {
    target = <&am33xx_pinmux>;
    __overlay__ {
      mygpio: pinmux_mygpio{
        pinctrl-single,pins = <
          0x000 0xf // P8.25  GPIO 1.0
          0x004 0xf // P8.24  GPIO 1.1
          0x008 0xf // P8.5   GPIO 1.2
          0x00c 0xf // P8.6   GPIO 1.3
          0x010 0xf // P8.23  GPIO 1.4
          0x014 0xf // P8.22  GPIO 1.5
          0x018 0xf // P8.3   GPIO 1.6
          0x01c 0xf // P8.4   GPIO 1.7
          0x030 0xf // P8.12  GPIO 1.12
          0x034 0xf // P8.11  GPIO 1.13
          0x038 0xf // P8.16  GPIO 1.14
          0x03c 0xf // P8.15  GPIO 1.15
          >;
      };
    };
  };

  fragment@1 {
    target = <&ocp>;
    __overlay__ {
      test_helper: helper {
        compatible = "bone-pinmux-helper";
        pinctrl-names = "default";
        pinctrl-0 = <&mygpio>;
        status = "okay";
      };
    };
  };

  fragment@2{
  target = <&pruss>;
    __overlay__ {
      status = "okay";
    };
  };
};
_____________________________________________

and here's my compile and load overlay file :
_____________________________________________

 dtc -O dtb -o BB-BONE-SWI.dtbo -b o -@ BB-BONE-SWI.dts
cp BB-BONE-SWI.dtbo /lib/firmware/

echo BB-BONE-SWI.dtbo > /sys/devices/platform/bone_capemgr/slots

more /sys/devices/platform/bone_capemgr/slots
__________________________________

This is derived from working dts and compile/load files from another project based on an earlier kernel.

Thanks much for any help with this!

Jon