Hi Grant,
Grant Erickson wrote:
On 6/5/08 3:30 PM, Grant Erickson wrote:
I'm following up with you on this since 'git blame cmd_nand.c' seems to
indicate you added the CONFIG_FIT support to this file.
Based on stepping through with the debugger, my initial guess about hardware
issues may
On 6/2/08 3:02 PM, Grant Erickson wrote:
On 6/2/08 11:21 AM, Scott Wood wrote:
On Mon, Jun 02, 2008 at 08:22:21AM +0200, Stefan Roese wrote:
Hi Grant,
On Monday 02 June 2008, Grant Erickson wrote:
Before I jump in with the BDI and start debugging, has anyone else using
'nboot' and FIT
On 6/5/08 1:47 PM, Grant Erickson wrote:
On 6/2/08 3:02 PM, Grant Erickson wrote:
On 6/2/08 11:21 AM, Scott Wood wrote:
On Mon, Jun 02, 2008 at 08:22:21AM +0200, Stefan Roese wrote:
Hi Grant,
On Monday 02 June 2008, Grant Erickson wrote:
Before I jump in with the BDI and start debugging,
On 6/5/08 3:30 PM, Grant Erickson wrote:
I'm following up with you on this since 'git blame cmd_nand.c' seems to
indicate you added the CONFIG_FIT support to this file.
Based on stepping through with the debugger, my initial guess about hardware
issues may have been incorrect. Is there an
Hi Grant,
On Monday 02 June 2008, Grant Erickson wrote:
Before I jump in with the BDI and start debugging, has anyone else using
'nboot' and FIT images noticed that 'nboot' periodically fails where 'nand
read.i' of the SAME region of NAND succeeds?
Not sure here, since I never used nboot
On Mon, Jun 02, 2008 at 08:22:21AM +0200, Stefan Roese wrote:
Hi Grant,
On Monday 02 June 2008, Grant Erickson wrote:
Before I jump in with the BDI and start debugging, has anyone else using
'nboot' and FIT images noticed that 'nboot' periodically fails where 'nand
read.i' of the SAME
On 6/2/08 11:21 AM, Scott Wood wrote:
On Mon, Jun 02, 2008 at 08:22:21AM +0200, Stefan Roese wrote:
Hi Grant,
On Monday 02 June 2008, Grant Erickson wrote:
Before I jump in with the BDI and start debugging, has anyone else using
'nboot' and FIT images noticed that 'nboot' periodically fails
Before I jump in with the BDI and start debugging, has anyone else using
'nboot' and FIT images noticed that 'nboot' periodically fails where 'nand
read.i' of the SAME region of NAND succeeds?
= echo $bootaddr
80
= echo $boot0
nboot ${bootaddr} 0 0 setenv bootargs
