Memory window context confusion!

[TjBordelon]

I'm using the XS1-G... and when using the memory window, it isn't clear to me what tile's ram is being displayed.

My understanding is that each tile has it's own 64k memory space. So consequently when showing a dump of a particular address, the context of which tile is very important.

Intuitively, I try to click in the debug window to select different cores but the memory window seemingly shows the dump of the same tile's ram.

1) How do I know what tile's ram is being shown in the memory window?

2) How do I change context from one tile's ram to another?

Thanks.

[TjBordelon]

Ticket was opened on this. Apparently it's a known issue/bug.

WOW. How are you guys debugging? I can't live without my memory window.

[edschulz]

One way is by using command-line xgdb. After connect, run, Ctrl-C suspend, "tile 3" (for example) gets you to the Tile 3 context, and you can print whatever you want.

[kris]

The memory window currently shows the content of the tile on which we are
suspended, i.e. the tile on which the breakpoint has been hit (see the debug
view for this info). Also, there is no way at present of switching tile whilst suspended.
Likewise, when a memory monitor is created, the global symbols available are those
that are relevant for the tile on which we are suspended.

We are currently looking into updating this to make it a little more usable.
Hope this helps,
Cheers,
Kris.