info reg RISCWATCH

info reg RISCWATCH

[Prakash S]

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

Hi All,
   Sorry if I am posting this in a wrong forum. I am looking at RISC watch
debugger for our PPC board. We are currently trying to estimate the cost and
effort of porting a vxworks image to a linux based image. Does any of you
know the approximate cost of procuring the RISC watch debugger. I thought
would query you folks before i goto IBM support guys.

Thanking you,
Prakash S

[-- Attachment #2: Type: text/html, Size: 459 bytes --]

Re: info reg RISCWATCH

[Stefan Roese]

On Friday 14 March 2008, Prakash S wrote:
>    Sorry if I am posting this in a wrong forum. I am looking at RISC watch
> debugger for our PPC board. We are currently trying to estimate the cost
> and effort of porting a vxworks image to a linux based image. Does any of
> you know the approximate cost of procuring the RISC watch debugger.

No. But I'm sure that the IBM RiscWatch is pretty expensive. Do you really 
need an RiscWatch? I would recommend to buy an Abatron BDI2000.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office@denx.de
=====================================================================

Re: info reg RISCWATCH

[Wolfgang Denk]

In message <200803141311.21994.sr@denx.de> Stefan Roese wrote:
> 
> No. But I'm sure that the IBM RiscWatch is pretty expensive. Do you really 
> need an RiscWatch? I would recommend to buy an Abatron BDI2000.

...or rather a BDI3000 if you don't  need  compatibility  to  already
existing BDI2000's.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
If it happens once, it's a bug.
If it happens twice, it's a feature.
If it happens more than twice, it's a design philosophy.