For P2, when Debug is enabled, the Info View's hex display shows the memory image with the Debugger prepended, as it is upon download; however, this is not how the memory appears upon start of user code.
Upon execution, the Debugger is relocated to the end of Hub memory and the Spin2 Interpreter (if included) and the user's code/data are relocated to the start of Hub memory (as they'd be if Debug were disabled), then Cog0 is restarted with the user's code.
To address this, the Hex display should default to the relocated view to maintain the purpose as it was originally intended. Additionally, as a potential enhancement, a way to toggle between the user-start vs. the download-image views could be implemented and the latter could also include the flash loader.
For P2, when Debug is enabled, the Info View's hex display shows the memory image with the Debugger prepended, as it is upon download; however, this is not how the memory appears upon start of user code.
Upon execution, the Debugger is relocated to the end of Hub memory and the Spin2 Interpreter (if included) and the user's code/data are relocated to the start of Hub memory (as they'd be if Debug were disabled), then Cog0 is restarted with the user's code.
To address this, the Hex display should default to the relocated view to maintain the purpose as it was originally intended. Additionally, as a potential enhancement, a way to toggle between the user-start vs. the download-image views could be implemented and the latter could also include the flash loader.