That looks like old sdk infoIMO these PRU were added because there is little free RTOS support(I don't consider linux realtime) for this chip for the hobbyist hence you have these PRU(processors) that run bare bones programs loaded by the ARM and get something NOT bloated downwhich is what most hard realtime controllers can provide if you run barebones(the easiest way to calculate determinism) or run RTOS with interrupts(worst case timing required). In Avionics and other verified/certified environs you need determinism. I can tell you having worked in that industry no one runs linux the FCC cost to certify it would bankrupt you. I did work at one company that ran Integrity on the ARM used the DSP and the PRU unfortunately this costs big $$ here on this chip your SW support is this group 😊 and if your app end use fits well with linux user model its great. I see the PRU as a TI marketing to sell hard realtime users what you could get buying a non muticore processor and running it barebones. If you need all the features linux provides and some real time feature the PRU allows it. I will say they seem to have improved programming language and maybe even have jtag support for PRU. Not sure about c source level debugging. The PRU used to be programmed mistly in assembler. You have the arm dump the program and twiggle gpios to debug.Unless you have many years of experience calculating determinism is complex even on simple one chip solutions and the fact you ask a question like this after choosing a SoC and reading some old docs makes me realize typing this was a waste of time.Is this your college assignment run something determinism on Linux?
Sent from Yahoo Mail on Android On Tue, Jan 8, 2019 at 7:44 AM, daveyjohn...@gmail.com<daveyjohn...@gmail.com> wrote: Hi, I have read this nice ad for PRUs http://www.staroceans.org/documents/TI-sdk/spry264.pdf which states how deterministic the PRUs are, "each PRU has its own single-cycle I/O" etc. Then I wanted details... http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit "Content is no longer maintained and is being kept for reference only! " http://processors.wiki.ti.com/index.php/PRU-ICSS "Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only." http://processors.wiki.ti.com/index.php/PRU_Read_Latencies "The PRU write instruction is a fire-and-forget command that executes in ~1 cycle" that tilde... "The read latency values at the following links are considered "best-case," accounting for the 2 cycle instruction and interconnect introduced latency". best case.... Possibly, there is some doc which states min/max execution times? Deterministic or not? etc, etc. Not found. Just not found. ----------------------------------------------- I do not want to be pessimistic.... but neither I want to reverse-engineer these "deteministic" units, that do not really look that-deterministic. And that docs obsolete or missing??? What is it all about? -- 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/8976d66c-9bb4-40b9-aec9-b33874d42b99%40googlegroups.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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1050695667.16643106.1546986697430%40mail.yahoo.com. For more options, visit https://groups.google.com/d/optout.
