Flash footprint, in bytes, of one image of chip_type on board.
This is the v2 slot size — 2^num_addr_pins * word_bytes — which is what the
ROM Slot Builder's flash-usage tally needs per slot, and the number
docs/COMPATIBILITY.md's "Image size" column tabulates. It can far exceed the
ROM's own capacity, so it is not the same as ChipType::size_bytes().
Computed via onerom_gen::compat::check_chip_set_on_board for a single-chip
slot, which errors for an unsupported chip/board combination — surfaced here
as a clean JS error.
version is parsed and validated but unused in the maths: the v2 footprint is
determined by board + chip alone. It is kept in the signature for API symmetry
with the other builder bindings and to leave room for future version-dependent
sizing.
Flash footprint, in bytes, of one image of
chip_typeonboard.This is the v2 slot size —
2^num_addr_pins * word_bytes— which is what the ROM Slot Builder's flash-usage tally needs per slot, and the numberdocs/COMPATIBILITY.md's "Image size" column tabulates. It can far exceed the ROM's own capacity, so it is not the same asChipType::size_bytes().Computed via
onerom_gen::compat::check_chip_set_on_boardfor a single-chip slot, which errors for an unsupported chip/board combination — surfaced here as a clean JS error.versionis parsed and validated but unused in the maths: the v2 footprint is determined by board + chip alone. It is kept in the signature for API symmetry with the other builder bindings and to leave room for future version-dependent sizing.