Andrew Leech

> Leave the resume command in place, as then just a no-op with the new default. While I don't love leaving no-op functionality around, perhaps it's worthwhile until V2.0 or...

> It's a lot easier to just set environment variable overrides directly at the point of use:`\n\nMPREMOTE_AUTO_SOFT_RESET=0 mpremote connect ${device} exec \"a = 1\" eval \"a\` Well for this example...

> I believe this also fixes #16697 Ah I missed that one, yes I do believe it should be essentially the same bug. The uninitialised pbuf was the same problem...

> I've run this updated test on a PYBD_SF6 and RPI_PICO2_W, and it passes without the fix from this PR. That's a bit strange, I'll try to test again to...

> `./run-multitests.py -i pyb:/dev/ttyACM0 -i cpython multi_net/tcp_accept_recv_listen.py` `-t` was needed for me to figure out what was going one; yes it was "passing" in that it's not really running: ```...

Great catch @dpgeorge I've updated as suggested and re-tested: ``` corona@NUG:~/mpy/socket_listed_recv/tests$ ./run-multitests.py -t -i pyb:/dev/usb/tty-Pyboard_Virtual_Comm_Port_in_FS_Mode-3254335D3037 -i cpython multi_net/tcp_accept_recv.py TRACE tty-Pyboard_Virtual_Comm_Port_in_FS_Mode-3254335D3037|python3: 181 i0 : SET IP = '192.168.0.65' 181 i0 :...

Nice one @sanderjo there's a bunch of new chips getting added to IDF these days! It still needs testing but this commit on the top of my C6 branch is...

@agatti the latest changes on C6 (about to push) should enable the emitter on all risk chips based on the soc defines, rather than listing individual chips. I suggest this...

Hi @TrekMax could you also take a look at this which is intended to make it much easier to bring in new chips: https://github.com/micropython/micropython/pull/15862

Hi, your first few commits looked like good cleanups of compiler warnings thanks! The latest couple however look like they belong on a personal project / personal branch instead perhaps?