Wilko Nienhaus

I have found that the documentation and code (ESP-IDF) don't always match 100%. In such cases, I tend to trust the code in the ESP-IDF, as that is what's actually...

Interesting case :) The ULP code looks correct. (Except if you also want to stop the ULP timer from starting the ULP program again: [as per here](https://github.com/espressif/esp-idf/blob/v4.4.1/examples/system/ulp_fsm/ulp_adc/main/ulp/adc.S#L114) - but anyway,...

About the age of the chip - I am not sure it matters that much. Our assembler only supports the original ESP32 anyway (not the newer S2, C3, etc models),...

Ok. Good to know the latest nightly build works. I am still curious however, if we could solve it another way. One thing I noticed is you were pointing to...

I have not tried I2C from the ULP yet, so I can perhaps try to give some pointers, rather than a concrete answer. Your code snippet looks like it might...

I had a quick look and I have the feeling the PIN might not be in output mode. This line sets the output mode: https://github.com/micropython/micropython-esp32-ulp/blob/master/examples/blink.py#L63 Did you change the `RTC_IO_TOUCH_PAD2_REG`...

Thanks for letting me know. I will try update the example file to better explain this for future users.

(to keep all the discussion together here) In #82, @mattytrentini suggested: > How about tagging releases in lock-step with MicroPython releases? And follow MicroPython master on this master?

Found [this approach](https://github.com/espressif/binutils-esp32ulp/issues/19#issuecomment-945091131) (i.e. using gcc 7) to building on `ubuntu-20.04` and it works. It does not work on `ubuntu-22.04` because it doesn't have gcc-7 anymore, but building on 20.04...

The assembler does use quite a bit of memory (it's actually mostly about memory fragmentation, rather than purely allocating it all). But: the ULP requires "no memory" - at least...