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 Nov 2010 01:09 PM by  Scott Harris
New L138 experimenter user needing help
 6 Replies
Sort:
You are not authorized to post a reply.
Author Messages
jheoaustin
New Member
New Member
Posts:


--
02 Mar 2010 10:15 PM
    Hi,

    I'd like to just do a sanity check on this board, and make sure that I don't have to return the board. Hopefully I ask questions in a right way to get answers.

    1. Typing the boot command at U-boot without parameters doesn't work. At a TI training video using an L138 board, it is said that 'boot' should boot linux kernel as there is a preloaded image on the SPI1 flash. Am I right to expect that the linux would boot without a problem on an out-of-box L138 experimenter kit?

    2. I happened to try mtest command, and it gives following errors, and then get stuck in writing FFFFFFF test. Is it also expected?

    U-Boot > mtest
    Pattern 00000000 Writing... Reading...
    Mem error @ 0xC0F7FE14: found 0000000A, expected 003DFF85

    Mem error @ 0xC0F7FE18: found C0F7FE18, expected 003DFF86

    Mem error @ 0xC0F7FE1C: found C1086854, expected 003DFF87

    Mem error @ 0xC0F7FE20: found C109F559, expected 003DFF88

    Mem error @ 0xC0F7FE24: found C0F7FE20, expected 003DFF89

    Mem error @ 0xC0F7FE28: found C0F7FE20, expected 003DFF8A

    Mem error @ 0xC0F7FE2C: found 003DFF8A, expected 003DFF8B
    Pattern FFFFFFFF Writing...

    3. When I plugged the board into my XP desktop, a 'PCI device' and some USB/serial devices are also detected. But windows XP couldn't install the device driver for some reason. Does this sound like an expected behavior for just plugging the board in through USB connection?

    I am looking forward to some helps from you. Thank you.
    richard.laborde@logicpd.com
    Basic Member
    Basic Member
    Posts:247


    --
    05 Mar 2010 01:47 PM
    The early versions of the kits had a uboot without the proper environment variables to boot the linux image. The changes that need to be made are spelled out in the errata - http://support.logicpd.co..._EVM_Beta_Errata.pdf

    TI has all of the SW support on this kit. Please go to their e2e site for software assistance.

    Thanks
    jheoaustin
    New Member
    New Member
    Posts:


    --
    11 Mar 2010 10:38 PM
    Posted By richardl on 5 Mar 2010 1:47 PM
    The early versions of the kits had a uboot without the proper environment variables to boot the linux image. The changes that need to be made are spelled out in the errata - http://support.logicpd.co..._EVM_Beta_Errata.pdf

    TI has all of the SW support on this kit. Please go to their e2e site for software assistance.

    Thanks





    Thank you for your reply. Could you also answer the question about the mtest error messages?

    Best regards
    richard.laborde@logicpd.com
    Basic Member
    Basic Member
    Posts:247


    --
    19 Mar 2010 01:52 PM
    I'm not sure about the memory test error. I seem to recall seeing that somewhere - maybe it was on TI's e2e.ti.com site.

    Thanks
    jheoaustin
    New Member
    New Member
    Posts:


    --
    19 Mar 2010 10:13 PM
    I guess I wasn't clear enough on the question. Could you just tell me if that kind of 'mtest' result on U-boot is expected? Thank you.

    Posted By richardl on 19 Mar 2010 1:52 PM
    I''m not sure about the memory test error. I seem to recall seeing that somewhere - maybe it was on TI''s e2e.ti.com site.

    Thanks


    nathank
    New Member
    New Member
    Posts:11


    --
    25 Mar 2010 12:15 PM
    Try putting memory bounds on the test. For example mtest 0xc0000000 0xc0f70000 works ok for me with U-Boot version 2009.08. I'm guessing if you just run mtest, it might be clobbering some space in the RAM that is being used to run U-Boot.
    Scott Harris
    New Member
    New Member
    Posts:


    --
    23 Nov 2010 01:09 PM
    I am seeing the same mtest results on my L138 Experimenters kit. LogicPD support replied that they see the same thing and didn't seem worried about it. Told me the board was OK to go.
    You are not authorized to post a reply.