Posted on January 18, 2018 at 22:46Hi,
Keil's Logic Analyzer is not a 'hardware' logic analyzer, and do not monitor I/O pins. It is also limited by the debugger and the MCU core you are using.
See below.
Cheers,
Alex.
_____________________________________________
From Keil uVision User's Guide: Logic Analyzer
µVision User's Guide: Restrictions
RestrictionsWhen debugging on hardware, the number of items that can be defined in the
is restricted by the microcontroller core (refer to
Access Breakpoints in
http://www.keil.com/ulink/cmp.asp
). Many more different items can be defined in simulation mode.
The Logic Analyzer can record changes of:
- Global program variables, including
struct
members. - that represent I/O pins of the microcontroller.
- Peripheral registers that are triggered by external or internal events, but with the restrictions outlined below.
The Logic Analyzer
cannot
record changes of: - Automatic variables defined inside a functionAutomatic variables are located on the stack or in overlayable memory regions. It is not possible to record changes of dynamic memory locations.
- CPU registersCPU registers cannot be triggered with read or write breakpoints. Therefore, such changes cannot be recorded.
- Peripheral registers that represent timer registersIncrements of timers (or similar peripherals) are not simulated. Instead, the timing of events that are triggered by a timer, is calculated. Therefore, it is not possible to view timer increments.
- I/O pins of communication peripheralsI/O pin toggling of UART, CAN, SPI, or I²C communication peripherals is not simulated. It is assumed that the timing of communication streams behaves according to the specifications. Instead, the I/O stream is represented by VTREGs.
- Memory BUS signalsµVision simulates a CPU including memory areas, but it does not simulate the Memory BUS signals (data BUS, address BUS, and control lines like RD, WR, ALE). Therefore, it is not possible to view memory BUS signals with the Logic Analyzer
