Find the answer to your Linux question:
Results 1 to 2 of 2
Hi Guys, I am trying to flash ROM memory with Linux Kernel 2.6.39.4 with busy box I have following hw and requirements 1/ Using intel's Atom E660T process which only ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Feb 2010
    Posts
    10

    Cool Linux Kernel 2.6.39-4


    Hi Guys,

    I am trying to flash ROM memory with Linux Kernel 2.6.39.4 with busy box I have following hw and requirements

    1/ Using intel's Atom E660T process which only can go upto 32bit no more.
    2/ On board 8MB of ROM eMM connected to SPI0 bus and like to store a kernel 2.6.39.4 into it so the entire board could boot from it

    3/ After successful build of Kernel 2.6.39.4 an OS image file found in the linux-2.6.39.4/arch/x86/boot/bzImage

    4/ Which normally converted to binary using following command
    Code:
    ./mkimage -c "console=ttyS0,115200n8 rootwait root=/dev/mmcblk0p2 init=/sbin/init loglevel=7 position_fix=1 pcie_aspm=off lpj=1499875" -i ramdisk.cpio bzImage plk.bin
    5/ Finally I get plk.bin file which is roughly around 3.1MB in size

    6/ Normally there are two partition on the eMM (NAND ROM) i.e
    p1 and p2
    7/ The p2 is created for the busybox utilities and p1 for actual kernel image i.e plk.bin to be store for regular use.

    8/ After sending command
    Code:
    dd if=/plk.bin  of=/dev/mmcblk0p1  conv=fsync
    The image get flashed into the ROM but boot process beigins
    following stage it crashes the kernel and boot does NOT successfully
    reach to bash prompt.
    I wonder what I am missing? File, or any other resource I could not figure out whats gone wrong. If some please shed light on this remedy.
    Code:
    L*0d58 *ɣkH,K*9f9 6.-} ..43-,)6ʥK*ṳd
    [    2.928575] Write protecting the kernel text: 3728k
    [    2.933567] Write protecting the kernel read-only data: 1684k
    console ready
    execve() failed: no such file or directory
    [    2.947582] Kernel panic - not syncing: Attempted to kill init!
    [    2.953623] Pid: 1, comm: init Not tainted 2.6.39.4 #9
    [    2.958866] Call Trace:
    [    2.961380]  [<c139fed2>] ? printk+0xf/0x11
    [    2.965652]  [<c139fdd9>] panic+0x5b/0x145
    [    2.969838]  [<c103120e>] do_exit+0x92/0x5c5
    [    2.974201]  [<c11bdb42>] ? tty_write+0x1e5/0x1e5
    [    2.979003]  [<c10318de>] sys_exit+0x13/0x13
    [    2.983364]  [<c13a2621>] syscall_call+0x7/0xb
    Thank you in advance, guys I am really upto my last thread.
    Shy

  2. #2
    Just Joined!
    Join Date
    Jun 2012
    Posts
    28
    Why don't you try using a more stable version of the kernel? I've compiled a kernel myself before, and I can tell you that 3.2.9 is much more stable than 2.6.39-4. Wasn't that just a placeholder anyway?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •