[Open SoC Debug] GSoC project to improve soft-CPU debugging in LiteX + MiSoC
philipp.wagner at tum.de
Wed Apr 12 11:44:19 CEST 2017
It seems this approach works well with our all timelines, so let's go
for that and revisit later in the summer. Until then, OSD should be more
stabilized and ready to be adopted more widely (as I have a personal
need for that).
On 04/12/2017 09:48 AM, Tim Ansell wrote:
> Sadly we didn't get any bites for the project as part of GSoC. After
> chatting with Wallento, it sounds like we are going to wait until you
> guys have finished getting initial things going. After that he and I
> will work on getting this into LiteX / MiSoC this together.
> As I have been reasonable successful at getting QEmu emulation of our
> SoC going, that has satiated our immediate need for now. Even if it was
> a GSoC project it would have been ~3 months before we /might/ have
> gotten something useful.
> Tim 'mithro' Ansell
> On 21 March 2017 at 02:50, Philipp Wagner <philipp.wagner at tum.de
> <mailto:philipp.wagner at tum.de>> wrote:
> On 03/19/2017 09:57 PM, Tim Ansell wrote:
> Hi Philipp,
> At the moment I'm looking at the lowest effort way to add
> debugging to
> LiteX as kind of a "proof of concept" to demonstrate how it
> might work.
> I had previously gotten adv_debug_sys working with the or1k and was
> planning on getting that stuff working again before I came across
> At the moment I just want some Verilog code that I can wrap with
> and hook up to the or1k core's debug interface. It seems like
> OSD might
> not be ready for me to use that way yet?
> In this case, I'd not go with OpenSoCDebug for now, but use the or1k
> debug infrastructure with adv_debug_sys & Co. directly. It should be
> easy to revisit this decisions once you have a need for more
> sophisticated debug/trace infrastructure (and by then OSD should
> also have run-control debug working out of the box).
More information about the OpenSoCDebug