Memory access GDB extension
========================

This extension implements read/write GDB commands for reading and writing from memory. This extension
is a wrapper for GDB monitor read/write memory command, it uses parameters: context, size, count and memory space. 


 
The following commands are currently implemented in commands.py
mem_read, mem_write and mem_spaces.

Usage examples:
- mem_read [context] address [access_size] [memory_space] [count]
	o context is optional and has following form :ccs:S32G2XX:Cortex-M7#0(string). If argument is omitted then current project context is retrieved and used as default.
	o address is mandatory and indicates start address where reading should begin. Address should be in form of hexadecimal string representation(ex.: 0x34000000).
	o access_size is optional and is meant to indicate width of accessing memory and is represented in bytes(integer number). If argument is omitted, read is done in 4 bytes that is 32bit. This default is conditioned by legacy support for some devices which don’t support 1byte read.
	o memory_space is optional and indicates in which space of current context should address be read. Input is string and can be physical/virtual. Default value is virtual.
	o count is optional and indicates how many times the memory will be read. Default(integer number) is 1.

- mem_write [context] address [access_size] [memory_space] data
	o context, address, access_size, memory_space are the same as above with same defaults.
	o data – is mandatory and represents data to be written. Current support is only for 1 value and should be a string representation of a hexadecimal(ex: 0x12345678)

A few words about output:
- mem_read – will output a string in hex representation(without 0x) of (access_size * 2hex_digit) * count. For example: mem_read 0x34000000 4 physical 2 will output: 12345678abcdef09. In case of error, same mechanism is used as for core registers: application is closed and an error is thrown.
- mem_write – current support is for only 1 value at a time, no arrays of file. For future this functionality can be expended. No return in case of success, in case of fail application is closed and an error is thrown.