[U-Boot] Questions about U-boot of customized MPC8315E board
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.
Dear "du zhenhuan",
In message 202dafde.df1f.13e4197224a.Coremail.dev_du@163.com 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.
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?
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
Hi, About debug, Where should I define the macro to enable debug() function definition? Is there a place in makefile or head file?
On 2013/4/26 3:36, Wolfgang Denk wrote:
Dear "du zhenhuan",
In message 202dafde.df1f.13e4197224a.Coremail.dev_du@163.com 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.
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?
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
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
In message 517A05CC.60003@163.com 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
On 04/25/2013 09:27:03 AM, du zhenhuan wrote:
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?
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
participants (4)
-
du zhenhuan -
Scott Wood -
Wolfgang Denk -
zhenhuan