Performed cleanup and reorganization of flash-related code. The following
items have been changed in the libbladeRF API:
- Fixed "sector" vs "erase block" misnomer. While the SPI flash on the
bladeRF has "sectors", these are not the units actually being used
in the firmware to perform erase operations. As such, the API and
underlying code has been updated to perform erases in terms of the
"erase block" unit.
- Renamed bladerf_program_flash_unaligned() to
bladerf_write_flash_unaligned() for consistency.
- Flash-related API calls now only return 0 on success, or a
BLADERF_ERR_* value upon failure. They no longer return the number of
bytes read/written/erased. This is intended to be more consistent
with the rest of the API. The requested size of the read/erase/write
is guaranteed to be performed at requested size, so returning a byte
count merely complicates the API "contract" and offers no usefulness.
- To erase the FPGA stored in SPI flash for autoloading, a new
function, bladerf_erase_stored_fpga(), has been introduced. This
replaces the use of bladerf_flash_fpga(dev, "X").
Internally, the following changes have been made:
- All flash-related code has been moved to flash.c (e.g., from bladerf.c).
This is part of the ongoing effort to move logic out of bladerf.c and
into the associated module, with the intent of the bladerf.c
"API top-level" of only acquiring a per-device lock (in the future)
and delegate actions to the module implementations.
- Backend flash operations are now in units of erase blocks and pages,
to alleviate backend code needing to deal with conversions.