Re: [beagleboard] Re: Best way to build a large array for access by PRU0?

Am Donnerstag, 1. März 2018 23:37:01 UTC+1 schrieb john3909: > > Hi TJF, > > I love the work you do and the advise you give. My only purpose was to > remove any confusion ;-) > > Regards, > John > If that is a fact, why don't you replace phrasing like This is not a true statement. by wording

Re: [beagleboard] baseboard folder disappears in bone_capemgr after kernel upgrade to latest 4.4 kernel

Is there a way to get the serial number without using sudo? --Luther On Tuesday, February 20, 2018, 12:59:42 AM GMT+8, Robert Nelson wrote: On Mon, Feb 19, 2018 at 10:50 AM, Luther Goh Lu Feng wrote: > For clarity, the difference is as

Re: [beagleboard] Re: GPIO_60 pin is set to 1, and is missing from /sys/class/gpio

- All version is in the first post - All details about export are in the history of this post. - All other pins exports works, except this one. This is unexportable and it's voltage is 1 On Wednesday, February 28, 2018 at 9:29:30 PM UTC-5, Wulf Man wrote: > > If

Re: [beagleboard] Fwd: Pocket Beagle index.js issue?

Thanks, it reports 0.6.3 now. What pins should I be using? I don't know the conventions and expected usages. I'm wiring OE to ground, and driving SDI, CLK, and LE. 44 LED light bar: Based on the STP08CL596 chip made by ST. There are six IC's. Five control forty LED's(eight each...) and one IC

Re: [beagleboard] Re: Best way to build a large array for access by PRU0?

Hi TJF, I love the work you do and the advise you give. My only purpose was to remove any confusion ;-) Regards, John > On Mar 1, 2018, at 9:06 AM, TJF wrote: > > > > Am Mittwoch, 28. Februar 2018 16:28:18 UTC+1 schrieb john3909: > >> On Feb 28, 2018, at 6:47

Re: [beagleboard] https://github.com/beagleboard/pocketbeagle/wiki/System-Reference-Manual#table-8-p2-header-pinout

There is a .csv version at https://github.com/beagleboard/capes. On Thu, Mar 1, 2018 at 3:42 PM Fred Kerr wrote: > > Hello, it appears that P2.36 may have a typo in this table. It looks like > some of P2.35 data may be copied twice. > > Are these tables available in a .CSV or

Re: [beagleboard] Fwd: Pocket Beagle index.js issue?

Responding to a query you made privately Try clearing the npm cache and setting the install path. The root user environment doesn't seem quite right. TERM=none sudo npm cache clear TERM=none sudo npm install -g --prefix /usr/local --unsafe-perm bonescript On Thu, Mar 1, 2018 at 2:38 PM

[beagleboard] Re: rproc bind/unbind problem

Hey, unbind/bind doesn't work in the latest kernel versions. Instead you can use this to restart remoteproc and load the firmware: echo 'stop'>/sys/class/remoteproc/remoteproc1/state echo 'start'>/sys/class/remoteproc/remoteproc1/state Regards. On Monday, February 19, 2018 at 8:33:32 PM

[beagleboard] Re: Lots of wpa_supplicant CTRL-EVENT-SIGNAL-CHANGE in syslog

I'm seeing the same thing in our logs, our connections keep getting reset. Did you get an answer? On Sunday, November 19, 2017 at 3:43:54 PM UTC-8, bodd...@gmail.com wrote: > > Same problem but in my case, after about 15 minutes the network is > inaccessible but my wifi dongle still connected

[beagleboard] https://github.com/beagleboard/pocketbeagle/wiki/System-Reference-Manual#table-8-p2-header-pinout

Hello, it appears that P2.36 may have a typo in this table. It looks like some of P2.35 data may be copied twice. Are these tables available in a .CSV or plain text format? I'll keep poking around. Thanks, Fred -- For more options, visit http://beagleboard.org/discuss --- You received this

Re: [beagleboard] Fwd: Pocket Beagle index.js issue?

Great, thanks! I was just choosing some pins to connect to the light bar. I had initially wired it up to an Arduino101 to amuse my ~4 - year old son. I'm just grabbing things out of my parts that I have available and as time permits. I started playing with a small solar cell as an input to 1.8v

[beagleboard] Re: Best way to build a large array for access by PRU0 ?

Hi Evan, I'm still with you! The solution is drop rproc and use libprussdrv instead. You'll find everything you need, just use it out-of-the-shelf. Everything is explained in the docs. The steps are: 1. compile your PRU code by pasm assembler 2. load the uio_pruss driver with suiting

Re: [beagleboard] BB Blue with single pulse encoder input

On 2/28/18 10:33 AM, justincre...@gmail.com wrote: Hi Mark, I am interested in doing the same thing (i.e. a basic hall effect sensor connected to the encoder channel on BB Blue). Can you provide more details on how you got it to work? How did you change the control registers in the eQEP

[beagleboard] Best way to build a large array for access by PRU0 ?

Hello, I've been working with PRU0 on the Beaglebone Black (wireless) for a couple weeks now (only a beginner) and have made some hopeful progress towards developing a real time system that will change gpio logic states based on given location data from a pupil-tracking system. So far

Re: [beagleboard] Fwd: Pocket Beagle index.js issue?

Thanks for the issue report and test code. It helped me verify the fix for shiftOut.js. Indeed it got broken some time back and it seems no one tried using the function. Anyway, it is now fixed in 0.6.3. Install via 'sudo npm install -g --unsafe-perm bonescript'. I tested with the BaconBits

Re: [beagleboard] Re: Best way to build a large array for access by PRU0?

Am Mittwoch, 28. Februar 2018 16:28:18 UTC+1 schrieb john3909: > > > On Feb 28, 2018, at 6:47 AM, TJF > wrote: > > When you allocate the array from user space the memory may be not > continuous. To get a single block, you have to allocate from kernel space. > > This is