GDB Issue

Hello All,

I am having an issue getting U-Boot going on a PPC-440GX board. I am using
the GDB that was built with U-Boot for ppc-4xx and a BDI3000 to connect to
the target. Whenever I attempt to connect to the BDI3000, I get the
following error:

     (gdb) target remote 192.168.4.252:2001

     Remote debugging using 192.168.4.252:2001

     Remote 'g' packet reply is too long:deadbeaf....

I believe this error is caused by GDB being configured to the wrong
architecture. So I did the following...

     [njozwiak <at> localhost tftpboot]$ ppc_4xx-gdb u-boot

     GNU gdb Red Hat Linux (6.7-1rh)

     Copyright (C) 2007 Free Software Foundation, Inc.

     License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>

     This is free software: you are free to change and redistribute it.

     There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"

Re: GDB Issue

Dear "Nate Jozwiak",

In message <024501cb7abd$a49f1dd0$eddd5970$ <at> biz> you wrote:
>
> I am having an issue getting U-Boot going on a PPC-440GX board. I am using
> the GDB that was built with U-Boot for ppc-4xx and a BDI3000 to connect to
> the target. Whenever I attempt to connect to the BDI3000, I get the
> following error:
> 
>      (gdb) target remote 192.168.4.252:2001
>      Remote debugging using 192.168.4.252:2001
>      Remote 'g' packet reply is too long:deadbeaf....

You hit a FAQ. Please see here:
http://www.denx.de/wiki/view/DULG/ELDKGDBProblemsOnE500

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@...
Computers make excellent and efficient servants, but I have  no  wish
to  serve under them. Captain, a starship also runs on loyalty to one
man. And nothing can replace it or him.
	-- Spock, "The Ultimate Computer", stardate 4729.4

Re: GDB Issue

Hi Wolfgang,

I appreciate the reply. I did go through the FAQs and saw that one. I
believe it's exclusive to issues with e500 architectures, am I correct? My
target is not an e500 based system it's the 440 architecture and GDB appears
to be locked into an e500 arch configuration.

Thanks,
Nate

-----Original Message-----
From: Wolfgang Denk [mailto:wd@...] 
Sent: Tuesday, November 02, 2010 16:01 PM
To: Nate Jozwiak
Cc: eldk@...
Subject: Re: [ELDK] GDB Issue

Dear "Nate Jozwiak",

In message <024501cb7abd$a49f1dd0$eddd5970$ <at> biz> you wrote:
>
> I am having an issue getting U-Boot going on a PPC-440GX board. I am using
> the GDB that was built with U-Boot for ppc-4xx and a BDI3000 to connect to
> the target. Whenever I attempt to connect to the BDI3000, I get the
> following error:
> 
>      (gdb) target remote 192.168.4.252:2001
>      Remote debugging using 192.168.4.252:2001
>      Remote 'g' packet reply is too long:deadbeaf....

Resource temporarily unavailable

Hello,

The original kernel of my TQM885D module with U-boot 1.3.0-rc2 and Linux 2.4.25, has got the Ethernet
support via MPC8xx Serial Communication Controller SCC2.

Unfortunately I need to use SSC2 as UART in my system. So I recompiled the kernel setting:

-Enable Ehternet Support Via serial communication controller on SCC1
-Enable SCC for UART
-Use SCC2 for UART

On the original carrier board (from TQ) everything works fine! I can send, receive data and drive RTS line properly...
But, when I mount the module on my own carrier board, using this uart I found:

"Resource temporarily unavailable"

And this time also the RTS line is not driven?

Any hint?

Luigi

_______________________________________________
eldk mailing list
eldk@...
http://lists.denx.de/mailman/listinfo/eldk

Re: Building U-Boot

Hi all,

I am having an issue debugging U-Boot so I decided to try and go back and
rebuild it from the start to verify it was built correctly. I have an AMCC
Taishan eval board. It is a PPC-440GX. Following the instructions in the
U-Boot documentation doesn't seem to be correct.

$ wget ftp://ftp.denx.de/pub/u-boot/u-boot-1.2.0.tar.bz2

$ bunzip2 < u-boot-1.2.0.tar.bz2 | tar xf -

$ cd u-boot-1.2.0

$ make distclean
$ make taishan_config
$ make all

But I get the following error: 

[njozwiak <at> localhost u-boot-1.2.0]$ make taishan_config

make: *** No rule to make target `taishan_config'.  Stop.

So I pull up the Makefile in the root directory and sure enough, there is no
rule for a taishan_config. So I downloaded the latest version of U-Boot
(2010.09) and tried with that. 

[njozwiak <at> localhost u-boot]$ make distclean

[njozwiak <at> localhost u-boot]$ make taishan_config

Re: Building U-Boot

Am 08.11.2010 19:00, schrieb Nate Jozwiak:
> Hi all,
> 
>  
Hi,
> 
> 
> $ bunzip2 < u-boot-1.2.0.tar.bz2 | tar xf -
> 
> $ cd u-boot-1.2.0

This is very old...

> So I pull up the Makefile in the root directory and sure enough, there is no
> rule for a taishan_config. So I downloaded the latest version of U-Boot
> (2010.09) and tried with that. 

Good idea. Better to start with the current version.

> [njozwiak <at> localhost u-boot]$ make distclean
> 
> [njozwiak <at> localhost u-boot]$ make taishan_config
> 
> Configuring for taishan board...
> 
> [njozwiak <at> localhost u-boot]$ make all
> 
> make: ppc_8xx-gcc: Command not found

It seems you have not correctly setup the ELDK. Have you set the

Re: Resource temporarily unavailable

Dear Luigi Rizzi,

In message
<28EC12D487C391468508F50C4A67A23901B3F02184B7@...> you wrote:
>
> The original kernel of my TQM885D module with U-boot 1.3.0-rc2 and Linux 2.
> 4.25, has got the Ethernet support via MPC8xx Serial Communication Controll
> er SCC2.
> 
> Unfortunately I need to use SSC2 as UART in my system. So I recompiled the
> kernel setting:
> 
> -Enable Ehternet Support Via serial communication controller on SCC1
> -Enable SCC for UART
> -Use SCC2 for UART
> 
> On the original carrier board (from TQ) everything works fine! I can send,
> receive data and drive RTS line properly...
> But, when I mount the module on my own carrier board, using this uart I fou
> nd:
> 
> "Resource temporarily unavailable"
> 
> And this time also the RTS line is not driven?
> 
> Any hint?

Sorry, but you don't even mention what the differences between your
custom carrier board and the STK8xx board might be.  How could we even
guess then what might be wrong in yoru configuration?

Re: Building U-Boot

Dear "Nate Jozwiak",

In message <001401cb7f6e$e55f4fb0$b01def10$ <at> biz> you wrote:
> 
> I am having an issue debugging U-Boot so I decided to try and go back and
> rebuild it from the start to verify it was built correctly. I have an AMCC
> Taishan eval board. It is a PPC-440GX. Following the instructions in the
> U-Boot documentation doesn't seem to be correct.

The documentation *is* correct. You just have to go through it step by
step. Don't omit important things...

...
> $ wget ftp://ftp.denx.de/pub/u-boot/u-boot-1.2.0.tar.bz2
...
> But I get the following error: 
> 
> make: *** No rule to make target `taishan_config'.  Stop.

Well, yes. You download a more than 3 year old version of U-Boot. I
don't think the Taishan board was even available to normal customers
by then.

> So I pull up the Makefile in the root directory and sure enough, there is no
> rule for a taishan_config. So I downloaded the latest version of U-Boot
> (2010.09) and tried with that. 
...
> make: ppc_8xx-gcc: Command not found

Well, you forgot to install and/or configure the cross tool chain

Re: GDB Issue

Hi Nate Jozwiak,

[...]

> As you see, initially GDB says the target architecture is powerpc:403. But
> the show arch command claims it is the powerpc:e500. And commands placed to
> change it from powerpc:e500 do not appear to be working.

This looks fishy indeed.

> As I said, this it the version of GDB that was built with U-Boot following
> the instructions on the website. Does anyone have any insight into why it
> does not work and why I am unable to change the architecture?

What exactyl do you mean by "built with U-Boot"?

Can you please give the pre-compiled binaries from our ELDK 4.2 and 4.1
a go?

Thanks!
  Detlev

--

-- 
Die meisten schaetzen nicht, was sie verstehen; aber was sie nicht fassen
koennen, verehren sie.  Um geschaetzt zu werden, muessen die Sachen Muehe
kosten; daher wird geruehmt, wer nicht verstanden wird.
                                    --- Baltasar Gracian
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany