No, rev 1 is 112017 or later

Right but these are not on the list either Ottawa/Boston/Washington/Philadelphia/Atlanta/Miami

To make it as compact as possible, it should be only one listing per time zone per country/region and use the largest city.

The openssl compatibility layer is just a shim/wrapper for mbedtls so you're going to have to look deeper

Thanks, so bits that are not set to 0 should be set to 1? All 3 nybbles should be either 0 or F?

How do you output I2S0 clock on CLK_OUT1 and I2S1 clock on CLK_OUT2? Or you can only route one clock to gpio matrix?

Yes! Seriously, though, it would be great to be able to have the ability to deploy an interpreted main program, interpreted wake stub, and interpreted ULP program (what kind of interpreter could run there?).

ESP_igrr wrote:Well, technically you can use the interpreter from wake stub: copy it into RAM, un-memfrob it, jump to the entry point.

Ah OK, not ideal, but could you then point it to a basic program to execute in rtc fast memory?

What about from a wake stub?

ESP_Sprite wrote:what, specifically, you would want to use this for

802.15.4, backscatter, TMD, ...

...definitely nothing rhyming with hammer.

martinayotte wrote:The DB is missing "America/Montreal" ...

Same TZ as Toronto, right? To have the most compact db you only want to list the largest city per time zone. Although there are 8 cities listed in Indiana for some reason.

Section has not been updated.