Hello ,
I am new to u-boot code. I had a requirement for running memory, cpu and
cache tests as part of diagnostics, on an ARM based platform. After
going through the code, I found that only PPC variants are available for
cpu and cache post tests.
1) Is that a limitation, or Is it some sort of mis
Hi ,
I am new to u-boot code. I had a requirement for running memory, cpu and
cache tests as part of diagnostics, on an ARM based platform. After
going through the code, I found that only PPC variants are available for
cpu and cache post tests.
Please help me...
Thanks,
shobin.b
_
Hello sreekumar.sivakumar,
sreekumar.sivaku...@wipro.com wrote:
> I am new to u-boot code. I had a requirement for running memory, cpu and
> cache tests as part of diagnostics, on an ARM based platform. After
> going through the code, I found that only PPC variants are available for
> cpu and cach
Hi Heiko,
On 07/15/2011 10:13 AM, Heiko Schocher wrote:
> sreekumar.sivaku...@wipro.com wrote:
>
> Actually nobody used it on arm
>
>> 2) If NO, Is there a branch or patch I can pickup which will have ARM
>> POST tests for cache and cpu?
>
> Try this patches (I actually worked on getting POST t
On Fri, Jul 15, 2011 at 04:13, Heiko Schocher wrote:
> sreekumar.sivaku...@wipro.com wrote:
>> 2) If NO, Is there a branch or patch I can pickup which will have ARM
>> POST tests for cache and cpu?
>
> Try this patches (I actually worked on getting POST tests running
> on an davinci based board):
>
Dear Valentin Longchamp,
In message <4e25a2d0.1090...@keymile.com> you wrote:
>
> With the memory test, that takes place before the relocation, it is extremly
> slow (even if I reduce the size of the memory tested to a very small portion).
> Is it something you have noticed as well ?
This might
On 07/19/2011 08:45 PM, Wolfgang Denk wrote:
> Dear Valentin Longchamp,
>
> In message <4e25a2d0.1090...@keymile.com> you wrote:
>>
>> With the memory test, that takes place before the relocation, it is extremly
>> slow (even if I reduce the size of the memory tested to a very small
>> portion).
Dear Valentin Longchamp,
In message <4e26b523.3070...@keymile.com> you wrote:
>
> I have done a little bit of profiling this morning, and the main culprit is
> the
> call to getenv_f in post_get_flags for the four environment variables:
>
> "post_poweron", "post_normal", "post_slowtest" "post_cr
On 07/20/2011 02:20 PM, Wolfgang Denk wrote:
> Dear Valentin Longchamp,
>
> In message <4e26b523.3070...@keymile.com> you wrote:
>>
>> I have done a little bit of profiling this morning, and the main culprit is
>> the
>> call to getenv_f in post_get_flags for the four environment variables:
>>
>>
Dear Valentin Longchamp,
In message <4e26cad9.3090...@keymile.com> you wrote:
>
> We are currently planning to move away from I2C EEPROM for environment (for
> future hardware), but what would you advise me to do for our current hardware
> where the environment is in this EEPROM ?
This depends on
Hi,
I am doing post for arm in uboot-toradex(in iris based colibri t20 board).When
i enabled post in my board file(colibri_t20.h) it showing following errors
after making uboot,
i=aapcs-linux -mno-thumb-interwork -march=armv5 -Werror -Wall
-Wstrict-prototypes -fno-stack-protector -o display.o d
Hi,
On 28 January 2014 23:04, shobin b wrote:
> Hi,
>
> I am doing post for arm in uboot-toradex(in iris based colibri t20 board).When
> i enabled post in my board file(colibri_t20.h) it showing following errors
> after making uboot,
>
> i=aapcs-linux -mno-thumb-interwork -march=armv5 -Werror -Wa
12 matches
Mail list logo
