Showing results for 
Search instead for 
Did you mean: 


Associate II

Using this API returns 0x3157 error code after running SIGFOX_API_close successfully (return code is 0), anyone tried that? What are we missing here?
BTW - Same behavior observed when using ST provided Sigfox_AT_Slave_DualCore example out of the box with the NUCLEO-WL55 board so we can rule out any HW or SW issues , we probably miss some other API call before using the SIGFOX_API_start_continuous_transmission or some ST library bug....

Thanks for your help

P.S. Opened a ticket with ST support, will post here on any further developments.

Andrew Neil
Evangelist III

@ASchw.1 wrote:

Using this API returns 0x3157 error code 

So have you looked-up what that code means?

Associate II

Thanks Andrew,


Well the lower part is defined like this:
SFX_ERR_API_START_CONTINUOUS_TRANSMISSION (sfx_u8)(0x57) /*!< Error occurs during the start continuous transmission : check the manuf error code to get the error */

The high part which is the manuf error code - I couldn't find any reasonable documentation.



did you manage to get an answer to this?

We're facing the same issue.


Associate II

Nothing to work with. They found bugs in their SDK that is only relevant for the Dual Core implementation. The single core version is working fine. No updates or proper answer as for when a fix is expected. ST suggest using single core variant. We ended up rewriting lots of their code as a workaround.