We are planning to build a synergy project that connects to Azure Cloud.
Since we are new to the synergy platform, we are looking for a sample project.
Can someone help us by sharing any sample project for the synergy platform(S7G2) that uses netxduo/addons/azure_iot/ ?
https://github.com/azure-rtos/netxduo/tree/068a9493ecd5af0024005ce695b992c4b172d6aa/addons/azure_iot
Hello Bhanu,
This is the only project provided by Renesas with the Azure connectivity https://www.renesas.com/us/en/document/scd/synergy-mqtttls-azure-cloud-connectivity-solution-application-project-r11an0337eu0105-rev105-sample
It is written for S5D9 MCU though, but I believe it won't be too difficult to change it to S7G2.
Kind regards,
Sergey
If this response, or one provided by another user, answers your question, please verify the answer. Thank you!
Renesas Engineering Community Moderatorhttps://community.renesas.com/https://academy.renesas.com/https://en-support.renesas.com/knowledgeBase/
Hi Sergey (SWF),
Thanks for sharing the project. We have tried changing the board type to S7G2 and project compilation is successful.
This project is more like a MQTT client rather than using azure_iot SDK and connect to Azure Cloud(https://github.com/azure-rtos/netxduo/tree/068a9493ecd5af0024005ce695b992c4b172d6aa/addons/azure_iot).
Could you please provide your inputs on the following.
- Lets assume we have downloaded "netxduo/addons/azure_iot/" directory from GitHub. How this can be added into any of the project in e2 studio?
Thanks,
Bhanu
As I understand this, you can see how this project is done for RX65N MCU, and then you can make the same project structure for S7G2 as well. But in this case you will need to replace the low level functions as they don't match for RX65N and Synergy.
Thanks for sharing the details.
I have tried having the same project structure for S7G2. i.e., building "netxduo/addons/azure_iot" as library and link it to our application. However, compilation is giving the following error.
c:/renesas/synergy/e2studio_v2021-10_ssp_v2.2.0/toolchains/gcc_arm/9_2019q4/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: s7_sk_snmp_card_solution_202204.elf section `.interp' will not fit in region `ID_CODES'c:/renesas/synergy/e2studio_v2021-10_ssp_v2.2.0/toolchains/gcc_arm/9_2019q4/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: region `ID_CODES' overflowed by 26356 bytes
Can you please help us in resolving this? Please let us know if any additional details are required.
Many Thanks,
Check the linker loader file which is located in the "script" folder of the project and has the ".ld" extension. In it you can see the addresses and sizes of all areas. Here you can also change them.
Seems like this ID_CODES region is too big which is weird because S7G2 has quite a plenty of RAM.
Hi Sergey,
I tried changing the IDCODES as follows and getting an error while loading the program and unable to load any other project afterwards.
Error:
Can you please suggest what needs to be done in this case?
Did you check thoroughly the addresses and the sizes of the memory regions to make sure they are not overlapped?
Seems like you somehow enabled the protection of the debugging interface. Try to use the ALeRASE command as described in the S7G2 User's Manual.
Thanks, Sergey.
Due to IDCODES change in the linker script, protection of the debugging interface got enabled.
I have found another thread in this forum and able to clear the flash.
https://community.renesas.com/mcu-mpu/embedded-system-platform/f/forum/7546/code-flash-erase-issue
Sergey (SWF) said:This is the only project provided by Renesas with the Azure connectivity https://www.renesas.com/us/en/document/scd/synergy-mqtttls-azure-cloud-connectivity-solution-application-project-r11an0337eu0105-rev105-sample It is written for S5D9 MCU though, but I believe it won't be too difficult to change it to S7G2.
We have loaded the ELF on SK-S7G2 after changing the board type. When the board is connected to Ethernet, LEDs are not blinking and we are not sure network stack is up.
Could you please help us with the following queries?
1. How to ensure the board is connected to network and got an IP using DHCP?
2. Any configuration/files needs to be modified after changing the board type from S5D9 to S7G2?
1. Please check this guide https://www.renesas.com/us/en/document/apn/netx-port-ether-module-guide. Here is the information about the sequence of the connection and checking of the status.
2. Frankly I don't know. On the API level it should be the same.
Check the settings of the used RMII-Channel and reset pin in the driver config. Additionally check the RMII pin configuration. They may be different on the S7-SK and the S5D9 Boards and I'm not sure if all the settings are migrated when you change the Board in the BSP-Tab.To check basic functionality and get a template for the right settings you can use a NetX example for the S7-SK, something with a Telnet-Server. Check the jumper settings on the SK.
Pic is just an example, it does not necessarily shows the right settings for the S7-SK!