Create Account
Search
You are here: TDG Forum  >>  NXP SOMs and Development Kits  >>  LH7A400 Card Engine and Development Kit  >>   Running the Image From CF

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 10 Aug 2004 01:42 PM by  mikee@logicpd.com
Running the Image From CF
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
SAC
New Member
New Member
Posts:


--
06 Aug 2004 12:03 PM
    I have tried to execute the NK.BIN file from the fatfs mounted compact flash drive through LoLo, but with no success. The result is a LoLo reboot.

    Is it possible for the OS to run from the CF?

    I have successfully run images from the on-board flash, but with my need to increase the actual NK.BIN file size above 15 MB, this seems unlikely with my current hardware configuration. Each attempt to write an Image to Flash via Platform Builder that is of greater size than 15 MB fails with the following error message:

    [Connecting to Platform Builder]
    [Error, image doesn't fit in FLASH]

    Thanks in Advance.

    -Dave
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    10 Aug 2004 01:42 PM
    SAC,

    This should work fine. Although, you need to link your image to execute from RAM. When you tell LoLo to load the nk.bin off of the Compact Flash card, LoLo will look at the addresses of the file and unpack it into RAM for you.

    A reset is probably caused by one of the following reasons:

    1) You adjusted the start address of the image and it collides with LoLo's address space.

    2) Your image is larger than the available RAM on your hardware. When LoLo is unpacking it, it does some sort of bad access and resets.

    Write back if you have more questions.

    Best regards,

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

    Forums NXP SOMs and Development Kits LH7A400 Card Engine and Development Kit