Installing/Troubleshooting machinekit

[Bradley Turner]

Hello,

I have had lots of help throughout the setup process of getting machinekit to work properly/Charles graciously got our HAL and INI files working beautifully. I have been able to fix/troubleshoot/have the community/Charles fix-answer most of the issues I have been having, however, I am currently having an issue when launching machinekit that I can't figure out.

I am running a Beaglebone Black with CRAMPS cape attached. The setup is a 4 axis CNC, this is the BCNC Bamboo CNC project that I have posted about earlier in the machinekit group - if you recognize it.

I launch the config selector from the command line and select the config I have. This all seems to work fine. I then get the machinekit splash screen, and then nothing. In the terminal, it seems to be stuck on the line "Waiting for /sys/class/uio/uio0..........." but nothing ever loads. I'm not sure what this means, or how to fix the problem. I was looking into what this error means and saw some discussions in this group about the Linux booting process? I wasn't able to completely understand what was wrong or how to fix it, so any help clarifying what I should try next would be greatly appreciated.

Many thanks appreciated for any help anyone can provide.

Thank you for your time,

Bradley

[Charles Steinkuehler]

That sounds like something to do with the overlays. IIRC, I didn't
have to do anything with the latest uSD image and the PRU UIO devices
were there.

Robert Nelson is the expert on the latest U-Boot overlays, but I have
seen others have problems if their on-board eMMC boot loader was too old.

Send the output of "sudo /opt/scripts/tools/version.sh" and we should
be able to figure out what's wrong.

--
Charles Steinkuehler
cha...@steinkuehler.net

[Bradley Turner]

When I enter that command I get the following, not sure what it all means.

machinekit@beaglebone:~$ sudo /opt/scripts/tools/versian.sh

sudo: /opt/scripts/tools/versian.sh: command not found

machinekit@beaglebone:~$ sudo /opt/scripts/tools/version.sh

git:/opt/scripts/:[1c496b4fc22006f7fa78e7cde0f59a2d53b78e39]

eeprom:[A335BNLT00C03818BBBK0A66]

model:[TI_AM335x_BeagleBone_Black]

dogtag:[Machinekit Debian Image 2019-04-28]

bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-gc8b5ad3a1f]:[location: dd MBR]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2016.01-00001-g4eb802e]:[location: dd MBR]

kernel:[4.19.31-bone-rt-r31]

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]

uboot_overlay_options:[enable_uboot_cape_universal=1]

pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]

pkg:[bb-cape-overlays]:[4.4.20190404.0-0rcnee0~stretch+20190404]

pkg:[bb-wl18xx-firmware]:[1.20190227.1-0rcnee0~stretch+20190227]

pkg:[kmod]:[23-2rcnee1~stretch+20171005]

WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]

pkg:[firmware-ti-connectivity]:[20180825+dfsg-1rcnee1~stretch+20181217]

groups:[machinekit : machinekit adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev gpio pwm eqep admin spi tisdk weston-launch xenomai cloud9ide]

cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable]

dmesg | grep remote

[    0.885371] remoteproc remoteproc0: wkup_m3 is available

[    1.421143] remoteproc remoteproc0: powering up wkup_m3

[    1.421164] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217168

[    1.423355] remoteproc remoteproc0: remote processor wkup_m3 is now up

dmesg | grep pru

dmesg | grep pinctrl-single

[    0.704516] pinctrl-single 44e10800.pinmux: 142 pins, size 568

dmesg | grep gpio-of-helper

lsusb

Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver

Bus 001 Device 002: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

END

machinekit@beaglebone:~$

Thanks

[Charles Steinkuehler]

I believe you are having the same overlay problem as in this thread
(your eMMC boot loader is too old):

https://groups.google.com/d/msg/machinekit/fSgf7NFRNdE/X94DrfYEBwAJ

Try the fix proposed by Robert Nelson:

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

...and reboot.

>> cha...@steinkuehler.net <javascript:>
>>
>


--
Charles Steinkuehler
cha...@steinkuehler.net