pfSense » pfSense Packages

Example report from a customer (serial omitted):
Running 2.4.1 and trying to update Netgate Coreboot from 01.00.00.09 to 01.00.00.18.

Incorrect flash image file size.
Failed to update OEM section, exiting ...
Updating flashing ...
SN: XXXXX
Serial Number Read from Flash XXXXX

Another report from the same customer - may indicate a deeper issue at play, odd since we didn't receive reports of this prior to .18*:

The Coreboot of the other unit upgraded succesfully from 01.00.00.14 to 01.00.00.15. I'm doing the firmware upgrade in couple of minutes on that one too.

After firmware upgrade on other unit, the Coreboot version is now downgraded to 01.00.00.09. After trying to update, the same problem occurs.

Incorrect flash image file size.
Failed to update OEM section, exiting ...
Updating flashing ...
SN: XXXXXXXX
Serial Number Read from Flash XXXXXXXX

Serial omitted

After powering off/on the equipment, the system shows the latest version number with the proper serial (I had no physical access to the device at that time).

I suspect, for this platform (RCC -- not RCCVE, RCCVE works perfectly), the adi_powercycle is not working properly.

EDIT: Sorry, I see there is no adi_powercycle for the RCC platform (that reboot apparently is not good enough):

https://github.com/pfsense/FreeBSD-ports/blob/237f203ce317a86824bd4544babf750d2a7c7412/sysutils/pfSense-pkg-Netgate_Coreboot_Upgrade/files/usr/local/www/netgate_coreboot_upgrade.php#L97

Update from the customer in my previous comment:

The BIOS now shows the latest version. Apparently a physical shutdown (restart) is required. Or the adi_powercycle is not working properly for that platform.

The “scrambled” serial number appeared after the reboot initiated by the firmware upgrade process of the Netgate_Coreboot_Upgrade pfSense-package, as I had no physical access to the device.

Today, the person who took the pictures had to power off and unplug the device, producing the needed power cycle. After that, it showed the serial number and firmware version correctly.

Update from the customer in my initial post:

Confirmed. After power cycling, the version reported was 01.00.00.18.

According ADI engineers XG-2758 requires a physical power cycle after upgrade coreboot and because package tries to reboot it, it ends up booting on 2nd flash (8m).

Package must be changed to doesn't reboot but instead add a warning on dashboard asking user to power cycle it.

I am experiencing a problem similar to this.

except my XG-2758 is rebooting by it self after upgrade. And it stays on version ADI_RCC-01.00.00.09-nodebug, not ADI_RCC-01.00.00.18.

I have tried manual power cycle but no luck.

It worked just had to unplug the power instead of pushing the red button the back.

Renato Botelho wrote:

According ADI engineers XG-2758 requires a physical power cycle after upgrade coreboot and because package tries to reboot it, it ends up booting on 2nd flash (8m).

Package must be changed to doesn't reboot but instead add a warning on dashboard asking user to power cycle it.

So that's still not working for me. I'm on 01.00.00.09 currently, and no combo of power cycles/reboots seems to update it to 01.00.00.18 which it says is available.