New project, litehm2: a hostmot2 port to linsn rv901t

Do you really need more than 72 pins? It can be changed, but I'm not 100% sure about the implications ,if linuxcnc handles it without modifications.
In the long run we need this value to be dynamic.
If you need it now, I can look into it.

sensille wrote:

Do you really need more than 72 pins?
 

Not now, but I think about colorlight 5a-75e ...

Now I have got big problem.
I can compile litehm2, but board is unstable, even if compiled your config.
I got <hm2/hm2_lite.0: error finishing read! iter=2380>
(Your firmware gives no this error.)
LinuxCNC 2.9 patched and compiled from sources.
LinuxCNC 2.10 not works at all, of course due to Python.
I'm afraid your project is completely unusable - it works for you only ...

So if my firmware is stable for you, there is still something wrong with your build process?
How about the firmware I built for you?
You can also give me your board.conf and I build a firmware for you to double check.

Btw, I think as of 2 days ago litex now has all my patches in master, linuxcnc has it in master, only mesaflash merge request is pending. It should become easier to build and run once all patches make it into releases.

tuxcnc wrote:

I got <hm2/hm2_lite.0: error finishing read! iter=2380>

The dreaded error in all mesa setups, can be network latency. I had that, too. Turned out to be a bad router in the path. Now I run the card back-to-back on a dedicated network interface and it is rock solid.

Not just Mesa, anything using ethernet will return that error if the comms fail due to latency.
As a general rule, never ever use a Hub or a Switch or a Router between PC and board.
For testing it is ok, but running a machine, never. Direct connection only.