Clever Geek Handbook

Bullseye for EDK based applications

Is there a way to integrate EDK2 based app to get into Cover Eye Eye tool for Bulls? The executable file will have a .efi extension and only open in an EFI shell. I believe I also need to develop a driver to capture coverage data to an external drive for analysis, since the application will only operate in the EFI shell (BIOS).

So, does anyone have any ideas how this can be done for general EFI applications?

Thanks, Pramod

0


source to share


2 answers


These are the steps I took to integrate Bullseye into EDK2 (after installing Bullseye as instructed on the website):

  • Use / run / libcov -printf.c and replace "printf" with "AsciiPrint".
  • Copy all files from / run / to your EDK $ WORKSPACE
  • Create a library .inf file and add libcov-printf.c to its [Source] section
  • Add an instance of the library to your platform's .dsc file (probably MdeModulePkg.dsc)
  • Add a link to the library of your .inf file of your application in the [LibraryClass] section
  • Add cov_dumpData () to your application source code (usually at its exit point).
  • compile with assembly EDK2


You end up with an efi binary that you can run on your target and get measurements as soon as the app reaches the exit point. The output can be redirected to a file (using the> directive inside the EDK2 wrapper) and then processed by covpost to be merged into a cov file created during the build process.

+1


source


Well, I don't know how EFI works. However, bullseye support is customizable. When I was working on an embedded system. I created open / read / write functions to write coverage data not to a file but to a serial cable, and I created a host application to interpret the data sent from the serial cable and save it to a cov file. I'm not sure if this works well for your case. However, you can start with the following link. http://www.bullseye.com/help/env-embedded.html



0


source






More articles:


All Articles