<<THINK my next-steps are to learn how to build SDK RTOS DSP images with the <<resource table, and then load and debug via CCS. That's all documented in the SDK documents including how CCS put the cores in the correct state with gel files. That's the beauty of CCS /JTAG.
the same may need to be done using IPC in an actual Linux app I don't know. If I were you I would see if you can generate a simple DSP application in CCS of your own that actually works then make sure it still works having rproc load it. I'd be Leary of modifying these canned examples or building/ modifying a new DSP program in the SDK make file. It's possible something crucial isn't explained. Rapidly debugging in source level in CCS is orders of magnitude faster than all the hocus pocus your doing to get Linux to load DSP and using printf. That arm loading part can be done only once at end when DSP application is done. Interesting the x15 uses a beaglebone prompt in your screen captures of prompt it's actually a Beagleboard. Minor detail. And your original thread used an EVM prompt. That may confuse some You have a fan for board or is that just needed for the AI? That's nice that the bbx15 requires no mods for JTAG right? Connectors present I guess you bought a jtag for home use? Which one? Just anticipating questions users may ask trying to replicate the SDK DSP running on Debian and then wanting to follow in the footsteps of writing DSP apps -- 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/1273680453.437796.1613882237192%40mail.yahoo.com.
