By setting LDFLAGS, you overrule the esp-idf defaults. Can you try setting EXTRA_LDFLAGS instead, see if that gives the result you need?

Where do you see this? The TRM makes no such reference, at least not to what I recall.

SPI1 at the moment in esp-idf can indeed only be used for writing to flash. We want to update the SPI driver to also allow access to other devices connected via a different CS pin, but that's not in the driver yet.

Oops, I see I accidentally allowed this topic twice. Closing this one, please proceed in the other topic.

Can you try to connect it and post the last lines of output of the dmesg command? Also, have you tried with a different cable?

I see a lot of issues you have with the ESP8266 SDK that you think you will also have with the ESP32. While I do acknowledge the fact that you have these issues with the ESP8266, I'd like you to know that we weren't entirely happy with the way that ended up either. That is why we decided to go a dif...

Nothing yet, sorry, haven't been able to come around to looking into this.

I'm gonna respond in English; if you cannot understand the explanation because of that please tell me and I will have someone translate it into Chinese. Just to check if I understand it correctly: You have an external 50MHz clock source and want to feed that signal into GPIO0 to feed the Ethernet MA...

It looks like for some reason, dumping the core took long enough for a watchdog to trigger. We merged a fix for that bug three days ago; can you try pulling esp-idf and then see if the problem is still there?

Not entirely sure if that wasn't the case earlier on, but we keep the fast RTC ram powered now, in order to quickly resume after a wakeup event (to work around a bug in the current silicon). You can disable that by adding esp_deep_sleep_pd_config(ESP_PD_DOMAIN_RTC_FAST_MEM, ESP_PD_OPTION_OFF); in yo...

Could be, yes. We should get the new silicon this week, I guess general availability won't be too far off from there.