KRATOS REV6 BIG SCREEN — SINGLE-FILE FACTORY TEST
Version: 0.6.5-kratos-v6b-test / factory packaging revision 1

PURPOSE
One combined BIN for manufacturer testing on ONE matching Rev6 big-screen unit.
It contains the bootloader, partition table, application, dashboard and blank
factory state. It is not a universal image and not approved for batch production.
Do not put this image into the existing Kratos Rev6/Rev7 website installer or a
miner's application-only OTA upload field.

EXACT HARDWARE
VastBTC yyslupingB++, ESP32-S3, actual 32 MiB flash, 480x320 display,
4x BM1370, positive legacy Rev6 regulator identification.
NOT ordinary 16 MiB Rev6, Rev7, the 320x170 model, Hammer or Nexus.
Never force a flash past a controller, flash-size or security mismatch.

ONE FILE / ONE ADDRESS
File: kratos-rev6-big-screen-0.6.5-factory-test.bin
Length: 33,554,432 bytes (32 MiB)
Write address: 0x0
SPI mode: DIO     SPI frequency: 40 MHz     Flash size: 32 MB

WARNING: FULL FACTORY RESET
This writes the whole 32 MiB address space, including bootloader and partitions.
It clears Wi-Fi, pool/payout, tuning, authenticator and custom dashboard/artwork
settings, old OTA slots and crash data. It does not preserve a previous install.
On a configured unit, offer a private recovery copy before proceeding. A backup
contains secrets and must not be sent to us or included in production images.
Do not clone a configured miner's full flash to other units.

MANUFACTURER FLASHING TOOLS
A programmer that supports ESP32-S3 and 32 MiB can use the BIN at 0x0. This is
the combined-file route; choose no additional app/web/partition files.
Use Espressif esptool v4.13.0 for the command sequence below. These are commands
for the human operator, not commands that were executed on a miner by Kratos.
Replace PORT with the actual COM port or /dev/cu.* device, and run from the folder
containing the BIN. Use a reliable USB data cable and the board's required power.
Enter the manufacturer's documented USB download mode; do not guess button pins.

1. Install the pinned utility in a virtual environment:
   python -m pip install esptool==4.13.0

2. Inspect the actual unit before any write:
   python -m esptool --chip esp32s3 --port PORT --after no_reset chip_id
   python -m esptool --chip esp32s3 --port PORT --after no_reset flash_id
   python -m esptool --chip esp32s3 --port PORT --after no_reset get_security_info

   Require ESP32-S3, detected 32 MB flash, Secure Boot disabled and flash
   encryption disabled. If identity/security cannot be established, stop and use
   the manufacturer's supported provisioning process. Do not use --force or burn
   eFuses. Physically confirm PCB/regulator/display and power supply separately.

3. Verify SHA256SUMS against this exact downloaded BIN. Then, only after the
   operator accepts the factory reset, write the single combined image:
   python -m esptool --chip esp32s3 --port PORT --baud 460800 --after no_reset write_flash --flash_mode dio --flash_freq 40m --flash_size 32MB 0x0 kratos-rev6-big-screen-0.6.5-factory-test.bin

4. Verify the complete programmed image before restarting:
   python -m esptool --chip esp32s3 --port PORT --baud 460800 --after no_reset verify_flash 0x0 kratos-rev6-big-screen-0.6.5-factory-test.bin

   Do not restart on a write/readback failure. Keep the exact vendor big-screen
   recovery image and its documented recovery procedure available.
   If verification passes, close the serial tool, leave download mode and restart
   the unit using its normal manufacturer procedure.

FIRST BOOT / 6 TH/s TARGET
This combined file reuses the existing application unchanged. Its blank-state
clock default is 600 MHz and its steady-state core-voltage default is 1150 mV
(the existing startup sequence initially requests at least 1200 mV). It is NOT a
pre-tuned 6 TH/s production preset. The 800 MHz ceiling includes the usual
approximately 750 MHz / 6 TH/s range, but the manufacturer must validate voltage,
power, cooling and stable shares on the actual board before selecting that tune.
No 1000 MHz / 8 TH/s profile is added.

The fresh setup access point is named Nerdaxe_XXXX, with a per-unit suffix.
The code starts a local setup web server; use the IP shown by the unit/AP network.
The stock example Wi-Fi fallback is not a customer credential. Configure actual
Wi-Fi and payout details locally. Payout is blank; mining is not started until
network and a payout/pool configuration have been supplied. Each unit must be
configured separately; no owner wallet, Wi-Fi credentials or private key is baked in.

BEFORE REPEATING ON A BATCH
Have the manufacturer report: PCB/regulator/flash identification; successful
write/readback and cold boot; full 480x320 orientation/colours/backlight; local
dashboard version 0.6.5-kratos-v6b-test; real temperatures/fans; advancing accepted
shares; measured power and stability at the intended 6 TH/s tune; reboot/settings
persistence; and recovery to the exact matching vendor image. A build or readback
pass alone is not physical mining, thermal or recovery validation.

The redesigned Opus dashboard/LCD work is separate and is NOT in this 0.6.5 file.
Do not mix an app from one version with another version's dashboard.

Source, hashes and current status:
https://kratos.mineshop.eu/firmware/rev6-big-screen.html
