00:20 <mattb0ne> Is it possible to pass a variable to the PRU private memory and have it take

00:20 <mattb0ne> I wanted to move the encoder count away from zero to deal with the problem if it accidentally wraps

00:21 <mattb0ne> I am passing the value from python after mapping it. I guess I could put an offset on the python side but I figured I would try to have the data come correct off the encoder

00:22 <mattb0ne> let me try that brb

01:22 <zmatt> wtf is he doing now, encoder count wrapping should not be a problem unless your code is broken

10:53 <set_> Whelp...

10:54 <set_> This ServoCape is hurting my senses. I think people are working to make it work. So, young sir. Staying patient once more.

10:56 <set_> It is either a remote error or a resource busy error. Either way, no go.

11:05 <zmatt> did you disable the overlay?

11:05 <set_> Yes.

11:06 <zmatt> can you pastebin the output of: ls -l /sys/bus/i2c/devices/

11:06 <set_> Sure.

11:06 <set_> Please hold. Let me boot.

11:06 <zmatt> and show-pins

11:07 <set_> Last time I checked /dev/i2c2, it showed root : i2c.

11:07 <set_> Okay.

11:07 <set_> I will check show-pins too.

11:08 <set_> ls -l shows root root

11:08 <zmatt> ???

11:09 <set_> I will show you the output.

11:09 <set_> Please hold.

11:10 <set_> https://pastebin.com/H9GMYRkD is the show-pins.

11:11 <set_> https://pastebin.com/xYt6GmRv is the ls -l command.

11:12 <zmatt> the overlay is not disabled

11:13 <set_> Yes it is. I have no overlay on my /boot/uEnv.txt file.

11:13 <zmatt> there's no need for that, it gets autodetected and loaded unless you explicitly disable it

11:13 <set_> No overlay.

11:14 <set_> I will show you.

11:14 <set_> maybe uboot-ovlerays=1 ?

11:14 <zmatt> again, unless you either physically remove the overlay from the filesystem or disable overlay detection for that specific cape, it will get loaded, and it did get loaded

11:15 <set_> https://pastebin.com/WDyRVNDP

11:15 <zmatt> try uncommenting disable_uboot_overlay_addr0=1

11:15 <set_> Okay.

11:15 <zmatt> (I don't know for sure if the cape is slot 0, I'm just assuming it is)

11:16 <set_> It is done. Now, rebooting.

11:17 <set_> Well...

11:18 <set_> cap i2c sda/scl report different now.

11:18 <set_> cap = cape

11:20 <zmatt> perhaps a better way to do this actually would be this:

11:20 <zmatt> sudo dpkg-divert --rename --add /lib/firmware/BBORG_SERVO-00A2.dtbo

11:20 <set_> I am back to remote I/O error.

11:20 <set_> Oh.

11:20 <set_> Okay.

11:20 <zmatt> then you can undo the change in /boot/uEnv.txt

11:21 <zmatt> this will just specifically disable that one specific overlay, without causing problems if you later put a different cape on the beaglebone

11:22 <set_> Okay.

11:22 <set_> I rebooted now.

11:22 <zmatt> ah crap it might not get loaded from there

11:22 <set_> I undid the change in /boot/

11:22 <set_> Ha.

11:22 <zmatt> since overlays are included with kernels now

11:22 <set_> Right!

11:22 <set_> But...it was located there.

11:23 <zmatt> that's annoying, that means there's no easy way to suppress broken/unwanted overlays

11:23 <set_> the overlay for BBORG_SERVO-00A2.dtbo was located in /lib/firmware/

11:23 <set_> Well, the board did boot.

11:24 <zmatt> yeah but at least here it's also included with some kernel packages: /boot/dtbs/*/overlays/BBORG_SERVO-00A2.dtbo

11:24 <set_> Aw. Let me check.

11:24 <set_> Not on mine.

11:24 <set_> I checked earlier.

11:25 <zmatt> okay, but then probably if you ever install a kernel update it would break again, so that's not ideal

11:25 <set_> Hmm.

11:25 <set_> So, remove the newer kernel?

11:25 <zmatt> so the previous solution (disable_uboot_overlay_addr0=1) may be better... just don't forget to disable it if you want to use a different cape that *does* need an overlay

11:26 <set_> Okay. It did not work either way so far.

11:26 <zmatt> that's just as likely an issue with whatever you're doing though :P

11:26 <set_> I tried w/ BB-I2C2-BME680.dtbo and it still would...probably.

11:26 <set_> It is probably my source.

11:26 <zmatt> but just for confirmation pastebin show-pins and ls -l /sys/bus/i2c/devices/ again

11:26 <set_> Okay.

11:26 <zmatt> ???!?

11:27 <set_> Well, i2c was in the title. I figured nothing it working. Why not?

11:27 <zmatt> the servo cape doesn't need an overlay, and a BME680 is a gas sensor

11:28 <set_> Thank you.

11:28 <set_> I need to get a BME680.

11:28 <set_> https://pastebin.com/BaVjGVak is show-pins

11:29 <set_> https://pastebin.com/mkj30KaQ is ls -l.

11:30 <set_> I think the issue is when I use root w/ sudo permissions, I get the lib. not showing up. Then, when I run i2c devices w/out root/sudo permissions, I get errors.

11:30 <zmatt> this looks fine

11:30 <set_> either way, no go.

11:30 <zmatt> you don't need sudo

11:30 <set_> Okay.

11:31 <zmatt> unless your system is broken

11:31 <set_> I just installed this system.

11:31 <set_> It has not worked yet. It is probably my source.

11:31 <zmatt> what does ls -l /dev/i2c-2 show?

11:32 <set_> crw-rw---- 1 root i2c 89, 2 Jul 9 11:22 /dev/i2c-2

11:32 <zmatt> that looks fine, no root privileges needed

11:32 <set_> Okay.

11:36 <zmatt> rcn-ee: the BBORG_SERVO-00A2 overlay is completely broken and will prevent people from being able to use the cape

11:37 <set_> @zmatt: I think they are building something nice for the Cape usages.

11:38 <set_> Just guessing.

11:40 <zmatt> rcn-ee: it's full of typos, it's changing properties of the &i2c2 bus, it has a broken declaration of the pwm controller that doesn't match the DT binding of the driver, they're using gpio-keys for the inputs even though they should almost certainly just be normal gpios, that gpio-keys declaration is however also broken and doesn't match the DT binding, moreover the pinmux for it disables input on all ...

11:40 <zmatt> ...those pins

11:40 <zmatt> like, this was clearly never tested

11:41 <zmatt> having no overlay for this cape at all would be a great improvement over this thing

11:41 <set_> Ha.

22:25 <Guest59> Good day

22:25 <Guest59> I have a beaglebone Black A5B, I bought it a long time ago and I want to install a service called AdguardHome on it

22:25 <Guest59> The problem is that after it is installed the page does not work on port 3000, does anyone have a similar experience