[beagleboard] Re: Systemd start service early in boot

My stuff was working fine and has no dependency on networking. It was networking that stopped working when I tried to run before it. It appears that my .service file was changing how networking was staring. I still haven't found a good description on how to set all this up but the following wor

[beagleboard] Re: Systemd start service early in boot

No, I am trying to get my stuff to start as early as possible. After networking starts is too long. Before would be best but in parallel is probably OK. On Friday, August 28, 2015 at 4:35:38 PM UTC-4, Graham wrote: > > > It looks like you are programming that you want your service to start > "B

[beagleboard] Systemd start service early in boot

I am trying to create a systemd service to start before or in parallel with networking in the boot process. I have tried a bunch of variations to try to get my script to start early that don't work. This may be getting it to start early but then networking doesn't work. This is running /bin/tr

[beagleboard] Re: Reduce PRU DDR read latency

On Saturday, January 17, 2015 at 11:17:55 AM UTC-5, ericgg...@gmail.com wrote: > > I found the examples in 'am335x_pru_package' on GitHub very useful, and > was able to get them working on a 3.8 kernel. > > I have used that. I don't think there is a DMA example that works in there. I have ever

[beagleboard] Re: What happens if PRU & host try and write same memory address at same time?

On Friday, January 16, 2015 at 1:58:33 PM UTC-5, Bill Gray wrote: > > The idea is that the host program is constantly setting an address in > shared memory to 0 in a loop. The PRU is also constantly incrementing that > same address. If the host loop stops, the value at the address climbs >

[beagleboard] Reduce PRU DDR read latency

I see up to 5.8 microseconds of latency when the PRU is reading from DDR memory. Is it possible to reduce this? I tried changing registers that looked promising for giving the PRU priority but they didn't have a noticeable effect. This is running on a Beaglebone black using a PRU timer to mea

[beagleboard] Changes needed to use PRUSS with kernel 3.14

I have a user of my cape who tried to use the 3.14 beaglebone black based Debian image. My instructions were for 3.8 so didn't work. So far I have been unable to find a good summary on what I would need to do to convert configuring using /sys/devices/bone_capemgr.* to the method used for 3.14.