Create Account
Search
You are here: TDG Forum  >>  Board Support Packages (BSP)  >>  Linux  >>   ZOOM AM3517 EVM Board - kernel panic

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 14 Jun 2010 01:20 AM by  qavaxb
ZOOM AM3517 EVM Board - kernel panic
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
qavaxb
New Member
New Member
Posts:


--
08 Jun 2010 06:26 AM
    Hello,
    I couldn't find any topics about ZOOM AM3517 EVM Board.
    I'm booting precompiled kernel from TI PSP for AM3517 via tftp, using root filesystem from Arago project via NFS and I get kernel panic.
    My command lines (2 lines) in u-boot:
    setenv bootargs 'console=ttyS2,115200n8 rw eth=33:55:77:99:aa:bb ip=10.3.101.86:10.3.101.105:10.3.101.1:255.255.255.0:my.name.domain:eth0:off root=/dev/nfs nfsroot=10.3.101.105:/nfs,nolock mem=256M omapfb.rotate=1 omapfb.vrfb=y omap_vout.vid1_static_vrfb_alloc=y'
    tftp 0x80000000 uImage; bootm 0x80000000


    Of course MAC address is different.
    I get from console:

    (...)
    eth0; attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, id=7c0f1)
    IP-Config: Complete:
    (...)
    Looking up port of RPC 100003/2 on 10.2.101.105
    PHY: ffffffff:00 - Link is Up - 100/Full
    Looking up port of RPC 100003/2 on 10.2.101.105
    VFS: Mounted root (nfs filesystem) on device 0:11.
    Freeing init memory: 164K
    Warning: unable to open an initial console.
    Kernel panic - not syncing: Attempted to kill init!

    What can I do in such situation?

    Thaks in advance for help
    richard.laborde@logicpd.com
    Basic Member
    Basic Member
    Posts:247


    --
    08 Jun 2010 07:38 AM
    Out of curiosity, you did saveenv before you tried to boot the kit, correct?
    qavaxb
    New Member
    New Member
    Posts:


    --
    08 Jun 2010 10:05 AM
    No, I did it not. If I undertood corectly, saveenv writes variables to flash. All required variables (in that 2 lines) seemed to be correct processed, for instance IP address, hostname are visible just as they are in 'bootargs', only phy_addr, which points MAC address is not correct.
    Moreover if rootfs is not loaded, then all stops after kernel decompression, but in my case that went good.

    ------------------------------------------------
    -- edited --
    ------------------------------------------------
    I have searched the web for information about that error. From what I found, it seems, that kernel is to old to understand MAC address, AM3517 is MAC-sensitive and makes problem to boot via NFS.
    If I'm wrong, please correct my information.
    richard.laborde@logicpd.com
    Basic Member
    Basic Member
    Posts:247


    --
    11 Jun 2010 03:27 PM
    My suggestion is to use the TI e2e site for your Linux questions. They wrote the code and have apps engineers that can support you on it.

    http://e2e.ti.com/
    qavaxb
    New Member
    New Member
    Posts:


    --
    14 Jun 2010 01:20 AM
    I was wrong. It all works when we unpack tar.gz direct into nfs folder, without any mv or cp.
    You are not authorized to post a reply.

    Forums Board Support Packages (BSP) Linux