Regarding ADC functionality as you have earlier mentioned (in ktrkl thread) a basic evolvable generic intended commit for the hm2soc fpga has recently been accepted revelant links here:
https://github.com/machinekit/mksocfpga/blob/master/HW/QuartusProjects/Common/adc_ltc2308_fifo.sv#L75 https://github.com/machinekit/machinekit/blob/master/src/hal/drivers/mesa-hostmot2/nano_soc_adc.c https://github.com/machinekit/machinekit/pull/1253 This text file describes the full functionality of the 2 registers retained from the Terasic university template ip. The mk driver runs one 8 channel scan in auto channel update mode per cycle. (first 8 reads then setups a new 8 channel scan) I have created following issue to keep the (across camps) discussion visable: https://github.com/machinekit/machinekit/pull/1253 I seek positively framed relevant inputs additions suggestions and commits to update evolve and get the pieces that need corrections molded correctly in the right direction and added whats obviously is missing fro the initial crude but working sketch. :-) https://github.com/machinekit/mksocfpga/blob/master/SW/MK/kernel-drivers/README.md 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 [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
