@dpgeorge - Thanks, should be fine without a test.

Also, it might be good to search the code base for tight loops like that which don't wait.

Code size report:

Reference:  rp2: Run vm/gc/parse from SRAM by fixing linker object suffix. [f452dab]
Comparison: mimxrt/eth: Sleep while waiting for ETH link to come up. [merge of 54157b7]
  mpy-cross:    +0 +0.000% 
   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
      esp32:    +0 +0.000% ESP32_GENERIC
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

I compiled it for a Seeed Arch Mix, and ETH both times out if not connected and gets a connection if yes. Any suggestion what to test for polling being active? The wait period can be interrupted with Ctrl-C.

P.S.: For Teensy 4.1 you just need the RJ45 plug: https://www.pjrc.com/store/ethernet_kit.html for ETH.

I compiled it for a Seeed Arch Mix, and ETH both times out if not connected and gets a connection if yes.

Thanks for testing! That sound good, that both those cases work.

Any suggestion what to test for polling being active? The wait period can be interrupted with Ctrl-C.

If the wait can be interrupted, then the polling is working. To double check that, you can try interrupting the wait with ctrl-C prior to this patch.

For Teensy 4.1 you just need the RJ45 plug

I have a lot of boards (as you can imagine), but I don't actually have a Teensy 4.1...!

To double check that, you can try interrupting the wait with ctrl-C prior to this patch.

Check! Without this path the wait cannot be interrupted.

Check! Without this path the wait cannot be interrupted.

Excellent! Thanks for that, now I don't need to find the right hardware :)

I guess this is OK to merge now. At least it fixes this case.

Octoprobe PR report

• Duration: 8min, 3171 tests run, 170ms/test
• Tested ports: mimxrt
• Summary Report , Logdirectory