[U-Boot-Users] U-boot Memory Map
Hi,
Looking for a document for u-boot memory map. Enabling DEBUG at board.c I got few of them, Is there any addition to this ?
*************************************************** CPU: unknown MPC860 (0x08000003) at 50 MHz: 4 kB I-Cache 4 kB D-Cache FEC pres ent Board: Force ( MPC852T ) DRAM: 64 MB Top of RAM usable for U-Boot at: 04000000 Reserving 256k for U-Boot at: 03fc0000 Reserving 448k for malloc() at: 03f50000 Reserving 60 Bytes for Board Info at: 03f4ffc4 Reserving 44 Bytes for Global Data at: 03f4ff98 Stack Pointer at: 03f4ff78 New Stack Pointer is: 03f4ff78 Now running in RAM - U-Boot at: 03fc0000 FLASH: 1 MB AM29LV008BB (8 Mbit, bottom boot sect) ******************************************************
Warm Regards, Raghu.
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
In message 20031014143335.59640.qmail@web40413.mail.yahoo.com you wrote:
Looking for a document for u-boot memory map. Enabling DEBUG at board.c I got few of them, Is there any addition to this ?
Sorry, I can't parse this. What exactly is your question?
The memory map is something you define BEFORE starting to port any software, not something that is magically hidden in U-Boot.
Best regards,
Wolfgang Denk
Oh Sorry, For putting wrong words..!
I got few of them, Is there any addition to this ?
Sorry, I can't parse this. What exactly is your question?
The memory map is something you define BEFORE starting to port any software, not something that is magically hidden in U-Boot.
I want to know where in RAM the u-boot maintains its code and data. The monitor code begins from the highest memory in RAM, then we have the malloc region, Stack, board info, global data etc etc. Are some of u-boot data maintained else where.
As mentioned in the README/Docs when we perform mem test board hangs on writes or read at certain regions. I get this at RAM address 0 aswell.
A small write up on this will help all
Warm Regards Raghu
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
In message 20031015022817.19022.qmail@web40404.mail.yahoo.com you wrote:
I want to know where in RAM the u-boot maintains its code and data. The monitor code begins from the highest memory in RAM, then we have the malloc region, Stack, board info, global data etc etc. Are some of u-boot data maintained else where.
What exactly are you missing in section "Memory Management" of the README file?
As mentioned in the README/Docs when we perform mem test board hangs on writes or read at certain regions. I get this at RAM address 0 aswell.
It is probably not a good idea to overwrite the exception vector code while the system has interrupts enabled...
A small write up on this will help all
It's all there. You just have to read it.
Best regards,
Wolfgang Denk
participants (2)
-
Raghu -
Wolfgang Denk