**** BEGIN LOGGING AT Sat Aug 10 03:00:09 2019
Aug 10 12:58:15 <embden_new[m]> julieng:  sstabellini  any thoughts? ^
Aug 10 15:07:02 <pratimugale[m]> zeekhuge: the pruss_api driver needs the rpmsg_core.c module to be installed into the kernel which needs to be done manually. If rpmsg_core is not installed, the module does not load and this is the dmesg log: https://pastebin.com/4vXMpY92. So the process now is: 1. modprobe rpmsg_core, 2. insmod pruss_api.ko; and then start the pru firmware. How should this process ideally be?
Aug 10 17:27:50 <zeekhuge[m]> pratimugale : Did you try using "modprobe pruss_api" Instead of using insmod?
Aug 10 17:28:24 <zeekhuge[m]> Modprobe tries to load in the dependencies.
Aug 10 17:36:16 <pratimugale[m]> zeekhuge: "modprobe pruss_api" works after copying pruss_api.ko to /lib/modules/4.14.71-ti-r80/
Aug 10 17:36:17 <pratimugale[m]> and then doing "$ depmod -ae"
Aug 10 17:37:29 <pratimugale[m]> But the device file doesn't appear until the modprobe is done manually
Aug 10 17:37:29 <zeekhuge[m]> Well. Yeah, that's how one has to install a module.
Aug 10 17:38:13 <zeekhuge[m]> You mean until "modprobe pruss_api" Is done manually?
Aug 10 17:38:27 <pratimugale[m]> zeekhuge: yes
Aug 10 17:39:02 <zeekhuge[m]> Pruss_api has the rpmsg channel name as a key, right?
Aug 10 17:40:01 <zeekhuge[m]> If it is their, then loading the firmware itself should probe the module.
Aug 10 17:42:05 <pratimugale[m]> the key is actually "pruss-api" (not an underscore): https://github.com/pratimugale/PRUSS-Bindings/blob/2fca2c95f553c71dbef65b136d42ce4c57a277e0/drivers/pruss_api.c#L307
Aug 10 17:44:37 <zeekhuge[m]> And its the same in firmware?
Aug 10 17:44:52 <pratimugale[m]> yes
Aug 10 17:52:08 <zeekhuge[m]> Not sure why that isn't working.
Aug 10 17:52:15 <zeekhuge[m]> I am away from the keyboard as of now.
Aug 10 17:52:19 <zeekhuge[m]> Will try morning.
Aug 10 17:52:37 <zeekhuge[m]> https://github.com/ZeekHuge/BeagleScope/blob/master/beaglescope/beaglescope_driver.c#L437
Aug 10 17:52:37 <zeekhuge[m]> Is this module working? Have you tried testing it?
Aug 10 17:54:08 <zeekhuge[m]> Also, if you can try to look into rproc driver, it should be parsing the code and then invoking the driver.
Aug 10 17:54:30 <zeekhuge[m]> So, its possible they might have changed it in later versions.
Aug 10 17:54:49 <zeekhuge[m]> Try to look into, if they have removed this, then no point in trying to debug this thing.
Aug 10 17:58:13 <pratimugale[m]> zeekhuge: the device file for "pruss_api" is created, only if the "rpmsg-pru" key has been used previously in the firmware. Otherwise after a fresh reboot, the file for pruss_api isn't created
Aug 10 17:59:16 <pratimugale[m]> I'll test more on this and give you more details
Aug 10 17:59:33 <zeekhuge[m]> Thanks.
**** ENDING LOGGING AT Sun Aug 11 02:59:57 2019