From: Bo Shen <voice.shen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Remounting UBI image leads to ECC errors
Date: Mon, 4 Mar 2013 11:25:42 +0800 [thread overview]
Message-ID: <51341436.4080000@atmel.com> (raw)
In-Reply-To: <512CD0A8.9030209@mimc.co.uk>
Hi Mark,
On 02/26/2013 11:11 PM, Mark Jackson wrote:
> We have a custom made AM335x board I'm working on and I have encountered
> a problem when mounting an ubifs image from nand. If I ...
>
> (1) Write an ubifs image to nand
> (2) Mount the ubifs image
> (3) Repeat step (2)
>
> ... this then corrupts the ubifs image.
>
> Below is a full log.
>
> Can anyone help ?
>
> Regards
> Mark J.
> ---
> U-Boot SPL 2013.01-00336-g044fbc4-dirty (Feb 26 2013 - 14:07:36)
> U-Boot 2013.01-00336-g044fbc4-dirty (Feb 26 2013 - 14:07:36)
> I2C: ready
> DRAM: 256 MiB
> WARNING: Caches not enabled
> NAND: 256 MiB
> MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
> musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
> musb-hdrc: MHDRC RTL version 2.0
> musb-hdrc: setup fifo_mode 4
> musb-hdrc: 28/31 max ep, 16384/16384 memory
> USB Host mode controller at 47401000 using PIO, IRQ 0
> Net: cpsw
> U-Boot# nandecc hw 2
> HW BCH8 selected
> U-Boot# mw.b 82000000 ff 81f000
> U-Boot# dhcp 82000000 10.0.0.100:/nanobone/rootfs.ubifs
> link up on port 0, speed 100, full duplex
> BOOTP broadcast 1
> *** Unhandled DHCP Option in OFFER/ACK: 46
> *** Unhandled DHCP Option in OFFER/ACK: 46
> DHCP client bound to address 10.0.0.104
> Using cpsw device
> TFTP from server 10.0.0.100; our IP address is 10.0.0.104
> Filename '/nanobone/rootfs.ubifs'.
> Load address: 0x82000000
> Loading: #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #################################################################
> #####################
> 657.2 KiB/s
> done
> Bytes transferred = 6029312 (5c0000 hex)
> U-Boot# nand erase 200000 4000000
>
> NAND erase: device 0 offset 0x200000, size 0x4000000
> Erasing at 0x41e0000 -- 100% complete.
> OK
> U-Boot# nand write 82000000 200000 81f000
Please try to write with sub command trimffs. The command looks like
nand write.trimffs 82000000 200000 81f000
If not has trimffs sub command, please add CONFIG_CMD_NAND_TRIMFFS into
board configuration file.
Best Regards,
Bo Shen
prev parent reply other threads:[~2013-03-04 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 15:11 [U-Boot] Remounting UBI image leads to ECC errors Mark Jackson
2013-03-02 10:43 ` Mark Jackson
2013-03-04 3:25 ` Bo Shen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51341436.4080000@atmel.com \
--to=voice.shen@atmel.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox