amos ac3d3db9e0 Add 13 more Qwen-measured tasks from batches 26 and 27 (8 HARD, 5 MEDIUM)
Route D (real fixes in embedded open-source projects) keeps producing the
hard tasks: of 64 measured so far, 15 are HARD and 4 MEDIUM, mostly because
Qwen exhausts its context in the larger real workspaces. This adds
CANopen SRDO and ASCII timing, FreeRTOS DHCP, lwIP MQTT fragments, printf
extremal exponents, Zephyr packet buffers and heatshrink (HARD), plus
lwjson, RFM9x, SFUD and nanopb proto3 (MEDIUM).

From batch 27 (spec-dense implementation tasks) come one HARD and one
MEDIUM; that batch is winding down after 30 tasks gave 1 HARD and 3 MEDIUM.

Each task comes from the commit Qwen measured, its digest matches, and it
is still present at the batch branch head. Agent timeouts stay excluded:
a pyserial attempt timed out on Qwen's own blocking read yet graded PASS.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 16:29:21 +08:00

4.1 KiB
Raw Permalink Blame History

Storage API and bus contract

R01. Keep the public interfaces in sfud/inc/sfud.h and the supplied build configuration usable; a supported device with a working bus initializes with SFUD_SUCCESS. Device parameters may be configured by the port or discovered using JEDEC ID and the existing information tables.

R02. The storage integration owns the entire MX25L3206E array after successful initialization. With WP# inactive and status-register writes permitted, its existing software block protection must not prevent subsequent erase or program operations anywhere in the array. Other configured page-program devices retain their status-register protection policy during initialization.

R03. Bus failures while preparing a device for use are returned to the caller as a failure. In particular a failed write-enable or status-register write during required preparation must not be reported as successful initialization.

R04. sfud_read returns the requested bytes at the requested address after initialization, including after sfud_qspi_fast_read_enable is called with a maximum bus data width of 1, 2, or 4. Mode selection may be repeated on the same device. A device without an extended read-mode entry falls back to ordinary SPI reading.

R05. A NOR address is sent most significant byte first. At capacities through 16 MiB ordinary addresses use 24 bits; larger parts enter 4-byte address mode. Ordinary read is 03h, with an address of the active mode, or 13h with a 32-bit address on the large profiles. 04h is write-disable. The QSPI callback represents bus phases, not a different device command set.

R06. Dual-output, dual-I/O, quad-output, and quad-I/O reads use 3Bh, BBh, 6Bh, and EBh. Their dedicated 32-bit-address forms are 3Ch, BCh, 6Ch, and ECh. Instruction width is one line; output modes keep one address line, I/O modes use their data width for addresses. Output and dual-I/O modes use eight dummy cycles; quad-I/O uses six. Ordinary read uses no dummy cycles and one data line. No alternate-byte phase is used by this port.

R07. sfud_erase erases complete sectors intersecting its address range; sfud_write programs the requested bytes without erasing and preserves other bytes. sfud_erase_write performs those operations in order. Page programming must respect the 256-byte page boundary. Erased bytes are FFh and programming can change one bits to zero bits. Out-of-capacity reads and writes return SFUD_ERR_ADDR_OUT_OF_BOUND.

R08. The SST AAI profile remains usable with its existing volatile-status-write preparation and byte/word program support. Its nonvolatile block protection is writable using the supplied status-register API; MX25L3206E requires WREN (06h) before WRSR (01h). WEL is status bit 1, WIP is bit 0, and MX25L3206E block protection occupies bits 5:2. WRSR clears WEL when completed; software reset leaves nonvolatile block protection intact.

R09. The virtual port is synchronous: accepted erase, program, and register operations complete before the callback returns. It has no real-time requirement and does not constrain the number of polling, locking, or preparation transactions. It ignores program and erase operations aimed at protected regions, as the devices do. The observation suite may vary addresses, data, initial status, and fault injection without changing these rules.

The profiles are small (8 MiB Winbond), edge (16 MiB Winbond), large (32 MiB Winbond), mx (4 MiB MX25L3206E), sst (1 MiB SST), and port-configured ordinary-read parts normal32/normal64 (32/64 MiB). A zero-filled SFUD descriptor is populated by sfud_spi_port_init; the bus starts with the supplied nonvolatile status and array content. The configured ordinary-read parts have no extended-mode entry. These are controlled software devices, not claims of hardware certification.

References: SFUD public header comments; Macronix MX25L3206E datasheet PM1568 revision 1.5, Table 2 and command descriptions (1), (3), (4), (8)–(11); Winbond W25Q256FV revision F, sections 6.1.5, 8.1.2 and 8.2.10–8.2.18. This document paraphrases the relevant integration contract; source details are retained outside the candidate workspace.