I'm trying to create a simple "hello world" usb device, that doesn't follow any prespecified class type (not HID/MSC/etc), because I don't want any preexisting generic driver from my PC to pick it up. I'm trying to code a custom driver that kicks in based solely on VID:PID, which I have chosen arbit...

Recently, compilation speed is not rising above 22% except for sporadic spikes to 50%. Does anyone have an idea what is causing this? This is the case irrespective if I compile in CLI or VSCode. Is anyone else experiencing this? I'm on Ubuntu 24.10 x64, Ryzen 5500U, 8GB RAM, Samsung Evo 970 Plus NVM...

Why not just open it up as beta and let anyone/everyone test at their leisure? That's effectively how things are anyways with the rest of esp-idf, everybody heads to the issues section to report problems. I don't think it makes sense to require anyone/someone to proclaim themselves as official teste...

Hi,

I've recently begun debugging esp32 through openocd/jtag. However, serial output is sent to UART0. Is it possible to send this data in-band over JTAG?

I don't have experience with AWS IOT. But more importantly, MDF hasn't been updated in years, it is presumed defunct. I would advise trying BLE-Mesh instead or 3rd party libraries, such as ESP-Now BATMAN, or https://github.com/aZholtikov/ZHNetwork . PainlessMesh is another alternative, but was a pai...

I'm aware of remapping... but I couldn't find anything in the TRM that mentions that ROM0 specifically is mappable to a reserved region in I-space. Could you please point me to the specific page/section? Perhaps this is mentioned in some source file instead?

Hi, The linker script "...../esp_rom/esp32/ld/esp32.rom.libgcc.ld" starts as follows: [Codebox] /* Unlike other ROM functions which are exported using PROVIDE, which declares weak symbols, these libgcc functions are exported using assignment, which declares strong symbols. This is done so that ROM f...

Hugo_Weijers wrote: ↑

Mon Nov 27, 2023 8:41 am

However my disp value is always 0

That means your display was never working. You should ask in the LVGL forums why this is so, and mention what controller it is and show how it is being created (in software) and how it is wired to mcu.

it means your display isn't setup correctly. The object must exist and you must pass its handle to lvgl. lvgl unfortunately doesn't check & gracefully handle the case where the display is not set up hence its address is NULL. lvgl doesn't automatically setup the display.

I was so curious about this for a long time, thx.