Re: [beagleboard] New DTO RSCM
I still want to be able to understand how to enable the ports and use one wire in the newer kernels. I can see the one wire driver being loaded on startup. But I cannot see /sys/devices/w1_devices -- 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/d/optout.
[beagleboard] New DTO RSCM
So, I'm finding the Really Simple Cape Manager anything but simple... I made a Java DTO library that would use a JSON file (https://github.com/DougEdey/SB_Elsinore_Server/blob/master/extras/beaglebone.json) to create Device Tree Overlays that could be applied easily. This created files that could do basic GPIO exports, but I'm confused/concerned about how to do this for the new RSCM. There's no lines in the boneblack.dts (https://github.com/RobertCNelson/rscm/blob/master/3.13-bone/am335x-boneblack.dts) that indicate which GPIO pins are which, and, much more concerningly to me, I have no idea how to enable OneWire like I used to, using this (https://github.com/DougEdey/SB_Elsinore_Server/blob/master/extras/w1.dts) source. Am I missing something very fundamental? Like some documentation or instructions for how to use RSCM? I have a lot of users who want to use the BBB and I want to support the latest kernel images. -- 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/d/optout.
Re: [beagleboard] New DTO RSCM
OK, I'm still unclear as to how my old dts for one wire: /* * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/ * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License version 2 as * published by the Free Software Foundation. * * Modified by Russell Senior from the weather cape's DTS file. * Minor formatting by C W Rose. */ /dts-v1/; /plugin/; / { compatible = ti,beaglebone, ti,beaglebone-black; part-number = BB-W1; version = 00A0; exclusive-use = P8.11; fragment@0 { target = am33xx_pinmux; __overlay__ { bb_w1_pins: pinmux_bb_w1_pins { pinctrl-single,pins = 0x34 0x37 /* gpmc_ad13.gpio1_13, OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */ ; }; }; }; fragment@1 { target = ocp; __overlay__ { onewire@0 { status = okay; compatible = w1-gpio; pinctrl-names = default; pinctrl-0 = bb_w1_pins; gpios = gpio2 13 0; }; }; }; }; Would convert to the new dtsi, is there any documentation on the dtsi? -- 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/d/optout.
Re: [beagleboard] New DTO RSCM
/3.14.22-ti-r31/am3517-evm.dtb' 'src/arm/am3517_mt_ventoux.dtb' - '/boot/dtbs/3.14.22-ti-r31/am3517_mt_ventoux.dtb' 'src/arm/am437x-gp-evm-hdmi.dtb' - '/boot/dtbs/3.14.22-ti-r31/am437x-gp-evm-hdmi.dtb' 'src/arm/am437x-gp-evm.dtb' - '/boot/dtbs/3.14.22-ti-r31/am437x-gp-evm.dtb' 'src/arm/am437x-sk-evm.dtb' - '/boot/dtbs/3.14.22-ti-r31/am437x-sk-evm.dtb' 'src/arm/am43x-epos-evm-hdmi.dtb' - '/boot/dtbs/3.14.22-ti-r31/am43x-epos-evm-hdmi.dtb' 'src/arm/am43x-epos-evm.dtb' - '/boot/dtbs/3.14.22-ti-r31/am43x-epos-evm.dtb' 'src/arm/am57xx-beagle-x15.dtb' - '/boot/dtbs/3.14.22-ti-r31/am57xx-beagle-x15.dtb' 'src/arm/dra7-evm-lcd10.dtb' - '/boot/dtbs/3.14.22-ti-r31/dra7-evm-lcd10.dtb' 'src/arm/dra7-evm-lcd7.dtb' - '/boot/dtbs/3.14.22-ti-r31/dra7-evm-lcd7.dtb' 'src/arm/dra7-evm.dtb' - '/boot/dtbs/3.14.22-ti-r31/dra7-evm.dtb' 'src/arm/dra72-evm-lcd10.dtb' - '/boot/dtbs/3.14.22-ti-r31/dra72-evm-lcd10.dtb' 'src/arm/dra72-evm-lcd7.dtb' - '/boot/dtbs/3.14.22-ti-r31/dra72-evm-lcd7.dtb' 'src/arm/dra72-evm.dtb' - '/boot/dtbs/3.14.22-ti-r31/dra72-evm.dtb' 'src/arm/k2hk-evm.dtb' - '/boot/dtbs/3.14.22-ti-r31/k2hk-evm.dtb' 'src/arm/omap3-beagle-xm.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-beagle-xm.dtb' 'src/arm/omap3-beagle.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-beagle.dtb' 'src/arm/omap3-cm-t3730.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-cm-t3730.dtb' 'src/arm/omap3-devkit8000.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-devkit8000.dtb' 'src/arm/omap3-evm-37xx.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-evm-37xx.dtb' 'src/arm/omap3-evm.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-evm.dtb' 'src/arm/omap3-gta04.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-gta04.dtb' 'src/arm/omap3-igep0020.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-igep0020.dtb' 'src/arm/omap3-igep0030.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-igep0030.dtb' 'src/arm/omap3-ldp.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-ldp.dtb' 'src/arm/omap3-n9.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-n9.dtb' 'src/arm/omap3-n900.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-n900.dtb' 'src/arm/omap3-n950.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-n950.dtb' 'src/arm/omap3-overo-storm-tobi.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-overo-storm-tobi.dtb' 'src/arm/omap3-overo-tobi.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-overo-tobi.dtb' 'src/arm/omap3-sbc-t3730.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-sbc-t3730.dtb' 'src/arm/omap3-zoom3.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3-zoom3.dtb' 'src/arm/omap3430-sdp.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap3430-sdp.dtb' 'src/arm/omap4-panda-a4.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap4-panda-a4.dtb' 'src/arm/omap4-panda-es.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap4-panda-es.dtb' 'src/arm/omap4-panda.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap4-panda.dtb' 'src/arm/omap4-sdp-es23plus.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap4-sdp-es23plus.dtb' 'src/arm/omap4-sdp.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap4-sdp.dtb' 'src/arm/omap4-var-som.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap4-var-som.dtb' 'src/arm/omap5-uevm.dtb' - '/boot/dtbs/3.14.22-ti-r31/omap5-uevm.dtb' Edited my uEnv.txt to: #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 uname_r=3.14.22-ti-r31 dtb=am335x-boneblack.dtb uuid=a9ecee33-898c-4ddb-a96c-461b113cc230 cmdline=quiet ##Example #cape_disable=capemgr.disable_partno= #cape_enable=capemgr.enable_partno= ##enable BBB: eMMC Flasher: ##make sure, these tools are installed: dosfstools rsync #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh On Thursday, November 20, 2014 10:27:32 PM UTC-5, RobertCNelson wrote: On Thu, Nov 20, 2014 at 9:16 PM, Doug Edey doug...@gmail.com javascript: wrote: OK, I'm still unclear as to how my old dts for one wire: /* * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/ * * This program is free software; you can redistribute it and/or modify * it under the terms of the GNU General Public License version 2 as * published by the Free Software Foundation. * * Modified by Russell Senior from the weather cape's DTS file. * Minor formatting by C W Rose. */ /dts-v1/; /plugin/; / { compatible = ti,beaglebone, ti,beaglebone-black; part-number = BB-W1; version = 00A0; exclusive-use = P8.11; fragment@0 { target = am33xx_pinmux; __overlay__ { bb_w1_pins: pinmux_bb_w1_pins { pinctrl-single,pins = 0x34 0x37 /* gpmc_ad13.gpio1_13, OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */ ; }; }; }; fragment@1 { target = ocp; __overlay__ { onewire@0 { status = okay; compatible = w1-gpio; pinctrl-names = default; pinctrl-0 = bb_w1_pins; gpios = gpio2 13 0; }; }; }; }; Would convert to the new dtsi, is there any documentation on the dtsi? First test this: http://pastebin.com/yDyaHKcS If it works, i'll factor it into the patchset.. make sudo make install Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org
Re: [beagleboard] New DTO RSCM
The DTB doesn't match the hardware, it matches the kernel? That seems odd... I ran those. commands, uEnv still points at am335-boneblack.dtb, but I don;t see any one wire devices, even though there is one connected in the same configuration as the old kernel 3.8 that used the previous DTB I pasted which was exported to the capemgr. What was the reason for the change away from capemgr? capemgr seemed to work -- 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/d/optout.
Re: [beagleboard] New DTO RSCM
Then just: sudo apt-get update sudo apt-get install linux-image-3.8.13-bone67 sudo reboot Running What was the reason for the change away from capemgr? capemgr seemed to work Search the list, it's been explained too often. Surely, as a fellow software dev, if you have to explain yourself a lot, there's an issue (I've worked on a lot of massive projects down to the low level, JVM - network management product for ISPs/larger) -- 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/d/optout.
Re: [beagleboard] New DTO RSCM
On Thursday, November 20, 2014 11:32:13 PM UTC-5, RobertCNelson wrote: On Thu, Nov 20, 2014 at 10:25 PM, Doug Edey doug...@gmail.com javascript: wrote: The DTB doesn't match the hardware, it matches the kernel? That seems odd... I ran those. commands, uEnv still points at am335-boneblack.dtb, but I don;t see any one wire devices, even though there is one connected in the same configuration as the old kernel 3.8 that used the previous DTB I pasted which was exported to the capemgr. Then just: sudo apt-get update sudo apt-get install linux-image-3.8.13-bone67 sudo reboot No, I want to support the changes you've made to kernel 3.13 running. -- 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/d/optout.
Re: [beagleboard] Boot failures with 2014-07-06 drops
Wait, the boot button has to be pressed every single time it powers off and on? This isn't good at all, I have a cape on my board. -- 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/d/optout.
[beagleboard] Re: (Resource temporarily unavailable)Error while reading ADC pins
Is there a reason why overreading causes the issue? I've noticed I can cause it by running a: find /sys/devices -iname ain* Which is really annoying! On Friday, December 6, 2013 1:27:13 AM UTC-5, nax...@gmail.com wrote: The problem seems to arise when I am trying to access ADC continuously without delay. When I tried to access ADC continuously, the Resource temporarily unavailable error remained constant and I was not able to read ADC unless I rebooted the system. If I give a delay after reading each ADC value, Occassionally I do get Resource temporarily unavailable error but it just remains for a few seconds and I am able to read ADC again normally. On Monday, December 2, 2013 6:26:11 PM UTC+5:30, nax...@gmail.com wrote: I am getting resource temporary unavailable when I tried to read ADC pins from BeagleBone Black root@beaglebone:~# cat /sys/devices/ocp.2/helper.11/AIN* cat: /sys/devices/ocp.2/helper.11/AIN0: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN1: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN2: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN3: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN4: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN5: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN6: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN7: Resource temporarily unavailable What might be the reason for the error ? The ADC pins AIN0 to AIN5 are connected to thermistors and the actual voltage at the ADC pins is around 0.77 volt -- 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.
[beagleboard] Re: Cape IIO Kernel NULL Pointer derefence
Ok, but how to I make the reading on the analogue inputs more reliable? On Wednesday, December 4, 2013 2:32:06 AM UTC-5, Giuseppe Iellamo wrote: As others have noted here https://groups.google.com/forum/#!category-topic/beagleboard/beaglebone-black/ZLSuKKM9Im4 Unloading cape is a bit problematic... shortly don't expect it to work reliably Il giorno mercoledì 4 dicembre 2013 01:41:47 UTC+1, Doug Edey ha scritto: Using Ubuntu 13.04 3.8.13-bone31 After approximately five minutes AIN* values go to Resource Temporarily Unavailable elsinore@brewery:~$ cat /sys/devices/ocp.2/helper.13/AIN* cat: /sys/devices/ocp.2/helper.13/AIN0: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN1: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN2: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN3: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN4: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN5: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN6: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN7: Resource temporarily unavailable When I unload the cape: Dec 3 19:38:04 brewery kernel: [ 873.063510] Unable to handle kernel NULL pointer dereference at virtual address 001b Dec 3 19:38:04 brewery kernel: [ 873.072312] pgd = df308000 Dec 3 19:38:04 brewery kernel: [ 873.075179] [001b] *pgd=9f475831, *pte=, *ppte= Dec 3 19:38:04 brewery kernel: [ 873.081805] Internal error: Oops: 17 [#1] SMP ARM Dec 3 19:38:04 brewery kernel: [ 873.086721] Modules linked in: g_multi libcomposite r8712u(C) hid_ntrig Dec 3 19:38:04 brewery kernel: [ 873.093665] CPU: 0Tainted: G C(3.8.13-bone31 #1) Dec 3 19:38:04 brewery kernel: [ 873.099955] PC is at omap_device_idle+0x10/0x54 Dec 3 19:38:04 brewery kernel: [ 873.104689] LR is at _od_runtime_suspend+0x1c/0x24 Dec 3 19:38:04 brewery kernel: [ 873.109697] pc : [c00284e0]lr : [c0028540]psr: a013 Dec 3 19:38:04 brewery kernel: [ 873.109697] sp : de5bbd68 ip : df0484cc fp : de155c18 Dec 3 19:38:04 brewery kernel: [ 873.121695] r10: de5bbda0 r9 : c0059db0 r8 : Dec 3 19:38:04 brewery kernel: [ 873.127155] r7 : 6013 r6 : r5 : df28f410 r4 : Dec 3 19:38:04 brewery kernel: [ 873.133976] r3 : r2 : 000c000b r1 : df28f480 r0 : df28f400 Dec 3 19:38:04 brewery kernel: [ 873.140800] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Dec 3 19:38:04 brewery kernel: [ 873.148256] Control: 10c5387d Table: 9f308019 DAC: 0015 Dec 3 19:38:04 brewery kernel: [ 873.154260] Process bash (pid: 1491, stack limit = 0xde5ba240) Dec 3 19:38:04 brewery kernel: [ 873.160356] Stack: (0xde5bbd68 to 0xde5bc000) Dec 3 19:38:04 brewery kernel: [ 873.182260] bd60: c0028540 df28f410 c0028524 c038e278 Dec 3 19:38:04 brewery kernel: [ 873.199820] bd80: c094f4d8 df28f410 c038e7d8 6013 0001 0003 Dec 3 19:38:04 brewery kernel: [ 873.215648] bda0: de664e00 fdf4 de5ba000 df28f410 df28f480 6013 00200200 Dec 3 19:38:04 brewery kernel: [ 873.227851] bdc0: c066a264 de623df8 de155c18 c038f684 df28f410 c0027984 0004 Dec 3 19:38:04 brewery kernel: [ 873.236519] bde0: 6013 c038ae38 df28f410 c038e278 c094f4d8 df28f410 c038ebb8 Dec 3 19:38:04 brewery kernel: [ 873.252565] be00: df28f51c df28f410 0004 df28f480 6013 c038ed10 c03943f4 df28f410 Dec 3 19:38:04 brewery kernel: [ 873.272087] be20: df7f9b10 c099be08 c039fbe8 c039fbbc df28f410 c099d194 c03878e0 Dec 3 19:38:04 brewery kernel: [ 873.287712] be40: c03878cc c03862d8 df578580 df28f444 df28f410 c038633c df28f410 Dec 3 19:38:04 brewery kernel: [ 873.304292] be60: df04843c c0385e70 df28f410 df0b7200 df0b7210 c03840e8 df28f400 df0b7200 Dec 3 19:38:04 brewery kernel: [ 873.312980] be80: c0387c58 df28f400 c0387e74 df47d680 c04d1bf8 002b df47d680 Dec 3 19:38:04 brewery kernel: [ 873.338590] bea0: de623dc0 de623df8 00100100 c04d1cc4 df578580 ffb0 de623dc8 Dec 3 19:38:04 brewery kernel: [ 873.361964] bec0: de623dc0 de623e10 db25f000 c04d2498 de39e410 df0d7c10 de00da58 Dec 3 19:38:04 brewery kernel: [ 873.381545] bee0: df0d7c10 c039c69c 0007 de155c20 0003 c039dca8 de00da58 Dec 3 19:38:04 brewery kernel: [ 873.394988] bf00: c09c05c0 c061992c de157f48 de00da40 0003 Dec 3 19:38:04 brewery kernel: [ 873.404766] bf20: de00da58 de5bbf80 c066a264 df0d7c18 c0382ed0 0003 c014e684 Dec 3 19:38:04 brewery kernel: [ 873.424443] bf40: de333bc0 000ac408 0003 de5bbf80 000ac408 de5ba000 0003 c00f5474 Dec 3 19:38:04 brewery kernel
[beagleboard] Re: Dallas 1-Wire BeagleBone Black
I've got 3 DS18B20 sensors on my bus at the moment, providing you've got the sensors running in non-parasitic mode, I think you'll be fine. On Tuesday, December 3, 2013 8:13:31 PM UTC-5, lorena...@gmail.com wrote: Thinking of replacing the dedicated microcontroller that runs my house with a BBB. Being able to read the existing 1-Wire network will be critical. Currently have 12 18B20 sensors on one bus, need more. Can the kernel module described here actually address and read multiple sensors on the same bus? Can it search and retrieve addresses from unknown sensors? I see people selling 8-port capes, as if maybe this is a simple one device per bus routine... Wouldn't help me! As for the considerations of long buses, yes there was a learning curve. I have both active pull-up and active pull-down, with careful source-end termination. All cable is CAT-5, and all sensors are within 1m of a single linear topology installation. In several cases the bus goes out one pair of the CAT-5 to a distant sensor and comes back on another pair of the same cable to continue to the next destination. Branching.in a star fashion is death to 1-Wire. My current system works, reliably controlling serious solar hot water and outdoor wood boiler operation that could blow off expensive antifreeze fluid (a huge hassle to recharge) if anything overheated. Great long-bus reference: http://www.1wire.org/Files/Articles/1-Wire-Design%20Guide%20v1.0.pdf -- 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.
[beagleboard] Re: Any nice solution ot power 10x BeagleBone Black boards?
You'd be better off using the DC Plugs to power the Beagleboards, get a nice big brick and split the power out. On Wednesday, December 4, 2013 6:32:11 AM UTC-5, ara...@gmail.com wrote: Hello, I have 10 beaglebone black boards and would like to put them nicely in stack... I am looking for a PSU or a solution to power these boards. I didn't found anything nice though. I'm looking for a solution/recommendation now... 1. Are there any kind of PowerPlug with adapter where I can put 10 wires and feed it to boards? 2. Or may be just to buy a USB Hub with 10 ports that has external power supply and use it just to power the boards? I hope you've got what I'm looking for... :-) Let me know if it's still unclear. thanks, Anton. -- 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.
[beagleboard] Re: (Resource temporarily unavailable)Error while reading ADC pins
Does anyone have any help on this? I'm getting this too, using Ubuntu on the Beaglebone Black. I've upgrade to 3.8.13-bone31 (the only higher version is 3.12 but I can't get the cape to load) I get some valid readings (for maybe a few minutes after I load the cape) then I get the resource temporarily unavailable, and there's nothing in the dmesg output to indicate an error :( On Monday, December 2, 2013 7:56:11 AM UTC-5, nax...@gmail.com wrote: I am getting resource temporary unavailable when I tried to read ADC pins from BeagleBone Black root@beaglebone:~# cat /sys/devices/ocp.2/helper.11/AIN* cat: /sys/devices/ocp.2/helper.11/AIN0: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN1: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN2: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN3: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN4: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN5: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN6: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN7: Resource temporarily unavailable What might be the reason for the error ? The ADC pins AIN0 to AIN5 are connected to thermistors and the actual voltage at the ADC pins is around 0.77 volt -- 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.
[beagleboard] Cape IIO Kernel NULL Pointer derefence
Using Ubuntu 13.04 3.8.13-bone31 After approximately five minutes AIN* values go to Resource Temporarily Unavailable elsinore@brewery:~$ cat /sys/devices/ocp.2/helper.13/AIN* cat: /sys/devices/ocp.2/helper.13/AIN0: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN1: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN2: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN3: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN4: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN5: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN6: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.13/AIN7: Resource temporarily unavailable When I unload the cape: Dec 3 19:38:04 brewery kernel: [ 873.063510] Unable to handle kernel NULL pointer dereference at virtual address 001b Dec 3 19:38:04 brewery kernel: [ 873.072312] pgd = df308000 Dec 3 19:38:04 brewery kernel: [ 873.075179] [001b] *pgd=9f475831, *pte=, *ppte= Dec 3 19:38:04 brewery kernel: [ 873.081805] Internal error: Oops: 17 [#1] SMP ARM Dec 3 19:38:04 brewery kernel: [ 873.086721] Modules linked in: g_multi libcomposite r8712u(C) hid_ntrig Dec 3 19:38:04 brewery kernel: [ 873.093665] CPU: 0Tainted: G C(3.8.13-bone31 #1) Dec 3 19:38:04 brewery kernel: [ 873.099955] PC is at omap_device_idle+0x10/0x54 Dec 3 19:38:04 brewery kernel: [ 873.104689] LR is at _od_runtime_suspend+0x1c/0x24 Dec 3 19:38:04 brewery kernel: [ 873.109697] pc : [c00284e0]lr : [c0028540]psr: a013 Dec 3 19:38:04 brewery kernel: [ 873.109697] sp : de5bbd68 ip : df0484cc fp : de155c18 Dec 3 19:38:04 brewery kernel: [ 873.121695] r10: de5bbda0 r9 : c0059db0 r8 : Dec 3 19:38:04 brewery kernel: [ 873.127155] r7 : 6013 r6 : r5 : df28f410 r4 : Dec 3 19:38:04 brewery kernel: [ 873.133976] r3 : r2 : 000c000b r1 : df28f480 r0 : df28f400 Dec 3 19:38:04 brewery kernel: [ 873.140800] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Dec 3 19:38:04 brewery kernel: [ 873.148256] Control: 10c5387d Table: 9f308019 DAC: 0015 Dec 3 19:38:04 brewery kernel: [ 873.154260] Process bash (pid: 1491, stack limit = 0xde5ba240) Dec 3 19:38:04 brewery kernel: [ 873.160356] Stack: (0xde5bbd68 to 0xde5bc000) Dec 3 19:38:04 brewery kernel: [ 873.182260] bd60: c0028540 df28f410 c0028524 c038e278 Dec 3 19:38:04 brewery kernel: [ 873.199820] bd80: c094f4d8 df28f410 c038e7d8 6013 0001 0003 Dec 3 19:38:04 brewery kernel: [ 873.215648] bda0: de664e00 fdf4 de5ba000 df28f410 df28f480 6013 00200200 Dec 3 19:38:04 brewery kernel: [ 873.227851] bdc0: c066a264 de623df8 de155c18 c038f684 df28f410 c0027984 0004 Dec 3 19:38:04 brewery kernel: [ 873.236519] bde0: 6013 c038ae38 df28f410 c038e278 c094f4d8 df28f410 c038ebb8 Dec 3 19:38:04 brewery kernel: [ 873.252565] be00: df28f51c df28f410 0004 df28f480 6013 c038ed10 c03943f4 df28f410 Dec 3 19:38:04 brewery kernel: [ 873.272087] be20: df7f9b10 c099be08 c039fbe8 c039fbbc df28f410 c099d194 c03878e0 Dec 3 19:38:04 brewery kernel: [ 873.287712] be40: c03878cc c03862d8 df578580 df28f444 df28f410 c038633c df28f410 Dec 3 19:38:04 brewery kernel: [ 873.304292] be60: df04843c c0385e70 df28f410 df0b7200 df0b7210 c03840e8 df28f400 df0b7200 Dec 3 19:38:04 brewery kernel: [ 873.312980] be80: c0387c58 df28f400 c0387e74 df47d680 c04d1bf8 002b df47d680 Dec 3 19:38:04 brewery kernel: [ 873.338590] bea0: de623dc0 de623df8 00100100 c04d1cc4 df578580 ffb0 de623dc8 Dec 3 19:38:04 brewery kernel: [ 873.361964] bec0: de623dc0 de623e10 db25f000 c04d2498 de39e410 df0d7c10 de00da58 Dec 3 19:38:04 brewery kernel: [ 873.381545] bee0: df0d7c10 c039c69c 0007 de155c20 0003 c039dca8 de00da58 Dec 3 19:38:04 brewery kernel: [ 873.394988] bf00: c09c05c0 c061992c de157f48 de00da40 0003 Dec 3 19:38:04 brewery kernel: [ 873.404766] bf20: de00da58 de5bbf80 c066a264 df0d7c18 c0382ed0 0003 c014e684 Dec 3 19:38:04 brewery kernel: [ 873.424443] bf40: de333bc0 000ac408 0003 de5bbf80 000ac408 de5ba000 0003 c00f5474 Dec 3 19:38:04 brewery kernel: [ 873.440066] bf60: de333bc0 000ac408 de333bc0 000ac408 c00f5754 Dec 3 19:38:04 brewery kernel: [ 873.461551] bf80: 0003 0003 000ac408 b6f55a78 0004 c000da04 Dec 3 19:38:04 brewery kernel: [ 873.477265] bfa0: c000d880 0003 000ac408 0001 000ac408 0003 Dec 3 19:38:04 brewery kernel: [ 873.487589] bfc0: 0003 000ac408 b6f55a78 0004 0003 000a6094 Dec 3 19:38:05 brewery kernel: [
[beagleboard] Re: (Resource temporarily unavailable)Error while reading ADC pins
] (pm_generic_runtime_idle+0x20/0x50) Dec 3 19:38:05 brewery kernel: [ 873.555037] [c038ae38] (pm_generic_runtime_idle+0x20/0x50) from [c038e278] (__rpm_callback+0x30/0x58) Dec 3 19:38:05 brewery kernel: [ 873.565084] [c038e278] (__rpm_callback+0x30/0x58) from [c038ebb8] (rpm_idle+0x180/0x228) Dec 3 19:38:05 brewery kernel: [ 873.573948] [c038ebb8] (rpm_idle+0x180/0x228) from [c038ed10] (__pm_runtime_idle+0x48/0x90) Dec 3 19:38:05 brewery kernel: [ 873.583100] [c038ed10] (__pm_runtime_idle+0x48/0x90) from [c039fbe8] (ti_tscadc_remove+0x2c/0x48) Dec 3 19:38:05 brewery kernel: [ 873.592795] [c039fbe8] (ti_tscadc_remove+0x2c/0x48) from [c03878e0] (platform_drv_remove+0x14/0x18) Dec 3 19:38:05 brewery kernel: [ 873.602663] [c03878e0] (platform_drv_remove+0x14/0x18) from [c03862d8] (__device_release_driver+0x7c/0xc4) Dec 3 19:38:05 brewery kernel: [ 873.613168] [c03862d8] (__device_release_driver+0x7c/0xc4) from [c038633c] (device_release_driver+0x1c/0x28) Dec 3 19:38:05 brewery kernel: [ 873.623852] [c038633c] (device_release_driver+0x1c/0x28) from [c0385e70] (bus_remove_device+0xc8/0xd8) Dec 3 19:38:05 brewery kernel: [ 873.633988] [c0385e70] (bus_remove_device+0xc8/0xd8) from [c03840e8] (device_del+0x108/0x16c) Dec 3 19:38:05 brewery kernel: [ 873.643308] [c03840e8] (device_del+0x108/0x16c) from [c0387c58] (platform_device_del+0x14/0x44) Dec 3 19:38:05 brewery kernel: [ 873.652810] [c0387c58] (platform_device_del+0x14/0x44) from [c0387e74] (platform_device_unregister+0xc/0x18) Dec 3 19:38:05 brewery kernel: [ 873.663510] [c0387e74] (platform_device_unregister+0xc/0x18) from [c04d1bf8] (of_overlay_device_entry_change.isra.0+0xe8/0x16c) Dec 3 19:38:05 brewery kernel: [ 873.675928] [c04d1bf8] (of_overlay_device_entry_change.isra.0+0xe8/0x16c) from [c04d1cc4] (of_overlay_revert_one+0x48/0x1e8) Dec 3 19:38:05 brewery kernel: [ 873.688069] [c04d1cc4] (of_overlay_revert_one+0x48/0x1e8) from [c04d2498] (of_overlay_revert+0x3c/0x60) Dec 3 19:38:05 brewery kernel: [ 873.698298] [c04d2498] (of_overlay_revert+0x3c/0x60) from [c039c69c] (bone_capemgr_remove_slot_no_lock+0x40/0xc8) Dec 3 19:38:05 brewery kernel: [ 873.709436] [c039c69c] (bone_capemgr_remove_slot_no_lock+0x40/0xc8) from [c039dca8] (slots_store+0x78/0x3b0) Dec 3 19:38:05 brewery kernel: [ 873.720118] [c039dca8] (slots_store+0x78/0x3b0) from [c0382ed0] (dev_attr_store+0x18/0x24) Dec 3 19:38:05 brewery kernel: [ 873.729170] [c0382ed0] (dev_attr_store+0x18/0x24) from [c014e684] (sysfs_write_file+0x100/0x148) Dec 3 19:38:05 brewery kernel: [ 873.738751] [c014e684] (sysfs_write_file+0x100/0x148) from [c00f5474] (vfs_write+0xa8/0x178) Dec 3 19:38:05 brewery kernel: [ 873.747963] [c00f5474] (vfs_write+0xa8/0x178) from [c00f5754] (sys_write+0x38/0x64) Dec 3 19:38:05 brewery kernel: [ 873.756362] [c00f5754] (sys_write+0x38/0x64) from [c000d880] (ret_fast_syscall+0x0/0x30) Dec 3 19:38:05 brewery kernel: [ 873.770224] Code: e350 e92d4010 01a04000 159041c8 (e5d4301b) Dec 3 19:38:05 brewery kernel: [ 873.776680] ---[ end trace 11c5dfaa4d81386f ]--- On Tuesday, December 3, 2013 7:24:54 PM UTC-5, Doug Edey wrote: Does anyone have any help on this? I'm getting this too, using Ubuntu on the Beaglebone Black. I've upgrade to 3.8.13-bone31 (the only higher version is 3.12 but I can't get the cape to load) I get some valid readings (for maybe a few minutes after I load the cape) then I get the resource temporarily unavailable, and there's nothing in the dmesg output to indicate an error :( On Monday, December 2, 2013 7:56:11 AM UTC-5, nax...@gmail.com wrote: I am getting resource temporary unavailable when I tried to read ADC pins from BeagleBone Black root@beaglebone:~# cat /sys/devices/ocp.2/helper.11/AIN* cat: /sys/devices/ocp.2/helper.11/AIN0: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN1: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN2: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN3: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN4: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN5: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN6: Resource temporarily unavailable cat: /sys/devices/ocp.2/helper.11/AIN7: Resource temporarily unavailable What might be the reason for the error ? The ADC pins AIN0 to AIN5 are connected to thermistors and the actual voltage at the ADC pins is around 0.77 volt -- 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.