Presentation
Automation of Shmoo Engine based Pre-Si BDI Testing
DescriptionLow power microcontrollers are becoming increasingly complex, making it crucial to test corner cases to avoid unexpected issues in the field. Testing low power and security scenarios can be high-risk, as failures can lead to device power up issues and security vulnerabilities. To mitigate this, emulation platforms like Cadence's Palladium can be used to analyze waveforms and ensure comprehensive coverage of all possible time windows. However, manual testing and analysis can be time-consuming and prone to errors. The BDI (Break the Device Intent) methodology involves identifying a scenario of interest, sweeping events to cover a specific time window, and using a shmoo engine to generate events at desired delays. To perform BDI testing on the Palladium emulator, a shmoo engine needs to be hooked to the DUT (Device Under Test) via a testbench, and a test code needs to be loaded on the DUT. The shmoo engine must be configured to generate events at desired times, and this information is communicated to the Palladium via qel files. The manual creation of qel files and the process of capturing and saving waveforms can be time-consuming and repetitive, requiring significant effort. Additionally, failed scenarios can cause the DUT to get stuck, making it necessary for the tester to actively monitor the process.
Event Type
Engineering Poster
Networking
TimeWednesday, June 2512:15pm - 1:15pm PDT
LocationEngineering Posters, Level 2 Exhibit Hall