Litexcnc install #107

horcsab · 2024-08-15T16:07:37Z

horcsab
Aug 15, 2024

Dear Peter,

I replaced the PC with a new one and I am experiencing the following installation problem.
Linuxcnc Debian 12 Bookworm PREEMPT-RT ISO freshly installed.
Python3, pip3 installed and Litexcnc installed.

Oss-cad-suite is also installed.
When compiling firmware (litexcnc build_firmware *.json --build) I always get the error "Litex is not installed. Please run 'litexcnc install_litex' first."

If I issue the litexcnc command, it shows the litex commands (build_firmware, convert, flash,...).

What can I do wrong, what might not be set correctly?

Peter-van-Tol · 2024-08-15T16:24:22Z

Peter-van-Tol
Aug 15, 2024
Maintainer

At this moment I'm on holiday, so have this answer is from my mobile phone and from my head. My apologies, more detailed answer I can send on Sunday.

I see that the documentation / error message is maybe outdated. The command litexcnc install_litex has been replaced with litexcnc install_toolchain; did you run this command? If not, this will solve your error.

Will change the error message.

3 replies

kzali Aug 16, 2024

@horcsab

This is what I used on Ubuntu. I found this in one of the discussions:

sudo apt-get update && sudo apt-get -y upgrade
sudo apt-get install python3-pip python3-wheel python3-venv
python3 -m venv ~/.local --system-site-packages
echo -e "" >> ~/.bashrc
echo -e "# set PATH so it includes user's private bin if it exists" >> ~/.bashrc
echo -e "if [ -d "$HOME/.local/bin" ] ; then" >> ~/.bashrc
echo -e " PATH="$HOME/.local/bin:$PATH"" >> ~/.bashrc
echo -e "fi" >> ~/.bashrc
. ~/.bashrc
pip install litexcnc[cli]

litexcnc install_toolchain --user
sudo env "PATH=$PATH" litexcnc install_driver
. ~/.bashrc

Of course Peter is way more competent. Maybe this helps

Peter-van-Tol Aug 16, 2024
Maintainer

You're spot on with the recipe 👍, cannot improve on that.

horcsab Aug 16, 2024
Author

@horcsab

This is what I used on Ubuntu. I found this in one of the discussions:

sudo apt-get update && sudo apt-get -y upgrade sudo apt-get install python3-pip python3-wheel python3-venv python3 -m venv ~/.local --system-site-packages echo -e "" >> ~/.bashrc echo -e "# set PATH so it includes user's private bin if it exists" >> ~/.bashrc echo -e "if [ -d "$HOME/.local/bin" ] ; then" >> ~/.bashrc echo -e " PATH="$HOME/.local/bin:$PATH"" >> ~/.bashrc echo -e "fi" >> ~/.bashrc . ~/.bashrc pip install litexcnc[cli]

litexcnc install_toolchain --user sudo env "PATH=$PATH" litexcnc install_driver . ~/.bashrc

Of course Peter is way more competent. Maybe this helps

kzali and Peter,
Thank you for your help!
The problem was solved, I reinstalled the machine and then installed it according to the above instructions. It worked!

Have a nice rest everyone!

Regards, Csaba

horcsab · 2024-08-16T13:59:10Z

horcsab
Aug 16, 2024
Author

So, next problem,

firmware build...

FUW400-5A-75E.json

build error,

Traceback (most recent call last):
File "/home/cnc/.local/bin/litexcnc", line 8, in
sys.exit(cli())
^^^^^
File "/home/cnc/.local/lib/python3.11/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/cnc/.local/lib/python3.11/site-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "/home/cnc/.local/lib/python3.11/site-packages/click/core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/cnc/.local/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/cnc/.local/lib/python3.11/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/cnc/.local/lib/python3.11/site-packages/litexcnc/cli/build_firmware.py", line 37, in cli
firmware_config = LitexCNC_Firmware.parse_raw(' '.join(config.readlines()))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "pydantic/main.py", line 549, in pydantic.main.BaseModel.parse_raw
File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj
File "/home/cnc/.local/lib/python3.11/site-packages/litexcnc/firmware/soc.py", line 65, in init
current_module = subclass(**current_module)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "pydantic/main.py", line 341, in pydantic.main.BaseModel.init
pydantic.error_wrappers.ValidationError: 4 validation errors for PWM_ModuleConfig
instances -> 0 -> pin
field required (type=value_error.missing)
instances -> 1 -> pin
field required (type=value_error.missing)
instances -> 2 -> pin
field required (type=value_error.missing)
instances -> 3 -> pin
field required (type=value_error.missing)

What am I not setting correctly in the pwm section?

6 replies

horcsab Aug 16, 2024
Author

I changed the keyword to pin, but the error is the same.

instances -> 0 -> pin
str type expected (type=type_error.str)
instances -> 1 -> pin
str type expected (type=type_error.str)
instances -> 2 -> pin
str type expected (type=type_error.str)
instances -> 3 -> pin
str type expected (type=type_error.str)

Peter-van-Tol Aug 16, 2024
Maintainer

The error is different, it now says it expects the name of the pin. So this means you have to install the latest version from GitHub instead of PyPi.

pip install git+https://github.com/Peter-van-Tol/LiteX-CNC

Peter-van-Tol Aug 16, 2024
Maintainer

Above should install the development version, which includes the feature you are looking for.

No further installations required.

horcsab Aug 16, 2024
Author

Thanks Peter!
It worked!

Peter-van-Tol Aug 16, 2024
Maintainer

You're welcome.

Please share your experience with LitexCNC.

horcsab · 2024-08-17T06:57:13Z

horcsab
Aug 17, 2024
Author

Good morning,

nc@cnc:~$ halrun
halcmd: loadrt litexcnc connections="eth:192.168.12.20"
Note: Using POSIX realtime
litexcnc: Loading Litex CNC driver version 1.2.4
litexcnc: Loading and registering default modules:
litexcnc: Registered module gpio
litexcnc: Registered module pwm
litexcnc: Registered module encoder
litexcnc: Registered module step
litexcnc: Setting up board drivers:
litexcnc: Registered driver eth
LitexCNC-eth: connected to board on '192.168.12.20:1234'
litexcnc: INFO: Version of firmware (1.3.0) is different with the version of the driver (1.2.4). Communication is still possible, although the firmware could use an update for the best experience.
litexcnc: Setting up modules...
litexcnc: Reading 28 bytes
litexcnc: - Watchdog
litexcnc: - Wallclock
litexcnc: - gpio ... done!
litexcnc: Out of memory!
litexcnc: Failed to instantiate module: 'pwm'
litexcnc: - pwm ...board fails LitexCNC registration
litexcnc: Failed to initialize the driver.
litexcnc: rtapi_app_main: Invalid argument (-22)
:1: waitpid failed /usr/bin/rtapi_app litexcnc
:1: /usr/bin/rtapi_app exited without becoming ready
:1: insmod for litexcnc failed, returned -1
halcmd:

What could be the problem?
Flash, ping, ok.

0 replies

Peter-van-Tol · 2024-08-17T13:58:26Z

Peter-van-Tol
Aug 17, 2024
Maintainer

I see this as a bug. Break down of what happens: - the error only happens when memory cannot be allocated for a module, i.e. `pwm` in this case; - I don't think this is hardware related, so most-likely the byte with the number of instances received from the FPGA is zero (which prevents allocation of memory); - either in the firmware there is an error or in the driver. Going to check which part has been changed with the latest modification, as this behavior I didn't experience before. Op za 17 aug 2024 om 08:57 schreef Csaba Horvath ***@***.***>:

…

Good morning, ***@***.***:~$ halrun halcmd: loadrt litexcnc connections="eth:192.168.12.20" Note: Using POSIX realtime litexcnc: Loading Litex CNC driver version 1.2.4 litexcnc: Loading and registering default modules: litexcnc: Registered module gpio litexcnc: Registered module pwm litexcnc: Registered module encoder litexcnc: Registered module step litexcnc: Setting up board drivers: litexcnc: Registered driver eth LitexCNC-eth: connected to board on '192.168.12.20:1234' litexcnc: INFO: Version of firmware (1.3.0) is different with the version of the driver (1.2.4). Communication is still possible, although the firmware could use an update for the best experience. litexcnc: Setting up modules... litexcnc: Reading 28 bytes litexcnc: - Watchdog litexcnc: - Wallclock litexcnc: - gpio ... done! litexcnc: Out of memory! litexcnc: Failed to instantiate module: 'pwm' litexcnc: - pwm ...board fails LitexCNC registration litexcnc: Failed to initialize the driver. litexcnc: rtapi_app_main: Invalid argument (-22) :1: waitpid failed /usr/bin/rtapi_app litexcnc :1: /usr/bin/rtapi_app exited without becoming ready :1: insmod for litexcnc failed, returned -1 halcmd: What could be the problem? Flash, ping, ok. — Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUVAUEOUW4664CJP4H74L3ZR3X55AVCNFSM6AAAAABMSPBQ2SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZWGQ3TKMI> . You are receiving this because you commented.Message ID: ***@***.*** com>

0 replies

Peter-van-Tol · 2024-08-17T14:14:50Z

Peter-van-Tol
Aug 17, 2024
Maintainer

Quick check: after installing the development version of the firmware, did you also re-install the driver? There has been a change in the driver which could explain the behavior you are experiencing. Op za 17 aug 2024 om 15:58 schreef Peter Van Tol ***@***.***>:

…

I see this as a bug. Break down of what happens: - the error only happens when memory cannot be allocated for a module, i.e. `pwm` in this case; - I don't think this is hardware related, so most-likely the byte with the number of instances received from the FPGA is zero (which prevents allocation of memory); - either in the firmware there is an error or in the driver. Going to check which part has been changed with the latest modification, as this behavior I didn't experience before. Op za 17 aug 2024 om 08:57 schreef Csaba Horvath ***@***.*** >: > Good morning, > > ***@***.***:~$ halrun > halcmd: loadrt litexcnc connections="eth:192.168.12.20" > Note: Using POSIX realtime > litexcnc: Loading Litex CNC driver version 1.2.4 > litexcnc: Loading and registering default modules: > litexcnc: Registered module gpio > litexcnc: Registered module pwm > litexcnc: Registered module encoder > litexcnc: Registered module step > litexcnc: Setting up board drivers: > litexcnc: Registered driver eth > LitexCNC-eth: connected to board on '192.168.12.20:1234' > litexcnc: INFO: Version of firmware (1.3.0) is different with the version > of the driver (1.2.4). Communication is still possible, although the > firmware could use an update for the best experience. > litexcnc: Setting up modules... > litexcnc: Reading 28 bytes > litexcnc: - Watchdog > litexcnc: - Wallclock > litexcnc: - gpio ... done! > litexcnc: Out of memory! > litexcnc: Failed to instantiate module: 'pwm' > litexcnc: - pwm ...board fails LitexCNC registration > litexcnc: Failed to initialize the driver. > litexcnc: rtapi_app_main: Invalid argument (-22) > :1: waitpid failed /usr/bin/rtapi_app litexcnc > :1: /usr/bin/rtapi_app exited without becoming ready > :1: insmod for litexcnc failed, returned -1 > halcmd: > > What could be the problem? > Flash, ping, ok. > > — > Reply to this email directly, view it on GitHub > <#107 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACUVAUEOUW4664CJP4H74L3ZR3X55AVCNFSM6AAAAABMSPBQ2SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMZWGQ3TKMI> > . > You are receiving this because you commented.Message ID: > ***@***.*** > com> >

1 reply

horcsab Aug 17, 2024
Author

A driver update solved this problem.

However, I find that the ethernet connection is disconnected for some reason. During continuous pinging, the connection is interrupted more and more often, and then the connection with the card is terminated.

Could the card be faulty?
5A-75E v8.0

horcsab · 2024-08-17T16:22:41Z

horcsab
Aug 17, 2024
Author

I tried a previous firmware setting on the card and it works.
I am attaching the previous json file, this ok.
CSABA-5A-75E.json

And new json, is not ok.
FUW400-5A-75E.json

If you have some time, could you check what the error could be? I can't find it.
Thanks!

10 replies

horcsab Aug 19, 2024
Author

Currently, 20kHz PWM is set for the test, but I will reduce this. I am attaching the existing documentation.
At the moment, I only have the basics, I still have a lot to improve on the settings, and the conversion electronics are not perfect yet.

I replaced the 74245 circuits on the colorlight board with SN74CBT3245APWR.With this, the level adjustment was solved and the outputs became bidirectional.

+-10V_pdf_colorlight.pdf

fuw400.zip

Peter-van-Tol Aug 19, 2024
Maintainer

I like the schematics! Gives inspiration of creating my own 0-10 Volt converters.

As I can see in you your HAL, the servo's are running in position mode. Even when running as low as 1 kHz, I have the feeling that the resolution of 400.000 positions along an axis is too low. This ultimately depends on the size of the machine whether this is acceptable. Whilst having tinkered on PWM anyways, I think adding dithering is a good next step. The aim is to make PWM with full 32-bit resolution, independent on the frequency.

Peter-van-Tol Aug 19, 2024
Maintainer

horcsab Aug 20, 2024
Author

Sorry for my bad English. I will try to describe my experience.

I still don't understand a lot about linuxcnc, that's for sure.

The motor drive receives an analog signal, the range of which is +/-10V. According to my experience, it is sufficient to control this with a resolution of 1-2mV.

If I understand correctly, the positioning of linuxcnc works in such a way that the incremental encoder on the motor axis gives the position. And in linuxcnc there is the command position. If these two values differ, the regulating +/-10V signal is created from the difference between these two values. The larger this error is, the larger the signal is, of course with reversed sign.

I don't understand why the resolution of 400,000 would be insufficient for PWM. A value of 40000 should be enough.
I just tried driving an old SOPREL DC motor on the table, which has a 500 pulse/revolution encoder at the end of the shaft.
The encoder is processed with 4x resolution by Linuxcnc and apparently works perfectly. Both at low and high speeds. The maximum speed of the motor is 3000rpm.

Peter-van-Tol Aug 20, 2024
Maintainer

My bad, as I didn't read well enough your HAL-file. The output for your servo-drive determines the speed, not the position! In case of speed, the resolution is well enough. I can still learn everyday! With your explanation, I can follow what you are doing and it should work.

BTW: your English is good enough. It isn't my primary language either!

EhsanRasouli1371 · 2024-12-25T08:37:41Z

EhsanRasouli1371
Dec 25, 2024

hello
I did the installation steps as follows

sudo apt-get update && sudo apt-get -y upgrade
sudo apt-get install python3-pip python3-wheel python3-venv
python3 -m venv ~/.local --system-site-packages
echo -e "" >> ~/.bashrc
echo -e "# set PATH so it includes user's private bin if it exists" >> ~/.bashrc
echo -e "if [ -d "$HOME/.local/bin" ] ; then" >> ~/.bashrc
echo -e " PATH="$HOME/.local/bin:$PATH"" >> ~/.bashrc
echo -e "fi" >> ~/.bashrc
. ~/.bashrc
pip install litexcnc[cli]

litexcnc install_toolchain --user
sudo env "PATH=$PATH" litexcnc install_driver
. ~/.bashrc

But I get this error when building the firmware
config.json

3.43. Executing ABC pass (technology mapping using ABC).

3.43.1. Extracting gate netlist of module `\colorlight_5a_75e' to `<abc-temp-dir>/input.blif'..
Extracted 19030 gates and 26137 wires to a netlist network with 7105 inputs and 4306 outputs.

3.43.1.1. Executing ABC.
Running ABC command: "<yosys-exe-dir>/yosys-abc" -s -f <abc-temp-dir>/abc.script 2>&1
ABC: Bus error
ERROR: ABC: execution of command ""/home/ehsan/toolchain/oss-cad-suite/lib/yosys-abc" -s -f /tmp/yosys-abc-Uy7EKr/abc.script 2>&1" failed: return code 135.
Traceback (most recent call last):
  File "/home/ehsan/.local/bin/litexcnc", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/home/ehsan/.local/lib/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ehsan/.local/lib/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/home/ehsan/.local/lib/python3.11/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ehsan/.local/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ehsan/.local/lib/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ehsan/.local/lib/python3.11/site-packages/litexcnc/cli/build_firmware.py", line 58, in cli
    builder.build(run=build)
  File "/home/ehsan/toolchain/litex/litex/litex/soc/integration/builder.py", line 350, in build
    vns = self.soc.build(build_dir=self.gateware_dir, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ehsan/toolchain/litex/litex/litex/soc/integration/soc.py", line 1205, in build
    return self.platform.build(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ehsan/toolchain/litex/litex/litex/build/lattice/platform.py", line 43, in build
    return self.toolchain.build(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/ehsan/toolchain/litex/litex/litex/build/lattice/trellis.py", line 236, in build
    _run_script(script)
  File "/home/ehsan/toolchain/litex/litex/litex/build/lattice/trellis.py", line 174, in _run_script
    raise OSError("Error occured during Yosys/Nextpnr's script execution.")
OSError: Error occured during Yosys/Nextpnr's script execution.

Can someone tell me how to fix this error?

2 replies

Peter-van-Tol Dec 25, 2024
Maintainer

Will help you after Christmas. Wish you all nice days with family and friends!

EhsanRasouli1371 Dec 25, 2024

Thank you dear Peter
I also wish you and your esteemed family a year full of success

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Litexcnc install #107

{{title}}

Replies: 7 comments 22 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Litexcnc install #107

horcsab Aug 15, 2024

Replies: 7 comments · 22 replies

Peter-van-Tol Aug 15, 2024 Maintainer

kzali Aug 16, 2024

Peter-van-Tol Aug 16, 2024 Maintainer

horcsab Aug 16, 2024 Author

horcsab Aug 16, 2024 Author

horcsab Aug 16, 2024 Author

Peter-van-Tol Aug 16, 2024 Maintainer

Peter-van-Tol Aug 16, 2024 Maintainer

horcsab Aug 16, 2024 Author

Peter-van-Tol Aug 16, 2024 Maintainer

horcsab Aug 17, 2024 Author

Peter-van-Tol Aug 17, 2024 Maintainer

Peter-van-Tol Aug 17, 2024 Maintainer

horcsab Aug 17, 2024 Author

horcsab Aug 17, 2024 Author

horcsab Aug 19, 2024 Author

Peter-van-Tol Aug 19, 2024 Maintainer

Peter-van-Tol Aug 19, 2024 Maintainer

horcsab Aug 20, 2024 Author

Peter-van-Tol Aug 20, 2024 Maintainer

EhsanRasouli1371 Dec 25, 2024

Peter-van-Tol Dec 25, 2024 Maintainer

EhsanRasouli1371 Dec 25, 2024

horcsab
Aug 15, 2024

Replies: 7 comments 22 replies

Peter-van-Tol
Aug 15, 2024
Maintainer

Peter-van-Tol Aug 16, 2024
Maintainer

horcsab Aug 16, 2024
Author

horcsab
Aug 16, 2024
Author

horcsab Aug 16, 2024
Author

Peter-van-Tol Aug 16, 2024
Maintainer

Peter-van-Tol Aug 16, 2024
Maintainer

horcsab Aug 16, 2024
Author

Peter-van-Tol Aug 16, 2024
Maintainer

horcsab
Aug 17, 2024
Author

Peter-van-Tol
Aug 17, 2024
Maintainer

Peter-van-Tol
Aug 17, 2024
Maintainer

horcsab Aug 17, 2024
Author

horcsab
Aug 17, 2024
Author

horcsab Aug 19, 2024
Author

Peter-van-Tol Aug 19, 2024
Maintainer

Peter-van-Tol Aug 19, 2024
Maintainer

horcsab Aug 20, 2024
Author

Peter-van-Tol Aug 20, 2024
Maintainer

EhsanRasouli1371
Dec 25, 2024

Peter-van-Tol Dec 25, 2024
Maintainer