OpenCores

OpenCores

debug unit features/documentation

no use

no use

1/1

no use

no use

debug unit features/documentation by Unknown on Feb 5, 2004			Not available!
[q]So I suggest calling these registers "Checkpoint registers" or in short "Checkpoints". We should get rid of all occurences of "Breakpoint" and "Watchpoint" in the manual. Instead of saying "Watchpoints generating Breakpoint" (as in DMR2[WPE] documentation) say "Checkpoints generating Trap exception".[/q] [q] Probably even better would be calling them "Matchpoint".[/q] Sounds good. Lets agree how to change the documentation. Do you wanna go and change the way you like it and then I'm gonna add my changes, do should I make al lthe changes and you review them (this second alternative might take more time)[/q] I'd like to update the text so it uses a clear terminology. However, you should write down the architecture changes, since you're the one implementing them. I will finalize the text then. We can meet on #opencores to discuss details, that might work out quicker than by email. We can also use AIM (AOL Instant Messenger). I don't have Microsoft Word, so I can't really edit your .doc. But I can modify the text, and you paste it back in. Heiko So I suggest calling these registers "Checkpoint registers" or in short "Checkpoints". We should get rid of all occurences of "Breakpoint" and "Watchpoint" in the manual. Instead of saying "Watchpoints generating Breakpoint" (as in DMR2[WPE] documentation) say "Checkpoints generating Trap exception". Probably even better would be calling them "Matchpoint". Sounds good. Lets agree how to change the documentation. Do you wanna go and change the way you like it and then I'm gonna add my changes, do should I make al lthe changes and you review them (this second alternative might take more time) I'd like to update the text so it uses a clear terminology. However, you should write down the architecture changes, since you're the one implementing them. I will finalize the text then. We can meet on #opencores to discuss details, that might work out quicker than by email. We can also use AIM (AOL Instant Messenger). I don't have Microsoft Word, so I can't really edit your .doc. But I can modify the text, and you paste it back in. Heiko

debug unit features/documentation by Unknown on Feb 5, 2004			Not available!
How about if I send you the RTF? If you have openoffice you shoudl have no problem reading RTF. Also other Word processors read RTF. I kinda don't like the irc stuff too much. It is too real time for me. ;-) But if you have a web interface to these two then I might try (I don't want to download an irc client...). regards, Damjan [q] I'd like to update the text so it uses a clear terminology. However, you should write down the architecture changes, since you're the one implementing them. I will finalize the text then. We can meet on #opencores to discuss details, that might work out quicker than by email. We can also use AIM (AOL Instant Messenger). I don't have Microsoft Word, so I can't really edit your .doc. But I can modify the text, and you paste it back in. Heiko _______________________________________________ <A HREF="http://www.opencores.org/mailman/listinfo/openrisc">http://www.opencores.org/mailman/listinfo/openrisc</A> [/q] How about if I send you the RTF? If you have openoffice you shoudl have no problem reading RTF. Also other Word processors read RTF. I kinda don't like the irc stuff too much. It is too real time for me. ;-) But if you have a web interface to these two then I might try (I don't want to download an irc client...). regards, Damjan I'd like to update the text so it uses a clear terminology. However, you should write down the architecture changes, since you're the one implementing them. I will finalize the text then. We can meet on #opencores to discuss details, that might work out quicker than by email. We can also use AIM (AOL Instant Messenger). I don't have Microsoft Word, so I can't really edit your .doc. But I can modify the text, and you paste it back in. Heiko _______________________________________________ http://www.opencores.org/mailman/listinfo/openrisc

debug unit features/documentation by Unknown on Feb 6, 2004			Not available!
> How about if I send you the RTF? Sure, that would be fine. Heiko > How about if I send you the RTF? Sure, that would be fine. Heiko

no use

no use

1/1

no use

no use

© copyright 1999-2025 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.