From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Nelson <eric.nelson@boundarydevices.com>
Date: Tue, 17 Mar 2015 09:51:57 -0700
Subject: [U-Boot] [PATCH] arm: mx5: Add support for USB armory board
In-Reply-To: <CAOMZO5DGOmsGsHCYgnA9nwkwKXpSj-s--FfQZPi-XMW9DXGubg@mail.gmail.com>
References: <1424768633-22084-1-git-send-email-andrej@inversepath.com>
 <CAGHP0pJt4XHvhGXDbVvXz1v-BoLyDTY9S1ABFGSUwEm2aAA6yw@mail.gmail.com>
 <CAOMZO5DGOmsGsHCYgnA9nwkwKXpSj-s--FfQZPi-XMW9DXGubg@mail.gmail.com>
Message-ID: <55085BAD.4020907@boundarydevices.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Fabio,

On 03/17/2015 09:30 AM, Fabio Estevam wrote:
> On Mon, Mar 16, 2015 at 1:50 PM, Chris Kuethe <chris.kuethe@gmail.com> wrote:
> 
>> U-Boot 2015.04-rc3-00209-ga74ef40-dirty (Mar 15 2015 - 22:04:22)
>>
>> CPU:   Freescale i.MX53 rev2.1 at 800 MHz
>> Reset cause: WDOG
> 
> Here the reset cause is printed correctly.
> 
>> Board: Inverse Path USB armory MkI
>> I2C:   ready
>> DRAM:  512 MiB
>> MMC:   FSL_SDHC: 0
>> In:    serial
>> Out:   serial
>> Err:   serial
>> CPU:   Freescale i.MX53 rev2.1 at 800 MHz
>> Reset cause: unknown reset
> 
> ,but here it fails.
> 
> Why does CPU version and reset cause are printed twice?
> 

It appears that get_reset_cause() is being called twice,
and since it's destructive, the second will say "unknown reset".

This patch will fix the value of the return value:
	http://patchwork.ozlabs.org/patch/439934/

> Is this happening with all mx53 boards or only with this one?
> 

I have no idea about this, but there appear to be multiple
calls to print_cpuinfo().

Regards,


Eric