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 21 Jun 2005 11:33 AM by  Anonymous
Need Bolo flash image
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Gerald
New Member
New Member
Posts:


--
20 Jun 2005 09:49 AM
    Hi,

    After using an alternative bootrom I need to reflash BOLO via JTAG.
    Under "All Downloads" only a RAM image is available.
    Where can I get the flash version?

    Thanks,
    Gerald

    P.S. Flashing LOLO 2.0.1 works. After a reset it directly boots to LOLO, but I cannot interrupt to BOLO (by pressing 'q' at startup).
    abest
    New Member
    New Member
    Posts:


    --
    20 Jun 2005 11:38 AM
    Hey Gerald,

    Not a logic guy, but regarding the new layout of BoLo & Lolo, it is my understanding that "BoLo" no longer exists. The functionality of BoLo has been rolled into LoLo.

    From the Readme.

    Removed features:
    - Removed Bolo (Lolo now resides at block 0)


    This is also from the readme concerning the 'q' interrupt for the boot script:

    - change operation of the mode2 pin on ARM engines. A low on the mode2 pin now indicates to LoLo that it should not look for the 'q' key but instead attempt to immediately execute any boot scripts it finds.

    I would check the state of the mode2 pin on power-up to make sure LOLO doesn't automatically execute any bootscript you may have. Previously the system would check for the 'q' for 1.5 - 2.0 seconds. This time has been reduced to 500ms. So you may want to keep your finger on 'q' before you even reset.

    Also in the Readme under "Feature Enhancements and Bug Fixes"
    - make lolo watch just 500ms for 'q' before executing a boot script

    Hope this helps.
    Gerald
    New Member
    New Member
    Posts:


    --
    20 Jun 2005 12:48 PM
    Hi Adam,

    Thanks for your response. Should have better read the release notes.

    Assuming LOLO 2.0.1 flash image is mapped from 0-0x3ffff I burned my VxWorks bootrom (beta version) at 0x40000 successfully. With the new LOLO 2.0.1. it doesn't run anymore (jump 0x40000). With the last version of BOLO this worked fine.

    Do you perhaps have the last BOLO flash image available?

    Thanks,
    Gerald
    Anonymous
    Posts:


    --
    20 Jun 2005 02:11 PM
    Hi Gerald,

    You can get all the info you need by typing 'info mem' in LoLo.

    Are you using the 'exec' command or the 'jump' command to launch your bootrom?

    Thanks,
    Gerald
    New Member
    New Member
    Posts:


    --
    20 Jun 2005 03:35 PM
    Hi Aaron,

    I'm using jump. I got the 404 board from a customer who wants to run VxWorks on it. He uses the same board except he uses the shipped BOLO/LOLO whereas I use LOLO 2.0.1. My customer has no problem booting the same VxWorks bootrom.bin using "jump 0x40000" but in my case it hangs.

    Would be great if I can get the last shipped BOLO flash file to check if that solves the VxWorks boot problem. Alternatively I can ask the customer to make a binary dump with JTAG of the first 256K FLASH.

    Thanks,
    Gerald
    Anonymous
    Posts:


    --
    21 Jun 2005 11:33 AM
    Hi Gerald,

    Please feel free to post back here if you have any further questions. For the most rapid response I would recommend using platformsupport@logicpd.com to send your support request.

    Thank you,
    You are not authorized to post a reply.