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 06 Feb 2006 11:57 AM by  Anonymous
fseek error message from Lolo
 4 Replies
You are not authorized to post a reply.
Author Messages
New Member
New Member

06 Feb 2006 09:27 AM

    I have a SDK-LH79520 board that I am tyring to get Linux up and running on (using Sharp's BSP package 1.2.9). I am following the quick start guide and every think works up until the point where I try to use Lolo to load their APEX bootloader. I get the following error message:

    <start Tera Term copy and paste>

    losh> mount fatfs /cf
    losh> ls
    D : cf 0
    D : tftp 0
    D : dev 0
    losh> cd cf

    losh> ls
    r: APEX.BIN 51996
    r: APEX 254950
    losh> load elf APEX
    loading from /cf/APEX:
    Rfatfs_seek: ERROR!

    fseek(delta:32652) failed during load, possibly strange elf?
    0x2003611c 7f 45 4c 46 01 01 01 61 00 00 00 00 00 00 00 00 .ELF...a........
    0x2003612c 02 00 28 00 01 00 00 00 00 00 20 20 34 00 00 00 ..(....... 4...
    0x2003613c 84 95 03 00 02 00 00 00 34 00 20 00 02 00 28 00 ........4. ...(.
    0x2003614c 1a 00 17 00 ....
    0x2003607c 01 00 00 00 00 80 00 00 00 00 20 20 00 00 20 20 ..........
    0x2003608c 1c cb 00 00 1c cb 00 00 07 00 00 00 00 80 00 00 ................

    elf file type : 0x0002
    machine type: 0028 version: 1
    prog start addr : 0x20200000
    num prog headers: 2
    num sect headers: 26
    offset : 0x20036160 disk length: 0x00000074 mem len: 0x20200000
    phyaddr: 0xf0daf002 vaddr : 0xff68f200 dl addr: 0x20200000

    elf load failed

    <end Tera Term copy and paste>

    I have little experiece with this board and I was wondering if anybody could explain what the error message means and give me a few ideas on how to proceed. I guess it could be something with how I partitioned my 256MB flash card but as far as I can tell it is correct (FAT16).

    Is there a document that goes over Lolo error messages? I didn't see anything relating to error messages in the Lolo user manual.

    Also my SDK board has Lolo ver1.1.2. Would you recommend updating Lolo to the latest version? I found ver 1.2.6 on lpd's website. I also notice there are no specific instrucions on how to update lolo. I would guess you use bolo to erase the old lolo memory section and program in the new one. Is that the gist of it? I don't have access to a JTAG rig so I really don't want to accidently clobber the bootloader.

    Any help you could give me would be greatly appreciated.

    Thanks for your time,

    06 Feb 2006 09:56 AM
    Hi Bill,

    Yes you're going to want to update your version of LogicLoader to the latest which is 1.2.6 for the LH79520 card engine.

    1) type 'load elf' at the losh> prompt

    2) Go to "File > Send File" in TeraTerm

    3) Select the LogicLoader file making sure the binary box is checked abd

    click open

    4) When it's done loading the file, type 'burn'

    5) Reset the kit

    Additional information for commands can be found in the LogicLoader User's Manual and the SDK User's Guide.
    New Member
    New Member

    06 Feb 2006 10:43 AM
    Hello Aaron,

    Thanks for your quick reply. I updated Lolo as you instructed and rebooted the board. That seem to fix my original problem but a new one poped up. Now when Lolo tries to load the file but I get the following error message over and over:

    fatfs_read: ata_read failed ffffffff
    ata_read: lba too big 4 at 747537

    I would guess this error may have somenting to do with the way my compact flash card is partitioned. I am goint to try redoing that and see what happens. Any other ideas you have would be helpful.

    Thanks for the help,
    New Member
    New Member

    06 Feb 2006 11:03 AM
    I think the CF card is too large. Its been awhile since I've worked with that specfic product, but I recall a <=32MB limit for that product. Also, the number of directories on the card can also cause problems because they eat up all the available RAM. Try without any directories otherwise you might want to test with a smaller card.


    06 Feb 2006 11:57 AM

    I know that a 64 mb card will work and is recommended. However I'm not sure if a card larger than that will work.

    You are not authorized to post a reply.