Hello Jeff Summary of Mark and Jeff Research This thread has validated DSP on am5728 x 15 platforms on everything but CCS which hasnt has been tested by us yet. Either board works to learn DSP.But EVM has support in E2E its their product they have to support it Beagleboard X15 DSP support IS this thread 😉 this is our humble attempt to help the community. Until we know more we want readers to understand the following.
#########START of AM57x DSP summary For DSP you need an EVM or x15 Beagle board as of right now. Readers can attempt to replicate our findings on BBAI but note jtag needs mods and we didn't test it. CCS/JTAG is optional but strongly suggested by myself. You need both SDKs at least right now(to build DSP example code and ARM IPC code.) Documents need to be read in proper order then questions will be supported You Jeff validated Debian on ARM using 2 programs that did ARM to DSP IPC supplied by SDK on Beagle board x15 hardware M4 IPC is documented in SDK as well it provides examples for EVM on SDK linux PRU IPC is documented in SDK same as above We dont see no reason why either m4 or IPU examples in sdk won't work on Debian x15. The SDK has detailed information to help new users and examples so it highly recommended but user can decide which Linux to run on ARM. Bone AI is untested and JTAG needs mod. It says SDK supports BBAI but CCS JTAG isn't discussed in detailed example code ########END DSP AM57x Summary Important please confirm your Beagle Board X15 version you used.??????We will support and guarantee DSP works time willing answe question as long as users read docs and this summary is my stance. We want user's to have confidence if they buy an x15 or EVM they will have a positive experience and be running DSP code quickly Feel free to add anything I'd prefer we keep the thread simple right? Your a positive fellow but maybe a disclaimer about x15 GPIO breakout should be mention or paste link to your current discussion I saw today as a reply TO use some famous words from a seasoned support person If new users can't follow this thread " I'm not sure I know how to support them🤣😃😂" In all seriousness everything is right here in this thread and the links . I forsee people asking as they always do the same questions without searching the forum for this thread title or rwzdung zero they should get referred here. Neither of has time to create a nice orderly step by step wiki the documents tell the story. I believe a good engineer learns by researching not demanding what is next step please. I see our goal is to help engineer's think out of box and get marketable skill and have fun doing it. We have no control over what gets fixed but we can help engineer's buying a platform know exactly what works for DSP and M4. It ain't really pretty but it's better than nothing and seeing the same questions repeated bi weekly is ridiculous. I better shut up before I cloud the summary and people miss it hidden in here.Or we can refine it at end of thread in a final post. Mark Sent from Yahoo Mail on Android On Sun, Feb 21, 2021 at 6:18 PM, [email protected]<[email protected]> wrote: Mark, When I downloaded TI Linux SDK and TI RTOS SDK, I downloaded CCS from the same listing of products from TI for 57xx. I ended up downloading CCS, 9.3. I'd love to get an AI and am waiting for updates on the JTAG fix as well.. Once they implement the JTAG fix, wonder how distributors will handle that if they still are stocking the older version prior to the fix?? On Sunday, February 21, 2021 at 5:52:12 PM UTC-5 lazarman wrote: I do have a question. Which version of CCS are you planning on using? Looks Great as you know I have no hardware I easily followed your initial post found the source code and traced what you were doing its all documented in the link you provided ie the IPC DSP doc your example runs from DDR using CCS and JTAG at least on the EVM and as binaries the way you did it but with no HW I cant replicate CCS success or your approach until Im confident Im buying a board that works out of box with CCS/JTAG EVM is cost prohibitive for probally everyone that asked about using DSP Im very confident it works on the EVM the BBAI is another story its not covered in the CCS example you ran just EVM the difference will be gel files and xml files needed by CCS adding a few more docs I think the biggest hurdle users face is the JTAG doesnt work without mods on the BBAI hopefully that gets fixed ASAP A few more important docs 2.1.3 OpenMP ModelOpenMP is an Application Programming Interface (API) for developingmulti-threaded applications in C/C++ or Fortran for shared-memory parallel (SMP)architectures. https://www.ti.com/lit/pdf/sprab27 - TMS320C6000 Optimizing Compiler v8.3.x User's Guide (Rev. C) https://www.ti.com/lit/pdf/sprui04 4.4.1. IPC User’s Guide 4.1. TI-RTOS Kernel — Processor SDK RTOS Documentation | | | | 4.1. TI-RTOS Kernel — Processor SDK RTOS Documentation | | | ESSENTIAL HOWTO FOR Building LINUX SDK on Linux Host and using CCS in linux 6. How to Guides — Processor SDK Linux Documentation | | | | 6. How to Guides — Processor SDK Linux Documentation | | | On Sunday, February 21, 2021, 04:02:11 PM CST, [email protected] <[email protected]> wrote: Thanks for cross referencing all the docs Mark! I'm sorry I missed this, but I stumbled upon an older GSOC project, libdsp-x15, which looks like it adds an FFT, IFFT, and biquad/sos functionality which are callable from a library added to Linux. Not sure if that's part of OpenCL.. https://github.com/henrix/libdsp-x15 On Sunday, February 21, 2021 at 2:46:31 PM UTC-5 lazarman wrote: First page here lists the boards supported by RTOS SDK Dev guide RTOS https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/rtos/index.html Dev Guide Linux https://software-dl.ti.com/processor-sdk-linux/esd/docs/06_03_00_106/linux/index.html quick start discusses jtag , CCS, bare metal and has 2 RTOS videos 3 jtag are supported make sure to research correct jtag connector is present on board you buy and works by googling https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/rtos/index_overview.html#emulator-support No gel file no fun make sure CCS has one for your board The support for connecting a JTAG to the EVM to debug software is included in the CCS package. In some cases, additional modifications to configuration GEL files are provided separately. To get the latest version, perform a CCS Check for Updates. Templates ie how to import samples into CCS https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/rtos/index_examples_demos.html Sent from Yahoo Mail on Android On Sun, Feb 21, 2021 at 2:13 AM, 'Mark Lazarewicz' via BeagleBoard<[email protected]> wrote: 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. -- 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/e965e272-d49d-4cd3-b37e-c1aef50da25bn%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/7b9b0d12-e704-4527-80e0-a33d1b0fb31dn%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/1796866633.478391.1613956473394%40mail.yahoo.com.
