António Silva wrote:
Hi,
I have been trying to make provision for this nand flash
unsuccessfully. I take a look to sprufb3.pdf (TMS320DM355 (DMSoC) ARM
Subsystem), and in chapter 11, section 11.1.1 (page 150), i have found
that nand devices supported allows a maximum page size of 2048 bytes.
Can anybody confirm is this holds true? Because this new nand device
has a page size of 4096 bytes, and I think this may be the problem I am
having.
Does anybody know of other nand devices that are supported (without
changes to UBL, u-boot, etc) that haven't bees discontinued?
Thanks in advance,
A.Silva
On Tue, Sep 30, 2008 at 4:39 PM, Paulraj,
Sandeep <[email protected]>
wrote:
There
should be provision for this chip
in both U-Boot and UBL.
IN UBL
source there is a structure gNandDevInfo.
If you have a look it has no entry for this device. You will have to
fill it up
appropriately.
Also in
U-boot nand_ids.c needs to be
updated.
Thanks,
Sandeep
From: António Silva
[mailto:[email protected]]
Sent: Tuesday,
September 30, 2008
11:27 AM
To: Paulraj, Sandeep
Subject: Re: Problem
with u-boot
and flash MT29F16G08DAA
Hi Sandeep,
When I perform nad info I get the following:
Device 0: NAND 1GiB 3,3V 8-bit, sector size 256 KiB
Device 1: NAND 1GiB 3,3V 8-bit, sector size 256 KiB
This is the dump when u-boot starts:
this is MT29F16G08QAA device
UBL: detected valid U-Boot magic number
UBL: booting to U-Boot
U-Boot 1.2.0 (Feb 2 2008 - 23:52:10)
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND
1GiB
3,3V 8-bit)
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB
3,3V 8-bit)
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
2048 MiB
In: serial
Out: serial
Err: serial
ARM Clock :- 216MHz
DDR Clock :- 171MHz
Hit any key to stop autoboot: 0
Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000
** Bad Magic Number 0xb1aced22 **
## Booting image at 80700000 ...
Bad Magic Number
I Know we have to perform some changes because the two flash memories
have a
slight difference. I just get confused with this bahaviour, because the
first
time it boots it is all fine, but when I get the u-boot prompt and do
the
saveenv command, i get the erros I reported.
I just want to clear out where do I have to perform changes, wheter in
u-boot
or/and UBL.
Thanks in advance, best regards,
A.Silva
On Tue, Sep 30, 2008 at 4:14 PM, Paulraj,
Sandeep <[email protected]>
wrote:
Antonio,
The problem might be due to the fact that UBL?U-Boot do not have the
relevant
info for this new chip in the UBL/U-Boot source. You will have to add
the
relevant info such as the block size, etc in the appropriate places in
the
UBL/U-Boot source. Basically the wrong NAND is getting detected. This
makes me
believe that these two are indeed very similar but there are minor
differences
which messes things up.
Also when
you manage to get the U-Boot prompt.
Please do a
nand info
I want to
see that dump. If possible also give
me a dump of what shows up when U-Boot starts.
Thanks,
Sandeep
From: António Silva [mailto:[email protected]]
Sent: Tuesday,
September 30, 2008
10:48 AM
To: Paulraj, Sandeep
Subject: Re: Problem
with u-boot
and flash MT29F16G08DAA
That's
just a print, in the first time the board boots after loading UBL and
u-boot it
prints that string and boot just fine. This print is from UBL, but the
problem
doesn't seems to be in UBL but in u-boot because it is after I perform
saveenv that UBL cannot load u-boot again.
On Tue,
Sep 30, 2008 at 3:43 PM, Paulraj, Sandeep <[email protected]>
wrote:
The answer
is in the e-mail itself. Have a look
at the part numbers.
MT29F16G08DAA
is what it is supposed to be and
MT29F16G08QAA
is what is getting detected.
Thanks,
Sandeep
Hi all,
The default flash that came with the evmdm355 has been discontinued and
the
replacement from Micron is MT29F16G08DAA.
The flash is very similar, I perform all tests and passes and in fact
with CCS
I can load UBL and u-boot perfectly. But in u-boot if I try to perform
saveenv
it cannot write to flash and I get the following errors:
this is MT29F16G08QAA device
UBL: Failed to read app descriptor
UBL: NANDBoot() failed
It seems like when u-boot is trying to save its enviroment variables it
is
writing to a bad location, and erases the location of the u-boot magic
number
and UBL cannot load u-boot again.
Does anyone has this problem before?
Thanks in advance,
A.Silva
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
What was the eventual resolution for this issue? Is the DMT29F16G08DAA
supported by the RBL of the DM355?
|
