STMicroelectronics / STM32CubeWL

STM32Cube MCU Full FW Package for the STM32WL series - (HAL + LL Drivers, CMSIS Core, CMSIS Device, MW libraries plus a set of Projects running on boards provided by ST (Nucleo boards)
Other
99 stars 52 forks source link

Rx Timeout on join when using the LSI clock #51

Closed rayaanlatief closed 1 year ago

rayaanlatief commented 1 year ago

We have a custom PCB with the stm32wl55 MCU, and for the most part, the reference design was followed. However the LSE crystal was not added.

I have updated the example code and enabled the LSI clock source.

For my application, we are using OTAA.

The join request is received by the gateway and responds to it. However, my end node does not receive the response.

I have tested with the nucleo-wl55 dev board with the LSI clock and disable the LSE clock source the device fails to join, However once enable the LSE clock source the device joins succesfully

IDE used: STM32CubeIDE 1.10.1

RomanJasmann commented 1 year ago

@rayaanlatief

  1. Have you configured the LSI clock to have a tick period below 1 ms?
  2. Have you adapted TIMER_IF_Convert_Tick2ms, TIMER_IF_Convert_ms2Tick and TIMER_IF_GetTime to reflect the LSI clock frequency?
  3. Consider that the LSI RC oscillator can have a high frequency error. The LoRaWAN stack has to be configured properly to tolerate higher timing errors

grafik

http://stackforce.github.io/LoRaMac-doc/LoRaMac-doc-v4.6.0/_p_o_r_t_i_n_g__g_u_i_d_e.html

grafik

RJMSTM commented 1 year ago

Hello @RomanJasmann,

Thank you for this report. We will get back to you as soon as we analyze it further. This may take some time. Thank you for your comprehension.

With regards, Rania

HBOSTM commented 1 year ago

Hello @rayaanlatief ,

Thank you for this contribution. I can't reproduce the problem from my side. So could you please give us more details about how you got this issue? And share a demo of the code you have used to reproduce this issue.

Best Regards,

HBOSTM commented 1 year ago

Hello @rayaanlatief,

Please allow me to close this thread as no activity. You may reopen it at anytime if you have any details to share with us in order to help you to solve the issue. Thank you for your comprehension.

With regards,