Re: [OpenOCD-devel] Is OPENOCD a useful tool for you?And will it be useful for me too?

[<jan...@ce...>]

Stefan,
Thank you for your reply.

> If you can connect the MIPS CPU with OpenOCD, your CPU is most probably
> OK. You can read/write registers or talk to integrated peripherals.
Do you mean if I read ONLY CPU Chip ID , the CPU is most probably
OK?



> To check SDRAM, initialize your SDRAM controller and write/read test
> patterns.
Can you please explain a little more what you mean by YOUR SDRAM controller?
( We did not design that MIPS  linux based device. We repair them only)


> I don't know what you mean with BIOS? The MIPS ROM part at 0xbfc00000 ?
> You can step through with single step mode or by setting breakpoints.

MIPS processor must fetch from address 0xBFC00000, the Reset
exception vector but in the device I am talking about , there is EPROM integrated circuit that 
serves as BIOS( ROM).And if THIS  BIOS is faulty, the device does not start. So , is it 
possible to step through this BIOS , using OpenOCD?


Thank you

> > We often repair a Linux based devices ( Linux embeded devices) that
> > use MIPS CPU. Sometimes this device is dead and the problem can be
> > CPU or BIOS( ROM) or SDRAM( DDR)
> > How can OpenOCD help us so that we are  able identify where the
> > problem is? Whether CPU or Bios or SDRAM?
> 

> 
> To check SDRAM, initialize your SDRAM controller and write/read test
> patterns.
> 
> I don't know what you mean with BIOS? The MIPS ROM part at 0xbfc00000 ?
> You can step through with single step mode or by setting breakpoints.
> 
> Stefan
>