Re: [beagleboard] Ti's RPMsg Examples Significantly Changed

> Also, would suggest looking at open-amp. There is ongoing work trying to > create a rpmsg framework for multiple platforms, i.2 imx6sx (ARM9/M4), > Zync/Xilinx > 1. able to create larger rpmsg sizes 2. baremetal library etc... -- For more options, visit http://beagleboard.org/discuss ---

Re: [beagleboard] uio_pruss on Mainline Linux

Maybe you should explain why you think this is worthless? > if the software is under going a redesign what are the changes? does this mean the documentation is now worthless due to the redesign? > remoteproc_pruss is getting "redesigned" again... ;( >> >> woow, here is new documentation from

Re: [beagleboard] uio_pruss on Mainline Linux

> > remoteproc_pruss is getting "redesigned" again... ;( > > woow, here is new documentation from TI and now its worthless? http://processors.wiki.ti.com/index.php/PRU-ICSS_Remoteproc_and_RPMsg -- For more options, visit http://beagleboard.org/discuss --- You received this message because yo

Re: [beagleboard] Re: BuildRoot with Nelson Build

I use the TI kernel because the PRU can be loaded using remoteproc and soon will have the virtio from user space. When running the following: git clone https://github.com/RobertCNelson/ti-linux-kernel-dev/ cd ti-linux-kernel-dev/ git checkout origin/ti-linux-3.14.y -b tmp ./build_kernel.sh (Thi

Re: [beagleboard] Re: BuildRoot with Nelson Build

e Kernel version to Local directory change path to. the full path to the ti kernel i.e /home/tcmichals/projects/copter/demo/ti-linux-kernel-dev/KERNEL Then change the configuration path to /home/tcmichals/projects/copter/demo/ti-linux-kernel-dev/patches/defconfig then save exit make (it is still buildin

[beagleboard] Re: BuildRoot with Nelson Build

On Monday, February 2, 2015 at 3:03:35 PM UTC-6, Satya wrote: > > In my scenario i would like to use Nelson Build with BuildRoot Filesystem. > > Followed the instruction to build kernel & Uboot along with MLO from > NELSON post: >https://eewiki.net/display/linuxonarm/BeagleBone+Black > >

[beagleboard] Re: How to reload PRU firmware 3.14.26 (TI)

> > OK.. > Modified pru1.c to include a resource table #include //#include #include "resource_table_1.h" volatile register uint32_t __R30; volatile register uint32_t __R31; ... add this to the cmd file .PRU0_CTRL> PRU0_CTRL, PAGE 1 .resource_table > PRUDMEM, PAGE 1 and it load

[beagleboard] Re: How to reload PRU firmware 3.14.26 (TI)

PRUDMEM, PAGE 1 .rodata> PRUDMEM, PAGE 1 .rofardata> PRUDMEM, PAGE 1 .farbss> PRUDMEM, PAGE 1 .fardata> PRUDMEM, PAGE 1 } On Wednesday, December 31, 2014 1:43:12 PM UTC-6, tcmichals wrote: > > I'm trying to force a reload of the PRU firm

[beagleboard] How to reload PRU firmware 3.14.26 (TI)

I'm trying to force a reload of the PRU firmware via file system, is there a way to force a reload from the file system? Guess will try and make it a module and do a modprobe FYI, remoteproc has some information on tracing for PRU Getting trace information from remoteproc mount debugfs mkdir /tm

Re: [beagleboard] Re: Yocto build error

This is for the beagleboard-xm -- 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+unsubscr.

[beagleboard] Yocto build error

| tar: --same-order option cannot be used with -c | Try 'tar --help' or 'tar --usage' for more information. | tar: This does not look like a tar archive | tar: Exiting with failure status due to previous errors | WARNING: /home/tcmichals/projects/demoBeagleBoard/yocto/beagle/tmp/work/

Re: [beagleboard] RobertCNelson Tree

> > > pru is enabled in the 3.14-ti tree: > > http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Capes > > Use bb.org_defconfig for the default config file? I guess this will be the kernel moving forward? I se

Re: [beagleboard] RobertCNelson Tree

> > > > PRU: > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/267588.html > > "capemgr": > Waiting for overlays/etc... > https://lkml.org/lkml/2014/7/23/756 > > PM: Beg/borrow/steal from: > http://git.ti.com/ti-linux-kernel/ti-linux-kernel/commits/ti-linux-3.12.y > http://g

Re: [beagleboard] RobertCNelson Tree

> > > > The three biggest subsystems missing on mainline are: > > PRU: > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/267588.html > > "capemgr": > Waiting for overlays/etc... > https://lkml.org/lkml/2014/7/23/756 > > PM: Beg/borrow/steal from: > http://git.ti.com/ti-linux