Re: [Machinekit] Machinekit issue with config-pin on BBB

[Jim Craig]

On Thursday, April 9, 2020 at 6:55:22 PM UTC-5, Robert Nelson wrote:
>
>
> What user are you using when you do this? There should be a udev rule 
> kicking off the gpio class permiossoins... 
>
>
I am using machinekit as the username. I have changed the password from the 
default machinekit.
I created this user from the original debian image. I followed the steps 
located in this tutorial.
https://machinekoder.com/machinekit-debian-stretch-beaglebone-black/

looking at the udev rules it appears that they apply to users in the "gpio" 
group. My machinekit user is not in the "gpio" group. I tried to add this 
user to the "gpio" group using 

sudo su
usermod -aG gpio machinekit
exit

When i list groups the machinekit user is still not in the "gpio" group.

I read the group change is not immediately changed so a reboot is required. 
logout and login would also work.

After reboot machinekit is in the "gpio" group

After this machinekit runs with the CRAMPS.ini configuration. I commented 
out the eMMC pins that were set up for "servo" use.

Robert, thanks for the nudge in the right direction. ; )

Jim


-- 
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 machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/12d0cee8-e173-4daf-b484-bb7c4a620276%40googlegroups.com.

Re: [Machinekit] Travis CI builds of machinekit-cnc

[Cameron McQuinn]

Alright so I've been working on getting automated Docker container builds 
going, and I've run into a hiccup. As you mentioned, machinekit-cnc needs 
files from machinekit-hal to build, and the approach that I am taking to 
solve the problem is to build Docker containers for machinekit-cnc using 
the ones for machinekit-hal as a base, and installing the Debian packages 
generated from the mk-hal build into the mk-cnc containers. Here is where I 
run into a problem. The build needs header files that are provided by the 
machinekit-hal-dev package, which depends on machinekit-hal, but both 
packages provide /usr/bin/comp. When installing via apt-get install, apt 
detects that machinekit-hal-dev tries to overwrite /usr/bin/comp from 
machinekit-hal and aborts the install. This behavior can be mitigated for 
non sys_root environments by passing -o Dpkg::Options::="--force-overwrite" 
to apt. However, when those two packages are specified in a multistrap 
config, multistrap fails silently and does not install any of the 
machinekit packages.

I am not very familiar with Debian packaging, but noticed that the file 
debian/machinekit-hal.install in the mk-hal repo contains the 
line usr/bin/* which I assume sweeps up everything produced by the build 
under /usr/bin and puts it into the Debian package. Is there a way to 
exclude /usr/bin/comp from the machinekit-hal package so that we can 
install the machinekit-hal-dev package in multistrap systems?

You can follow along with what I have been doing at cmcquinn/machinekit-hal 
 and cmcquinn/machinekit-cnc 
.

Regards,
Cameron McQuinn

On Sunday, March 22, 2020 at 8:00:20 AM UTC-6, ce...@tuta.io wrote:
>
> Hi, 
> Mar 22, 2020, 03:09 by cameron...@gmail.com : 
>
> > What is the status of Travis CI builds for machinekit-cnc? I would love 
> to help get this going if needed. Let me know how I can help :) 
> > 
> The current status is that it is not working. And frankly have no idea if 
> it ever worked or was just left as a something from the original split into 
> separate repositories. I am currently trying to implement the CI/CD flow 
> based on Github Actions. (You can read about it here: 
> https://github.com/machinekit/machinekit-hal/issues/268 .) Main reason 
> for this is the higher limits for Open-Source project, it is simply in the 
> Github repository, so every fork will have it by default and Github will 
> store the artifacts for later download. 
>
> Of course, if somebody will implement Travis CI jobs, then that's good for 
> redundancy. 
>
> How I imagine it to work is following: The mk-cross-builder code was 
> integrated into Machinekit-HAL repository, so in given time some job will 
> build from it Debian images and store them in some repository (I am 
> thinking about Github Packages as it is directly connected to Github Git 
> repository and it is on one network with Github Actions workers). On this 
> will be constructed the Machinekit-HAL building and packaging. 
>
> Given that Machinekit-CNC needs for its build the Machinekit-HAL (some 
> info can be glanced from 
> https://github.com/machinekit/machinekit-cnc/pull/93 ), I was thinking 
> that Machinekit-CNC will add another onion layer to the Machinekit-HAL 
> created builder images with its own build dependencies and from this get 
> its own builder (or builder which will be capable of building both 
> Machinekit-HAL and Machinekit-CNC). 
>
> So what needs to be done is to rework the Debian packaging in 
> Machinekit-CNC ("debian" folder in root of the repository), build of the 
> specific Machinekit-CNC builder (so far it can just take the Machinekit-HAL 
> builder images from DockerHub) and the CI job. 
>
> If you have specific question, just ask. Here or on the Matrix chat. 
> Cern. 
>
> > 
> > Thanks, 
> > Cameron McQuinn 
> > 
> > -- 
> > 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 machi...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/0bca17f7-2840-483a-9fc1-63b5a3e642fb%40googlegroups.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 machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/d4a6d775-cb1c-4556-9cd2-807cbde080c7%40googlegroups.com.

Re: [Machinekit] Machinekit issue with config-pin on BBB

[Robert Nelson]

On Thu, Apr 9, 2020 at 6:19 PM Jim Craig  wrote:
>
> I am trying out Machinekit on the BBB. I am wanting to keep the HDMI output 
> on the board.
>
> I have the uEnv enable_uboot_cape_universal = 1
>
> I do not have an actual cape on the BBB at this time.
>
> I am trying to run the CRAMPS sample configuration. I am getting the 
> following error.
>
> sudo: no askpass program specified, try setting SUDO_ASKPASS
> Cannot write gpio direction file: /sys/class/gpio/gpio66/direction.
> CRAMPS.hal:12: program 'config-pin' failed, returned 1

What user are you using when you do this? There should be a udev rule
kicking off the gpio class permiossoins...

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 machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/CAOCHtYjEg1pF0xFNhHtJq1hy7YP-EEeTAX56iHCb96fvUhvh9g%40mail.gmail.com.

[Machinekit] Machinekit issue with config-pin on BBB

[Jim Craig]

I am trying out Machinekit on the BBB. I am wanting to keep the HDMI output 
on the board. 

I have the uEnv enable_uboot_cape_universal = 1

I do not have an actual cape on the BBB at this time.

I am trying to run the CRAMPS sample configuration. I am getting the 
following error.

sudo: no askpass program specified, try setting SUDO_ASKPASS
Cannot write gpio direction file: /sys/class/gpio/gpio66/direction.
CRAMPS.hal:12: program 'config-pin' failed, returned 1

In the CRAMPS.bbio file the first pin it tries to configure is P8_07 which 
equates to gpio66. If I comment out that line it gives the error for the 
next pin gpio67 or P8_08.

These pins should not be conflicting with the HDMI cape. 

What is the issue with this set of errors.

I do see something in the CRAMPS.hal file that concerns me after this. it 
says the following.

loadrt hal_bb_gpio output_pins=816,822,823,824,825,826,914,923,925 
input_pins=807,808,809,810,817,911,913

I don't understand why it is trying to set pins 822,823,824,825 as gpio. 
What are the "servo" signals used for that are connected to these pins. I 
don't see a purpose. Then you would not have to disable the eMMC.

Mainly looking for help on the SUDO_ASKPASS issue and not being able to 
write to the gpio pins using config-pin.

Thanks,

Jim

-- 
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 machinekit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/512ca30f-7940-4577-bb26-c3e2a17e23e2%40googlegroups.com.