Re: [beagleboard] Re: Figure out how to configure correctly modules, pins, and PRU to blink a led

I did some step forward and I putted my header file on github . I hope that it could be helpfull :) One note: it is mandatory to power the TSC_ADC via PRCM or DT (i.e. device tree, I used the uio_pdru_genirq as suggested by zmatt). Now, I am experiencing that

Re: [beagleboard] Re: [beagle-alpha] v4.9.x-ti now open for testing...

Thanks Drew. On Tue, Jan 31, 2017 at 9:08 PM, Drew Fustini wrote: > On Tue, Jan 31, 2017 at 9:28 PM, William Hermans > wrote: > > Drew, do you have a complete gist on how you set this all up ? Mark Yoder > > was interested in the wqep module a while back,

Re: [beagleboard] Re: [beagle-alpha] v4.9.x-ti now open for testing...

On Tue, Jan 31, 2017 at 9:28 PM, William Hermans wrote: > Drew, do you have a complete gist on how you set this all up ? Mark Yoder > was interested in the wqep module a while back, but I do not thnk he was > able to figure it out completely. Also, from a personal project /

Re: [beagleboard] Re: [beagle-alpha] v4.9.x-ti now open for testing...

On Tue, Jan 31, 2017 at 4:47 AM, Drew Fustini wrote: > On Mon, Jan 30, 2017 at 8:40 PM, Robert Nelson > wrote: > > Once you enable the power control, it's it acting the same as v4.4.x was? > > Yes, it does read position ok. > > # uname -r >

Re: [beagleboard] Re: Of SPI and such

On Tue, Jan 31, 2017 at 8:08 PM, William Hermans wrote: > No way in hell CANBUS is going to keep up with multi channel ADC samples > at faster sample rates. If one needs fast, or super fast sampling, the only > real option is going to be SPI. > Sorry, I meant to say ethernet

Re: [beagleboard] BBBwireless Wifi disabled with LiPo

I have no idea what voltage is required by the wifi module is. But if it requires more than 3.7v, it won't get it when you're running off the onboard PMIC battery circuit. So if you need a constant 5v uninterrupted, you would be better off setting up your own external "UPS" type of system. On

Re: [beagleboard] eqep in linux 4.4.38+ not working

On Tue, 1/31/17, abhilash h wrote: Subject: Re: [beagleboard] eqep in linux 4.4.38+ not working To: beagleboard@googlegroups.com Date: Tuesday, January 31, 2017, 11:05 PM Hi ,Its in device driver/misc/ ti eqepOn Tue, 31

Re: [beagleboard] Re: Of SPI and such

No way in hell CANBUS is going to keep up with multi channel ADC samples at faster sample rates. If one needs fast, or super fast sampling, the only real option is going to be SPI. So using the on die ADC last year I did a bit of a test to see how much data really would be written out to "disk"

Re: [beagleboard] eqep in linux 4.4.38+ not working

Hi , Its in device driver/misc/ ti eqep On Tue, 31 Jan 2017 at 8:44 PM, Justin Pearson wrote: > Hi Abhilash, where are the EQEP settings in the kernel config menu? > Thanks, > Justin > > On Monday, January 30, 2017 at 9:06:43 AM UTC-8, abhilash h wrote: > > My bad . It

Re: [beagleboard] Phasors calculation using libpruio

> On Jan 31, 2017, at 7:19 AM, TJF wrote: > > > > Am Montag, 30. Januar 2017 18:36:37 UTC+1 schrieb john3909: > Well, again it depends on what you mean by realtime. To most developers, it > means deterministic > > Yes, deterministic: > steady latency > the lowest

Re: [beagleboard] Phasors calculation using libpruio

Am Montag, 30. Januar 2017 18:36:37 UTC+1 schrieb john3909: > > Well, again it depends on what you mean by realtime. To most developers, > it means deterministic > Yes, deterministic: 1. steady latency 2. the lowest possible steady latency and since the AM335x ADC uses a sequencer to

Re: [beagleboard] eqep in linux 4.4.38+ not working

Hi Abhilash, where are the EQEP settings in the kernel config menu? Thanks, Justin On Monday, January 30, 2017 at 9:06:43 AM UTC-8, abhilash h wrote: > > My bad . It was disabled in the kernel config. > On Mon, 30 Jan 2017 at 3:08 PM, abhilash h > wrote: > >> Dear All, >>

Re: [beagleboard] config for BBBW on buildroot

On Tue, Jan 31, 2017 at 7:38 AM, rajesh bhandari wrote: > Hi all, > > I have worked on RPi for quite some time , but because of lack of onboard > storage on it, I decides to switch to BBBW. > My problem is that, I do not want to use a 4GB image for my system which is >

[beagleboard] BBBwireless Wifi disabled with LiPo

Hi, I have an issue when booting from battery on the VIN_BAT. The WIFI_EN light never turns on in this case but it does on USB power. It seems like the TL1963A Regulator doesn't get any input voltage when on battery. We noticed the D2 diode is missing from our boards and it would give power to

[beagleboard] config for BBBW on buildroot

Hi all, I have worked on RPi for quite some time , but because of lack of onboard storage on it, I decides to switch to BBBW. My problem is that, I do not want to use a 4GB image for my system which is basically an IoT device. Thats why I usually use buildroot to generate minimal rootfs. I see

Re: [beagleboard] Interfacing four 8-bit cameras with Beagalboard X-15.

If there are conflicts in the pinmux tool, you need to contact TI for assistance. Or you can go through the TRM to determine whether the pinmux tool is corrector not. Gerald On Mon, Jan 30, 2017 at 10:13 PM, wrote: > Hi, > I want to interface four 8-bit cameras

[beagleboard] Interfacing four 8-bit cameras with Beagalboard X-15.

Hi, I want to interface four 8-bit cameras with my BeagalBoard X-15 development baoard. I have gone through TI pinMux tool for pin mapping but i found some pin conflicts in "de","fld" pins selection in VIN ports. Please guide me whether these pins are useful or not. Thanks. Regards Rahul

[beagleboard] Re: can't load device tree on Debian jessie 8.6 with kernel version 4.4.43-ti-r84

There are two examples, one for PRU0 and another for PRU1. So you will get rpmsg_pru30 for PRU0, and rpmsg_pru31 for the other. So if you are seeing rpmsg_pru31, this is a major step forward and you have it working!!! Also note the "c" at the first column of the ls; this indicates a character

[beagleboard] Re: Of SPI and such

If you want one 'thing' to talk to a bunch of 'things', or a bunch of 'things' to all talk to each other, you should read up on that mysterious CAN stuff. That is exactly what it was designed for. On Monday, January 30, 2017 at 1:16:41 PM UTC-8, woody stanford wrote: > > The answer I was

[beagleboard] Re: [beagle-alpha] v4.9.x-ti now open for testing...

On Mon, Jan 30, 2017 at 8:40 PM, Robert Nelson wrote: > Once you enable the power control, it's it acting the same as v4.4.x was? Yes, it does read position ok. # uname -r 4.9.6-ti-r17 # cat /sys/devices/platform/ocp/48304000.epwmss/48304180.eqep/power/control

Re: [beagleboard] Re: pyserial stopped working after Debian update?

Thanks Robert, Now it works. I modified uEnv.txt at two places; one for the display to work end another for the UART's to work. Back to the application. Regards, Harke On 30 January 2017 at 22:02, Robert Nelson wrote: > On Mon, Jan 30, 2017 at 2:41 PM, Harke Smits

[beagleboard] Re: can't load device tree on Debian jessie 8.6 with kernel version 4.4.43-ti-r84

so did an ls on /lib/firmware, I am showing part of the ls, but it should show the 2 files you are interested in (bold and underlined): root@beaglebone:/lib/firmware# ls -l -rw-r--r-- 1 root root 1102 Dec 9 21:09 ADAFRUIT-SPI0-00A0.dtbo -rw-r--r-- 1 root root 1105 Dec 9 21:09