Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Hi Aaron, Thanks you for such a detailed explanation. It was of a great help to me. Thanks, Pandu On Thu, Mar 10, 2011 at 6:05 AM, Aaron Williams < aaron.willi...@caviumnetworks.com> wrote: > Hi Pandurang, > > We solved this problem by using TLB mapping for U-Boot on our MIPS > platforms. > >

Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Hi Pandurang, We solved this problem by using TLB mapping for U-Boot on our MIPS platforms. This was also due to the fact that we need to load U-Boot at the top of physical memory which is often unreachable with 32-bit addressing. By doing this we always link U-Boot at address 0xC000 and it

Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Hi Wolfgang Denk, Thanks a lot for all the clarification and help. I really appreciate your support. I have few question with reards to the start.S file for MIPS. What is the significance of CONFIG_SYS_MONITOR_BASE ?? why is this used as the base/source address in relocate_code in mips start.S

Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Dear Pandurang Kale, In message you wrote: > > For MIPS I do not find the TEXT_BASE symbol, there is SYS_CFG_MONITOR_BASE Please check again. MIPS uses CONFIG_SYS_TEXT_BASE like all other architectures. > which it uses to relocate the code from the define symbol to high RAM > address. how can

Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Hi Wolfgang Denk, Thanks for the response. Please find my questions inline. On Thu, Mar 3, 2011 at 11:11 PM, Wolfgang Denk wrote: > Dear Pandurang Kale, > > In message > you wrote: > > > > But when primary bootloader copies the uboot image to the RAM and passes > the > > control to the uboot,

Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Dear Pandurang Kale, In message you wrote: > > But when primary bootloader copies the uboot image to the RAM and passes the > control to the uboot, uboot (MIPS version of start.S and > arch/mips/lib/borad.c) tries to relocate the > already copied image from RAM (the primary bootloader copied it

Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Hi Charles, Thanks for the info. We have a primary boot loader, which read the flash which might contain more than one existing mod-image(containing header, uboot and kernel) and depending on the state and condition it decides which mod is valid and copies the uboot from the valid mod-image to

Re: [U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Dear Pandurang: Sounds like you have battling boot loaders going on, perhaps with the Broadcom CFE (Common Firmware Environment) ? Someone else may have some data on CONFIG_SKIP_RELOCATE_UBOOT, or you could reflash your target and replace the existing bootloader with the U-Boot bootloader so your

[U-Boot] uboot for MIPS: need help to skip relocate uboot and start uboot from RAM

Hello Everyone, We have MIPS based development board and I am trying to get the uboot up and running on it. We have a primary bootloader which check for the valid mod-image stored on the flash. This mod-image consist of header, uboot and linux kernel. Depending on the recent, active and stable ima