**** BEGIN LOGGING AT Mon Dec 07 02:59:57 2020
Dec 07 03:00:08 <ayjay_t> neglect is okay because part of this is learning which means its okay to struggle through some bugs/etc
Dec 07 03:00:36 <ayjay_t> i'm not sure what kind of response i'll receive from the group so i'm not sure what "success" looks like
Dec 07 03:00:48 <ayjay_t> worse case scenario is i post a bunch of educational stuff and... nobody cares
Dec 07 03:01:22 <ayjay_t> if four or five people actually DO it and a 50 people think "wow these guys are smart" that's a success
Dec 07 03:01:29 <ayjay_t> (huge sucess)
Dec 07 03:01:31 <ayjay_t> success*
Dec 07 03:29:41 <set_> Enormous! Success!
Dec 07 03:30:24 <set_> PRU stuff even on an already done and coded example is hard to figure out. Did prudebug stop working?
Dec 07 06:38:03 <vedant16[m]> zmatt: those instructions don't wokr
Dec 07 06:38:06 <vedant16[m]>  * zmatt: those instructions don't work
Dec 07 06:52:17 <zmatt> vedant16[m]: they were briefly wrong yesterday but I fixed them about an hour later... are you using the latest version of the instructions?
Dec 07 06:52:35 <vedant16[m]> Yes, the module doesn't load
Dec 07 06:52:39 <vedant16[m]> installs correctly
Dec 07 06:53:14 <zmatt> ah
Dec 07 06:54:18 <zmatt> I hadn't tried that, though I should have
Dec 07 06:57:04 <zmatt> can you please use pastebin to share the kernel log output that resulted from it?  the module loads just fine here (but I don't have the overlay installed, so the driver doesn't probe)
Dec 07 06:57:43 <zmatt> or, what do you mean by "the module doesn't load" ?
Dec 07 07:00:26 <vedant16[m]> Okay, my steps were
Dec 07 07:00:32 <vedant16[m]> ./install.sh
Dec 07 07:00:40 <vedant16[m]> then instructions on git issue
Dec 07 07:00:42 <vedant16[m]> reboot
Dec 07 07:00:49 <vedant16[m]> sudo modproble beaglelogic
Dec 07 07:00:58 <vedant16[m]> <zmatt "can you please use pastebin to s"> dmesg ?
Dec 07 07:01:08 <zmatt> normally you never have to modprobe it, it will get loaded automatically
Dec 07 07:01:41 <zmatt> how did you conclude it didn't load?
Dec 07 07:19:49 <vedant16[m]> <zmatt "how did you conclude it didn't l"> https://stackoverflow.com/a/30311688
Dec 07 07:20:10 <vedant16[m]> I suspected since sigrok-cli said, no devices found
Dec 07 07:20:20 <vedant16[m]> and then found using this
Dec 07 07:21:57 <zmatt> that seems like a weird way to check if a module is loaded (instead of just checking lsmod)
Dec 07 07:24:55 <vedant16[m]> Can you try it on your bbbw
Dec 07 07:25:00 <vedant16[m]> does it load the module on boot ?
Dec 07 07:30:31 <zmatt> it loads the module just fine yes.  it doesn't seem to work, but the module loads just fine :P
Dec 07 07:36:33 <zmatt> anyway, that's as much debugging as I'm interested in doing right now, I don't care to dig into how this driver works
Dec 07 07:38:27 <zmatt> I think it's a problem with the device tree though
Dec 07 07:39:22 <zmatt> ah, the beaglelogic install script configures the beaglelogic overlay as replacement of the pru remoteproc one, but it needs both
Dec 07 07:40:04 <zmatt> ok, let's give this one final try
Dec 07 07:41:29 <zmatt> didn't help though
Dec 07 07:42:43 <zmatt> wtf
Dec 07 07:45:12 <zmatt> anyway, yeah now I'm done trying, like I said I don't really feel like digging into this driver, I have other stuff to do
Dec 07 11:14:27 <vedant16[m]> Still not working on my system. I'll just go for those 5$ logic analysers.
Dec 07 11:14:44 <zmatt> vedant16[m]: I mean, if you want to get it working easily, use the premade image
Dec 07 11:15:00 <zmatt> I assumed you had personal motivation to get it working on a current image
Dec 07 11:15:24 <zmatt> https://beaglelogic.readthedocs.io/en/latest/beaglelogic_system_image.html
Dec 07 11:15:34 <vedant16[m]> Yup, I was working on bitbang i2c, and wanted a LA to debug it.
Dec 07 11:15:34 <vedant16[m]> I'll download the image, thanks
Dec 07 11:16:21 <vedant16[m]> Can I run this image off the sd card?
Dec 07 11:16:26 <vedant16[m]> or flashing is necessary
Dec 07 11:17:27 <zmatt> you should probably have read the page before asking that
Dec 07 11:17:40 <zmatt> (these steps are for running the image off sd card)
Dec 07 11:18:01 <vedant16[m]> my bad, sorry
Dec 07 11:30:51 <Abhishek[m]_> zmatt: I saw that you tried to compile BeagleLogic for 4.19, and it should have compiled
Dec 07 11:31:09 <Abhishek[m]_> But you need to add an overlay for it to load
Dec 07 12:31:53 <zmatt> Abhishek[m]_: it compiled with a one-line fix (commenting out a non-existent #include)
Dec 07 12:32:23 <zmatt> and I had the overlay enabled (in addition to the remoteproc-pru overlay, rather than instead of it which is what install.sh tries to do)
Dec 07 12:32:35 <zmatt> it tries to probe the driver at boot, but fails
Dec 07 12:42:56 <Abhishek[m]_> Okay, wonder what the error is
Dec 07 12:43:04 <zmatt> I posted it in the github issue
Dec 07 12:44:39 <zmatt> btw I noticed that error message occurs in two places in the driver.. the second one should have been PRU1 instead of PRU0
Dec 07 19:06:39 <ayjay_t> most cortex-m's initialize the program counter from 0x0 (or 0x4? can't remember). i think some boot modes will start in a boot rom. is that also the case on the sitara?
Dec 07 19:22:25 <zmatt> the default base address for the vector table at 0x0.  the first two 32-bit entries of that table are the initial stack pointer and the reset vector (i.e. initial program counter)
Dec 07 19:23:55 <zmatt> usually that address is in internal flash, but obviously that wil depend on the microcontroller
Dec 07 19:26:07 <zmatt> there is no "the sitara", sitara is a marketing name for a diversity of TI's SoCs that have little in common
Dec 07 19:26:21 <zmatt> none of them are cortex-m so your question doesn't make sense regardless
Dec 07 19:27:22 <zmatt> (unless you're referring to the auxiliary cortex-m3/m4 cores that some of TI's SoCs have)
Dec 07 20:32:49 <Siegurd> Hi guys! In case you want to set a UART baud rate in float I created a github repo with details. Im using a blue pill board for the project. Just sharing. https://github.com/Siegurd01/Arduino-STM32-software-UART-with-a-float-baudrate
Dec 07 21:40:52 <ds2> now I am curious... which SoCs do NOT have a cortex-m in it?
Dec 07 22:20:57 <zmatt> ds2: freon/primus (omap-L1xx, AM1xxx), omap3, am35xx
Dec 07 22:23:22 <zmatt> most of the C6x/Keystone SoCs probably also don't
Dec 08 02:19:28 <ayjay_t> no zmatt i just dont know anything about cortex a
Dec 08 02:19:33 <ayjay_t> so i'm basing it off my knowledge of cortex m
Dec 08 02:19:43 <ayjay_t> and by sitara i mean TI's line of cortex a's
**** ENDING LOGGING AT Tue Dec 08 02:59:57 2020