Also I believe there was a default IPU image on the Debian BB-X15 image, which I overwrote in /lib firmware which remote proc also gave the same messages as above (didn't see complaints). I wonder what that stock IPU image does, where more info can be found and if it can be used as a starting point for what you all are wanting to do???
On Thursday, February 18, 2021 at 12:55:30 PM UTC-5 jeff....@gmail.com wrote: > Thanks Mark for your words of wizdom on here and in our email chats! You > helped me look for the linker command file for the DSP build. The linker is > allocating space for the resource table, but I don't see where the > server_dsp1 code is statically initializing the table in the RTOS SDK linux > build (DRA7XX_linux_elf build for ex02_message). I just need to make sure > that the DSP1 build's resource table is getting initialized and retry and > see if the remoteproc error goes away on the BB.ORG latest BB-X15 build > which I am loading all of the DSP/IPU images (built under TI SDK RTOS) onto. > > I did notice that the IPU code under the same example DOES appear to be > statically initializing it's resource table, so I thought I'd give loading > that a try with remoteproc on the latest Debian image for the BB-X15 by > deleting the exitsing IPU load on the Debian image, ln -s to it in > /lib/firmware, bind it, and look at the dmesg remoteproc traffic. I see > something interesting here and hopefully promissing!! Maybe a good > intermediate step would be to build the application side of the ex02 linux > application natively on the BB-X15 and see if it will pingpong the 14 > messages with IPU1 on the Debian build as shown on the TI IPC examples.. > > > This is just a baby step, but it maybe of interest to someone... > > Built the entire ex02_message example under TI SDK RTOS > > SCP'ed IPU1 build under example02 on TI SDK to the latest Debian BB-X15 > image on target. > > beagle:/lib/firmware ln -s /home/debian/ipc-starter/server_ipu1.xem4 > dra7-ipu1-fw.xem4 > > echo 58820000.ipu > unbind > 96 dmesg|grep remote > 97 echo 58820000.ipu > bind > 98 dmesg|grep remote > > > [16120.924223] remoteproc remoteproc0: stopped remote processor > 58820000.ipu > [16120.924561] remoteproc remoteproc0: releasing 58820000.ipu > [16140.961256] remoteproc remoteproc0: 58820000.ipu is available > [16140.969895] remoteproc remoteproc0: powering up 58820000.ipu > [16140.969921] remoteproc remoteproc0: Booting fw image dra7-ipu1-fw.xem4, > size 3984688 > [16140.989530] remoteproc remoteproc0: registered virtio0 (type 7) > [16140.989540] remoteproc remoteproc0: remote processor 58820000.ipu is > now up > > > Anyhow, lots more things to try!! If I'm able to root out configuration > errors that are obvious to me, I'll do so and post up here and on E2E (and > maybe other places) when I'm stuck.. > > Let me know if you have any advice or want me to try anything! > > Jeff > > > On Monday, February 15, 2021 at 2:23:34 PM UTC-5 lazarman wrote: > >> Hi Jeff its not easy to find and is confusing >> I have bought many boards and found out they did not do what I hoped >> I have an update BBAI is supported that is very good news the EVM is $600 >> Be aware that BBAI rev A1 I think needs a mod for JTAG >> >> Just to be clear I am not a linux expert so it appears all cores are >> supported and the Linux on Host ARM is SDK version it may night support all >> the bells Debian has for device drivers >> >> I have many years using DSP/BIOS and CCS and JTAG at board support level >> not Linux apps >> >> Theres a lot of tools here and RTOS and dual cores isnt something you >> pick up over night >> >> Pleny of good tutorials On learning TI RTOS using CCS and JTAG for a DSP >> application its really complex for a beginner and throw in MPUs and Cache >> and threads and 6 cores you really could spend a month learning tools alone >> >> In all fairness a single core AM35X is simpler the beauty is TI has gel >> scripts to handle all cores and load code internally until MPU is set up >> for quick and simple apps on ARM and fast learning and low cost the >> Debian/Beagle approach is probally better its pretty obvious I am RTOS fan >> (-: >> >> TI has world class tools and good documents >> >> I cant help anyone that insists on mixing the Debian on ARM with TI RTOS >> on DSP I'm not qualified it may be possible >> >> Looks like I was also wrong about omap l138 support for SDK the docs are >> confusing so maybe I buy a BBAI its cheaper than the EVM and play around I >> miss work I took care of mom 3 years she passed away October so I apologize >> at times Im grouchy >> >> Hopefully I helped someone that feels good as well Im excited reading >> these docs so maybe I make a come back!!! >> and find some work >> >> Regards >> >> The SDK includes a real-time multitasking kernel, FAT file system, >> network communications support, examples, and drivers. The exact content of >> the SDK depends on the capabilities of the device, but all devices share >> common APIs and build on existing proven software components to ensure >> reliability and quality. The software components are fully tested to ensure >> that they work together with TI’s Code Composer Studio integrated >> development environment. >> >> Supported Platforms >> >> <https://www.ti.com/tool/beagle-3p-bbone-ai> >> Platform Supported Devices Supported EVMs >> AM57x <https://www.ti.com/am57x> AM5728 >> <https://www.ti.com/product/am5728>, AM5726 >> <https://www.ti.com/product/am5726>, AM5729 >> <https://www.ti.com/product/am5729>, AM5718 >> <https://www.ti.com/product/am5718>, AM5716 >> <https://www.ti.com/product/am5716>, AM5708 >> <https://www.ti.com/product/am5708>, AM5706 >> <https://www.ti.com/product/am5706>, AM5748 >> <https://www.ti.com/product/am5748>, AM5746 >> <https://www.ti.com/product/am5746>, AM5749 >> <https://www.ti.com/product/am5749> AM572x EVM (TMDSEVM572X >> <https://www.ti.com/tool/TMDSEVM572X>), >> AM572x Industrial Development Kit (TMDXIDK5728 >> <https://www.ti.com/tool/TMDXIDK5728>), >> AM571x Industrial Development Kit (TMDXIDK5718 >> <https://www.ti.com/tool/TMDXIDK5718>), >> AM574x Industrial Development Kit (TMDSIDK574 >> <https://www.ti.com/tool/TMDSIDK574>), >> AM5729 Industrial Development Kit (TMDSIDK572 >> <https://www.ti.com/tool/TMDSIDK572>), >> Beaglebone AI <https://www.ti.com/tool/beagle-3p-bbone-ai> >> >> BeagleBone® AI AM5729 development board for embedded Artificial >> Intellig... >> >> <strong>What is BeagleBone® AI?</strong> <p>Built on the proven >> BeagleBoard.org® open source Linux approach, Bea... >> >> >> >> >> On Monday, February 15, 2021, 11:52:18 AM CST, Jeff Andich < >> jeff....@gmail.com> wrote: >> >> >> Thanks Mark for providing us all this! >> >> I tried starting to port one of the main examples from TI RTOS SDK into >> the latest Beagleboard-X15 images this weekend. Built the IPC example under >> the link you posted yesterday. Scp'd server_dsp1.xe66 to the SD card and >> then linked to it, and attempted to load. >> >> It looks like it started to load but then complained that the resource >> table is not found. I have lots more homework to do.. >> >> My plan dejour is to try to see how far I can get with that example on BB >> Debian and TI SDK Linux. >> >> I do plan to develop the DSP application with CCS and JTAG, and deploy it >> using remoteproc from Linux once it's debugged. >> >> Don't know if there are currently any Linux tools for debugging the other >> cores. >> >> But at this point I'm not sure where this will all lead.. >> >> But it sounds like there's an appetite within the Beagle community to get >> this tested and working... My guess is the more applications that can >> access the other processors on the SOC, the merrier for BB.org and TI.. >> >> On Mon, Feb 15, 2021, 12:34 PM Mark Lazarewicz <laza...@yahoo.com> wrote: >> >> Looks like good examples here .I also saw M4 example on github. >> >> Dont see any documents on using Debian Linux and DSP Why? >> and wonder if that OS will supply tools to get the DSP executable >> transferred in correct format >> Cant even imagine debugging this with printf LOL and no jtag >> The DSP has to be taken out of rest when running linux >> >> >> >> Its documented here below why in the world someone would not use CCS and >> JTAG? and expect to run IPC on 6 core chip with no documents is beyond me. >> Any commercial customer would never accept being stonewalled by a vendor >> >> Perhaps Debain/Beagle is for hobbyists only I dont know >> >> And for Dimtry GCC is supported >> >> >> 10.1. Target — Processor SDK RTOS Documentation >> <https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/rtos/index_how_to_guides.html> >> >> 10.1. Target — Processor SDK RTOS Documentation >> >> >> <https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/rtos/index_how_to_guides.html> >> >> >> >> >> >> The following examples demonstrate some of the rudimentary IPC >> capabilities. They are mostly two processors examples. These examples may >> be built for any two processors on your device, but only for two at a time. >> An IPC Ping example using three processors is also presented at the end. >> >> >> Why? >> >> >> >> On Monday, February 15, 2021, 09:41:20 AM CST, 'Mark Lazarewicz' via >> BeagleBoard <beagl...@googlegroups.com> wrote: >> >> >> OpenVX,cmem,PRU and remote proc support today >> >> >> https://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/index.html >> >> >> >> Sent from Yahoo Mail on Android >> <https://overview.mail.yahoo.com/mobile/?.src=Android> >> >> On Tue, Feb 9, 2021 at 8:14 AM, jeff....@gmail.com >> <jeff....@gmail.com> wrote: >> I think I have a similar question in that I'm hoping to develop an >> application (as much of a software defined radio application as I can cram >> into this platform) which utilizes the C66 DSP's on the BB-X15. I'm trying >> to converge on a process for developing a TI RTOS application for the C66's >> on the BB-X15 which is compatible with the BB Debian distro running on the >> A15's. More on this later, hopefully. >> >> I imagine you've already stumbled upon the following, but it seems like a >> good starting point. >> >> https://e2e.ti.com/support/processors/f/791/t/765821. >> >> Also google all of the examples on of PRU applications . My guess is >> that may also shed some light on how to develop and debug code for the >> other processors on the Sitara SOC of interest. >> >> I just received a USB100V2 JTAG cable, and I hope to start hacking on >> this on my BB-X15 in my spare time. I have a lot of questions on how this >> works, and I will post up when I think I have something worthwhile or >> relevant.. >> >> Also, please post up as you make progress as I imagine there are others >> wanting guidance on developing applications on the other processors on the >> SOC and interfacing Linux to them. There's not a lot of postings on the >> C66 or M4.. >> >> >> >> >> >> On Wednesday, February 3, 2021 at 8:21:36 AM UTC-5 databac...@gmail.com >> wrote: >> >> >> Hi >> I and another student have been tasked with exploring ways to develop for >> the M4 processor using BBAI. We've had difficulty finding a good debug >> setup, preferably one where you could step through instructions in the M4 >> processors. >> >> Could anyone point us towards whats worth looking in to? >> >> Regards, Fredrik Eriksson >> >> -- >> 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...@googlegroups.com. >> To view this discussion on the web visit >> >> https://groups.google.com/d/msgid/beagleboard/024abb86-4ada-4b24-b801-5119a941796en%40googlegroups.com >> >> <https://groups.google.com/d/msgid/beagleboard/024abb86-4ada-4b24-b801-5119a941796en%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> 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...@googlegroups.com. >> To view this discussion on the web visit >> >> https://groups.google.com/d/msgid/beagleboard/1775160073.1490894.1613403668325%40mail.yahoo.com >> >> <https://groups.google.com/d/msgid/beagleboard/1775160073.1490894.1613403668325%40mail.yahoo.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> 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...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/CALJg6gScvvTT_vnBaOR552OHpTgArJWA8kY%3D_W6nc1Ogh_gDLA%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/beagleboard/CALJg6gScvvTT_vnBaOR552OHpTgArJWA8kY%3D_W6nc1Ogh_gDLA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/92d25abd-e60c-4b59-bed9-04dc76ad6767n%40googlegroups.com.
