On 19 September 2017 at 05:43, Edgar E. Iglesias <edgar.igles...@xilinx.com> wrote: > On Mon, Sep 18, 2017 at 04:50:23PM +0100, Peter Maydell wrote: >> I'm currently running into a similar issue with M profile, >> where at the moment we stuff the information about what >> kind of fault the MPU generates into a v7PMSA format >> FSR value and reinterpret it into M profile exception >> types and fault status register bits later. This works >> OK, but for v8M we want to start reporting kinds of fault >> (like SecureFault) that don't have equivalents in v7PMSA >> at all, and maybe it would be better to clean this up rather >> than assigning arbitrary bogus fsr values for internal use... > > I see, yes that sounds like a similar issue. > If you'd like to take over this, that'd be great :-)
For the moment I've taken the easy approach of using dummy FSR values. We'll see if that gets through code review :-) thanks -- PMM
