Error in buffer data for NAND flash write, read on OMAP3430SDP.
Hi All,
I am using NAND Flash write, read APIs for writing and reading of my data to/from the same block.
[SNIP]
OMAP34XX SDP # nand dua//I created this command
The manufacturer id = 2c
device Id = a1
Erasing at 0x01440000 -- 100% complete. Cleanmarker written at 0x01440000 .
ERASE OK
Writing data at 0x01440000 -- 100% complete.
WRITE OK
Reading data from 0x01440000 -- 100% complete.
READ OK
OMAP34XX SDP #
But when I compare write buffer and read buffer,some of the data is not matching(read data is different from write data).
Could some one tell me the solution for this.
Regards,
Krishna.
Krishna,
Quoted 7 lines · Radha Krishna
Hi All,
I am using NAND Flash write, read APIs for writing and reading of my data to/from the same block.
[SNIP]
OMAP34XX SDP # nand dua//I created this command
Can you give details what this custom command is doing? See below, too.
Quoted 11 lines
The manufacturer id = 2c
device Id = a1
Erasing at0x01440000-- 100% complete. Cleanmarker written at0x01440000.
ERASE OK
Writing data at0x01440000-- 100% complete.
WRITE OK
Reading data from0x01440000-- 100% complete.
READ OK
OMAP34XX SDP #
Quoted 5 lines
But when I compare write buffer and read buffer,some of the data is not matching(read data is different from write data).
Could some one tell me the solution for this.
Can you give complete log and more details of what you are doing, i.e. complete output from board boot on? What would be helpful:
- U-Boot version, where do you got it from
- printenv output (showing the native commands for your "nand dua" above).
- Which data you are writing. Can you try it with some dummy data you can share here making other people able to test this. Maybe you can create some easy test data with mw.w and mm.l commands (e.g. writing all zero's or some other dummy data)
- How do you compare the data
- Other useful info
Many thanks
Dirk
Hi Dirk,
Thanks for the response.
Here are the details
nand dua ...this commad is simple and executes nand erase,nand write and nand read APIs. Write data and read data are like 1,2,3,4,5....131072.
For comparing byte by byte data, using two buffers write_buffer, read_buffer both are of size 131072.
U-boot version:
U-Boot uses a 3 level version number containing a version, a sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2", sub-version "34", and patchlevel "4".
I got the U-boot from the URL:
https://omapzoom.org/gf/project/bootloader/frs/
Please let me know for any other information.
Thanks,
krishna.
Quoted 54 lines · Dirk Behme
From: Dirk Behme <[email protected]>
Subject: Re: [U-Boot] Error in buffer data for NAND flash write, read on OMAP3430SDP.
To:hi_krishna01at yahoo.com
Cc: u-boot at lists.denx.de
Date: Tuesday, December 23, 2008, 10:26 PM
Krishna,Quoted 2 lines · Radha Krishna
Hi All,
I am using NAND Flash write, read APIs for writingand
Quoted 3 lines
reading of my data to/from the same block.
[SNIP]
OMAP34XX SDP # nand dua//I created this commandCan you give details what this custom command is doing? See below, too.
Quoted 3 lines
The manufacturer id = 2c
device Id = a1
Erasing at0x01440000-- 100% complete. Cleanmarkerwritten
Quoted 8 lines
at
0x01440000.
ERASE OK
Writing data at0x01440000-- 100% complete.
WRITE OK
Reading data from0x01440000-- 100% complete.
READ OK
OMAP34XX SDP #
But when I compare write buffer and read buffer,someof the
Quoted 1 line
data is not matching(read data is different from
write
Quoted 2 lines
data).
Could some one tell me the solution for this.Can you give complete log and more details of what you are doing, i.e. complete output from board boot on? What would be helpful:
- U-Boot version, where do you got it from
- printenv output (showing the native commands for your "nand dua" above).
- Which data you are writing. Can you try it with some dummy data you can share here making other people able to test this. Maybe you can create some easy test data with mw.w and mm.l commands (e.g. writing all zero's or some other dummy data)
- How do you compare the data
- Other useful infoMany thanks
Dirk
Radha Krishna said the following on 12/24/2008 01:37 AM:
Quoted 4 lines
nand dua ...this commad is simple and executes nand erase,nand write and nand read APIs. Write data and read data are like 1,2,3,4,5....131072.
For comparing byte by byte data, using two buffers
write_buffer,read_bufferboth are of size 131072.
Quoted 9 lines
U-boot version:
U-Boot uses a 3 level version number containing a version, a sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2", sub-version "34", and patchlevel "4".I got the U-boot from the URL:
https://omapzoom.org/gf/project/bootloader/frs/
I think you are with a really old U-Boot if the above is the place you picked it from! if you look up the boot message it probably should be 1.1.5 or something of that revision. You can find the old revision in [1]. We are attempting to merge in patches to the very latest 1.5 release which still does not have SDP3430 support (but can be done with a little effort). You can see this new community initiative for a mainstream OMAP3 U-Boot in [2] - but note, it is still a work in progress and yet to be accepted in the mainline tree (But I guess we are getting pretty close to it now)..
Regards,
Nishanth Menon
Ref:
[1] http://git.omapzoom.org/?p=u-boot.git;a=summary
[2]
http://git.sakoman.net/cgi-bin/gitweb.cgi?p=u-boot-omap3.git;a=shortlog;h=refs/heads/omap3-dev
Nishanth Menon said the following on 12/24/2008 07:41 AM:
Quoted 12 lines
Radha Krishna said the following on 12/24/2008 01:37 AM:
Quoted 5 lines
I got the U-boot from the URL:
https://omapzoom.org/gf/project/bootloader/frs/I think you are with a really old U-Boot if the above is the place you picked it from! if you look up the boot message it probably should be 1.1.5 or something of that revision. You can find the old revision in [1].
<snip>
Quoted 2 lines
One more minor item of interest - for the u-boot
pulled from omapzoom.org, you may be interested in contacting either [1] or [2].
Regards,
Nishanth Menon
Ref:
[1] http://vger.kernel.org/vger-lists.html#linux-omap
[2] https://omapzoom.org/mailman/listinfo/omapandroid-discussion