zuowenping a écrit :
thanks Deepak:
I have configed kernel by the command :
      make ARCH=arm CROSS_COMPILE=arm_v5t_le- davinci_dm355_defconfig
      make ARCH=arm CROSS_COMPILE=arm_v5t_le- uImage
use the default configs for dm355,the kernel can't been boot up,I have Enabled kernel hacking->kernel debuging->low level debug functions.

I don't think the low level debug can do anything for your from kernel decompression, and until the console is registered.

Try to apply the attached printascii hack

Jean-philippe François


the same result i goted! the envirment is:
software:DaVinciLSP_02_00_00_110 ,mvltools5_0_0801921 hardware: dm355 evm
and resut is as:
DM355 EVM # tftpboot
TFTP from server 10.0.0.89; our IP address is 10.0.0.53
Filename 'uImage'.
Load address: 0x80700000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###########################################################
done
Bytes transferred = 1965512 (1dfdc8 hex)
DM355 EVM # bootm
## Booting image at 80700000 ...
   Image Name:   Linux-2.6.18_pro500-davinci_evm-
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1965448 Bytes =  1.9 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux................................................................................................................................... It stoped here for ever! it seems no printed kernel information only uboot prints,I have doubled where the serial configs have errors,I have checked the bootargs whick can been used well for the uImage that comes with DVSDK.
setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs 
nfsroot=10.0.0.89:/opt/montavista/pro/devkit/arm/v5t_le/target/,
nolock mem=116M video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16, 2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=$(videostd) so it is not the bootargs error i think! serial driver error? board config driver error? It amazed me so far! 2009-05-15
------------------------------------------------------------------------
zuowenping
------------------------------------------------------------------------
*发件人:* Deepak Mundra
*发送时间:* 2009-05-14  22:46:04
*收件人:* Steve Chen
*抄送:* zuowenping; davinci-linux-open-source
*主题:* Re: I can't boot linux2.6.18 uImage in dm355

Dear *zuowenping*

 do make menuconfig

 Enable kernel hacking->kernel debuging->low level debug functions
and compile the kernel and post the kernel output here


Regards
Deepak

On 5/14/09, *Steve Chen* <sc...@mvista.com <mailto:sc...@mvista.com>> wrote:

    On Thu, 2009-05-14 at 13:49 +0800, zuowenping wrote:
     > My develop envirment :
     > DaVinciLSP_02_00_00_110 ,mvltools5_0_0801921  and dm355 evm
     > I have built the kernel by reference the pdf " TMS320DM355 DVEVM
    v1.30
     > Getting Started Guide" ,
     > DM355 EVM # printenv
     > bootdelay=3
     > baudrate=115200
     > bootfile=uImage
     > bootcmd=nboot 0x80700000 0 0x400000;bootm 0x80700000
     > fileaddr=80700000
     > ipaddr=10.0.0.53
     > bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs
    nfsroot=10.0.0.89:/nfs/restore_dm355,nolock mem=116M
    video=davincifb:vid0=720x576x16,2500K:vid1=720x576x16,
    2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE
    davinci_enc_mngr.ch0_mode=pal
     > serverip=10.0.0.89
     > filesize=2191c0
     > stdin=serial
     > stdout=serial
     > stderr=serial
     > videostd=pal
     >
     > Environment size: 491/16380 bytes
     > why not success?
     > Any clues will be appreciated!


    Just want to make sure I understand, you can boot the board with the
    binary that comes with DVSDK, but you can not boot the board with the
    binary generated by following the "Getting Started Guide"

    If that is the case,   what are the commands you used to configure and
    build the kernel and what error did you see during boot up?


    Regards,

    Steve



    _______________________________________________
    Davinci-linux-open-source mailing list
    Davinci-linux-open-source@linux.davincidsp.com
    <mailto:Davinci-linux-open-source@linux.davincidsp.com>
    http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source



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

_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Index: .kernel/kernel/printk.c
===================================================================
--- .kernel.orig/kernel/printk.c        2009-02-28 02:52:32.000000000 +0100
+++ .kernel/kernel/printk.c     2009-04-30 14:12:29.000000000 +0200
@@ -41,6 +41,7 @@
 {
 }
 
+extern void printascii(const char *);
 #define __LOG_BUF_LEN  (1 << CONFIG_LOG_BUF_SHIFT)
 
 /* printk's without a loglevel use this.. */
@@ -552,7 +553,7 @@
 
        /* Emit the output into the temporary buffer */
        printed_len = vscnprintf(printk_buf, sizeof(printk_buf), fmt, args);
-
+        printascii(printk_buf);
        if (printed_len > 0) {
                unsigned int loglevel;
                int mark_len;
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source

Reply via email to