Home
Support

Knowledge Base

BSPs and drivers
Community resources
Product documentation
Questions?
Contact us

How to boot in UEFI mode
 
________________________________________________________________________

Applicable Environment
________________________________________________________________________
  • Topic: BSP, UEFI
  • SDP: 7.1.0, 7.0.0
  • Target: x86_64
________________________________________________________________________

Issue
________________________________________________________________________
    UEFI doesn't support text mode (console) messages any more. You will likely not see any messages on the monitor when booting from disk once ExitBootServices is called in startup.

    ________________________________________________________________________

    Solution
    ________________________________________________________________________
      The QNX x86_64 BSP includes a build file (x86_64-uefi.build) for an UEFI bootimage (IFS) and configuration files to create a disk image. After installing the BSP the files are located in the $BSP_ROOT_DIR/images directory. The UEFI IFS is built by running

      # make x86_64 x86_64-uefi.efi

      in $BSP_ROOT_DIR/images. The disk image is created by running

      # make uefi_disk_image

      The created uefi_disk.img disk image contains a 100MB EFI boot partition and a 200MB fs-qnx6 partition. Total size is by default 400MB. You can copy the disk image onto a USB stick or hard drive and boot from the device. You can flash the image with dd, win32diskimager or rufus.

      You will need to use one of the following options to get access to a console on UEFI systems:
      • Serial port (UART), using devc-ser8250 driver. If you have a serial port, then you can redirect startup and display_msg messages to this device.
      • USB-to-Serial dongle, using the devc-serusb driver.
      • Configure your build file to start a telnet/ssh host session as the system boots, so that the session can be logged into remotely.
      The UEFI buildfile is setup to start the devc-ser* drivers (in startup-script), and inetd is started to access the system via telnet (via net-start.sh).


      ________________________________________________________________________
      NOTE: This entry has been validated against the SDP version listed above. Use caution when considering this advice for any other SDP version. For supported releases, please reach out to QNX Technical Support if you have any questions/concerns.
      ________________________________________________________________________


      Related Attachments
       None Found





      Please contact us with your questions or concerns.