mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: R Arun Kumar <paiarunk@gmail.com>
To: barebox@lists.infradead.org
Subject: Regarding nandwrite issue for huge files ?
Date: Fri, 12 Feb 2010 12:32:19 +0530	[thread overview]
Message-ID: <faef843a1002112302u6b80cb57we22db316d94e792e@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3297 bytes --]

Hai,

I am able to successfully port the barebox for my custom IMX31 board and
also boot linux on the same.
I am trying to write the uImage and the root.jffs2 file from barebox and
found that even though uImage is written successfully and able to boot from
nand flash also. The nand file write for files more than 3.5 mega size is
not able to write and the barebox loader is hanged.

Please help or suggest what could be the issue ?

Arun

my log
===============================

barebox 2009.12.0 (Feb 12 2010 - 12:19:11)

Board: Phytec phyCORE-i.MX31
cfi_probe: cfi_flash base: 0xa0000000 size: 0x02000000

NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB
3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 2046 at 0x0ffc0000
Bad eraseblock 2047 at 0x0ffe0000
got MAC address from EEPROM: 00:08:EE:01:86:71
Malloc space: 0x87b00000 -> 0x87f00000 (size  4 MB)
Stack space : 0x87af8000 -> 0x87b00000 (size 32 kB)
envfs: wrong magic on /dev/env0
no valid environment found on /dev/env0. Using default environment
running /env/bin/init...

Hit any key to stop autoboot:  3

type update_kernel nand|nor [<imagename>] to update kernel into flash
type update_root nand|nor [<imagename>] to update rootfs into flash

barebox:/ devinfo
devices:
|----imx_serial0
|----cs0
|----ramfs0
|----devfs0
|----mem0 (defaultenv)
|----mem1 (mem)
|----cfi_flash0 (nor0, self0, env0, nor0.barebox, nor0.bareboxenv,
nor0.kernel, nor0.root)
|----mem2 (sram0)
|----imx_nand0
|----nand0 (nand0, nand_oob0, nand0.kernel, nand0.root)
|----smc911x0
|----miiphy0 (phy0)
|----eth0
|----mem3 (ram0)

drivers:
imx_serial
     ramfs
     devfs
   smc911x
    miiphy
  imx_nand
 cfi_flash
       mem
barebox:/ erase /dev/nand0.kernel.bb
barebox:/
barebox:/
barebox:/ tftp uImage_080210 /dev/nand0.kernel.bb
phy0: Link is up - 100/Full
TFTP from server 192.168.50.247; our IP address is 192.168.50.182

Filename 'uImage_080210'.
Loading: *\b#################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ###############################
done
Bytes transferred = 1822080 (1bcd80 hex)
barebox:/
barebox:/
barebox:/
barebox:/

barebox:/ erase /dev/nand0.root.bb
Skipping bad block at 0x0ffc0000
Skipping bad block at 0x0ffe0000
barebox:/
barebox:/
barebox:/
barebox:/ tftp root-pcm037.jffs2 /dev/nand0.root.bb
phy0: Link is up - 100/Full
TFTP from server 192.168.50.247; our IP address is 192.168.50.182

Filename 'root-pcm037.jffs2'.
Loading: *\b#################################################################
	 #################################################################
	 #################################################################
	 ############################################################T #####
	 #################################################################
	 #################################################################
	 #####################(hanged)




===============================

[-- Attachment #1.2: Type: text/html, Size: 3726 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2010-02-12  7:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  7:02 R Arun Kumar [this message]
2010-02-12  7:30 ` Sascha Hauer

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=faef843a1002112302u6b80cb57we22db316d94e792e@mail.gmail.com \
    --to=paiarunk@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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