If it does not work according to the documentation, then it is a bug.
If you have read the documentation, and can't figure out how they work, then the documentation is inadequate.
That a function should rather work that way because some other function works that way is not a valid argument.
> Was that the intention of the creators?
To provide a wrapper function for setting every bitfield in every hardware register, because the HAL functions are inadequate, and some users have the notion that register names should not appear in the application code.
> For me it is confusing.
Me too. I could not figure it out yet why do these wrapper functions exist at all.
Some people argue that LL functions have names that are easier to remember and more descriptive as register names. You have provided a perfect counterexample.
Read the TIM1/TIM8 functional description chapter of the reference manual, I am sure there is an illustrated description of a use case similar to yours which explains what you should set in what registers, and why.
Then replace the LL functions in your code with direct register reads, writes and bitwise operations. This will make future maintenance easier, because register and bitfield names can be directly looked up in the reference manual.
If it still does not work, post the contents of the registers, or the initialization code with proper register and bitfield names that can be found in the reference manual, so that other developers like me could look up what is going on, without having to work through multiple levels of definitions in the LL headers.
