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 17 Dec 2004 06:26 PM by  elf-coastal@buici.com
BLOB fail to run
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages
benlau@linux.org.hk
New Member
New Member
Posts:


--
08 Dec 2004 08:17 PM
    hi all,

    Firstly , Thanks Marc Singer for his great work to provide useful information and Linux support from his site..

    Unfortunately, I could not bring the blob up in my LPD7A400 using the precompiled wblob.bin or self compiled blob using the patch from http://projects.buici.com/arm/lpd7a400/. According to the instructions provided , I first load the wblob.bin into the SRAM address of 0xB0000000 , and then run from this address. The blob screen could show correctly , and then i flashed the binary into address 0x0000 0000 to replace bolo/lolo.

    However , after reset the board , nothing was shown on the console.

    In tracing the codes using a Wiggler-compitable JTAG , I found that blob hang in mem_test_loop. The data wrote to SDRAM could not be read correctly. I did tried to write it manually , the result are same in blob.

    I guess that is the SDRAM did not initializated correctly. Do it have any SDRAM initialization code available other than the codes in blob? or it should not replace bolo , but instead it should flash to the address of lolo?

    Thanks for any advise.
    Anonymous
    Posts:


    --
    13 Dec 2004 03:55 PM
    ben,

    Logic does not directly support blob. However I would encourage you to contact Marc Singer or Sharp with more questions pertaining to blob.

    Thank you,
    tom@cyberiansoftware.com
    New Member
    New Member
    Posts:


    --
    13 Dec 2004 10:57 PM
    I've had similar experience. The wblob binary wouldn't run, so I built from his source. Unfortunately, it appears that the blob sources he used is the release, not the CVS. I found that that blob would not work with the CFI flash. It appears, from the source, that this uses the older flash interface.

    I've recently grabbed the CVS sources and started in the process of bringing that up. So far, I have the patches in place but it hasn't run yet. That's when I got off on a tangent and started learning the ARM asm language as I needed to have some thing to say "here I am!". That's when I ran into the problem of the CPLD vs. PCMCIA vs. LEDs.

    Still, I have control over the processor, can build a standalone binary that will boot. Now, to turn back and look again at the CVS source to get that running. The sources from CVS have some advancements not available in the release. Notably it handles CFI Flash.
    elf-coastal@buici.com
    New Member
    New Member
    Posts:


    --
    17 Dec 2004 06:26 PM
    I've written a new boot loader to deal with the myriad of problems with blob. I haven't posted it, yet, because I'm using it on another project. When I release the next milestone for that project, I'll post the new loader.

    In a nutshell, I've found blob to be unmaintainable. It is really tough to build and it is configured in too many different places. The new loader uses the build code from the kernel which guarantees correctness of the binary.

    The new loader already works with the lpd7a400. I'll post again in a couple of weeks when I've got things settled.

    Cheers.
    You are not authorized to post a reply.