Thanks jgnoss, it is true it is important. ~$ ls machinekit/configs/ARM.BeagleBone.CRAMPS/ 3D.postgui.hal autosave.halscope CRAMPS.bbio CRAMPS.ini pru-stepper.var README setup.sh ShuttleXpress. postgui.hal 3D.Temps.panel.xml CRAMPS2.hal CRAMPS.hal CRAMPS.ShuttleXpress.ini pru-stepper.var.bak setup2.sh ShuttleXpress.glade tool.tbl
If I do ls, all the files (ini, hal, bbio, setup.sh) are in the same folder. The rest of the files are test I have been doing. I think I have identified the problem. On the top of the CRAMPS.hal I have this lines: # Launch the setup script to make sure hardware setup looks good #loadusr -w /home/machinekit/machinekit/configs/ARM.BeagleBone.CRAMPS/setup.sh loadusr -w ./setup.sh loadusr -w config-pin -f ./CRAMPS.bbio I have commented out the config-pin line, and I have the same result previously explained. I think my config-pin is not working properly for the kernel distribution I am using (4.19). I found the correct OCPDIR and GPIODIR directories, but I couldn't figure out the SLOTS, I tried with the /lib/firmware directory. #!/bin/dash # Some important directories for use later OCPDIR=/sys/devices/platform/ocp/ocp* GPIODIR=/sys/class/gpio #SLOTS=/sys/devices/bone_capemgr.*/slots SLOTS=/lib/firmware If config-pin is not setting my setup, then hpg is not able to use the desired pins. Does it make sense? Does anyone using kernel 4.19? Thanks in advance. Finally my ootput to the shell script version.sh machinekit@beaglebone:~$ sudo /opt/scripts/tools/version.sh git:/opt/scripts/:[9599f8c47e18db5cdd36ee11355593ecdfe50979] eeprom:[A335BNLTEIA05116BBBK3FEC] model:[TI_AM335x_BeagleBone_Black] dogtag:[Machinekit Debian Image 2019-10-01] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-gf15b99f0b6 ]:[location: dd MBR] kernel:[4.19.72-bone-rt-r39] /boot/uEnv.txt Settings: 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.20190922.0-0rcnee0~stretch+20190922] 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 remoteproc admin spi tisdk weston-launch xenomai cloud9ide] cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root= /dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet] dmesg | grep remote [ 1.138401] remoteproc remoteproc0: wkup_m3 is available [ 1.380413] remoteproc remoteproc0: powering up wkup_m3 [ 1.380435] remoteproc remoteproc0: Booting fw image am335x-pm-firmware. elf, size 217168 [ 1.382520] remoteproc remoteproc0: remote processor wkup_m3 is now up dmesg | grep pru dmesg | grep pinctrl-single [ 0.760692] pinctrl-single 44e10800.pinmux: 142 pins, size 568 dmesg | grep gpio-of-helper [ 0.771665] gpio-of-helper ocp:cape-universal: ready lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub END Sergio Salinas > -- 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/4fbbc517-efc2-4b09-897c-532737974c30%40googlegroups.com.
