You could remove your sdkconfig and drop this file in your project directory, then run menuconfig again. (Note you may need to select one of the default partition schemes there as that file uses a custom one.)

Have you enabled PSRAM in menuconfig? If not, you can only use the internal RAM, and that's probably too little.

We're not talking about flash here, we're talking about RAM. And I'm sorry, but I can't tell you exactly what is going wrong - 300K seems enough RAM to me, but perhaps your RAM is fragmented and miniz tries to allocate a large contiguous buffer.

fawazapp wrote: ↑

Thu Sep 12, 2024 7:26 am

However, the device is still not working, and I’m unable to pinpoint the problem.

That is about the most useless diagnostics you can post here. In what way specifically is it not working? What did you already measure / try?

USB-C needs two 5.1 resistors on the CC pins for it to supply power. It's likely your USB-C adapter thingy does not have those. That means an USB-C to USB-A cable will work (as USB-A does not require those resistors) but USB-C to USB-C will not.

Its possible in theory: you'd have to make a composite device with a MSC plus a CDC-ACM serial port, then hook up the DTR/RTS signals of the serial port to call something that resets the chip into bootloader mode. Not sure if anyone implemented that already, though.

Trivial alternative solution: can you allocate more RMT blocks to your Tx channel?

How's about you post a (clear, in focus) picture of the devboard with the broken component clearly marked? That probably makes it a lot easier to tell you what broke than going by 'SL' as the only hint.

miniz needs a bunch of space to allocate data structures that are needed for compression, e.g. for the dictionary. Could be that you don't have enough (contiguous) memory for that, making the call fail.