Hi Fischer what I meant to say is the AM57xx is definitely more complicated as there's more cores and that will definitely break quickly without correctly modifying the table for the DSP or M4. There's absolutely no docs beyond the SDK and many people are not using SDK they use the Debian build wiki so I think that's a weak point in getting users to use x15 or AI. Here's the link for thae AM57x Linux IPC If you dig around in this document you see some messages being displayed for normal loads and rpmsg and it discusses changing resource table. Also look at the details involved in getting complicated examples working in CCS. Again the Am35 build may be set up to handle most PRU examples and while I could envision debugging it's PRUs with printf I can't imagine trying complex DSP or a M4 without CCS and JTAG to debug for exactly the reasons you point out the documents are scarce. Buts just me. Here's the 57x document as you can see in it the DSP and M4 have MMU on the interconnect between the ARM Host. http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_IPC.html#ipc-for-am57xx
If anything this overview should give you more confidence deciphering what your original question was and still remains. My understanding is hazy but the carvout and increasing of any shared memory sizes is where you need to change this table and I've seen no other documents discuss this for. I suspect the existing working PRU on Am35x examples are very simple in nature as you said in last post simple demos work. You mentioned using interrupts that's probably a faster way to get Data to the Host. To me what good is a determistic fast IO processor if the Data needs to be acted on quickly as in a hard realtime control theory loop.The other cores the DSP and M4 have edma also on the interconnect not sure about PRU. It's all described in the document below. Your simple example comment bthat's what caught my eye I think your right 🤔. Most people use the PRU for dedicated offloading I doubt many use every function available for IO like a normal processor application I might be wrong but I do know the DSP and M4 share many peripheral with the ARM so full blown applications on those cores can and will be designed eventually.I know this as I have seen product that's in field doing so. How those engineer's deciphering questions like yours I don't know I suspect they had dedicated engineer's at TI assigned to the company as they were buying large quantities of chips then and in the past. With open source it's kind of like the book I'm reading about Google and Stanford students. The professor assigns summer projects to their PHD candidate's 🤪🤭 and in the case of the Google Co-founders they crashed the University computer and we're nicely ask to leave the campus but told they could come back anytime if Google didn't work out.And they paid the tuition. Sorry for detour there but I think this is were Google's Summer projects are inspired from Stanford. Keep us updated if you find more details Mark Sent from Yahoo Mail on Android On Tue, Mar 2, 2021 at 5:09 AM, Fisher Grubb<[email protected]> wrote: Hi Mark, Thanks for your reply, yes, I've not seen a lot posted about remoteProc when I searched, and I know it has to be an important issue due to at least PRU interest being almost totally based on it. Even with JTAG and directly programming your code into the PRUs, Linux still has to receive the interrupts.Plus, as you mentioned, more chips are multi-architecture. We're spoilt for choice with dual core M4 and C6000 DSP in the AI, and they need to be used properly to take advantage of this chip.I think too many people likely use it like a Raspberry Pi which defeats the point, as the Pi is multi-core Cortex A just for Linux, while the BeagleBone AI and Black have less Linux CPU power, but excel in using the PRUs and M3/M4 etc. Thanks a lot for the documentation link, I've only more recently returned to programming, so have had to refresh myself in not just C and C++, but also micro controller architecture and compile options with Makefiles. Ya, I'll look over the documentation you sent a little later, thankfully that documentation framework exists, as documentation is the last thing programmers want to do. I'm currently sorting out the IEP timer use so a simple real-time scheduler can run using it. It will run state-machines. I'll document all I've done in the end, my supervisor should want to go through and replicate what I've done to confirm the steps are correct, and then people will have more of a guide. Fisher On Tuesday, 2 March 2021 at 10:48:04 UTC+10 lazarman wrote: Hello Fischer This file looks like it's processing the resource table https://docs.huihoo.com/doxygen/linux/kernel/3.7/remoteproc__core_8c_source.html * 804 * take a firmware and boot a remote processor with it. 805 */ 806 static int rproc_fw_boot(struct rproc *rproc, const struct firmware *fw) 807 { I'm no kernel internals guy but I'm pretty sure dev_info below in a working load gets displayed look at the output in Linux to DSP IPC SDK documents. Have you seen it? It's helped me if you have not let me know it also discussed M3 I know you are doing OUR 817 dev_info(dev, "Booting fw image %s, size %zd\n", name, fw->size); Perhaps what you need is to recompile kernel with debug level for appropriate driver verbose mode.I'm sure it's possible but I'm not the right guy maybe it's a defconfigoption. You'd want to make sure dev_dbg below spits out useful info is my guess If unable to actually talk to somebody who writes code like this us mere mortals are left to study the source code. I been there I feel your pain. Have you located the file Din pointed to and the corresponding c files ??? 701 /* make sure table isn't truncated */ 702 if (avail < 0) { 703 dev_err(dev, "rsc table is truncated\n"); 704 return -EINVAL; 705 } 706 707 dev_dbg(dev, "rsc: type %d\n", hdr->type); 708 709 I remember that IPC document also talking about disabling interrupts in an example as well. And lastly I've got the sneaky feeling that this whole remoteoroc falls apart rather quickly when the DSP, M3 or PRU examples get complex.My interest is DSP I need more modern HW or I'd be in there with you deciphering what it takes to use complex example on the DSP only my interest is using JTAG. That L3 message looks like the ones the kernel spits out processing the image but again Im not a Linux guy. Also that IPC DSP doc lists addresses for all the cores you should be able to find At Address: 0x00806664 [ 2393.327706] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 370028[ 2393.327762] ------------[ cut here ]------------[ 2393.327782] WARNING: CPU: 0 PID: 1810 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x368/0x3a4[ 2393.327790] 44000000.ocp:L3 Standard Error: MASTER PRUSS2 PRU1 TARGET PCIE1 (Read): At Address: 0x00806664 : Data Access in Supervisor mode during Functional access Keep us posted I'm interested if you find more data I think we will be seeing many more questions about remoteproc once people start running DSP and M4 code especially about resource tables 😉 Mark Sent from Yahoo Mail on Android On Sun, Feb 28, 2021 at 11:46 PM, Fisher Grubb<[email protected]> wrote: Hi all, I solved my issue in the end of it not booting, or causing errors with "L3_main" in the title from remoteProc to dmesg. The issue turned out to be both having interrupts from the IEP timer, and that C++ needs .init_array in the linker command file to actually initialise the constructors.The linker did add the .init_array section at the end of the binary, but I don't think actually got the code to jump to the needed addresses without that section specifically put into the linker file. I assume the interrupt issue may be been due to using an empty resource_table, so the kernel module didn't set anything up to receive them on the Linux side, but then the timer sent them.I'm not fully sure about that because I believe I've also left them enabled, and not had dmesg errors. I still can't find any RemoteProc documentation of the possible config options, or how to get extra info out of the kernel modules, such as what it's doing as it processes the resource_table. Fisher On Friday, 12 February 2021 at 02:29:00 UTC+10 [email protected] wrote: The error message is emitted from the system bus driver (drivers/bus/omap_l3_noc.c ). I interpret it as a bug in your PRU firmware. When issue occurs, please try to inspect the PRU state. See https://zeekhuge.me/post/ptp_docs_commands_and_tools/ , or use JTAG. Regards,DimitarOn Thursday, February 11, 2021 at 7:30:58 AM UTC+2 Fisher Grubb wrote: Hi Dimitar, Thanks for your reply, yes, I don't understand that as its code to flash lights. Its built with different states, which makes it more complicated, but only flashes LEDs. How can I know what the kernel module is doing so I can see more details and know where to look? Such as, is this happening when the firmware is being processed by the module, or is this the module giving the error once the code is trying to run on the PRU? Thanks,Fisher On Thursday, 11 February 2021 at 02:58:57 UTC+10 [email protected] wrote: Looks like PRU attempts to access PCIE1 address space. I suspect it's a bug in your PRU firmware. MASTER PRUSS2 PRU1 TARGET PCIE1 (Read): At Address: 0x00806664 TI has tutorials how to use JTAG to debug PRU. Another option is https://markayoder.github.io/PRUCookbook/04debug/debug.html Regards,Dimitar On Wednesday, February 10, 2021 at 2:27:01 PM UTC+2 Fisher Grubb wrote: Hi all, I've done a few searches and couldn't find any threads or "conversations" in this forum/group on the remoteproc kernel module for loading firmware onto the PRUs. The remoteproc framework is supposed to be a Linux standard, there are some generic documents for it, but I've only found a general diagram and explanation in TIs SDK docs for their implementation. Simple code to flash LEDs loads and runs fine, but larger, more complicated code that also just flashes LEDs fails to load, occasionally parts of it run, or none of it runs and the there's a bit of a stack trace in dmesg. The first line of the error in dmesg is:44000000.ocp:L3 Standard Error: MASTER PRUSS2 PRU1 TARGET PCIE1 (Read): At Address: 0x00806664 : Data Access in Supervisor mode during Functional access Is this resource_table related? Or its meaning that there's a strange memory access? I'm trying to find out: - How to get verbose info that shows what the pru_rproc kernel module is doing - How to configure it, maybe commandline, or through the sysfs - Documentation of how it functions, and what it expects, such as the resource_table and firmware layout to match, how it handles errors etc. Thanks,Fisher Here's my dmesg: [ 76.711182] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready[ 76.736257] IPv6: ADDRCONF(NETDEV_CHANGE): usb1: link becomes ready[ 77.894970] NOHZ: local_softirq_pending 08[ 77.903344] NOHZ: local_softirq_pending 08[ 77.923339] NOHZ: local_softirq_pending 08[ 77.967346] NOHZ: local_softirq_pending 08[ 77.977416] NOHZ: local_softirq_pending 08[ 78.009731] NOHZ: local_softirq_pending 08[ 78.227509] NOHZ: local_softirq_pending 08[ 78.414768] NOHZ: local_softirq_pending 08[ 78.478154] NOHZ: local_softirq_pending 08[ 78.483369] NOHZ: local_softirq_pending 08[ 139.787136] remoteproc remoteproc6: powering up 4b2b4000.pru[ 139.792152] remoteproc remoteproc6: Booting fw image PRU-LEDs.out, size 32644[ 139.792176] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 152.475360] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 207.719337] pru-rproc 4b2b4000.pru: can't provide a NULL firmware[ 234.455246] remoteproc remoteproc6: powering up 4b2b4000.pru[ 234.455834] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 369696[ 234.455878] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 241.915304] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 254.522378] remoteproc remoteproc6: powering up 4b2b4000.pru[ 254.522557] remoteproc remoteproc6: Booting fw image PRU-LEDs.out, size 32644[ 254.522577] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 257.559216] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 375.451166] remoteproc remoteproc6: powering up 4b2b4000.pru[ 375.451886] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 369696[ 375.451931] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 380.203249] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 387.895263] remoteproc remoteproc6: powering up 4b2b4000.pru[ 387.895392] remoteproc remoteproc6: Booting fw image PRU-LEDs.out, size 32644[ 387.895411] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 390.959144] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 407.879207] remoteproc remoteproc6: powering up 4b2b4000.pru[ 407.879755] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 369696[ 407.879800] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 425.139157] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 628.915190] remoteproc remoteproc6: powering up 4b2b4000.pru[ 628.915736] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 369876[ 628.915780] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 840.639171] pru-rproc 4b2b4000.pru: can't change firmware while running[ 845.259199] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 852.903126] remoteproc remoteproc6: powering up 4b2b4000.pru[ 852.903663] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 370028[ 852.903716] ------------[ cut here ]------------[ 852.903735] WARNING: CPU: 0 PID: 1810 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x368/0x3a4[ 852.903744] 44000000.ocp:L3 Standard Error: MASTER PRUSS2 PRU1 TARGET PCIE1 (Read): At Address: 0x00806664 : Data Access in Supervisor mode during Functional access[ 852.903750] Modules linked in: rpmsg_rpc rpmsg_proto pru_rproc pruss_intc bnep pruss pvrsrvkm(O) pruss_soc_bus ti_vpe ti_sc videobuf2_dma_contig ti_csc ti_vpdma v4l2_mem2mem v4l2_common videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btsdio bluetooth joydev ecdh_generic brcmfmac stmpe_adc brcmutil cfg80211 omap_remoteproc virtio_rpmsg_bus rpmsg_core usb_f_ncm usb_f_mass_storage usb_f_rndis u_ether libcomposite uio_pdrv_genirq uio cmemk(O)[ 852.903951] CPU: 0 PID: 1810 Comm: bash Tainted: G W O 4.14.108-ti-r137 #1buster[ 852.903958] Hardware name: Generic DRA74X (Flattened Device Tree)[ 852.903979] [<c0112de8>] (unwind_backtrace) from [<c010d6a8>] (show_stack+0x20/0x24)[ 852.903994] [<c010d6a8>] (show_stack) from [<c0cb2ea4>] (dump_stack+0x80/0x94)[ 852.904007] [<c0cb2ea4>] (dump_stack) from [<c013fbb8>] (__warn+0xec/0x114)[ 852.904019] [<c013fbb8>] (__warn) from [<c013fc38>] (warn_slowpath_fmt+0x58/0x74)[ 852.904032] [<c013fc38>] (warn_slowpath_fmt) from [<c0736718>] (l3_interrupt_handler+0x368/0x3a4)[ 852.904048] [<c0736718>] (l3_interrupt_handler) from [<c01ac04c>] (__handle_irq_event_percpu+0x84/0x2d0)[ 852.904061] [<c01ac04c>] (__handle_irq_event_percpu) from [<c01ac2d4>] (handle_irq_event_percpu+0x3c/0x90)[ 852.904072] [<c01ac2d4>] (handle_irq_event_percpu) from [<c01ac370>] (handle_irq_event+0x48/0x6c)[ 852.904085] [<c01ac370>] (handle_irq_event) from [<c01b030c>] (handle_fasteoi_irq+0xd0/0x178)[ 852.904098] [<c01b030c>] (handle_fasteoi_irq) from [<c01ab15c>] (generic_handle_irq+0x34/0x44)[ 852.904109] [<c01ab15c>] (generic_handle_irq) from [<c01ab76c>] (__handle_domain_irq+0x8c/0xfc)[ 852.904121] [<c01ab76c>] (__handle_domain_irq) from [<c01015bc>] (gic_handle_irq+0x4c/0x88)[ 852.904133] [<c01015bc>] (gic_handle_irq) from [<c0ccef4c>] (__irq_svc+0x6c/0xa8)[ 852.904140] Exception stack(0xce9bbc20 to 0xce9bbc68)[ 852.904151] bc20: c104179c ce9bbcac 00000053 c104179f ce9bbcac c104179c ce9bbd0c d3761420[ 852.904162] bc40: c108c08c ce9bbdac ce9bbcac ce9bbc8c ce9bbc90 ce9bbc70 c0cc6b40 c0cc2d90[ 852.904169] bc60: 20010013 ffffffff[ 852.904182] [<c0ccef4c>] (__irq_svc) from [<c0cc2d90>] (format_decode+0x5c/0x5e8)[ 852.904194] [<c0cc2d90>] (format_decode) from [<c0cc6b40>] (vsnprintf+0x84/0x3f4)[ 852.904206] [<c0cc6b40>] (vsnprintf) from [<c0cc6f34>] (snprintf+0x38/0x54)[ 852.904221] [<c0cc6f34>] (snprintf) from [<c08891f0>] (dev_vprintk_emit+0x64/0x210)[ 852.904235] [<c08891f0>] (dev_vprintk_emit) from [<c08893dc>] (dev_printk_emit+0x40/0x5c)[ 852.904248] [<c08893dc>] (dev_printk_emit) from [<c088949c>] (__dev_printk+0x58/0x98)[ 852.904260] [<c088949c>] (__dev_printk) from [<c08898ac>] (_dev_info+0x58/0x74)[ 852.904276] [<c08898ac>] (_dev_info) from [<c0a800d8>] (rproc_boot+0x574/0x634)[ 852.904291] [<c0a800d8>] (rproc_boot) from [<c0a80ea8>] (state_store+0x80/0x144)[ 852.904305] [<c0a80ea8>] (state_store) from [<c0887ca8>] (dev_attr_store+0x28/0x34)[ 852.904319] [<c0887ca8>] (dev_attr_store) from [<c038637c>] (sysfs_kf_write+0x48/0x54)[ 852.904332] [<c038637c>] (sysfs_kf_write) from [<c03859d0>] (kernfs_fop_write+0xf8/0x1dc)[ 852.904346] [<c03859d0>] (kernfs_fop_write) from [<c02fae18>] (__vfs_write+0x28/0x48)[ 852.904360] [<c02fae18>] (__vfs_write) from [<c02fb020>] (vfs_write+0xb4/0x1c8)[ 852.904372] [<c02fb020>] (vfs_write) from [<c02fb2a0>] (SyS_write+0x5c/0xbc)[ 852.904386] [<c02fb2a0>] (SyS_write) from [<c0109000>] (ret_fast_syscall+0x0/0x54)[ 852.904393] ---[ end trace 0de72da1c33b76f4 ]---[ 852.904407] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 866.703170] pru-rproc 4b2b4000.pru: can't change firmware while running[ 869.891225] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 876.519176] remoteproc remoteproc6: powering up 4b2b4000.pru[ 876.519299] remoteproc remoteproc6: Booting fw image PRU-LEDs.out, size 32644[ 876.519318] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 879.759196] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 889.235104] remoteproc remoteproc6: powering up 4b2b4000.pru[ 889.235793] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 370028[ 889.235848] ------------[ cut here ]------------[ 889.235867] WARNING: CPU: 0 PID: 1810 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x368/0x3a4[ 889.235875] 44000000.ocp:L3 Standard Error: MASTER PRUSS2 PRU1 TARGET PCIE1 (Read): At Address: 0x00806664 : Data Access in Supervisor mode during Functional access[ 889.235881] Modules linked in: rpmsg_rpc rpmsg_proto pru_rproc pruss_intc bnep pruss pvrsrvkm(O) pruss_soc_bus ti_vpe ti_sc videobuf2_dma_contig ti_csc ti_vpdma v4l2_mem2mem v4l2_common videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btsdio bluetooth joydev ecdh_generic brcmfmac stmpe_adc brcmutil cfg80211 omap_remoteproc virtio_rpmsg_bus rpmsg_core usb_f_ncm usb_f_mass_storage usb_f_rndis u_ether libcomposite uio_pdrv_genirq uio cmemk(O)[ 889.236083] CPU: 0 PID: 1810 Comm: bash Tainted: G W O 4.14.108-ti-r137 #1buster[ 889.236090] Hardware name: Generic DRA74X (Flattened Device Tree)[ 889.236111] [<c0112de8>] (unwind_backtrace) from [<c010d6a8>] (show_stack+0x20/0x24)[ 889.236125] [<c010d6a8>] (show_stack) from [<c0cb2ea4>] (dump_stack+0x80/0x94)[ 889.236139] [<c0cb2ea4>] (dump_stack) from [<c013fbb8>] (__warn+0xec/0x114)[ 889.236151] [<c013fbb8>] (__warn) from [<c013fc38>] (warn_slowpath_fmt+0x58/0x74)[ 889.236164] [<c013fc38>] (warn_slowpath_fmt) from [<c0736718>] (l3_interrupt_handler+0x368/0x3a4)[ 889.236180] [<c0736718>] (l3_interrupt_handler) from [<c01ac04c>] (__handle_irq_event_percpu+0x84/0x2d0)[ 889.236193] [<c01ac04c>] (__handle_irq_event_percpu) from [<c01ac2d4>] (handle_irq_event_percpu+0x3c/0x90)[ 889.236204] [<c01ac2d4>] (handle_irq_event_percpu) from [<c01ac370>] (handle_irq_event+0x48/0x6c)[ 889.236216] [<c01ac370>] (handle_irq_event) from [<c01b030c>] (handle_fasteoi_irq+0xd0/0x178)[ 889.236229] [<c01b030c>] (handle_fasteoi_irq) from [<c01ab15c>] (generic_handle_irq+0x34/0x44)[ 889.236240] [<c01ab15c>] (generic_handle_irq) from [<c01ab76c>] (__handle_domain_irq+0x8c/0xfc)[ 889.236252] [<c01ab76c>] (__handle_domain_irq) from [<c01015bc>] (gic_handle_irq+0x4c/0x88)[ 889.236264] [<c01015bc>] (gic_handle_irq) from [<c0ccef4c>] (__irq_svc+0x6c/0xa8)[ 889.236271] Exception stack(0xce9bbc28 to 0xce9bbc70)[ 889.236282] bc20: 0000000a ce9bbcac 00000025 c10417a6 ce9bbcac c104179c[ 889.236292] bc40: ce9bbd0c d3761420 c108c08c ce9bbdac ce9bbcac ce9bbc8c ce9bbc90 ce9bbc78[ 889.236300] bc60: c0cc6b40 c0cc2dac 20010013 ffffffff[ 889.236314] [<c0ccef4c>] (__irq_svc) from [<c0cc2dac>] (format_decode+0x78/0x5e8)[ 889.236326] [<c0cc2dac>] (format_decode) from [<c0cc6b40>] (vsnprintf+0x84/0x3f4)[ 889.236338] [<c0cc6b40>] (vsnprintf) from [<c0cc6f34>] (snprintf+0x38/0x54)[ 889.236353] [<c0cc6f34>] (snprintf) from [<c08891f0>] (dev_vprintk_emit+0x64/0x210)[ 889.236367] [<c08891f0>] (dev_vprintk_emit) from [<c08893dc>] (dev_printk_emit+0x40/0x5c)[ 889.236379] [<c08893dc>] (dev_printk_emit) from [<c088949c>] (__dev_printk+0x58/0x98)[ 889.236391] [<c088949c>] (__dev_printk) from [<c08898ac>] (_dev_info+0x58/0x74)[ 889.236406] [<c08898ac>] (_dev_info) from [<c0a800d8>] (rproc_boot+0x574/0x634)[ 889.236421] [<c0a800d8>] (rproc_boot) from [<c0a80ea8>] (state_store+0x80/0x144)[ 889.236435] [<c0a80ea8>] (state_store) from [<c0887ca8>] (dev_attr_store+0x28/0x34)[ 889.236450] [<c0887ca8>] (dev_attr_store) from [<c038637c>] (sysfs_kf_write+0x48/0x54)[ 889.236463] [<c038637c>] (sysfs_kf_write) from [<c03859d0>] (kernfs_fop_write+0xf8/0x1dc)[ 889.236477] [<c03859d0>] (kernfs_fop_write) from [<c02fae18>] (__vfs_write+0x28/0x48)[ 889.236490] [<c02fae18>] (__vfs_write) from [<c02fb020>] (vfs_write+0xb4/0x1c8)[ 889.236503] [<c02fb020>] (vfs_write) from [<c02fb2a0>] (SyS_write+0x5c/0xbc)[ 889.236516] [<c02fb2a0>] (SyS_write) from [<c0109000>] (ret_fast_syscall+0x0/0x54)[ 889.236524] ---[ end trace 0de72da1c33b76f5 ]---[ 889.236536] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 1267.955180] pru-rproc 4b2b4000.pru: can't change firmware while running[ 1271.783200] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 1281.595190] remoteproc remoteproc6: powering up 4b2b4000.pru[ 1281.595471] remoteproc remoteproc6: Booting fw image PRU-LEDs.out, size 32644[ 1281.595490] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 1284.647130] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 2370.791112] remoteproc remoteproc6: powering up 4b2b4000.pru[ 2370.791406] remoteproc remoteproc6: Booting fw image PRU-LEDs.out, size 32644[ 2370.791426] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 2376.151149] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 2380.387163] remoteproc remoteproc6: powering up 4b2b4000.pru[ 2380.387284] remoteproc remoteproc6: Booting fw image PRU-LEDs.out, size 32644[ 2380.387303] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 2382.287146] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 2393.327159] remoteproc remoteproc6: powering up 4b2b4000.pru[ 2393.327706] remoteproc remoteproc6: Booting fw image PRU_ucfsm.out, size 370028[ 2393.327762] ------------[ cut here ]------------[ 2393.327782] WARNING: CPU: 0 PID: 1810 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x368/0x3a4[ 2393.327790] 44000000.ocp:L3 Standard Error: MASTER PRUSS2 PRU1 TARGET PCIE1 (Read): At Address: 0x00806664 : Data Access in Supervisor mode during Functional access[ 2393.327796] Modules linked in: rpmsg_rpc rpmsg_proto pru_rproc pruss_intc bnep pruss pvrsrvkm(O) pruss_soc_bus ti_vpe ti_sc videobuf2_dma_contig ti_csc ti_vpdma v4l2_mem2mem v4l2_common videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btsdio bluetooth joydev ecdh_generic brcmfmac stmpe_adc brcmutil cfg80211 omap_remoteproc virtio_rpmsg_bus rpmsg_core usb_f_ncm usb_f_mass_storage usb_f_rndis u_ether libcomposite uio_pdrv_genirq uio cmemk(O)[ 2393.327996] CPU: 0 PID: 1810 Comm: bash Tainted: G W O 4.14.108-ti-r137 #1buster[ 2393.328002] Hardware name: Generic DRA74X (Flattened Device Tree)[ 2393.328024] [<c0112de8>] (unwind_backtrace) from [<c010d6a8>] (show_stack+0x20/0x24)[ 2393.328039] [<c010d6a8>] (show_stack) from [<c0cb2ea4>] (dump_stack+0x80/0x94)[ 2393.328052] [<c0cb2ea4>] (dump_stack) from [<c013fbb8>] (__warn+0xec/0x114)[ 2393.328064] [<c013fbb8>] (__warn) from [<c013fc38>] (warn_slowpath_fmt+0x58/0x74)[ 2393.328078] [<c013fc38>] (warn_slowpath_fmt) from [<c0736718>] (l3_interrupt_handler+0x368/0x3a4)[ 2393.328093] [<c0736718>] (l3_interrupt_handler) from [<c01ac04c>] (__handle_irq_event_percpu+0x84/0x2d0)[ 2393.328107] [<c01ac04c>] (__handle_irq_event_percpu) from [<c01ac2d4>] (handle_irq_event_percpu+0x3c/0x90)[ 2393.328118] [<c01ac2d4>] (handle_irq_event_percpu) from [<c01ac370>] (handle_irq_event+0x48/0x6c)[ 2393.328130] [<c01ac370>] (handle_irq_event) from [<c01b030c>] (handle_fasteoi_irq+0xd0/0x178)[ 2393.328143] [<c01b030c>] (handle_fasteoi_irq) from [<c01ab15c>] (generic_handle_irq+0x34/0x44)[ 2393.328154] [<c01ab15c>] (generic_handle_irq) from [<c01ab76c>] (__handle_domain_irq+0x8c/0xfc)[ 2393.328166] [<c01ab76c>] (__handle_domain_irq) from [<c01015bc>] (gic_handle_irq+0x4c/0x88)[ 2393.328178] [<c01015bc>] (gic_handle_irq) from [<c0ccef4c>] (__irq_svc+0x6c/0xa8)[ 2393.328185] Exception stack(0xce9bbc20 to 0xce9bbc68)[ 2393.328196] bc20: c104179c ce9bbcac 00000025 c10417a6 ce9bbcac c104179c ce9bbd0c d3761420[ 2393.328206] bc40: c108c08c ce9bbdac ce9bbcac ce9bbc8c ce9bbc90 ce9bbc70 c0cc6b40 c0cc2da4[ 2393.328214] bc60: 20010013 ffffffff[ 2393.328227] [<c0ccef4c>] (__irq_svc) from [<c0cc2da4>] (format_decode+0x70/0x5e8)[ 2393.328239] [<c0cc2da4>] (format_decode) from [<c0cc6b40>] (vsnprintf+0x84/0x3f4)[ 2393.328252] [<c0cc6b40>] (vsnprintf) from [<c0cc6f34>] (snprintf+0x38/0x54)[ 2393.328267] [<c0cc6f34>] (snprintf) from [<c08891f0>] (dev_vprintk_emit+0x64/0x210)[ 2393.328280] [<c08891f0>] (dev_vprintk_emit) from [<c08893dc>] (dev_printk_emit+0x40/0x5c)[ 2393.328293] [<c08893dc>] (dev_printk_emit) from [<c088949c>] (__dev_printk+0x58/0x98)[ 2393.328305] [<c088949c>] (__dev_printk) from [<c08898ac>] (_dev_info+0x58/0x74)[ 2393.328320] [<c08898ac>] (_dev_info) from [<c0a800d8>] (rproc_boot+0x574/0x634)[ 2393.328335] [<c0a800d8>] (rproc_boot) from [<c0a80ea8>] (state_store+0x80/0x144)[ 2393.328348] [<c0a80ea8>] (state_store) from [<c0887ca8>] (dev_attr_store+0x28/0x34)[ 2393.328363] [<c0887ca8>] (dev_attr_store) from [<c038637c>] (sysfs_kf_write+0x48/0x54)[ 2393.328377] [<c038637c>] (sysfs_kf_write) from [<c03859d0>] (kernfs_fop_write+0xf8/0x1dc)[ 2393.328391] [<c03859d0>] (kernfs_fop_write) from [<c02fae18>] (__vfs_write+0x28/0x48)[ 2393.328404] [<c02fae18>] (__vfs_write) from [<c02fb020>] (vfs_write+0xb4/0x1c8)[ 2393.328416] [<c02fb020>] (vfs_write) from [<c02fb2a0>] (SyS_write+0x5c/0xbc)[ 2393.328431] [<c02fb2a0>] (SyS_write) from [<c0109000>] (ret_fast_syscall+0x0/0x54)[ 2393.328439] ---[ end trace 0de72da1c33b76f6 ]---[ 2393.328452] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 2397.083151] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru[ 2406.111125] remoteproc remoteproc6: powering up 4b2b4000.pru[ 2406.111417] remoteproc remoteproc6: Booting fw image PRU-LEDs.out, size 32644[ 2406.111437] remoteproc remoteproc6: remote processor 4b2b4000.pru is now up[ 2408.331136] remoteproc remoteproc6: stopped remote processor 4b2b4000.pru -- 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/ba3de786-420b-4cc9-a256-53c3c44e3ab1n%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/1d76ed85-ba11-457a-b099-713737c4c865n%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/539841947.809346.1614707431793%40mail.yahoo.com.
