Stm32wl55 LoraWAN

[tcpipchip]

Let me see when you have a beta test with stm32lorawan
I can test with au915 and la915 in Brazil.

[StevenCellist]

We have tested the LoRaWAN stack on both STM32duino and STM32Cube (using a custom HAL). Both work fine, so you should be able to give it a go!

[tcpipchip]

Hi @StevenCellist
Did you tested on STM32WL55 ?
If yes, how did you setup
SX1278 radio = new Module(10, 2, 9, 3); ?
and where is the custom HAL and where you copied on STM32 LORAWAN lib ?
I will test here first on LA915, that is a AU915 variant...

[StevenCellist]

I haven't tried the WL55, I've worked with the WLE5 - in most regards close enough.

Regarding the custom HAL, unfortunately I don't have the time to help you now. There is a page on the wiki that explains how you can use RadioLib on other platforms. As per step 2, you should be able to place RadioLib into the Inc/ folder (assuming you're working with STM32CubeIDE), and then go through the process of step 3. You could look at the ESP-IDF example for inspiration on how to use (and create) the HAL.

Note that RadioLib is not the official STM32 LoRaWAN package - it is a different library. And note that RadioLib does not implement LA915 which I'm not really aware of as an official region - where did you get that from?

[tcpipchip]

No problem
Can you send your WLE5 arduino project ?
Here in Brazil, i ported the LA915 to STM32LORAWAN Arduino. LA915 is exclusive of EVERYNET
Now, i want to test RADIOLIB LoRaWAN too...
And finally, add the RADIO LoRaWAN to VISUINO..
and my new plans too, VISUINO today not have LoRaWAN, and the RADIOLIB should be official option...

[StevenCellist]

For use with STM32duino, there is a bunch of examples in RadioLib already: https://github.com/jgromes/RadioLib/tree/master/examples/STM32WLx
Note however that you might need to adapt some (source) code for the WL55 - I am not sure what the actual differences would be w.r.t. the SubGhz Phy for example.

[tcpipchip]

sorry, but those examples are to LoRa, not LoRaWAN

[tcpipchip]

but i will try...

[StevenCellist]

LoRaWAN is just a protocol on top of the radio, so as long as the radio works, LoRaWAN will work just like in the LoRaWAN examples. But I'd first investigate if plain LoRa works to see if the radio and pins etc. are all good.

[tcpipchip]

Yes,
and RADIOLIB LoRa is working perfectly on STM32WL55JCI... our module is the South Korean LSM110A

i am doing this modifications

STM32WLx radio = new STM32WLx_Module();

// set RF switch configuration for Nucleo WL55JC1
// NOTE: other boards may be different!
static const uint32_t rfswitch_pins[] =
{PB12, PC13, PC5};
static const Module::RfSwitchMode_t rfswitch_table[] = {
{STM32WLx::MODE_IDLE, {LOW, LOW, LOW}},
{STM32WLx::MODE_RX, {HIGH, LOW, LOW}},
{STM32WLx::MODE_TX_LP, {HIGH, HIGH, HIGH}},
{STM32WLx::MODE_TX_HP, {HIGH, HIGH, HIGH}},
END_OF_MODE_TABLE,
};

[StevenCellist]

Cool - if you plug that into the LoRaWAN examples, you should be good to go!

[tcpipchip]

[StevenCellist]

Just don't forget to use the RF switch - besides that, looking good!

[tcpipchip]

not sure if i need to include

---> radio.setRfSwitchTable(rfswitch_pins, rfswitch_table);

before the

---> int16_t state = radio.begin();
debug(state != RADIOLIB_ERR_NONE, F("Initialise radio failed"), state, true);

[StevenCellist]

As per the examples and per my comment above - yes.

[tcpipchip]

Can you very if ok ? Attached
LoRaWAN_Starter.zip

[tcpipchip]

Good start
Recognized the STM32WL55 radio

[tcpipchip]

Tryng to find out why said that my KEYS are wrong...

[StevenCellist]

How did you register your device on the Network Server? Can you show a screenshot with the LoRaWAN version, regional parameters and EUIs? If you want to keep the keys hidden that's fine, although you did share them in the .zip already.

[tcpipchip]

#define RADIOLIB_LORAWAN_JOIN_EUI  0x0000000000000000

// the Device EUI & two keys can be generated on the TTN console 
#ifndef RADIOLIB_LORAWAN_DEV_EUI   // Replace with your Device EUI
#define RADIOLIB_LORAWAN_DEV_EUI   0x88571DFFFEEE8C47
#endif
#ifndef RADIOLIB_LORAWAN_APP_KEY   // Replace with your App Key 
#define RADIOLIB_LORAWAN_APP_KEY   0x71,0x1F,0xF8,0xBA,0xD9,0xE7,0x20,0x4B,0xE3,0xF6,0xBD,0xF6,0x96,0xBB,0x98,0xA8

#define RADIOLIB_LORAWAN_NWK_KEY <===not used on OTAA

[StevenCellist]

Please try specifically setting the NwkKey to NULL in activateOTAA() to make sure that RadioLib uses 1.0.4 and does not try to use 1.1.

[tcpipchip]

@StevenCellist
Thanks to help me!

[tcpipchip]

More info

// regional choices: EU868, US915, AU915, AS923, AS923_2, AS923_3, AS923_4, IN865, KR920, CN500
const LoRaWANBand_t Region = AU915;
const uint8_t subBand = 0;  // For US915, change this to 2, otherwise leave on 0

Does subBand should be 1 ?

[StevenCellist]

SubBand should be 2, just as it is on your gateway (and on TTN). The comment only mentions US915 but it applies to AU915 as well.

[tcpipchip]

Hi
on TTN side got JOINED

but on Radiolib side

it´s a progress!

[tcpipchip]

now only getting

[tcpipchip]

Tomorrow I will test if is my power supply the problem.

[HeadBoffin]

is my power supply the problem.

Interesting - what leads you to that conclusion. Takes 4x more power to transmit than to receive so clearly the power is good.

Try reading the Readme written by @CaptainAwesome in the Starter folder and you will fix it without any PSU fiddling at all.

[tcpipchip]

Hi, the powe suppy is not the problem.

[StevenCellist]

The examples come with notes.md which explains how to resolve the error you see - lots of useful stuff in there so recommend to read it all.

[HeadBoffin]

Hi, the powe suppy is not the problem.

Why even test it - read the docs!

[tcpipchip]

yes, i read all.

Someday late i am will be back to my tests...

thanks for your help @StevenCellist

[HeadBoffin]

It very clearly mentions Dev Nonce - try a search??

[tcpipchip]

wow, the problem is that was not implemented the persistent storage in my example...
I will see the ESP32 example...

[HeadBoffin]

OR that you'd not turned off DevNonces in the console - which is a one click solution.

The code for ESP32 persistence is two halves - getting the data to persist is generic - the code to save on an ESP32 is entirely ESP32 only and won't even begin to work on an STM32WL