On 03/05/2018 12:31 AM, Robert Nelson wrote:
> [...]

Your old eMMC is blocking U-Boot Overlays:

sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10


I'm in a middle of a rewrite to enable cape-universal in this
situation, currently your selection of
"uboot_overlay_addr0=/lib/firmware/bb_autoclave-00A0.dtbo" is blocking

Step 1: Upgrade to this bootloader:

sudo /opt/scripts/tools/developers/update_bootloader.sh --beta

Step 2: Install this kernel: (haven't backported the changes to
v4.14.x/v4.9.x/v4.4.x yet)

sudo /opt/scripts/tools/update_kernel.sh --bone-channel --exp

Performing these steps seems to have unblocked the universal cape, as you said, and now `/sys/devices/platform/ocp/ocp:P*_*_pinmux` have reappeared without needing my custom .dts file at all. Great!

Even better, the USB WiFi adapter (that worked fine on the BB white) that hadn't been working is now happy again. Before, it wouldn't come up after boot, and had to be unplugged and replugged in order to start working.

Only thing missing is the RT_PREEMPT patch. For my application it may not be necessary, since autoclave control timings aren't critical.

Step 3: in your overlay add a new fragment@0 section like this, but
with the pins your "bb_autoclave" uses:


I still haven't managed to get my overlay working. Charles's suggestions to add the pinmux configuration and this suggestion to free the pins caused errors. I probably made a mistake following y'all's directions. I'm happy to go back and troubleshoot if it helps anyone, but right now with the pins in the default state, it's all good.

Thank you!


website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
--- You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to