2022-02-17 08:31 PM
I have function to receive Dev EUI, APP Key, and NWK Key data from UART. Then, I want to put and replace of Dev EUI, APP Key, and NWK Key in se-identity.h with my own data which I have saved in flash memory. But, an error occurs when only include my own file header in se-identity.h after compiling, It also happens to when only include main.h. How can I include my own header file in se-identity.h without error ?
Or maybe there is another way to change Dev EUI, APP Key, and NWK Key without hardcode in se-identity or FUOTA ?
Any assistance would be greatly appreciated
Error occurred:
Solved! Go to Solution.
2022-03-16 06:08 AM
Hello,
Could you try with the new firmware package STM32Cube_FW_WL_V1.2.0 please.
It's working fine for me with the End_Node and AT_Slave projects
Regards
2022-03-10 12:32 AM
Hello,
If you want to modify Dev EUI, App Key etc, you can use the function set/get located in Middleware/LoRaWAN/LmHandler.c to interact with those variables.
Hope it helps
Regards
2022-03-10 01:24 AM
Hi @Louis AUDOLY ,
Thank you for your answer. Maybe, I want to share a screenshot of my main case. This screenshot shows an error occurred when I added #include "main.h" in the se-identity.h and compile it. Maybe there is information regarding the troubleshooting, that would be very helpful.
Thank you
2022-03-16 06:08 AM
Hello,
Could you try with the new firmware package STM32Cube_FW_WL_V1.2.0 please.
It's working fine for me with the End_Node and AT_Slave projects
Regards
2022-03-25 01:12 AM
Hi @Louis AUDOLY ,
Thank you for your suggestion. I have tried the new firmware package STM32Cube_FW_WL_V1.2.0 and it's working fine. But, an error occurred when I put TIM_HandleTypeDef in my code. I don't know why it happened, because I just use directly from the example project (LoRaWAN_End_Node) and library was complete.
The error is like this:
error: unknown type name 'TIM_HandleTypeDef'; did you mean 'RTC_HandleTypeDef'?
2022-03-28 08:52 PM
I check in stm32wlxx_hal_conf.h, the HAL driver for timer module is not enabled. After I activate it, no more error.