[Machinekit] Re: Broken CRAMPS.bbio
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 However there is no cape-bone-io in /lib/firmware, further removing the reference to it in CRAMPS.hal will again produce halcmd loadusr io started Waiting for /sys/class/uio/uio0 ... Whats even more confusing is that this thread https://groups.google.com/forum/#!topic/machinekit/XSxIKD_mi-s suggest exactly the opposite of RCN suggestion It appears that I'm dammed if I do, and Dammed if I don't. I really don't want to spend several days tearing down a system and replacing the cramps board so I can run a few panel mount temperature control modules. It would be far simpler just to drop back a few years to old code that worked. Trouble is... it's doesn't seem to be available. -- 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/e1c5b697-fcc1-4e04-a782-5f1f203d88bf%40googlegroups.com.
Re: [Machinekit] Re: DE10 Nano suggested development environment?
After looking at it I wonder if it is not just the 8i20 portion of SSerial code has issues. I'm sort of at a loss as I'm not really sure what I'm seeing. Like I said, if you want I can whip you up a board and send it to you on the next run if you want to debug this further. I just don't want to give you bad info since I'm not totally sure I understand why I'm getting the results I'm getting. On Tuesday, August 27, 2019 at 8:26:00 PM UTC-4, justin White wrote: > > New deb is still not working for SS although there is a minor change that > I did not see before. the card status light will blink once, then fault, > then status will blink again and fault. Previously the status light only > lit one time. > > On Tuesday, August 27, 2019 at 7:31:34 PM UTC-4, justin White wrote: > > It would certainly be nice to build firmware with docker with the Quartus > fixes you've made to the DExx_cramps config, in case I come up with some > other hardware. > > On Tuesday, August 27, 2019 at 5:41:28 AM UTC-4, Michael Brown wrote: > > That PR is waiting for the finalizing your pin file: > > https://github.com/the-snowwhite/mksocfpga/blob/sserial-work/HW/hm2/config/DExx_Nano_xxx_Cramps/PIN_st_fpga_soc_dc1f_ss.vhd > > > after the PR is then commited and approved: > When the MKSocfpga changes are merged the changes will show up in the mk > deb (socfpga-rbf) packages, > then you don't have to build yourself. > > > > > On Tuesday, 27 August 2019 00:51:56 UTC+2, justin White wrote: > > BTW, have the > > ... -- 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/d65ef8ba-0d7e-410f-a03b-455aec6f937d%40googlegroups.com.
Re: [Machinekit] Re: DE10 Nano suggested development environment?
It would certainly be nice to build firmware with docker with the Quartus fixes you've made to the DExx_cramps config, in case I come up with some other hardware. On Tuesday, August 27, 2019 at 5:41:28 AM UTC-4, Michael Brown wrote: > > That PR is waiting for the finalizing your pin file: > > https://github.com/the-snowwhite/mksocfpga/blob/sserial-work/HW/hm2/config/DExx_Nano_xxx_Cramps/PIN_st_fpga_soc_dc1f_ss.vhd > > > after the PR is then commited and approved: > When the MKSocfpga changes are merged the changes will show up in the mk > deb (socfpga-rbf) packages, > then you don't have to build yourself. > > > > > On Tuesday, 27 August 2019 00:51:56 UTC+2, justin White wrote: >> >> BTW, have the DExx-cramps changes been merged in a way that I can do a >> docker build on my end yet? >> >> On Monday, August 26, 2019 at 6:49:23 PM UTC-4, justin White wrote: >>> >>> There are comm errors thrown after discovery as mentioned on git, trying >>> to determine if its the hardware or MK's hm2 driver ATM, Still a bit >>> difficult to determine without a verifiable working instance of SS in >>> current MK systems. >>> >>> -- 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/a5eb5f58-37b7-4114-af42-a8d8dcd80c96%40googlegroups.com.
Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
On 8/27/2019 12:16 PM, Michael Brown wrote: > @Charles: > > NOTE: I have a uSD image that's "Plain ole Debian" if you want >> something more generic to work with than the Xilinx AI SDK. It's for >> the ZCU104 but you should be able to use it as-is with the Ultra96 if >> you swap out the boot files (kernel, device-tree, & U-Boot). Let me >> know if you're interested. > > Swapping out the BOOT.BIN and adding image.ub from the U96 petalinux bsp to > the AI image > gives about 1 min of gui access before rebooting, re-placing the rootfs > with the petalinux one fixes the reboots, however ...too minimal Make sure the device tree is copied over as well. Depending on the setup the device tree can be in the BOOT.BIN file, in image.ub, a separate file, stored in raw sectors on the boot media, etc. > I think its time to make that call, for your "Plain ole Debian" rootfs. > Is it Stretch ? Yes, it's stretch but it probably wouldn't take much to migrate to Buster. I'll PM you a link to the uSD images. If you (or anyone else) is interested in the source (I've got scripts for building full working uSD images for the Zybo-Z7-20 and ZCU104 from scratch), follow along below: Hit the following link, scroll to the bottom, and click the download link for the Embedded SDK: https://www.newtek.com/ndi/sdk/ After installing the SDK, the uSD README file has the links to the images. The scripts for building the uSD Image are in the fpga_reference_design/os_uSD/ directory. The root filesystem is virtually identical for both images, one's just armhf and the other is aarch64. They are almost bone-stock Debian installs, with a few minor tweaks here and there (mostly customizing the login prompt & such) as well as a couple "magic" bits you'll likely want to keep (like generating ssh keys and resizing the uSD partition on first boot). Depending on how the 96 boards image is setup, it may be easier to copy the boot loader & such onto my uSD images, or it may work better to copy (rsync) the contents of the rootfs onto their image. My Debian rootfs system is agnostic with regards to where it lives, as long as you pass an appropriate root= command to the kernel. :) -- Charles Steinkuehler char...@steinkuehler.net -- 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/fcba8541-f261-138e-2896-9eb1efe1b162%40steinkuehler.net.
Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
@Charles: NOTE: I have a uSD image that's "Plain ole Debian" if you want > something more generic to work with than the Xilinx AI SDK. It's for > the ZCU104 but you should be able to use it as-is with the Ultra96 if > you swap out the boot files (kernel, device-tree, & U-Boot). Let me > know if you're interested. > Swapping out the BOOT.BIN and adding image.ub from the U96 petalinux bsp to the AI image gives about 1 min of gui access before rebooting, re-placing the rootfs with the petalinux one fixes the reboots, however ...too minimal I think its time to make that call, for your "Plain ole Debian" rootfs. Is it Stretch ? On Saturday, 24 August 2019 14:20:49 UTC+2, Charles Steinkuehler wrote: > > On 8/24/2019 5:19 AM, Michael Brown wrote: > > Now having some experience with Vivado and the Ultra96 I'm thinking of > > following up on this.. > > Xilinx has a Ultra96 Debian buster image online here as a starting > point: > > > https://www.xilinx.com/products/design-tools/ai-inference/ai-developer-hub.html#edge > > > Looks like an interesting board. The Ultrascale+ parts are really > nice to work with. I support a ZCU104 design for my Day Job that runs > video compression/streaming between the HDMI ports and Ethernet. > > NOTE: I have a uSD image that's "Plain ole Debian" if you want > something more generic to work with than the Xilinx AI SDK. It's for > the ZCU104 but you should be able to use it as-is with the Ultra96 if > you swap out the boot files (kernel, device-tree, & U-Boot). Let me > know if you're interested. > > > Next to find out how to install (aarch64) ARM64 Machinekit. > > Are there yet arm64 Machinekit packages online ? > > Or > > What are the commands for building mk-hal/cnc from source (been a while > > since I last built debs...) > > It's been ages since I've compiled from source. I always just look at > the CI files and do it manually: > > https://github.com/machinekit/machinekit/blob/master/.travis.yml#L92 > > https://github.com/machinekit/machinekit/blob/master/scripts/build_docker > > -- > Charles Steinkuehler > cha...@steinkuehler.net > -- 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/2f044baa-5fc8-4622-a239-c6fda597c0b9%40googlegroups.com.
Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
I think 96boards provides schematics for most of their boards, when I get home I’ll look at it but I “think” the differential signaling is done with the FPGA, not external hardware. If that’s the case I would just see if it’s possible to change them to straight I/O pins which is better suited to hm2. That connector is meant as a high speed board to board interconnect but it’s not something I think really matters for machine control. You want differential signaling to cancel out noise on the wires leaving the board, you don’t need it to data at high speeds. If possible it’s better to program them as straight gpio pins and use external circuits that are tolerant to field voltages to handle differential splitting. Sent from my iPhone > On Aug 27, 2019, at 5:56 AM, Michael Brown wrote: > > Thinking DExx gpio wise: > > As I'm struggeling to find out exact how fast a datarate the pins on the > Mezzaine connector have, this is just pure speculation, however: > > The mezzanine has 16 differential I/O's (plus some dedicated differential > clock pins), So it might be possible to > create a highspeed serial bus there and route to 2 x 36 parallel GPIO pins > (DExx style) ? > > >> On Tuesday, 27 August 2019 01:01:43 UTC+2, justin White wrote: >> Curious what the current use case for the ultra96 might be. There's >> mezzanines available that are suitable for machine control as far as I'm >> aware. The "high density" "low density" gpio connectors look like a PIA to >> work with. If they stuck that SOC on a form factor similar to the DE10 Nano >> it'd be pretty serious. >> >>> On Monday, August 26, 2019 at 3:15:18 PM UTC-4, Michael Brown wrote: >>> So now have a fully compiled and implemented Ultra96 design, just have to >>> figure out how to test it...(pin file, device tree etc). >>> >>> It would be nice af someone could spin up a 2018.3 Vivado Docker Image... >>> (or input some very verbose instructions as to how) :-) >>> > > -- > 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/7cd05f66-8917-489b-92a4-8e2d7e2317fc%40googlegroups.com. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/BEE882D7-84F1-4752-944A-500A0E246F0E%40gmail.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] VFD for 180v DC motor
Succefully moded the board for PNP ouptup, i'm happy reverse all led, swap pin 3/4 and swap Gnd/Vcc Br -- 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/10ad12cb-6992-4ce5-aa4b-a012099f30a4%40googlegroups.com.
Re: [Machinekit] Re: Broken CRAMPS.bbio
On 8/26/2019 11:07 PM, c.glas...@cox.net wrote: > AXIS comes up fine but NOBODY is home, nothing moves it's as though the > CRAMPS board is not even there. > > Is the uEnv.txt file correct? Any other suggestions as to resolving the > absence of functionality? Usually the "totally dead" symptom results from not having one of the CRAMPS power rails connected. In addition to the 5V coming from the BeagleBone, you need to have some/all of the following power rails connected: P201: Motor power (for the Pololu stepper drivers) P401: Bed power (for the heated bed output: P403) P402: Ext power (for the extruder outputs: E0-E2) P404: Aux power V+ (for low-power outputs: FET5-FET6) Also check your ESTOP chain and the status of the LEDs: BB ON : Should always be on STATUS: Application dependent (driven by GPIO pin) ACTIVE: Should be on when machine power is active (F2) ESTOP : Should be on until the machine is out of ESTOP (F1) -- Charles Steinkuehler char...@steinkuehler.net -- 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/eb30eb12-2576-30a7-54da-95879da791e4%40steinkuehler.net.
Re: [Machinekit] VFD for 180v DC motor
Le mardi 27 août 2019 14:21:29 UTC+2, Aurelien a écrit : > > Hi > > Can you confirm do this change to optoisolator can work fine ? > > > -- 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/78e8a163-ab9e-45b0-b574-eb6281144350%40googlegroups.com.
Re: [Machinekit] VFD for 180v DC motor
Le mardi 27 août 2019 14:21:29 UTC+2, Aurelien a écrit : > > Hi > > Can you confirm do this change to optoisolator can work fine ? > > > -- 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/5ece7678-1ef4-4558-926b-bc47a1ad6c05%40googlegroups.com.
Re: [Machinekit] VFD for 180v DC motor
Hi Can you confirm do this change to optoisolator can work fine ? -- 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/57640384-92e8-43ae-a510-ea4de6f09877%40googlegroups.com.
Re: [Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96
Thinking DExx gpio wise: As I'm struggeling to find out exact how fast a datarate the pins on the Mezzaine connector have, this is just pure speculation, however: The mezzanine has 16 differential I/O's (plus some dedicated differential clock pins), So it might be possible to create a highspeed serial bus there and route to 2 x 36 parallel GPIO pins (DExx style) ? On Tuesday, 27 August 2019 01:01:43 UTC+2, justin White wrote: > > Curious what the current use case for the ultra96 might be. There's > mezzanines available that are suitable for machine control as far as I'm > aware. The "high density" "low density" gpio connectors look like a PIA to > work with. If they stuck that SOC on a form factor similar to the DE10 Nano > it'd be pretty serious. > > On Monday, August 26, 2019 at 3:15:18 PM UTC-4, Michael Brown wrote: >> >> So now have a fully compiled and implemented Ultra96 design, just have to >> figure out how to test it...(pin file, device tree etc). >> >> It would be nice af someone could spin up a 2018.3 Vivado Docker Image... >> (or input some very verbose instructions as to how) :-) >> >> -- 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/7cd05f66-8917-489b-92a4-8e2d7e2317fc%40googlegroups.com.
Re: [Machinekit] Re: DE10 Nano suggested development environment?
That PR is waiting for the finalizing your pin file: https://github.com/the-snowwhite/mksocfpga/blob/sserial-work/HW/hm2/config/DExx_Nano_xxx_Cramps/PIN_st_fpga_soc_dc1f_ss.vhd after the PR is then commited and approved: When the MKSocfpga changes are merged the changes will show up in the mk deb (socfpga-rbf) packages, then you don't have to build yourself. On Tuesday, 27 August 2019 00:51:56 UTC+2, justin White wrote: > > BTW, have the DExx-cramps changes been merged in a way that I can do a > docker build on my end yet? > > On Monday, August 26, 2019 at 6:49:23 PM UTC-4, justin White wrote: >> >> There are comm errors thrown after discovery as mentioned on git, trying >> to determine if its the hardware or MK's hm2 driver ATM, Still a bit >> difficult to determine without a verifiable working instance of SS in >> current MK systems. >> >> -- 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/adcf4609-5ccb-429d-92af-112a75fb43a1%40googlegroups.com.
