doryan/BloomPatched
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

WCH-Link erase command doesn't erase the whole chip, as initially thought. It only erases the program memory segment.

Browse Source 
The boot segment appears to be left untouched.
This commit is contained in:
Nav
2024-12-13 22:48:20 +00:00
parent a971e92a58
commit 00919e4057
6 changed files with 33 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
src/DebugServer/Gdb/RiscVGdb/CommandPackets/FlashErase.cpp
View File

@@ -45,14 +45,27 @@ namespace DebugServer::Gdb::RiscVGdb::CommandPackets
Logger::info("Handling FlashErase packet");
try {
const auto segmentDescriptorOpt = gdbTargetDescriptor.systemAddressSpaceDescriptor.getContainingMemorySegmentDescriptor(
this->startAddress
);
if (!segmentDescriptorOpt.has_value()) {
throw Exception{"Invalid command - no containing memory segment found for the given start address"};
}
const auto& segmentDescriptor = segmentDescriptorOpt->get();
if (!segmentDescriptor.programmingModeAccess.writeable) {
throw Exception{"Memory segment (\"" + segmentDescriptor.name + "\") not writable in programming mode"};
}
Logger::warning("Erasing \"" + segmentDescriptor.name + "\" segment, in preparation for programming");
targetControllerService.enableProgrammingMode();
Logger::warning("Erasing program memory, in preparation for programming");
// We don't erase a specific address range - we just erase the entire program memory.
// We don't erase a specific address range - we just erase the entire segment
targetControllerService.eraseMemory(
gdbTargetDescriptor.systemAddressSpaceDescriptor,
gdbTargetDescriptor.programMemorySegmentDescriptor
segmentDescriptor
);
debugSession.connection.writePacket(OkResponsePacket{});