.@cyberswitching.com
> > Cc: u-boot@lists.denx.de
> > Subject: Re: [U-Boot] environmental "baudrate" not used at boot up
> >
> > The full NAND code only works after relocation. So you cannot read out
> > the NAND environment, in the normal way, before seria
> -Original Message-
> From: u-boot-boun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de]
> On Behalf Of Wood Scott-B07421
> Sent: Thursday, January 20, 2011 1:28 AM
> To: chr...@cyberswitching.com
> Cc: u-boot@lists.denx.de
> Subject: Re: [U-Boot] environmenta
On Tue, 18 Jan 2011 21:34:45 -0800
wrote:
> On Sun, Jan 16, 2011 at 06:01:22AM -0800, chr...@cyberswitching.com wrote:
> > ...
> > Any advice on where to take it from here?
>
> Hi everyone,
>
> I investigated this a little further, and I'm wondering if the problem
> is related to the initializa
On Wed, Jan 19, 2011 at 08:49:12PM +0100, Reinhard Meyer wrote:
> I just want to point out that this works fine on our AT91SAM9260/9XE,
> however the environment is read from I2C EEPROM. Not sure where
> his ENV is coming from, whether it is read before use, or if there is
> static data involved be
Dear Wolfgang Denk,
> Dear chr...@cyberswitching.com,
>
> In message<20110119144640.GA8828@cslinux-build01.cyberswitching.local> you
> wrote:
>>
>> Thanks for the feedback. I hope that someone else can continue this
>> work now that I've identified the problem and have developed a solution
>> th
Dear chr...@cyberswitching.com,
In message <20110119144640.GA8828@cslinux-build01.cyberswitching.local> you
wrote:
>
> Thanks for the feedback. I hope that someone else can continue this
> work now that I've identified the problem and have developed a solution
> that works for my needs with no o
On Wed, Jan 19, 2011 at 07:59:10AM +0100, Wolfgang Denk wrote:
> > Based on empirical testing, I've discovered that re-running
> > init_baudrate() after env_relocate() fixes everything. The serial
> > console uses the baud rate stored in the "baudrate" variable now, and
> > some ordering of displa
Dear chr...@cyberswitching.com,
In message <20110119053445.GA9776@cslinux-build01.cyberswitching.local> you
wrote:
>
> I investigated this a little further, and I'm wondering if the problem
> is related to the initialization ordering in lib_arm/board.c.
>
> Here's the sequence:
>
>start_arm
On Sun, Jan 16, 2011 at 06:01:22AM -0800, chr...@cyberswitching.com wrote:
> ...
> Any advice on where to take it from here?
Hi everyone,
I investigated this a little further, and I'm wondering if the problem
is related to the initialization ordering in lib_arm/board.c.
Here's the sequence:
On Sun, Jan 16, 2011 at 03:42:25PM +0100, Albert ARIBAUD wrote:
> Le 16/01/2011 15:01, chr...@cyberswitching.com a ?crit :
> > I have a board based on an Atmel AT91SAM9263-EK running U-boot 2009.01.
> > I can't seem to get the environmental variable "baudrate" to be used
> > properly, though.
>
>
Le 16/01/2011 15:01, chr...@cyberswitching.com a écrit :
> Hi list,
>
> I have a board based on an Atmel AT91SAM9263-EK running U-boot 2009.01.
> I can't seem to get the environmental variable "baudrate" to be used
> properly, though.
>
> Here's the sequence:
>
> 1. Power on board, baudrate=115
Hi list,
I have a board based on an Atmel AT91SAM9263-EK running U-boot 2009.01.
I can't seem to get the environmental variable "baudrate" to be used
properly, though.
Here's the sequence:
1. Power on board, baudrate=115200
2. setenv baudrate 9600
(change terminal baud to 9600)
12 matches
Mail list logo