• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 100 subscribers
  • Views 731 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM365 IPNC 3.0 can't get kernel image!

saurabh sharma104286
Prodigy 10 points

I gave the following set of commands for

Flashing by TFTP on U-Boot (AS PER Users_Guide_IPNC_DM36x)

sudo su

minicom

 

setenv serverip '192.168.120.173'

setenv ipaddr '192.168.120.168'

setenv ethaddr '00:0C:13:A5:DE:D1'

setenv gatewayip '192.168.120.1'

setenv netmask '255.255.255.0'

setenv dnsip '10.1.11.50'

setenv dnsip2 '10.1.11.57'

 

setenv bootcmd 'nboot 0x80700000 0 0x200000;bootm 0x80700000'

setenv bootargs 'mem=48M console=ttyS0,115200n8 root=/dev/mtdblock3 rootfstype=squashfs ip=off eth=00:0C:13:A5:DE:D1 lpj=741376 cmemk.phys_start="0x83000000" cmemk.phys_end="0x88000000" cmemk.phys_start_1="0x00001000" cmemk.phys_end_1="0x00008000" cmemk.pools_1="1x28672" cmemk.allowOverlap="1"'

 

saveenv

 

tftpboot 0x80700000 uImage_ipnc_dm365_3.0.0

tftpboot 0x82000000 ipnc_dm365_3.0.0.squashfs

 

nand erase 0x200000 0x400000

nand write 0x80700000 0x200000 0x400000

nand erase 0x600000 0x1000000

nand write 0x82000000 0x600000 0x1000000

 

Reset

 Press Enter and login as root. Kernel prompt will be available.

 -------- ---------- --------- -------- ---------- ------------- ------------- -----

 

  With these set of commands I have faced following errors:

 saurabh@saurabh-desktop:~$ sudo su

[sudo] password for saurabh:

root@saurabh-desktop:/home/saurabh# minicom

 

Welcome to minicom 2.4

 

OPTIONS: I18n

Compiled on Jan 25 2010, 06:49:09.

Port /dev/ttyS0

 

Press CTRL-A Z for help on special keys

 

DM36x initialization passed!

TI UBL Base Version: 1.50

Boot Loader BootMode = NAND

Starting NAND Copy...

Valid magicnum, 0xA1ACED66, found in block 0x00000008.

Boot Mode Task Completed

 

IPNC UBL Version: 2.0.0

Platform: DM365

 

Reset RTC Fail..

 

Jumping to entry point at 0x81080000

                                                                               

U-Boot 1.3.4 (Feb 28 2012 - 15:01:39) DM365-IPNC-2.0.0                         

                                                                               

I2C:   ready                                                                   

DRAM:  128 MB                                                                   

NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,)

Bad block table found at page 65504, version 0x00                              

Bad block table found at page 65472, version 0x00                              

32 MiB                                                                         

In:    serial                                                                  

Out:   serial                                                                  

Err:   serial                                                                  

ARM Clock :- 297MHz                                                            

DDR Clock :- 270MHz                                                            

Ethernet PHY: GENERIC @ 0x01                                                   

Hit any key to stop autoboot:  0                                               

                                                                                

Loading from NAND 32MiB 3,3V 8-bit, offset 0x200000                            

   Image Name:   Linux-2.6.18_pro500-davinci_IPNC                              

   Image Type:   ARM Linux Kernel Image (uncompressed)                         

   Data Size:    2658244 Bytes =  2.5 MB                                       

   Load Address: 80008000                                                      

   Entry Point:  80008000                                                       

## Booting kernel from Legacy Image at 80700000 ...                            

   Image Name:   Linux-2.6.18_pro500-davinci_IPNC                              

   Image Type:   ARM Linux Kernel Image (uncompressed)                          

   Data Size:    2658244 Bytes =  2.5 MB                                       

   Load Address: 80008000                                                      

   Entry Point:  80008000                                                       

   Verifying Checksum ... Bad Data CRC                                         

ERROR: can't get kernel image!                                                 

DM365 IPNC :>

--------------------- -----------------  --------------- ------------------ ------------------- ------------------- ------------------ ------------------ ------------------

KINDLY REPLY ASAP. WHERE TO LOOK FOR ERROR. DO BOOTCMD, BOOTARGS NEED TO BE MODIFIED 

  • 0
    Guru 11260 points

    Hi,

    Looks like the image being copied is corrupted somewhere in nand. What you can you

    try out is do  tftp 0x80700000 and than bootm 0x80700000 so that nand read write dont come into picture.

    Once if this successfully loads the linux, you can try out with nand.

    Thx,

    --Prabhakar Lad

  • 0 in reply to Prabhakar Lad
    Prodigy 150 points

    Hello Prabhakar,

    Thanks for your reply. Im working with saurabh (who posted this query).

    I did tftp transfer and then nand write commands.. n then reset command on promt.. It works fine for the first time.. But when I switch off the system and switch it on again it gives bad CRC error.. It seems that either its not writing on NAND or not writing on correct location.

    This is sequence i followed:-

    To set bootargs used this =

    $setenv bootcmd 'nboot 0x80700000 0 0x200000;bootm 0x80700000'
    $setenv bootargs 'mem=48M console=ttyS0,115200n8 root=/dev/mtdblock3 rootfstype=squashfs ip=off eth=00:0C:13:A5:DE:D1 lpj=741376 cmemk.phys_start="0x83000000" cmemk.phys_end="0x88000000" cmemk.phys_start_1="0x00001000" cmemk.phys_end_1="0x00008000" cmemk.pools_1="1x28672" cmemk.allowOverlap="1"'
    $saveenv

    And then for tftp
     
    $tftpboot 0x80700000 uImage_ipnc_dm365_3.0.0
    $tftpboot 0x82000000 ipnc_dm365_3.0.0.squashfs

    $nand erase 0x200000 0x400000
    $nand write 0x80700000 0x200000 0x400000
    $nand erase 0x600000 0x1300000
    $nand write 0x82000000 0x600000 0x1300000
    $reset

    Size of uImage is 2597 KB and size of squashfs is 12712 KB

  • 0 in reply to mahesh adsul
    Guru 11260 points

    Hi,

    Instead of nboot command can you give nand read and then bootm, And see weather

    the same issue occurs.

    Thx,

    --Prabhakar Lad

  • 0 in reply to Prabhakar Lad
    TI__Genius 11000 points

    Please set "setenv verify no" in bootargs, this sill remove verification during bootup to save time

    This is mentioend in the USERS GUIDE

    Regads,

    Raghu

  • 0 in reply to Raghu Kudva
    Prodigy 150 points

    Thanks !!

    It worked for me .

    But would like to know what verification it stops.. User guide says "Diasble verification in ENV variables using following commands"

    I mean how it started working after I used this fix?

    Regrads

    Mahesh