I repeat:
Do you see any messages when you do a post mortem dump of the log_buf memory? [See http://www.denx.de/twiki/bin/view/DULG/LinuxPostMortemAnalysis]
????
I think I don't understand something in your explenation of post mortem, how can I do grep log_buf system.map when I have nothing but UBOOT prompt?
I tried removing all my code and tried again, that was the first thing I thought that maybe I crash the system. I tried again and again and the problem was the same.
You cannot make such a claim. The _symptoms_ may have been the same. The problem may have been a different one.
- Check your memory map, and the init sequence of your SDRAM [no,
I'm not going to explain this here again. Search the archives.]
Unfortunatly the archives are not searchable, otherwise that would be the first thing I would
The GMANE archive _is_ searchable.
What is the GNAME archive?
do, could you give me some hints on what do you mean init sequence of SDRAM?
IO mean the initialization sequence that is required for the SDRAM chips. In 98% of all porting problems this is the culprit.
I still do not understand what do you mean by init sequence of SDRAM, If I had any hint of what you mean by that I would check for it. All I know is that I have 128MB of RAM mapped from 0x0000 I have checked it again.
Did you read the FAQ? How about the "clocks_in_mhz" setting? Or the bd_info structure used by the Linux kernel?
Yes, I have thought about the clock value and made sure it is passed Ok, since I am using kernel 2.4.25 I understand that the clock should be in Hz and that is what U-boot transfers.
-- Ori Idan