Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use none-blocking call and callback for R_FLASH_* #2

Open
HirokiIshiguro opened this issue Dec 22, 2018 · 0 comments
Open

use none-blocking call and callback for R_FLASH_* #2

HirokiIshiguro opened this issue Dec 22, 2018 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@HirokiIshiguro
Copy link
Member

Is your feature request related to a problem? Please describe.
related commit: da8be8c

I would like to improve FLASH erase/write from blocking with disable interrupt to none-blocking without disable interrupt with serializing the process.

R_FLASH_* functions are not thread safe. I added disable interrupt code before R_FLASH_* and added enable interrupt code after R_FLASH_*. But this is not good implementation because user cannot execute other code during erase/write FLASH. This might have take a time as ms order. I will consider serializing the calls in next.

Describe the solution you'd like
To use none-blocking without disable interrupt with serializing the process.

Describe alternatives you've considered
No.

Additional context
No.

@HirokiIshiguro HirokiIshiguro added the enhancement New feature or request label Dec 22, 2018
@HirokiIshiguro HirokiIshiguro self-assigned this Dec 22, 2018
HirokiIshiguro referenced this issue Dec 22, 2018
[UPDATED] RX65N RSK (Ether) aws_pkcs11_pal.c data storing to FLASH ROM.

Signed-off-by: SheltyDog <hiroki.ishiguro.fv@renesas.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant