Skip to content

Commit 39a5f0d

Browse files
committed
docs: blank-check only works reliably for code flash
1 parent 67de9fd commit 39a5f0d

File tree

2 files changed

+6
-1
lines changed

2 files changed

+6
-1
lines changed

src/main.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ usage(int status) {
3535
" write <file>[:<addr>] ... Write file(s) to flash memory\n"
3636
" verify <file> Verify flash memory against file\n"
3737
" erase Erase flash sectors\n"
38-
" blank-check Check if flash region is erased (all 0xFF)\n"
38+
" blank-check Check if flash region is erased (code flash only)\n"
3939
" crc Calculate CRC-32 of flash region\n"
4040
" dlm Show Device Lifecycle Management state\n"
4141
" dlm-transit <state> Transition DLM state (ssd/nsecsd/dpl/lck_dbg/lck_boot)\n"

src/radfu.h

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,11 @@ int ra_verify(
7474
/*
7575
* Check if flash memory region is blank (all 0xFF)
7676
* Reports first non-blank byte if found
77+
*
78+
* NOTE: This only works reliably for code flash. Data flash returns
79+
* undefined values after erase (not 0xFF) per Renesas RA hardware spec.
80+
* The bootloader protocol does not expose the hardware blank-check command.
81+
*
7782
* Returns: 0 on success (blank), -1 on error or non-blank
7883
*/
7984
int ra_blank_check(ra_device_t *dev, uint32_t start, uint32_t size);

0 commit comments

Comments
 (0)