diff options
| author | Pavel Labath <labath@google.com> | 2018-02-27 22:14:33 +0000 |
|---|---|---|
| committer | Pavel Labath <labath@google.com> | 2018-02-27 22:14:33 +0000 |
| commit | 029fb693722ee87cf0aebc75ba823d4ed020215a (patch) | |
| tree | f6939628eacb5ebb1c58b6f97662c6f3521625d2 /lldb/packages/Python/lldbsuite/test/expression_command/fixits/main.cpp | |
| parent | 3acdc6773444b0dea84a69e99024e07ebabc0c98 (diff) | |
| download | bcm5719-llvm-029fb693722ee87cf0aebc75ba823d4ed020215a.tar.gz bcm5719-llvm-029fb693722ee87cf0aebc75ba823d4ed020215a.zip | |
[lldb] Use vFlash commands when writing to target's flash memory regions
Summary:
When writing an object file over gdb-remote, use the vFlashErase, vFlashWrite, and vFlashDone commands if the write address is in a flash memory region. A bare metal target may have this kind of setup.
- Update ObjectFileELF to set load addresses using physical addresses. A typical case may be a data section with a physical address in ROM and a virtual address in RAM, which should be loaded to the ROM address.
- Add support for querying the target's qXfer:memory-map, which contains information about flash memory regions, leveraging MemoryRegionInfo data structures with minor modifications
- Update ProcessGDBRemote to use vFlash commands in DoWriteMemory when the target address is in a flash region
Original discussion at http://lists.llvm.org/pipermail/lldb-dev/2018-January/013093.html
Reviewers: clayborg, labath
Reviewed By: labath
Subscribers: arichardson, emaste, mgorny, lldb-commits
Differential Revision: https://reviews.llvm.org/D42145
Patch by Owen Shaw <llvm@owenpshaw.net>
llvm-svn: 326261
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/fixits/main.cpp')
0 files changed, 0 insertions, 0 deletions
