Production Mode

Production mode

For flashing the same image onto many chips: pick the image once, then every batch runs with one key press.

Starting

1. Select the target: ALL to flash all sockets per batch, or a single socket. With ALL, a batch is a broadcast, or one-by-one if that option is on.
2. Tick production mode and pick the production image.
3. Confirm. From now on, batches run without asking again.

The write button becomes ▶ run batch ⏎, and the footer shows the image, the batch number and the pass/fail counts.

Running batches

1. Insert the chips.
2. Press Enter (or ▶ run batch). The batch erases, writes and verifies the image with your current settings.
3. When it finishes, the log says Batch #n: … · swap chips. Swap the chips and repeat.

Rules in production mode:

• The image must be exactly the chip size. There's no pad/truncate prompt mid-production; prepare the image beforehand.
• With ALL as a broadcast, all chips must be the same type.
• With ALL and one-by-one, a batch writes and verifies each socket in turn, as one job. The chips may differ: a socket whose chip doesn't fit the image fails on its own, counts as failed, and the batch goes on with the others. The batch result then says, for example, 1/3 socket(s) failed (CS1).
• Jobs aren't queued in production mode, so one batch runs at a time.
• Images dropped on the window are ignored; the batch image stays the one you picked.
• From the second batch on, the status line shows how long the batch usually takes (~35s left).

Untick production mode to stop. The log then shows the totals (n batch(es), ✓ ok ✕ failed).

Flash log

Every write and verify, in production and in normal use, is appended to a CSV file:

• Linux/macOS: ~/.local/share/hydra-flasher/flash_log.csv
• Windows: %APPDATA%\HydraFlasher\flash_log.csv

flash log ▸ opens the flash history page: the newest entries as a table (time, socket with its name, chip, operation, image, ✓ pass / ✕ fail, how long it took; production rows show their batch as write #3). The newest 1000 are shown.

• show: all, failures or today. The line next to it counts the entries and failures.
• export CSV… saves a copy of the whole file anywhere, for example to hand over with a batch.
• open folder opens the data folder with the file and its archives.
• clear… starts an empty log. The old entries aren't deleted: the file is renamed to flash_log-<date>.csv in the same folder.
• ← back or Esc returns to the main view.

The file itself has one row per chip and operation:

Column	Content
time	Date and time
mode	manual or production
batch	Production batch number
socket	CS0 to CS3
jedec	JEDEC ID of the chip
unique_id	The chip's unique ID (Winbond chips), for tracing a single chip
chip	flashprog chip name
operation	write or verify
image	Image file name (one starting with =, +, - or @ gets a leading ', so a spreadsheet doesn't run it as a formula)
image_crc32	CRC32 of the image, to prove which image a chip got
result	pass or fail
seconds	How long it took