Franck Freiburger
Franck Freiburger
> The partition table looks not common. https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/partition-tables.html I rely on automatic offset determination (I hope I've understood correctly how it works.)
same issue, in "debug" mode with the following partition: ``` nvs , data , nvs , 0x9000 , 0x4000 otadata , data , ota , 0xd000 , 0x2000 phy_init ,...
ok, in "release" mode bootloader is 25 152 bytes. I wondering if it is possible to build bootloader in "release" and firmware in "debug" ? (this already seems to be...
in my platformio.ini: `;build_flags = -D DEBUG` bootloader: 26 992 bytes `build_flags = -D DEBUG` bootloader: 28 704 octets
Thanks to the advice ! I still don't understand why bootloader is bigger in `build_type` debug than release (despite the use of `build_src_flags` instead of `build_flags`) I then changed CONFIG_PARTITION_TABLE_OFFSET...
Is `jerry_source_name()` suitable for this purpose, (even if it depends on `JERRY_SOURCE_NAME`) ?
i have this problem in Node 20 as well
hello SMen1, yes, the solution you are talking about is quite old ` { content: content, type: ".mjs" }` is not valid any more. In order to handle binary files...
see PDFJS issue https://github.com/mozilla/pdf.js/issues/9103
As far as I can understand, weak map container buffer always grow (ecma_collection_append), but never shrinks (GCed items are replaced by ECMA_VALUE_EMPTY) note that all containers are affected (Map, Set,...