kernal flashing for dm6446 board

parwath r

Intellectual 510 points

can anyone help me to solve this problem?

i am flashing kernal to DM6446 nand flash. i am facing error while flashing which i attached above.

i followed below link:

please help me to solve

Thanks and regards

Parwath

over 9 years ago

0 Titusrathinaraj Stalin over 9 years ago

TI__Guru** 116100 points

Dear Parwath,
1) Set the IP address for your target board
2) Assign the server IP in u-boot where you have kernel image.
3) Loading the kernel image into RAM
4) Flash into kernel.
5) Set u-boot bootcmd to boot the kernel from NAND flash
6) Try to flash the filesystem via NFS booting or write the filesystem in u-boot itself (if DM6446EVM supports)

Ex:
setenv ipaddr 10.100.1.20
setenv serverip 10.100.1.25
tftp 0x80700000 uImage-dm644x-evm.bin
nand erase 0x60000 0x200000
nand write 0x80700000 0x60000 0x200000
setenv bootcmd 'nboot 0x80700000 0 0x60000; bootm'

0 parwath r over 9 years ago in reply to Titusrathinaraj Stalin

Intellectual 510 points

thanks Titusrathinaraj,

after your suggestion

Fullscreen kernel_flashing_log.txt Download

Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000006.
   DONE
Jumping to entry point at 0x81080000.


U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

I2C:   ready
DRAM:  256 MB
NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit)
64 MiB
In:    serial
Out:   serial
Err:   serial
ARM Clock: 405MHz
DDR Clock: 189MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot:  0 

Loading from NAND 64MiB 1,8V 8-bit, offset 0x60000
   Image Name:   Arago/2.6.31+2.6.32-rc1-r37+gitr
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1893880 Bytes =  1.8 MB
   Load Address: 80008000
   Entry Point:  80008000
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Arago/2.6.31+2.6.32-rc1-r37+gitr
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1893880 Bytes =  1.8 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................... done, booting the kernel.
Linux version 2.6.32-rc2-davinci1 (davinci@localhost.localdomain) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 PREEMPT Mon Jun 21 16:46:22 IST 2010
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: DaVinci DM644x EVM
Memory policy: ECC disabled, Data cache writeback
DaVinci dm6446a variant 0x1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 30480
Kernel command line: mem=120M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x82000000,4M ip=dhcp
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 120MB = 120MB total
Memory: 113464KB available (3556K code, 327K data, 124K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:245
Console: colour dummy device 80x30
Calibrating delay loop... 201.93 BogoMIPS (lpj=1009664)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
DaVinci: 71 gpio irqs
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pcf857x 1-0038: gpios 144..151 on a pcf8574
pcf857x 1-0039: gpios 152..159 on a pcf8574
pcf857x 1-003a: gpios 160..167 on a pcf8574
vpss vpss: dm644x_vpss vpss probed
vpss vpss: dm644x_vpss vpss probe success
ch0 default output "COMPOSITE", mode "NTSC"
VPBE Encoder Initialized
LogicPD encoder initialized
Switching to clocksource timer0_1
musb_hdrc: version 6.0, cppi-dma, host, debug=0
musb_hdrc: USB Host mode controller at fec64000 using DMA, IRQ 12
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (junk in compressed archive); looks like an initrd
Freeing initrd memory: 4096K
msgmni has been set to 229
io scheduler noop registered
io scheduler anticipatory registered (default)
Console: switching to colour frame buffer device 90x30
davincifb davincifb: dm_osd0_fb: 720x480x16@0,0 with framebuffer size 675KB
davincifb davincifb: dm_vid0_fb: 0x0x16@0,0 with framebuffer size 1020KB
davincifb davincifb: dm_osd1_fb: 720x480x4@0,0 with framebuffer size 675KB
davincifb davincifb: dm_vid1_fb: 0x0x16@0,0 with framebuffer size 1020KB
davincifb davincifb.0: dm_osd0_fb: Failed to obtain ownership of OSD window.
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
console [ttyS0] enabled
serial8250 serial8250.0: unable to register port at index 1 (IO0 MEM1c20400 IRQ41): -22
serial8250 serial8250.0: unable to register port at index 2 (IO0 MEM1c20800 IRQ42): -22
brd: module loaded
at24 1-0050: 32768 byte 24c256 EEPROM (writable)
Read MAC addr from EEPROM: 00:0e:99:02:43:b1
Uniform Multi-Platform E-IDE driver
ide-gd driver 1.18
    ide0: MMIO-DMA
ide0 at 0xfec661f0-0xfec661f7,0xfec663f6 on irq 22
console [netcon0] enabled
netconsole: network logging started
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbtest
i2c /dev entries driver
Linux video capture interface: v2.00
vpfe_init
vpfe-capture: vpss clock vpss_master enabled
vpfe-capture: vpss clock vpss_slave enabled
vpfe-capture vpfe-capture: v4l2 device registered
vpfe-capture vpfe-capture: video device registered
tvp514x 1-005d: tvp514x 1-005d decoder driver registered !!
vpfe-capture vpfe-capture: v4l2 sub device tvp514x registered
vpfe_register_ccdc_device: DM6446 CCDC
DM6446 CCDC is registered with vpfe.
Trying to register davinci display video device.
layer=c67d9600,layer->video_dev=c67d9770
Trying to register davinci display video device.
layer=c67d9c00,layer->video_dev=c67d9d70
davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
watchdog watchdog: heartbeat 60 sec
davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
No device for DAI tlv320aic3x
No device for DAI davinci-i2s
asoc: tlv320aic3x <-> davinci-i2s mapping ok
ALSA device list:
  #0: DaVinci EVM (tlv320aic3x)
TCP cubic registered
NET: Registered protocol family 17
Clocks: disable unused uart1
Clocks: disable unused uart2
Clocks: disable unused emac
Clocks: disable unused spi
Clocks: disable unused vlynq
Clocks: disable unused pwm0
Clocks: disable unused pwm1
Clocks: disable unused pwm2
Clocks: disable unused timer1
emac-mii: probed
eth0: attached PHY driver [LXT971] (mii_bus:phy_addr=1:01, id=1378e2)
Sending DHCP requests .
PHY: 1:01 - Link is Up - 100/Full
., OK
IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.101
IP-Config: Complete:
     device=eth0, addr=192.168.1.101, mask=255.255.255.0, gw=192.168.1.1,
     host=dhcppc1, domain=, nis-domain=(none),
     bootserver=192.168.1.1, rootserver=192.168.1.1, rootpath=
RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions:
No filesystem could mount root, tried:  ext3 ext2 cramfs vfat msdos
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
Backtrace: 
[<c002b7f0>] (dump_backtrace+0x0/0x114) from [<c02c5300>] (dump_stack+0x18/0x1c)
 r7:00008000 r6:c6012000 r5:c0023808 r4:c03c62b0
[<c02c52e8>] (dump_stack+0x0/0x1c) from [<c02c5358>] (panic+0x54/0x124)
[<c02c5304>] (panic+0x0/0x124) from [<c0008fbc>] (mount_block_root+0x1e0/0x220)
 r3:00000000 r2:00000020 r1:c6025f60 r0:c0349f2d
[<c0008ddc>] (mount_block_root+0x0/0x220) from [<c00090c0>] (mount_root+0xc4/0xfc)
 r8:00000000 r7:00000000 r6:00000000 r5:c0023808 r4:00100000
[<c0008ffc>] (mount_root+0x0/0xfc) from [<c0009268>] (prepare_namespace+0x170/0x1c8)
 r5:c0023808 r4:c03c5da0
[<c00090f8>] (prepare_namespace+0x0/0x1c8) from [<c00084bc>] (kernel_init+0xe4/0x118)
 r5:00000000 r4:c03c5b60
[<c00083d8>] (kernel_init+0x0/0x118) from [<c0040250>] (do_exit+0x0/0x684)
 r5:00000000 r4:00000000

i flashed kernel image but i m confused wether i flashed kernel image properly or not. it stucked in middle i attched the log file also please take a look and suggest me

0 Titusrathinaraj Stalin over 9 years ago in reply to parwath r

TI__Guru** 116100 points

Log seems to be kernel booted well and stuck at filesystem stage.
Sounds like you need to flash the RAMDISK filesystem.

Please do the following commands to boot the linux on DM6446 (flashing the ramdisk image)

tftp 0x82000000 arago-base-image-arago.ext2.gz
nand erase 0x460000 0x300000
nand write 0x82000000 0x460000 0x300000
setenv bootcmd 'nand read 0x82000000 0x460000 0x300000; nboot 0x80700000 0 0x60000; bootm'
saveenv

0 parwath r over 9 years ago in reply to parwath r

Intellectual 510 points

i m getting the follwoing error how to make it work
No output after uncompressing kernel,

TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000006.
DONE
Jumping to entry point at 0x81080000.

U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

I2C: ready
DRAM: 256 MB
NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit)
64 MiB
In: serial
Out: serial
Err: serial
ARM Clock: 405MHz
DDR Clock: 189MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot: 0
U-Boot >
U-Boot > <INTERRUPT>
U-Boot > DM644x_810MHz initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000006.
DONE
Jumping to entry point at 0x81080000.

U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

I2C: ready
DRAM: 256 MB
NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit)
64 MiB
In: serial
Out: serial
Err: serial
ARM Clock: 405MHz
DDR Clock: 189MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot: 0
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4

Abort
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................... done, booting the kernel.

0 Titusrathinaraj Stalin over 9 years ago in reply to parwath r

TI__Guru** 116100 points

U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

I2C: ready
DRAM: 256 MB
NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit)
64 MiB
In: serial
Out: serial
Err: serial
ARM Clock: 405MHz
DDR Clock: 189MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot: 0
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4

Abort
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Why the abort is happened ?

You should get the log like below.

U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

I2C: ready
DRAM: 256 MB
NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit)
64 MiB
In: serial
Out: serial
Err: serial
ARM Clock: 405MHz
DDR Clock: 189MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot: 0

Loading from NAND 64MiB 1,8V 8-bit, offset 0x60000
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Don't do "ctrl+c" while reading the kernel from NAND flash....just give "boot" command or simply reset the board & wait for boot complete .

0 parwath r over 9 years ago in reply to Titusrathinaraj Stalin

Intellectual 510 points

still i m getting that abort if i am not entered it will go like BOOTP broadcast 1
BOOTP broadcast 2 contineously its going wat i have to do now

0 parwath r over 9 years ago in reply to Titusrathinaraj Stalin

Intellectual 510 points

I2C: ready
DRAM: 256 MB
NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit)
64 MiB
In: serial
Out: serial
Err: serial
ARM Clock: 405MHz
DDR Clock: 189MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot: 0

Loading from NAND 64MiB 1,8V 8-bit, offset 0x60000
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................... done, booting the kernel.

it is strucking here itself only i m not getting wat to do plaese suggest me

thanks and regards
parwath r

0 Titusrathinaraj Stalin over 9 years ago in reply to parwath r

TI__Guru** 116100 points

Provide the output of "printenv" u-boot command.

u-boot# printenv

Try the following command and do "saveenv' & check whether you could boot.

setenv bootcmd 'nboot 0x80700000 0 0x60000; bootm'
saveenv

0 parwath r over 9 years ago in reply to parwath r

Intellectual 510 points

U-Boot > tftp 0x82000000 arago-demo-image-glibc-ipk-2009.11-dm6446-evm.rootfs.ext2
Booting with RAMDISK as a root filesystem
i followd the bello link
processors.wiki.ti.com/.../UG:_DaVinci_PSP_Installation_on_DM644x_EVM

but still i m not getting its strucked what i have to do now is there any other way to do this plaease suggest me i attched the log bellow

TFTP from server 192.168.1.110; our IP address is 192.168.1.101
Filename 'arago-demo-image-glibc-ipk-2009.11-dm6446-evm.rootfs.ext2'.
Load address: 0x82000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###########
done
Bytes transferred = 33554432 (2000000 hex)
U-Boot > nand erase 0x460000 0x300000

NAND erase: device 0 offset 0x460000, size 0x300000
Erasing at 0x75c000 -- 100% complete.
OK
U-Boot > nand write 0x82000000 0x460000 0x300000

NAND write: device 0 offset 0x460000, size 0x300000
3145728 bytes written: OK
U-Boot > setenv bootcmd 'nand read 0x82000000 0x460000 0x300000; nboot 0x80700000 0 0x60000; bootm'
U-Boot > setenv bootargs mem=120M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x82000000,4M ip=dhcp
U-Boot > DM644x_810MHz initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000006.
DONE
Jumping to entry point at 0x81080000.

U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

I2C: ready
DRAM: 256 MB
NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit)
64 MiB
In: serial
Out: serial
Err: serial
ARM Clock: 405MHz
DDR Clock: 189MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot: 0

Loading from NAND 64MiB 1,8V 8-bit, offset 0x60000
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................... done, booting the kernel.

--parwath r

0 Titusrathinaraj Stalin over 9 years ago in reply to parwath r

TI__Guru** 116100 points

Dear Parwath,

I think, the below bootcmd is causing this hang problem.
setenv bootcmd 'nand read 0x82000000 0x460000 0x300000; nboot 0x80700000 0 0x60000; bootm'

So, can you please try the following command instead ?
setenv bootcmd 'nboot 0x80700000 0 0x60000; bootm'

Please try the above command and let me know whether you could boot the kernel without any hang.

0 parwath r over 9 years ago in reply to Titusrathinaraj Stalin

Intellectual 510 points

U-Boot > printenv
i tried with your command also still its giving same problem no changes in output. bellow is the details printenv and log also i attched please take a look and suggest me.

bootdelay=3
baudrate=115200
ethaddr=00:0E:99:02:43:B1
loadaddr=0x80700000
rootpath=/home/yash12/workdir1/filesys
nfshost=192.168.1.1
bootargs=video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=$(videostd) console=/dev/ttyUSB0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=120M
bootfile=/var/lib/tftpboot/uImage-dm6446-evm.bin
filesize=1CE638
fileaddr=80700000
netmask=255.255.255.0
ipaddr=192.168.1.101
serverip=192.168.1.112
bootcmd=nboot 0x80700000 0 0x60000; bootm
stdin=serial
stdout=serial
stderr=serial
videostd=ntsc
ver=U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

Environment size: 701/16380 bytes
U-Boot > DM644x_810MHz initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000006.
DONE
Jumping to entry point at 0x81080000.

U-Boot 2009.03 (Jun 21 2010 - 16:30:08)

I2C: ready
DRAM: 256 MB
NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0x36 (Samsung NAND 64MiB 1,8V 8-bit)
64 MiB
In: serial
Out: serial
Err: serial
ARM Clock: 405MHz
DDR Clock: 189MHz
Ethernet PHY: LXT972 @ 0x01
Hit any key to stop autoboot: 0

Loading from NAND 64MiB 1,8V 8-bit, offset 0x60000
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................... done, booting the kernel.

regards
--parwath

0 Titusrathinaraj Stalin over 9 years ago in reply to parwath r

TI__Guru** 116100 points

bootargs=video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=$(videostd) console=/dev/ttyUSB0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=120M

I'm suspecting the problem in configuring the console "/dev/ttyUSB0"

Is that correct console ?
or /dev/ttyS0 or /dev/ttyS2 ?

0 parwath r over 9 years ago in reply to Titusrathinaraj Stalin

Intellectual 510 points

no sir its detecting as /dev/ttyUSB0 only if it is not there means i will not get normal mincom output prints also.

0 parwath r over 9 years ago in reply to parwath r

Intellectual 510 points

sir is there any missmatches in memory allocation for boot the kernel image....

--parwath r

0 parwath r over 9 years ago in reply to Titusrathinaraj Stalin

Intellectual 510 points

hi sir,
1)In nand earse and nand write offset is 0x60000 but size is depends on image size or fixed?

2) u-boot log

Loading from NAND 64MiB 1,8V 8-bit, offset 0x60000
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Arago/2.6.31+2.6.32-rc1-r37+gitr
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1893880 Bytes = 1.8 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux........................................................................................................................... done, booting the kernel.

its hanging here only...
if it is kernel image flashed means i will go to Setting up the target filesystem but it will overwrite before image file or we need to any changes ?
if its not yet flashed kernel image only meanshow to do that i tried all the way that as your replies please suugest me

0 Titusrathinaraj Stalin over 9 years ago in reply to parwath r

TI__Guru** 116100 points

1)In nand earse and nand write offset is 0x60000 but size is depends on image size or fixed?

It depends on the linux kernel image size.

0 parwath r over 9 years ago in reply to Titusrathinaraj Stalin

Intellectual 510 points

In nand erase offset is fixed or it will change?

0 parwath r over 9 years ago in reply to parwath r

Intellectual 510 points

Bytes transferred = 1893944 (1ce638 hex)
this is the size of image please send me the the proper nand erase nand write commands depends the size of image. and in some wesite i saw that offset address for dm644x is 0x2060000 . please suggest me.

0 Titusrathinaraj Stalin over 9 years ago in reply to parwath r

TI__Guru** 116100 points

If you are not using the correct offset then you would have erase either u-boot or filesystem.
I would like to suggest you to boot the DM6446 board via NFS.

0 parwath r over 9 years ago in reply to Titusrathinaraj Stalin

Intellectual 510 points

subnet 10.0.0.0 netmask 255.0.0.0 {
host targetboard {
fixed-address 10.0.0.10;
hardware ethernet 12:34:56:78:9a:bc;
option root-path "/full/path/to/rfs";
filename "uImage-2.6.28-ts-armv5l";
}
}
i am not getting how to edit of the above code some parmeters
subnet =host system ip
netmask=subnet mask
fixed adrees=board ip
hardwre ethernet is board mac adrress
is all above are correct or is there any changes please suggest me...

Processors

Processors forum

kernal flashing for dm6446 board