Indilinx. Self repairing SSD firmware



Yes it does. Looks like we can Raid 0 now without worrying about Trim support

Perhaps the biggest take-home on all of this is the fact that sequential performance was restored to like-new conditions, on it's own, and completely independent of any partition being present on the drive. Other controllers, like those from Samsung, have resorted to a so called 'auto-TRIM' feature, which is only compatible with NTFS partitions at present, and can not work properly when those units are behind a RAID.
 
The new OCZ Vertex v1.4 firmware was released tonight, it's based on the latest Indilinx firmware but the OCZ's own additions. It includes automatic Garbage collection and TRIM support on Win7.

Just downloaded and installed, works a treat. Leave your drive for 10mins and it self-cleans itself restoring full performance.


But can you use the OCZ Vertex v1.4 firmware with the Crucial or Supertalent SSD?

I know you can flash the lastest Indilinx firmware 1711, but the OCZ firmware also has the garbage collector.
 
You can to the G.Skill Falcon, it's been done. But you will lose your warranty if you do it.

The G. Skill Falcon uses the exact same PCB as the Vertex. Both are the same reference board design from Indilinx. So its no surprise that the OCZ firmware flashes into the G.Skill.

The Supertalent me and the Corsair also use the exact same PCB, but its different than the Vertex. However its components are the same, eg Arm based controller, Elpida 64MB cache and the same Samsung Nand flash.

So IMO, the ocz firmware should also flash into the supertalent/corsair.

I was just hoping someone else would try it before I did:)
 
Thanks for the pictures. You can clearly see the Vertex and the falcon are the same. So are the ST and the Crucial.
I posted on the super talent web forum if anyone has tried to flash the vertex firmware. No reply as yet.

The big square chip is an ARM 7 microcontroller, the cpu of the system. Its a ARM7TDMI which is the same chip as the Nintendo DS and also many Samsung and Nokia mobile phones.

When you flash in firmware, you are just copying some code into a reserved part of Nand flash which is called when the system boots.

Normally this code would be encrypted and decrypted before running. Its entirely possible that a "device id" is also part of the reserved space (written at production). The firmware code would first check this "device id" and abort if it doesnt match the manufacturers code (hidden in the encrypted firmware). It is then entirely possible that on abort another reserved word could be written which means "lock out". In which case, if lock_out==true then you have a brick and further flashing wont work.

NOW the ST and Crucial are both using the exact same firmware, which is ARM 7 code provided by Indilinx. Neither of them have been bothered to tweak the base code and provide it from Indilinx, as is.

However the Vertex code is bespoke. Its based on the ARM7 code provided by Indilinx with an additional "in house" bit of code. In which case they could have implemented the above.
 
Last edited:
Back
Top Bottom