Sync length does not correspond to actual packet sync length

[IBims1NicerTobi]

In stm32wl3x_ll_mrsubg.h the register is directly set the sync length value, however according to the reference manual of the stm32wl3 series page 882 a value of 0 in the register field corresponds to a value of 1 in the packet. This is inconsistent with the x-cube-subg2 radio settings.

[MKISTM]

Hello @IBims1NicerTobi,

Thank you for your report. Could you please add more details so that I can support you further and better understand the issue?

Best Regards,
KIWA Mohamed Chaker.

[IBims1NicerTobi]

Setting a sync word length in MRSubG_PcktBasicFields_t leads to an actual sync word length that is one bit longer.

[IBims1NicerTobi]

What details are you missing?

[MKISTM]

Hello @IBims1NicerTobi,

Sorry, but I still have trouble understanding your issue.
Could you clarify what the issue is exactly? I do not see any inconsistency between the driver and the reference manual.
Could you please provide enough details so that I can support you further?

Best Regards,
Mohamed Chaker KIWA.

[IBims1NicerTobi]

The LL_MRSubG_SetSyncLength function writes the value of uint8_t cSyncLength directly into the PCKT_CONFIG_SYNC_LEN. However the reference manual clearly states that writing a 0 in that field leads to a sync length of 1 in the actual packet.

So somewhere between the user calling HAL_MRSubG_PacketBasicInit and LL_MRSubG_SetSyncLength the value needs to be increased by one. Also while writing this I noticed the SyncLength fields documentation states that valid values are from 1 to 64 while actual valid values are 1 to 31 right now or 0 to 32 in reality.

[MKISTM]

Hello @IBims1NicerTobi,

Regarding the documentation you are right and the SyncLength must <=32 but I didn't understand why the value needs to be increased by one?
Where is the problem when writing a 0 in that field leads to a sync length of 1 that is expected according to the reference manual!?

Best Regards,
Mohamed Chaker KIWA.