Yes the PRU is unique. This is both good and bad. Bad because using it locks you to Texas Instruments "forever" Good because the PRU bandwidth is very good because of the shared memory.
As for debugging. The STM32 has that, hardware breakpoint and all. The STM32 now has about 2/3 of the market which means that 33% of the time some other solution worked better. One good thing about thePi/STM32hybris of the TI's integrated PRUs is that if your requirements grow you are "stuck" if your software it tried to the Beagle Board. With Pi3/STM32 there is a LOT of room to grow. The Pi3canbe replaced with a Xeon-based server class machine and the STMline goes all the way to the M7. Also there as only two PRUs, if your project needs more pins you are again"stuck" but you can always add more STM32 and connect them all with I2C. I like the BBB. I own two of them. But only for a project that is never going to get big. On Sat, Mar 9, 2019 at 1:52 PM John Dammeyer <jo...@autoartisans.com> wrote: > > Hey Chris, > > AFAIK, the Pi has better HDMI support compared to the Beagle but then it was > designed more for multimedia. The Beagle PRUs have the advantage that they > have access to some of the Beagle Processor RAM. That gives them a bit of an > advantage over the PI/32 bit hybrid using SPI. > > > > Somepeople are using BeagalBone Black boards because the BBB has those > > PRUs. This is like the Pi/STM32 hybrid, logically identical. > > > > I did a project last year where I used a PIC32 as a Vehicle CAN bus monitor > collecting CAN packets, timestamping and logging GPS information during the > 20 seconds or so it took the Pi3 to boot. Once the PI was alive, an app > written initially in Python but then changed to C for speed, would gather and > file the messages chronologically for later forwarding up to a cloud > database. Someone else wrote that software. Our connection between the two > applications the files and pipes. > > In developing that project I chose the PIC32 over an STM32 because price of > the processor wasn't a consideration but having an ICD-3 In Circuit Debugging > tool was invaluable. I used the free PIC32 compiler and MPLAB IDE. > Development board that could hold MIKROE Click modules > https://www.mikroe.com/click > The CLICK boards made changing our minds really easy. > > > What's available for the STM32 that is equivalent to the In Circuit Debuggers > from Microchip? > > John Dammeyer > http://www.autoartisans.com > > > > > Chris Albertson > > Redondo Beach, California > > > > _______________________________________________ > > Emc-users mailing list > > Emc-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/emc-users > > > > _______________________________________________ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Chris Albertson Redondo Beach, California _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
