# US 12,117,912 B2 · Enriched pre-extensible firmware interface initialization graphics > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,117,912 B2 - Document ID: US12117912B2 - Status: Granted - Kind: B2 - Application number: 17/708,280 - Filed: 2022-03-30 - Published: 2023-10-05 - Granted: 2024-10-15 - Earliest claimed: 2022-03-30 - Assignees: Dell Products L.P. - Applicants: Dell Products L.P. - Inventors: Ibrahim Sayyed; Frank Quintanilla; Adolfo S. Montero; Jagadish Babu Jonnada - Web page: https://patentgrep.com/patent/US12117912B2 ## CPC - G06F 11/2221: {to test input/output devices or peripheral units} - G06F 9/4401: Bootstrapping (security arrangements therefor G06F21/57) - G06F 11/2284: {by power-on test, e.g. power-on self test [POST]} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An information handling system includes an embedded controller configured to transmit an error code to a pre-extensible firmware interface initialization module. A graphics font manager may generate a glyphs database during a boot process. If the error code is associated with a no power-on self-test, no video condition, then the pre-extensible firmware interface initialization module may retrieve information associated with the error code transmitted by the embedded controller, and locate the glyphs database generated by the graphics font manager from the non-volatile storage device. ## Claims ### Claim 1 A method comprising: generating, by a processor, a glyphs database during a boot process; storing the glyphs database in a non-volatile storage device, wherein the glyphs database includes a plurality of font glyphs; in response to determining that a no power-on self-test (POST), no video condition is encountered during the boot process, transmitting by an embedded controller an error code associated with the no POST, no video condition to a basic input/output system; retrieving information associated with the error code from the glyphs database; and rendering, by the basic input/output system, the information in a display device using the font glyphs in the glyphs database. ### Claim 2 (depends on 1) The method of claim 1, wherein the rendering is performed using a graphics output protocol. ### Claim 3 (depends on 1) The method of claim 1, wherein the glyphs database is accessible to the embedded controller during the boot process. ### Claim 4 (depends on 1) The method of claim 1, wherein the embedded controller saves an address of the glyphs database in the non-volatile storage device. ### Claim 5 (depends on 1) The method of claim 1, wherein the generating of the glyphs database is performed during a driver execution environment phase. ### Claim 6 (depends on 1) The method of claim 1, in response to determining that the no POST, no video condition is a fatal error, halting the boot process. ### Claim 7 (depends on 1) The method of claim 1, in response to determining that the no POST, no video condition is not a fatal error, continuing with the boot process. ### Claim 8 An information handling system, comprising: an embedded controller configured to transmit an error code to a basic input/output system; and a processor configured to generate a glyphs database during a boot process of the information handling system and to store the glyphs database in a non-volatile storage device, wherein the glyphs database includes a plurality of font glyphs; the basic input/output system configured to: retrieve information associated with the error code transmitted by the embedded controller; in response to a determination that the error code is associated with a no power-on self-test, no video condition, locate the glyphs database from the non-volatile storage device; and render the information using the font glyphs in the glyphs database. ### Claim 9 (depends on 8) The information handling system of claim 8, wherein the basic input/output system renders the information using a graphics output protocol. ### Claim 10 (depends on 8) The information handling system of claim 8, wherein the glyphs database is accessible to the embedded controller during the boot process of the information handling system. ### Claim 11 (depends on 8) The information handling system of claim 8, wherein the glyphs database is stored in an extensible firmware interface system partition. ### Claim 12 (depends on 8) The information handling system of claim 8, wherein the embedded controller saves an address of the glyphs database in the non-volatile storage device. ### Claim 13 (depends on 8) The information handling system of claim 8, wherein the processor generates the glyphs database during a driver execution environment phase of the boot process. ### Claim 14 A non-transitory computer-readable media to store instructions that are executable to perform operations comprising: generating a glyphs database during a boot process: storing the glyphs database in a non-volatile storage device, wherein the glyphs database includes a plurality of font glyphs; in response to determining that an issue that is a no power-on self-test (POST), no video condition is encountered during the boot process, transmitting an error code associated with the no POST, no video condition to a basic input/output system; retrieving an image associated with the error code from the glyphs database; and rendering the image associated with the issue using the font glyphs in the glyphs database. ### Claim 15 (depends on 14) The non-transitory computer-readable media of claim 14, wherein the image is associated with a firmware file globally unique identifier. ### Claim 16 (depends on 14) The non-transitory computer-readable media of claim 14, wherein the font glyphs are bitmaps of fonts. ### Claim 17 (depends on 14) The non-transitory computer-readable media of claim 14, further comprising in response to determining that the no POST, no video condition is a fatal error, halting the boot process. ### Claim 18 (depends on 14) The non-transitory computer-readable media of claim 14, wherein the image includes mitigation steps for the no POST, no video condition. ### Claim 19 (depends on 14) The non-transitory computer-readable media of claim 14, wherein the rendering of the image is performed using a graphics output protocol. ### Claim 20 (depends on 14) The non-transitory computer-readable media of claim 14, wherein the retrieving of the error code is performed during a pre-extensible firmware interface initialization phase of the boot process.