Skip to contentSkip to conversation

Questions about U-boot of customized MPC8315E board

U-Boot du zhenhuan 3 participants 5 messages Apr 25, 2013 – May 21, 2013

lore
Share & tools
lore
#0 lore raw

Hello,
I'm a newbie using U-boot and met several problems with a customized board based on MPC8315E-RDB board.
On the new board, I have changed the Ethernet PHY to TI's DP83848
and NAND FLASH to 64Mbit (from old 32Mbit).

During U-boot form NOR FLASH , I met two problems :

1, if NAND flash support is enabled,
U-boot just print out "NAND : " without size info and then print out text like "machine check ...,",
then print out "resetting board ..."
So the board keep resetting again and again.
Does this have anything to do with NAND FLASH size change or NAND PART types?

2.if NAND flash support is disabled,
U-boot just go to Ethernet PHY initialization part and print out that DP83848 is not supported ,
Where can I put new driver to support it?

3.How can I watch more ouput infomation during U-boot boot process to debug these problems ?

Thanks.

#1 lore raw

Dear "du zhenhuan",

Quoted 6 lines · In message <[email protected]> you wrote:

1, if NAND flash support is enabled,
U-boot just print out "NAND : " without size info and then print out text like "machine check ...,",
then print out "resetting board ..."
So the board keep resetting again and again.
Does this have anything to do with NAND FLASH size change or NAND PART types?

It has probably nothing to do with the NAND flash size, but with the NAND chip type, and/or with other changes you did for your port.

Quoted 4 lines

2.if NAND flash support is disabled,
U-boot just go to Ethernet PHY initialization part and print out that DP83848 is not supported ,
Where can I put new driver to support it?

PHY support is in drivers/net/phy/

Are you sure generic PHY support does not work for you?

Quoted 1 line

3.How can I watch more ouput infomation during U-boot boot process to debug these problems ?

Define DEBUG for the interesting files?

Attach a JTAG debugger und fire up GDB?

Best regards,

Wolfgang Denk

Signature · 5 lines
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
Reader, suppose you were an idiot. And suppose you were a  member  of
Congress. But I repeat myself.                           - Mark Twain
author
#2 lore raw

Hi,
About debug,
Where should I define the macro to enable debug() function definition? Is there a place in makefile or head file?

Quoted 27 lines · Wolfgang Denk

Dear "du zhenhuan",

Quoted 5 lines · In message <[email protected]> you wrote:

1, if NAND flash support is enabled,
U-boot just print out "NAND : " without size info and then print out text like "machine check ...,",
then print out "resetting board ..."
So the board keep resetting again and again.
Does this have anything to do with NAND FLASH size change or NAND PART types?

It has probably nothing to do with the NAND flash size, but with the NAND chip type, and/or with other changes you did for your port.

Quoted 3 lines

2.if NAND flash support is disabled,
U-boot just go to Ethernet PHY initialization part and print out that DP83848 is not supported ,
Where can I put new driver to support it?

PHY support is in drivers/net/phy/

Are you sure generic PHY support does not work for you?

Quoted 1 line

3.How can I watch more ouput infomation during U-boot boot process to debug these problems ?

Define DEBUG for the interesting files?

Attach a JTAG debugger und fire up GDB?

Best regards,

Wolfgang Denk

#3 lore raw

Dear zhenhuan,

Please follow the nteiquette: do not top post / full quote!! If you need help, please see
http://www.netmeister.org/news/learn2quote.html

Quoted 3 lines · In message <[email protected]> you wrote:

Where should I define the macro to enable debug() function definition? Is there a place in makefile or head file?

Enable it (either on the compile command line or as a #define which must go _before_ the first #include) for/in the files for which you want to see debug information.

Note: it is usually not a good idea to enable it globally.

Best regards,

Wolfgang Denk

Signature · 7 lines
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
If a packet hits a pocket on a socket on a port,
And the bus is interrupted as a very last resort,
And the address of the memory makes your floppy disk abort,
Then the socket packet pocket has an error to report! - Ken Burchill?
#4 lore raw
In reply to du zhenhuan
Quoted 10 lines · du zhenhuan

Hello,
I'm a newbie using U-boot and met several problems with a customized board based on MPC8315E-RDB board.
On the new board, I have changed the Ethernet PHY to TI's DP83848
and NAND FLASH to 64Mbit (from old 32Mbit).

During U-boot form NOR FLASH , I met two problems :

Quoted 7 lines

1, if NAND flash support is enabled,
U-boot just print out "NAND : " without size info and then print out text like "machine check ...,",
then print out "resetting board ..."
So the board keep resetting again and again.
Does this have anything to do with NAND FLASH size change or NAND PART types?

Make sure that the physical address you're trying to map NAND at is covered by a LAW that points to eLBC, and that the LAW, eLBC, and TLB physical addresses match.

-Scott