[U-Boot-Users] u-boot -> Linux prompt assistance

[U-Boot-Users] u-boot -> Linux prompt assistance

[Alfred Manheim]

I have u-boot running and am currently working on the Linux prompt. I store
uImage at ffd00000. u-boot is at fff00000. 

* The Freescale BSP for the MPC8360 was used for the base. u-boot
1.1.6 and Linux 2.6.19 are the versions selected and reported.
* u-boot is running at the prompt and seems stable for u-boot functionality.
* Enabling the 64M of DDR2 memory was quite an endeavor but it appears
stable today. Nothing shows up with the basic u-boot memory test, and there
are no crashes using the normal u-boot functions. i-cache is enabled. Memory
problems have not been fully ruled out. Any suggestions on how to validate
the memory better?
* Linux (~2.6.19) is compiled with no changes at this point. 

Executing "bootm ffd00000" results in a transfer to Linux that (due to the
CodeWarrior USB TAP?) I can follow the code up to the RFI in head_32.S. It
looks like it is executing farther than that. I have attached a dump of the
memory found at log_buf. Also attached is System.map. 

My interpretation of the stack dump suggests that start_here is successfully
executing in high memory and the crash is within MMU_init. The crashes that
follow would seem to be as much a result of this first problem.

Any suggestions or observations about this crash would be appreciated.

Alfred Manheim

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: System_map_trimmed.txt
Url: http://lists.denx.de/pipermail/u-boot/attachments/20070820/174557f4/attachment.txt 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oops.log
Type: application/octet-stream
Size: 6155 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070820/174557f4/attachment.obj 

[U-Boot-Users] u-boot -> Linux prompt assistance

[Wolfgang Denk]

In message <007701c7e3a4$ff339220$fd9ab660$@rr.com> you wrote:
> 
> Executing "bootm ffd00000" results in a transfer to Linux that (due to the
> CodeWarrior USB TAP?) I can follow the code up to the RFI in head_32.S. It
> looks like it is executing farther than that. I have attached a dump of the
> memory found at log_buf. Also attached is System.map. 
> 
> My interpretation of the stack dump suggests that start_here is successfully
> executing in high memory and the crash is within MMU_init. The crashes that
> follow would seem to be as much a result of this first problem.
> 
> Any suggestions or observations about this crash would be appreciated.

Just an observation: this is off topic here.

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
In accord with UNIX philosophy, Perl gives you enough  rope  to  hang
yourself.              - L. Wall & R. L. Schwartz, _Programming Perl_