Impossible boot the patched kernel

Help
Cristóbal
2009-06-04
2013-04-15
  • Cristóbal

    Cristóbal - 2009-06-04

    I have my equipment running a 2.4.29 kernel, from Toradex. And all is ok.
    But I want to run a more modern 2.6. so searching in the net i found the patch of this project, its looks very interesting and complete.

    I at the moment only have a little problem, the 2.6.29.4 patched kernel don't do anything at all. To boot the kernel I am using a version of uBoot patched by Toradex labeled 'u-boot-1.1.2-col2'.

    To configure the kernel i am running this sequence:
      ARCH=arm make colibri_defconfig
      ARCH=arm make menuconfig (deactivate EABI and exit saving)
    them compile with a cross-compiler gcc 3.4.3:
      make CROSS_COMPILE=arm-Linux- ARCH=arm
    them prepare the kernel binary to be load whit uBoot.

    I am downloading the kernel by dhcp command of uboot and them launching whit the command bootm, and this is what i get:
    -------------------------------------------------------------------------------------
    Load address: 0xa1000000
    Loading: #################################################################
             #################################################################
             ############
    done
    Bytes transferred = 722508 (b064c hex)
    u-boot$ bootm
    ## Booting image at a1000000 ...
       Image Name:   Linux Kernel Image
       Created:      2009-06-03  23:06:13 UTC
       Image Type:   ARM Linux Kernel Image (gzip compressed)
       Data Size:    722444 Bytes = 705.5 kB
       Load Address: a0008000
       Entry Point:  a0008000
       Verifying Checksum ... OK
       Uncompressing Kernel Image ... OK

    Starting kernel ...

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

    And anything more.

    Have any body an idea

    Thank for read this and for the answer.

     
    • marc_balcells

      marc_balcells - 2009-06-12

      Hello Cristobal, you might want to review the bootargs environment variable on uboot, you need to specify where your root partition is located, if you are working over dhcp, you'll probably want to have your root partition on nfs.
      on uboot just do:
      printenv bootargs
      and post what you're getting.

       
      • Cristóbal

        Cristóbal - 2009-06-12

        Thanks  marc,

        I must postpone this work a month, but as i remember in my test the rootfs is int jffs2 and locate in /dev/mtdblock2, My bootargs in as folow

           'bootargs=root=/dev/mtdblock2 rootfstype=jffs2 console=ttyS0,9600n8'

        But it crash before training to load the rootfs, don't do nothing at all or don't send anything to the console.

        Thank you

         
  • MinimumLaw

    MinimumLaw - 2010-02-17

    Hello!

    Are you flash U-Boot from this site? Kernel will be NOT working in some special situations;
    1. MACHINE ID not set correctly. Bootloader MUST set special MACHINE_ID value in PXA register. Kernel check this register for equ with them MACHINE_ID. If not equ - kernel stop loading.
    2. Are you have CONSOLE_ON_SERIAL_PORT (???) kernel options? May be kernel loading, but you not see debug messages.
    3. VGA console enabled? Disable it. On ARM this option NOT NEDDED.

    After this you may rebuild kernel with maximum debug support. In this case you (may be) see diagnostic error message after "Starting kernel…."

     
  • MinimumLaw

    MinimumLaw - 2010-02-17

    Are you have some speed, parity and stop-bits settings on bootloader and serial console? May be trouble so simple?

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks