ESP32 Forum

This is just a query. I am looking for following details.

Where to find source code
license of libat_core.a

I'll ask the team to specify it a bit better, but I think it's safe to assume that libat_core.a is licensed under the same license as its include file (essentially MIT but only when used on ESP32 hardware). The sources for this library are not publicly available, sorry.

uart interrupt subroutine create following error.
could you please tell what goes wrong here.

abort() was called at PC 0x40082b05 on core 0
0x40082b05: lock_acquire_generic at /home/zlt-b39/esp/esp-idf/components/newlib/./locks.c:141


Backtrace: 0x40087310:0x3ffb01c0 0x400874e7:0x3ffb01e0 0x40082b05:0x3ffb0200 0x40082c25:0x3ffb0230 0x400d8baa:0x3ffb0250 0x400dbde5:0x3ffb0560 0x40082941:0x3ffb0590 0x400d229d:0x3ffb05e0 0x400822ed:0x3ffb0610 0x400d153b:0x00000000
0x40087310: invoke_abort at /home/zlt-b39/esp/esp-idf/components/esp32/./panic.c:648

0x400874e7: abort at /home/zlt-b39/esp/esp-idf/components/esp32/./panic.c:648

0x40082b05: lock_acquire_generic at /home/zlt-b39/esp/esp-idf/components/newlib/./locks.c:141

0x40082c25: _lock_acquire_recursive at /home/zlt-b39/esp/esp-idf/components/newlib/./locks.c:169

0x400d8baa: _vfprintf_r at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdio/../../../.././newlib/libc/stdio/vfprintf.c:860 (discriminator 2)

0x400dbde5: vprintf at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdio/../../../.././newlib/libc/stdio/vprintf.c:39

0x40082941: esp_log_write at /home/zlt-b39/esp/esp-idf/components/log/./log.c:121

0x400d229d: uart_rx_intr_handler at /home/zlt-b39/Documents/indoor/work/uart_events/main/./uart_events_example_main.c:157 (discriminator 1)

0x400822ed: _xt_lowint1 at /home/zlt-b39/esp/esp-idf/components/freertos/./xtensa_vectors.S:1105

0x400d153b: esp_vApplicationIdleHook at /home/zlt-b39/esp/esp-idf/components/esp32/./freertos_hooks.c:85

You're trying to call printf from the interrupt handler. Very few functions can be successfully invoked from an interrupt handler and these in general have something like 'fromISR' in their name; printf is not one of them. For debugging, you can try ets_printf instead.