-
Syllabus
-
Terminology
- Introduction to mdb
-
Introduction to MDBCore Interface mdb 1 min
-
What is mdb? 2 min
- Using, Extending and Limits of mdb
-
Features of mdb 1 min
-
Using command files 4 min
-
Extending mdb functionality with Python 3 min
-
Limits of mdb 2 min
- mdb Demo
-
Test Structure 2 min
-
Prepare Lab 2 min
-
Firmware used in Lab 2 min
-
Lab mdb 4 min
- Summary
-
Summary 1 min
-
Please provide some feedback!
Automate FW testing with MDBCore scripting - MDBCore Interface mdb
In this module we cover the mdb, the simplest and first method to utilize MDBCore. (December 2023)
We are now prepared to explore the three distinct MDBCore usage models for automated firmware testing.
In this module we cover the mdb, the simplest and first method to utilize MDBCore, includes a script mdb.bat/.sh that manages instructions from an mdb-commands.txt file. However, it has certain limitations that are addressed with the next usage model, mdbcs.
The objective of this series of courses is to showcase the potential of MDBCore-scripting in automating firmware testing.
Target audience: FW-tester, Quality or Project-Leads
Knowledge: working experience of MPLAB®X & any OO-language knowledge helpful
1)Introduction Course: We commence by exploring the MPLABX ecosystem, the MDBCore, and the SDK, before delving into specific use-cases.
2)Compile without IDE: Prior to firmware testing, we examine the process of automatically compiling sources into *.elf files from a script.
We are now prepared to explore the three distinct MDBCore usage models for automated firmware testing.
3.a) MDBCore Interface mdb: The MDB, as the simplest and first method to utilize MDBCore, includes a script mdb.bat/.sh that manages instructions from an mdb-commands.txt file. However, it has certain limitations that are addressed with the next usage model, mdbcs.
3.b) MDBCore Interface mdbcs: mdbcs is designed to overcome the limitations of mdb. It is delivered as a Java module, mdbcs.jar, thus requiring a scripting language with a Java interface, such as Jython. This adds a bit more complexity but resolves the mdb limitations and provides access to a wide range of Java libraries, such as the Java Swing library for simplified user interfaces.
3.c)FW test automation with Java: The final and most complex usage model is pure Java, which offers full MDBCore functionality, albeit with the highest level of complexity.