Florian Loitsch
Florian Loitsch
Apparently this is in the `i2c_ll_read_rxfifo`: (Note: I copied over the original toit.elf from the envelope repository, to make sure the offsets are correct). ``` ᐅ riscv32-esp-elf-addr2line -pfiaC -e build/esp32c6/toit.elf...
Normally, primitive operations are not allowed to block for longer periods of time. The i2c operation is currently blocking, which usually isn't a problem, since the operation shouldn't take long....
6:5 is I2C-read. Almost certainly the same reason: the device pulls the clock low and delays the I2C transaction. -> we run into a timeout.
6:7, 6:8 and 6:9 are now "write", "read" and "write_read". I haven't been able to convert the I2C to asynchronous operation yet, so this is probably still related to the...
It comes with an esp-idf update, but not yet to the latest esp-idf.
The cross-compilation isn't working anymore. Also, there might be issues with the DROM sections.
With the default configuration the esp32-p4 crashes *immediately*. If I disable cmpct-malloc, it manages to run a bit. However, It has a tendency to run out of memory: ``` Heap...
Agreed. For field-initialization that's fortunately not a problem. If we exit the constructor without an exception, then we must have gone through all statements in the try-block. And the finally...
> Have you tried to run my example? Not correctly :)