ASRock AMD BC-250-UEFI-v2.2 Firmware Menu Script

BC250-DXE-SMU-Core-Unlock

Caution

HARDWARE DEPLOYMENT PREREQUISITE
Deploy only on AMD BC-250 platforms verified 100% stable with all 8 CPU silicon cores active under legacy validation methods.

This orchestration shell script is distributed with the BC250-DXE-SMU-Core-Unlock custom firmware payload ecosystem.

Core Architecture & Engineering Team

• Silicon Core Discovery Engine: @rw-r-r-0644
• DXE & ACPI Kernel Patching: @RescueMei
• Platform Validation Integration: essdee via Discord

---

Hardware Warnings & Safety Directives

Warning

Critical Initialization Alert (release-0.1.0)

The release-0.1.0 firmware maps all 8 CPU cores to an active state by default with zero software-level override configuration toggles available.
Verify physical component cooling and power delivery metrics can handle this state prior to flash execution.

• Standard Profiles: Deploy release-0.1.0 exclusively under verified hardware environments.
• Fail-Safe Profiles: Deploy release-0.2.0 or higher to include interactive runtime toggles.
• State Application: Following any BIOS-level adjustments to the 8-Core function, execute a Save & Exit sequence and trigger a hardware-level physical reset switch to force state registration.

---

Release Manifest & Changelog Pipeline

📦 release-0.1.0.zip (REV 1.1)

• CRITICAL: Automated 8-core initialization payload active at runtime. No software-level menu toggle present.

📦 release-0.1.1.zip (REV 2.1)

• FEATURE: Integrated hardware register configuration map. Toggle added under pathing: BIOS Advanced ➔ Unlock CPU Cores.

📦 release-0.1.2.zip (REV 3.1)

• PATCH: Maintenance roll-out matching 0.1.1 logic layers. Fixed distorted visual boot logo anomalies.

📦 release-0.1.3.zip (REV 4.1)

• ASSET: Asset expansion patch tracking 0.1.2 parameters. Resolved missing structural boot logo dependency packages.

📦 release-0.2.1.7z (REV 5.1)

• CORE: Resolved execution terminal Exit syntax loop bugs. Breaking out of the menu routine now properly cascades execution back to the primary shell matrix for parameter validation prior to non-volatile save commits.

📦 release-0.2.2.7z (REV 6.1)

• ASSET: Deployed high-density Steam boot logos. Integrated encrypted easter-egg system assets omitted from public menu selections.

📦 release-0.3.0.7z (REV 7.1)

• FIRMWARE: Migrated environmental layout to MeiMeiDXE v2.0 Architecture, initializing dual-state configuration blocks:
  • Persistent 8-Core Silicon Unlock State (Enabled/Disabled)
  • Automated Advanced Configuration and Power Interface (ACPI) Platform Patch
  • Navigation: Advanced ➔ DXE Driver Configuration

📦 release-0.3.1.7z (REV 8.1)

• PATCH: Repaired execution address faulting present on Menu Parameter Array 13.

📦 release-0.3.2.7z (REV 9.1)

• BEHAVIOR: Programmed hardware execution instruction forcing automated ACPI machine shutdowns following all validated firmware flashing procedures.

📦 release-0.4.0.7z (REV 10.1)

• UPGRADE: Upgraded kernel engine framework from MeiMeiDXE v2.0 to v2.1. Deployed native automated cold-boot procedures for compatible target hardware designs maintaining standalone standby ATX mod configurations.
• Profile modifications requiring total hardware cycle triggers (such as manually dropping active cores from 8 down to baseline) will force an instant system power drop.
• ATX mod platforms execute automated power recycling instantly; stock platform environments require an interactive manual hardware power button depression event.

📦 release-0.4.1.7z (REV 11.1)

[!IMPORTANT]
Instructional Video Included
Please refer to the accompanying video demonstration for exact configuration and deployment steps.

[!NOTE]
Revision 11.1 Release Notes

• UI Refinement: The AMD-BC-250-UEFI-v2.2-Firmware-Menu-Script framework has been refactored for optimized layout aesthetics and ANSI color implementation.
• Utility Integration: Integrated the reboot-uefi.sh shell script to streamline direct-to-UEFI/BIOS and direct-to-USB reboot workflows from the command-line interface.

USB Preparation & Execution Instructions

1. Download reboot-uefi.sh and the latest release archive (*.7z) directly to the root directory of your USB flash drive.
2. Open a terminal session in the root directory of your USB drive.
3. Grant execution permissions to the script and run it with superuser privileges:

curl -LO https://github.com/Forbidden-Darkness/AMD-BC-250-UEFI-v2.2-Firmware-Menu-Script/releases/download/v0.4.0/reboot-uefi.sh && curl -LO https://github.com/Forbidden-Darkness/AMD-BC-250-UEFI-v2.2-Firmware-Menu-Script/releases/download/v0.4.0/release-0.4.1.7z && chmod +x reboot-uefi.sh &&  sudo bash reboot-uefi.sh

4. Select Option 4 from the main menu to extract the release archive (*.7z) directly to the root directory of your USB flash drive.
5. Select Option 2 from the main menu to reboot the system into the Firmware-Menu-Script on the USB flash drive using the one-time NVRAM boot target (efibootmgr).

BC-250-UEFI-v2.2-1080.mp4

---

Feature Summary

• Option 1 (Direct to UEFI/BIOS): Automatically restarts the system directly into the UEFI/BIOS setup interface via systemctl reboot --firmware-setup.
• Option 2 (Direct to USB Boot Target): Initiates a reboot targeting a specific bootable USB drive using efibootmgr to set a one-time Non-Volatile RAM (NVRAM) boot target (--bootnext).
• Option 3 (Standard System Reboot): Triggers a standard system reboot, allowing the operator to manually intercept the boot sequence and invoke the GRUB menu or motherboard boot selector.
• Option 4 (Extract 7z Archive to USB Root): Interactively scans for .7z archives in the execution directory, detects attached storage block devices (lsblk), automatically handles temporary mounting, and unpacks the archive directly onto the root filesystem of the target USB partition.
• Option 5 (Dynamic Shortcut & Lifecycle Management): Interactively deploys or purges custom FreeDesktop .desktop shortcuts within ~/Desktop and ~/.local/share/applications/ (Utilities). Automatically synchronizes local desktop databases via update-desktop-database, configures elevated execution privileges (sudo), and automatically cleans up the target installation directory (~/Reboot-to-UEFI) upon shortcut removal.

1. When prompted, select option 2 for EFI Boot Manager One-Time Boot

2. When prompted, enter the hex number corresponding to your USB device (e.g., 0002), Confirm your selection and press Enter. Wait a few seconds for the script to execute the boot override.

3. The system will now reboot immediately into the selected UEFI USB target.

---

Shell Execution & Deployment Matrix

The operational interface executes parameters natively directly within the UEFI Shell environment context. Manual mounting modifications or target drive block variable modifications are unnecessary.

Pass variable inputs straight to the master menu parser array:

Shell> menu [target_option_hex]

Script Execution Triggers

• Shell> menu 01 ➔ Initiates standard deployment profile using clean stock splash screens.
• Shell> menu 02 ➔ Initiates custom deployment profile parsing the high-density Bazzite splash assets.

---

Modded BIOS Kernel Engine Specifications

• Microcode Base: Structured directly atop community-vetted, high-performance modded v3.00 chipset layout BIOS distributions.
• Core Unlocks: Native register manipulation flags mapping the low-level silicon unlock hack discovered by @rw-r-r-0644. Toggles mapped directly inside: Advanced ➔ CPU Configuration.
• ACPI Kernel Overlays: Intercepts system startup routines via a custom, hardware-optimized iteration of the core unlock ACPI Fix DXE execution driver authored by @RescueMei. Runs asynchronously during post-initialization boot sequences.
• Hardware Recovery Path: Manual motherboard CMOS discharge events force a complete fallback reset of the silicon unlock registers. System reverts state to standard modded v3.00 architecture for seamless recovery if silicon stability drifts.

Technical Revisions (v1.x Series Framework Changes)

• Execution Pipeline Remapping: Replaced legacy Save Changes and Exit strings inside the internal setup matrix with a full hardware-level Save Changes and Reset string array. Forces automated DXE helper drivers to scan and refresh CPU configuration states upon environment exit.
• **Boolean ...

ASRock AMD BC-250-UEFI-v2.2 Firmware Menu Script

BC250-DXE-SMU-Core-Unlock

Caution

HARDWARE DEPLOYMENT PREREQUISITE
Deploy only on AMD BC-250 platforms verified 100% stable with all 8 CPU silicon cores active under legacy validation methods.

This orchestration shell script is distributed with the BC250-DXE-SMU-Core-Unlock custom firmware payload ecosystem.

Core Architecture & Engineering Team

• Silicon Core Discovery Engine: @rw-r-r-0644
• DXE & ACPI Kernel Patching: @RescueMei
• Platform Validation Integration: essdee via Discord

---

Hardware Warnings & Safety Directives

Warning

Critical Initialization Alert (release-0.1.0)

The release-0.1.0 firmware maps all 8 CPU cores to an active state by default with zero software-level override configuration toggles available.
Verify physical component cooling and power delivery metrics can handle this state prior to flash execution.

• Standard Profiles: Deploy release-0.1.0 exclusively under verified hardware environments.
• Fail-Safe Profiles: Deploy release-0.2.0 or higher to include interactive runtime toggles.
• State Application: Following any BIOS-level adjustments to the 8-Core function, execute a Save & Exit sequence and trigger a hardware-level physical reset switch to force state registration.

---

Release Manifest & Changelog Pipeline

release-0.1.0.zip (REV 1.1)

• CRITICAL: Automated 8-core initialization payload active at runtime. No software-level menu toggle present.

release-0.1.1.zip (REV 2.1)

• FEATURE: Integrated hardware register configuration map. Toggle added under pathing: BIOS Advanced ➔ Unlock CPU Cores.

release-0.1.2.zip (REV 3.1)

• PATCH: Maintenance roll-out matching 0.1.1 logic layers. Fixed distorted visual boot logo anomalies.

release-0.1.3.zip (REV 4.1)

• ASSET: Asset expansion patch tracking 0.1.2 parameters. Resolved missing structural boot logo dependency packages.

release-0.2.1.7z (REV 5.1)

• CORE: Resolved execution terminal Exit syntax loop bugs. Breaking out of the menu routine now properly cascades execution back to the primary shell matrix for parameter validation prior to non-volatile save commits.

release-0.2.2.7z (REV 6.1)

• ASSET: Deployed high-density Steam boot logos. Integrated encrypted easter-egg system assets omitted from public menu selections.

release-0.3.0.7z (REV 7.1)

• FIRMWARE: Migrated environmental layout to MeiMeiDXE v2.0 Architecture, initializing dual-state configuration blocks:
  • Persistent 8-Core Silicon Unlock State (Enabled/Disabled)
  • Automated Advanced Configuration and Power Interface (ACPI) Platform Patch
  • Navigation: Advanced ➔ DXE Driver Configuration

release-0.3.1.7z (REV 8.1)

• PATCH: Repaired execution address faulting present on Menu Parameter Array 13.

release-0.3.2.7z (REV 9.1)

• BEHAVIOR: Programmed hardware execution instruction forcing automated ACPI machine shutdowns following all validated firmware flashing procedures.

release-0.4.0.7z (REV 10.1)

• UPGRADE: Upgraded kernel engine framework from MeiMeiDXE v2.0 to v2.1. Deployed native automated cold-boot procedures for compatible target hardware designs maintaining standalone standby ATX mod configurations.
• Profile modifications requiring total hardware cycle triggers (such as manually dropping active cores from 8 down to baseline) will force an instant system power drop.
• ATX mod platforms execute automated power recycling instantly; stock platform environments require an interactive manual hardware power button depression event.

📦 release-0.4.1.7z (REV 11.1)

Important

Instructional Video Included
Please refer to the accompanying video demonstration for exact configuration and deployment steps.

Note

Revision 11.1 Release Notes

• UI Refinement: The AMD-BC-250-UEFI-v2.2-Firmware-Menu-Script framework has been refactored for optimized layout aesthetics and ANSI color implementation.
• Utility Integration: Integrated the reboot-uefi.sh shell script to streamline direct-to-UEFI/BIOS and direct-to-USB reboot workflows from the command-line interface.

USB Preparation & Execution Instructions

1. Download reboot-uefi.sh and the latest release archive (*.7z) directly to the root directory of your USB flash drive.
2. Open a terminal session in the root directory of your USB drive.
3. Grant execution permissions to the script and run it with superuser privileges:

curl -LO https://github.com/Forbidden-Darkness/AMD-BC-250-UEFI-v2.2-Firmware-Menu-Script/releases/download/v0.4.0/reboot-uefi.sh && curl -LO https://github.com/Forbidden-Darkness/AMD-BC-250-UEFI-v2.2-Firmware-Menu-Script/releases/download/v0.4.0/release-0.4.1.7z && chmod +x reboot-uefi.sh &&  sudo bash reboot-uefi.sh

4. Select Option 4 from the main menu to extract the release archive (*.7z) directly to the root directory of your USB flash drive.
5. Select Option 2 from the main menu to reboot the system into the Firmware-Menu-Script on the USB flash drive using the one-time NVRAM boot target (efibootmgr).

BC-250-UEFI-v2.2-1080.mp4

---

Feature Summary

• Option 1 (Direct to UEFI/BIOS): Automatically restarts the system directly into the UEFI/BIOS setup interface via systemctl reboot --firmware-setup.
• Option 2 (Direct to USB Boot Target): Initiates a reboot targeting a specific bootable USB drive using efibootmgr to set a one-time Non-Volatile RAM (NVRAM) boot target (--bootnext).
• Option 3 (Standard System Reboot): Triggers a standard system reboot, allowing the operator to manually intercept the boot sequence and invoke the GRUB menu or motherboard boot selector.
• Option 4 (Extract 7z Archive to USB Root): Interactively scans for .7z archives in the execution directory, detects attached storage block devices (lsblk), automatically handles temporary mounting, and unpacks the archive directly onto the root filesystem of the target USB partition.
• Option 5 (Dynamic Shortcut & Lifecycle Management): Interactively deploys or purges custom FreeDesktop .desktop shortcuts within ~/Desktop and ~/.local/share/applications/ (Utilities). Automatically synchronizes local desktop databases via update-desktop-database, configures elevated execution privileges (sudo), and automatically cleans up the target installation directory (~/Reboot-to-UEFI) upon shortcut removal.

1. When prompted, select option 2 for EFI Boot Manager One-Time Boot

2. When prompted, enter the hex number corresponding to your USB device (e.g., 0002), Confirm your selection and press Enter. Wait a few seconds for the script to execute the boot override.

3. The system will now reboot immediately into the selected UEFI USB target.

---

Shell Execution & Deployment Matrix

The operational interface executes parameters natively directly within the UEFI Shell environment context. Manual mounting modifications or target drive block variable modifications are unnecessary.

Pass variable inputs straight to the master menu parser array:

Shell> menu [target_option_hex]

Script Execution Triggers

• Shell> menu 01 ➔ Initiates standard deployment profile using clean stock splash screens.
• Shell> menu 02 ➔ Initiates custom deployment profile parsing the high-density Bazzite splash assets.

---

Modded BIOS Kernel Engine Specifications

• Microcode Base: Structured directly atop community-vetted, high-performance modded v3.00 chipset layout BIOS distributions.
• Core Unlocks: Native register manipulation flags mapping the low-level silicon unlock hack discovered by @rw-r-r-0644. Toggles mapped directly inside: Advanced ➔ CPU Configuration.
• ACPI Kernel Overlays: Intercepts system startup routines via a custom, hardware-optimized iteration of the core unlock ACPI Fix DXE execution driver authored by @RescueMei. Runs asynchronously during post-initialization boot sequences.
• Hardware Recovery Path: Manual motherboard CMOS discharge events force a complete fallback reset of the silicon unlock registers. System reverts state to standard modded v3.00 architecture for seamless recovery if silicon stability drifts.

Technical Revisions (v1.x Series Framework Changes)

• Execution Pipeline Remapping: Replaced legacy Save Changes and Exit strings inside the internal setup matrix with a full hardware-level Save Changes and Reset string array. Forces automated DXE helper drivers to scan and refresh CPU configuration states upon environment exit.
• Boolean Logic Inversion: Inverted active data...

ASRock AMD BC-250-UEFI-v2.2 Firmware Menu Script

CAUTION: ONLY USE THIS ON BC250s THAT HAVE BEEN VERIFIED TO HAVE ALL 8 CPU CORES FUNCTIONAL VIA ORIGINAL METHOD FIRST: This firmware menu script, is bundled with BC250-DXE-SMU-Core-Unlock firmware with custom Logos.

Credit to the following developers for making this possible:

https://github.com/rw-r-r-0644

https://github.com/RescueMei/

essdee on discord

WARNING:
The release-0.1.0 firmware has 8 CPU cores enabled by default without an option to disable them. Please be 100% sure your BC-250 can handle this feature before upgrading. If you are certain, use release-0.1.0. If you want to play it safe, use release-0.2.0 instead; it includes a built-in toggle to disable the 8 CPU core function if your BC-250 cannot run with all 8 cores enabled. When disabling the 8 CPU core function in the BIOS, save and exit, then press the BC-250 reset button for the changes to take effect.

RELEASE NOTES:

1. release-0.1.0.zip
   1.1. WARNING: This release has all 8 cores unlocked by default with no option to disable them.

2. release-0.1.1.zip
   2.1. NEW: Includes 8 unlocked cores with a toggle option located under BIOS Advanced > Unlock CPU Cores. Please read the notes above to learn how to properly disable this feature.

3. release-0.1.2.zip
   3.1. Identical to release-0.1.1.zip, but includes updated and fixed boot logos.

4. release-0.1.3.zip
   4.1. Identical to release-0.1.2.zip, but includes additional and previously missing logos.

5. release-0.2.1.7z
   5.1. Fixed, the Exit option on the menu. Exit will bring you back into the so you can make you final changes before you fully exit to save.

6. release-0.2.2.7z
   6.1. New high quality Steam Logos. Hidden bonus Logos not listed on menu. Look below for details.

7. release-0.3.0.7z
   7.1 New MeiMeiDXE v3 Firmware with the following:
   Toggle on/off: Permanent 8 Cores unlocked
   Toggle on/off ACPI Fix
   ( New settings can be found under Advance > DXE Driver Configuration )

8. release-0.3.1.7z
   8.1 Fixed option 13

9. release-0.3.2.7z
   9.1 Your system will now shutdown after every successful Firmware Flash.

How to use:
Please note that the menu command runs directly under the Shell; there is no need to change the drive letter.
For example, entering Shell> menu 01 will automatically locate your chosen firmware.

Modded BIOS w/ CPU Core Unlock Toggle and ACPI Fix Included v3:

• Based on the popular modded v3.00 chipset menu BIOS

• A toggle to enable or disable the core unlock discovered by @rw-r-r-0644 has been added to the BIOS settings under Advanced -> CPU Configuration

• Includes a customized version of the CPU unlock /ACPI Fix DXE driver by @RescueMei which runs automatically on boot.

• A CMOS reset will disable the CPU unlock in case you run into trouble. This will function just like the regular modded v3.00 when the CPU unlock option is disabled.

Notable changes since v1:

• "Save Changes and Exit" under the "Save & Exit" menu in BIOS setup has been replaced with "Save Changes and Reset" to ensure that the DXE driver runs again after the CPU unlock is toggled.

• The internal values for the unlock toggle have been reversed. This means that clearing CMOS is no longer necessary if you're already using another v3.00 based BIOS. However, this also means that if you're upgrading from the last version, you will need to set the unlock toggle again after flashing.

• When the unlock is disabled in BIOS but still active, the DXE driver will automatically show a shutdown screen after exiting the BIOS to allow you to either turn off the board or press the reset button to finish disabling the unlock. The board will automatically shut down after 30 seconds. Enabling the CPU unlock does not require this step. Clearing CMOS is not necessary to disable the unlock, only a shutdown or reset.

• The help text for the unlock option in BIOS has been updated to add some additional information.

Hidden Bonus Logos in release-0.3.0->:

ATARI = menu R1
WEYLAND = menu R2

Full Changelog: v0.2.0...v0.3.0

How to use the Menu Options: menu + [option] Examples:

Shell> menu 01 ( for no Logo Option )

or

Shell>menu 02 (for Bazzite Logo, etc.)

ASRock AMD BC-250-UEFI-v2.2 Firmware Menu Script

CAUTION: ONLY USE THIS ON BC250s THAT HAVE BEEN VERIFIED TO HAVE ALL 8 CPU CORES FUNCTIONAL VIA ORIGINAL METHOD FIRST: This firmware menu script, is bundled with BC250-DXE-SMU-Core-Unlock firmware with custom Logos.

Credit to the following developers for making this possible:

https://github.com/rw-r-r-0644

https://github.com/RescueMei/

essdee on discord

NOTE:
A new function was added by essdee in release-0.2.0.7z. Within BIOS Advanced > CPU Configuration, you can now enable or disable the 8 CPU Core function. However, you currently need to perform a CMOS clear to disable it.

WARNING:
The release-0.1.0 firmware has 8 CPU cores enabled by default without an option to disable them. Please be 100% sure your BC-250 can handle this feature before upgrading. If you are certain, use release-0.1.0. If you want to play it safe, use release-0.2.0 instead; it includes a built-in toggle to disable the 8 CPU core function if your BC-250 cannot run with all 8 cores enabled. When disabling the 8 CPU core function in the BIOS, save and exit, then press the BC-250 reset button for the changes to take effect.

RELEASE NOTES:

1. release-0.1.0.zip
   1.1. WARNING: This release has all 8 cores unlocked by default with no option to disable them.

2. release-0.1.1.zip
   2.1. NEW: Includes 8 unlocked cores with a toggle option located under BIOS Advanced > Unlock CPU Cores. Please read the notes above to learn how to properly disable this feature.

3. release-0.1.2.zip
   3.1. Identical to release-0.1.1.zip, but includes updated and fixed boot logos.

4. release-0.1.3.zip
   4.1. Identical to release-0.1.2.zip, but includes additional and previously missing logos.

5. release-0.2.1.7z
   5.1. Fixed, the Exit option on the menu. Exit will bring you back into the so you can make you final changes before you fully exit to save.

6. release-0.2.2.7z
   6.1. New high quality Steam Logos. Hidden bonus Logos not listed on menu. Look below for details.

How to use:
Please note that the menu command runs directly under the Shell; there is no need to change the drive letter.
For example, entering Shell> menu 01 will automatically locate your chosen firmware.

Modded BIOS w/ CPU Core Unlock Toggle v2
• Based on the popular modded v3.00 chipset menu BIOS

• A toggle to enable or disable the core unlock discovered by @rw-r-r-0644 has been added to the BIOS settings under Advanced -> CPU Configuration

• Includes a customized version of the CPU unlock DXE driver by @RescueMei which runs automatically on boot.

• A CMOS reset will disable the CPU unlock in case you run into trouble. This will function just like the regular modded v3.00 when the CPU unlock option is disabled.

Notable changes since v1:
• "Save Changes and Exit" under the "Save & Exit" menu in BIOS setup has been replaced with "Save Changes and Reset" to ensure that the DXE driver runs again after the CPU unlock is toggled.

• The internal values for the unlock toggle have been reversed. This means that clearing CMOS is no longer necessary if you're already using another v3.00-based BIOS. However, this also means that if you're upgrading from the last version, you will need to set the unlock toggle again after flashing.

• When the unlock is disabled in BIOS but still active, the DXE driver will automatically show a shutdown screen after exiting the BIOS to allow you to either turn off the board or press the reset button to finish disabling the unlock. The board will automatically shut down after 30 seconds. Enabling the CPU unlock does not require this step. Clearing CMOS is not necessary to disable the unlock, only a shutdown or reset.

• The help text for the unlock option in BIOS has been updated to add some additional information.

Hidden Bonus Logos in release-0.2.2->:

ATARI = menu R1
WEYLAND = menu R2

ASRock AMD BC-250-UEFI-v2.2 Firmware Menu Script

CAUTION: ONLY USE THIS ON BC250s THAT HAVE BEEN VERIFIED TO HAVE ALL 8 CPU CORES FUNCTIONAL VIA ORIGINAL METHOD FIRST: This firmware menu script, is bundled with BC250-DXE-SMU-Core-Unlock firmware with custom Logos.

Credit to the following developers for making this possible:

https://github.com/rw-r-r-0644

https://github.com/RescueMei/

essdee on discord

NOTE:
A new function was added by essdee in release-0.1.1.zip. Within BIOS Advanced > CPU Configuration, you can now enable or disable the 8 CPU Core function. However, you currently need to perform a CMOS clear to disable it.

WARNING:
The release-0.1.0 firmware has 8 CPU cores enabled by default without an option to disable them. Please be 100% sure your BC-250 can handle this feature before upgrading. If you are certain, use release-0.1.0. If you want to play it safe, use release-0.1.1 instead; it includes a built-in toggle to disable the 8 CPU core function if your BC-250 cannot run with all 8 cores enabled. When disabling the 8 CPU core function in the BIOS, save and exit, then press the BC-250 reset button for the changes to take effect.

RELEASE NOTES:

1. release-0.1.0.zip
   1.1. WARNING: This release has all 8 cores unlocked by default with no option to disable them.

2. release-0.1.1.zip
   2.1. NEW: Includes 8 unlocked cores with a toggle option located under BIOS Advanced > Unlock CPU Cores. Please read the notes above to learn how to properly disable this feature.

3. release-0.1.2.zip
   3.1. Identical to release-0.1.1.zip, but includes updated and fixed boot logos.

4. release-0.1.3.zip
   4.1. Identical to release-0.1.2.zip, but includes additional and previously missing logos.

How to use:
Please note that the menu command runs directly under the Shell; there is no need to change the drive letter.
For example, entering Shell> menu 01 will automatically locate your chosen firmware.