[U-Boot-Users] does this situation can assert to be a hardware problem?
in the u-boot, when run into board_init_r(lib_mips/board.c), sometimes it stop at the call of mem_malloc_init, sometimes it stop at the call of env_relocate. does it means it maybe caused by hardware or uncorrect sdram init?, it can not be the software ploblem of the board.c file? when i used the bdi2000 to debug in, i found at the call of mem_malloc_init "lw t9,8(gp)" , if i set a breadpoint at "addiu t9,t9,1552", the t9 is not the correct value ,but in gp+8 is still a correct value
and if a set a breakpoint before "lw t9,8(gp)" at anywhere after in_ram, the t9 can get the correct value, so it can run the mem_malloc_init, and run to hang at env_relocate
as follow is the dissamble file bfc00b80 <board_init_r>: ...... bfc00c90: 8f990008 lw t9,8(gp) //to call mem_malloc_init bfc00c94: 00000000 nop bfc00c98: 27390610 addiu t9,t9,1552 bfc00c9c: 0320f809 jalr t9 bfc00ca0: 00000000 nop
as follow is the printf info of two different reset and go situation
U-Boot 1.1.3 (Nov 23 2005 - 19:23:54)
checkboard Board: ACT213X (CPU Speed 0 MHz) DRAM: 32 MB Top of RAM usable for U-Boot at: a2000000 Reserving 146k for U-Boot at: a1fd8000 Reserving 192k for malloc() at: a1fa8000 Reserving 44 Bytes for Board Info at: a1fa7fd4 Reserving 36 Bytes for Global Data at: a1fa7fb0 Reserving 128k for boot params() at: a1f87fb0 Stack Pointer at: a1f87f98 before gd->bd operation!
U-Boot 1.1.3 (Nov 23 2005 - 19:23:54)
checkboard Board: ACT213X (CPU Speed 0 MHz) DRAM: 32 MB Top of RAM usable for U-Boot at: a2000000 Reserving 146k for U-Boot at: a1fd8000 Reserving 192k for malloc() at: a1fa8000 Reserving 44 Bytes for Board Info at: a1fa7fd4 Reserving 36 Bytes for Global Data at: a1fa7fb0 Reserving 128k for boot params() at: a1f87fb0 Stack Pointer at: a1f87f98 before gd->bd operation! after memmalloc! binrelocate
Best Regards
zhuzhenhua
In message 50c9a2250511232229t3f2e10e2m4af95ef4e53dbc39@mail.gmail.com you wrote:
in the u-boot, when run into board_init_r(lib_mips/board.c), sometimes it stop at the call of mem_malloc_init, sometimes it stop at the call of env_relocate. does it means it maybe caused by hardware or uncorrect sdram init?, it
Yes.
can not be the software ploblem of the board.c file?
Yes, it can be caused by incorrect software (like a bad port, incorrect hardware initialization), too.
Best regards,
Wolfgang Denk
On 11/24/05, Wolfgang Denk wd@denx.de wrote:
In message 50c9a2250511232229t3f2e10e2m4af95ef4e53dbc39@mail.gmail.com you wrote:
in the u-boot, when run into board_init_r(lib_mips/board.c), sometimes it stop at the call of mem_malloc_init, sometimes it stop at the call of env_relocate. does it means it maybe caused by hardware or uncorrect sdram init?, it
Yes.
can not be the software ploblem of the board.c file?
Yes, it can be caused by incorrect software (like a bad port,
~~~~~~~~~~~~~
you mean give a long address for io operation?
incorrect hardware initialization), too.
Best regards,
Wolfgang Denk
-- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de COMPONENT EQUIVALENCY NOTICE: The Subatomic Particles (Electrons, Protons, etc.) Comprising This Product Are Exactly the Same in Every Measurable Respect as Those Used in the Products of Other Manufactu- rers, and No Claim to the Contrary May Legitimately Be Expressed or Implied.
Best regards zhuzhenhua
participants (2)
-
Wolfgang Denk -
zhuzhenhua