difference between config-pin executables

On my Beaglebone Black, I have two config-pin executables. One is a compiled executable from the bb-cape-overlays package, the other is a bash script in /opt/source/bb.org-overlays:

$ which config-pin

$ dpkg -S /usr/bin/config-pin
bb-cape-overlays: /usr/bin/config-pin

$ find / -name config-pin 2> /dev/null

I have a script that configures specific pins using config-pin in the format:
config-pin P8.8 in-
Which sets pin P8.8 to an input configured as a pull down.

The bash script seems to be the one that accepts that format, the other does not and errors with:
ERROR: open() for /sys/devices/platform/ocp/ocp:P8_8_pinmux/state failed, No such file or directory

The compiled version is the default on my Beaglebone and I’d like to know more about it. For my script to work, I need to use the other one right now. I can certainly update the script if the compiled config-pin is a newer version and recommended practice is to use it, but I can’t seem to make it work right. Any information is appreciated!

P8.8 -> P8.08, the original had a fixup for the missing zero.. I
don't think 'in-' has been migrated yet..


What is the equivalent to the following: