--
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/261e8b4f-928e-4b33-bf37-47fd5385b423%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I had the PRU's working with an 4.x kernel around 4-5 months ago. Basically I downloaded Jason's PRU github files, and got two of the examples working. Back then, you could only use the older UIO PRU source examples with the *bone* kernel, as TI's kernel was remoteproc only. Now days, supposedly it's possible to to use either with TI kernels by properly commenting / uncommenting a given device tree overlay, and blacklisting the driver modules you're not going to use. I say "supposedly" as I do not know from first hand experience, because I've been too busy building a system professionally( day job ).
Robert has laid out the general procedure, and the given overlay files are commented well, in order to achieve the end goal of using pruss_uio, or remoteproc. However, knowing which file needs modification, and the rest can be hard to figure out if you're unaware of these changes.
Additionally, the less you know about Linux in general. The harder time you're going to have setting up either UIO, or remoteproc.The only time I ever saw a seg fault happen with the PRU example code. Was when I tried running the example code as a regular user. e.g. you need to run the examples with elevated permissions. Which means you must be the user root, or use sudo as a regular user.
--
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/CALHSORqpBaqCFk3UAVmRxbcE-8j0DkUtiaams5B6wD_ejAANvw%40mail.gmail.com.
I had the PRU's working with an 4.x kernel around 4-5 months ago. Basically I downloaded Jason's PRU github files, and got two of the examples working. Back then, you could only use the older UIO PRU source examples with the *bone* kernel, as TI's kernel was remoteproc only. Now days, supposedly it's possible to to use either with TI kernels by properly commenting / uncommenting a given device tree overlay, and blacklisting the driver modules you're not going to use. I say "supposedly" as I do not know from first hand experience, because I've been too busy building a system professionally( day job ).To make things simpler, I'd like to see Robert adjust the default to have remote-proc turned on and require UIO users alone to need to edit uEnv.txt.What would be great is if someone helped edit the examples in the am335x_pru_package to use remote-proc. Shouldn't be hard if mmap() is still used to do the live communications and remote-proc is mostly just replacing the loader.Robert has laid out the general procedure, and the given overlay files are commented well, in order to achieve the end goal of using pruss_uio, or remoteproc. However, knowing which file needs modification, and the rest can be hard to figure out if you're unaware of these changes.They are documented in /boot/uEnv.txt.
--Additionally, the less you know about Linux in general. The harder time you're going to have setting up either UIO, or remoteproc.The only time I ever saw a seg fault happen with the PRU example code. Was when I tried running the example code as a regular user. e.g. you need to run the examples with elevated permissions. Which means you must be the user root, or use sudo as a regular user.
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqpBaqCFk3UAVmRxbcE-8j0DkUtiaams5B6wD_ejAANvw%40mail.gmail.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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/28A1EDA6-E490-4FDB-BF9E-39C375CD4486%40gmail.com.
Jason,Is this a pure uEnv.txt edit only now ? Last I looked, you had to modify the the board overlay file. Or maybe it was one of the includes, I forget which.
On Wed, Mar 1, 2017 at 6:37 PM, Jason Kridner <jkri...@gmail.com> wrote:
I had the PRU's working with an 4.x kernel around 4-5 months ago. Basically I downloaded Jason's PRU github files, and got two of the examples working. Back then, you could only use the older UIO PRU source examples with the *bone* kernel, as TI's kernel was remoteproc only. Now days, supposedly it's possible to to use either with TI kernels by properly commenting / uncommenting a given device tree overlay, and blacklisting the driver modules you're not going to use. I say "supposedly" as I do not know from first hand experience, because I've been too busy building a system professionally( day job ).To make things simpler, I'd like to see Robert adjust the default to have remote-proc turned on and require UIO users alone to need to edit uEnv.txt.What would be great is if someone helped edit the examples in the am335x_pru_package to use remote-proc. Shouldn't be hard if mmap() is still used to do the live communications and remote-proc is mostly just replacing the loader.Robert has laid out the general procedure, and the given overlay files are commented well, in order to achieve the end goal of using pruss_uio, or remoteproc. However, knowing which file needs modification, and the rest can be hard to figure out if you're unaware of these changes.They are documented in /boot/uEnv.txt.
--Additionally, the less you know about Linux in general. The harder time you're going to have setting up either UIO, or remoteproc.The only time I ever saw a seg fault happen with the PRU example code. Was when I tried running the example code as a regular user. e.g. you need to run the examples with elevated permissions. Which means you must be the user root, or use sudo as a regular user.
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/CALHSORqpBaqCFk3UAVmRxbcE-8j0DkUtiaams5B6wD_ejAANvw%40mail.gmail.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...@googlegroups.com.
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhV1RvCXzDk%2B633EMM6tt%2BSjvjTBGBFX3%3DX6Rc7Mo6UoA%40mail.gmail.com.
Let's see who screams.Probably the same people as disabling root ssh access. ;-)
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiMWoLaOqKXDHji8VCCrPf2RboU0mTfWFSduhWS8Km2EA%40mail.gmail.com.
By the way, leaving root enabled via port 22 with no passwd, is an extremely bad idea. So may while those people will whine to no end about that "problem". Perhaps they should be made to understand the implications of leaving port 22 wide open to root access ?
The above is disabled by default as of 2-3 weeks ago..