I am a colleague of 5G-antry, and would like to follow up on this matter.
We have now, as indicated above, everything running with a network emulator, which also emulates a 1Gbit/s PHY.
We transitioned from this network emulator to a special wireless connection that has similar characteristics over-the-air as the network emulator. Yet, there is one noticeable difference: there is an additional microcontroller involved that transfers data from ETH to the wireless device. Unfortunately, this device only has a very limited number of ETH buffers - fewer than a 100MBit/s ETH would normally require.
When we boot the system, it starts to initialize itself and everything runs (almost) as expected up to a certain point (in the GUI it is indicated as the third boot phase with something like "fvs_spin"), where >20 packets are generated within a couple of microseconds. This unfortunately overwhelms the microcontroller, leading to packet loss, leading to an abort.
Is there a way to slow down this packet generation a bit to not cause a buffer depletion at this microcontroller?
We traced both scenarios. Find attached two wireshark packet dump screenshots one of the critical section: one for the smooth bootup when using only ETH, and one with the hickup when inserting the device with the slightly limited mikrocontroller.
