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 Oct 2004 06:14 PM by  mike tesch
Do I Have A Wrong Version of BDK or What?
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Kenneth Lerman
New Member
New Member
Posts:


--
18 Sep 2004 08:09 PM
    My BDK is ’02101lh9520bdk.iso’

    The patch file I downloaded contained: lpd-linux-LLH79520-02.tgz

    The "white paper" refers to: tar xzvf lpd-linux-LLH79520-04.tgz

    Clearly NOT the same, but I downloaded it today, so what the heck, I continued.
    The tar command worked fine... sort of. But the file ownership was messed up because the owners of some of the files were not root and I was running as root. (I bet there is another switch to tar that will set the owner to me even if I'm root.)

    So I did a chown -R src/linux scripts. And got a lot further. Until I was unable to execute ./.../split-include. So I chmod +x that file.

    Now I'm up to :

    hd.c:70: asm/arch/platform.h: No such file or directory
    hd.c: In function `dump_status':
    hd.c:218: `CPLD_CE_CS_COMPACTFLASH_REG' undeclared (first use in this function)
    hd.c:218: (Each undeclared identifier is reported only once
    hd.c:218: for each function it appears in.)

    plus lots more errors -- probably all related to the include file.

    What am I missing? What am I doing wrong? Is there another document I should have seen?

    Thanks,

    Ken
    tschoemaecker@micromedical.co.uk
    New Member
    New Member
    Posts:


    --
    29 Sep 2004 10:21 AM
    Hi Kenneth.

    Got exactly the same problem right now. I was wondering if you managed to sort this out...

    Regards,

    Thomas.
    Kenneth Lerman
    New Member
    New Member
    Posts:


    --
    29 Sep 2004 10:42 AM
    Michael Tesh <tesch1@gmail.com> provided me with a set of patches to:

    (ftp://ftp.lineo.com/pub/downloads/smea/ and sharp_lh79520_embedix_bdk.iso)

    That's what I'm using, now. He described the patches as "Beta", so I won't post them without his permission.

    A major problem I'm still having is that writes to the CF (disk) are very (unacceptably) slow. I don't know if that is also true of the release others are using.

    Ken
    miket@logicpd.com
    New Member
    New Member
    Posts:


    --
    01 Oct 2004 03:22 AM
    There is a new version (1.0.1) of the BSP on the website. It has been
    restructured to be easier to use. It's now a set of scripts and
    patches to add support for the card engine to the Lineo 79520
    BDK. Please see the file in the release called "LPD-README" for
    further information about & limitations of this release.
    sreedhar
    New Member
    New Member
    Posts:


    --
    20 Oct 2004 06:26 PM
    Here is a dump of my build

    ---------

    make[3]: Leaving directory `/bdk/lh79520/build/rpmdir/BUILD/linux/arch/arm/nwfpe'
    make -C arch/arm/fastfpe fastdep
    make[3]: Entering directory `/bdk/lh79520/build/rpmdir/BUILD/linux/arch/arm/fastfpe'
    /bdk/lh79520/build/rpmdir/BUILD/linux/scripts/mkdep -D__KERNEL__ -I/bdk/lh79520/build/rpmdir/BUILD/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fno-common -pipe -g -mapcs-32 -march=armv4 -mtune=arm7tdmi -mshort-load-bytes -msoft-float -- CPDO.S CPDT.S CPRT.S entry.S module.c > .depend
    make[3]: Leaving directory `/bdk/lh79520/build/rpmdir/BUILD/linux/arch/arm/fastfpe'
    make[2]: Leaving directory `/bdk/lh79520/build/rpmdir/BUILD/linux'
    make[1]: Leaving directory `/bdk/lh79520/build/rpmdir/BUILD/linux'
    + [ 1 = 1 ]
    + set -x -e
    + export PATH=/opt/Embedix/tools/arm-linux/bin/:/opt/Embedix/tools/bin:/opt/Embedix/bin:/opt/Embedix/usr/bin:/opt/Embedix/usr/local/bin
    + PATH=/opt/Embedix/tools/arm-linux/bin/:/opt/Embedix/tools/bin:/opt/Embedix/bin:/opt/Embedix/usr/bin:/opt/Embedix/usr/local/bin
    + cd /bdk/lh79520/build/rpmdir/BUILD/linux
    + export PATH=/opt/Embedix/tools/native-linux/bin:/opt/Embedix/tools/bin:/opt/Embedix/bin:/opt/Embedix/usr/bin:/opt/Embedix/usr/local/bin
    + PATH=/opt/Embedix/tools/native-linux/bin:/opt/Embedix/tools/bin:/opt/Embedix/bin:/opt/Embedix/usr/bin:/opt/Embedix/usr/local/bin
    + make ARCH=arm CROSS_COMPILE=arm-linux- zImage
    make[1]: Entering directory `/bdk/lh79520/build/rpmdir/BUILD/linux'
    gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/split-include scripts/split-include.c
    scripts/split-include include/linux/autoconf.h include/config
    /usr/bin/find-new: /lib/libc.so.6: version `GLIBC_2.2.3' not found (required by /usr/bin/find-new)
    /usr/bin/find-new: /lib/libc.so.6: version `GLIBC_2.3' not found (required by /usr/bin/find-new)
    /usr/bin/find-new: /lib/libc.so.6: version `GLIBC_2.2' not found (required by /usr/bin/find-new)
    /usr/bin/find-new: /lib-new/ld-linux.so.2: version `GLIBC_2.1.1' not found (required by /lib/libc.so.6)
    scripts/split-include: find: No such file or directory
    make[1]: *** [include/config/MARKER] Error 1
    make[1]: Leaving directory `/bdk/lh79520/build/rpmdir/BUILD/linux'
    make: *** [firsttime] Error 2

    ------------

    Does anyone have an answer

    sreedhar
    mike tesch
    New Member
    New Member
    Posts:


    --
    21 Oct 2004 06:14 PM
    you may have to copy any libraries that the new find binary
    uses into the /opt/Embedix root. please read the scripts to
    understand what is happening. i could only verify the operation
    on SuSE 9.1, any other distributions may require you to
    intervene manually, but the basic ideas of what need to happen
    are expressed in the install scripts. it does require a minimum
    of unix knowledge to understand.
    You are not authorized to post a reply.