Re: [Machinekit] RT kernel problem on OrangePi+Armbian
On Mon, Aug 3, 2020 at 5:01 AM Albinas Bambukas wrote: > > Hello all, > > I have freshly installed Armbian Stretch > (Armbian_20.05.2_Orangepione_stretch_current_5.4.43.img.xz from here) running > on an OrangePi One. I've successfully installed Machinekit via the command > > sudo apt-get install machinekit-rt-preempt. > > However, installing a real time kernel (using command dpkg -i > linux-image-5.6.17-armv7-rt-x14_1stretch_armhf.deb) selected from > documentation causes the OrangePi not to boot (shows just a black screen > after rebooting). Sorry, I don't have an OrangePi, so that kernel is untested.. 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/CAOCHtYjcA7_nQQ4GEH9b%2BS-GKBb6V9w4fyHwn7r7r-f47KX%3Dsg%40mail.gmail.com.
Re: [Machinekit] Machinekit issue with config-pin on BBB
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.
Re: [Machinekit] Latest Image from elinux nonfunctional?
On Sat, Dec 21, 2019 at 7:42 AM Alice Crichton wrote: > > Hey guys > > Currently, I don't have the ability to set up my own image, so I went with > the Machinekit.io suggestion of just flashing the pre-existing file on > elinux. The current version (2019/12/16) I could not get fully functional for > the life of me, I got past the login easily enough, and then it just sits > there with the cursor indefinitely. I spent about two days working on it, > trying different things to get it to run, with no luck. This morning, after > working through the night I realized for the sake of a sanity check I should > flash other things to check if it was my process, and managed to install > Debian, and then I attempted to hunt for an older image to try. Me and a > friend searched for about an hour for something prebuilt, and couldn't find > any backdated ones, so eventually I resorted to Wayback Machine, and the next > closest I could find was from 2017. I got that one working with no trouble, > but it doesn't seem to have support for my board (CRAMPS) and is, I'm sure, > missing out on all the cool tech you guys have been working on for the past > two years. > > I know you guys are normally a little more intense than "I screwed up > installing" and I wouldn't want to be the annoying noob with the idiot > question, but I've been working on solving this for around 2.5 days and all > I've got seems to point to "Something is wrong with the latest prebuilt > image". I've worked with a few singleboard computers in the past, and I > worked in QA for software for a bit, so I'm trying my best to point at the > problem, but I don't have the linux chops to know exactly what's going wrong > here. My old Ubuntu machine fried around 6 years ago and I haven't had the > time or courage to go back since. The only other thing I can think of is the > (brand new) beaglebone was actually just ancient stock, and is no longer > supported by the current update? > > If anyone can point me in the right direction I'd be very grateful, I'm > already quite a ways into this project in both time and money, and was hoping > to have some steppers spinning by christmas. Currently there is no maintainer for the BeagleBone MachineKit image: Here is the config file, patches welcome.. https://github.com/beagleboard/image-builder/blob/master/configs/machinekit-debian-stretch.conf It still get's built once a week, as that part is automated. But as you can see, no one really boots or tests it anymore.. 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/CAOCHtYgt%2B-aOpqqDe73y64HJkRiAhtDnm_G6U_FqeT-M%3Dairuw%40mail.gmail.com.
Re: [Machinekit] Re: Broken CRAMPS.bbio
On Sat, Aug 31, 2019 at 9:52 PM c.glas...@cox.net wrote: > > > I remember the first time I loaded Linux. It was a Slackware 0.95 release. I > must have loaded it a dozen times before I got the hang of it. > > I find myself doing the same thing again, this time with various releases for > the BBB and Machinekit. Bone-debian-9.9-machinekit-armhf-2019-08-25-4gb > seems to be almost correct for my particular problem. Except ... > > Today I used config-pin and the results matched up with the CRAMPS.bbio file. > I'm even able to yank on a few pins and see the effect. Slow progress. In > earlier version from a few years ago I was able to use the led (P9_25) for > signaling. No more. > > It's very clear that at some fairly recent time a decision was made to muck > with P9_25. Why? > Further, calling up other configurations will break because > /sys/devices/platform/ocp/ocp:P9_25_pinmux no longer exists. That isn't very > nice. For some reason, that for me at least is completely obscure, this pin > was disabled. Will someone, anyone with a knowledge of the events around this > pin please comment. I would really like to know when so I can load up the > release just before that happened. P9.25 is hdmi audio.. 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/CAOCHtYg7WOWxAzbKsT628WKZHsSmk-ikJP5OD1mO8QN7aaq-Qg%40mail.gmail.com.
Re: [Machinekit] Re: Broken CRAMPS.bbio
On Wed, Aug 28, 2019 at 11:26 PM c.glas...@cox.net 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-2-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 machinekit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/CAOCHtYjKtnjuqOxH6hUsysESJfYEzGacNS1Y%3Do4q1%2B9cXHXvAw%40mail.gmail.com.
Re: [Machinekit] Re: Broken CRAMPS.bbio
On Wed, Aug 28, 2019 at 12:40 AM c.glas...@cox.net wrote: > > Commenting out > > uboot_overlay_addr0=/lib/firmware/cape-universal-00A0.dtbo > > Then > > machinekit@beaglebone:~$ machinekit > > MACHINEKIT - 0.1 > Machine configuration directory is > '/home/machinekit/machinekit/configs/ARM.BeagleBone.CRAMPS' > Machine configuration file is 'CRAMPS.ini' > Starting Machinekit... > rtapi_msgd command: /usr/libexec/linuxcnc/rtapi_msgd --instance=0 > --rtmsglevel=1 --usrmsglevel=1 --halsize=524288 > rtapi_app command: /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0 > io started > halcmd loadusr io started > Waiting for /sys/class/uio/uio0 > ... > > since CRAMPS.bbio has in the first few lines > > overlay cape-universal > overlay cape-bone-iio Comment these out, they are loaded by u-boot by default ps, run: sudo /opt/scripts/tools/version.sh It'll give more hints of what's loading.. 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/CAOCHtYjfN8PWWYZuK0L48PeyhZxSkxj0EhNkgZfWRj_M-us%3DEw%40mail.gmail.com.
Re: [Machinekit] Re: Broken CRAMPS.bbio
On Mon, Aug 26, 2019 at 11:07 PM c.glas...@cox.net wrote: > > On a BBB with a CRAMPS V1.0 board I re-flashed the onboard flash memory with > the latest release bone-debian-9.9-machinekit-armhf-2019-08-25-4gb. > > I then edited the /boot/uEnv.txt file to the following taking the measure to > remove the useless commented out lines for clarity > > #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 > > uname_r=4.19.59-bone-rt-r36 > enable_uboot_overlays=1 > uboot_overlay_addr0=/lib/firmware/cape-universal-00A0.dtbo ^ don't do that, you just broke things.. > disable_uboot_overlay_audio=1 > disable_uboot_overlay_wireless=1 > uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > enable_uboot_cape_universal=1 ^ this already enabled correctly, what you tried to do above.. 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/CAOCHtYj7GWUystr%3DseqvE-pZX6A8Fc00KedSreTdCknjEq7otQ%40mail.gmail.com.
Re: [Machinekit] Broken CRAMPS.bbio
On Sun, Aug 25, 2019 at 6:01 PM c.glas...@cox.net wrote: > > The CRAMPS.bbio file has a line commented out that drives a test led on the > CRAMPS board. > When this line is enabled by removing the # and run it provokes a series of > error messages starting with P9_25 pinmux file not found! > NOT GOOD!! > > I'm presently running the latest RCN release -- > bone-debian-9.9-machinekit-ARMhf-2019-06-30-4gb > > There is no doubt that all my troubles as noted in my post yesterday are > related to a broken pinmux definition. > > Would anyone care to point to a known good release? P9_25 is hdmi audio... Disable it in /boot/uEnv.txt https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices 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/CAOCHtYgj6KpgyAgE0wkVJnUMhTm5LduFyqp2UZ%3DSrPft92i%2BfQ%40mail.gmail.com.
Re: [Machinekit] testing hardware with halrun (on BBB)
> markus@machinekit:~$ sudo /opt/scripts/tools/version.sh > git:/opt/scripts/:[9df8deb6b2ae7570c9102ab58f795d3bed592194] > eeprom:[A335BNLT00C03818BBBK09B3] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[Machinekit Debian Image 2019-04-14] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2019.01-2-g6de8c74429]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2016.01-1-g4eb802e]:[location: dd MBR] The old version of u-boot on the eMMC is blocking things from working with overlays, retry after running: sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 and reboot. 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. Visit this group at https://groups.google.com/group/machinekit. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/CAOCHtYg5f8%3D%3DhD8KRZJubcMhXmLrwTMryKwJoLiENN9%2Bu8XW_Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: how to configure PRU pins ?
On Wed, May 1, 2019 at 5:03 PM Charles Steinkuehler
wrote:
>
> On 5/1/2019 4:21 PM, Robert Nelson wrote:
> > On Wed, May 1, 2019 at 4:12 PM Jon Elson wrote:
> >>
> >> OK, now I seem to have (maybe) got it! So, I put in :
> >> ###Custom Cape
> >> dtb_overlay=/lib/firmware/cape-universalh-00A0.dtbo
> >>
> >> And I seem to have both the uio_pruss module loaded, AND all the P8 pins
> >> available!
> >
> > So, you shouldn't have to force that overlay, as out of the box, we
> > have cape-universal auto-loading..
>
> Does U-Boot automatically change the universal overlay loaded when you
> disable on-board "capes" like the eMMC and HDMI?
That is correct, u-boot will pick the correct path based on the
enable/disables of the onboard devices set in /boot/uEnv.txt
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices
Now even more crazy then that, in v4.14.x-ti and v4.19.x-(all)+, we
merged in the cape-universal rewrite, that even when other random
overlays are loaded, the config-pin pinmux's will still show up..
This why all overlays now have a
Px_yz_pinmux { status = "disabled";}; section at the start:
https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAN0-00A0.dts#L31-L40
PS, a dynamic generated config-pin vs the classic static config-pin
then makes this work very well..
https://github.com/beagleboard/bb.org-overlays/tree/master/tools/pmunts_muntsos
( i have it set as default for buster, as it's not 100% compatible
with the classic config-pin output..)
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: how to configure PRU pins ?
On Wed, May 1, 2019 at 4:12 PM Jon Elson wrote: > > OK, now I seem to have (maybe) got it! So, I put in : > ###Custom Cape > dtb_overlay=/lib/firmware/cape-universalh-00A0.dtbo > > And I seem to have both the uio_pruss module loaded, AND all the P8 pins > available! So, you shouldn't have to force that overlay, as out of the box, we have cape-universal auto-loading.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: how to configure PRU pins ?
On Wed, May 1, 2019 at 4:04 PM Jon Elson wrote: > > > > On Wednesday, May 1, 2019 at 3:38:22 PM UTC-5, Robert Nelson wrote: >> >> >> No, it's a variable, last one get's set and used.. >> >> > OK, ever so SLOWLY, I'm starting to understand a little bit. > So, am I supposed to use the AM335X-PRU-UIO-00A0.dtbo WITH the > cape-universalh-00A0.dtbo ? > If so, how do I tell uboot to do that? Docs: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays "cape-universal" will be autoloaded by u-boot... As long as: "dtb=something.dtb" is NOT set and "enable_uboot_overlays=1" and "enable_uboot_cape_universal=1" is set.. Using: sudo /opt/scripts/tools/version.sh we can see the important bits of what you currently have set.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: how to configure PRU pins ?
On Wed, May 1, 2019 at 3:07 PM Jon Elson wrote: > > > > On Wednesday, May 1, 2019 at 2:50:24 PM UTC-5, Charles Steinkuehler wrote: >> >> >> You'll need to disable HDMI to use those PRU pins on P8: >> >> >> ...I think you then need to either load a different universal overlay >> or a second chunk of the overlay that will add support for those pins. >> >> > Yes, getting CLOSER!! So, I commented out the HDMI line, and then added > universalh right after the PRU-UIO overlay, like this: > uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > uboot_overlay_pru=/lib/firmware/cape-universalh-00A0.dtbo No, it's a variable, last one get's set and used.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: how to configure PRU pins ?
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2019.01-2-g6de8c74429]:[location: dd MBR] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2016.03-1-gd12d09f]:[location: dd MBR] There you go, eMMC bootloader is too old, thus blocking everything else.. sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 and reboot. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: how to configure PRU pins ?
On Fri, Apr 26, 2019 at 5:40 PM Jon Elson wrote: > > OK, just another test, i switched over to the > > uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo > > in uEnv.txt, and I still do not see uio_pruss in the lsmod listing. Now, > when I was tinkering with uEnv.txt, I did take out the > uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > line and replace it with my .dtbo file from another project, that JUST had > the pin mapping info. So, maybe some startup script noted there was no pruss > that could be started, and has set some variable somewhere that is preventing > pruss from starting now. I'm just guessing... > > Any suggestions to seeing why uio_pruss is not starting? Should be a message > somewhere. Hi Jon, Let's see the output of this script: sudo /opt/scripts/tools/version.sh 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: config-pin setting for Mode 0 (gpmc) question
On Fri, Apr 19, 2019 at 3:08 PM Jeff Pollard wrote: > > Hi, > That makes sense, but > > I can use config-pin to set the value to something like: > pwm > for example: > config-pin P8.14 pwm > will work just fine > as will gpio > and gpio_pd, etc. > > But, gpmc (mode 0) is not a valid choice i.e. config-pin p8.14 gpmc is > invalid > I tried adding it to the config-pin script for pin 8_14, but that didn't > help as it appears the problem is deeper than than. I can't change the value > of state in: > > /sys/devices/platform/ocp/ocp:P8_14_pinmux/state > > the error I get is: > > Cannot write pinmux File: /sys/devices/platform/ocp/ocp:P8_14_pinmux/state Hi Jeff, This is the first we've had anyone ask about gpmc. Right now the kernel overlay isn't setup to export the gpmc pinmux. Thus the error. Today, your best bet is to write an overlay to enable the gpmc pinmux. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Downloading APT Repos. and Packages from Machinekit Site - BBB Connected But Won't Download!
On Tue, Mar 26, 2019 at 5:25 AM Sardar Vayghannezgad wrote: > > Hi everyone. > I'm having a hrad time downloading the packages and whatnot. > > > My stats. > > root@beaglebone:/home/machinekit# uname -a > Linux beaglebone 3.8.13-xenomai-r83 #1 Thu Jan 5 01:32:32 UTC 2017 armv7l > GNU/Linux > > > root@beaglebone:/home/machinekit# hostnamectl >Static hostname: beaglebone > Icon name: computer > Machine ID: f4ee2c0f817c4a6e91d28c4d1c48a642 >Boot ID: 94201995500146bbaf62c8705208f177 > Operating System: Debian GNU/Linux 8 (jessie) > Kernel: Linux 3.8.13-xenomai-r83 > Architecture: arm > > > I am currently well on my way to have M.K on my BBB for using on my Windows > Desktop, but my problems are: > > I am not exactly sure which link is for me here. Since I'm using Jessie, 6,7 > and 8 on that link are out, right? (If so, what is that BBB in the 6.Debian > Stretch on armhf (BBB | RPi2/3 | Other armhf)? > What about #1-5? Does it matter that my Laptop Windows system, on which I > want to see my Machinekit interface, is 64-bit, Does that mean I should go > for #5. Debian Jessie on amd64? But, at the same time, I'm using Beaglebone > Black. Does this imply I download from 2.Debian Jessie on arm7 (BeagleBone) > Even if I attempt to download from whichever link, I can't seem to succeed; > this is what I get on my PuTTY: > root@beaglebone:/home/machinekit# sudo apt-key adv --keyserver > hkp://keyserver.ubuntu.com:80 --recv 43DDF224 > Executing: gpg --ignore-time-conflict --no-options --no-default-keyring > --homedir /tmp/tmp.DGANIHYx8U --no-auto-check-trustdb --trust-model always > --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg > --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg > --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg > --keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg --keyring > /etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg --keyring > /etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg > --keyring /etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg --keyring > /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring > /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring > /etc/apt/trusted.gpg.d/rcn-ee-archive-2015.gpg --keyserver > hkp://keyserver.ubuntu.com:80 --recv 43DDF224 > gpg: requesting key 43DDF224 from hkp server keyserver.ubuntu.com > gpg: keyserver timed out > gpg: keyserver receive failed: keyserver error It helps to actually "read" the error message, as it's telling you something important.. Now if you go to keyserver.ubuntu.com and enter 43DDF224 it'll also tell you: "No results found No results found: No keys found" Which should make it obvious that 43DDF224 doesn't exist on that keyserver.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] RE: Why are We Using an Older Kernel for the MachineKit for the BBB?
On Thu, Mar 14, 2019 at 4:27 PM Mala Dies wrote: > > Hello, > > I was just reading the github.com page for MachineKit. I see under Stretch, > we are supposed to get the binary files. > > ... > > Curious minds want to know. > > Seth > > P.S. I do not mind the prepackaged version. Do not misunderstand me. I was > just wondering. The "old" 3.8.x based image is well known.. It works as is, any updates and you are really on your own.. There is a newer image here, using v4.19.x-rt, it's just not as much utilzed.. https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#microSD.2FStandalone:_.28machinekit.29_Based_on_Debian_Stretch_with_4.19.x_rt_kernel_with_U-Boot_Overlays 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] How does machinekit test to see if it is running on a rt-preempt kernel?
On Tue, Feb 19, 2019 at 11:06 AM Robert Nelson wrote: > > On Tue, Feb 19, 2019 at 10:26 AM Condit Alan wrote: > > > > Schooner and Robert, > > > > OK, here is what I see when I run those tests. Rather than grep the results > > of uname -r, I just printed out uname -r. > > > > machinekit@beaglebone:~$ cat /sys/kernel/realtime > > cat: /sys/kernel/realtime: No such file or directory > > machinekit@beaglebone:~$ cat /boot/config-4.19.23-bone-rt-r22 | grep > > CONFIG_PREEMPT_RT_FULL=yes > > machinekit@beaglebone:~$ > > machinekit@beaglebone:~$ uname -a > > Linux beaglebone 4.19.23-bone-rt-r22 #1stretch Sat Feb 16 22:07:49 UTC 2019 > > armv7l GNU/Linux > > > > > > Actually looking at /boot/config-4.19.23-bone-rt-r22 here is what I found > > with respect to CONFIG_PREEMPT_* > > CONFIG_HAVE_PREEMPT_LAZY=y > > CONFIG_PREEMPT_NONE=y > > # CONFIG_PREEMPT_VOLUNTARY is not set > > # CONFIG_PREEMPT__LL is not set > > # CONFIG_PREEMPT_RTB is not set > > # CONFIG_PREEMPT_RT_FULL is not set > > Ah Crap, 22 builds into the v4.19.x branch and we missed that... > > https://github.com/RobertCNelson/bb-kernel/commit/b84cdf5a972d5e9f4347a37d6fa486ce92ab0c6b > > pushing to build farm right now. and now available: sudo /opt/scripts/tools/update_kernel.sh 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] How does machinekit test to see if it is running on a rt-preempt kernel?
On Tue, Feb 19, 2019 at 10:26 AM Condit Alan wrote: > > Schooner and Robert, > > OK, here is what I see when I run those tests. Rather than grep the results > of uname -r, I just printed out uname -r. > > machinekit@beaglebone:~$ cat /sys/kernel/realtime > cat: /sys/kernel/realtime: No such file or directory > machinekit@beaglebone:~$ cat /boot/config-4.19.23-bone-rt-r22 | grep > CONFIG_PREEMPT_RT_FULL=yes > machinekit@beaglebone:~$ > machinekit@beaglebone:~$ uname -a > Linux beaglebone 4.19.23-bone-rt-r22 #1stretch Sat Feb 16 22:07:49 UTC 2019 > armv7l GNU/Linux > > > Actually looking at /boot/config-4.19.23-bone-rt-r22 here is what I found > with respect to CONFIG_PREEMPT_* > CONFIG_HAVE_PREEMPT_LAZY=y > CONFIG_PREEMPT_NONE=y > # CONFIG_PREEMPT_VOLUNTARY is not set > # CONFIG_PREEMPT__LL is not set > # CONFIG_PREEMPT_RTB is not set > # CONFIG_PREEMPT_RT_FULL is not set Ah Crap, 22 builds into the v4.19.x branch and we missed that... https://github.com/RobertCNelson/bb-kernel/commit/b84cdf5a972d5e9f4347a37d6fa486ce92ab0c6b pushing to build farm right now. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Machinekit on BBB - long boot times with PREEMPT kernel
On Mon, Feb 11, 2019 at 4:39 PM mugginsac wrote: > > So, does that mean there will be a new Stretch-Machinekit image, or is it > just the new kernel for the moment? Please give this a shot: https://rcn-ee.net/rootfs/bb.org/testing/2019-02-11/stretch-machinekit/ ps, let me know what else you want installed in it by default. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Machinekit on BBB - long boot times with PREEMPT kernel
On Mon, Feb 11, 2019 at 12:25 PM Charles Steinkuehler wrote: > > On 2/4/2019 12:32 PM, Robert Nelson wrote: > > On Mon, Feb 4, 2019 at 6:36 AM Charles Steinkuehler > > wrote: > >> > >> On 2/4/2019 1:15 AM, Malte Schmidt wrote: > >>> Not yet. > >>> > >>> I asked the same question here: > >>> https://groups.google.com/forum/#!category-topic/beaglebone/beagleboardorg-beaglebone-black/wEv-JGvom8U > >>> > >>> and was suggested to go with 4.19. I tried this and it does indeed boot > >>> fast. The current issue is that I lack the PRU drivers (rproc) for this > >>> kernel. My next try would be to investigate if the rproc drivers can be > >>> replaced by the UIO version. > >>> ... and I totally don't know if this approach makes sense at all as I'm > >>> far > >>> from exactly knowing what I'm doing / using and how rproc or UIO differ > >>> > >> > >> Have you tried configuring U-Boot to load the UIO driver? > >> > >> Robert tries to keep this working with all kernel flavors so you > >> should just have to set: > >> > >> uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > >> > >> Details: > >> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_PRU_Options > > > > Sadly post v4.18.x the uio-pru driver on mainline is broken for > > "uio".. Around the same time Roger from TI posted his first pass at > > remoteproc for mainline, so I've been focusing on that instead. > > Looks like this just got fixed: > > https://groups.google.com/forum/#!msg/beagleboard/poKd5tCRD04/Zjc1hNxLAwAJ Yeap, Matthijs fixed it, the new "4.19.15-ti-rt-r8" should be available in a few hours.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Machinekit on BBB - long boot times with PREEMPT kernel
On Mon, Feb 4, 2019 at 6:36 AM Charles Steinkuehler wrote: > > On 2/4/2019 1:15 AM, Malte Schmidt wrote: > > Not yet. > > > > I asked the same question here: > > https://groups.google.com/forum/#!category-topic/beaglebone/beagleboardorg-beaglebone-black/wEv-JGvom8U > > > > and was suggested to go with 4.19. I tried this and it does indeed boot > > fast. The current issue is that I lack the PRU drivers (rproc) for this > > kernel. My next try would be to investigate if the rproc drivers can be > > replaced by the UIO version. > > ... and I totally don't know if this approach makes sense at all as I'm far > > from exactly knowing what I'm doing / using and how rproc or UIO differ > > Have you tried configuring U-Boot to load the UIO driver? > > Robert tries to keep this working with all kernel flavors so you > should just have to set: > > uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > > Details: > https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_PRU_Options Sadly post v4.18.x the uio-pru driver on mainline is broken for "uio".. Around the same time Roger from TI posted his first pass at remoteproc for mainline, so I've been focusing on that instead. RFC 2 was just posted today: https://marc.info/?l=linux-omap=154929024724527=2 PS, last week another user asked about uio on v4.19.x too.. So we have 2 users asking about it.. Last i looked at it we need to revert all the uio changes back down to v4.17.x... I don't think i'll have time to personally hack this up, (projects for Embedded World). I think zmatt on beagleboard irc was going to look at it. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] RT demon is not running. rtapi_app_main(rtapi): -22 Invalid argument ???
On Thu, Sep 13, 2018 at 12:18 PM Magnus Wiberg wrote: > > Is uio what is used in pru_generic.bin? > Shouldnt this take care of that then? > https://groups.google.com/forum/#!topic/beagleboard-x15/MfB-GMl0UYA > > Any suggestions on what I can do to get machinekit working? Or should I just > wipe it and start from scratch? Oh, i totally forgot about that.. i don't know then. ;) Just make sure you switch to the v4.14.x-rt kernel, the "non-rt" is installed by default in the x15 image 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] RT demon is not running. rtapi_app_main(rtapi): -22 Invalid argument ???
Based on the logs, this is an x15 right? fyi: There's no uio driver setup, only ti's remoteproc_pruss.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Xylotex.ini failing to run under Stretch
On Fri, Aug 31, 2018 at 10:55 AM schoone...@gmail.com wrote: > > On 31/08/18 16:19, Condit Alan wrote: > > Schooner, > > So I am trying to build a Machinekit system on Stretch. But I sort of > expected that the configs that were released on the Stretch image would at > least load > > > There is a basic lack of understanding of the process here > > The image is nothing to do with machinekit, it is released by RCN who is > an authority on BBB and all things ARM, but he just builds, or installs the > packages, for the current Machinekit. > > The configs were written or adapted by people using Xenomai on Wheezy most > likely. > > Doubtless many people have adapted them to run on rt-preempt and Stretch, > but no-one has submitted working configs for inclusion in the repo, so they > are not there. > I would take a look at the Replicape-Stretch dir: https://github.com/machinekit/machinekit/tree/master/configs/ARM/BeagleBone https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Replicape-Stretch/README.md and use that for comparison.. I think the old 3.8.13-bone xenomai will be the old default for awhile.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Xylotex.ini failing to run under Stretch
On Thu, Aug 30, 2018 at 5:55 PM Condit Alan wrote: > > I found a link talking about getting a CRAMPS board working with Stretch. It > said you need to replace > #PRUBIN=xenomai/pru_generic.bin > with > PRUBIN=rt-preempt/pru_generic.bin. > > Does that apply to the Xylotex DB25 cape also? > > I tried it in Xylotex.ini but the errors seemed to be the same either way. i thought that was fixed in git.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Xylotex.ini failing to run under Stretch
On Thu, Aug 30, 2018 at 1:33 PM Robert Nelson wrote: > > On Thu, Aug 30, 2018 at 1:20 PM mugginsac wrote: > > > > I got machinekit loaded to where I can pick the ini file to load. (I am > > running ssh -X machinekit@beaglebone.local.) > > > > I chose Xylotex under ARM.BeagleBone.Xylotex. Is that the correct ini file > > to load for a Xylotex DB25 cape? > > > > Do Xylotex.ini and Xylotex.hal need some changes to run under Stretch? > > > > It reported a failure on executing setup.sh. > > > > MACHINEKIT - 0.1 > > Machine configuration directory is > > '/home/machinekit/machinekit/configs/ARM.BeagleBone.Xylotex' > > Machine configuration file is 'Xylotex.ini' > > Starting Machinekit... > > rtapi_msgd command: /usr/libexec/linuxcnc/rtapi_msgd --instance=0 > > --rtmsglevel=1 --usrmsglevel=1 --halsize=524288 > > rtapi_app command: /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0 > > io started > > emc/iotask/ioControl.cc 768: can't load tool table. > > halcmd loadusr io started > > grep: /sys/devices/bone_capemgr.*/slots: No such file or directory > > Loading cape-universal overlay > > bash: /sys/devices/bone_capemgr.*/slots: No such file or directory > > Error loading device tree overlay file: cape-universal > > ps, you can debug u-boot via: > > sudo /opt/scripts/tools/version.sh > > cape-universal is "auto" loaded in u-boot, thus "bone_capemgr" doesn't > apply anymore.. > > config-pin is enabled out of the box.. > > What pins do the Xylotex use? > > Just remember to disable internal hardware devices you don't need > (audio/hdmi/etc)... > > https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices nuke these lines: https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Xylotex/setup.sh#L34-L51 and use: uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo in /boot/uEnv.txt 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Xylotex.ini failing to run under Stretch
On Thu, Aug 30, 2018 at 1:20 PM mugginsac wrote: > > I got machinekit loaded to where I can pick the ini file to load. (I am > running ssh -X machinekit@beaglebone.local.) > > I chose Xylotex under ARM.BeagleBone.Xylotex. Is that the correct ini file to > load for a Xylotex DB25 cape? > > Do Xylotex.ini and Xylotex.hal need some changes to run under Stretch? > > It reported a failure on executing setup.sh. > > MACHINEKIT - 0.1 > Machine configuration directory is > '/home/machinekit/machinekit/configs/ARM.BeagleBone.Xylotex' > Machine configuration file is 'Xylotex.ini' > Starting Machinekit... > rtapi_msgd command: /usr/libexec/linuxcnc/rtapi_msgd --instance=0 > --rtmsglevel=1 --usrmsglevel=1 --halsize=524288 > rtapi_app command: /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0 > io started > emc/iotask/ioControl.cc 768: can't load tool table. > halcmd loadusr io started > grep: /sys/devices/bone_capemgr.*/slots: No such file or directory > Loading cape-universal overlay > bash: /sys/devices/bone_capemgr.*/slots: No such file or directory > Error loading device tree overlay file: cape-universal ps, you can debug u-boot via: sudo /opt/scripts/tools/version.sh cape-universal is "auto" loaded in u-boot, thus "bone_capemgr" doesn't apply anymore.. config-pin is enabled out of the box.. What pins do the Xylotex use? Just remember to disable internal hardware devices you don't need (audio/hdmi/etc)... https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] BBB not booting from bone-debian-9.5-machinekit-armhf-2018-08-20-4gb.img.xz
On Thu, Aug 30, 2018 at 9:27 AM Lang Gu wrote: > > Oh, sorry , I have no serial device now。。 > > Is there any other way? Do you have a 2nd beagle? Otherwise: https://elinux.org/Beagleboard:BeagleBone_Black_Serial 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] BBB not booting from bone-debian-9.5-machinekit-armhf-2018-08-20-4gb.img.xz
On Thu, Aug 30, 2018 at 9:22 AM Lang Gu wrote: > > Hi,Robert , > > When I used sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 > > i find my BBB can not start without SDcard(my BBB sys is debian 7.5 2G eMMC > ), > > but I insert SDcard(brun debian 8.7 machinekit 2017-02-12) can start > (debian 8.7) > > when I burn debian 9.X into SDcard and insert to BBB , it's still can not > start . sometimes 4 LED bright。。 serial log? 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] BBB not booting from bone-debian-9.5-machinekit-armhf-2018-08-20-4gb.img.xz
On Wed, Aug 29, 2018 at 10:45 AM Condit Alan wrote: > > Robert, > > After I wrote the last message I found the “Boot” button on the picture. The > problem is that it is under the DB25 cape. So that just leaves erasing the eMMC's version of u-boot: sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] BBB not booting from bone-debian-9.5-machinekit-armhf-2018-08-20-4gb.img.xz
On Tue, Aug 28, 2018 at 8:46 PM mugginsac wrote: > > I am trying to boot and log in over ethernet with ssh -X > machinekit@beaglebone.local. This works with the 2017-02-12 image uSD. > I used Etcher to flash both the 2017-02-12 image and the 2018-08-20 image to > uSD. With the 2018-08-20 uSD I am seeing the outboard three of four LEDs go > solid blue. The inboard LED of the four is not lighting. However, they just > stay solid -- no flashing. > With the 2017/2/12 image the 4 LEDs go solid and then I see the typical > flashing during the boot process. > > Is there a problem with the 8/20 image? > > I am running this on an A6 BBB but I also tried it on a A5C BBB. Same results > on both. I have a Xylotex DB25 cape on the board. Hold down the "boot" button, your board just has a version of u-boot (really old) in the eMMC that's doesn't understand the newer boot scripts.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Can't install machine kit on Beagle Bone stock image
On Wed, May 16, 2018 at 10:39 AM, Eric <ericschi...@gmail.com> wrote: > I'm guessing that updating the kernel on the Machinekit image isn't as > trivial as installing an app? (can you tell I'm new to Linux! :) > > Where would I find Robert Nelson? The image with 3.8.13-xenomai, don't bother trying to update it to 4.14.x-rt so you can get wifi working.. Instead use a later stretch build: https://rcn-ee.net/rootfs/bb.org/testing/2018-04-22/stretch-machinekit/ Currently there's a high cpu load issue on v4.14.x, we think we figured it out, but it involves switching from: CONFIG_PREEMPT_RT_FULL -> CONFIG_PREEMPT_RTB So it might not work with machinekit's rt requirements... 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] BeagleBone Black overlays
Hi John, On Sat, Mar 3, 2018 at 10:59 PM, John Morris <j...@zultron.com> wrote: > I'm having a heck of a time getting overlays working on the BBB with RCN's > 2018-02 MK image. I'm weak on the concepts to begin with, and here's what > I've done. > > With the stock `/boot/uEnv.txt`, most pins aren't already assigned to any > cape: > > machinekit@beaglebone:~$ config-pin P9.18 lo > P9_18 pinmux file not found! > Pin has no cape: P9_18 > machinekit@beaglebone:~$ ls -d /sys/devices/platform/ocp/ocp:P* > /sys/devices/platform/ocp/ocp:P9_19_pinmux > /sys/devices/platform/ocp/ocp:P9_20_pinmux > > Trying to load the universal cape with `config-pin overlay cape-universal` > dumps a huge list of errors to the console and kernel oopses on the 4.14 > kernel. On the 4.4 kernel, the pins seem to appear in > `/sys/devices/platform/ocp/ocp:P*`, but `config-pin P9.18 lo` says "WARNING: > GPIO pin not exported, cannot set direction or value!". So I don't do that. > > Instead, I compile and install a .dts file with just the wanted pins, and > add the line `uboot_overlay_addr0=/lib/firmware/bb_autoclave-00A0.dtbo` to > `/boot/uEnv.txt`. This doesn't seem to assign any pins, but I'm unclear > whether it's a bad file or something else. > > > https://github.com/zultron/autoclave_control/blob/master/etc/bb_autoclave.dts > > Compiling produces no unexpected errors: > >> machinekit@beaglebone:~$ sudo dtc -O dtb -o >> /lib/firmware/bb_autoclave-00A0.dtbo -b 0 -@ etc/bb_autoclave.dts >> /lib/firmware/bb_autoclave-00A0.dtbo: Warning (unit_address_vs_reg): >> Node /fragment@0 has a unit name, but no reg property > > > > Maybe this is meaningful; the Linux 4.14 version: > >> machinekit@beaglebone:~$ sudo /opt/scripts/tools/version.sh >> git:/opt/scripts/:[ad016da40de5805f1a6f981cbb6c454b1a7f244b] >> eeprom:[A335BNLT0A5A1513BBBK3416] >> model:[TI_AM335x_BeagleBone_Black] >> dogtag:[Machinekit Debian Image 2018-02-04] >> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot >> 2018.01-2-g9aa111a004] >> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot >> 2015.01-1-gb2412df] Your old eMMC is blocking U-Boot Overlays: sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10 >> kernel:[4.14.16-ti-rt-r30] >> uboot_overlay_options:[enable_uboot_overlays=1] >> >> uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/bb_autoclave-00A0.dtbo] >> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo] >> uboot_overlay_options:[enable_uboot_cape_universal=1] 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 cape-univesal: 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 Step 3: in your overlay add a new fragment@0 section like this, but with the pins your "bb_autoclave" uses: https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BONE-4D4C-01-00A1.dts#L16-L53 >> pkg:[bb-cape-overlays]:[4.4.20180126.0-0rcnee0~stretch+20180126] >> pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~stretch+20180104] >> pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830] >> groups: �‘debian�’: no such user opps, i need to check for machinekit too.. >> groups:[] >> dmesg | grep pinctrl-single >> [1.409569] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 >> size 568 >> dmesg | grep gpio-of-helper >> [1.411448] gpio-of-helper ocp:cape-universal: ready >> END > > > The Linux 4.4 version, slightly different: > >> root@beaglebone:/home/machinekit# sudo /opt/scripts/tools/version.sh >> [...] >> kernel:[4.4.113-ti-rt-r147] >> [...] >> dmesg | grep gpio-of-helper >> [1.511377] gpio-of-helper ocp:cape-universal: Allocated GPIO id=0 >> [1.511589] gpio-of-helper ocp:cape-universal: Allocated GPIO id=1 >> [1.511604] gpio-of-helper ocp:cape-universal: ready >> END > > > So who knows what dumb thing I'm missing? Thanks! > > John > > -- > 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 grou
Re: [Machinekit] Beaglebone Black I2C question
On Thu, Feb 22, 2018 at 1:00 PM, Stefano Schmidt <stefano.schmidt.un...@gmail.com> wrote: > I'd like to know if it's possible to use the I2C2 ( P9.19 & P9.20 ) sharing > the bus with the configuration EEPROM and other devices (e.g. a GPIO > expander)? Yes any 3.3v i2c device can be directly plugged in.. in later kernel/images's, those pins are even available to you to mux to gpio/can/etc.. thru config-pin.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] machinekit kernel sources??
On Fri, Feb 16, 2018 at 1:45 PM, 'schooner30@btinternet' via Machinekit <machinekit@googlegroups.com> wrote: > You should find the source package in the repo has the full source files > > http://deb.machinekit.io/debian/pool/main/l/linux/linux_3.8.13.orig.tar.xz > > Don't bother trying to use apt, just download from the http link and > unarchive it > > The config file distributed with the kernel should be able to be renamed > .config in the source tree root dir and you have the build setup that > produced the kernel in the package Those files are out of date for that kernel: linux_3.8.13-12~1jessie~1da.debian.tar.xz 2016-03-04 11:051.7M linux_3.8.13-12~1jessie~1da.dsc 2016-03-04 11:051.8K linux_3.8.13-12~1wheezy~1da.debian.tar.xz 2016-03-04 11:051.7M linux_3.8.13-12~1wheezy~1da.dsc 2016-03-04 11:051.8K linux_3.8.13.orig.tar.xz 2016-03-04 11:0568M 3.8.13-xenomai-r83 was tagged: https://github.com/RobertCNelson/bb-kernel/commits/3.8.13-xenomai Jan 4, 2017 10 months later.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] machinekit kernel sources??
On Fri, Feb 16, 2018 at 1:18 PM, Damien D <damien.d...@gmail.com> wrote: > Hi, > > I'm using this working machinekit image: > https://rcn-ee.com/rootfs/bb.org/testing/2017-02-12/machinekit/ > > As you might know, this kernel have some USB hot plug issue and I have a > patch for it that I would like to apply. > > For that I need to (re)compile the kernel and maybe also kernel modules > (including those from machinekit?).. > > At the moment I'm stuck at the easiest part, I cannot find/don't know where > to look the exact sources that have been used to build the kernel within the > image I'm using. > > Does anyone know where I can find sources that have been used to > produce the kernel (3.8.13-xenomai-r83) that is in this image? or even for > the all rootfs image? Use yakbuild: https://github.com/RobertCNelson/yakbuild Follow the readme and use the "recipe.sh.v3.8.x.sample" sample.. kernel_tag="3.8.13-xenomai-r83" run: ./build_kernel.sh the build after you exit out of menuconfig apply your patch to ./KERNEL/ Then run: ./tools/rebuild.sh 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] MK with touch screen
On Fri, Jan 26, 2018 at 10:44 AM, gary <garybur...@gmail.com> wrote: > https://www.adafruit.com/product/3396 > > Has anyone tried this touchscreen with BBB and cramps or is there a pin > conflict > if no conflicts any suggestions on how to get it going it's a 16bit screen, here's the pin's used: https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAPE-DISP-CT4-00A0.dts 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black
On Mon, Dec 25, 2017 at 10:56 AM, TJoseph Powderly <tjt...@gmail.com> wrote: > Robert > sorry prev post used MachineKoder's image not yours, > (i have too many cf's here attempting to get the job done, my bad) > i will make clean images from your latest > https://rcn-ee.net/rootfs/bb.org/testing/2017-12-24/stretch-machinekit/bone-debian-9.3-machinekit-armhf-2017-12-24-4gb.img.xz > and report back > thanks tomp Yeah no eMMC is showing up.. Either your eMMC has completely failed, or you have a cape plugged into the pins used to communicate with the eMMC.. You have nothing plugged into P8/P9 right? 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black
On Mon, Dec 18, 2017 at 10:35 AM, TJoseph Powderly <tjt...@gmail.com> wrote: > Hello > yes i have usb to serial ( db9) adapters that i use to talk to old cnc > machines with newer laptops > i dont know how to use it with BBB. > I suspect you mean something else, > where can i read about it? Make sure it's a 3.3v one.. Plug it into J1, pinout listed here: https://elinux.org/Beagleboard:BeagleBone_Black_Serial fire up tio/screen/gtkterm/etc and just log the serial output from the flasher.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black
On Mon, Dec 18, 2017 at 9:56 AM, TJoseph Powderly <tjt...@gmail.com> wrote: > Hello > here is result ( ssh'd in with debian:temppwd ) > """ > debian@beaglebone:~$ cat /boot/uEnv.txt > #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 > > uname_r=4.9.67-ti-r82 > #uuid= > #dtb= > > > ###U-Boot Overlays### > ###Documentation: > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > ###Master Enable > enable_uboot_overlays=1 > ### > ###Overide capes with eeprom > #uboot_overlay_addr0=/lib/firmware/.dtbo > #uboot_overlay_addr1=/lib/firmware/.dtbo > #uboot_overlay_addr2=/lib/firmware/.dtbo > #uboot_overlay_addr3=/lib/firmware/.dtbo > ### > ###Additional custom capes > #uboot_overlay_addr4=/lib/firmware/.dtbo > #uboot_overlay_addr5=/lib/firmware/.dtbo > #uboot_overlay_addr6=/lib/firmware/.dtbo > #uboot_overlay_addr7=/lib/firmware/.dtbo > ### > ###Custom Cape > #dtb_overlay=/lib/firmware/.dtbo > ### > ###Disable auto loading of virtual capes (emmc/video/wireless/adc) > #disable_uboot_overlay_emmc=1 > #disable_uboot_overlay_video=1 > #disable_uboot_overlay_audio=1 > #disable_uboot_overlay_wireless=1 > #disable_uboot_overlay_adc=1 > ### > ###PRUSS OPTIONS > ###pru_rproc (4.4.x-ti kernel) > #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo > ###pru_uio (4.4.x-ti & mainline/bone kernel) > uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo > ### > ###Cape Universal Enable > enable_uboot_cape_universal=1 > ### > ###Debug: disable uboot autoload of Cape > #disable_uboot_overlay_addr0=1 > #disable_uboot_overlay_addr1=1 > #disable_uboot_overlay_addr2=1 > #disable_uboot_overlay_addr3=1 > ### > ###U-Boot fdt tweaks... > #uboot_fdt_buffer=0x6 > ###U-Boot Overlays### > > cmdline=coherent_pool=1M net.ifnames=0 quiet > > #In the event of edid real failures, uncomment this next line: > #cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e > > ##Example v3.8.x > #cape_disable=capemgr.disable_partno= > #cape_enable=capemgr.enable_partno= > > ##Example v4.1.x > #cape_disable=bone_capemgr.disable_partno= > #cape_enable=bone_capemgr.enable_partno= > > ##enable Generic eMMC Flasher: > ##make sure, these tools are installed: dosfstools rsync > #cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh > > debian@beaglebone:~$ > """ Thanks! /boot/uEnv.txt is perfect... Do you have a usb-serial adapter, and can you log the serial boot sequence leading up the error in the flasher? 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] help upgrading to latest 4.14 kernel machinekit image
> https://rcn-ee.com/repos/debian/pool/main/l/linux-upstream/ > I'm not sure if it's missing or perhaps not needed with this kernel version "in-kernel" firmware got nuked in v4.14.x mainline.. So no more special package with blobs we don't use.. > I was going to ask which is better to use bone-rt or ti-rt > I'm not sure what the differences are, but looking at the thread it looks > like ti-rt is preferred > although bone-rt does have a firmware image for 4.13 > linux-firmware-image-4.13.16-bone-rt-r3_1stretch_armhf.deb > (perhaps these are not needed for 4.14 I'm unsure) Give "4.14.6-bone-rt-r10" a shot, the RT guys just published a few fixes last friday and that version has the latest, inluding a fix for hte bbb... (that fix won't get rolled into v4.14.x-ti till tomorrow when i'm at work..) https://patchwork.kernel.org/patch/10115425/ 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] help upgrading to latest 4.14 kernel machinekit image
On Fri, Dec 15, 2017 at 8:55 AM, <j...@allwinedesigns.com> wrote: > I'm flashing the 4.14 TI RT kernel that Robert linked earlier. I'll let you > know how it goes. Where is the image of the 4.4 TI RT kernel that you'd like > me to try? Or is there an easy what to switch out the kernel for the image I > have? Hi John, v4.14-ti-rt: sudo /opt/scripts/tools/update_kernel.sh --ti-rt-channel --lts-4_14 v4.4.x-ti-rt --lts-4_4 v4.9.x-ti-rt --lts-4_9 Once a kernel deb files get's installed it just a matter of changing: uname_r in /boot/uEnv.txt to swap between versions.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] help upgrading to latest 4.14 kernel machinekit image
On Thu, Dec 14, 2017 at 2:22 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Thu, Dec 14, 2017 at 2:16 PM, <j...@allwinedesigns.com> wrote: >> Found this in dmesg: >> [ 30.418037] pinctrl-single 44e10800.pinmux: pin PIN103 already requested >> by 48038000.mcasp; cannot claim for 4a30.pruss >> [ 30.580322] pinctrl-single 44e10800.pinmux: pin-103 (4a30.pruss) >> status -22 >> [ 30.692649] pinctrl-single 44e10800.pinmux: could not request pin 103 >> (PIN103) from group foo_pins on device pinctrl-single >> >> Looks like P9.28 is used by something else. What is mcasp? PS, i've just added this to the version.sh check.. On a normal boot when all overlays are correctly combined, it'll only show: [2.340306] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 https://github.com/RobertCNelson/boot-scripts/commit/66e6b465c450a03cc0060589deb163fc5577a476 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] help upgrading to latest 4.14 kernel machinekit image
On Thu, Dec 14, 2017 at 2:16 PM, <j...@allwinedesigns.com> wrote: > Found this in dmesg: > [ 30.418037] pinctrl-single 44e10800.pinmux: pin PIN103 already requested > by 48038000.mcasp; cannot claim for 4a30.pruss > [ 30.580322] pinctrl-single 44e10800.pinmux: pin-103 (4a30.pruss) > status -22 > [ 30.692649] pinctrl-single 44e10800.pinmux: could not request pin 103 > (PIN103) from group foo_pins on device pinctrl-single > > Looks like P9.28 is used by something else. What is mcasp? P9.28 is hdmi audio add: disable_uboot_overlay_audio=1 to /boot/uEnv.txt 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] help upgrading to latest 4.14 kernel machinekit image
On Thu, Dec 14, 2017 at 2:02 PM, <j...@allwinedesigns.com> wrote: > Thanks Bas! I've attached a more verbose log. It looks like it's something > PRU related. Dec 14 19:59:25 pocketnc rtapi:0: 4:rtapi_app:2498:user hpg: module 'uio_pruss' already loaded Dec 14 19:59:25 pocketnc rtapi:0: 1:rtapi_app:2498:user hpg: ERROR: failed to initialize PRU Dec 14 19:59:25 pocketnc rtapi:0: 4:rtapi_app:2498:user halg_exit:293 HAL: removing component 686 'hal_pru_generic' Dec 14 19:59:25 pocketnc rtapi:0: rtapi_app_main(hal_pru_generic): -1 Operation not permitted Dec 14 19:59:25 pocketnc rtapi:0: 1:rtapi_app:2498:user rtapi_app_main(hal_pru_generic): -1 Operation not permitted Dec 14 19:59:25 pocketnc rtapi:0: 4:rtapi_app:2498:user pid=2498 flavor=rt-preempt gcc=4.9.2 git=v0.1~-detached~50f3952 That's a little odd.. already loaded/failed to initialize... 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] help upgrading to latest 4.14 kernel machinekit image
On Thu, Dec 14, 2017 at 12:37 PM, John Allwine <j...@allwinedesigns.com> wrote: > Looks like it: > git:/opt/scripts/:[ef2c5982e3788e07d9ec4a3d23089dc5e5a3f9cd] > eeprom:[A335BNLT000C1625BBBG0497] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[Machinekit Debian Image 2017-12-10] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot > 2018.01-rc1-2-g87ef84] > kernel:[4.14.4-bone-rt-r7] > nodejs:[v4.8.7] > uboot_overlay_options:[enable_uboot_overlays=1] > uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/PocketNCdriver-00A0.dtbo] > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo] > uboot_overlay_options:[enable_uboot_cape_universal=1] > pkg:[bb-cape-overlays]:[4.4.20171207.0-0rcnee1~jessie+20171207] > pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~jessie+20170829] > pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~jessie+20170830] Okay everything is setup correctly in u-boot/kernel for using the pru over uio... is there a way to enable more verbosity in the linuxcrc log file.. rtapi_app_main(hal_pru_generic): -1 Operation not permitted 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] help upgrading to latest 4.14 kernel machinekit image
On Thu, Dec 14, 2017 at 12:16 PM, <j...@allwinedesigns.com> wrote: > Here at Pocket NC we locked on an old version of machinekit running the 3.8 > kernel when we launched our machine a couple years ago. It runs on the > Beaglebone Black. I only recently came onboard and have been trying to get > up to speed with the configuration while wrangling different pieces of > software together to get a web interface going on the machine. It all works > on the old version of machinekit. I am working on upgrading to a newer > version of machinekit and am running into problems. > > When I try the latest 3.8 image built for the BBB I run into problems with > the Xenomai kernel: https://github.com/machinekit/machinekit/issues/1332 > > Ideally, we could make the jump to the latest 4.14 kernel image, but I'm > unsure what changes need to be made. Kernel 4.14 uses U-boot for loading > overlays, so I've added our device tree overlay to /boot/uEnv.txt to load it > at boot. In the old setup, there is a setup.bridge.sh file that loads the > overlays and does some checks for analog pins and pru control files. I've > commented all of that out, but I'm not sure what should replace them or if I > even need to (I've attached the current state of the file). Right now when I > try to start machinekit I get "rtapi_app_main(hal_pru_generic): -1 Operation > not permitted". I'm not sure where to go from here. I've attached the files > that I think are pertinent (which are the only changes that I've made to the > whole configuration, which is here: https://github.com/PocketNC/pocketnc). > Any help you can offer is appreciated! Is the pru overlay loading??? Double check with: sudo /opt/scripts/tools/version.sh PS, Alexander Rössler is having better luck with the v4.14.x-ti-rt vs v4.14.x-bone-rt There's a test image here: https://rcn-ee.net/rootfs/bb.org/testing/2017-12-12/stretch-machinekit/ 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] BBB MachineKit Image doesn't launch from desktop (ok from command line)
Hi Jerry, On Thu, Nov 9, 2017 at 3:04 PM, Jerry Trantow <jerry.tran...@gmail.com> wrote: > Working from the 10/28 microSD/Standalone: (machinekit) Based on Debian > Jessie with 4.13.x kernel with U-Boot Overlays > I have been able to get the ARM.BeagleBone.Prototix configuations to work > from the command line with Axis. The configs also work with the remote > client Cetus and MachineFace. > I didn't worry about this while debugging but now I would like to commit my > changes. Before I commit I wanted to test several use cases. Using the > desktop menu, I get nothing when I try to start MachineKit??? The Latency > Test and PNC config menu items work. But not Machinekit itself. > > I'm 95% sure this was the case with the basic MachineKit image. When it > didn't work, I started using the command line and haven't gone back to > desktop until today. I don't see any debug *.txt files in home. For the new images using "RT" and v4.x+ kernel's i've elected to rip out most of x11. On the am335x, we just don't have the horsepower for any fancy graphic's. Since we also lose a little bit with moving from 3.8.13-xenomai -> 4.x-rt+ kernel, i figured a mostly headless setup, would be a better choice. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW
On Mon, Nov 6, 2017 at 10:34 AM, Daren Schwenke <darenschwe...@gmail.com> wrote: > > > On Monday, November 6, 2017 at 11:04:43 AM UTC-5, Daren Schwenke wrote: >> >> >> >> On Monday, November 6, 2017 at 8:37:21 AM UTC-5, Charles Steinkuehler >> wrote: >>> >>> That processor is supposed to have the PRUs, so I'm not sure what's >>> going wrong. I don't have a BBGW to test with, but I think some other >>> folks have worked with this board and didn't run into any unusual >>> problems. > > I did find other instances of people using the BBGW, but in all cases they > had disabled or didn't have a kernel suitable for enabling the wifi so that > they could use the regular capes. > None of the regular capes will work with the BBGW wifi enabled as the pins > it uses steps on all of them somewhere. > To have wifi enabled requires > 3.8 kernel and using the rt-preempt. You could make 3.8 work on the bbgw (with wifi), it's just not something i was going to waste any time on.. you'd also have to back port "gpio-hogs": https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am335x-bonegreen-wireless.dts?h=v4.14-rc8#n116 Otherwise, wifi will only work on 2nd boot, and then sometimes not at all.. As the wl18xx likes to enter a special test mode with that pin floating.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] MachineKit Install directions (Cape, U-boot, Device Tree Overlay confusion)
On Fri, Nov 3, 2017 at 3:22 AM, Alexander Rössler <alexander@roessler.systems> wrote: > I would love to see the setup.sh files converted to config-pin bbio > files as here: > https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/MendelMax-CRAMPS/CRAMPS.bbio > > This format is kernel independent and even editable with a graphical > editor: https://github.com/machinekoder/BBIOConfig > > else we have the exactly same problem again with the next incompatible > device tree change. > > I have create an issue for this problem: > https://github.com/machinekit/machinekit/issues/1310 > > I think, this would be a great task to solve by someone new who wants to > contribute to Machinekit. I see a potential problem with 3.8 -> 4.4.x+ here: P9_28 spi #SPI CS0 P9_29 spi #SPI MISO P9_30 spi #SPI MOSI P9_31 spi #SPI SCLK P9_41 low #FET 5 P9_42 spics #SPI CS1 P9_29/P9_30 are fine as "spi" but the CSx and SCLK pins are now: spi_cs spi_sclk as usually the spi_cs modes are shared with spi_sclk on the same pin.. considering config-pin loads the bbio file i could fix it up in config-pin.. ;) But just a heads up... 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] MachineKit Install directions (Cape, U-boot, Device Tree Overlay confusion)
On Wed, Nov 1, 2017 at 1:45 PM, Jerry Trantow <jerry.tran...@gmail.com> wrote: > Thanks, disable_uboot_overlay_audio=1 fixed the problems with all (P9_25, > P9_28, P9_29, P9_31) the GPIO assignment in setup.sh. But, I'm still failing > with: > > MACHINEKIT - 0.1 > Machine configuration directory is > '/home/machinekit/machinekit/configs/ARM.BeagleBone.Probotix' > Machine configuration file is 'Comet_Metric.ini' > Starting Machinekit... > io started > Unrecognized line skipped: POC FMS LEN DIAMCOMMENT > halcmd loadusr io started > Skip cape-universal overlay load with kernel >3.8. > Comet.hal:20: insmod failed, returned -1: > rtapi_app_main(hal_pru_generic): -1 Operation not permitted Which module is it trying to load via "insmod"... 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit package repo
On Sun, Oct 29, 2017 at 11:12 AM, Lewis Cobb <lewishc...@gmail.com> wrote: > Hi Robert > > I've imaged a new SD Card and just poked it into the BBB. Below are the > results of your instructions to run the "version.sh" script - > > Couple of questions come to mind - it appears that the eMMc is doing the > actual booting and not the SD card, and not wanting to erase the eMMC, I am > wondering - if we monkey with the eMMC with this new image - does that mean > I can't go back to the exsiting SD card I am using now with the older > version of things on it? It appears from this that the uboot overlays are > enabled, yes? Yeah, if you clear out the eMMC, you can just swap microSD card's to test different version.. > --- > > machinekit@beaglebone:/$ sudo /opt/scripts/tools/version.sh > git:/opt/scripts/:[6c2688b0be448b7bb9ca18849b430d496a84acb4] > eeprom:[A335BNLT00C02916BBBK0A3C] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[Machinekit Debian Image 2017-10-26] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2017.09-2-g0f3f1c7907] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.10-1-g143c9ee] To use the new U-Boot overlays, you'll have to remove this "old" bootloader from eMMC.. sudo dd if=/dev/zero of=/dev/mmcbkl1 count=1 seek=1 bs=128k Should be enough to get it working. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] PocketBeagle/BBB custom overlays at boot
On Fri, Oct 27, 2017 at 1:32 PM, Robert Nelson <robertcnel...@gmail.com> wrote:
> On Fri, Oct 27, 2017 at 1:27 PM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>> Hi John,
>>
>> On Fri, Oct 27, 2017 at 1:20 PM, John Morris <j...@zultron.com> wrote:
>>> To get Beagle GPIOs configured correctly at boot, is a custom overlay the
>>> right way to go? I want a bunch of the PocketBeagle pins configured as GPIO
>>> output low, but some of them start up in other modes with unwanted signals.
>>
>> So one of the difference between the BBB and the PocketBeagle, we have
>> 'config-pin' built-into the base *.dtb
>>
>> So if you want a dedicated use of a pin, you need to disable the
>> config-pin/cape-unversal pinmux:
>>
>> P1_02_pinmux {
>> status = "disabled";
>> };
>>
>> So this should work:
>>
>> https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677
>
> OH and Charles wrote another option, i don't think we ever tested it..
>
> https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.9.y/patches/drivers/ti/gpio/0008-bone-pinmux-helper-Add-support-for-mode-device-tree-.patch
>
> P1_02_pinmux {
> mode = "gpio_pd";
> };
it looks silly:
https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677#file-gistfile2-txt
but it should work..
There will still be a little noise from power on -> u-boot -> kernel
(kernel loads in about 1 - 2 seconds)
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] PocketBeagle/BBB custom overlays at boot
On Fri, Oct 27, 2017 at 1:27 PM, Robert Nelson <robertcnel...@gmail.com> wrote:
> Hi John,
>
> On Fri, Oct 27, 2017 at 1:20 PM, John Morris <j...@zultron.com> wrote:
>> To get Beagle GPIOs configured correctly at boot, is a custom overlay the
>> right way to go? I want a bunch of the PocketBeagle pins configured as GPIO
>> output low, but some of them start up in other modes with unwanted signals.
>
> So one of the difference between the BBB and the PocketBeagle, we have
> 'config-pin' built-into the base *.dtb
>
> So if you want a dedicated use of a pin, you need to disable the
> config-pin/cape-unversal pinmux:
>
> P1_02_pinmux {
> status = "disabled";
> };
>
> So this should work:
>
> https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677
OH and Charles wrote another option, i don't think we ever tested it..
https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-4.9.y/patches/drivers/ti/gpio/0008-bone-pinmux-helper-Add-support-for-mode-device-tree-.patch
P1_02_pinmux {
mode = "gpio_pd";
};
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] PocketBeagle/BBB custom overlays at boot
Hi John,
On Fri, Oct 27, 2017 at 1:20 PM, John Morris <j...@zultron.com> wrote:
> To get Beagle GPIOs configured correctly at boot, is a custom overlay the
> right way to go? I want a bunch of the PocketBeagle pins configured as GPIO
> output low, but some of them start up in other modes with unwanted signals.
So one of the difference between the BBB and the PocketBeagle, we have
'config-pin' built-into the base *.dtb
So if you want a dedicated use of a pin, you need to disable the
config-pin/cape-unversal pinmux:
P1_02_pinmux {
status = "disabled";
};
So this should work:
https://gist.github.com/RobertCNelson/41ed096d96bede9617c0a1adafb24677
>
> I attempted an overlay config [1]. It may not be correct, but it at least
> compiles. It's installed as shown at the top of the file by putting it in
> `/lib/firmware` and adding `dtb_overlay=/lib/firmware/pb_goldibox-00A0.dtbo`
> to `/boot/uEnv.txt`. That doesn't seem to have any effect on the pins in
> question, however.
>
> Hints appreciated!
>
> John
>
> [1]: https://github.com/zultron/goldibox/blob/master/pb_goldibox.dts
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit package repo
On Fri, Oct 27, 2017 at 12:11 PM, schoone...@btinternet.com <schoone...@btinternet.com> wrote: > Hi Robert > > Whilst you are looking at this can I pick your brains for the best of your > rt-preempt kernels to upgrade the DE0-NANO-Soc > mksocfpga image with. > > I have already upgraded the existing SD image to Stretch and have it > working, but with the old 4.1.22-ltsi-rt23 kernel > > I have crossbuild tools installed and can quite happily build one from your > sources if required I'd use their 4.9.x branch: https://github.com/altera-opensource/linux-socfpga/branches/all as that has rt right now: https://www.kernel.org/pub/linux/kernel/projects/rt/ But as soon as they open up socfpga-4.13 i'd move to that.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit package repo
On Fri, Oct 27, 2017 at 7:49 AM, Lewis Cobb <lewishc...@gmail.com> wrote: > Hi Robert - > > This is great - thanks very much. > > I'm pretty new to all this but looking at the Uboot link you provided it > looks like I just have to make sure the Uboot is a recent one, and then that > the overlays are enabled ? The easiest thing to do is just run this script and report it's output.. sudo /opt/scripts/tools/version.sh Then we can walk you thru what you need to do.. > > Now - here's a real noob question for you - are Uboot overlays and Device > Tree Overlays the same thing ? I've just started to read about the DT stuff > and my head is spinning, so if you have a link to some educational material > on the uboot overlay stuff it would be much appreciated. They are exactly the same. We've just EOL'ed kernel overlays and have u-boot doing all the overlay loading work. (its more reliable/etc..) 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit package repo
On Thu, Oct 26, 2017 at 3:07 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Thu, Oct 26, 2017 at 1:41 PM, schoone...@btinternet.com > <schoone...@btinternet.com> wrote: >> What RCN does is very much down to him :) >> >> The way is open for him to produce a rt-preempt kernel 4.x.x image using the >> packages, if he is so minded > > It had build issue last Sunday, think i have everything worked out, so > I should have a new build this weekend.. (using v4.13.x-bone-rt with > u-boot overlays)... Lewis, Give this a shot.. https://rcn-ee.net/rootfs/bb.org/testing/2017-10-26/machinekit/bone-debian-8.9-machinekit-armhf-2017-10-26-4gb.img.xz to work, it has to use u-boot overlays: https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit package repo
On Thu, Oct 26, 2017 at 1:41 PM, schoone...@btinternet.com <schoone...@btinternet.com> wrote: > What RCN does is very much down to him :) > > The way is open for him to produce a rt-preempt kernel 4.x.x image using the > packages, if he is so minded It had build issue last Sunday, think i have everything worked out, so I should have a new build this weekend.. (using v4.13.x-bone-rt with u-boot overlays)... 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Error with CRAMPS.hal
On Fri, Oct 13, 2017 at 3:58 PM, 'Dimitar Dobrev' via Machinekit <machinekit@googlegroups.com> wrote: > I get the following for the same commands: > > $ cat /proc/cmdline > console=ttyO0,115200n8 capemgr.disable_partno=BB-BONELT-HDMI > bone_capemgr.enable_partno=BB-UART1 bone_capemgr.uboot_capemgr_enabled=1 > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M > net.ifnames=0 quiet cape_universal=enable nuke the: capemgr.disable_partno=BB-BONELT-HDMI This replaces it: disable_uboot_overlay_video=1 Remove bone_capemgr.enable_partno=BB-UART1 This replaces it: config-pin P9.24 uart config-pin P9.26 uart > $ uname -r > 4.4.91-bone-rt-r19 > $ ls -lha /sys/devices/platform/bone_capemgr/ > total 0 > drwxr-xr-x 3 root root0 Oct 13 20:51 . > drwxr-xr-x 15 root root0 Oct 13 20:49 .. > lrwxrwxrwx 1 root root0 Oct 13 20:51 driver -> > ../../../bus/platform/drivers/bone_capemgr > -rw-r--r-- 1 root root 4.0K Oct 13 20:51 driver_override > -r--r--r-- 1 root root 4.0K Oct 13 20:51 modalias > lrwxrwxrwx 1 root root0 Oct 13 20:51 of_node -> > ../../../firmware/devicetree/base/bone_capemgr > drwxr-xr-x 2 root root0 Oct 13 20:51 power > lrwxrwxrwx 1 root root0 Oct 13 20:49 subsystem -> ../../../bus/platform > -rw-r--r-- 1 root root 4.0K Oct 13 20:49 uevent This is correct, U-Boot hinted to the kernel via "bone_capemgr.uboot_capemgr_enabled=1" to not enable SLOTS, because you are not allowed too.. The system is ready for config-pin call's.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Error with CRAMPS.hal
On Mon, Oct 16, 2017 at 3:00 AM, 'Dimitar Dobrev' via Machinekit <machinekit@googlegroups.com> wrote: > I did have /uEnv.txt, unfortunately moving it changed nothing. Okay, time to plug in a usb-serial adapter so we can see what's really going on.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Error with CRAMPS.hal
On Fri, Oct 13, 2017 at 2:23 PM, 'Dimitar Dobrev' via Machinekit <machinekit@googlegroups.com> wrote: > Option 1 made no difference to the output. Option 2 removed this line: > > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.10-1-g143c9ee] > > Unfortunately, it makes no difference. I still get: > > grep: /sys/devices/bone_capemgr.*/slots: No such file or directory That's 3.8.x path in v4.1.x + it's debian@test-bbb-2:~$ cat /proc/cmdline console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 debian@test-bbb-2:~$ uname -r 4.9.54-ti-r68 debian@test-bbb-2:~$ ls -lha /sys/devices/platform/bone_capemgr/ total 0 drwxr-xr-x 4 root root0 Oct 13 20:43 . drwxr-xr-x 20 root root0 Oct 13 20:43 .. drwxr-xr-x 2 root root0 Oct 13 20:43 baseboard lrwxrwxrwx 1 root root0 Oct 13 20:43 driver -> ../../../bus/platform/drivers/bone_capemgr -rw-r--r-- 1 root root 4.0K Oct 13 20:43 driver_override -r--r--r-- 1 root root 4.0K Oct 13 20:43 modalias lrwxrwxrwx 1 root root0 Oct 13 20:43 of_node -> ../../../firmware/devicetree/base/bone_capemgr drwxr-xr-x 2 root root0 Oct 13 20:43 power -rw-r--r-- 1 root root 4.0K Oct 13 20:43 slots lrwxrwxrwx 1 root root0 Oct 13 20:43 subsystem -> ../../../bus/platform -rw-r--r-- 1 root root 4.0K Oct 13 20:43 uevent While the slots file is only there if U-Boot does not pass: bone_capemgr.uboot_capemgr_enabled=1 btw, do you have a file located here: /uEnv.txt That also breaks U-Boot overlays, remove it. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Error with CRAMPS.hal
On Fri, Oct 13, 2017 at 1:11 PM, 'Dimitar Dobrev' via Machinekit <machinekit@googlegroups.com> wrote: > git:/opt/scripts/:[6b111dede3053d977465860905cfc27d6effe51e] > eeprom:[A335BNLT00C04016BBBK042B] > model:[TI_AM335x_BeagleBone_Black] > dogtag:[Machinekit Debian Image 2017-02-12] > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > 2017.09-2-g0f3f1c7907] > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.10-1-g143c9ee] So here's the issue, eMMC version of U-Boot get's used, and all uboot overlay options get ignored.. So you have two options: 1: care about the data on eMMC just run this to nuke the "MLO" file sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 bs=128k 2: Erase the eMMC.. sudo dd if=/dev/zero of=/dev/mmcblk1 > kernel:[4.4.91-bone-rt-r19] > nodejs:[v6.11.2] > uboot_overlay_options:[enable_uboot_overlays=1] > uboot_overlay_options:[uboot_overlay_addr0=/lib/firmware/BB-UART1-00A0.dtbo] > uboot_overlay_options:[disable_uboot_overlay_video=1] > uboot_overlay_options:[disable_uboot_overlay_audio=1] > uboot_overlay_options:[disable_uboot_overlay_wireless=1] > uboot_overlay_options:[enable_uboot_cape_universal=1] > pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728] > WARNING:pkg:[bb-wl18xx-firmware]:[NOT_INSTALLED] > WARNING:pkg:[firmware-ti-connectivity]:[NOT_INSTALLED] Then reboot, you should see the kernel come up differently.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Error with CRAMPS.hal
On Fri, Oct 13, 2017 at 10:21 AM, 'Dimitar Dobrev' via Machinekit <machinekit@googlegroups.com> wrote: > Bas, I have run: > > grep -c bone_capemgr.uboot_capemgr_enabled=1 /proc/cmdline > > I get: > > 0 > > This was both before and after I enabled enable_uboot_cape_universal=1 in > /boo/uEnv.txt (with a reboot between, of course). I've also tried enabling: > > cape_enable=bone_capemgr.enable_partno=BB-UART1 > > to no avail. I've also followed > https://groups.google.com/d/msg/beagleboard/go89maLiYPc/ebAJrTtJzMsJ . I > keep getting 0 from > grep -c bone_capemgr.uboot_capemgr_enabled=1 /proc/cmdline > and the same error with CRAMPS. > Do I perhaps need to enable additional settings? Please run: sudo /opt/scripts/tools/version.sh So we can see a better picture of your u-boot/kernel combination for debugging.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] How to run Machinekit on the new Pocketbeagle?
On Tue, Oct 3, 2017 at 4:17 AM, Thomas Hagen <liquid2...@gmail.com> wrote: > Hello, > > I just go my hands on the new Pocketbeagle. I would like to run machinekit > on it. > Is there already an image I can install on it? If not maybe someone has an > idea how to adapt an existing image to it. Well, start with this Jessie based image: https://rcn-ee.net/rootfs/bb.org/testing/2017-10-02/iot/bone-debian-8.9-iot-armhf-2017-10-02-4gb.img.xz and add the machinekit repo's.. config-pin is setup for all the pins on the header Only v4.4.x-ti/v4.9.x-ti kernels are currently setup to work with the board. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: DE10-DE0-Nano - Invitation to collaborate
On Thu, Aug 31, 2017 at 6:03 PM, mugginsac <muggin...@gmail.com> wrote:
> Michael,
>
> How much swap did you add? I am trying to get my image to load but my SD
> writing programs don't like your image. I use ApplePi Baker or Etcher.
> Etcher complains about no partition table. ApplePi Baker wrote an SD image
> but Linux thinks it is a CD.
>
> How do you format the uSD card??
>
> sudo sfdisk ${DISK} <<-__EOF__
> 1M,1M,0xA2,
> ---swap format goes here--
> 2M,,,*
> __EOF__
Or just use a swap file, then you don't have to worry about the
partition table..
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
On Thu, Aug 24, 2017 at 3:51 PM, mugginsac <muggin...@gmail.com> wrote: > OK that made some progress. It still looks like some command processor is > running at the same time as the login process. > > It printed "U-Boot SPL 2017.05-dirty (Aug 23 2017 - 15:20:51) > drivers/ddr/alt" on the serial console and then went quiet. Next thing I saw > was that it had apparently loaded the kernel and was waiting for a user > name. > > However, some process was feeding characters that were being consumed by the > login process. Every so often it would hit something that corresponded to > something the command processor recognized and display a bunch of stuff on > the screen again, like a help menu. Look at the file I captured and see if > it helps understand what is going on. I don't know what process is putting > up the various help menus. "Something" else is echoing data into your serial device node from your development pc. What program are you using to access the serial terminal? 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
On Wed, Aug 23, 2017 at 10:56 PM, mugginsac <muggin...@gmail.com> wrote: > I still have problems with the serial terminal. > > It seems to me like U-boot is starting up and receiving input that is > putting it into command mode. Then it is like the process that outputs the > text from the DE10 is being fed into the console input and confusing the > heck out of the command processor. It keeps reporting command not understood > or not recognized and then advising to try help. This seems to continue > until minicom, putty or screen are overwhelmed and abort or terminate. It is > almost like the command processor is still running but u-boot is restarting > and outputting the startup messages again. > > Does any of this make any sense? > > Occasionally, it will hit a state where the boot process will complete to > where it will read extlinux.conf and load the kernel. +CONFIG_AUTOBOOT_KEYED=y +CONFIG_AUTOBOOT_PROMPT="Press SPACE to abort autoboot in %d seconds\n" +CONFIG_AUTOBOOT_DELAY_STR="d" +CONFIG_AUTOBOOT_STOP_STR=" " Then the only way to enter command mode, is the "space" key... 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?
On Mon, Aug 21, 2017 at 4:56 PM, mugginsac <muggin...@gmail.com> wrote: > Here is what I am getting from trying to boot the uSD I built. Is it > possible that I have a bad uSD? > > U-Boot SPL 2017.05 (Aug 20 2017 - 08:57:37) > drivers/ddr/altera/sequencer.c: Preparing to start memory calibration > drivers/ddr/altera/sequencer.c: CALIBRATION PASSED > drivers/ddr/altera/sequencer.c: Calibration complete > Trying to boot from MMC1 > > > U-Boot 2017.05 (Aug 20 2017 - 08:57:37 -0700) > > CPU: Altera SoCFPGA Platform > FPGA: Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0 > BOOT: SD/MMC Internal Transceiver (3.0V) >Watchdog enabled > I2C: ready > DRAM: 1 GiB > MMC: dwmmc0@ff704000: 0 > *** Warning - bad CRC, using default environment > > In:serial > Out: serial > Err: serial > Model: Terasic DE10-Nano > Net: > Error: ethernet@ff702000 address not set. > No ethernet found. > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > Unknown command 'part' - try 'help' add: CONFIG_CMD_PART=y this was missed in v2017.05-ish time frame... diff --git a/configs/socfpga_de10_nano_defconfig b/configs/socfpga_de10_nano_defconfig index 26addc3c4d..fc2dcc3951 100644 --- a/configs/socfpga_de10_nano_defconfig +++ b/configs/socfpga_de10_nano_defconfig @@ -25,6 +25,7 @@ CONFIG_CMD_DFU=y CONFIG_CMD_GPIO=y CONFIG_CMD_I2C=y CONFIG_CMD_MMC=y +CONFIG_CMD_PART=y CONFIG_CMD_SPI=y CONFIG_CMD_USB=y CONFIG_CMD_USB_MASS_STORAGE=y 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS
On Sat, Jul 29, 2017 at 3:39 PM, Daren Schwenke <darenschwe...@gmail.com> wrote: > Everything works, with the caveat of really high processor utilization. > About 80-90% all the time, with rtapi:0 taking about 50% of that. > This makes for a slower user interface even when using remote. > But, that doesn't seem to affect operation as I've printed 2 good looking > 1.5 hour parts so far with no issues. > I've only tested on the BBG thus far. I don't forsee any issues with the > BBGW other than configuring it headless is confusing me as it uses > connmanctl. > > Steps: > Download the image Robert has made for this: > https://rcn-ee.net/rootfs/bb.org/testing/2017-07-28/machinekit/bone-debian-8.9-machinekit-armhf-2017-07-28-4gb.img.xz > Login as machinekit:machinekit. > sudo apt-get update > cd /usr/lib/linuxcnc/ > # save some files we need from xenomai > sudo tar -cvpf xenomai.tar xenomai/pru* > # remove it. > sudo apt-get remove --purge machinekit-xenomai > # install rt-preempt > sudo apt-get install machinekit-rt-preempt > # put the saved files back > sudo tar -xvf xenomai.tar > # move a couple from preempt to xenomai > sudo cp -p rt-preempt/hal_pru* xenomai/ > > #now edit /usr/bin/hal_temp_bbb and on line 154 change it so it reads: > #syspath = '/sys/bus/iio/devices/iio:device0/' I've submitted a pull request for this adc change: https://github.com/machinekit/machinekit/pull/1241 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS
On Fri, Jul 28, 2017 at 5:40 PM, Daren Schwenke <darenschwe...@gmail.com> wrote: > So I think this is getting really close now. I'm compiling again so I can > remove the dependencies outside of the RIP build I have. > So I'm going to take this and sort the last few thingies here (by removing > them) and test it on a real machine. > Then, if it works, I'll compile a list of what had to happen. Short list: > > Robert, your image was missing the wireless firmware files and it doesn't > look like it was rebuilt since then. Could you kick that off? > It also seems we'll need rt-preempt and xenomai at the same time (cause the > pru_generic bin was compiled as part of xenomai). Not sure if the packages > currently allow that. > It would be great if machinekoder could take a look at the velocity > extrusion related errors, but I have a version where I stripped out reset I > believe so I can move forward. > https://github.com/machinekit/machinekit/blob/master/src/hal/user_comps/hal_temp_bbb.py#L154 > needs to point to '/sys/bus/iio/devices/iio:device0/', then it works on both > 3.8.13 and 4.4 here you go: https://rcn-ee.net/rootfs/bb.org/testing/2017-07-28/machinekit/ 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS
On Fri, Jul 28, 2017 at 3:25 PM, Daren Schwenke <darenschwe...@gmail.com> wrote:
> found the new path and changed 154 to:
> syspath =
> '/sys/devices/platform/ocp/44e0d000.tscadc/TI-am335x-adc/iio:device0/'
> Works. Next error:
another option would be the generic:
/sys/bus/iio/devices/iio:device0/
(it might actually exist on 3.8.13 too..)
> machinekit@beaglebone:~/machinekit/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS$
> ./run.pyloading cramps2_cape.bbio... done
> starting configserver... done
> starting linuxcnc... MACHINEKIT - 0.1
> Machine configuration directory is
> '/home/machinekit/machinekit/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS'
> Machine configuration file is 'fabrikator-mini.ini'
> Starting Machinekit...
> done
> io started
> halcmd loadusr io started
> Traceback (most recent call last):
> File "fabrikator_mini.py", line 34, in
> ve.velocity_extrusion(extruders=numExtruders, thread='servo-thread')
> File
> "/home/machinekit/machinekit/lib/python/fdm/config/velocity_extrusion.py",
> line 261, in velocity_extrusion
> velocity_jog(extruders, thread)
> File
> "/home/machinekit/machinekit/lib/python/fdm/config/velocity_extrusion.py",
> line 80, in velocity_jog
> reset = rt.newinst('reset', 'reset.ve-jog-trigger')
> File "machinekit/rtapi.pyx", line 265, in
> machinekit.rtapi.RTAPIcommand.newinst (hal/cython/machinekit/rtapi.c:5541)
> RuntimeError: rtapi_newinst '('reset', 'reset.ve-jog-trigger')' failed:
> Invalid argument
> Shutting down and cleaning up Machinekit...
> exiting HAL component storage
> exiting HAL component temp
> Cleanup done
> Machinekit terminated with an error. You can find more information in the
> log:
> /home/machinekit/linuxcnc_debug.txt
> and
> /home/machinekit/linuxcnc_print.txt
> as well as in the output of the shell command 'dmesg' and in the terminal
> stopping configserver... done
> machinekit@beaglebone:~/machinekit/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS$
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.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS
Here you go, fresh build with v4.4.x-ti-rt https://rcn-ee.net/rootfs/bb.org/testing/2017-07-26/machinekit/bone-debian-8.9-machinekit-armhf-2017-07-26-4gb.img.xz on first bootup, make sure u-boot overlays is active: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays (it should be, but if your eMMC u-boot is too old it won't be) To disable hdmi/emmc/etc: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices cape universal is setup to load automaticlly too. (config-pin doesn't require root ;) ) This image also defaults to uio mode for the pru, so you won't have to change, as it's setup correctly http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_PRU_Options 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] BBB latest Machinekit Image
On Sat, Jul 1, 2017 at 5:09 AM, 'Timm Eversmeyer' via Machinekit <machinekit@googlegroups.com> wrote: > Hi, > > I tried to get the latest machinekit for Beaglebone running. I flashed the > sd card with Ether. After plugging in and booting I connected via SSH. I > have X-forwarding running. > > > machinekit@beaglebone:~$ machinekit > Creating machinekit directory > MACHINEKIT - 0.1 > Machine configuration directory is > '/home/machinekit/machinekit/configs/sim.axis' > Machine configuration file is 'axis.ini' > Starting Machinekit... > Warning - /usr/libexec/linuxcnc/rtapi_app_posix not setuid > 'sudo make setuid' missing? > /usr/bin/realtime: line 192: /usr/libexec/linuxcnc/rtapi_app_posix: No such > file or directory > rtapi_app startup failed - aborting > halcmd: cant connect to rtapi_app: -1 (uri= > uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout > > halcmd: the rtapi:0 RT demon is not running - please investigate > /var/log/linuxcnc.log > io started > halcmd: cant connect to rtapi_app: -1 (uri= > uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout > > halcmd: the rtapi:0 RT demon is not running - please investigate > /var/log/linuxcnc.log > halcmd loadusr io started > halcmd: cant connect to rtapi_app: -1 (uri= > uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout > > halcmd: the rtapi:0 RT demon is not running - please investigate > /var/log/linuxcnc.log > halcmd: cant connect to rtapi_app: -1 (uri= > uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout > > halcmd: the rtapi:0 RT demon is not running - please investigate > /var/log/linuxcnc.log > Shutting down and cleaning up Machinekit... > > > Seems that the there is no realtime kernel running? > > > machinekit@beaglebone:~$ uname -a > Linux beaglebone 4.4.68-ti-xenomai-r110 #1 SMP Wed Jun 21 11:37:17 UTC 2017 > armv7l GNU/Linux > > uname says that the xenomai kernel ist running. But it seems that the > machinekit expects that the rt-preempt is running? > > I tried images which where assembled before. There is the same problem. Use the last 3.8.x build from here: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#microSD.2FStandalone:_.28machinekit.29_Based_on_Debian_Jessie_with_3.8.x_kernel I'll stop all MachineKit builds for BBB, till you guys port to Xenomai 3.0.x. As i can't win, as the 3.8.x doesn't support the new WiFi boards (and blue)... 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Autobuilt jessie image with kernel 4.4
On Tue, Jun 20, 2017 at 2:10 PM, Aivaras Spaicys <spaiva...@gmail.com> wrote: > Its my first time trying to use linuxcnc/machinekit so please excuse me. By > flowing tutorials and readme's from beaglebone page I downloaded machinekit > prebuild SD card images based on jessie kernel 4.4.x from > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit > > Booted it on BBB with no modifications to anything it seems I can't start > machinekit or latency_test they all give similar output > > > Starting Machinekit... > Warning - /usr/libexec/linuxcnc/rtapi_app_posix not setuid > 'sudo make setuid' missing? > /usr/bin/realtime: line 192: /usr/libexec/linuxcnc/rtapi_app_posix: No such > file or directory > rtapi_app startup failed - aborting > halcmd: cant connect to rtapi_app: -1 (uri= > uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout > > > No readme's anywhere talk about any initial configuration or building > something (reference to make) > > I am probably missing something very simple, or could be that auto builds > have problems. Currently trying the 3.8.x kernel flavour one, will post on > the status The kernel witch is used by default: v4.4.x-ti-xenomai is part of Xenomai 3.0.x. Whereas the 3.8.13-xenomai kernel is part of Xenomai 2.6.x Since you have a classic BBB, you can safely down-grade to the 3.8.13 kernel cd /opt/scripts/tools/ git pull sudo ./update_kernel.sh --bone-xenomai-channel --stable 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Replicape revB and Machinekit on Kernel 4.4 Xenomai
On Thu, May 11, 2017 at 12:43 PM, <hypersolut...@gmail.com> wrote: > OK, I'll stick with 3.8. > > As for the overlays this repo seems to have drop support for 3.8 kernels. > There is no tags or branches for older releases. > https://github.com/beagleboard/bb.org-overlays This repo has always been v4.1.x+ (now v4.4.x+) > Do someone knows a repo with 3.8 compatible device tree overlay sources? They are inside the 3.8 kernel tree: https://github.com/beagleboard/linux/tree/3.8/firmware/capes 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Debian Stretch Beaglebone Black machine kit axis and the gpu
Nope it's still an open project: Tom here's the base wayland project: https://rcn-ee.net/rootfs/bb.org/testing/2017-04-09/stretch-wayland/ Then do: sudo apt install ti-sgx-ti335x-modules-`uname -r` sudo depmod -a `uname -r` sudo update-initramfs -uk `uname -r` then this userspace: git clone -b ti-img-sgx/1.14.3699939 git://git.ti.com/graphics/omap5-sgx-ddk-um-linux.git --depth=1 cd omap5-sgx-ddk-um-linux/ sudo su export DISCIMAGE=/ export TARGET_PRODUCT=ti335x make install exit #fix: libgbm.so.2 (one line:) sudo ln -s /usr/lib/arm-linux-gnueabihf/libgbm.so.1 /usr/lib/arm-linux-gnueabihf/libgbm.so.2 sudo modprobe pvrsrvkm sudo /usr/bin/pvrsrvctl --start --no-module and that's as far as i've gotten.. Then figure out how to make it work. ;) 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] BeagleBone Family MachineKit image
On Wed, Mar 22, 2017 at 3:08 AM, <alexander.roess...@zuehlke.com> wrote: > > > Am Mittwoch, 22. März 2017 04:47:47 UTC+1 schrieb Robert Nelson: >> >> Sorry for the delay, traveling this week. Will be back Friday. >> >> On Tue, Mar 21, 2017 at 11:46 AM, <alexander...@zuehlke.com> wrote: >> > I'm working on getting the Replicape to work with the Jessie Machinekit >> > images. Here are my findings so far: >> > >> > I had to replace the Xenomai kernel with the RT-PREEMPT kernel. I think >> > some >> > configuration for the Xenomai kernel might be missing. However, I think >> > the >> > RT-PREEMPT kernel should work fine too. >> >> So with v4.4.x-xenomai we get 3.0.x Xenomai vs 2.6.x Xenomai with the >> old 3.8.13.. I know Xenomai userspace changed. > > Then I guess this would require changes in Machinekit too. Therefore, I > suggest switching to the RT-PREEMPT kernel as default for the Jessie images. > >> >> > >> > Then I tried to get the cape-universal overlays for my application. As >> > part >> > of the process I created the two PRs: >> > https://github.com/cdsteinkuehler/beaglebone-universal-io/pull/48 >> > https://github.com/beagleboard/bb.org-overlays/pull/42 >> >> When i looked at that, it was referenced as not ready. If it's ready >> i'll pull it in.. >> >> >> fyi: in the bb.org-overlays repo, since we utilized the pre-processor >> for a few #define's, i've been experimenting ways to keep all the cape >> universal overlays in sync: >> >> >> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/univ-bbb-EVA-00A0.dts#L17-L19 > > Clever solution. > >> >> >> i have the "univ-bbb-XXX-00A0.dts" tied into U-Boot overlays: >> >> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > > Now I'm confused. What is the difference between cape-universala, > univ-bbb-EVA and univ-all ? Is there a reason for having three separate > capes? it's because boards aren't 100% compatible with the BeagleBone & BeagleBone Black.. So for u-boot overlays i'm taking the time to clean things up into: univ---00A0.dtb bbb = done bbbw = bbb but we lose a usart to bluetooth, unless wifi is disabled (who would do that) bbg = bbb but no hdmi/hdmi-audio bbgw = bbb bot no hdmi/hdmi-audio and wireless takes a bunch of pins on the p8 header > >> >> >> > >> > The Replicape uses some pins usually occupied with the HDMI audio pins >> > and I >> > experience some problems using config-pin to pinmux these pins. >> > sudo config-pin P9_25 in >> > >> > [sudo] password for machinekit: >> > bash: /sys/devices/platform/ocp/ocp*P9_25_pinmux/state: No such file or >> > directory >> > >> > Cannot write pinmux file: >> > /sys/devices/platform/ocp/ocp*P9_25_pinmux/state >> > >> > I experience this problem with the following pins: >> > P9.25 >> > P9.28 >> > P9.29 >> > P9.31 >> > >> > The slots file looks as follows: >> > machinekit@beaglebone:~$ cat /sys/devices/platform/bone_capemgr/slots >> > 0: P- -1 Replicape 3D printer cape,0B3A,Intelligent >> > Agen,BB-BONE-REPLICAP >> > >> > 1: PF -1 >> > 2: PF -1 >> > 3: PF -1 >> > 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,cape-universaln >> > >> > >> > >> > >> > Robert, do you maybe have an idea what could be the problem? >> >> It looks like once that peripheral took the pins in the first overlay, >> the kernel locked them so the 2nd overlay couldn't modify them >> anymore. Might be best to add the config-pin options to the replicape >> overlay, or just use the cape-universaln as-is. > > The Replicape cape is not installed and therefore does not affect my setup. > > I figured out that this problem seems to occur in the TI kernels only. With > the following kernel > Linux beaglebone 4.4.55-bone-rt-r16 #1 PREEMPT RT Tue Mar 21 10:06:36 UTC > 2017 armv7l GNU/Linux > it does work as expected. > > Since I would like to use the SGX drivers which come with the TI kernel -> > where can I best report this problem? > > I will proceed with the mainline kernel for now and report back if I have > troubles or on success. so in 4.4.x-ti hdmi audio is enabled by default. the pre-u-boot-overlay method had you disable the hdmi via: http://elinux.org/Beagleboard:BeagleBone_Debian_Image_Migration#Disabling_eMMC_or_HDMI but that missed a bunch of combinations.. hence the newer u-boot overlay disable optoins.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
[Machinekit] Re: Universal-Universal Cape Overlay [was: BeagleBone Family MachineKit image]
On Wed, Mar 22, 2017 at 8:12 AM, Charles Steinkuehler <char...@steinkuehler.net> wrote: > On 3/21/2017 10:47 PM, Robert Nelson wrote: >> >> fyi: in the bb.org-overlays repo, since we utilized the pre-processor >> for a few #define's, i've been experimenting ways to keep all the cape >> universal overlays in sync: >> >> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/univ-bbb-EVA-00A0.dts#L17-L19 > > > Nice! > > I've hated all the duplication across the various universal cape > "flavors", and I'm loving the U2C idea (Universal Universal Cape!). > ;-) > > Now I'm wondering about managing the repositories. It really feels like > your bb.org-overlays is "upstream" for the device tree files, but IIRC > you're still pulling config-pin from my repo. Is that correct? I've recently imported your config-pin script, into bb.org-overlays https://github.com/beagleboard/bb.org-overlays/tree/master/tools/beaglebone-universal-io and now it's part of the bb-cape-overlay debian/ubuntu package, so users can have a small image with config-pin and don't need to install the git package to clone the repo for the script.. > > Perhaps config-pin should be promoted to it's own project with it's own > repo (maybe even under the beagleboard umbrella) and my existing > beaglebone-universal-io repo with overlays can be deprecated or > relegated to use with 3.8 kernels only? Got any better ideas? my only idea was to leave your repo 3.8.x only (we will probally be supporting 3.8.x for ever ;) ) 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: BBB Machinekit Debian Jessie images and USB
On Sat, Mar 18, 2017 at 5:04 AM, Alexander Rössler <mail.aroess...@gmail.com> wrote: > It turns out the image in the link is the 2-12 Debian Jessie Machinekit > image, I have to check again with the 3-12 version linked by RCN. So the fat drive is actually a virtual *.img file.. Installed by the package: doc-beaglebone-getting-started which we don't install on the machinekit image to save space with 3-12 and later i swapped the 3.8.x kernel for v4.4.x-xenomai tomorrrow's version will have u-boot cape overlays + u-boot cape-universal enabled.. use this define to force a driver partition or a new 2nd partition: https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L85 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] frame buffer for Optocape in 3.8
On Thu, Mar 9, 2017 at 5:32 PM, Dean Gouramanis <temproducts...@gmail.com> wrote: > I had Optocape working last week using 4.1 kernel. > > https://twitter.com/deandzines/status/839979348602028033 > > I used the am335x-boneblack-emmc-overlay.dtb and loaded my .dtbo file from > /lib/firmware. > > Here is a link to the .dts > > https://github.com/dgouramanis/optocape/blob/master/device%20tree/BB-OPTOCAPE1-00A0.dts So first, make sure you are using the old dtc compiler, it should be installed in /usr/local/bin/dtc second, for your overlay, 3.8.x needs a fb section: https://github.com/beagleboard/linux/blob/3.8/firmware/capes/BB-BONE-LCD7-01-00A3.dts#L272-L280 with 3.8.x the usart is off by one: https://github.com/beagleboard/linux/blob/3.8/firmware/capes/BB-UART4-00A0.dts#L41 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] HDMI disabled but not HDMIN
On Sat, Feb 18, 2017 at 2:52 PM, Sag ich Dir nich <stevie.rammst...@live.de> wrote: > okay does that mean i can only disable HDMI or HDMIN, not both? No, it simply means you messed up the uEnv.txt file.. Look at it again.. only have 1: capemgr.disable_partno= 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] HDMI disabled but not HDMIN
On Sat, Feb 18, 2017 at 1:57 PM, Sag ich Dir nich <stevie.rammst...@live.de> wrote: > i think so, > > the thing is when i see the screen via vnc and load machinekit, i do not see > machinekit in the hdmi monitor (vnc is extremely slow and does not work with > AXIS) Nope, look at your screen shot again.. you have "two" capemgr.disable_partno, so only the "last" one get's used.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit multicore merge
On Sun, Feb 12, 2017 at 12:40 PM, Alexander Rössler <alexander@roessler.systems> wrote: > I have not checked recently, but there was problem with the USB Ethernet > not working I think. Last time I tested it was mid December. Machinekit for Wheezy & Jessie share the same ancient 3.8.13 kernel.. So if that was an issue in jessie, i'd fully expect the wheezy image to have the exact same problem. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: Machinekit multicore merge
On Wed, Feb 8, 2017 at 11:37 AM, Marius Alksnys <mar...@robotise.lt> wrote: > > 02/08/2017 03:13 PM, schoone...@btinternet.com rašė: >> >> >> On 08/02/17 12:13, Marius Alksnys wrote: >>> >>> What does it mean for BeagleBone machinekit existing and new >>> applications? >>> >>> >> Hi >> >> I don't see it changes anything >> There is no reason I am aware of to use a Wheezy based image with BBB. >> >> The Robert Nelson image is based upon Jessie, so in a couple of weeks >> that will have the new code in it. >> >> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit > > > That's completely fine if there is working jessie image for BBB. But, as I > remember, I and Alexander R. couldn't use it. > I hope functions like pru pwmgen, stepgen, encoders, eQEP and ADC will work > right, otherwise I will have to stick to wheezy with all my BB+machinekit > projects. What is broken? it's using the same 3.8.13 based kernel as the old wheezy image.. 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] ADC and printing issues on the Beaglebone CRAMPS
On Mon, Jan 2, 2017 at 4:26 PM, Charles Steinkuehler <char...@steinkuehler.net> wrote: > On 1/2/2017 4:20 PM, Jonathan Cohen wrote: >> So, is it safe to go with the >> bone-debian-8.6-machinekit-armhf-2017-01-01-4gb.img.xz image for a test run ? >> Rather than the 7.11 ? > > I have been using Jessie (8.x) based Machinekit images for some time > (most of 2016) and consider the Wheezy (7.x) images pretty much > deprecated. last week i actually updated the wheezy image so it would atleast build.. (nodejs v0.10.x removal) > The image 2017-01-01 Jessie image should still contain a 3.8.13 > Xenomai kernel and ought to work fine (or as well as any other image) > unless RCN unexpectedly replaced the kernel with 4.4 in which case > lots of things will break and you will probably not be able to even > launch a machine configuration. :) Nope it's still 3.8.13-xenomai based.. You guys let me know when your ready to switch it. ;) 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] ADC and printing issues on the Beaglebone CRAMPS
On Thu, Dec 29, 2016 at 7:20 PM, Charles Steinkuehler <char...@steinkuehler.net> wrote: > On 12/29/2016 9:12 AM, Robert Nelson wrote: >> On Thu, Dec 29, 2016 at 8:40 AM, Charles Steinkuehler >>> >>> There are now Xenomai patches for some 4.x version ARM kernels, >>> if some adventuresome soul cares to try and make this work. :-) >> >> You should checkout this.. ;) >> >> cd /opt/scripts/tools/ git pull sudo ./update_kernel.sh >> --ti-xenomai-channel --lts-4_4 > > Is that kernel expected to work with the uio PRU driver? I can get > the ADC and universal cape to load, but not uio_pruss. > > I've blacklisted the remoteproc modules and cape manager claims to > load the uio_pruss_enable overlay, but I don't get any uio device > entries and the uio_pruss module isn't getting loaded. :( That's right, you guys need uio_pruss. ;) Right now it's just a copy of the ti/rt-ti which has you select one (uio_pruss/remoteproc_pruss) I'll enable this section for the xenomai image for you guys. https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-emmc-overlay.dts#L24-L32 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS
On Wed, Dec 28, 2016 at 12:00 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Wed, Dec 28, 2016 at 11:57 AM, Daren Schwenke > <darenschwe...@gmail.com> wrote: >> I don't suppose either way. I'm just adding my data points to the >> conversation in hopes it might add as mine were different. :) >> If easy, I would load that version and see if it makes a difference (with >> the caveats I've mentioned). Could just be luck, but my luck has run out >> much more quickly before. >> >> I tried to go to 8, but tried it on a BBGW which didn't work at all (the >> image won't boot) and I haven't had the time to figure it out. > > BBGW, BBBW, BB Blue haven't been back-ported to the 3.8.13-bone tree.. > (wl18xx driver is the worst part of that) > > SO just use: > > BBGW: > > dtb=am335x-bonegreen.dtb > > BBBW: > > dtb=am335x-boneblack.dtb I've added a patch so users won't have to do this.. https://github.com/RobertCNelson/bb-kernel/commit/6d969f205926d7329c7bfe277854812bd9d8d5bc (no wl18xx wireless, but at-least the boards will bootup) 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] Re: ADC and printing issues on the Beaglebone CRAMPS
On Wed, Dec 28, 2016 at 11:57 AM, Daren Schwenke <darenschwe...@gmail.com> wrote: > I don't suppose either way. I'm just adding my data points to the > conversation in hopes it might add as mine were different. :) > If easy, I would load that version and see if it makes a difference (with > the caveats I've mentioned). Could just be luck, but my luck has run out > much more quickly before. > > I tried to go to 8, but tried it on a BBGW which didn't work at all (the > image won't boot) and I haven't had the time to figure it out. BBGW, BBBW, BB Blue haven't been back-ported to the 3.8.13-bone tree.. (wl18xx driver is the worst part of that) SO just use: BBGW: dtb=am335x-bonegreen.dtb BBBW: dtb=am335x-boneblack.dtb 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
Re: [Machinekit] ADC and printing issues on the Beaglebone CRAMPS
On Wed, Dec 28, 2016 at 9:59 AM, Jonathan Cohen <electronl...@gmail.com> wrote: > So here is a silly question... > > In the file, hal_temp_bbb.py there is a syspath file path for the TI ADC, " > syspath = '/sys/devices/ocp.*/44e0d000.tscadc/tiadc/iio:device0/' " > > Going from Wheezy to Jessie, the location has changes from > /sys/devices/ocp.*/helper.*/AIN* to /sys/bus/iio/devices/iio:device0 > > Was this updated in the Jessie build ? > > Maybe it's a naive question, in that if it was built on Jessie, the path > would be correct ? It's not related to Jessie.. It's just 3.8.13 vs 4.1.x+ 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. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
