[beagleboard] Want to PRU binary using prussdrv_exec_program - Can't seem to get .bin file loading on PRU
Hi,
Wondering if anyone can help. I had the Remote Proc/RpMsg working passing
data to and fro. However I liked the functionality of uio_pruss so I have
updated my kernel to 4.4.20-ti-r44 following advice from some of the guys
on the board. Thanks to all who responded last time, uio_pruss is what I
need.
So I have rebuilt my device tree to include am33xx-pruss-io.dtsi. and
installed under the kernel directory in /boot/dtbs. I reboot and when I run
lsmod I can see the three uio kernel objects. I am sure it is using the
rebuilt device tree because I turned off the heartbeat on the USR0 led as a
test in the am335x-common.dtsi. It isn't toggling anymore.
I have built an example PRU program, PRU_LED0. I have setup the hex utility
to run the following cmd file
--b
--image
ROMS {
PAGE 0:
.text: o = 0x0, l = 0x2000, files={text.bin}
PAGE 1:
.data: o = 0x0, l = 0x2000, files={data.bin}
}
I have an error, if I use this it complains 'not enough files for ".text"
and ".data". So I removed the files command to make it like what I built
for Remotew Proc/RpMsg and it builds a _image.obj. Trouble is that it is
the test and data combined. The rp_proc loader I think can split the file
and load text and data. However I can't see a way to split them for using
with uio_pruss which calls prussdrv_exec_program and
prussdrv_load_datafile.
Is there a utility or macro I could use to find the data and text portions
of the image obj and split them ?
I am pretty sure this is the problem. I took portions of the
prussdrv_exec_program function into my programm to see where the calls
fails. I seem to be able to run prussdrv_pru_disable. It is failing at
prussdrv_pru_write_memory, just before it calls prussdrv_pru_enable_at to
run the code.
Fustrating... I am sure I am missing something obvious.
Cheers,
Paul
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/535e7b33-8cfc-4180-8a51-ab594e32a00b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Enable can0, can1, adc and spi0 with dtb-rebuilder (Debian Jessy 8.4, 4.4.9-ti-r25)
Andre,
I'm using the same BeagleBone image, but I've been unable to get the
BeagleBone to boot after I followed your step-by-step instructions. Do you
know if anything has changed in the dtb-rebuilder since you were successful
in enabling can0?
Thanks,
Jay
On Monday, May 30, 2016 at 7:31:56 AM UTC-4, Andre Wippich wrote:
>
> CAN is running now :-)
>
> There were two errors:
>
> 1) I didn't know that I have to add
>
> dtb=am335x-boneblack-custom.dtb
>
> to the /boot/uEnv.txt
>
> 2) In line 43 of
>
> src/arm/am335x-bone-pinmux-spi0.dtsi
>
> stands " {" instead of " {"
>
> CAN and ADC are fine now. I've a little trouble with SPI, but this could
> be my software.
>
>
>
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/422ed0e0-424a-4d5d-b55e-fed1687cd549%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: Remote Proc and examples to fill PRU data memory, store/read data in PRU shared memory
Hi, Thanks for the link , updated kernel to latest , 4.4.20-ti-r44. Followed the instructions and the uio kernel objects are loaded. Just working through examples now. It will be easier to use uio for my application. Cheers, Paul On Tuesday, September 13, 2016 at 3:25:37 PM UTC+1, paulandre...@gmail.com wrote: > > Hi, > I am investigating the beagleboard black PRUs at the moment for data > acquisition and/or transmission. For context I'll explain what I want to > do. I want to use a 16 bit ADC/DAC at 100KSps. It is a half duplex system, > so I can use both PRUs to receive, then load new firmware and transmit. > Starting the transmission must be to 1 us accuracy. Hopefully that will > explain what I am trying to do. > > I am using the PRU Software package 4.0.2. My kernel is Linux Beaglebone > 4.4.9-ti-r25. I have the CCSv6 environment setup and I can build and run > examples on the PRU, and I have built a user space example (Pru Lab 6 user > space) and it is working fine sending strings to and from both PRUs using > RpMsg. Great so far > > I would like to extend the User space example to allow me to fill PRU > memory (basically Sine wave sample data to use as a carrier for modulation) > , or write directly from user space any samples I want to transmit. Also > any examples in user space using the pruss_intc.ko to send/receive > interrupts from the PRUs would be good. > > The data I want to fill into the PRU will fill most of the data memory in > the PRU, I don't want to have to load it up piece by piece through RpMsg, > which looks to be maximum 512 bytes per transfer. I am hoping to trigger > commands through RpMsg for the PRU to read/write data to shared or ARM DDR > memory. There are plenty of examples on the PRU side to read/write to > shared or DRR memory, so i should be able to plod through the examples to > create my code for the PRU. > > However I can't see any example on the ARM side. Is it possible for a user > space program to read/write to shared memory ? Or allocate a section of DDR > memory for the each PRU to write to that nothing else will touch ? > > Also once the ARM is through with writing to shared or DRR memory the PRU > generate a ARM Host interrupt (EVOUT1 to EVOUT7). Does pruss_intc.kp map > these interrupts to user space, or allow a callback to be added ? > > I know a lot of questions, apologies if they are basic, new to this. > > Regards, > Paul > -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9c3cebfc-9e27-4c2c-9813-8e5d64e02337%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: how to copy sd card kernel image into emmc memory of beaglebone black by uisng windows os?
it means that its not possible to copy kernel image from sd card to EMMC memory. On Friday, September 16, 2016 at 12:43:58 PM UTC+5:30, sven.n...@gmail.com wrote: > > As far as I remember, kernel is not located on a Windows-readable > filesystem. Its easy enough to copy kernel when running Linux though. > You must also copy modules directory (in /lib/modules) for the kernel you > want to boot normally. > And maybe change some uEnv variables. > /Sven > > > Den fredag 16 september 2016 kl. 07:19:52 UTC+2 skrev kara...@yahoo.com: >> >> how to copy sd card kernel image into emmc memory of beaglebone black by >> uisng windows os? >> > -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/f23fac48-007d-4c16-949a-749cbd93976f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: how to copy sd card kernel image into emmc memory of beaglebone black by uisng windows os?
As far as I remember, kernel is not located on a Windows-readable filesystem. Its easy enough to copy kernel when running Linux though. You must also copy modules directory (in /lib/modules) for the kernel you want to boot normally. And maybe change some uEnv variables. /Sven Den fredag 16 september 2016 kl. 07:19:52 UTC+2 skrev kara...@yahoo.com: > > how to copy sd card kernel image into emmc memory of beaglebone black by > uisng windows os? > -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/91a0fce9-37d1-4f03-8b6d-1b54a8d29ff6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
