-
Syllabus
-
Terminology
- Preparation
-
Introduction to compile without IDE 1 min
-
Revision Control 3 min
-
Parts of a MPLABX project 1 min
- Compile Steps
-
Creating Makefiles 2 min
-
Compile with make 1 min
- Summary
-
Summary 1 min
-
Please provide some feedback!
Automate FW testing with MDBCore scripting - Compile without IDE
In this course you will learn how to manually extract firmware revisions and how to compile code without an Integrated Development Environment (IDE) (December 2023)
In this course you will learn how to manually extract firmware revisions and understand their components. You'll also learn to create make files, which are essential for organizing code compilation. This will lead you to understand how to compile code without an Integrated Development Environment (IDE). Additionally, you'll gain knowledge about version control systems and effective file and data management.
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.