ESP_Sprite wrote: ↑

Tue May 21, 2019 1:33 am

less derpy ULP

Excited to see the ULP got some love! Can you give us any more details than "less derpy"? What kind of general improvements can we expect?

I understand that yield() should do the job. I suspect it's actually the loopTask causing your issues.

It's unclear if that's actually your loop() function or if you've cut it down to that for the sake of brevity. If that's actually it, could you try adding vTaskDelay(portMAXDELAY) to it?

NVS is not typically erased during a firmware flash, so this pseudo partition type of "EEPROM" must act a little differently, and that's definitely specific to Arduino. Interestingly, EEPROM implementation has just been overhauled for the next release to use a normal NVS partition. See https://githu...

Thanks, Sprite, that makes sense. It seems to have worked for a while... Then I returned later to find the board non-functional as a MOSFET had died, so not a good idea to play with those registers :lol: I think the macros aren't really supported but I'll add here that it would be great to have the ...

Reorder the parameters in config:

The ULP CP instruction set says "ULP coprocessor has 4 16-bit general purpose registers, labeled R0, R1, R2, R3". I'm currently using the macros to program it, and only R0-R3 are defined here: https://github.com/espressif/esp-idf/blob/master/components/ulp/include/esp32/ulp.h#L35 Yet, looking throug...

I know they seem to have a lot of overlap but a server and WiFi are completely different things. It doesn't look like that library has an easy method like that, but do you really need it? There's no Keep-Alive wizardry going on or anything, you can safely assume the connection will be closed after e...

Your question doesn't make sense. When in station mode, your ESP32 *is* the client.

void loop() { } The loopTask is pinned to CPU1. This means that CPU1 is very busy doing your empty loop() over and over and over again, so Task2 (which is also pinned to CPU1) is starved of CPU time. There are two easy solutions. Tell the scheduler to make it idle, or just delete the task: void loo...

It does seem to be possible. Try this: (it's also used in there to calculate hashes of the current program, which is a good example usage) https://github.com/espressif/arduino-esp32/blob/e602145c2b822a6d9288ae31c0d9ca8a7ee097d1/cores/esp32/Esp.cpp#L151 Looks like the real magic happens here, for int...