[Open SoC Debug] GSoC Proposal | To improve soft-CPU debugging in LiteX + MiSoC
philipp.wagner at tum.de
Mon Mar 26 14:09:47 CEST 2018
Please keep all project-related discussion on the public mailing list so
that others can profit from the answers as well. Thank you!
On 03/26/2018 01:50 PM, SHIVAM AGGARWAL wrote:
> I have a few doubts regarding the implementation of CDM module.
> As far as I understand, CDM is responsible for translating requests made
> by OSD interconnect to CPU core.
Requests are not made by the interconnect, but by the software on the host.
> These request are in OSD specific
> registers packets and need to be transferred to CPU core such that it
> can understand the request and respond accordingly. Similarly, all
> response actions and events triggered by CPU core will be translated
> back into OSD specification
You cannot translate something into a specification. Responses are
packaged into Debug Interconnect packets, i.e. the "data format" used
for all communication in OSD.
> and transferred back to the host. So, CDM
> module is basically a memory mapped interface between CPU core and OSD
> interconnect. Is that correct?
The wording is rather unusual, but not completely wrong.
> I mapped debug registers given in the OR1K CPU VERILOG module into OSD
> specific registers. But, I believe that's not what I was supposed to do.
It's expected to map the debug registers of the CPU. But what you did is
one layer below that, you mapped individual ports in the Verilog
> Please help a bit for this part. I looked at the documentation of debug
> packets in OSD. Basically, OSD packets have following register types:
That's not a "register type" of a packet (there is no such thing), that
are fields inside a Debug Interconnect Packet. These fields describe the
general structure of a communication packet. The semantics come from the
higher layer, i.e. how these fields are used. That is what is described
What we're looking for is a mapping between CPU debug registers, as
specified in the OR1k ISA Chapter 11 (Debug Unit) to registers in the
to-be-developed OSD Core Debug Module (CDM).
For example, the register DVR0 of an OR1k CPU (Debug Value Register 0,
could be a breakpoint or watchpoint address) could be mapped to register
address 0x300 of the CDM module. When you write (from the host software)
the register 0x300 of the CDM module, this register write is forwarded
to the CPU's DVR0 register over the debug bus (the one with the du_*
signal names in the mor1kx implementation).
Reads happen in the same way. All of that discussion doesn't touch the
internal structure of the Debug Interconnect Packet that you showed,
it's semantics on top of that.
> Here, each register is 16 bits long. So, according to the documentation.
> So, debug registers in CPU core need to be translated into these
> specifications, right?
What do you mean by "here"?
> Now, you mentioned in the last mail, regarding osdacceess register
There is no module with that name.
> VERILOG module. I tried looking for the documentation of the module but
> couldn't find a lot of details. I mentioned some points in the proposal
> regarding the module. Please throw some more light on this part as how
> it will be used.
More information about the OpenSoCDebug