Re: debugging using bdi2000, unable to proceed.

["Omanakuttan" <omanakuttan@tataelxsi.co.in>]

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

Wolfgang Denk wrote:
>>we are using http://www.ultsol.com/PDFS/Tool%20Talk%2002-001a.pdf as a
>>refernce to get bdi 2000 setup running.
>>Connections are made as per the document.
>>bdisetup is run from the host. Using the configuration file.
>>We used format IMAGE and file zImage and the image file  loaded to
>>0x400000 using bdi2000.
>
>
> Don't do this. Build a PPCBoot image as usual using the mkimage tool,
> and use PPCboot to download and start the kernel. Use the BDI2000 for
> debugging only.
Hi,
We tried loading a ppcboot image of linux kernel and ramdisk referring
the document and
http://lists.linuxppc.org/linuxppc-embedded/200108/msg00188.html.
What we did is,
power up both bdi2k and target.
We got ppcboot prompt on the serial console.
Setup the bdi2000 using serial connection from the host (using bdisetup
executable) telnet to bdi2000. bdi2000 picks up the configuration file
and configures target and itself. in host, ppc_82xx-gdb <path to
vmlinux> put breakpoint at start_kernel

Now ideally we should be able to give bootm <image loc> <ramdisk loc>
from ppcboot. but bdi2k holds the target in debug mode. In this state we
are unable to enter any command into ppcboot prompt.
Same behaviour is shown in our custom board also.

we use the vads8260.cfg file provided by bdi2000.
I think there is some configuration that we need to change in the bdi
supplied file like bdimode and breakmode. Is it so? I cannot think of
any other reason.

Thanks,
Om.

[-- Attachment #2: VADS8260.CFG --]
[-- Type: application/x-unknown-content-type-CodeWarrior_cfg, Size: 5653 bytes --]