Firmware Updates
Please find all available firmware updates below.
If your product is not listed there is no firmware update available
Solid-State Drives
Firmware updates will enable your solid-state drive to deliver the best performance.
WARNING: The firmware update process is done entirely at your own risk. Before initiating the update process be sure to backup or make copies of all important files. If the firmware process is interrupted your solid-state drive may not function properly.
Firmware 1711 - Important Notice:
If your Crucial M225 Solid-State Drive has firmware 1711 you must first revert back to the 1571 firmware prior to updating to the new 1819 version. Please download the 1571 firmware and follow these instructions.
M225 Series
| Version |
Compatible Models |
Description |
Boot from CD Option |
Boot from USB Option |
| 1819 |
64GB M225 SSD Part #:CT64M225 |
Release Notes |
guide — firmware |
guide — firmware |
| 1819 |
128GB M225 SSD Part #:CT128M225 |
Release Notes |
guide — firmware |
guide — firmware |
| 1819 |
256GB M225 SSD Part #:CT256M225 |
Release Notes |
guide — firmware |
guide — firmware |
Release Date: 10/22/2009
Change Log:
- Updater runs out of DOS instead of Windows
1.1 Added ATA8 ACS2 TRIM Support
1.2 SATA Rx SSC is turned off by default, Now Rx and Tx SSC both off
1.3 IDENTIFY word 69 bit 14 is cleared (Non deterministic trim)
1.4 IDENTIFY word 60-61 are changed (User addressable logical sectors for LBA28)
1.5 FPDMA error return code was not adequate
1.6 SMART related changes were made (BBM error log was removed)
1.7 SATA error handling code was enhanced
1.8 Added paired page calculation for Micron 34nm MLC NAND
- Bug Fix: Fixed a bug in error handling in Set Multiple mode command
- Bug Fix: Fixed a bug that caused 1.5Gbps diagnostic failure
- Bug Fix: SMART related bugs were fixed
- Bug Fix: Current ATA security state was not reflected in IDENTIFY information
- Bug Fix: Performance boost routine reused the recently used block and it did harm to wear leveling.
- Bug Fix: During SATA protocol, abrupt OOB made Controller hang
- Bug Fix: In bad block management, wrong number of free blocks is used and it led to timeout and hang
- Bug Fix: After STANDBY_IMMEDIATE, most host controllers wait for OOB reply for 100ms. Sometimes Indilinx Barefoot firmware couldn’t answer to COMRESET because FTL initialization took longer time. This bug caused Windows Sleep/Hibernate test failure.
- Bug Fix: Various read fail scenario were found with FTL simulation
- Barefoot ECO chip support code was added
- More NAND ICs supported
|
| Crucial Wiper tool for user-initiated Garbage Collection. (For use with Windows XP and Vista only.) |
download |