07:39 <Prashanth> Hi All, I am Prashanth S from IIIT Allahabad India Studying Masters. I am interested to contribute in gsoc for the beagleboard community. I have good understanding of the am335x soc and have developed a bare metal source code with support of gpio, interrupts, cpsw with u-boot as reference. My github link

07:39 <Prashanth> https://github.com/slpp95prashanth/Beaglebone-mBootloader/tree/cpsw.

07:40 <Prashanth> Can someone give some pointers or guidance?

09:59 <johanhenselmans> Any reason why ‘config-pin p8.09 gpio’ does not create /sys/class/gpio/gpio69? As far as I can see, it should be created (5.10.78-bone57).

11:28 <johanhenselmans> Just rebooted in 4.19.217-bone73. Now it’s there. Strange.

13:02 <giort> Hello! Is there a reason why the config-pin utility on the BBB gives an error like this: (i have the correct boot overlay selected in /boot/uEnv.txt, and audio overlay disabled)

13:02 <giort> ERROR: write() to /sys/devices/platform/ocp/ocp:P9_29_pinmux/state failed, No such device

13:03 <giort> meanwhile, if I ls the given pinmux folder, the state file exists, and has "default" in it

13:03 <giort> The PRU has worked before, but setting it up always feels unreliable.

13:23 <markand> o/

13:25 <markand> I'm finally upgrading our old appliance using a fresh image of debian buster. once the setup is complete I wonder how do I create a SD "flasher" image? just by editing /boot/uEnv.txt and reboot?

13:26 <markand> (and obviously, insert SD card before)

14:38 <rcn-ee_> markand, if your running a good image on your eMMC, just run: ```sudo /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh```

14:38 <rcn-ee_> that's build a microSD "flasher"...

17:04 <markand> rcn-ee, okay thanks! :))

18:57 <giort> to my question earlier: turns out I wrote pru_out instead of pruout, so thats where the error came from.

19:35 <Guest60> Hi, I would like to know if it's possible to use UFW on my PocketBeagle and still be able to connect with the USB IP 192.168.7.2. If yes, What rules do we need to add in the firewall ?

20:12 <rcn-ee> Guest60, ssh over usb? port 22..

20:32 <Guest60> yes but when plug USB windows or linux create 192.168.7.0 that 192.168.7.1 is windows i belived and 192.168.7.2 is the BB but I try opening the port 22 for my ip ex: 192.168.1.100 and 192.168.7.1 (Because the BB see me that way) and it dosen't work.

20:33 <Guest60> BTW: it work when my Modem it plug in and i use the WAN IP. But if I have a problem with the modem I want a quick way (the USB) to connect SSH by using the 192.168.7.2

20:36 <Guest60> I even try to open port 22 to 192.168.0.0/16 and still not working :/

21:01 <zmatt> giort: so yeah, if you get ENODEV (No Such Device) from setting the state of a pinmux helper, that means the requested pinmux state is not defined (for that pinmux helper)

21:02 <giort> zmatt: thanks. The error message is a bit misleading tho.

21:04 <zmatt> johanhenselmans: config-pin just changes the pinmux (effectively reconnecting a physical processor pin to a different peripheral/function) and some options on the pin's i/o cell (such as the pull-up/down configuration). peripherals (such as the gpio controller) are not aware of whether their signals are actually connected to some physical pin

21:04 <zmatt> giort: yes, options for error reporting from a write() system call is unfortunately fairly restrictive

21:05 <zmatt> though I don't know why config-pin doesn't provide a sensible error message

21:07 <zmatt> it should definitely have special cased getting ENODEV from the write()... which is exactly what I do in this tiny python library for getting/setting pinmux: https://pastebin.com/MKtWJ8G8

21:08 <zmatt> johanhenselmans: note that setting a pin to "gpio" mode using config-pin is usually not what you want, since it actually means "gpio with internal pull-up/down disabled" ... just leave the pin configured to "default"

21:09 <zmatt> (which is gpio mode with default internal pull enabled)

21:13 <giort> zmatt: yes, that type of error message would be nice. Where is the source code for the config-pin utility? I couldn't find it on github

21:14 <zmatt> johanhenselmans: as for the missing gpio... all digital I/O pins on the expansion headers have their gpio exported by default (even pins that are currently not reconfigurable to gpio, e.g. the eMMC pins)

21:14 <zmatt> johanhenselmans: you might have run into a known bug where attempting to manually export a gpio that's already exported actually breaks things and causes it to disappear

21:15 <zmatt> giort: no idea, sorry

21:16 <zmatt> giort: btw, a useful pin when getting unclear errors from anything in sysfs: check the kernel log!

21:16 <zmatt> Nov 24 22:05:35 beaglebone kernel: bone-pinmux-helper ocp:P9_20_pinmux: Failed to find state dfksjhfkdsj

21:16 <zmatt> *a useful tip