Create Account
Search
You are here: TDG Forum  >>  Board Support Packages (BSP)  >>  Linux  >>   Working with Freescale Linux BSP on the MCF5329

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 Aug 2007 07:55 AM by  mcelweep@msoe.edu
Working with Freescale Linux BSP on the MCF5329
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
mcelweep@msoe.edu
New Member
New Member
Posts:


--
13 Aug 2007 08:38 AM
    I am cross posting because I am not sure where this post fits best. I have also posted in the MCF5329 forum

    I have been trying to use Lolo as a boot loader for the uclinux image I have built using the BSP supplied by Freescale. The image I have built downloads and runs fine using Dbug, but I cannot seem to get it to work through Lolo. I want to use Lolo, so I can do some simple logic of mounting the Compact Flash, check for a new image, dump that image to flash, dump flash image to ram, run the image. I can do all of that except for running the image. Whenever I try to load it using the command load I get the following.

    losh> load bin image.bin
    loading from image.bin:
    error: load: address space does not fit in ram (0x2ebc00 bytes at 0x7cfc0980)
    load failed

    I tried to write it to the free RAM using the raw switch on the load command and it loads it, but it doesn't seem to want to run.


    losh> load raw 0x400c0000 3748864 image.bin
    loading from image.bin:
    loading raw binary to 0x400c0000 (ram) len 00393400:
    ...................................................................................................................................:
    ea61e0b03eeb5eb7c1476472ec249b68 - addr: 400c0000 len: 00393400
    file loaded
    losh> exec 0x400c0000 - "root=romfs"
    kernel cmdline: 'root=romfs' at 4004e840


    Any ideas about how to go about this? Am I missing something simple?
    mcelweep@msoe.edu
    New Member
    New Member
    Posts:


    --
    14 Aug 2007 07:55 AM
    Well, I figured out my issue from a combination of RTM and dumb luck.

    The first issue is that BIN is not binary, but the Microsoft BIN file format, which is definately not what the the freescale LTIB builds to. So loading the image with the raw command is the correct way to go.

    Second issue, when Dbug is running, the first chunk of free RAM is at 0x40020000. When Lolo is running (i.e. after typing go_lolo in dbug), the first chunk of free RAM is at 0x400C0000.

    When configuring the Kernel there is an option under "Processor type and features" called "address of the base of kernel code". This needs to be changed to the start of the free RAM (i.e. where the image is going to be loaded to), so in Dbug it would be 0x40020000, but in Lolo it would be 0x400C0000.
    You are not authorized to post a reply.

    Forums Board Support Packages (BSP) Linux