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
In sblib 2.10, we implemented cooperative pause+resume, focused on the bootloader usage scenario as our BL does the most IAP, by far. Now that both pause and resume are reliable, we can and should roll this feature out to all applications and all IAP operations.
Today, there are a bunch of code paths that end up in IAP, and it's not clear whether it's sufficient to have IAP call into Bus to pause bus access as that might (!) cause deadlocks or timeouts. We need to analyze the call patterns and see, what the best approach to this is.
The text was updated successfully, but these errors were encountered:
In sblib 2.10, we implemented cooperative pause+resume, focused on the bootloader usage scenario as our BL does the most IAP, by far. Now that both pause and resume are reliable, we can and should roll this feature out to all applications and all IAP operations.
Today, there are a bunch of code paths that end up in IAP, and it's not clear whether it's sufficient to have IAP call into
Bus
to pause bus access as that might (!) cause deadlocks or timeouts. We need to analyze the call patterns and see, what the best approach to this is.The text was updated successfully, but these errors were encountered: