LinuxCNC 2.8.1 configuration doesn't run after upgrading from 2.7.15

That's unfortunately unhelpful.

We see:
./mikron.hal:881: Pin 'hm2_5i24.0.7i69.0.0.input-16' linked to signal 'b3b'
HAL: creating signal 'over'
smalloc_up: shmem available 15552
smalloc_dn: shmem available 15472

But then it stops reporting memory allocation until saying that it is out of memory creating PyVCP pins.

This isn't a good answer, but is there anything in the HAL which isn't actually necessary?
I see "paramsaver" for example.

andypugh wrote: This isn't a good answer, but is there anything in the HAL which isn't actually necessary?
I see "paramsaver" for example.

Mikron has lubrication based on the distance traveled by each axis. Every 2000 mm for example the pump is activated.
The distance is calculated by my component "lubtravel" the product of the speed per fperiod.
the distance traveled between each session is saved with paramsaver
My pleasure is to respect the original management of the machine as closely as possible,
such also the automatic gearbox ratio changes.
And to add more with my "big pendant" all the comfort of conventional controls of a milling machine

I did suggest that trimming back the HAL wasn't the ideal solution.

I think that you are 5 pins from the bottom of the XML file. If you can remove 5 pins from the config it will probably start.

Default configs tend to add a number of ddt functions that are rarely used, for example.

The other alternative is to recompile LinuxCNC with a larger HAL_SIZE. Would you prefer to do that?

what do you mean by "ddt function" ?

I must be able to gain old debug pins in my components for example, but as over time,
the machine will tend to become more complex,:whistle: one day it will be necessary to increase the memory.
Can be wait for the next update, other people may be bored ? plus other issues like the cursor glitch that reappeared on my OLED (lcd.c) that you had solved in 2.7.15

gaston48 wrote: what do you mean by "ddt function"

"ddt" is a HAL module that is used to calculate velocity from position.

Quite often a configuration will have one loaded for each axis, but never used.

Yes, increasing the memory is the long-term solution, but that's no help to you, now.