Update to below

This morning I have been able to get a turret knee mill in my workshop, which already has a 7i76
board in the controller head, working with the DE0-Nano-Soc

This after the semi-obligatory 'brain-fade' where I forgot how I had powered the 5v source to the 7i76
and could not work out why the 7i76 was 'missing'.
The answer is that the DE0-Nano does NOT supply a 5v feed as the 5i25 will do, so you must wire
one in and change the W2 jumper accordingly - thanks for the prompt Bas!

I used the debian-8.4 image as below, NOT upgraded.
As previously, there is some as yet undetermined problem with the instantiable driver, or the related
changes in the later image. 
The earlier driver and image work fine though.

The configuration is identical to my original 5i25-7i76 one, except for the [HOSTMOT2] section of the ini

[HOSTMOT2]
DRIVER=hm2_soc_ol
BOARD=de0n
CONFIG="firmware=socfpga/dtbo/DE0_Nano_SoC_DB25.7I76_7I76_7I76_7I76.dtbo num_encoders=2 num_stepgens=4"

The .hal file begins with

loadrt trivkins
loadrt tp
loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES  tp=tp kins=trivkins
loadrt hostmot2 debug_idrom=1 debug_modules=1
loadrt [HOSTMOT2](DRIVER) config=[HOSTMOT2](CONFIG)

NB. if you copy & paste from the sample config, note that tp=tp kins=trivkins is commented out in that config

The eagle eyed amongst you may have spotted that I specified encoders=2 in the config line

Each header on the 5i25 and thus the Nano, only has 4 stepgens and 1 encoder, what this does is effectively enable the second DB25 header output socket on Charles's
interface board (equivalent to the header P2 on the 5i25) and the encoder.01 can be accessed from that.

I use the second encoder solely for a hardware pendant MPG on this mill, all the IO for the switches etc on that pendant go onto the 7i76 and are dealt with on the primary header.

My aim for the DE0-Nano, is to replace the parport based controller setup on my slant-bed lathe, with this board and interface running headless and
accessed via the existing computer with the lathe

Congratulations and thanks to Charles Steinkuehler, Michael Haberler, Michael Brown and Devin Hughes for their parts in getting this to fruition.

It is a major achievement


On 13/11/16 14:16, [email protected] wrote:
URLs got corrupted somehow

Should of course be

http://www.mgware.co.uk/temp/debian-8.4-machinekit-de0-armhf-2016-07-20-4gb.bmap
and
http://www.mgware.co.uk/temp/debian-8.4-machinekit-de0-armhf-2016-07-20-4gb.img.xz

ie dot not forward slash after co

On 13/11/16 13:32, [email protected] wrote:
I have temporarily hosted it at

http://www.mgware.co/uk/temp/debian-8.4-machinekit-de0-armhf-2016-07-20-4gb.bmap
and
http://www.mgware.co/uk/temp/debian-8.4-machinekit-de0-armhf-2016-07-20-4gb.img.xz

Create the card image with
bmaptool copy debian-8.4-machinekit-de0-armhf-2016-07-20-4gb.img  /dev/sdX
from the extracted image

Set the MAC code for the NIC on first boot as before, but when booted into the rootfs, update apt but do not run
apt-get upgrade, or you will get later files and kernel and this is what does not work for me

regards


On 13/11/16 11:36, Chen Cheng Xi wrote:
Dear schooner,

Would you mind share with me the debian-8.4 image link?
I am struggle with it now.

Thanks!
-chengxi

On Sun, Nov 13, 2016 at 8:15 PM, [email protected] <[email protected]> wrote:

On 13/11/16 10:52, [email protected] wrote:

Now , both with an upgraded 8.4 image and a new 8.5 image, the hm2_soc_ol module errors thus

Nov 12 15:05:36 mksocfpga msgd:0: startup pid=2818 flavor=rt-preempt rtlevel=1 usrlevel=1 halsize=524288 shm=Posix gcc=4.9.2 version=unknown
Nov 12 15:05:36 mksocfpga msgd:0: ØMQ=4.0.5 czmq=3.0.2 protobuf=2.6.1 libwebsockets=<no version symbol>
Nov 12 15:05:36 mksocfpga msgd:0: configured: sha=ba632dd
Nov 12 15:05:36 mksocfpga msgd:0: built:      Nov 12 2016 12:30:29 sha=ba632dd
Nov 12 15:05:36 mksocfpga msgd:0: register_stuff: actual hostname as announced by avahi='mksocfpga.local'
Nov 12 15:05:36 mksocfpga msgd:0: zeroconf: registering: 'Log service on mksocfpga.local pid 2818'
Nov 12 15:05:36 mksocfpga msgd:0: rtapi_app:2823:user accepting commands at ipc:///tmp/0.rtapi.a42c8c6b-4025-4f83-ba28-dad21114744a
Nov 12 15:05:36 mksocfpga msgd:0: hal_lib:2823:rt hm2: loading Mesa HostMot2 driver version 0.15
Nov 12 15:05:37 mksocfpga msgd:0: hal_lib:2823:rt hm2_soc_ol: loading Mesa AnyIO HostMot2 socfpga overlay driver version 0.9
Nov 12 15:05:37 mksocfpga msgd:0: zeroconf: registered 'Log service on mksocfpga.local pid 2818' _machinekit._tcp 0 TXT "uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" "instance=7759df84-a8e9-11e6-9629-bad04a9c4ece"
Nov 12 15:05:39 mksocfpga rtapi:0: hal_call_usrfunct(newinst,config="firmware=socfpga/dtbo/DE0_Nano_SoC_DB25.7I76_7I85S_GPIO_GPIO.dtbo num_stepgens=4 num_encoders=1 num_mencoders=4") failed: -1 - Operation not permitted
Nov 12 15:05:39 mksocfpga msgd:0: hal_lib:2823:rt hm2_soc_ol: failed to map hm2-socfpg0 to /dev/uioX
Nov 12 15:05:39 mksocfpga msgd:0: hal_lib:2823:rt hm2_soc_ol: soc_mmap_fail hm2-socfpg0
Nov 12 15:05:39 mksocfpga msgd:0: hal_lib:2823:rt hm2/foo: failed to program fpga, aborting hm2_register
Nov 12 15:05:39 mksocfpga msgd:0: hal_lib:2823:rt foo: hm2_soc_ol_board fails HM2 registration
Nov 12 15:05:39 mksocfpga msgd:0: hal_lib:2823:rt hm2_soc_ol: error registering UIO driver
Nov 12 15:05:39 mksocfpga msgd:0: rtapi_app:2823:user hal_call_usrfunct(newinst,config="firmware=socfpga/dtbo/DE0_Nano_SoC_DB25.7I76_7I85S_GPIO_GPIO.dtbo num_stepgens=4 num_encoders=1 num_mencoders=4") failed: -1
Nov 12 15:05:40 mksocfpga msgd:0: hal_lib:2823:rt hm2: ignoring request to unregister foo: not found
Nov 12 15:05:40 mksocfpga msgd:0: hal_lib:2823:rt hm2: unloading

This happens irrespective of whether there is a 7i76 attached and is so early in the process that it is something fairly fundamental
eg
`hm2_soc_ol: failed to map hm2-socfpg0 to /dev/uioX`

I am currently in the process of making a debian-8.4 image based card and trying that, in the meanwhile any ideas???

BTW the debian-8.5 image does not seem to include `xauth`, so that needs to be added before you can ssh into it and get X forwarding working.

For whatever reason, the debian-8.5 image does not work

Just wrote the 8.4 image and did NOT upgrade anything and although not tested yet, the pins are created



--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
--- You received this message because you are subscribed to a topic in the Google Groups "Machinekit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/machinekit/wqH_V52qdQY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to machinekit+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.



--
Best regards!
陈成细
R&D Engineer
(\__/)
(='.'=) This is Bunny. Copy and paste bunny into your
(")_(") signature to help him gain world domination.

--
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.

--
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.

--
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.

Reply via email to