Commit 99939c3c authored by David Brownell's avatar David Brownell
Browse files

NOR: stellaris message tweaks



Give a more accurate failure message when trying to unprotect; don't
complain about pages being write protected, just say that unprotect is
not supported by the hardware ... referencing the new "recover" command,
which is the way to achieve that.

Likewise, when trying to protect, talk about "pages" (matching hardware
doc) not "sectors" (an concept that's alien to these chips).

Also make the helptext for the "recover" command mention that it
also erases the device.
Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
parent 2119c0a7
......@@ -693,8 +693,8 @@ static int stellaris_protect(struct flash_bank *bank, int set, int first, int la
if (!set)
{
LOG_ERROR("Can't unprotect write-protected pages.");
/* except by the "recover locked device" procedure ... */
LOG_ERROR("Hardware doesn't suppport page-level unprotect. "
"Try the 'recover' command.");
return ERROR_INVALID_ARGUMENTS;
}
......@@ -706,7 +706,7 @@ static int stellaris_protect(struct flash_bank *bank, int set, int first, int la
|| (last < first) || !(last & 1)
|| (last >= 2 * stellaris_info->num_lockbits))
{
LOG_ERROR("Can't protect unaligned or out-of-range sectors.");
LOG_ERROR("Can't protect unaligned or out-of-range pages.");
return ERROR_FLASH_SECTOR_INVALID;
}
......@@ -1240,7 +1240,7 @@ static const struct command_registration stellaris_exec_command_handlers[] = {
.handler = stellaris_handle_recover_command,
.mode = COMMAND_EXEC,
.usage = "bank_id",
.help = "recover locked device",
.help = "recover (and erase) locked device",
},
COMMAND_REGISTRATION_DONE
};
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment