Arduino for STM32

mrburnette wrote: Wed Sep 22, 2021 11:03 pm As you did not specify the exact library source, I assume this Ethernet library: https://github.com/arduino-libraries/Ethernet

Actually I did:

> STM32duino_STM32Ethernet/src/EthernetUdp.h

In `EthernetUdp.h` I see the following `#define`:

#define UDP_TX_PACKET_MAX_SIZE 24

1. Doing a search inside the arduino directories I cannot find any use of it but in the examples (at application level):


step73@lap:~/Arduino/libraries$ grep -nrw . -e UDP_TX_PACKET_MAX_SIZE
./STM32duino ...

Nucleo-144 F429ZI.
Here my test setup:

PC ---> ethernet switch ---> one or more Nucleo-144 F429ZI boards

A software that runs on the PC (other details below) sends OSC bundles (UDP packets) to one or more devices.
The device does something and then answer with another OSC bundle after some time ...

Due to the limited "horse-power" of standard Arduino boards, I migrated to STM32-based (Nucleo 429ZI) with the hope I can use certificates to connect to AWS services. For example, I found this for a WiFi Arduino: https://github.com/Ameba8195/Arduino/blob/master/hardware_v2/libraries/MQTTClient ...

You can try inserting delay between each packet send.

Unfortunately I don't have control of the sender application.
Thanks anyway for pointing out another limitation. At least now I understand why it doesn't work.

well i'd guess you'd probably need to debug the codes if you want to find out why the udp packets are missing.
or possibly try to do some serial prints() to see what may be happening after all.



You're talking about my code?
Udp.parsePacket() returns only 3 times a value > 0 on 4 messages sent ...

On a Nucleo F429ZI I wrote this code:

#include <LwIP.h>
#include <STM32Ethernet.h>
#define UDP_TX_PACKET_MAX_SIZE 512
#include <EthernetUdp.h>

IPAddress remoteIP;
unsigned int remotePort;

EthernetUDP Udp;
uint8_t packetBuffer[UDP_TX_PACKET_MAX_SIZE];

void setup()
{
Serial.begin(115200 ...

Good catch! I'm going to patch the library manually to check if it fixes. Thanks.

No, this library was provided like that since a long time. For most of the use case it is enough. We can't answered to all the requests. :? And all requests does not satisfied all users. One wants it works like this, an other like that... It is hard to satisfied all people.
This is a community ...

The Servo library is provided for Arduino compatibility.
By extension the core is to provide as far as possible the same Arduino compatibility for all STM32 series.
You can have a look to the HardwareTimer library or implement your own Servo library.

That's not the point. I just wonder why limit ...