You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Hardware Loop feature is automatically generated and used in exception handlers, HWloop CSRs are not saved/restored.
So when returning to main program from exception handler using HWloop, it is corrupted if exception happened during main program HWloop execution.
This could happen with illegal exception, interrupt, debug code and maybe other situations.
The text was updated successfully, but these errors were encountered:
Technically not a bug, but a design decision. There are a number of options, which trade performance against flexibility when using hardware loops within interrupt handlers. For now we shall just document the issue in the GCC user manual.
When Hardware Loop feature is automatically generated and used in exception handlers, HWloop CSRs are not saved/restored.
So when returning to main program from exception handler using HWloop, it is corrupted if exception happened during main program HWloop execution.
This could happen with illegal exception, interrupt, debug code and maybe other situations.
The text was updated successfully, but these errors were encountered: