2 вопроса - почему в логе nand - 512mb и бэд блоки?
Фотографии платы и используемого блока питания приложены.
Сам лог:

RomBOOT
>Run ...


U-Boot 2010.03 (Apr 21 2010 - 18:56:06)

DRAM: 32 MB
NAND: 256 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: macb0
macb0: PHY present at 1
macb0: Starting autonegotiation...
macb0: Autonegotiation timed out (status=0x7849)
macb0: link down (status: 0x7849)
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x60000, size 0x780000
7864320 bytes read: OK
## Booting kernel from Legacy Image at 20400000 ...
Image Name: Linux Kernel Image
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 4438174 Bytes = 4.2 MB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK

Starting kernel ...

Linux version 2.6.28 (user@debian) (gcc version 4.2.0 20070413 (prerelease) (CodeSourcery Sourcery G++ Lite 2007q1-10)) #46 Sat Mar 27 17:36:08 EDT 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Starterkit.ru SK-AT91SAM9XXXXX-SIMXXX
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 200 MHz, master 100 MHz, main 12.000 MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: root=/dev/ram0 rw initrd=0x23100000,0x800000 console=ttyS0,115200 mem=64M
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 50564KB available (2988K code, 238K data, 2880K init)
Calibrating delay loop... 99.73 BogoMIPS (lpj=498688)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 288 bytes
NET: Registered protocol family 16
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
Freeing initrd memory: 8192K
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (SUMMARY) бL 2001-2006 Red Hat, Inc.
yaffs Mar 27 2010 12:35:28 Installing.
msgmni has been set to 114
io scheduler noop registered (default)
Console: switching to colour frame buffer device 60x34
fb0: Hecuba frame buffer device, using 510K of video memory
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb8000 (irq = 8) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
ssc ssc.0: Atmel SSC device at 0xc48f8000 (irq 14)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:1f:f2:00:00:00)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01, irq=-1)
Driver 'sd' needs updating - please use bus_type methods
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 87 at 0x00ae0000
Bad eraseblock 334 at 0x029c0000
Bad eraseblock 526 at 0x041c0000
Bad eraseblock 1082 at 0x08740000
Bad eraseblock 1157 at 0x090a0000
Bad eraseblock 1165 at 0x091a0000
Bad eraseblock 1459 at 0x0b660000
Bad eraseblock 1516 at 0x0bd80000
Bad eraseblock 1555 at 0x0c260000
Bad eraseblock 1753 at 0x0db20000
Bad eraseblock 2010 at 0x0fb40000
Creating 2 MTD partitions on "atmel_nand":
0x00000000-0x00800000 : "Partition 1"
0x00800000-0x10000000 : "Partition 2"
atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffcc000 (irq 13)
usbmon: debugfs is not available
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
input: HP Jornada touchscreen as /class/input/input0
i2c /dev entries driver
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.18rc3.
tlv320aic23b spi1.0: tlv320aic23b: supported bitrate is 47348 (66 divider)
ALSA device list:
#0: AT91SAM9260 external CODEC on irq 14
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
Freeing init memory: 2880K
Initializing random number generator... done.
Starting network...
route: SIOCADDRT: File exists
Starting vsftpd: start-stop-daemon: applet not found
yaffs: dev is 32505857 name is "mtdblock1"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.1, "mtdblock1"
yaffs: auto selecting yaffs2
block 24 is bad
block 271 is bad
block 463 is bad
block 1019 is bad
block 1094 is bad
block 1102 is bad
block 1396 is bad
block 1453 is bad
block 1492 is bad
block 1690 is bad
block 1947 is bad
yaffs_read_super: isCheckpointed 0
tlv320aic23b: playback bitrate is 47348 (66 divider)


Welcome to SK-AT91SAM9XXXXX-SIMXXX development board!

Цитата

DRAM: 32 MB
NAND: 256 MiB

Цитата

NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)

где еще упоминается Nand (512MB)?

о бед-блоках. практически во всех доках на чипы есть примерно такой абзац:

Код

Micron NAND devices are specified to have a minimum of 2,008 (NVB) valid blocks out
of every 2,048 total available blocks. This means the devices may have blocks that are
invalid when they are shipped. An invalid block is one that contains one or more bad
bits. Additional bad blocks may develop with use. However, the total number of available
blocks will not fall below NVB during the endurance life of the product.
Although NAND memory devices may contain bad blocks, they can be used quite reliably
in systems that provide bad-block mapping, replacement, and error correction
algorithms. This type of software environment ensures data integrity.
Internal circuitry isolates each block from other blocks, so the presence of a bad block
does not affect the operation of the rest of the Flash device.
The first block (physical block address 00h) for each CE# in Micron NAND devices is
guaranteed to be free of defects (up to 1,000 PROGRAM/ERASE cycles) when shipped
from the factory. This provides a reliable location for storing boot code and critical boot
information.

Цитата

где еще упоминается Nand (512MB)?

Я опечатался, хотел сказать что в логе - 256, а должно быть разве не 512?

Цитата

Я опечатался, хотел сказать что в логе - 256, а должно быть разве не 512?

может у вас спецзаказ? что написано в спецификации на заказ?