Aptivi - Deprecated Manuals
ProjectsWebsiteBlog
GRILO - Manual
GRILO - Manual
  • 👋Welcome!
  • Versions
    • 🗞️Version Release Notes
      • 💎API v1.0 series
      • 🎆API v2.0 series
    • 🗒️Compatibility Notes
      • 🔼Upgrading from API v1.0
  • Installation
    • 📀Installing GRILO
      • 🖥️Windows
      • 🐧Linux
      • 📱Android
    • ⬆️Upgrading GRILO
      • 🖥️Windows
      • 🐧Linux
      • 📱Android
  • Fundamentals
    • 💿What is the Bootloader?
    • 💎What is GRILO?
    • 🪄Simulated Bootloader Features
      • 📀Boot Choices
  • Power Users
    • ⚙️Configuration
    • 💡Custom Boot Styles
    • 💽Boot Apps
    • 🦠Diagnostics
  • 🧱Project Dependencies
  • Report an issue
  • Source code
  • Our projects
  • API Reference
Powered by GitBook
On this page
  1. Power Users

Diagnostics

How do you diagnose the bootloader?

GRILO contains diagnostic tools that can be enabled with the Diagnostic messages variable found in the bootloader configuration. It basically saves all the debug information written with the DiagnosticsWriter.WriteDiag() function.

The following diagnostics levels (DiagnosticsLevel enum) are usable:

  • Info

    • Informational diagnostic messages

  • Warning

    • Warning messages

  • Error

    • Error messages, usually indicating that something is wrong

Any diagnostic information is written to the BootloaderDebug.log file with the following format:

[<level>] <content>

where:

  • level

    • The first letter of the diagnostics level

  • content

    • Any message to be written

Before GRILO 1.2.0, if the printing to console option is enabled, you can also see the diagnostic messages being printed to the console live.

Last updated 1 year ago

🦠