Replies: 6 comments 3 replies
-
Hi, @acutetech. Thanks for contacting. Hope it helps, Cheers |
Beta Was this translation helpful? Give feedback.
-
Thanks for that. Two comments and two questions: (a) I find it curious that PB5 is available externally but PA4 is not. The two questions: (q1) Given the above, and that their data sheet lists PB5 as "MCU GPIO" with no restriction on its use, I wonder if the pin assignments you sent me are correct? It would be much more helpful if Seeed would release either the circuit diagram or the radio_board_if.h and .c files. Perhaps you can pass on this request. |
Beta Was this translation helpful? Give feedback.
-
Hi Orkhan I just thought you might be interested: A few minutes ago I transferred my first LoRaWan messages to The Thing Network, using the LoRa-E5 on my own PCB. I am using ST's "LoRaWan_End_Node" application code, modified for my hardware, and making adjustments for the LoRa-E5 module. These included the radio pin assignment inforation you sent me. There were many problems to solve on the way, and much testing remaining, but I thought it is worth reporting here that it can be done! I had to make guesses on a number of questions, and I am upset that Seeed refuse to share their radio_board_if.h & .c Have you managed to communicate on your own board? If so, can we exchange radio_board_if.h & .c files? |
Beta Was this translation helpful? Give feedback.
-
Hi, @acutetech (Charles). |
Beta Was this translation helpful? Give feedback.
-
Hi Orkhan Rather than your suggestions I will attach some files here and you can see what you can do with them. My notes to myself follow: So I could accomodate different boards, I created different board_resources_xxx.h files for each board, board_resources.h now specifies one of:
The switches are like this: There are further changes for the radio control - both for the GPIO pin allocation and for the
I added IRQ handlers for all GPIO pins in stm32wlxx_it.c |
Beta Was this translation helpful? Give feedback.
-
Hi Orkhan I have just been told by Seeed that they have published software and some documentation for the LoRa-E5, here: Both that page and the radio_board_if.h file are clear that the two RF control pins are PA4 and PA5, not PA4 and PB5 as your contact at Seeed provided in the email below. I have tried their code and it seems to work. (I have not figured out why my code also worked when I was using the wrong pin!). But my confidence is not high - for instance they seem to have a bug - see my comment here regarding #define RBI_CONF_RFO I note that the settings of the three RF control signals on generic-node-se are the same as on the Nucleo board. Are you using the same RF design at ST? I cannot find the schematics of their Nucleo board. The LoRa-E5 uses the same values on the first two control signals, but does not have the third. I would much prefer to have the schematic of the LoRa-E5 - then I would not have to rely on dubious documentation and code! Your comments welcome. |
Beta Was this translation helpful? Give feedback.
-
Hi Orkhan
I have asked Seeed the following question but not received a reply. Are you able to help?
In order to develop with this module with ST's ST32CUBE IDE development environment further details are essential: which GPIO pins are used to control the TCXO and RF switch, and what do they do? Your radio_board_if.h and .c files will provide this information - can I have these please?
Beta Was this translation helpful? Give feedback.
All reactions