In my application the RISCV-ULP is responsible for blinking LEDs on behalf of the CPU. To indicate which LEDs have to blink we use a shared state variable that gets written by the CPU and read/reset by the RISCV-ULP.
Since the lock synchronization may introduce unwanted latencies, I wonder about the worst case if we don't do it. What can happen if read/write or two writes collide? Will either one win, will the resulting value be completely random or will the system crash?
RTC memory synchronization (RISCV-ULP vs. CPU)
-
- Posts: 168
- Joined: Sun May 22, 2022 2:42 pm
Re: RTC memory synchronization (RISCV-ULP vs. CPU)
I think you are experiencing race condition: viewtopic.php?t=6771
-
- Posts: 1708
- Joined: Mon Oct 17, 2022 7:38 pm
- Location: Europe, Germany
Re: RTC memory synchronization (RISCV-ULP vs. CPU)
I would be shocked if the hardware would fail to synchronize any memory accesses in this manner.DrMickeyLauer wrote: ↑Wed Jan 10, 2024 10:47 amwill the resulting value be completely random or will the system crash?
Who is online
Users browsing this forum: Bing [Bot] and 98 guests