I love the "show-pins" script, but I cannot run that since there is a utf8 mismatch with either perl or whatever is different/dependent on the TI SDK image. The Arago image is just a different animal in so many ways....
That post works great on the normal Cloud9 distro, but not on the TI SDK Matrix image. There are so many changes to the Arago build over the original Cloud9 image that came in flash.
But you did give me an idea -- load up the default Cloud9 image, run that and use your referenced post to create my dts and compile the dtb to disk, copy that and then reboot with the TI SDK image, with uEnv pointing to the new dtb board. That might work!
The documentation on the TI site is horrendous, it is out of date, just wrong in spots, etc. For example:
Then, modify “uEnv.txt” on the boot partition (“/run/media/mmcblk0p1” directory on filesystem) to specify fdtfile with the desired dtb file name.
In the image that I have from the latest SDK, uEnv.txt is not on the boot partition, but the second partition /run/media/mmcblk1p1/boot/uEnv.txt. On the raw TI image, that dtb line in uEnv.txt is actually commented out, so whatever the kernel does on boot, is how the pins are defined.
I spent countless hours researching, finding solutions, to find that they are outdated, wrong, don't work, or not defined well. I don't know how you all develop in this world, but I am at this point where I have to define the pins correctly, and perhaps, this project is done!