Getting multiple outlier traces in Lab 2_1B with CW Husky

Embedded Security
7

It may be a compiler optimization issue, not an OS issue.
I think you’ve run into exactly this issue: SAM4S target weird behaviour with HUSKY

Sorry I didn’t think of it until now! If you switch to the CW develop branch, you’ll get the fix.