On Wed, Aug 28, 2019 at 11:26 PM [email protected]
<[email protected]> wrote:
>
>
> Over the years I've learned that when someone is enthusiastic regarding their 
> suggestions it's a very good indicator that "It's working for them" and that 
> the problem is between my ears. OK I'll keep trying to sort it out. However, 
> I have observed one thing that requires some comment.
>
> The code than is within Machinekit and especially as it applies to the CRAMPS 
> board, depends upon files that are not to be found in the Machinekit code 
> base. /boot/uEnv.txt and all the dtbs that are to be found in /lib/firmware 
> for instance. So, if I someone were to come up with some code tweek, that 
> applied directly to a file that normally resides outside the code base of 
> Machinekit. Where would you put it?
>
> The first few lines of CRAMPS.bbio for instance. Specifically,
>
> > overlay cape-universal
> > overlay cape-bone-iio

They are needed for the old 3.8.x based kernel.. Rip those lines out
for anything newer.. (which is everything)

>
> Other than a small handful of guys, who would know? And if the code isn't 
> needed, why is it still there? Those few lines of code might as well be land 
> mines buried along my path, primed and ready to blow my time and life away.
>
> Even more frustrating is that two years ago my cramps board was working just 
> fine. Loaded it up and shabam. Worked right out of the box. Actually, that's 
> not completely true as as recall, it was fundamentally a LinuxCNC project and 
> not Machinekit. And then I thought to upgrade my system. If I had only 
> known.... dammit.
>
> running
> sudo /opt/scripts/tools/version.sh
> produced
>
> git:/opt/scripts/:[5b2e16aa1e5c0f627f1d48a6dd1c13b446b9f53b]
> eeprom:[A335BNLT00A54079BBBK2600]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[Machinekit Debian Image 2019-08-25]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2019.04-00002-gbb4af0f50f]:[location: dd MBR]
> kernel:[4.19.59-bone-rt-r36]
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/cape-universal-00A0.dtbo]

You still have this ^ enabled in /boot/uEnv.txt git rid of this line:

uboot_overlay_addr0=/lib/firmware/cape-universal-00A0.dtbo

It's BREAKING the later enablement:

enable_uboot_cape_universal=1

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/CAOCHtYjKtnjuqOxH6hUsysESJfYEzGacNS1Y%3Do4q1%2B9cXHXvAw%40mail.gmail.com.

Reply via email to