Re: [beagleboard] UIO and Pruss

Robert Nelson told us that the uio pruss is not working on the kernel ti. If you want to have uio pruss you should use the bb kernel. https://github.com/RobertCNelson/bb-kernel It's because Texas is working on a new pruss driver. Le dim. 13 déc. 2015 11:37, Strawson a écrit

[beagleboard] Different Kernel Options

Hi All, Had a bit of a search around but can't see anything recent on this subject. I'm trying to understand the difference between all the Kernel options we have to us on the BBB. By this I specifically mean the options we have for 4.1 (at the moment). bone ti ti-rt omap2plus armv7 Any

Re: [beagleboard] UIO and Pruss

Sadly I'm running into the same missing uio directories now that I'm trying to get my beaglebone code that was stable on the 3.8 kernel and Wheezy image. My old compiled dtbo wouldn't load with a 4.1 kernel until it was recompiled. Even with it loaded, the following modules don't load: PRU,

[beagleboard] why does RCN's wiki page use am335x_evm_defconfig for BBB u-boot?

let's see if someone answers this before RCN :-) ... at robert's wiki page here: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot robert describes using u-boot's "am335x_evm_defconfig" as the basis for building u-boot for the BBB, even though u-boot has

Re: [beagleboard] UIO and Pruss

On 12/13/2015 4:37 AM, Strawson wrote: > Sadly I'm running into the same missing uio directories now that I'm trying > to get my beaglebone code that was stable on the 3.8 kernel and Wheezy > image. My old compiled dtbo wouldn't load with a 4.1 kernel until it was > recompiled. Even with it

Re: [beagleboard] UIO and Pruss

> > *With newer kernels, you need to use the standard Linux remote-proc* > * interface, rather than the legacy UIO driver.* Not exactly. Only if you're using the *TI kernels. The *bone kernels have uio_pruss enabled. william@beaglebone:~$ *uname -r* 4.1.12-bone-rt-r16 william@beaglebone:~$

Re: [beagleboard] UIO and Pruss

Well, bone is far behind the ti kernel. When I added remote-proc to the bone kernel, the patch was very large. With the ti kernel, most of the patches where already applied. Anyway, I did send Robert the bone patches, but he decided not to apply them. Regards, John > On Dec 13, 2015, at

Re: [beagleboard] UIO and Pruss

So, not to argue, but my point of view. I have no problem with people using remoteproc, *if* that's what they want to do. At the same time, I feel that it should not be "forced down our throats", because right now, it is not ready for prime time. uio_pruss is a known quantity, lots of people have

Re: [beagleboard] BBB I2C device driver for linux Error

Regards, John > On Dec 12, 2015, at 11:19 PM, d.sachine...@gmail.com wrote: > > Hi > > I bought a BBB for learning purpose and now I'm trying to write a device > driver for i2c from scratch just to learn. > > The problem I face is according to TRM for am335x I used i2c1 at address >

Re: [beagleboard] UIO and Pruss

We're not talking about the X15 in this post, and personally, I probably won't be using an X15 for a long, long time. Too much board, for too much money. On Sun, Dec 13, 2015 at 1:30 PM, John Syne wrote: > Remoteproc/RPMSG is a standard in mainline for interfacing ARM to

Re: [beagleboard] UIO and Pruss

Remoteproc/RPMSG is a standard in mainline for interfacing ARM to other processors on the same SOC. On the x15, this will be the only way you can interface to the DSP, M4’s, etc. Other vendors have adopted this solutions as well. Regards, John > On Dec 13, 2015, at 12:25 PM, William

Re: [beagleboard] UIO and Pruss

. . . And my god, what is this supposed to be ? C ? https://github.com/dinuxbg/pru-gcc-examples/blob/master/blinking-led/pru/resource_table_0.h#L43-L72 On Sun, Dec 13, 2015 at 5:22 PM, William Hermans wrote: > I actually think remoteproc / rpmsg is usefu for multi core

Re: [beagleboard] UIO and Pruss

By real world I mean a real world useful example. Not some BS spit 100 "hello" messages out into dmesg. On Sun, Dec 13, 2015 at 4:19 PM, William Hermans wrote: > OK, so show us a real world example of rpmsg. > > On Sun, Dec 13, 2015 at 3:53 PM, John Syne

Re: [beagleboard] UIO and Pruss

On Sun, Dec 13, 2015 at 5:19 PM, William Hermans wrote: > OK, so show us a real world example of rpmsg. > Some good ones here: https://github.com/dinuxbg/pru-gcc-examples all using binutils/gcc. ;) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options,

Re: [beagleboard] UIO and Pruss

I actually think remoteproc / rpmsg is usefu for multi core systems. Say a dual core ARM processor where one core is running Linux, and the other is running bare metal for deterministic purpose. I am however still unconvinced how it is useful when you have multiple cores on die that are not all

Re: [beagleboard] UIO and Pruss

Robert, By the way, there is only one remoteproc / rpmsg example there. The rest is either uio based, or completely non relevant( demonstrating some "new" gcc feature ). On Sun, Dec 13, 2015 at 5:33 PM, William Hermans wrote: > . . . And my god, what is this supposed to be ?

Re: [beagleboard] UIO and Pruss

OK, so show us a real world example of rpmsg. On Sun, Dec 13, 2015 at 3:53 PM, John Syne wrote: > OK, so maybe you can explain why you think there is a difference between > writing PRU firmware targeting PRUSS vs PRU firmware targeting remoteproc? > The only difference is

Re: [beagleboard] UIO and Pruss

How is that a BS example? The example shows an ARM kernel module sending a message to the PRU, which interrupts the PRU, which then copies the message from the PRU rx buffer to the PRU tx buffer, which then executes a callback on the ARM kernel module. You should be able to take that code and

Re: [beagleboard] UIO and Pruss

OK, so maybe you can explain why you think there is a difference between writing PRU firmware targeting PRUSS vs PRU firmware targeting remoteproc? The only difference is the API. You can build the firmware for each in the same way. The only reference to CCSV6 is the examples TI created for

Re: [beagleboard] why does RCN's wiki page use am335x_evm_defconfig for BBB u-boot?

On Sun, Dec 13, 2015 at 4:37 AM, Robert P. J. Day wrote: > > let's see if someone answers this before RCN :-) ... at robert's > wiki page here: > > https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot > > robert describes using u-boot's

Re: [beagleboard] UIO and Pruss

It's a BS example because it does not illustrate how remoteproc and rpmsg are useful. It also does not illustrate how to access the hardware modules through this technology. Here . . . Something useful -> https://github.com/boxysean/beaglebone-DMX Something else useful ->

[beagleboard] Re: SSH'ing to BeagleBone Black via usb gadget takes ages

Don't have an answer but I've been playing with a variety of BBB images thes past few days and on some the gadget works fine and others it doesn't. What I find most curious is the exact same SD card booted on my BBG works fine, but the gadget doesn't work when booted on my A5A BBB. A wired

Re: [beagleboard] UIO and Pruss

On Sun, 13 Dec 2015 17:22:43 -0700, you wrote: >I actually think remoteproc / rpmsg is usefu for multi core systems. Say a >dual core ARM processor where one core is running Linux, and the other is >running bare metal for deterministic purpose. I am however still >unconvinced how it is useful

Re: [beagleboard] UIO and Pruss

interesting. Looks like the latest beaglebone stable image (2015-11-12 jessie) has the "ti" kernel, not a "bone" kernel. This explains why so many things don't load for me. root@beaglebone:~# uname -r 4.1.12-ti-r29 root@beaglebone:/sys/class/uio# cat /etc/dogtag BeagleBoard.org Debian Image