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

on riscv32, Does flow situation use right? #368

Open
jmx-wqz opened this issue Feb 29, 2024 · 0 comments
Open

on riscv32, Does flow situation use right? #368

jmx-wqz opened this issue Feb 29, 2024 · 0 comments
Labels
bug Something isn't working hardware New hardware or architecture support request

Comments

@jmx-wqz
Copy link

jmx-wqz commented Feb 29, 2024

Describe the bug
A clear and concise description of what the bug is.
i creast 2 thread, thread1's priority is 2 and thread2's priority is 4, thread1 call tx_thread_queue_receive() and thread2 write swint reg,and handler of swint will call context_store and interrupt process which is call tx_thread_send_message() which will resume thread1 but thread1 will not resume because tx_thread_system_state is not zero, and context_restore, in context_restore will identify there is preempt (thread1 is ready and execute_thread_ptr is thread1, current_thread_ptr is thread2) and will call thread_schedule which will switch thread to thead1,thread1's stack_type is 0(task type) and will sync_return but interrupt not return ,in this situation can't exit from interrupt is error

Please also mention any information which could help others to understand
the problem you're facing:

  • What target device are you using? riscv
  • Which version of Azure RTOS? newest
  • What toolchain and environment? riscv
  • What have you tried to diagnose or workaround this issue?

To Reproduce
Steps to reproduce the behavior:

  1. Build my project in IAR Workbench.
  2. See error

Expected behavior
A clear and concise description of what you expected to happen.

Impact
What impact does this issue have on your progress (e.g., annoyance, showstopper)

Logs and console output
If applicable, add console logs or other types of debug information like Wireshark capture as .zip file.

Additional context
Add any other context about the problem here.

@jmx-wqz jmx-wqz added bug Something isn't working hardware New hardware or architecture support request labels Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working hardware New hardware or architecture support request
Projects
None yet
Development

No branches or pull requests

1 participant