One of the causes is gbr. In the SGL system, gbr is used as the start address of the system variable area, and data is read and written from there using relative loading.
However, currently nothing is set in gbr, so it will not work as is.
So, it doesn't mean that it will work if you set gbr. This is a problem that depends on each CPU's cache. Data updated on the other CPU must be retrieved using a cache-through address, but SGL functions are not designed to retrieve that data using a cache-through address. Since SGL is running on each other's CPUs, the problem of system variable consistency is considered to be very large, so we cannot guarantee that it will work properly.
For the above reasons, avoid using SGL functions in slaves. SGL Think of the basic slave position as being for calculation (geometry engine).