On-Demand Webinar
Often, hardware-only debuggers are sufficient for checking timing and ensuring proper behavior for peripherals. Simulation, such as bus-functional modeling or its equivalent, may also be used to verify that the peripheral is reacting properly to “bus” stimulus.
Software-only debuggers enable users to single-step or run to (conditional) breakpoints and check values of variables and regions in memory.
But what happens when hardware and software are connected? Custom peripherals may not always integrate seamlessly. Are the device drivers for the peripheral working properly? Are the user’s APIs? Is the hardware behaving the way the driver writer thought it should?
Cross-triggering or hardware-software debugging brings a new capability to the developer to quickly narrow down where the issues are and get them resolved.
This live demo will demonstrate cross-triggering debugging.