THe 2 nd thing the mksoc hm2 driver will be doing is to probe the uio mapped memory for mesa signatures config settings device name and something delivered by the xilinx version of the firmware.mif protobuf generated rom.
Any of this missing or incorrect will make the driver unload with detailed warnings and errors only shown if you have debug enabled correctly. the error log is named linuxcnc.log and will be in /var or /tmp folder log/ folder .... debug=5 + ??? On Sunday, 22 October 2017 01:30:40 UTC+2, Michael Brown wrote: > > Well welcome Cameron > > I have myself an Snickerdoodle Black on order which I am hoping will be > delivered soon so I will be able to support the effort to get this board > added to the build system. > > First it would be great if you can share which linux image / distribution > you are booting your board on ? > > (Machinekit prefers Debian armhf Jessie or Stretch). > > While being able to compile Machine-kit is a good warm-up exercise the > initial effort lies in attracting the attention of those that have put > considerable effort effort into creating workable bitfiles to write > something here instead of in the krtkl google group list :-) > > The very first thing a machinekit config will be looking for is the/(a) > mksocfpga compatible uio driver in /dev (bitfile loaded from uboot) or a > specified devicetree-overlay file dts -> .dtbo in /lib/firmware/socfpga > which then will load the mesa based fpga mksocfpga hardware config into the > fpga and setup the /dev/uio port to address it. > > --≥ > https://groups.google.com/forum/#!searchin/krtkl-snickerdoodle/machinekit|sort:date/krtkl-snickerdoodle/JDwRRR79uZk/WRcc_QmuAAAJ > > Hmmmm > > Sorry I have been distracted by a now successful personal cyclone v > myth-busting quest. > > Well welcome here and hope the first part of my uninformed answer from > here can gain the momentum to help you forwards anyway :-) > > On Friday, 20 October 2017 19:51:14 UTC+2, Cameron McQuinn wrote: >> >> Hi everyone, >> >> I am trying to get MachineKit running on a Snickerdoodle Black dev board >> from Krtkl. My goal is to eventually get mksocfpga running and build a 3D >> printer controlled remotely via MachineFace. >> >> I managed to compile MachineKit from source, and am trying to start it >> using the 5i25-zynq configuration (I don't actually have a bitstream to >> program the FPGA yet, just trying to get MK running). Starting from the >> command line, MachineKit errors out because the rtapi app gets terminated >> due to "stack smashing". Output to from the terminal is as follows: >> >> MACHINEKIT - 0.1 >> Machine configuration directory is >> '/home/snickerdoodle/machinekit/./configs/hm2-soc-stepper' >> Machine configuration file is '5i25-zynq.ini' >> Starting Machinekit... >> *** stack smashing detected ***: rtapi:0 terminated >> halcmd: cant connect to rtapi_app: -1 (uri= >> uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout >> >> E: 17-10-20 11:16:04 dangling 'DEALER' socket created at >> hal/utils/halcmd_rtapiapp.cc:281 >> 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 >> E: 17-10-20 11:16:11 dangling 'DEALER' socket created at >> hal/utils/halcmd_rtapiapp.cc:281 >> halcmd loadusr io started >> halcmd: cant connect to rtapi_app: -1 (uri= >> uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout >> >> The lines starting with "halcmd:" are repeated until MK finally cleans >> everything up and quits. >> >> Operating system is Ubuntu 16.04, running an rt_preempt kernel that I >> compiled from source. Running "uname -a" gives "Linux snickerdoodle >> 4.9.0-rt1-snickerdoodle-68568-gfc719c0-dirty #1 SMP Tue Oct 10 19:54:36 MDT >> 2017 armv7l armv7l armv7l GNU/Linux". Contents of linuxcnc.log are at >> https://pastebin.com/0UPpnCb7. Git log shows: >> commit 15d5a3f6b1ac1760d3ec68c853b5c1e2e0101533 >> Merge: d88049e def2443 >> Author: Bas de Bruijn >> Date: Fri Oct 13 09:53:46 2017 +0200 >> >> Interestingly, I have to "export FLAVOR=rt-preempt" in the shell before >> attempting to start machinekit, or else it tries to load rtapi_app_posix, >> which I did not compile. >> >> If anyone can point me towards a solution and help me get MachineKit >> running, I would be very grateful. >> >> Thanks, >> Cameron >> > -- 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.
