• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 445 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-MT5 Kernel fails to start

Andrew Lee66217
Prodigy 20 points

Hello-

I loaded a kernel onto DM365 IPNC-MT5 through TFTP and now it won't boot:

DM365 IPNC :>boot                                                              
                                                                               
NAND read: device 0 offset 0x400000, size 0xe00000                             
 14680064 bytes read: OK                                                       
                                                                               
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:    1809716 Bytes =  1.7 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:    1809716 Bytes =  1.7 MB                                       
   Load Address: 80008000                                                      
   Entry Point:  80008000                                                      
   Verifying Checksum ... OK                                                   
   Loading Kernel Image ... OK                                                 
OK                                                                             
                                                                               
Starting kernel ...        

 

Then it just hangs there and never outputs anything else. This is supposed to be the original kernel (vendor-provided) too so I am confused as to why this is not working. These are my bootargs:

bootdelay=4                                                                    
baudrate=115200                                                                
ethaddr=00:0C:0C:A0:FF:FA                                                      
filesize=DCC000                                                                
fileaddr=82000000                                                              
ipaddr=10.2.1.5                                                                
bootcmd=nand read 0x82000000 0x400000 0xe00000;nboot 0x80700000 0 0x200000;bootm
 0x80700000                                                                    
nfshost=172.16.4.140                                                           
rootpath=/home/research/mvfilesys                                              
bootfile=uImage                                                                
serverip=172.16.4.140                                                          
bootargs=mem=60M console=ttyS0,115200n8 root=/dev/ram0 rw initrd=0x82000000,13M
stdin=serial                                                                   
stdout=serial                                                                  
stderr=serial                                                                  
ver=U-Boot 1.3.4 (Aug  5 2009 - 18:21:12) DM365-IPNC-0.6                       
                                                                               
Environment size: 467/16380 bytes     

 

Any help is appreciated.

  • 0
    TI__Mastermind 19985 points

    Hi,

    There can be multiple reasons of the failure. We can try to eliminate them by the following set of tests:

    1. Did the same uImage work out-of-box when the camera was shipped from the vendor?

    2. Did you program the NAND or is it from the initial NAND programmed uImage that you are seeing the problem?

    3. Did you change the uBoot? I guess not because the version shows DM365-IPNC-0.6.

    4. Which release of IPNC are you using? There are newer versions available (latest is ver 2.5). Ideally the one you have should also work, but based on the release version we can check internally.

    There are a few threads posted on the E2E for similar issues on different setups and the solutions people used to overcome the problem. Hope this helps.

     

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/p/86841/299995.aspx#299995

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/p/66007/238502.aspx#238502

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Prodigy 20 points

    Hi Anshuman-

    Thanks very much for your help - I was able to get it working. Turns out I needed to upload the cramfs image file as well as the kernel. Furthermore I changed the memory setting to the manufacturer recommended 48M and the kernel now boots just fine with the original uImage.

    However now I try to compile my own kernel using the evaluation MontaVista LSP provided (version 2_10_01_18). First I do make arch=ARM CROSS_COMPILE=arm_v5t_le- davinci_dm365_defconfig to load the default configuration. Then I did make arch=ARM CROSS_COMPILE=arm_v5t_le- uImage to build the image. The build process succeeded.

    But when I load the new uImage onto the camera the kernel fails to load...hangs at "Starting kernel..."

    I looked at the TI FAQ and it mentioned it possibly being a UART configuration error in uncompress.h. So I tried UART0, 1 and 2 but none of them seem to work. The schematic of the specific camera I am using (DM365IPNC-MT5) suggests that the JTAG interface is connecting via UART1 but still no output after Starting kernel...

    Any tips?

    Thanks,

    Andrew L.

  • 0 in reply to Andrew Lee66217
    TI__Mastermind 19985 points

    Hi Andrew,

    We provide the kernel source code along with the IPNC release. It is available in <Base_Dir>/ipnc/ti-davinci/lsp folder. Have you tried building this kernel source code with the defconfig created for IPNC. The defconfig that would come with DVSDK/LSP package is meant for DM365 EVM and might not match as-is for IPNC hardware. So i recommend using the kernel source and defconfig for the IPNC hardware.

    To get the exact make commands and compile options, you can refer to the topl leve makefile for "make lsp"

    Hope this helps.

    Regards,

    Anshuman

    PS:  Please mark this post as verified if you think it has answered your question. Thanks.