Lateralleap
Member

Hi Shawn. The test with the lpIP-master variant was workign fine until I stopped the test at 54 million packets received Is it right that the library manager should think that library variant is also called Version...

Hi Shawn. Increasing the timeout worked, thanks Have left a soaktest running with lwIP-master version, so far so good The previous 0.19.0-snapshot test got to 384 million packets, so I think we can call that...

Looking good at 4+ million packets

In the meantime I am leaving it on a soaktest with 0.19.0-snapshot but with the queue length back to 1 (previous few tests I still had it set to 64)

Hi Shawn Thanks for explaining the spelling :-) I tried the lwIP-master branch, however Ethernet.waitForLocalIP(kDHCPTimeout) was failing. I put back the 0.19.0-snapshot version and it worked immediately Let me...

Shawn. I will try the IWIp-master branch tomorrow and let you know

Many thanks for that by the way :-)

Thanks Shawn I installed the 0.19.0-snapshot (replacing the 0.18 version) So far it has not failed and I am up to 1 million packets Do you still want me to try the latest IwIP branch?

I tried with a queue length of 64 but it still crashes Once again I get a stream of complete 12345 sequences (obviously the first one is 345)

After a reset I get the null report and then: 11:11:34.540 -> Breadcrumb #1 was 3396345872 (0xCA702010) 11:11:34.540 -> Breadcrumb #6 was 2461095967 (0x92B1581F)

If that is what is happening, how can the main loop not be called again but no CrashReport

Here is the latest code #include <QNEthernet.h> using namespace qindesign::network; const uint32_t kDHCPTimeout = 10000; // 10 seconds const uint32_t PayloadLength = 6000;

I can certainly instrument the code more. The problem is the packet rate and the print statements will slow down the rate and may mask the problem. Hence why I am printing the keep alive every 10 seconds I will do...

Hi Shawn Another thought. Given that I am sending quite large packets (6008 bytes) much bigger than the MTU max packet size, might there be an issue with the splitting/ combining logic?

Here is CrashReport at startup: 09:20:01.779 -> Hopefully all is well, but certain types of crashes can't be reported: 09:20:01.779 -> stuck in an infinite loop (technically, hardware still running properly)...

I added some code to print the total packet count received and rate/s every 5 seconds that the end of the main loop It seems to die after about 40000 packets have been received It is no longer executing the main...

Hi Shawn I did try queue size in an earlier iteration but just of size 2. I will try 64 However the packet source is a C# application running in a tight loop so not sure why packets would be bunching up and why it...

What I think is happening when it seems to hang is that it is still receiving packets but at a much slower rate In other words, only 1 in every N packets gets through I will do some more tests to verify this

Thanks Sicco I have already confirmed the packets are still there Removing/ reinserting the ethernet cable does not restart it Resetting the Teensy does restart it Feels odd that it can typically do ~...

Does anyone have any insights into the original issue outlined in my first post? THanks

To put this discussion to bed, please see below:

Sorry but I think you have misunderstood the data declarations const uint32_t PayloadLength = 6000; struct __attribute__((packed)) T_MessageHeader { uint32_t messageId; uint32_t payloadLength; };

The buffer is 6008 bytes long not 6000

Sorry. I am struggling to understand what you mean. The size of the buffer I read into is the size of the structure that includes the payload and the header. The payload is immaterial in this test program. What matters...

I effectively do do that. I check if packetSize is greater that the size of the expected packet structure

Great news Shawn, thanks for doing that :-)

Many thanks Paul for the information Now that these ethernetless variants are out in the wild, it would be useful if the various ethernet libraries built in that PHY test code

I feel SO foolish... I looked at your photo to confirm the cable orientation was correct but did not spot the additional chip When the supplier specified "no ethernet", I assumed they meant "no ethernet adaptor"...

The benefit of sleeping on problems I woke this morning thinking, I wonder if there are multiple versions of the Teensy 4.1... I thought there was only one and that you just had to buy the ethernet adaptor. I...

Hi Paul, here you go: https://forum.arduino.cc/t/arduino-ide-2-03-hangs-on-startup/1095206/2 If you scroll up you will see the debug info from the Powershell capture

I have installed 1.58 beta 3 and no change I have plugged the enthernet cable (still plugged into the same switch port) into my laptop and it works fine I am not supplying separate power to the board, just the USB...

Thanks Defragster When I run it I get Link State: On but if I remove the ethernet cable, it still says the same!!! Just tried another board and ethernet adaptor. Same result I am using Teensydino 1.57.2 and IDE...

Thanks Paul. I can't resolve the Arduino IDE 2.03 issue on my desktop so posted a query on Arduino forum with debug output. Looks like it is crashing trying to load discovery related information related to Teensy ...

I decided to try a simple QNEthernet example #include <QNEthernet.h> using namespace qindesign::network; //=============================================================================== // Initialization...

Many thanks, much appreciated

Thanks. Yes, that was my next step. However having decided to update Arduino IDE to resolve another issue, that is not hanging on startup! Fun and games...

Thanks. I will those updates and revert

I have tried the UDP NTP client example below After the MAC address is printed, I get the error: "Failed to configure Ethernet using DHCP" So Ethernet.begin is failing #include <SPI.h> #include...

That made no difference in terms of green LED

Thanks I had already done that and tried two separate boards and adaptors I'm wondering if it's the type of switch it's plugged into so I will try a laptop

What seems to work sometimes is setting the sketch running with the 4.1 Teensy Port selected The select the COM8 port (ignoring Tensy 3.2 comment) and then open serial monitor

Hi, the COM8 port appears in device manager when I plug in the Teensy 4.1 so firstly I cannot delete it but also it's clearly being created by the Teensy 4.1 I have never had a Teensy 3.2 or Teensy 3.1 BTW The...

Next time it failed again: Error opening port 'COM8'

I have just selected COM8 (Teensy 3.2, 3.1), opened the serial monitor and then uploaded the sketch again and it has worked Is this what I should be doing despite the fact that I have Teensy 4.1?