Search

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 23 Aug 2004 02:02 PM by  mikee@logicpd.com
Updating Bolo/Lolo without JTAG
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Ingineerix
New Member
New Member
Posts:


--
10 Aug 2004 05:53 PM
    Bolo/Lolo's ELF load routines seem to be broken in my version. (BRA_release_1-2-pre1.2.5)

    Is there any way to get this fixed w/o JTAG? I got the Zoom kit from Logic because it (wrongly) listed that it supported Linux. Support queries refer me to Metrowerks which wants a support agreement.

    I tried to load BLOB in via Elf with Marc Singer's help, and I've come to find that ELF support just doesn't even work, not even to update itself!

    I followed the instructions to update Bolo/Lolo from the Logic docs, and It errors out upon load:

    losh> load elf
    loading from stdin:
    0xc003dbb8 00 c0 61 70 01 00 00 00 00 00 07 00 02 00 00 00 ..ap............
    0xc003dbc8 62 6f 6c 6f 5f 31 2e 34 2e 33 5f 4c 4c 48 37 61 bolo_1.4.3_LLH7a
    0xc003dbd8 8c 38 01 00 00 00 00 00 00 00 00 00 00 00 00 00 .8..............
    0xc003dbe8 5e 09 db 01 ^...
    ELF file must be: ARM, and elf-current:
    load failed

    elf file type : 0x6f62
    machine type: 6f6c version: 875442527
    prog start addr : 0x4c5f332e
    num prog headers: 0
    num sect headers: 2398
    offset : 0x2a2a2a2a disk length: 0x00000000 mem len: 0x2a2a2a2a
    phyaddr: 0x2a2a2a2a vaddr : 0x2a2a2a2a dl addr: 0x00000000
    elf load failed.
    ignoring rest of file... 79531 bytes. done


    Is this truly the case? Has Logic released a boot loader that can't even update itself?!
    Anonymous
    Posts:


    --
    11 Aug 2004 10:56 AM
    Ingineerix,

    Please email platformsupport@logicpd.com with more detail of your situation. I will recieve that email and we can step through the issues that you're having.

    You might also want to update to the most recent version of bolo/lolo. This can be accmplished by grabbing the latest release of bolo and lolo off of the LH7A400-10 downloads page. Make sure to get the .elf versions. From there please follow the Lolo User's Manual for instructions on how to complete the process.

    Please bear in mind that Logic does not support any third party products or software. The LH7A400-10 is able to run Linux but Logic has not created a Linux BSP yet for LH7A400-10 card engine.

    Regards,
    Ingineerix
    New Member
    New Member
    Posts:


    --
    12 Aug 2004 04:04 AM
    I am now running the current version of LoLo. (As listed on the support website; Version 1.4.3-LLH7a400_10 0001)

    I am not asking for support on third party products, but the Logic promotional materials indicated that a Linux BSP was available for this board, and that was why I chose this platform. This isn't *yet* true as you indicated, so I am a little annoyed.

    But that notwithstanding, I am trying to get LoLo to load an ELF file, which is a tested version of BLOB that others have been able to get to run on the Zoom, albeit with a JTAG load. The "word on the street" is that Logic's implementation of the ELF loader in LoLo is not to spec, and cannot be used to install BLOB. This is what I am finding out, as I even had trouble using it to update itself! That has been accomplished, here is my "info version":

    losh> info version
    Version : 1.4.3-LLH7a400_10 0001
    Build : lpd077 Thu Jun 3 17:53:35 CDT 2004
    CPLD_CE_REG_REVISION: 0x34 (rev: b)


    When I try to load an ELF, I don't get just an error, I appear to get a core dump. Why can others use a direct JTAG load of this code, while I cannot get LoLo to accept it as an ELF? Here is the output:

    losh> load elf /cf/WBLOB-0.4
    loading from /cf/WBLOB-0.4:
    R
    everything went wrong
    fsr: 00000005 (trans sect) far: 60000000
    exception mode: abort
    r00: 00000001 r01: 00000200 r02: 00000000 r03: 005a0000
    r04: 000020e0 r05: 60000000 r06: 0000005a r07: 00000000
    r08: 00000000 r09: c0046268 r10: c00351d0 r11: c0045a9c
    r12: c0000000 sp: c0045a58 lr: 00000200 pc: c0010764
    spsr:20000053 cpsr:200000d7
    bt: sp: c0045998 (stack: c0044b80 - c0046080)
    0: fp:c00459c0 + 40 c0000738() called from: c00042b8
    1: fp:c00459d8 + 20 c0004278() called from: c0000938
    2: fp:c00459ec + 16 c00008ac() called from: c000181c
    3: fp:c0045a0c + 28 c00017f8() called from: c000061c
    4: fp:c0045a9c + 140 c0010518() called from: c000fcd0
    5: fp:c0045ad4 + 52 c000fc1c() called from: c0002ae8
    6: fp:c0045af8 + 32 c0002a68() called from: c00086e8
    7: fp:c0045b20 + 36 c0008698() called from: c0009300
    8: fp:c0045c50 + 300 c0008f04() called from: c0005ce4
    9: fp:c0045de0 + 396 c0005b50() called from: c0008384
    10: fp:c0045e44 + 96 c00081f0() called from: c0008488
    11: fp:c0046064 + 540 c0008420() called from: c0003d98
    12: fp:c004607c + 20 c0003d70() called from: c0003d6c
    (fp:c004607c->bfdd6f3d, sp:c0046080)
    mike tesch
    New Member
    New Member
    Posts:


    --
    16 Aug 2004 03:02 AM
    could you mail me the binary 'WBLOB-0.4" ? send it to tesch1@gmail.com
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    23 Aug 2004 02:02 PM
    Do you have 'binary' checked on your terminal emulator?

    It looks like you don't and are trying to send the file in ASCII mode.

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