Is there an existing issue for this?
Current Behavior
I have a few test programs for basic network functions on STM32 controllers. I started by updating a Nucleo-STMf756 to the new driver. In doing so, I noticed that a larger memory area needs to be defined for the RX buffer (ARM-software/MDK-Middleware#150 (comment)).
After the adjustment, the programs ran without requiring any further adjustments.
Next, I was supposed to make the same change for the STM32H753. Even after adjusting the RX memory area, the programs still won't run. The board doesn't respond to a ping either. If you use driver version 1.3.0, everything works as expected.
During my tests, I also noticed that after upgrading to Middleware 8.3.0, the Component Viewer shows "-1" under Interfaces. This occurs regardless of whether the program is working (Driver 1.3.0) or not working (Driver 1.4.0).
With Driver version 1.4.0 STM32H753-HAL_ETH_TxCpltCallback(() is never called.
Expected Behavior
The H753 test program performs the following task. I launch a TCP echo program on the PC. This program receives a message from the controller and sends it back to the controller. The data received by the controller is displayed on a serial terminal (115200, 8,n,1). The command to run the PC program is:
.\echotool.exe /p tcp /s 2000
PC 192.168.7.254
Controller 192.168.7.1
Steps To Reproduce
- Win 11
- VSC 1.121.0
- Csolution 2.14.0
- CMSIS Soluition 1.67.2
Use attached program
- Compile and Test program (Driver 1.3.0)
- Start debugger
- start echotool
- See serial Terminal output
- Modify CubeMX.cbuild-pack.yml change entry to ARM::CMSIS-Driver_STM32@1.4.0
- Use Rebuild Solution to use new pack setting
- debug again - program fails
You can also try ping
101-STM32H753-Network-TCP.zip
Version
Keil::MDK-Middleware@8.3.0
ARM::CMSIS-Driver_STM32@1.3.0 (ok)
ARM::CMSIS-Driver_STM32@1.4.0 (fails)
Blocker
Is there an existing issue for this?
Current Behavior
I have a few test programs for basic network functions on STM32 controllers. I started by updating a Nucleo-STMf756 to the new driver. In doing so, I noticed that a larger memory area needs to be defined for the RX buffer (ARM-software/MDK-Middleware#150 (comment)).
After the adjustment, the programs ran without requiring any further adjustments.
Next, I was supposed to make the same change for the STM32H753. Even after adjusting the RX memory area, the programs still won't run. The board doesn't respond to a ping either. If you use driver version 1.3.0, everything works as expected.
During my tests, I also noticed that after upgrading to Middleware 8.3.0, the Component Viewer shows "-1" under Interfaces. This occurs regardless of whether the program is working (Driver 1.3.0) or not working (Driver 1.4.0).
With Driver version 1.4.0 STM32H753-HAL_ETH_TxCpltCallback(() is never called.
Expected Behavior
The H753 test program performs the following task. I launch a TCP echo program on the PC. This program receives a message from the controller and sends it back to the controller. The data received by the controller is displayed on a serial terminal (115200, 8,n,1). The command to run the PC program is:
.\echotool.exe /p tcp /s 2000
PC 192.168.7.254
Controller 192.168.7.1
Steps To Reproduce
Use attached program
You can also try ping
101-STM32H753-Network-TCP.zip
Version
Keil::MDK-Middleware@8.3.0
ARM::CMSIS-Driver_STM32@1.3.0 (ok)
ARM::CMSIS-Driver_STM32@1.4.0 (fails)
Blocker