Sylvain ANDRE | 4 May 09:48 2009

ELDK Linux 2.6.29, MPC885ADS and early console

Hi Detlev,

I came back to my office this morning. I removed all my code from the 
Linux kernel as you said and tried again with Linux post mortem.
Here is the result :

<6>Using Freescale MPC885 ADS machine description.
<6>Using Freescale MPC885 ADS machine description.
<5>Linux version 2.6.29-rc7(root at localhost.localdomain) (gcc version 
4.2.2) #4 Mon May 4 09:25:51 CEST 2009

and nothing after (the previous error message disapeared).
But the console is still quiet.

    Cheers.
    Sylvain.

Detlev Zundel a ?crit :
> Hi Sylvain,
>
>   
>> finally I succeeded with your recipe, here is the result of the memory
>> dump : (concatenated ASCII only)
>>
>> <6>Using Freescale MPC885 ADS machine description.
>> <6>Using Freescale MPC885 ADS machine description.
>> <5>Linux version 2.6.29-rc7 (root at localhost.localdomain) (gcc version
>> 4.2.2) #3 Fri Apr 17 09:30:49 CEST 2009.
>> <1>Unable................................................ess 0xff000ad8.
>> <................................................................s of
(Continue reading)

Detlev Zundel | 4 May 12:02 2009
Picon
Picon
Picon

ELDK Linux 2.6.29, MPC885ADS and early console

Hi Sylvain,

> Hi Detlev,
>
> I came back to my office this morning. I removed all my code from the
> Linux kernel as you said and tried again with Linux post mortem.
> Here is the result :
>
> <6>Using Freescale MPC885 ADS machine description.
> <6>Using Freescale MPC885 ADS machine description.
> <5>Linux version 2.6.29-rc7(root at localhost.localdomain) (gcc version
> 4.2.2) #4 Mon May 4 09:25:51 CEST 2009
>
> and nothing after (the previous error message disapeared).
> But the console is still quiet.

Hm, I'm running out of ideas now.  One really needs to debug the start
phase of Linux, as it goes AWOL pretty early.  Time to fire up a
debugger and walk through the code step by step.

Best wishes
  Detlev

--

-- 
Every generation laughs at the old fashions, but follows religiously
the new.
                                        -- Henry David Thoreau
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
(Continue reading)

Nathan French | 5 May 20:53 2009

PPC 405EX ethernet in MII mode instead of RGMII?

I'm bringing up a board that is similar to a Kilauea/Halakea but with a
NatSemi DP83640 ethernet phy.  We've wired the phy up for MII mode and
have it working with U-Boot after some slight modifications to U-Boot
(setting the phy address and MII mode for EMAC0).

Now I've got linux running on the board.  I'm using a kernel config from
AMCC.  I see that linux is seeing the phy at the right address (0x11)
and configuring it for RGMII (not the mode we're using).  Here's a
snippet from the kernel log:

~ # grep MII /var/log/messages 
Dec 31 18:00:13 kilauea user.info kernel:
RGMII /plb/opb/emac-rgmii at ef600b00 initialized with MDIO support
Dec 31 18:00:13 kilauea user.notice
kernel: /plb/opb/emac-rgmii at ef600b00: input 0 in RGMII mode
Dec 31 18:00:13 kilauea user.warn kernel: eth0: found Generic MII PHY
(0x11)

I tried defining CONFIG_MII=y in my kernel config since it is disabled
in the AMCC config.  I didn't see a change.

I took a quick look at arch/ppc/platforms/4xx/kilauea.c and it looks
like the EMAC0 is hard-coded for RGMII.

I'm a little green with linux (developed a couple simple PCI drivers,
nothing complicated) so I don't really know the right way to attack
this.  Can someone point me in the right direction?

Thanks,

(Continue reading)

Wolfgang Denk | 5 May 21:28 2009
Picon
Picon

PPC 405EX ethernet in MII mode instead of RGMII?

Dear Nathan French,

In message <1241549606.3241.524.camel at localhost.localdomain> you wrote:
> I'm bringing up a board that is similar to a Kilauea/Halakea but with a
> NatSemi DP83640 ethernet phy.  We've wired the phy up for MII mode and
> have it working with U-Boot after some slight modifications to U-Boot
> (setting the phy address and MII mode for EMAC0).

You probably want to post this on the ppc mailing list; your
question is actually not ELDK related.

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 at denx.de
On the subject of C program indentation: "In My Egotistical  Opinion,
most  people's  C  programs  should be indented six feet downward and
covered with dirt."                               - Blair P. Houghton

Felix Radensky | 5 May 21:30 2009

PPC 405EX ethernet in MII mode instead of RGMII?

Hi, Nathan

Nathan French wrote:
> I'm bringing up a board that is similar to a Kilauea/Halakea but with a
> NatSemi DP83640 ethernet phy.  We've wired the phy up for MII mode and
> have it working with U-Boot after some slight modifications to U-Boot
> (setting the phy address and MII mode for EMAC0).
> 
> Now I've got linux running on the board.  I'm using a kernel config from
> AMCC.  I see that linux is seeing the phy at the right address (0x11)
> and configuring it for RGMII (not the mode we're using).  Here's a
> snippet from the kernel log:
> 
> ~ # grep MII /var/log/messages 
> Dec 31 18:00:13 kilauea user.info kernel:
> RGMII /plb/opb/emac-rgmii at ef600b00 initialized with MDIO support
> Dec 31 18:00:13 kilauea user.notice
> kernel: /plb/opb/emac-rgmii at ef600b00: input 0 in RGMII mode
> Dec 31 18:00:13 kilauea user.warn kernel: eth0: found Generic MII PHY
> (0x11)
> 
> I tried defining CONFIG_MII=y in my kernel config since it is disabled
> in the AMCC config.  I didn't see a change.
> 
> I took a quick look at arch/ppc/platforms/4xx/kilauea.c and it looks
> like the EMAC0 is hard-coded for RGMII.
> 
> I'm a little green with linux (developed a couple simple PCI drivers,
> nothing complicated) so I don't really know the right way to attack
> this.  Can someone point me in the right direction?
(Continue reading)

Jay York | 6 May 05:02 2009
Picon
Picon

Rebuilding the ELDK from scratch

Following the instructions on http://www.denx.de/wiki/view/DULG/ELDKRebuilding 
  and http://www.denx.de/wiki/DULG/ 
AN2009_02_EldkReleaseBuildEnvironment, I've been able to rebuild the  
ELDK from scratch, with one addition.  I found it necessary to create  
the following file:

# cat /opt/eldkbuild/home/microwin/Arch.rules

include $(MW_DIR_SRC)/Arch.rules

HOSTCC = /usr/bin/gcc -B/usr/bin/

#

Without this file, my build would stop in target step 84 while making  
microwindows:

# tail /opt/eldk/build/ppc.LOG
Done
Building freetype package step trg.83 at 18:27:18
Done
Installing freetype-ppc_4xx-2.3.4-3.ppc.rpm package
Installing freetype-devel-ppc_4xx-2.3.4-3.ppc.rpm package
Done
Building microwindows package step trg.84 at 18:28:57
parse_file: build_package failed for microwindows.spec
+ exit 1
+ rm -fr /tmp/pkg.952
#
# tail -23 /opt/eldk/build/ppc-2009-04-07/logs/ppc_4xx/ 
(Continue reading)

Wolfgang Denk | 7 May 22:33 2009
Picon
Picon

Rebuilding the ELDK from scratch

Dear Jay York,

In message <5511FD4A-50BF-4619-8F7A-7139D834BDCC at verizon.net> you wrote:
> Following the instructions on http://www.denx.de/wiki/view/DULG/ELDKRebuilding 
>   and http://www.denx.de/wiki/DULG/ 
> AN2009_02_EldkReleaseBuildEnvironment, I've been able to rebuild the  
> ELDK from scratch, with one addition.  I found it necessary to create  
> the following file:
> 
> # cat /opt/eldkbuild/home/microwin/Arch.rules
> 
> include $(MW_DIR_SRC)/Arch.rules
> 
> HOSTCC = /usr/bin/gcc -B/usr/bin/
> 
> #

Hm... that should not be needed. At least it is not here.

> Without this file, my build would stop in target step 84 while making  
> microwindows:
> 
> # tail /opt/eldk/build/ppc.LOG
> Done
> Building freetype package step trg.83 at 18:27:18
> Done
> Installing freetype-ppc_4xx-2.3.4-3.ppc.rpm package
> Installing freetype-devel-ppc_4xx-2.3.4-3.ppc.rpm package
> Done
> Building microwindows package step trg.84 at 18:28:57
(Continue reading)

Bastian Ruppert | 8 May 11:17 2009
Picon

rpm: Failed dependencies

Hello, 
i am using eldk 4.2 arm and compiled some stuff on the target platform.
I created a rpm package on the target platform.
When i try to install this package the following error occurs:

-bash-3.2# rpm -i checkinstall-arm-1.6.1-1.armv5tejl.rpm
error: Failed dependencies:
        /bin/bash is needed by checkinstall-arm-1.6.1-1.armv5tejl
        /bin/sh is needed by checkinstall-arm-1.6.1-1.armv5tejl
-bash-3.2# 

/bin/bash and /bin/sh are existing, and googling about this problem shows that bash and sh are not
installed by rpm so it is not in a rpm database. 
Bash is listed as an ELDK Target Package (sh is not listed).

possible solutions :   
-Create dummy rpm-package and install them to solve the dependencies.
-install Package with ignoring dependencies (--nodeps)

Please tell me whats is the ELDK-way to solve this problem.
How to tell the rpm-database thats the bash package and the sh stuff is there (without faking something)?

Thank you very much,
Bastian.

Wolfgang Denk | 8 May 14:43 2009
Picon
Picon

rpm: Failed dependencies

Dear Bastian,

in message <31266277.494851241774253985.JavaMail.servlet at kundenserver> you wrote:
>
> i am using eldk 4.2 arm and compiled some stuff on the target platform.
> I created a rpm package on the target platform.
> When i try to install this package the following error occurs:
> 
> -bash-3.2# rpm -i checkinstall-arm-1.6.1-1.armv5tejl.rpm
> error: Failed dependencies:
>         /bin/bash is needed by checkinstall-arm-1.6.1-1.armv5tejl
>         /bin/sh is needed by checkinstall-arm-1.6.1-1.armv5tejl
> -bash-3.2# 
...
> possible solutions :   
> -Create dummy rpm-package and install them to solve the dependencies.
> -install Package with ignoring dependencies (--nodeps)

You could also try an re-install all packages using the native rpm
tool running on the target.

> Please tell me whats is the ELDK-way to solve this problem.

So far, ELDK's cross RPM does not maintain a target version of the RPM
database. The easiest way aroud this is to use the "--nodeps" opition.

Best regards,

Wolfgang Denk

(Continue reading)

Unknown | 13 May 09:34 2009

Enable MSI on ppc405ex kilauea board

Hi,

I am trying to enable MSI(-X) capability on the powerpc405ex. I'am currently using linux 2.6.27.17, and
correctly the pcie driver fails to enable MSI since there are no arch_setup_msi_irq for this platform.
Has anyone had any success enabling MSI on this platform via DTS ( if so, how should the blob look like )?

Best regards

Staale Aakermann


Gmane