From: Nataraj S Narayan <natarajsn@gmail.com>
To: barebox@lists.infradead.org
Subject: Re: at91sam9263ek, few issues
Date: Fri, 12 Aug 2011 13:38:37 +0000 [thread overview]
Message-ID: <CAK8HZOL36gu_PNR6OFuqsFb+LD==9igWYOPFT9+T4GUwxLNtyA@mail.gmail.com> (raw)
In-Reply-To: <CAK8HZO+mfyaj9CPUB+nOzppz_+=o5xzpgsDOofV=1jF9rcR2yQ@mail.gmail.com>
Hi
Changed nand_chip_delay =50 from 20 in
./drivers/mtd/nand/atmel_nand.c, and presently getting:-
barebox@Atmel at91sam9263-ek:/ ubiattach /dev/nand0.root
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
registering /dev/ubi0
UBI: attached mtd0 to ubi0
UBI: MTD device name: "nand0.root"
UBI: MTD device size: 254 MiB
UBI: number of good PEBs: 2028
UBI: number of bad PEBs: 5
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 2004
UBI: total number of reserved PEBs: 24
UBI: number of PEBs reserved for bad PEB handling: 20
UBI: max/mean erase counter: 1/1
But further giving a
barebox@Atmel at91sam9263-ek:/ tftp rootfs1.ubif /dev/ubi0
TFTP from server 192.168.0.110 ('rootfs1.ubif' -> '/dev/ubi0')
write: No space left on device
tftp failed: error -28
Btw , which is the irc channel of Barebox?
regards
Nataraj
On Fri, Aug 12, 2011 at 6:45 AM, Nataraj S Narayan <natarajsn@gmail.com> wrote:
> Hi
>
> The following is the gist of issues seen, namely
>
> 1. unable to saveenv
> 2. ubiattach issue.
>
> I am using NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung
> NAND 256MiB 3,3V 8-bit).
>
> Please help
>
> regards
>
> Nataraj
>
> barebox@Atmel at91sam9263-ek:/ eth0.serverip=192.168.0.110
> barebox@Atmel at91sam9263-ek:/ eth0.ipaddr=192.168.0.105
>
> barebox@Atmel at91sam9263-ek:/ saveenv
> saving environment
> could not open /dev/env0: Read-only file system
>
> barebox@Atmel at91sam9263-ek:/ printenv
> locals:
> ip=dhcp
> kernel_loc=tftp
> rootfs_loc=net
> rootfs_type=ubifs
> rootfsimage=root.ubifs
> kernelimage_type=uimage
> kernelimage=uImage
> nand_device=atmel_nand
> nand_parts=256k(barebox)ro,128k(bareboxenv),1536k(kernel),-(root)
> rootfs_mtdblock_nand=3
> autoboot_timeout=3
> bootargs=console=ttyS0,115200
> PS1=\e[1;32mbarebox@\e[1;31m\h:\w\e[0m
> globals:
> PATH=/env/bin
>
>
>
>
> barebox@Atmel at91sam9263-ek:/ ubiattach dev/nand0.root
> UBI: attaching mtd0 to ubi0
> UBI: physical eraseblock size: 131072 bytes (128 KiB)
> UBI: logical eraseblock size: 126976 bytes
> UBI: smallest flash I/O unit: 2048
> UBI: VID header offset: 2048 (aligned 2048)
> UBI: data offset: 4096
> UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 0:0,
> read 64 bytes
> UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB
> 476:0, read 64 bytes
> UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB
> 489:0, read 64 bytes
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-08-12 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 6:45 Nataraj S Narayan
2011-08-12 13:38 ` Nataraj S Narayan [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='CAK8HZOL36gu_PNR6OFuqsFb+LD==9igWYOPFT9+T4GUwxLNtyA@mail.gmail.com' \
--to=natarajsn@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