Ok, I'm 99.9% sure the GPIO's are all being configured correctly and
functional. As I know there are exactly 6 GPI's and the rest are GPO's.
root@wgd:~# cat /sys/class/gpio/gpio*/direction
out
out
out
out
out
out
out
out
out
in
in
in
in
in
in
out
out
out
out
On Wed, Apr 5, 2017 at 8:51 PM,
By the way, the remoteproc modules went away on their own. I'm not sure
why, but good ;)
On Wed, Apr 5, 2017 at 8:49 PM, William Hermans wrote:
> It appears everything loaded fine.
>
> *uEnv.txt*
> ###
> ###Additional custom capes
>
It appears everything loaded fine.
*uEnv.txt*
###
###Additional custom capes
uboot_overlay_addr4=/lib/firmware/custom-00A0.dtbo */* 6 channels PWM, and
~19 pins GPIO */*
uboot_overlay_addr5=/lib/firmware/BB-ADC-00A0.dtbo
uboot_overlay_addr6=/lib/firmware/BB-W1-P8.26-00A0.dtbo */* Modified 1-wire
Ok so an observation.
I've got one custom overlay to load. Well technically two, but only one at
a time so far. I've only experimented with one at a time so far. However,
the image I downloaded was an sdcard only image, and no flasher image on
the testing image page. So what ends up happening is
So after:
root@wgd:~# *systemctl disable generic-board-startup.service*
Removed
/etc/systemd/system/multi-user.target.wants/generic-board-startup.service.
root@wgd:~# *nano /boot/uEnv.txt*
Change: cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
To: cmdline=coherent_pool=1M
So, I've not actually gotten to testing the overlays loaded through uboot
yet. But I must say Robert, good job. Running lsmod after removing cape
universal from uEnv.txt (cmdline ) works awesomely. The only thing left is
the RNDIS related stuff, which can be disabled through your generic-board