Create Account
Search
You are here: TDG Forum  >>  Freescale / NXP SOMs and Development Kits  >>  i.MX31 LITEKIT Development Kit  >>   WindRiver BSP

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 18 Oct 2007 11:13 AM by  mikee@logicpd.com
WindRiver BSP
 9 Replies
Sort:
You are not authorized to post a reply.
Author Messages
dsanders16@gmail.com
New Member
New Member
Posts:


--
27 Sep 2007 08:35 PM
    Does anyone here use the Linux BSP from WindRiver? We just got the i.MX31 LITEKIT, and now we are trying to load this BSP onto the board.

    I followed the instructions from LogicPD in updating the LogicLoader, though I have been browsing documentation for the LITEKIT, and I am not really seeing some specifc area where it tells you how you load a BSP using LogicLoader...Basicaly I am a newbie in this and dont really know how to move forward from here.

    Even if its not a WindRiver BSP, Id be happy with getting any linux kernel running at the moment.

    I have all the commands for how to load the BSP from WindRiver, but it looks this requires some setup I am unaware of. I need to have the images set in some NFS folder, and I need to have TFTP configured, can any of this be done through windows or do I need to swith over to linux? Is there some guide that tells you about this step of loading BSPs?

    Thanks and apologies ahead of time.
    kurtl@logicpd.com
    New Member
    New Member
    Posts:


    --
    29 Sep 2007 08:37 AM
    Hi dsanders,

    You can get free Windows based tftp programs for the web. One I have used in the past is "Solar Winds TFTP Server". The TFTP program will allow your host PC to send files to the development kit when the kit requests them over Ethernet.
    http://www.solarwinds.com...freetools/index.aspx

    The commands you'll want to review in the Lolo User's guide to get a TFTP link work are: "ifconfig" for creating the ethernet link and "load <type> /tftp/<server:filename>" to load the specific file type from TFTP server. Once the file is loaded, you will probably need to use the "exec" command with a "-t" to pass command line parameters to Linux. The Linux boot sequence may also use the ethernet and TFTP link to download and/or mount external data sources.

    http://www.logicpd.com/do...mand_Description.pdf
    dsanders16@gmail.com
    New Member
    New Member
    Posts:


    --
    03 Oct 2007 05:51 PM
    Posted By KurtL on 29 Sep 2007 8:37 AM
    Hi dsanders,

    You can get free Windows based tftp programs for the web. One I have used in the past is "Solar Winds TFTP Server". The TFTP program will allow your host PC to send files to the development kit when the kit requests them over Ethernet.
    http://www.solarwinds.com...freetools/index.aspx

    The commands you''ll want to review in the Lolo User''s guide to get a TFTP link work are: "ifconfig" for creating the ethernet link and "load <type> /tftp/<server:filename>" to load the specific file type from TFTP server. Once the file is loaded, you will probably need to use the "exec" command with a "-t" to pass command line parameters to Linux. The Linux boot sequence may also use the ethernet and TFTP link to download and/or mount external data sources.

    http://www.logicpd.com/do...mand_Description.pdf




    Okay well I got it to start the uncompressing of the kernel despite it not recognizing the -t command. But now i get a Kernel panic, which I think has something to do with not having a rootfs?


    eth0: link down
    Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
    ., OK
    IP-Config: Got DHCP answer from 192.168.1.254, my address is 192.168.1.94
    IP-Config: Complete:
    device=eth0, addr=192.168.1.94, mask=255.255.255.0, gw=192.168.1.254,
    host=192.168.1.94, domain=launchmodem.com, nis-domain=(none),
    bootserver=192.168.1.254, rootserver=192.168.1.254, rootpath=
    Looking up port of RPC 100003/2 on 192.168.1.254
    portmap: server 192.168.1.254 not responding, timed out
    Root-NFS: Unable to get nfsd port number from server, using default
    Looking up port of RPC 100005/1 on 192.168.1.254
    portmap: server 192.168.1.254 not responding, timed out
    Root-NFS: Unable to get mountd port number from server, using default
    Root-NFS: Server returned error -5 while mounting /tftpboot/192.168.1.94
    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Cannot open root device "<NULL>" or unknown-block(2,0)
    Please append a correct "root=" boot option
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)


    Any ideas? Do I need to have a NFS going for this?

    edit: i am using this command to exec the kernel:
    exec 0x81000000 "console=ttymxc0,115200 rw root=/dev/nfs nfsroot=192.168.1.97:/export/rootfs.lite ip=192.168.1.94:192.168.1.97:192.168.1.254:255.255.255.0:lite:eth0:off"

    And I have a NFS Server running, but it still does the DHCP lookup and then tried to find the server at my gateway address, so now I am confused.
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    06 Oct 2007 10:16 AM
    You definitely need to have NFS going for this, since you are telling the kernel to mount root via NFS in your kernel command line.

    Are you saying that the kernel is trying to find its root file system on your gateway server rather than your development machine? If so, I think you are likely just specifying the nfsroot portion of your kernel command line wrong.

    From the output I can see, it looks like you are telling the kernel to find it's root file system on the machine 192.168.1.97 in the directory /export/rootfs.lite. Is that the correct IP address for your development machine?

    Other things to consider:
      * Are you sure that machine's NFS is set up correctly? Can you mount that share from another Linux box to check?

      * Does that machine have a firewall activated on it? If so, a machine trying to mount NFS as root might be blocked. Is the no-squash-root option set?

      * Are you using Fedora Core on your development machine and busybox on the kit? IIRC some versions of Fedora Core automatically turn on some sort of file system trickery which I've seen confuse busy-box. You'll have to google a bit for the details as it's been awhile since I ran into the problem.


    Regards,
    --mikee
    dsanders16@gmail.com
    New Member
    New Member
    Posts:


    --
    06 Oct 2007 01:21 PM
    Posted By mikee on 6 Oct 2007 10:16 AM
    You definitely need to have NFS going for this, since you are telling the kernel to mount root via NFS in your kernel command line.

    Are you saying that the kernel is trying to find its root file system on your gateway server rather than your development machine? If so, I think you are likely just specifying the nfsroot portion of your kernel command line wrong.

    From the output I can see, it looks like you are telling the kernel to find it''s root file system on the machine 192.168.1.97 in the directory /export/rootfs.lite. Is that the correct IP address for your development machine?

    Other things to consider:
      * Are you sure that machine''s NFS is set up correctly? Can you mount that share from another Linux box to check?

      * Does that machine have a firewall activated on it? If so, a machine trying to mount NFS as root might be blocked. Is the no-squash-root option set?

      * Are you using Fedora Core on your development machine and busybox on the kit? IIRC some versions of Fedora Core automatically turn on some sort of file system trickery which I''ve seen confuse busy-box. You''ll have to google a bit for the details as it''s been awhile since I ran into the problem.


    Regards,
    --mikee




    Ya I have the NFS server running, it is almost as if the kernel ignores what I am telling it. Because it doesn't even take the ip information I tell it.

    Do you know why the -t doesn't work? I have the latest LoLo on there.
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    07 Oct 2007 01:25 PM
    I know we were having some trouble in a later version of LoLo correctly passing parameters to the latest version of the ARM-Linux kernel.

    Why don't you try just hardcoding the kernel command line during the build. If that works, then at least you know your lab is correct from an IT standpoint and you can open a support ticket regarding LoLo.

    --mikee
    dsanders16@gmail.com
    New Member
    New Member
    Posts:


    --
    16 Oct 2007 03:09 PM
    Well, WindRiver gives me the compiled Image, I have never done that before myself, is there a tutorial somewhere, or perhaps on this forum, about building a linux kernel for this board?

    Though why does the LoLo not even recognize the -t, is there a LoLo version that does recognize it?

    Derek
    dsanders16@gmail.com
    New Member
    New Member
    Posts:


    --
    17 Oct 2007 11:20 AM
    Posted By mikee on 7 Oct 2007 1:25 PM
    I know we were having some trouble in a later version of LoLo correctly passing parameters to the latest version of the ARM-Linux kernel.

    Why don''t you try just hardcoding the kernel command line during the build. If that works, then at least you know your lab is correct from an IT standpoint and you can open a support ticket regarding LoLo.

    --mikee




    Mike,

    Well I got it to boot, a lot further. I did hardcode in my boot parameters:

    CONFIG_CMD = "console=ttymxc0,115200 rw root=/dev/nfs nfsroot=192.168.1.93:/home/nfs/exports ip=192.168.1.94:192.168.1.93:192.168.1.254:255.255.255.0:lite:eth0:off"

    But now it gives me this error:


    Warning: unable to open an initial console.
    Kernel panic - not syncing: No init found. Try passing init= option to kernel.


    Any idea what I need to do here? Do I need to have something existing in my /home/nfs/exports/ folder? Or am I missing something?
    dsanders16@gmail.com
    New Member
    New Member
    Posts:


    --
    17 Oct 2007 11:16 PM
    Update: Got it all working. Now I need to figure out how I can use the RNGA part of the board.
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    18 Oct 2007 11:13 AM
    Derek,

    Congratulations, I'm glad this is working for you. I apologize for dropping out of the conversation there, I've been traveling in Europe on several business engagements and it's been tough to keep up.

    We would welcome you to post what you found on this thread if you like so others can learn from your experience.

    Again, congratulations.

    Cheers,
    --mikee
    You are not authorized to post a reply.

    Forums Freescale / NXP SOMs and Development Kits i.MX31 LITEKIT Development Kit