Please find below the steps we followed:
- Download ITK6.1.5 from https://downloadcenter.intel.com/download/26307/Intel-Integrator-Toolkit
- Extract the zip file in a USB thumb drive and insert it into a USB port
- Copy the .jpg file in the thumb drive
- .jpg file must be less than 120KB
- Width/height larger than 120 px
- Width/height less than 1920 / 1080 px
- Press F2 during boot to enter BIOS setup
- Go to Advanced -> Boot -> Boot Configuration
- In the Boot devices pane, enable Internal UEFI Shell
- Press F10 to save changes and exit BIOS Setup
- When Shell screen in displayed, identify the fs(x) where the Removable device is located
- At the command prompt:
- Fsx: <enter> - Where x is the port identification
- ITX6.efi -b -x myCustomBio.bio -ic -il file.jpg
- The file myCustomBio.bio will be created in the thumb drive directory
- Restart the system and update the BIOS using F7 key and select the myCustomBio.bio file
- When the screen prompt, press 9 to allow changes in Graphics settings.
- Once the update finishes, the new splash image will be displayed.
Please try the steps above and let me know how it goes.
Hey Juan Carlos,
I followed your instructions to the letter, without success. According to the screen output everything went fine with creating and flashing the image, but there is still no splash image displayed. For reference, here's the logo I used to test this, and the resulting BIO file, which does not work as expected on both my 5CPYH kits. Inspecting the BIO file with a HEX editor also didn't result in anything useful.
Just to be sure not to miss anything:
- I'm using the NUC5CPYH kit (2 units) with my own RAM and SSD installed.
- BIOS version which was installed on both units was PY0062.bio
- You tested the same configuration (a NUC5CPYH kit), and following your steps produced an image with custom splash logo?
I quickly tested an older unit I had bought earlier, which is still on PY0050.bio, but no success either: That unit now also has a "blank" splash logo.
Thanks for the help so far!
Hey Juan Carlos,
yes, I talked to Noah about the issue and he gave me access to a modified ITK binary which resolved the issue. In short: The issue was triggered by my monitor, which is a custom-made solution for a customer. With off-the-shelf monitors the original ITK (and the steps described by you and the manual) work as expected.
While debugging this we also solved the SMBIOS issue: ITK wasn't able to copy the SMBIOS configuration into my BIO image because the "Chassis Type" has to be set explicitly - on a fresh unit it currently shows up as set to 1 (according to "ITK.efi -s -p"), although the value is actually not yet set. As soon as I set it (with e.g. "ITK.efi -s -t chassis -f type -v 1"), I was also able to include the SMBIOS config into my custom image.
According to Noah the fix for the monitor issue will land in an official release sometimes in the future, as well as some improvements to the SMBIOS handling which we discovered along the way.
Thanks for all the help!