Nevermind I understand I think now .PRU0_DRAM needs to be an address from linker command file that statement might work. Anyway linker command files have always been a murky science I might play around with. I use JTAG so the address being not correct is something you can catch quickly. Unfortunately Using RPMsg from my recent research isn't a good match with JTAG debugging.
I'm interested in what memory the Rpmsg carves out for it's use. Seems like between the PRU shared RAM and unused PRU0_DRAM if using only one PRU one can squeeze additional RAM if resources are tight that's why I'm interested in researching the linker command files further. These PRU are limited in resources it's like using a small 8 bit processor from 20 year's ago and squeezing every possible byte out. Back in the day some guys got job security by using so many tricks to steal memory their code was unmaintainable. They liked that boss couldn't get rid of them because changing the software would break the entire application. Ahh I digress . Mark Sent from Yahoo Mail on Android On Thu, May 13, 2021 at 7:11 PM, 'Mark Lazarewicz' via BeagleBoard<[email protected]> wrote: Hi Kasimir What's wrong with below?? My datastructure was not in internal ram.volatile Event_t *event_knoten = (Event_t *) (PRU0_DRAM + 0x200); IMO I think placing anything in a guaranteed memory area is best done with sections from linker command file. There's examples about placing data in PRU shared RAM in the those examples I mentioned. Yes external DDRAM yikes 🤟 the ARM is caching it. Glad you're rolling. Sent from Yahoo Mail on Android On Thu, May 13, 2021 at 6:26 PM, Kasimir<[email protected]> wrote: Hi Mark,more simple ...... in C source.My datastructure was not in internal ram.volatile Event_t *event_knoten = (Event_t *) (PRU0_DRAM + 0x200);and in main event_knoten = (Event_t *)malloc(100*sizeof(Event_t)); solved it. Kasimir -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/85feaea6-6059-4f9d-ba44-5bd44ea57f11n%40googlegroups.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/484390211.240541.1620951078816%40mail.yahoo.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/684080029.241326.1620952826607%40mail.yahoo.com.
