From 0eaa2622268c1a565a060c9d704087022588bbb3 Mon Sep 17 00:00:00 2001 From: Paul Gardner-Stephen Date: Wed, 17 Apr 2019 05:18:09 +0930 Subject: [PATCH] add note about using VICE's remote monitor to capture instruction streams --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 5f3acba8..b3f48fa9 100644 --- a/README.md +++ b/README.md @@ -43,3 +43,8 @@ at the location. A good way to cover this for many situations would be to gener running, and capturing exactly which entry points are called from where. That is, to generate a call-graph that is the combination of many program runs, so that we can build up a map of what is required in terms of correct function of the system. This then defines the interface exactly from the perspective of interoperability. + +We can capture this information using x64 -remotemonitor, and then making a program that connects to port 6510 +and uses reset 0 to reset the CPU, and then types step and sends carriage returns repeatedly, and logs the +instruction stream. If a program is loaded and run, then this will capture the instruction stream, and allow us +to generate this call graph.