Re: [beagleboard] Re: eQEP on 4.4.19-ti-r41

Mark, let us know if you figure anything out. I spent a couple hours on trying to figure this out myself - with no joy. Something seems very broken, but I did recall that the PWM modules exhibit the same behavior, if you do not load the epwmss modules prior to loading the actual pwmx module in a

Re: [beagleboard] Re: USB Disconnect/Reconnect Randomly

> > I have a BBB connected to Windows via USB. I'm watching the "Device > Manager" under Windows. The window constantly refreshes every 5 to 10 > seconds with the BBB Serial port showing and then... not showing. The > port is constantly reconnecting. It does this 90% of the time. There are >

Re: [beagleboard] Re: eQEP on 4.4.19-ti-r41

Yeah that probably wont work. It's probably configuring the eQEP module as a PWM. I don't know Mark, it seems broken to me. Nothing of use here: debian@beaglebone:~$ sudo find / -type d -name '*qep*' /sys/bus/platform/drivers/eqep /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep

Re: [beagleboard] Re: eQEP on 4.4.19-ti-r41

OK so hopedully this helps you Mark. debian@beaglebone:~$ ls /sys/devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm pwmchip5 debian@beaglebone:~$ ls /sys/class/pwm/pwmchip5 device export npwm power subsystem uevent unexport debian@beaglebone:~$ ls /sys/class/pwm/pwmchip5 device

Re: [beagleboard] Re: eQEP on 4.4.19-ti-r41

> > *echo bone_eqep1 > $SLOTS* > -bash: echo: write error: File exists > Yeah, you're going to get this error whenever you load a device tree file that attempts to mux pins that have already been muxed in a different overlay. At minimum, when using config-pin overlay . I'm not however sure if one

Re: [beagleboard] Re: Remote Proc and examples to fill PRU data memory, store/read data in PRU shared memory

Hi Paul, I would advise against doing any "production" code using /dev/mem + mmap(). For the simple reason that you'll have latency introduced that will not be predictable. For your purposes. However, with that said, it would be ok for "test code" where timing is not too important. I would also

Re: [beagleboard] Re: expansion connector spec?

The layout for the first of two boards has just completed. We are working on the second board layout now. Gerald On Wed, Sep 14, 2016 at 7:14 PM, Dennis Lee Bieber wrote: > On Wed, 14 Sep 2016 09:19:58 -0500, Gerald Coley > declaimed the

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

I have done some work with that sensor on a BBG: https://www.ccoderun.ca/sg++/api/classSG_1_1TemperatureSensor.html#details ...connected to this Grove ADC: https://www.ccoderun.ca/sg++/api/classSG_1_1I2CADC.html#details The problem is the numbers I was retrieving didn't make sense, and I

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

Robert, thank you once again, just a small correction I'm using a Beaglebone Black. When I tried referring to the officialpage of seeed studio I found this http://wiki.seeedstudio.com/images/thumb/8/8e/Grove_Temperature_Sensor_Hw_connect.jpg/600px-Grove_Temperature_Sensor_Hw_connect.jpg So i

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

> On Sep 14, 2016, at 5:24 PM, Robert Nelson wrote: > > > >> On Wed, Sep 14, 2016 at 3:41 PM, Siddharth Amaravadi >> wrote: >> Thank you for the response, but the pins are named as SIG and NC on the >> board. These are the pins that

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

Can I use the setup mentioned in this link https://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/adc to connecct the temperature sensor to ADC of my BBB? Is there any other setup that you'd suggest? Thanks Siddharth On Thu, Sep 15, 2016 at 4:33 AM, Jason Kridner

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

On Wed, Sep 14, 2016 at 5:50 PM, Siddharth Amaravadi wrote: > Oh I was totally misled by it. So, do you advise me to connect the SIG and > NC pins to the analog pins? > > If yes can you provide me some guide as in how to go with that. You'll need a voltage

Re: [beagleboard] wifi works when BBGW first powered on, but not after a warm reboot

While we wait for the kernel to build and get pushed out via apt, you can run this to update the *.dtb's.. debian@beaglebone:~$ git clone -b 4.4-ti https://github.com/RobertCNelson/dtb-rebuilder Cloning into 'dtb-rebuilder'... remote: Counting objects: 7564, done. remote: Compressing objects:

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

> Yeah i saw that picture too, that's so mis-leading.. > > That "pin" on that board, must have an adc-pinmux option.. or it's the wrong > stock picture.. in all my demo's i usually use this temperature sensor:

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

On Wed, Sep 14, 2016 at 4:34 PM, Siddharth Amaravadi < siddharth.amarav...@gmail.com> wrote: > Robert, thank you once again, just a small correction I'm using a > Beaglebone Black. When I tried referring to the officialpage of seeed > studio I found this >

Re: [beagleboard] wifi works when BBGW first powered on, but not after a warm reboot

Switching to using gpio-hog vs the regulators seem to have helped.. I'm about a dozen soft-reboot's into testing, so i pushed this debian@beaglebone:~$ dmesg | grep wl [ 34.377974] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11) [ 34.507372] wlcore: loaded [ 34.909463] wlcore: PHY

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

On Wed, Sep 14, 2016 at 3:41 PM, Siddharth Amaravadi < siddharth.amarav...@gmail.com> wrote: > > > Thank you for the response, but the pins are named as SIG and NC on the > board.

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

Thank you for the response, but the pins are named as SIG and NC on the board. These are the pins that I connected to the P9_19 and P9_20 respectively SIG -> P9_19 NC ->

[beagleboard] Re: eQEP on 4.4.19-ti-r41

Well, I found half my answer. A simple: *config-pin -a P8_11 qep* *config-pin -a P8_12 qe*p gets the eQEP pin muxes set, but once set how do I export them? *cd /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep* *ls* driver_override modalias of_node power subsystem uevent There

[beagleboard] Re: Header files for non PRU peripherals

#define CM_PER_SPI0_CLKCTRL(*((volatile unsigned int *) 0x44E0004C)) #define CM_PER_SPI1_CLKCTRL(*((volatile unsigned int *) 0x44E00050)) in your main method after you enable the OCP master port using STANDBY_INIT: // to enable SPI0 while (! (CM_PER_SPI0_CLKCTRL == 0x2) ) {

[beagleboard] Re: Header files for non PRU peripherals

Kirk, You probably need to enable the peripheral (and its clocks) using its CM_PER register in order to read and write its registers. Let me look up the address in the TRM real quick and I'll post some psuedo-code. Jason Reeder On Wednesday, September 14, 2016 at 2:48:51 PM UTC-5, Kirk

[beagleboard] eQEP on 4.4.19-ti-r41

Hi: I'm running BeagleBoard.org Debian Image 2016-08-28 which is running the 4.4.19-ti-r41 kernel. I've disabled the HDMI (audio and video) and want to use the eQEPs. *ls /lib/firmware/ | grep -i eqep* bone_eqep0-00A0.dtbo bone_eqep1-00A0.dtbo bone_eqep2-00A0.dtbo bone_eqep2b-00A0.dtbo

Re: [beagleboard] wifi works when BBGW first powered on, but not after a warm reboot

Yes, I have this problem, too. I have not tried figuring out a SW solution. I just power cycle on the thankfully few times I need to reboot. Mark On Wed, Sep 14, 2016, 11:34 AM Stephane Charette wrote: > On Saturday, September 10, 2016 at 2:09:16 PM UTC-7, Stephane

Re: [beagleboard] Re: Remote Proc and examples to fill PRU data memory, store/read data in PRU shared memory

I second TJF. It may end up being a case like this: https://xkcd.com/927/ See if RpMSG fits your needs, if it doesn't, try using pruss... On Wednesday, September 14, 2016 at 10:35:41 AM UTC-5, TJF wrote: > > Hi Paul! > > Am Mittwoch, 14. September 2016 12:45:04 UTC+2 schrieb >

Re: [beagleboard] expansion connector spec?

while the concept isn't really new some of the concepts made possible by today's soc e.g. such as integrated lcd controller or gpu + a host of other io features e.g. adc / dac etc made and other on soc modules possible new use cases

Re: [beagleboard] Re: Remote Proc and examples to fill PRU data memory, store/read data in PRU shared memory

Hi Paul! Am Mittwoch, 14. September 2016 12:45:04 UTC+2 schrieb paulandre...@gmail.com: > > Chris, yes uio_pruss/prussdrv examples seem to give me better control > than Remote Proc/RpMsg, I am thinking of trying to rebuild the kernel with > the pruss_io kernel objects instead, then use

[beagleboard] USB Disconnect/Reconnect Randomly

I have a BBB connected to Windows via USB. I'm watching the "Device Manager" under Windows. The window constantly refreshes every 5 to 10 seconds with the BBB Serial port showing and then... not showing. The port is constantly reconnecting. It does this 90% of the time. There are times

Re: [beagleboard] wifi works when BBGW first powered on, but not after a warm reboot

On Saturday, September 10, 2016 at 2:09:16 PM UTC-7, Stephane Charette wrote: > > On Friday, September 9, 2016 at 1:15:42 PM UTC-7, RobertCNelson wrote: >> >> On Fri, Sep 9, 2016 at 2:45 PM, Stephane Charette >> wrote: >> > When I first plug power into my BBGW,

Re: [beagleboard] expansion connector spec?

no worries, imho beagleboards, beagle bone black etc, raspberry pi etc had the 'public' 'discover' or become aware of a niche in the sense of 'form factor' the old pc desktops are bulky computers by today's standards, laptops, netbooks, tablets, mobile phones are 'non-expandable' intel compute

Re: [beagleboard] expansion connector spec?

This is not a BeagleBone Black, not even close. This is a whole different, complex and powerful beast. I am working on add on boards at the moment and should have some things out soon. Hopefully this will help to somewhat solidify an add-on board strategy. It is tough to make it as simple as the

Re: [beagleboard] expansion connector spec?

thanks for clarifying, no worries, i think it is a good development nevertheless, i'd guess as with new boards it'd take some time for the community (and add-on/cape makers) to come up with the 'add-ons' capes etc which hopefully would become a new eco-system On Wednesday, September 14, 2016

Re: [beagleboard] expansion connector spec?

It is not a custom part. It is a standard product offered by Hirose. I tried using the connectors used on the BeagleBone Black. I could not pull the boards apart. And there were signal integrity concerns on the SATA and PCIe signals Gerald On Wed, Sep 14, 2016 at 8:30 AM, Andrew Goh

[beagleboard] expansion connector spec?

On Thursday, February 18, 2016 at 9:10:55 PM UTC+8, m...@yapatel.com wrote: > Hi - > > Is the part number/spec for the expansion connector available somewhere or still waiting for public release? Was unable to find anything with go-ogle. On Friday, February 19, 2016 at 1:04:52 AM UTC+8, Gerald

[beagleboard] posting to forum without being moderated

is there any specific settings i can do so that i can post to the forums without the posts / replies going into moderation? it is rather frustrating as i'd not be able to review edit the post once submitted and i'd need to await moderation turnaround which could take a while -- For more

[beagleboard] Disable Wake-up from UART0

Hi All; --- I want disable/enable deep sleep using the following command: echo enabled > /sys/devices/4400.ocp/44e09000.serial/power/wakeup echo "disabled > /sys/devices/4400.ocp/44e09000.serial/power/wakeup When i disable WAKE-UP from uart then interface face is disable but it

[beagleboard] Re: an initial success; beagle bone black + 7" LCD touchscreen cape a very nice/awesome combo

additional success, yup u can power the beaglebone black with the lcd screen from one of those 'usb power banks' (lipo battery chargers) i've had to hack a usb cable in which one end is usb going to the power bank and the other the barrel jack going into the BBB -- For more options, visit

Re: [beagleboard] Grove temperature sensor on Beaglebone Black

> On Sep 14, 2016, at 12:22 AM, Siddharth Amaravadi > wrote: > > Hello, > > I've connected a Grove temperature sensor to my BBB. When I try to detect it > using i2cdetect, I don't see my sensor connected. Can you please help, > following are some details > >

[beagleboard] Grove temperature sensor on Beaglebone Black

Hello, I've connected a Grove temperature sensor to my BBB. When I try to detect it using i2cdetect, I don't see my sensor connected. Can you please help, following are some details I2C Connection Details: SIG -> P9_19 NC -> P9_20 root@beaglebone:/# uname -a Linux beaglebone 3.8.13-bone47 #1

[beagleboard] Grove Temperature Sensor on Beaglebone Black

Hello, I'm trying to connect a Grove Temperature sensor (http://wiki.seeedstudio.com/wiki/Grove_-_Temperature_Sensor_V1.2#Connecting_hardware) to my BBB. and when I try to detect the sensor I'm not able to find it. Can someone please help me out root@beaglebone:/# uname -a Linux beaglebone

Re: [beagleboard] Re: Remote Proc and examples to fill PRU data memory, store/read data in PRU shared memory

Hi, Thanks to everyone who replied. William, yes I would use the PRU IEP timer on one of the PRUs to generate 100kHz timer for time stamping data. It gives me 2000 cycles theoretically to play with. If the main loop takes longer I could always poll multiple times for the interrupt. Every

Re: [beagleboard] Unable to Flash the internal eMMC of BBB Rev C

I'm having the same "problem" with BBB rev C & BBG WiFi and I also came to conclusion that something was not explained right, or that SW flashing package was not "packed" well for novice users. And I just need to say that answer as such is very immature, specially giving the amount of

Re: [beagleboard] Re: Remote Proc and examples to fill PRU data memory, store/read data in PRU shared memory

Hi, Thanks for everyone who has got in touch. I have a few ideas now. I'll give /dev/mem and mmap() a go since I know the absolute addresses of the memories I want to read write from, thanks William. Greg, yes I am worried about how fast I can get RpMsg to work to spit out the ADC data, or

Re: [beagleboard] conflict with "cape-bone-iio" overlay and simple pinmux overlay?

Jason Kridner, You totally saved me! I had no idea what was going on until I stumbled on your guess. Keep on guessing is all I can say! Thanks!!! On Friday, February 21, 2014 at 5:21:36 PM UTC-8, Jason Kridner wrote: > > > > > On Fri, Feb 21, 2014 at 3:53 PM, wrote: >