This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Trying posting this again:
I am using the STM32Cube (IDE 1.12.0) tools to develop a simple network application in Azure RTOS on the Nucleo-H723G platform. I successfully imported and ran the online workshop NetX Duo Webserver project. The project is based on an older Azure RTOS package set. I created a new project with the latest packages, and enabled all the Azure RTOS and MCU setting equivelent to the workshop example. The firmware pops a hardfaul on the nx_ip_address_change_notify. Specifically, the tx_mutex_get is where the fault occures. What should I be looking for in this hardfauly to determine the root cause?
One item to note: If I download and run the workshop firmware, and then install my firmware, the new firmware runs. If the board is powered down and then powered back up, the firmware faults.
Hi @Sean Liming Greetings! Thank you for posting this question here. Our community SMEs will review this issue and share more insights as soon as possible. Please stay tuned to this thread for more updates.
@LeelaRajeshSayana-MSFT Thank you.
After some adjustments to interrupts and TIM base, the code gets to waiting for the DHCP semaphore and fails. I switched from DHCP to static IP, and I am not able to ping the board remotely.
I recreated the same project for the STM32H747I-DISCO board. Configured for the M7 processor, and I am getting the same issues.
Hi @Sean Liming Thanks for reaching out to us, the NetX Duo Webserver project was created by ST, you may ask for help from ST community
I did ask for help in the ST community. Per my original post, the issue is not with the NetX Duo Webserver project. That project works as expected.
The issue is creating a new project with the latest versions of NetX Duo and ThreadX. Trying to get the basic network connectivity up and running. The code gets lost in ThreadX kernel. If I attempt to use DHCP, the code crashes on DHCP semaphore. If I used static TCP/IP, the network stack doesn't work at all.
If I download the NetX Duo Webserver example and run, and the download my firmware, my firmware will run and I am able to ping the board. Once power has been cycled, my firmware will crash.
@LeelaRajeshSayana-MSFT and @bo chen
Removed Ethernet initialization, which got past the Hardfault. Now, the code fails on the DHCP semaphore. It appears the network stack never sends out the request for an address, and the call back on the semaphore is never made.
Still no resolution.
Hi @Sean Liming Looks the issue is for Ethernet initialization, ST may be able to help you troubleshoot it. One thing you can try is to increase the size of IP thread stack.