The development of an interface such as RSP can be incremental, where functionality is added in stages. A number of packets are not supported. In a few cases this is because the functionality is meaningless for the current target, but in the majority of cases, the functionality can be supported as the server is developed further in the future.
The unsupported packets are:
A. Specifying the arguments for a program is
hard on "bare metal". It requires determining whether the code has
yet entered its main ()
function and
if not patching in pointers to the new arguments.
C and S. Continuing or stepping with a signal is currently not supported. Implementing this would require insertion of an exception, which is not difficult, so this will be an enhancement for the near future.
F. File I/O is not meaningful with a bare metal target, where a file-system may not be present.
i and I. The target is an architectural simulator, executing one instruction at a time. So cycle accurate stepping is not available.
t. The meaning (or use) of the search command is not clear, so this packet is not currently implemented.