Is it possible to get an exception out of the bus monitor on the MCF54454?
I'm trying to track down what I believe is a bad Flex Bus access, one that causes the bus to hang. Presumably it's to an address that's not mapped to a CS.
If the bus monitor is disabled, but the core watchdog is set to interrupt-then-reset mode, I don't get the interrupt (because the bus cycle never completes; if I got the interrupt, it would give me a stack dump which would help).
If I turn on the bus monitor, it seems that the bus monitor terminates the bus transaction, doesn't throw a fault, and lets the CPU go on it's merry way. Which isn't particularly helpful.
Is there a way to get the bus monitor to throw an exception? Failing that, is there a way to configure the flex bus to throw an exception when you access FB space that isn't mapped to a CS? Anyone else find the documentaton of the bus monitor a little lacking?