Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
1,468 Views

NUC5PPYB firmware update fails

Jump to solution

Summary: F7 firmware update fails; after selection .bio file, system reboots (expected), but then reboots again without starting firmware update it just boots the installed OS. Previous firmware updates have happened without difficulty.

Version:

https://downloadcenter.intel.com/download/26630/NUCs-BIOS-Update-PYBSWCEL-86A- Download BIOS Update [PYBSWCEL.86A]

PY0062.BIO

Reproduce steps:

1. Download bio file from above URL.

2. Copy to a FAT formatted USB stick.

3. Reboot NUC, holding down F7.

4. Navigate to USB stick and choose the bio file then press enter.

Actual result:

Reboot (expected)

Reboot, and starts up installed OS.

Expected result:

Reboot and status as it's extracting and installing the various images in the update.

System info from dmidecode:

Product Name: NUC5PPYB

Version: H76558-102

PYBSWCEL.86A.0058.2016.1102.1842

From dmesg (basically the same info):

[0.000000] DMI: /NUC5PPYB, BIOS PYBSWCEL.86A.0058.2016.1102.1842 11/02/2016

There are no messages on the display throughout.

Tags (1)
0 Kudos

Accepted Solutions
Highlighted
Super User
68 Views

Hi

Try update your bios using bios recovery method: http://www.intel.com/content/www/us/en/support/boards-and-kits/000005532.html BIOS Recovery Update Instructions for Intel® NUC

As you can see there are two ways to execute bios recovery:

- Power Button Menu

or

- Security jumper removed

In both methods the USB with the .bio file shall be inserted into USB slot.

1. Power Button Menu

1.1 Press power Button about 3 seconds (now more than 4 seconds). Release the power button after you hear 3 beeps and/or the blue led changes color to orange.

1.3 NUC will reboot into Power Button menu.

1.4 Press F4 to start the recovery process.

2. Security jumper removed.

2.1 Open the bottom NUC cover and remove the Security Jumper

2.2 Power ON the NUC. The recovery process will start automatically.

2.3 After completion, power OFF the NUC and replace the security jumper.

Hope this helps

Leon

View solution in original post

0 Kudos
17 Replies
Highlighted
Super User
69 Views

Hi

Try update your bios using bios recovery method: http://www.intel.com/content/www/us/en/support/boards-and-kits/000005532.html BIOS Recovery Update Instructions for Intel® NUC

As you can see there are two ways to execute bios recovery:

- Power Button Menu

or

- Security jumper removed

In both methods the USB with the .bio file shall be inserted into USB slot.

1. Power Button Menu

1.1 Press power Button about 3 seconds (now more than 4 seconds). Release the power button after you hear 3 beeps and/or the blue led changes color to orange.

1.3 NUC will reboot into Power Button menu.

1.4 Press F4 to start the recovery process.

2. Security jumper removed.

2.1 Open the bottom NUC cover and remove the Security Jumper

2.2 Power ON the NUC. The recovery process will start automatically.

2.3 After completion, power OFF the NUC and replace the security jumper.

Hope this helps

Leon

View solution in original post

0 Kudos
Highlighted
Beginner
68 Views

OK so initially this fails the exact same way.

Following these instructions

http://www.intel.com/content/www/us/en/support/boards-and-kits/000005532.html BIOS Recovery Update Instructions for Intel® NUC

I get to step 6, but then step 7 doesn't appear, it just reboots again and I see the bootloader for the installed OS.

The USB stick in question uses GPT scheme, not MBR. sgdisk reports the following info for that partition:

[chris@f26h ~]$ sudo sgdisk -i 1 /dev/sda

Partition GUID code: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 (Microsoft basic data)

Partition unique GUID: 89814FF6-DB37-4641-B628-074E001864E4

First sector: 2048 (at 1024.0 KiB)

Last sector: 31277022 (at 14.9 GiB)

Partition size: 31274975 sectors (14.9 GiB)

Attribute flags: 0000000000000000

Partition name: 'Microsoft basic data'

The format is FAT32. This stick had been recently partitioned and formatted just for this firmware update. And the F7 update method in fact shows the firmware file on the stick.

Anyway, I went to a different stick MBR partitioned, and FAT32 formatted, with the same file saved on it. And the F4 method worked. I didn't try the F7 method first; and I don't have an easy way to test if there's a regression that makes either F4 or F7 methods dislike GPT partitioned USB sticks for flashing firmware, or if there's some other explanation.

0 Kudos
Highlighted
Super User Retired Employee
68 Views

Was the stick formatted from Linux? If so, there's your problem. Linux doesn't do FAT32, it does VFAT.

0 Kudos
Highlighted
Beginner
68 Views

'mkdosfs -F 32' certainly is FAT32, and the EFI System partition on this NUC is created with that command, and the firmware finds the bootloader and loads it just fine. So that's definitely not the problem.

0 Kudos
Highlighted
Community Manager
68 Views

Hello cmurf,

It's a strange behavior, from our end we have not seen cases similar like the one you are reporting. We always format in FAT32 from Windows, and the F7 method works fine.

I am glad to hear you were able to find a fix, and thank you for sharing it with the community.

Regards,

Amy.

0 Kudos
Highlighted
Beginner
68 Views

I also had serious problems after upgrading from BIOS 55 to 78. After the BIOS update completed successfully, the board won't provide any output on HDMI. I did this with two boards :-( both did the same thing. None of the BIOS recovery methods seem to provide HDMI output once this has happened, I'm afraid the units are bricked.

0 Kudos
Highlighted
Super User Retired Employee
68 Views

Did you jump all the way from 55 to 78 in one update? Can you see me wincing?

 

At this point, your best bet is to attempt to reinstall BIOS 78 using the jumper-based BIOS Recovery process.

 

Note: Once you power on with the jumper removed, if there is no update on the screen (meaning you cannot see when the operation completes), you must wait 10-15 minutes before powering off. If the recovery operation is actually proceeding without a display and you power off in the middle of it, you are pretty well guaranteed to brick the BIOS.

 

...S

0 Kudos
Highlighted
Beginner
68 Views

Yep, 55 to 78 in one update. I was worried about that too, but the release notes had no recommended update sequence and if intermediate BIOS releases are available anywhere, I wasn't able to find them. Do you know where they are? Is there a recommended upgrade sequence? The release/recovery notes suggest 5 minutes before powering off; did you see 10-15 somewhere?

0 Kudos
Highlighted
Super User Retired Employee
68 Views

The only-the-paranoid-survive rule of thumb is to install all releases that mention that they contain security fixes/changes. Realistically, though, you can jump up a few (say, not more than 10) releases at a time if nothing untoward is noted. From where you are now, jumper-based BIOS Recovery to the latest build is all you can do. If this doesn't work, you may be out of luck.

...S

0 Kudos
Highlighted
Beginner
68 Views

If true, at a *bare minimum* this needs to be a huge warning on the readme, release notes, and upgrade process. I've been designing embedded systems for 30 years and it would be absolutely unacceptable in any professional environment to release an upgrade that bricks the system even when properly installed. I don't believe a company like Intel would do that.

 

Moreover, as I'd mentioned, the earlier BIOS releases do not appear to be available so there isn't even a path to incremental upgrades of the BIOS (nor guidance on whether or how to do so).

 

Fortunately, I don't believe the two boards are bricked; when I attempt the security jumper update, the board's blue light comes on, fan spins up, the board complains if no RAM is present, and if RAM is present will access the USB flash drive. I suspect the HDMI output is simply disabled in 78; unfortunately I don't have a VGA cable and may need to get one.

0 Kudos
Highlighted
Beginner
68 Views

It turns out that the BIOS update was successful *BUT* with BIOS 78, there is absolutely no BIOS video output on the HDMI port. If you let the system boot, the OS output on HDMI is fine.

Is there any way to enable the BIOS output on HDMI from the latest BIOS without VGA access?

0 Kudos
Highlighted
Super User
68 Views

If you are connected to TV , try to connect your NUC to PC monitor.

 

Leon

 

Highlighted
Super User Retired Employee
68 Views

I have BIOS 78 installed on my NUC5PGYB (which is exact same board but has eMMC SSD soldered down) and there is no issue with BIOS output. If, as you say, it is properly outputting in Windows (showing that HDMI interface has not failed), then we need to look at the BIOS configuration. After some trial and error, I was finally able to repeat the scenario. You need to configure the BIOS to output only to the VGA connector. Now, this takes setting both the IGD Primary to VGA and the IGD Secondary to None. Setting only one of these two parameters does not completely block the output from appearing on the HDMI connector; it takes both.

 

Ok, I can see only two possibilities here, (1) this was purposefully configured this way prior to the BIOS upgrade or (2) the big jump from BIOS 55 to 78 somehow caused this configuration change. We know the former isn't true (thought I was going to accuse you for a minute there, eh?) so the latter must be true (unless I missed something?). I will see what the NUC team has to say about this (if they will even talk to me about a discontinued board).

 

...S

Highlighted
Beginner
68 Views

n.scott.pearson: first, wow...thank you for putting in such an amazing amount of effort to help a stranger!!! You're awesome!

Also, I'm sorry if you now have a unit with similarly disabled BIOS video.

 

It seems clear that possibility 2 is what happened. I did the upgrade from 55 using the BIOS (on the HDMI output) so it was clearly configured for HDMI (that's the only output I have!). I think Intel could easily reproduce this by configuring a board with BIOS 55 and doing the upgrade to 78. It happened on two boards so it was not a fluke. If this were me, I'd release a 79 to fix this since it's a fairly catastrophic failure with no clear recovery path.

 

That said, I wonder if I could ask a favor: there is almost certainly a key sequence at boot that will enable HDMI in78, since you have other units running 78, would you be willing to document that sequence? If so, I could probably fix my units by entering the BIOS (F2) and then the proper key sequence while flying blind.

 

Either way, thank you again for all of your efforts!

0 Kudos
Highlighted
New Contributor III
68 Views

I've seen issues like this where the HDMI monitor is older and can't handle something in the sync with the new BIOS. After you boot into Visual BIOS using a VGA monitor, did you load F9 Defaults? I do know that there are a lot of security updates and microcode updates in between 0058 and 0078. Could be something there that is preventing you from seeing the boot process. Also, check you version of the TXE firmware in the page that shows System and Product Manufacturer. Is it showing 02.00.02.2092?

0 Kudos
Highlighted
Super User Retired Employee
68 Views

Gee Mitch, even I didn't follow that completely. 😨

0 Kudos
Highlighted
Super User Retired Employee
68 Views

The default configuration for these parameters is Auto (i.e. use whatever output is identified first). So, do the following (in the blind):

 

  1. Power on NUC.
  2. Press F2 once per second for ~20 seconds.
  3. Press F9.
  4. Press Y.
  5. Press F10.
  6. Press Y.

 

Unit should reboot and default to the HDMI display if only display plugged in.

 

Hope this works for you (seemed to for me).

,,,S

0 Kudos