Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamWhich product type do i select, Test rack or End product after running the FCMCPTool
• Choose “End product”.
• Reserve “Test rack” only for factory test stations, engineering validation, or batch-qualification rigs.
What the menu really does
• FCMCPTool (FirstChip / FC-MPTool / FCMCPTool) writes a small parameter block into the controller’s OTP or external SPI flash.
• That block contains a flag (“ProductType”) that tells the firmware how it should enumerate and which self-tests to execute when the stick is powered.
• Two predefined values exist:
– 0 = End-product mode (normal USB Mass-Storage).
– 1 = Test-rack mode (engineering / production diagnostics).
Behaviour of each mode
End product
• Enumerates as a standard USB Mass-Storage Class (MSC) device with the VID/PID you define in the .ini/.cfg file.
• Runs only the minimal power-on self-test (bad-block scan, ECC tables) so start-up time is short.
• Exposes full capacity and the normal SCSI command set; Windows, Linux, macOS all mount it immediately.
• Ready for consumer use or for shipment to a customer.
Test rack
• Enumerates either as a vendor-specific device (sometimes HID 058F:6387) or as MSC with the “FC TEST” string.
• Runs extended pattern tests, program/erase cycle counters, and optionally keeps the LUN write-locked until the test sequence returns “PASS”.
• Often shows 0 MB capacity to the host OS; the real LBA map is hidden.
• Intended for conveyor-belt or ATE (Automatic Test Equipment) stations on the production line, not for field devices.
Consequences of a wrong choice
• If you flash “Test rack” and then plug the stick into a normal PC it will either (a) appear empty/0 MB, (b) ask for drivers, or (c) report vendor test commands only.
• You would have to repeat the whole MP run with “End product” to recover it. No permanent damage, just wasted time.
Why “End product” fits the scenario described by the user (VID FFFF / PID 1201 / 0 GB)
• The symptoms come from a corrupt parameter block or mismatched firmware; your goal is to restore a consumer USB drive.
• You are not running a mass-production line nor collecting burn-in statistics, so test-rack diagnostics offer no benefit.
• Therefore the correct workflow is:
• Most current FirstChip controllers (FC1179, FC1188, FC8308, FC1710) keep the same two-mode scheme.
• Some 2023/2024 MPTool builds added a third flag “ATS” (Automated Test Station) but it is still treated internally as Test-rack with an extended log format (CSV+JSON).
• Industry trend: USB flash manufacturers increasingly log production data in hidden SysInfo pages; selecting End-product truncates this log to 64 bytes, while Test-rack retains full 4 kB for factory analytics.
• Analogy: Think of “End product” as the release build of firmware; “Test rack” is the debug build with extra asserts, log output and an attached debugger.
• Technical detail: ProductType is written at offset 0x1E in the FC parameter block. Value 0x55AA → normal, 0xAA55 → rack.
• Flashing drives in Test-rack mode and selling them may violate CE/FCC self-certification because the device enumerates with vendor-specific commands that were not part of the compliance test.
• Altering VID/PID pairs to impersonate another vendor is a trademark issue—use only your own or the default FirstChip IDs for personal recovery work.
• Data safety: MPTools perform a full NAND-erase; remind end-users that all previous data is destroyed.
Implementation checklist for recovery
Common pitfalls
• Wrong voltage option (1.8 V vs 3.3 V) → controller overheats.
• Mismatched flash map → PASS but tiny capacity; re-select right “Flash IC Type”.
• If the controller or NAND is physically damaged, even End-product mode will not revive the drive.
• Some very old FirstChip firmware (<2014) names the modes “Mass Storage” vs “Engineering”. They map 1:1 to End-product vs Test-rack.
• Consult the latest “FC_MassProductionTool_UsersGuide_v2.15.pdf” (reverse-translated from Chinese) for new parameters like QC_TimeOut and ATS_LogSize.
• Follow threads on flashboot.ru and elektroda.com for chip-specific INI files.
• Explore open-source projects (e.g., FCMassPy) that parse the parameter block to automate large-batch recovery.
Select End product in FCMCPTool when your goal is to repair or prepare a USB flash drive for ordinary use. “Test rack” is strictly for production-line diagnostics; using it on a consumer stick will leave the drive in a special factory test state.
