I am having some problem making the ulp riscv to wake up the main cores, the first time it wakes them up without a problem, the second time it doesn't seem to work
In the main code i have:
ulp_riscv_reset();
LoadRiscvProg();
ulp_riscv_run();
esp_deep_sleep_start();

on the ulp code I simply use ...

Ok, thank you very much for the clarification

I am assuming that I don't have a way to specify which pin woke up the ulp, unless I make some type of logic to be run and check the source of the signal after waking up, correct?

The title says it all, can the ulp be woken up from "sleep" (halt) by using a gpio interrupt that was implemented in the ulp code?
I know it can be triggered by the timer if we don't specify timer_stop, but I want it to be woken up by the gpio interrupts previously implemented.

I noticed that when I try to open the library, the IDE has a preference to open the files from version 5.3.1, is it a problem if I have both versions on the computer? I already changed the environment variable path, yet it still opens the files from the old version.

Hi

I am getting conflicting definitions of GPIO enumerations and types (gpio_num_t and GPIO_NUM_*) when using "ulp_riscv_gpio.h" and "ulp_riscv_i2c.h" at the same time in the Risc-V coprocessor, I can´t find a workaround and I can´t not include them because I need to use more than just the GPIO_NUM ...

Hi all,

I can´t find anything else about this, so I am not sure if it has already been talked about.
I can't use the i2c_master library to write and read from specific registers from slave devices, there is no field to write the register address on the i2c_master's API's. On the other hand, I2C ...

One more question, if i have a struct in my main.c, can i make a struct of pointers in the risc-v program to access the original struct variables with the same logic? Or do i need to make use of simple pointers to access the variables in the struct placed in the rtc memory?
If can make a struct of ...

Thank you!! It worked.

Even after doing what you were telling me, I couldn't make it work, was already giving up on it, but then i tried passing the offset variable to the pointer AFTER loading and starting the risc-v program, which I wasn't doing before, and it worked. The variable is being ...

Hi, thanks for answering.
Could you elaborate more please on the b) option, I'm more interested in that one?

Are you saying that i can create a pointer in the risc-v program, and the main program passes the offseted address to the pointer in the risc-v? If so, do i need to make anything else on the ...