[beagleboard] beaglebone black pwm pin can't find duty, period, ...
I am trying to use the pin P8_13 for pwm. When I load the overlay I the
power file is created but no duty, period, ... files are created. I am
clearly doing something wrong. I can't use the universal overlay because I
can't figure out how to load a one wire device in the universal overlay.
With the universal overlay the pwm works perfectly.
I am using kernel 3.8.13-bone70
My overlay is as follows:
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
/* identification */
part-number = "BREW_PWM_P8_13";
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P8.13",
/* the hardware IP uses */
"ehrpwm2B";
fragment@0 {
target = <_pinmux>;
__overlay__ {
brew_pwm_P8_13: pinmux_brew_pwm_P8_13 {
pinctrl-single,pins = <0x024 0x24>;
};
};
};
fragment@1 {
target = <>;
__overlay__ {
brewery_pwm_P8_13 {
compatible = "pwm_brew";
pwms= < 1 50 0>;
pwm-names = "PWM_P8_13";
pinctrl-names = "pwm";
pinctrl-0 = <_pwm_P8_13>;
enabled = <1>;
duty= <0>;
status = "okay";
};
};
};
};
when I load the overlay dmesg shows the overlay was accepted
the directory for the pwm pin is created and it has
modalias: a file
power: a directory
subsystem: a link
uevent: a file
I can't find the duty, period, ... files that are needed to control the pwm.
Any guidance would be appreciated.
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/436ed8be-8a43-4c05-8362-db54d0ecd28f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: 1 Wire device with universal overlay
/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "BB-W1";
version = "00A0";
exclusive-use =
"P9.22",
"gpio0_2";
fragment@0 {
target = <_pinmux>;
__overlay__ {
dallas_w1_pins: pinmux_dallas_w1_pins {
pinctrl-single,pins = < 0x150 0x37 >; };
};
};
fragment@1 {
target = <>;
__overlay__ {
onewire@0 {
compatible = "w1-gpio";
pinctrl-names = "default";
pinctrl-0= <_w1_pins>;
status = "okay";
gpios = < 2 0>;
};
};
};
};
On Thu, May 12, 2016 at 11:07 AM, William Hermans <yyrk...@gmail.com> wrote:
> *That's correct, every pin is configured. And the load the driver for
>> PWM, or SPI, or ... but it is not configured to load the OneWire driver for
>> the pin. All of the config-pin options are for standard drivers. The
>> point is, if you want to use the pin to another device that is not a built
>> in device then one needs to do something different.*
>>
>
> How was the pin configured before ? There is no one wire peripheral
> module, so it must have been configured as GPIO. As far as one-wire goes I
> have never used it before, but have read it is basically a modified I2C
> protocol(somehow ).
>
> If I was able to look at the device tree file you use before. Perhaps I
> could offer assistance.
>
> On Thu, May 12, 2016 at 10:38 AM, Ray Madigan <raymond.madi...@gmail.com>
> wrote:
>
>> That's correct, every pin is configured. And the load the driver for
>> PWM, or SPI, or ... but it is not configured to load the OneWire driver for
>> the pin. All of the config-pin options are for standard drivers. The
>> point is, if you want to use the pin to another device that is not a built
>> in device then one needs to do something different.
>>
>> On Thursday, May 12, 2016 at 10:20:37 AM UTC-7, William Hermans wrote:
>>>
>>> *Because the universal overlay causes my one wire overlay to be
>>>> rejected. The error is File Exists and dmesg points to the conflict with
>>>> the slots entry that has the conflict. I am probably doing something
>>>> wrons, even when I delete the P9_22 from the universal overlay and reapply
>>>> it, it rejects my overlay.*
>>>
>>>
>>> Because the pin is already configured. *Every* pin is configured when
>>> you use universal io. Plus the point of using universal io is so you do not
>>> have to configure the pin through an overlay. So learn how to use universal
>>> io + config-pin to configure the pin.
>>>
>>>
>>> On Thu, May 12, 2016 at 9:05 AM, Ray Madigan <raymond...@gmail.com>
>>> wrote:
>>>
>>>> Because the universal overlay causes my one wire overlay to be
>>>> rejected. The error is File Exists and dmesg points to the conflict with
>>>> the slots entry that has the conflict. I am probably doing something
>>>> wrons, even when I delete the P9_22 from the universal overlay and reapply
>>>> it, it rejects my overlay.
>>>>
>>>> I am working on this from two perspectives, i need to be able to get
>>>> back to work :). I am building a non universal overlay that will include
>>>> my one wire pin, the pwm pins I need, and others as I work out my
>>>> application. I will use this until I figure out the universal overlay
>>>> issue.
>>>>
>>>> I have never written an overlay that uses two pins on the same device,
>>>> I am working that out now.
>>>>
>>>> On Thursday, May 12, 2016 at 8:41:41 AM UTC-7, TJF wrote:
>>>>>
>>>>> Why don't you adapt the 1-wire overlay? It should be easy to use a pin
>>>>> not connected to any PWMSS. Ie. use P9_11 or P8_07.
>>>>>
>>>> --
>>>> 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...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/beagleboard/5dc3979a-1d78-45d1-82d0-
Re: [beagleboard] Re: 1 Wire device with universal overlay
That's correct, every pin is configured. And the load the driver for PWM, or SPI, or ... but it is not configured to load the OneWire driver for the pin. All of the config-pin options are for standard drivers. The point is, if you want to use the pin to another device that is not a built in device then one needs to do something different. On Thursday, May 12, 2016 at 10:20:37 AM UTC-7, William Hermans wrote: > > *Because the universal overlay causes my one wire overlay to be rejected. >> The error is File Exists and dmesg points to the conflict with the slots >> entry that has the conflict. I am probably doing something wrons, even >> when I delete the P9_22 from the universal overlay and reapply it, it >> rejects my overlay.* > > > Because the pin is already configured. *Every* pin is configured when you > use universal io. Plus the point of using universal io is so you do not > have to configure the pin through an overlay. So learn how to use universal > io + config-pin to configure the pin. > > > On Thu, May 12, 2016 at 9:05 AM, Ray Madigan <raymond...@gmail.com > > wrote: > >> Because the universal overlay causes my one wire overlay to be rejected. >> The error is File Exists and dmesg points to the conflict with the slots >> entry that has the conflict. I am probably doing something wrons, even >> when I delete the P9_22 from the universal overlay and reapply it, it >> rejects my overlay. >> >> I am working on this from two perspectives, i need to be able to get back >> to work :). I am building a non universal overlay that will include my one >> wire pin, the pwm pins I need, and others as I work out my application. I >> will use this until I figure out the universal overlay issue. >> >> I have never written an overlay that uses two pins on the same device, I >> am working that out now. >> >> On Thursday, May 12, 2016 at 8:41:41 AM UTC-7, TJF wrote: >>> >>> Why don't you adapt the 1-wire overlay? It should be easy to use a pin >>> not connected to any PWMSS. Ie. use P9_11 or P8_07. >>> >> -- >> 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...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/5dc3979a-1d78-45d1-82d0-dea8b8004a14%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/5dc3979a-1d78-45d1-82d0-dea8b8004a14%40googlegroups.com?utm_medium=email_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/b53b6116-848f-4e97-8f68-34164f115300%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: 1 Wire device with universal overlay
Because the universal overlay causes my one wire overlay to be rejected. The error is File Exists and dmesg points to the conflict with the slots entry that has the conflict. I am probably doing something wrons, even when I delete the P9_22 from the universal overlay and reapply it, it rejects my overlay. I am working on this from two perspectives, i need to be able to get back to work :). I am building a non universal overlay that will include my one wire pin, the pwm pins I need, and others as I work out my application. I will use this until I figure out the universal overlay issue. I have never written an overlay that uses two pins on the same device, I am working that out now. On Thursday, May 12, 2016 at 8:41:41 AM UTC-7, TJF wrote: > > Why don't you adapt the 1-wire overlay? It should be easy to use a pin not > connected to any PWMSS. Ie. use P9_11 or P8_07. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5dc3979a-1d78-45d1-82d0-dea8b8004a14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] 1 Wire device with universal overlay
I have been using a 1 wire overlay for pin P9.22 for a while and I just expanded my toy to use a couple of pwm pins. Instead of creating the overlay myself, I figured I would try the universal overlay. I am using universaln and have an init.d script to load it and all is well. The problem is, I haven't solved the problem of getting P9.22 back to 1 Wire that I need. I tried looking at my overlay and modifying the universal overlay to implement it, I guess I don't understand enough to make that work. Then I commented out all of the P9_22 and P9.22 stuff in the overlay, make worked successfully, but when I try to load my old P9_22 overlay I get the File Exists error so there seems to still be a conflict. What is the preferred way to solve this problem? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c516dce7-0d8e-484a-abfd-ce1e183aa495%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Beaglebone Database Suggestions
I have an app I want to write for home use that I need database access for. The dataset isn't extremely large but will eventually overflow the file system on beaglebone. I can't think of a way to add additional storage that will work with a database like postgresql. I have read many online posts that suggest that most databases will not install on a fat file system. At this point I am blocked. I have thought of using a cloud database, for the size of the database it is an expensive option. Any suggestions would be appreciated. -- 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] sd card format
Is it possible to mount the microsd card in a format other then vfat? I'm not really sure if that is the issue, maybe what I want to do isn't even possible on a microsd card. The card is formated as a Linux partition but /etc/mtab mounts it as a vfat partition. When i try to link files on the card I get the error operation not permitted. I have a very slow application that I want to build for the beaglebone and I want to use the sdcard for logging and application data storage/retrieval. meanwhile I will look for another way to get extra storage for my application. -- 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] One Wire Device Tree
Thank to both of you, I do appreciate the information. I have read and implemented several of the instructions that have the cape manager in /sys/devices/cape_mgr.9/slots to read the temperature and they work sure enough. The problem is, I have an older Rev B device that is running the image debian-8.3-ixqt and the device tree is slightly different. I followed a couple of examples and I couldn't get it to work so I figured I needed to understand how the mechanism works because eventually I need to turn on and off some devices via a transistor and just copying something from the web doesn't tell me what each section of the device tree does. and how the two versions, different capemgr locations, are different. The last example i tried suggested i put the dtbo in /boot/uEnv.txt and now the bone won't boot, all four led's stay lit so I feel it is time to stop counting on guess work and hope that what someone writes in a blog somewhere actually has worked on a recent image and figure out what I am doing. Thanks for all of your help. On Saturday, March 5, 2016 at 6:46:27 PM UTC-8, William Hermans wrote: > > In addition to what Robert has shown you there . . . the internet is > literally littered with guides, blogs, and random ramblings on getting the > ds18x20 devices working on both the Beaglebone's, and the rPI . . . Heres > one. > > > http://mkaczanowski.com/one-wire-ds1820-thermometer-with-beaglebone-black-libmicrohttpd/ > > > On Sat, Mar 5, 2016 at 7:39 PM, Robert Nelson <robert...@gmail.com > > wrote: > >> >> On Mar 5, 2016 8:00 PM, "Ray Madigan" <raymond...@gmail.com > >> wrote: >> > >> > I have been looking for way too long so maybe I don't know what to >> search for. >> > >> > I am attempting to get the ds18B20 temperature sensor working on a rev >> b beaglebone black that is running jessie 4.5 that I downloaded from the >> official place. I have a beaglebone rev c that uses the capemgr device >> tree mechanism and I know how to make that work. I can't seem to find any >> reference that will get me started with the no capemgr device tree >> implementation. >> > >> > Can someone point me to a place that will help me figure this out? Or >> should I go back to the original angstrom distribution? >> >> >> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-W1-P9.12-00A0.dts >> >> >> https://github.com/beagleboard/bb.org-overlays/blob/master/examples/BB-W1-P9.12/example.sh >> >> Regards, >> >> -- >> 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...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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: Cross Development using the linaro 5.2 toolchain
On Wednesday, January 20, 2016 at 10:41:38 AM UTC-8, Ray Madigan wrote: > > I have been struggling with this issue for longer then I care to admit. I > followed the directions to install the toolchain from the page: > > > > https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-ARMCrossCompiler:GCC > > > with the toolchain: > > > gcc-linaro-5.2-2015.11-x86_64_arm-linux-gnueabihf.tar.xz > > > When I attempt to build an application I am getting the following error > message: > > > /usr/local/arm/arm-linux-gnueabihf/include/c++/5.2.1/arm-linux-gnueabihf/bits/os_defines.h:39:22: > > fatal error: features.h: No such file or directory compilation terminated. > > > I looked at the include search and saw several entries like: > > > ignoring nonexistent directory " > */usr/local/arm/bin/../arm-linux-gnueabihf/libc/usr/local/include/arm-linux-gnueabihf* > " > > > I tried to follow this path and it breaks because the path: > > > */usr/local/arm/../arm-linux-gnueabihf/libc* only has the directory > *arm-linux-gnueabihf > *and no directory *usr*. the directory *arm-linux-gnueabihf *does have > the directory *usr.* > > > if the nonexistent directory were: > > > > *"/usr/local/arm/bin/../arm-linux-gnueabihf/libc/arm-linux-gnueabihf/usr/local/include/arm-linux-gnueabihf"* > > instead of > > > *"/usr/local/arm/bin/../arm-linux-gnueabihf/libc/usr/local/include/arm-linux-gnueabihf"* > > > then it would find the features.h include. This error is replicated in > several other nonexistent directory error messages. > > > What could I be doing to cause this? > > > Thanks for your help. > Solved: The problem is with the toolchain sysroot. The sysroot pointed to the wrong place so the includes couldn't be found. It was also a problem for the linker. To solve the problem I moved the directories from the sysroot to the place where the sysroot pointed and everything works correctly now. Not the best answer and will have to solve it better at another time. -- 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] Upgrade runtime on beaglebone
I have searched for too long and can't find a solution. I have a beaglebone black revc and I need to update the c++ runtime to support something greater then glib 4.7. I have 4.9 and 5.1 on my machine that i build and deploy from, but I don't have 4.7 and I am using features of these compiles that I get the message: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version 'CXXABI_1.3.8' not found (required by MyDaemon); looking at strings for this lib indicates it supports up to 1.3.6 but not 1.3.8 glibc 4.9 supports 1.3.8 as does the 5.x versions. Any guidance would be appreciated. -- 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] Cross Development using the linaro 5.2 toolchain
I have been struggling with this issue for longer then I care to admit. I followed the directions to install the toolchain from the page: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-ARMCrossCompiler:GCC with the toolchain: gcc-linaro-5.2-2015.11-x86_64_arm-linux-gnueabihf.tar.xz When I attempt to build an application I am getting the following error message: /usr/local/arm/arm-linux-gnueabihf/include/c++/5.2.1/arm-linux-gnueabihf/bits/os_defines.h:39:22: fatal error: features.h: No such file or directory compilation terminated. I looked at the include search and saw several entries like: ignoring nonexistent directory " */usr/local/arm/bin/../arm-linux-gnueabihf/libc/usr/local/include/arm-linux-gnueabihf* " I tried to follow this path and it breaks because the path: */usr/local/arm/../arm-linux-gnueabihf/libc* only has the directory *arm-linux-gnueabihf *and no directory *usr*. the directory *arm-linux-gnueabihf *does have the directory *usr.* if the nonexistent directory were: *"/usr/local/arm/bin/../arm-linux-gnueabihf/libc/arm-linux-gnueabihf/usr/local/include/arm-linux-gnueabihf"* instead of *"/usr/local/arm/bin/../arm-linux-gnueabihf/libc/usr/local/include/arm-linux-gnueabihf"* then it would find the features.h include. This error is replicated in several other nonexistent directory error messages. What could I be doing to cause this? Thanks for your help. -- 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] BBB RevB with Debian 7.5 image
On Tuesday, January 5, 2016 at 10:12:04 AM UTC-8, RobertCNelson wrote: > > On Tue, Jan 5, 2016 at 12:05 PM, Ray Madigan <raymond...@gmail.com > > wrote: > > I have two Rev B beaglebone blacks. One I never used since I bought it. > I > > recently ordered a Rev C to use for my project but I thought I might as > well > > try to make some use the one I have never used. I wanted to put Debian > 7.5 > > on the device so it would be similar to the one I will get in a couple > of > > days. > > > > I first booted the device with the factory installed Angstrom > distribution. > > It worked well. > > I then downloaded the image from http://beagleboard.org/latest-images > > > > I downloaded > > > > Older Debian images > > BeagleBone Black (eMMC flasher) > > Debian 7.5 (BeagleBone Black - 2GB eMMC) 2014-05-14 - more info - > bittorrent > > - md5: 74615fb680af8f252c034d3807c9b4ae > > > > > > > > I put the image on a microSd card, held the boot button down until it > > started to echo info to the display > > > > It booted and the screen showed in red letters that it was a temporary > > installation and I needed to flash to the eMMC. I used the terminal > program > > and it seemed to work. I didn't have time to flash it so I shut it down. > > >> You shutdown mid flash... So it never completed the eMMC install, so > >> yeah, you have to reflash now... > > >> Here is the latest "stable" 7.x-wheezy/3.8 kernel/2GB: > >> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB.2FBBG_.28All_Revs.29_eMMC_Flashers > > <http://www.google.com/url?q=http%3A%2F%2Felinux.org%2FBeagleboard%3ABeagleBoneBlack_Debian%23BBB.2FBBG_.28All_Revs.29_eMMC_Flashers=D=1=AFQjCNGsDW_xPydCCOp5vncsa7u83SGx_Q> > > > >> btw, we nuked this method, now you users don't get a temp session to > >> play around anymore, everyone has to wait and watch the flashing > >> process ;) > > This is great, I really appreciate your help. I wish I had known that it was flashing. Some link sent me to this page: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC which told me I had to edit a file and reflash. To setup the standalone microSD image to automatically flash the eMMC on > powerup.In /boot/uEnv.txt: ##enable BBB: eMMC Flasher: cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh If this is no longer valid is there something I can do to modify the page? > A couple of hours later I went back to try it again and it would not boot > > the original Angstrom, the blue led's all stay on and nothing happens. > If I > > try to load the Debian image I get 3 lines on the display that I will > post > > next. > > > > [25.132791] libphy: PHY 4a101000.mdio:01 not found > > [25.137954] net etho: phy 4a101000.mdio.01 not found on slave 1 > > [28.305991] tilcdc 4830e000.fb: timeout waiting framedone > > > > Then it waits a period and seems go go to neverlnd. The display responds > > that it has lost its signal. > > > > Any help would be useful. > > > > Useful responses might be something like: > > > > Sorry dude, your device is now bricked. > > or > > Maybe you can get better response here > > or > > Advice on how to reset the device or something. > > Regards, > > -- > Robert Nelson > https://rcn-ee.com/ > -- 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] BBB RevB with Debian 7.5 image
I have two Rev B beaglebone blacks. One I never used since I bought it. I recently ordered a Rev C to use for my project but I thought I might as well try to make some use the one I have never used. I wanted to put Debian 7.5 on the device so it would be similar to the one I will get in a couple of days. I first booted the device with the factory installed Angstrom distribution. It worked well. I then downloaded the image from http://beagleboard.org/latest-images I downloaded Older Debian images BeagleBone Black (eMMC flasher) Debian 7.5 (BeagleBone Black - 2GB eMMC) 2014-05-14 - more info - bittorrent - md5: 74615fb680af8f252c034d3807c9b4ae I put the image on a microSd card, held the boot button down until it started to echo info to the display It booted and the screen showed in red letters that it was a temporary installation and I needed to flash to the eMMC. I used the terminal program and it seemed to work. I didn't have time to flash it so I shut it down. A couple of hours later I went back to try it again and it would not boot the original Angstrom, the blue led's all stay on and nothing happens. If I try to load the Debian image I get 3 lines on the display that I will post next. [25.132791] libphy: PHY 4a101000.mdio:01 not found [25.137954] net etho: phy 4a101000.mdio.01 not found on slave 1 [28.305991] tilcdc 4830e000.fb: timeout waiting framedone Then it waits a period and seems go go to neverlnd. The display responds that it has lost its signal. Any help would be useful. Useful responses might be something like: Sorry dude, your device is now bricked. or Maybe you can get better response here or Advice on how to reset the device or something. Thank you -- 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] Device Control Clock
I have done some searching and I know I need to do more investigation. I am working on the design of an embedded system that talks to a custom interface on an exiting peripheral. I am trying to sort out a bunch of issues, at this point I am overwhelmed with choices so i figured I could maybe shortcut a point that might reduce the investigation effort, at least for a short period. I am looking to figure out if the beaglebone black brings out a clock pin that would synchronize the pru with the external device? I have read that if this functionality is needed then one of the pru processor has to be used to generate the clock thereby reducing the application to use a single pru for it's functionality. The question is: Does the beaglebone black output a clock on any of the output pins? if it does, can you point me to a place to understand how to use it? Thank you. -- 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] chown on mounted microsd
I have mounted my microsd card to use as a database storage, however I can't seem to figure out how to change the settings in /etc/fstab to allow me to chown directories on the card so I can write to it. After rereading the mount man page I thought the suid option would allow change group and change owner to take effect, so maybe I have conflicting options. I have set auto,rw,suid,async,user,nofail 0 0 what am I missing? Thanks you -- 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: Any suggestions would be appreciated
I2C to an arduino or a teen will give me the ds18b20. -- 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] Any suggestions would be appreciated
I am trying to build an application on the Beaglebone Black and I have two semi-requirements. One is that I have to use the DS18B20 onewire temperature sensor. I will look at others like it, but I have many of these and they are setup for this project. The other requirement is that the application has a windowed interface. It can either be in qt or in java, or any other suggestion someone might have. I have tried the images with the 3.14 kernel and lxqt as the window environment and it seems like this would work well. The problem is I can't seem to find a way to make the temperature sensors work in the newer kernels. Everything I can find to make this sensor work uses the cape manager and the images I have use the universal overlay. I have even had people tell me that the sensor doesn't have a driver for the newer kernels and I'm wasting my time. I've looked at memory mapped solutions, most use the capemanager, but I wiould still need to write the one wire protocol and I don't think I'm up for that. I either have to go back to the older kernels that support the cape manager overlay to use the sensors. I'm stuck with finding a windowed environment in the older kernel. Or I have to find a way to access the sensors, or another sensor in the new kernels. Any guidance would be very helpful. Thanks. -- 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: Universal Overlay, enabling a single pin
Thank you for the help. I am trying to use a onewire ds18B20 temperature sensor and I also need to know how to convert the old capemgr dto to work with the universal overlay. Do I just take the fragment@1 piece and put it into a dtsi file and include it in the am335x-boneblack.dts file? Fragment@0 seems to be managed by am335x-boneblack.dts. Then I don't even know if the onewire driver is supported in the new kernel. On Thursday, March 19, 2015 at 8:47:35 AM UTC-7, Graham wrote: Ray: Which release/kernel are you running? You will need to download the correct dtb-rebuilder for that version kernel. Then, go inside the src (source) folder and start with am335x-boneblack.dts and follow the listing, including following and reading any #includes, until you find the file that manages the pin in question. Un comment the statement that will put it in the mode that you want. The universal-io has been rolled into this dtb-rebuilder source. You do not have to go to universal-io separately. You will know it when you find the file. The only warning I would offer, is that to be sure that if the pin is currently in use for some default mode, you need to find that, too, and comment it out. If the pin is assigned to do two modes, the compiler will complain. Once you have a clean make, check to see that the resulting .dtb is where it is supposed to be, then edit the dtb= statement in the uEnv.txt file. --- Graham == On Thursday, March 19, 2015 at 10:16:15 AM UTC-5, Ray Madigan wrote: Thanks Dave, I appreciate your help. I have read that post and the issue is, it uses the capemgr overlay and the image I have doesn't have the capemgr. On Thursday, March 19, 2015 at 1:25:29 AM UTC-7, Dave Blomfield wrote: Hi Ray, This one worked for me, there are a couple of errors in the DTS code which are mentioned in the posts below the main instructions but other than that it works fine. I have 10 sensors working on the same pin returning temperature. http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/ Cheers Dave On Tuesday, 17 March 2015 22:59:37 UTC, Ray Madigan wrote: I have been trying to figure out how to get a single gpio pin to work with my ds18b20 onewire device. I have installed dtb-rebuilder and looked at the device tree definitions in am335x-boneblack.dts and I get the idea that I can comment different sections to get the specific sets of pins to work. I have an old dts file, from 9 months ago or so, but I don't see how it fits in with universal-io. It seems like I need a file xxx.dtsi, and they don't look like the dts files. How do I figure this 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/d/optout.
[beagleboard] Re: Universal Overlay, enabling a single pin
Thanks Dave, I appreciate your help. I have read that post and the issue is, it uses the capemgr overlay and the image I have doesn't have the capemgr. On Thursday, March 19, 2015 at 1:25:29 AM UTC-7, Dave Blomfield wrote: Hi Ray, This one worked for me, there are a couple of errors in the DTS code which are mentioned in the posts below the main instructions but other than that it works fine. I have 10 sensors working on the same pin returning temperature. http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/ Cheers Dave On Tuesday, 17 March 2015 22:59:37 UTC, Ray Madigan wrote: I have been trying to figure out how to get a single gpio pin to work with my ds18b20 onewire device. I have installed dtb-rebuilder and looked at the device tree definitions in am335x-boneblack.dts and I get the idea that I can comment different sections to get the specific sets of pins to work. I have an old dts file, from 9 months ago or so, but I don't see how it fits in with universal-io. It seems like I need a file xxx.dtsi, and they don't look like the dts files. How do I figure this 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/d/optout.
[beagleboard] Universal Overlay, enabling a single pin
I have been trying to figure out how to get a single gpio pin to work with my ds18b20 onewire device. I have installed dtb-rebuilder and looked at the device tree definitions in am335x-boneblack.dts and I get the idea that I can comment different sections to get the specific sets of pins to work. I have an old dts file, from 9 months ago or so, but I don't see how it fits in with universal-io. It seems like I need a file xxx.dtsi, and they don't look like the dts files. How do I figure this 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/d/optout.
[beagleboard] Jessie debian lxqt
I have an installation of Jessie lxqt running and am having difficulty getting it to use a static ip address. in /etc/network/interfaces I have auto eth0 iface eth0 inet static address 192.168.1.113 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 dns-nameservers 184.16.33.54 184.16.4.22 my router has a reserved address for this mac address and it worked on the angstrom and ubuntu images. I am clearly doing something wrong. Thanks in advance. -- 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] Debian Jessie lxqt eMMc failed
I used a serial ftdi card, twice without redirection output and when I disconnected it the display was cleared bu screen. It stopped at some line like 1326.xxx after a few hours. I tried it this morning and it seemed to have worked. I will not try again on this bbb, I have a second bbb that I will keep trying with but somehow I seem to be unable to redirect the output ti=o a file. The file from before was blank. I used the following sudo screen /dev/ttyUSB0 115200 21 | tee bbb_lxqt.txt -- 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] Re: Using microsd card on beaglebone black
I seem to be unable to install LXDE to ubuntu when it is booted from the eMMC, not enough space. Is there a lighter gui environment that I can use? -- 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: Using microsd card on beaglebone black
What I am trying to accomplish is to run a single java application on the beaglebone. The java application extends JFrame so it needs a minimal window environment. The application also uses sqlite database. What I would really like is for the OS on the beaglebone to be able to access a mounted file system on the microsd card. All that I have read so far tells mewhen the beaglebone is loaded from the eMMC then the os can't/won't use the microsd card. In order to have enough storage to run the minimal windowed environment, I assume it to be LXDE, the beaglebone will have to reside on the sd card. Is this correct, or do I have to read more? -- 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] Debian Jessie lxqt eMMc failed
Does it shown the error during flashing on the hdmi? (more info is dumped over the serial debug interface..) It might, but by the time I see it all I can see is the [, ] and the keyboard is dead so I can't scroll up. I have an ftdi cable that I use to program vhdl boards, I will work on figuring that out tonight. Thanks -- 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] Debian Jessie lxqt eMMc failed
I tried to install this last night. It seemed to work for a while. I went away while it was installing and when I came back the leds were flashing, 1, 2, 3, 4, 3, 2, 1 ... repeat. and the display had something like [ , ] . I let it run all night, i don't know how long it is supposed to take. I am not sure if I didn't do something I should have, I held the boot button down on power up until all leds were on then let the button go. I installed this image: BBB-eMMC-flasher-debian-jessie-lxqt-armhf-2015-03-08-2gb.img.xz -- 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] Debian Jessie lxqt eMMc failed
It is writing to my hdmi display, Do I need to connect to it another way? Does it write to the microsd card? -- 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] Re: Using microsd card on beaglebone black
How long should it take? I used the image BBB-eMMC-flasher-debian-jessie-lxqt-armhf-2015-03-08-2gb and after 3 hours the led lights are running from one ent to the other and the display is showing [ 1 ] // not exactly correct because I can't copy/paste it. -- 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] Re: Using microsd card on beaglebone black
if i had the 4gb rev c all my troubles would be easy :) So i guess i will look at debian, since rev c ships with it. if it isn't enough i'll try the micro sd card. If the micro sd card is too slow, I'll have to move to rev c. At least i will be able to develop with what i have. -- 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] Re: Using microsd card on beaglebone black
lxqt implies the qt runtime libraries are already available for development. That would be much better. I will look into it tonight. Thanks for all of your help. -- 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] Using microsd card on beaglebone black
The instructions for expanding memory on a microsd card assume that the os is booted from the microsd card. Can I just use a microsd card and follow the same instructions, but deleting the boot partition to make use of the full microsd card? Sorry if this question has been asked probably hundreds of times before. -- 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] Booting from microSD
I have two beaglebone blacks rev B and I am trying to boot either of them from a microSD card and I can't make either one of them work. I must be doing something wrong and I need some help. I have a 32GB microSD card Pro from Samsung.I wrote the image: *bbxm-ubuntu-14.04.2-console-**armhf-2015-02-19-2gb.img* to the microsd card. I have the bone connected to a monitor, keyboard and mouse. It boots normally. I insert the microSD card press the user boot button and power it up, no light comes on at all for as long as I hold the button. If I try without the button press three lights light up immediately and stay there for ever. Am I doing something wrong? I tired connected to a network and not with the same result. Any guidance would be appreciated? -- 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] Unused BBB Network issues
I have a couple of beaglebone's and I have used one but not the other till this evening. I went in to try to give it a fixed ip address and couldn't ssh to it. I set it up with a HDMI monitor and keyboard and mouse. I went to /usr/lib/connman/tests and ran ./get-services and it just returned. No Services? I tried to opkg update and got bad_address for feeds.angstrom-distribution.org/... My router sees the bbb at address 192.168.1.14 and if I run ifconfig with no ip address and no sent, no anything. Did I forget to do something? -- 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] map timer to gpio pin
I am wondering if it is possible to map a pru timer to a gpio pin to drive another device clock? I am thinking about synchronizing code on the pru with an external device. Any reference to examples that are similar to this would be appreciated. -- 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] Map R30/R31 EGPIO pins
Taking your suggestion I went out to /lib/firmware and found several dts files that used pins like I want to use them. The number of pins in the list I want are 1 to all Plus some. The one that used all the pins I want to use include lots of stuff in the ocp fragment. Is there a way to use a modified version of this one. It is BB-BONE-PRU-04-00A0.dts On Wednesday, October 8, 2014 8:56:47 PM UTC-7, Ray Madigan wrote: I can't thank you enough for your help. Every response is at least another two day learning activity. I just wish I didn't have to work to pay the bills. I went back to see what I did and it turns out I misspelled the name of the dtbo file that I was using so there is no wonder it didn't work. Now I get an error that the file exists when I: echo pru_enable /sys/devices/bone_capemgr.8/slots echo: write error: File exists prussdrv_open open failed so I guess I have more to learn :( What I am really trying to do is learn how to work with this device. This activity is to learn to write to a set of 9 or 10 pins, 8 data and one enable or 2 handshake. My next step is to read fro a set of 9 or 10 pins, 8 for data and one for write enable or 2 for a handshake. So: If I add your desired pinmux settings to a custom PRU overlay based off of one of the BB-BONE-PRU overlays provided with the standard kernel. What would be the limitations? I figure I could work out the problems at a later time. after I see an led light up:) On Wednesday, October 8, 2014 12:21:37 PM UTC-7, Charles Steinkuehler wrote: On 10/8/2014 11:43 AM, Ray Madigan wrote: All I need to do is comment out the pins in exclusive-use section that I don't want to use and comment out all of the entries for those pins in the fragment. Then comment out the sections for the modes I don't want for the pins I do want? If you use a stripped down version of the universal cape overlay, you'll still have the pinmux helper in control of the pin multiplexing. That means you'll need to either setup the proper pin choice using sysfs after loading the overlay or make the desired PRU pinmux mode the default (or both). Alternately, you could add your desired pinmux settings to a custom PRU overlay based off of one of the BB-BONE-PRU overlays provided with the standard kernel. This would prevent any changes to the pinmux setting after loading the overlay, which might be good or bad, depending on exactly what you're attempting to do. -- Charles Steinkuehler cha...@steinkuehler.net -- 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] Map R30/R31 EGPIO pins
I also noticed in the exclusive-use list in the universal overlays you have pru0, pru1, pruss with no other reference. I don't have them in mine? What are they for? On Wednesday, October 8, 2014 11:47:04 PM UTC-7, Ray Madigan wrote: Taking your suggestion I went out to /lib/firmware and found several dts files that used pins like I want to use them. The number of pins in the list I want are 1 to all Plus some. The one that used all the pins I want to use include lots of stuff in the ocp fragment. Is there a way to use a modified version of this one. It is BB-BONE-PRU-04-00A0.dts On Wednesday, October 8, 2014 8:56:47 PM UTC-7, Ray Madigan wrote: I can't thank you enough for your help. Every response is at least another two day learning activity. I just wish I didn't have to work to pay the bills. I went back to see what I did and it turns out I misspelled the name of the dtbo file that I was using so there is no wonder it didn't work. Now I get an error that the file exists when I: echo pru_enable /sys/devices/bone_capemgr.8/slots echo: write error: File exists prussdrv_open open failed so I guess I have more to learn :( What I am really trying to do is learn how to work with this device. This activity is to learn to write to a set of 9 or 10 pins, 8 data and one enable or 2 handshake. My next step is to read fro a set of 9 or 10 pins, 8 for data and one for write enable or 2 for a handshake. So: If I add your desired pinmux settings to a custom PRU overlay based off of one of the BB-BONE-PRU overlays provided with the standard kernel. What would be the limitations? I figure I could work out the problems at a later time. after I see an led light up:) On Wednesday, October 8, 2014 12:21:37 PM UTC-7, Charles Steinkuehler wrote: On 10/8/2014 11:43 AM, Ray Madigan wrote: All I need to do is comment out the pins in exclusive-use section that I don't want to use and comment out all of the entries for those pins in the fragment. Then comment out the sections for the modes I don't want for the pins I do want? If you use a stripped down version of the universal cape overlay, you'll still have the pinmux helper in control of the pin multiplexing. That means you'll need to either setup the proper pin choice using sysfs after loading the overlay or make the desired PRU pinmux mode the default (or both). Alternately, you could add your desired pinmux settings to a custom PRU overlay based off of one of the BB-BONE-PRU overlays provided with the standard kernel. This would prevent any changes to the pinmux setting after loading the overlay, which might be good or bad, depending on exactly what you're attempting to do. -- Charles Steinkuehler cha...@steinkuehler.net -- 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] Map R30/R31 EGPIO pins
I found a problem that P9_31 conflicts with the HDMI Overlay so I will have to figure out if I try to eliminate it because it is not going to be used or if I can move the output to the pru1. On Wednesday, October 8, 2014 11:59:37 PM UTC-7, Ray Madigan wrote: I also noticed in the exclusive-use list in the universal overlays you have pru0, pru1, pruss with no other reference. I don't have them in mine? What are they for? On Wednesday, October 8, 2014 11:47:04 PM UTC-7, Ray Madigan wrote: Taking your suggestion I went out to /lib/firmware and found several dts files that used pins like I want to use them. The number of pins in the list I want are 1 to all Plus some. The one that used all the pins I want to use include lots of stuff in the ocp fragment. Is there a way to use a modified version of this one. It is BB-BONE-PRU-04-00A0.dts On Wednesday, October 8, 2014 8:56:47 PM UTC-7, Ray Madigan wrote: I can't thank you enough for your help. Every response is at least another two day learning activity. I just wish I didn't have to work to pay the bills. I went back to see what I did and it turns out I misspelled the name of the dtbo file that I was using so there is no wonder it didn't work. Now I get an error that the file exists when I: echo pru_enable /sys/devices/bone_capemgr.8/slots echo: write error: File exists prussdrv_open open failed so I guess I have more to learn :( What I am really trying to do is learn how to work with this device. This activity is to learn to write to a set of 9 or 10 pins, 8 data and one enable or 2 handshake. My next step is to read fro a set of 9 or 10 pins, 8 for data and one for write enable or 2 for a handshake. So: If I add your desired pinmux settings to a custom PRU overlay based off of one of the BB-BONE-PRU overlays provided with the standard kernel. What would be the limitations? I figure I could work out the problems at a later time. after I see an led light up:) On Wednesday, October 8, 2014 12:21:37 PM UTC-7, Charles Steinkuehler wrote: On 10/8/2014 11:43 AM, Ray Madigan wrote: All I need to do is comment out the pins in exclusive-use section that I don't want to use and comment out all of the entries for those pins in the fragment. Then comment out the sections for the modes I don't want for the pins I do want? If you use a stripped down version of the universal cape overlay, you'll still have the pinmux helper in control of the pin multiplexing. That means you'll need to either setup the proper pin choice using sysfs after loading the overlay or make the desired PRU pinmux mode the default (or both). Alternately, you could add your desired pinmux settings to a custom PRU overlay based off of one of the BB-BONE-PRU overlays provided with the standard kernel. This would prevent any changes to the pinmux setting after loading the overlay, which might be good or bad, depending on exactly what you're attempting to do. -- Charles Steinkuehler cha...@steinkuehler.net -- 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] Map R30/R31 EGPIO pins
After reading lots of stuff I have what I thought might work.
Segments from my .dts
exclusive-use =
p9.25; /* R30[7] */
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
mygpio: pinmux_mygpio{
pinctrl-single,pins =
0x1AC 0x25 /* P9.25 mode 5 pulldown output */
;
};
};
};
If I do nothing in my pru code this pin is always high even after I reboot
the bbb.
I tried
CLR R30.T7
and the pin still remained high.
Is there something else I need to do.
On Tuesday, October 7, 2014 4:00:44 AM UTC-7, Charles Steinkuehler wrote:
On 10/7/2014 12:39 AM, Ray Madigan wrote:
I am currently using pru0 simply because it is before pru1. Is there a
drawback to using pru1 over pru0.
The two PRU cores are identical, other than the external pins they are
tied to for direct I/O. Choose the PRU core to use based on the pins
you want, or if you're not using direct I/O it doesn't matter which core
you choose.
--
Charles Steinkuehler
cha...@steinkuehler.net javascript:
--
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] Map R30/R31 EGPIO pins
The trouble is, I don't know what to expect. I will look and see whats
there to see if I can make sense out of it.
I looked at the universal overlay when you sent the link to it and it
seemed overwhelming because of the number of entries for each pin. Now
that I have a little more experience with it I can go back and see if I can
figure it out.
All I need to do is comment out the pins in exclusive-use section that I
don't want to use and comment out all of the entries for those pins in the
fragment. Then comment out the sections for the modes I don't want for the
pins I do want?
On Wednesday, October 8, 2014 9:27:28 AM UTC-7, Charles Steinkuehler wrote:
On 10/8/2014 11:10 AM, Ray Madigan wrote:
After reading lots of stuff I have what I thought might work.
Segments from my .dts
exclusive-use =
p9.25; /* R30[7] */
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
mygpio: pinmux_mygpio{
pinctrl-single,pins =
0x1AC 0x25 /* P9.25 mode 5 pulldown output */
;
};
};
};
If I do nothing in my pru code this pin is always high even after I
reboot
the bbb.
I tried
CLR R30.T7
and the pin still remained high.
Is there something else I need to do.
Browse the live device tree (/proc/device-tree) and make sure it's what
you expect. Typically, you create a pinctrl-single,pin entry and refer
to that in some other device. When that device is loaded, the kernel
will implement the pinmux settings referred to.
Is there some reason you're not just using config-pin and loading one of
the universal overlays?
--
Charles Steinkuehler
cha...@steinkuehler.net javascript:
--
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] Map R30/R31 EGPIO pins
I can't thank you enough for your help. Every response is at least another two day learning activity. I just wish I didn't have to work to pay the bills. I went back to see what I did and it turns out I misspelled the name of the dtbo file that I was using so there is no wonder it didn't work. Now I get an error that the file exists when I: echo pru_enable /sys/devices/bone_capemgr.8/slots echo: write error: File exists prussdrv_open open failed so I guess I have more to learn :( What I am really trying to do is learn how to work with this device. This activity is to learn to write to a set of 9 or 10 pins, 8 data and one enable or 2 handshake. My next step is to read fro a set of 9 or 10 pins, 8 for data and one for write enable or 2 for a handshake. So: If I add your desired pinmux settings to a custom PRU overlay based off of one of the BB-BONE-PRU overlays provided with the standard kernel. What would be the limitations? I figure I could work out the problems at a later time. after I see an led light up:) On Wednesday, October 8, 2014 12:21:37 PM UTC-7, Charles Steinkuehler wrote: On 10/8/2014 11:43 AM, Ray Madigan wrote: All I need to do is comment out the pins in exclusive-use section that I don't want to use and comment out all of the entries for those pins in the fragment. Then comment out the sections for the modes I don't want for the pins I do want? If you use a stripped down version of the universal cape overlay, you'll still have the pinmux helper in control of the pin multiplexing. That means you'll need to either setup the proper pin choice using sysfs after loading the overlay or make the desired PRU pinmux mode the default (or both). Alternately, you could add your desired pinmux settings to a custom PRU overlay based off of one of the BB-BONE-PRU overlays provided with the standard kernel. This would prevent any changes to the pinmux setting after loading the overlay, which might be good or bad, depending on exactly what you're attempting to do. -- Charles Steinkuehler cha...@steinkuehler.net javascript: -- 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] Map R30/R31 EGPIO pins
I have been struggling to find a way to map which gpio pins on the BBB map to the specific bit in the R30 R31 registers. I am probably looking for the wrong thing, but I can't find many references. If they are fixed, can't be remapped, how do I find what pins are mapped? Thanks -- 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] Map R30/R31 EGPIO pins
Thank you for your help, I do appreciate it. This is like drinking from a fire hose :) I have a couple of questions. I read your spreadsheet and find the following pru0 has for output bits [0 - 7] and 14, 15 pru0 has for input bits [0-7] and 14, 15, 16 pru1 has for outputs [0 - 15] pru1 has for inputs [0 - 16] I am currently using pru0 simply because it is before pru1. Is there a drawback to using pru1 over pru0. my application will be focused on using about 12 input pins and the only other resource on the beaglebone is the ethernet port. If I wanted all the pins for pru0 as are on the pru1 I would have to learn the pinmux utility. I will eventually figure this out, I'm just looking to make some progress before I have to move to the next step. On Monday, October 6, 2014 10:12:25 AM UTC-7, Charles Steinkuehler wrote: On 10/6/2014 12:01 PM, Ray Madigan wrote: I have been struggling to find a way to map which gpio pins on the BBB map to the specific bit in the R30 R31 registers. I am probably looking for the wrong thing, but I can't find many references. If they are fixed, can't be remapped, how do I find what pins are mapped? You have to configure the pinmux for the pin(s) you want. Remember to enable the input driver, as well (also in the pinmux register). You can do this with a custom device tree overlay or by using my universal cape overlay (with kernel 3.8, partly supported for kernel 3.14) and the config-pin utility. On a recent RCN Debian image, just (for instance): config-pin P8.15 pruin ...to connect P8.15 to PRU 0, R31, bit 15. You may also find the pinmux spreadsheet useful, if you don't want to crawl through the TI data-sheet for the AM3358 and the BeagleBone SRM: https://github.com/cdsteinkuehler/beaglebone-black-pinmux/blob/hal_pru_generic/pinmux.ods -- Charles Steinkuehler cha...@steinkuehler.net javascript: -- 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] Host - Pru synchronization
Thank you very much. I appreciate you taking time to help me figure this out. Now I just have to figure out how to do what you just said. On Friday, September 26, 2014 2:15:28 PM UTC-7, Charles Steinkuehler wrote: You can't clear bits in the status register, you have to clear whatever is generating the status bit directly. That's either an input pin or (in your case) the interrupt from the local INTC. So try clearing the actual interrupt bit, and the PRU code should then wait as expected for the next handshake. I suspect the PRU is currently running to completion because you're never clearing the interrupt that kicks things off, so waitForHost() doesn't actually do anything after the first wait and simply falls through from then on. -- Charles Steinkuehler cha...@steinkuehler.net javascript: -- 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] Host Pru Synchronization
I thought I submitted this question but I can't find it so maybe i didn't
hit post. If it is a duplicate, I apologize.
I am trying to figure out the pru and see how I would use it in my
application. I am using the beta c libraries, which may be a problem.
All of the things I am doing I have made to work individually. I just can't
get them to all work together.
My goal here is to synchronize a set of commands to the pru.
The Pru code is:
for (i = 0; i 3; i++){
waitForHost();
// CLR R31, R31, 30 \n
// WBS R31, 30 \n
// CLR R31, R31, 30 \n
readInstruction();
// perform task
notifyHost();
// LDI R31.b0, PRU0_ARM_INTERRUPT + 16 \n
}
the Host code is:
initializeApplication();
for (i = 0; i 3; i++){
writeInstruction();
notifyPru();
//prussdrv_pru_send_event(ARM_PRU0_INTERRUPT);
waitForPru();
//prussdrv_pru_wait_event(PRU_EVTOUT_0);
//prussdrv_pru_clear_event(PRU_EVTOUT_0, PRU0_ARM_INTERRUPT);
}
I added a write to shared memory location 0 for debug and when I run this
once the pru gets the first notification
it does not stop at the waitForHost() at the top of the loop. The loop
index is 2, never stopping at 0 or 1.
if I comment out the notifyPru(); call the pru waits and does not execute
the loop.
I can either get it to not execute any passes or all of them at once.
Any light would be appreciated.
--
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] Host - Pru synchronization
I am trying to understand how to take advantage of the pru to see if I can
use it in my application.
I am trying to synchronize the pru execution from the host. I am using the
c libraries, which could be a proble. What I am doing is simple enough
that I don't think this should be a problem unless it really just doesn't
work.
My pru code looks like this:
for (i = 0; i 3; i++){
waitForHost()
// CLR R31, R31, 30 \n
// WBS R31, 30 \n
// CLR R31, R31, 30 \n
readInstruction();
// read from shared memory location
// do work for instruction
notifyHost()
// LDI R31.b0, PRU0_ARM_INTERRUPT + 16 \n
}
the host loop is:
// Initialize the pru
for (i = 0; i 3; i++){
// write to shared memory location
writeInstruction();
// Tell the pru to read the instruction
notifyPru();
// prussdrv_pru_send_event(ARM_PRU0_INTERRUPT);
// Wait for pru to complete the operation
waitForPru();
// prussdrv_pru_wait_event(PRU_EVTOUT_0);
// prussdrv_pru_clear_event(PRU_EVTOUT_0, PRU0_ARM_INTERRUPT);
}
For debugging the pru writes the loop index to shared memory location 0.
As is, the first time the host reads the debug location, its value is 2 and
never is 0 or 1.
It is as if the first time the pru is notified, it runs to completion, not
stoping for the waitForHost at the top of the loop.
If I comment out the notifyPru() in the host, the host hangs waiting for
the pru because the pru is still waiting.
Any help would be appreciated.
--
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.
