Advanced Search

Current state of Trixie:
Images build fine & boot, with non rt kernel.

6.12.47 kernel crashes
6.12.47 headers cant' be installed due to gcc version issues

6.12.34 kernel is good
6.12.34 headers can't be installed due to gcc version issues

Issues installing Linuxcnc built from image below wont install due to version issues with a lot of packages.

Using Trixie image downloads.raspberrypi.com/raspios_arm64/...-trixie-arm64.img.xz can have 6.12.34 kernel & headers installed.

I'll have to do some greater investigation.

Wanna know a secret, I did a big stupid, didn't realise the image was armf instead of arm64.

Current state of Bookworm.
All appears to be good, build process needs some tweaks, login screen and having xfce the default desktop plus a few little more odds and sods. Basically it works, just would like it a little more user friendly. Good thing regarding this build system is you can set your OS settings when using RPi-Imager, something that was not possible with the earlier build system.

Non necessary stuff (eyecandy), would like to have a linuxcnc themed splash screen (plymouth theming), login background (lightdm config) and desktop background. Just some Linuxcnc "branding".

How close are you, and how can I help? It's been three or four years since I worked on an ST ARM core, but I do work in the embedded world all the time, and I'm happy to be of assistance. With a little bit of digging, I can probably even find my old ST background debug dongle and the tools to support it.

I presently have a strong interest in seeing this project through to completion. I have been standardizing my computer controlled systems on a Bigtreetech Manta M8P board, which basically is a breakout board for a Raspberry Pi CM4 with an ST32H723ZET6 on it to run the lower-level stuff. I've had very good luck with it using it for Klipper/Mainsail/Crowsnest to run a 3D printer. And since the stepper drivers I want to use to drive the motors on my milling machine drop right in, I'd like to bridge LinuxCNC to it. The higher current drivers (like variants of the TMC5160) use SPI, so I'd need that driver. And it'd be nice to be able to poll a few GPIO's so I can move the mill bed with a joystick for setup. But it shouldn't be *that* difficult, I don't think.

Just let me know if/how I can contribute.

Yes you are almost there.
Just the pins are named lcec.0.0.something I would think. Second zero refers to ethercat slave id.
It's a bit catch 22. Easiest way to check pin names is with halshow and for that linuxcnc need to run and for that you need the pin names.
One can possibly temporarily comment out all reference to lcec.0.everything to use halshow to check the names.
Or use the name="X" in the slave line i  ethercat-conf.xml and refer to lcec.0.X.something.

hi there,

I think you have to check if drivers is running at FHPP or Cia402 protocol shape .. It is configurable and it should be hidden pain...

then you have to setup the SDOs and then PDOs  for Cia402 

If you are familiar with twincat 3 I can recommend it for you to jog motor from scratch... if it will jog over them just swap yout master to lcec

regards 

 

ok, i used your file, added your tools to the tool library, ran PB, homed, loaded your file, moved to a spot and set G54 using G10 L2 P1 X Y Z, then did the same for G55 and G56 and no error here,, im not near my machine with the actual probe to set things that way so can you test by the method above and see if you get the same backplot error that way? if not i will have to test next im at the shop near the machine.