I found this in some documents I will post link to this document it covers IPC and the document Jeff referenced is part of this. Snippet
The IOMMU is programmed by the ARM based on the associated resource table. If you’re planning any memory changes then you’ll want to make a custom resource table as described in the wiki page IPC Resource customTable. http://software-dl.ti.com/processor-sdk-linux/esd/docs/04_03_00_05/linux/Foundational_Components.html#id127 While a good resource it's talking about older versions of CCS I'd recommend finding the equivalent doc from the latest SDK and follow the recommended version of CCS in that documents This document discusses Linux device driver's in detail as well I'd guess the Debian kernel has similar read me docs but don't know. This doc also shows a cookbook approach with screen captures on installing tools and even using CCS to debug the Linux kernel with GAB This is the level of detail I was used to seeing 10 year's ago for omap4. Unfortunately some links are broken and give messages this wiki has been taken down. That's scary. Updating documents of this detail has to be daunting and a huge task Examples are covered in detail about modifying from RTOS to bare metal to Linux I'd say there's enough info here to fill a summer of full time experiments while most users won't use all the details beginners should be quickly cognizant of the complexity of the AM72x One last negative this document mentions EVM and black and white bones. I've found a version of this document that was newer that said the x15 and AI was supported but judging by questions in E2E forum many have struggled that's no fault of TI this chip is amazing and very complex. All the cores with benchmark programs and examples are covered that's nothing short of amazing to document yet alone support. New Users must do their homework to succeed there no easy shortcut Sent from Yahoo Mail on Android On Sat, Feb 20, 2021 at 10:37 PM, 'Mark Lazarewicz' via BeagleBoard<[email protected]> wrote: <<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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/1273680453.437796.1613882237192%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/1167961571.438372.1613894830024%40mail.yahoo.com.
