LV Embedded with Keil toolchain for ARM 7 series

Hello,
has anybody use LV Embedded with Keil toolchain for ARM processors? We have this development tools in the company ( used by C group of programmers ) and I would like to hook LV Embedded to this toolchain. We also have Phytec phyCORE-LPC2294 development kit.
Any suggestions where to start?
Regards,
Romp

Hi,
There is a way to hook LabVIEW into MicroVision. It has a TCP/IP interface called UVSock. I am attaching documentation on the interface to this message.
Michael P
National Instruments
Attachments:
UVSock.zip ‏19 KB

Similar Messages

  • APEX multi series line chart with different markers for each series

    I am using APEX 4.0 and trying to create a multi-series line chart that will have a different for each series.
    Does anyone know how to accomplish this?
    Edited by: user4635837 on Apr 19, 2011 7:22 AM

    Hello -
    It is possible to do.
    Another user in this forum has written some code snippets to assist in creating your own custom XML for charting. That reference can be found http://apex.oracle.com/pls/apex/f?p=36648:30:418355095936797::NO:::
    Look this over and it should get you moving in the right direction.
    What you are trying to do isn't terribly difficult. In fact, I did it fairly easily as can be seen http://apex.oracle.com/pls/otn/f?p=28155:4:362637005964920:::::
    First, create a Hidden page item.
    Next, create a process that runs before regions
    That process will create the XML for your line chart and store it in the hidden page item. Use the above references for assistance in setting up the PL/SQL in the process
    Then, create your custom XML for your chart. Replace the #DATA# tag in the custom XML with your hidden page item.
    It is a bit daunting at first, but once you get the hang of it, it really isn't that bad.
    Austin

  • LabView for ARM - MCB2300 Audio

    Hi, and thanks for reading!
      My name is Chuck and I'm an undergrad ME student taking a mechatronics course. We were asked to create a proximity alarm with the MCB2300 and an IR proximity sensor. I have the entire program running correctly, but this lab has brought up a couple questions about how to better implement audio with the LabView for ARM processors.
      I understand how interrupts work, and I've seen a couple examples online of using an interrupt with a timed loop, but I believe the current version of LabView (2010) doesn't support that feature any more. I had a couple questions about how to get a feature similar to this to work with LV 2010.
      I was thinking I could have the proximity trigger enable an interrupt that I could use to generate higher quality audio than I am already making with a While - Timer loop. However, I'm not sure how to make an increment in the interrupt VI without using some form of a loop. The solution I'm thinking of at the moment is to make a For loop run once and to have an incrementing integer separate from the loop iteration (which would only go from 0 to 1) that stores its most recent value in the shift register.
      My other question is about playing a sound file through the MCB2300. I wrote a VI that reads a .wav file and writes each sample as the output needed to drive a speaker, but that decompression turns a 10KB .wav file into a 300KB text file. I also don't have a way to really load the text file onto the board. Is there any reasonable way to go about this? I found an example online that processes audio data using the MicroVision software, but I don't want to learn a new language to implement this.
      Sorry for such a long post, I just had a couple questions and was looking for some feedback. Any help would be greatly appreciated.
    Thanks so much!

    charlestrep91 wrote:
    Hi everyone,
    I just got my Labview for ARM cortex M3 evaluation kit and I can't download a simple program to the target. I'm using the Keil ULink 2 programmer and I get this error when compiling/downloading:
    [4:23:16 PM] Status: Error
    SWD Communication Failure
    Error: Flash Download failed  -  Target DLL has been cancelled
    Detail: [UVSC_PRJ_FLASH_DOWNLOAD, MSG: 0X100A, STATUS: Ex.] (1) 
    Status: FLASH download error.
    I have read about this error and NI simply refers to Ulink2 user's guide which has this description for this error:
    Serial Wire Debug communication is corrupted. The target SWD interface is not working properly. Mainly caused by the target: debug block not powered or clocked properly. Avoid Deep-Sleep modes while debugging. Lower the Max Clock frequency in the ULINK USB-JTAG/SWD Adapter section.
    I have tried to "Lower the Max Clock frequency in the ULINK USB-JTAG/SWD Adapter section" but it didn't resolve the problem.
    I have also tried to download the program using the usb port on the dev board but instead I get this error:
    [4:51:22 PM] Status: ErrorUnexpected error occurred.
    [Source: Target is in debug mode
    Detail: [UVSC_PRJ_ADD_GROUP, MSG: 0x1002, 
    STATUS: 0xA] Code: 10]
    What am I supposed to do with that?? I'm wondering if the dev board is defective. And this was supposed to be plug and play...
    Any help is greatly appreciated!
    I'll ask the obvious question, are you intending to use SWD or just download through the JTAG.  Check your settings.  I have not used the ARM with LV, but can you download anything using the Keil software?  Give that a try.  That may tell us where the problem lies.  Try to duplicate your settings in LV from the Keil sw.
    Reese, (former CLAD, future CLD)
    Some people call me the Space Cowboy!
    Some call me the gangster of love.
    Some people call me MoReese!
    ...I'm right here baby, right here, right here, right here at home

  • Demand Paging for E-Series

    When will nokia develop new firmware with demand paging for e-series devices like e61i, e65 and e90 ? we already know that n95 has demand paging. Even n73 has it in the latest firmware. This had sped up n73 tremendously (note: n73 is older than most e-series & it does not have wifi)
    so my question is :
    1) is demand paging exclusive for n-series ?
    2) will future versions of firmware for e-series devices have
    demand paging ?
    3) will there be new versions of firmware for e-series devices as
    fast as nokia has developed new firmware for n-series
    almost every 3-6 months for each n-series model.

    Jaakko Kaidesoja
    N-Gage boss: 'We're not scared of the PlayStation phone'
    N73 will be one of the mobiles supporting the new n-gage platfrom
    http://www.pocketgamer.co.uk/r/N-Gage/N-Gage+(next+gen+platform)/news.asp?c=5917
    The N82 and both N95 handsets will be next in line for the commercial launch, but bad news N73 owners: you're going to have to wait a while.
    "We promised the N73 earlier, but we found some memory issues, as it has a lower memory spec than other devices," says Kaidesoja. "That gives some headaches, but we'll deal with that, and will release for the device during the second quarter."
    so clearly from here we can understand that something drastic is going to be done to the n73 yet again... to support the new n-gage platfrom and improve its performace.... why these improvements are never made to the e-series ?
    PS : can anyone enlighten me on the processor specs for both n73 and e61i...
    Message Edited by jananan on 02-Mar-2008 08:25 PM

  • Can I use the NI DAQmxbase C functions to develop a Smart Device application using a NI USB or NI ENET 9234 C module with Visual Studio for an iMX31 (ARM 11) embedded computer running Win CE 5.0 or 6.0?

    I have an embedded application running on a iMX31 (ARM 11) that does fairly high performance analog input (24 bit, 50K samples/second).  I use Microsoft Visual Studio 2005 C/C++ for the develoment environment and have currently built versions of the application for Win CE 5.0 and 6.0 without Labview or NI hardware.  I have used the NI 9234 with great success on several Labview applications in the past and I'd like to use the 9234 on this embedded application with VS2005 C/C++. The NI documentation hints that I should be able to do this (maybe I'm overly optimistic) and I'm wondering if anyone else has?   I've tried the Evaluation versions of Labview Mobile and Labview Touch panel to build a C application using the NI DAQmx base C function inside Visual Studio without success.  I can compile and link the ContAcq IntClk LV example project for an x86 platform using NIDAQmx but not for a ARM platform using NIDAQmxbase.lib.  I get the same linker error   error LNK2019: unresolved external symbol referred to in Knowledge Base Document ID 4HAEE7QQ  even though I've set up (or think I've set up ) VS2005 as the KB article indicates.
    If anyone has used the C functions and NIDAQmxbase library inside a VS2005 Smart Device project, I'd greatly appreciate your comments.
    Thanks 

    Hello Gene,
    I have been checking into this for you and have found out that what you are trying to do cannot be done.  At least not in the current manner you are hoping for.  The internal architecture of DAQmx Base requires the cross-compiling capability of the LabVIEW Mobile Module. While a stand-alone compiler can compile DAQmx Base calls for desktop processors, it cannot compile DAQmx Base calls for ARM.
    If your application requirements exclude the LabVIEW toolchain, then the remaining option is the USB Driver Development Kit which is avaliable here, but you will have to contact your local field sales representative to discuss support
    options as standard phone and e-mail support are not available for the
    NI Measurement Hardware DDK. 
    NI Measurement Hardware Driver Development Kit
    http://digital.ni.com/express.nsf/bycode/exyv4w?opendocument&lang=en&node=seminar_US
    ColeR
    Field Engineer

  • How to use USB interface with LabVIEW Embedded for ARM

    Hi everybody.
    I am developing an application based on the "LabVIEW Embedded for
    ARM". Now I am doing various tests using
    the evaluation board 2300 (with NXP LPC2378), but soon I will
    dedicate to program the micro used in my project (NXP
    LPC2148).
    During the tests, I have seen that "default" LabVIEW interface allows the use
    of CAN, I2C and SPI interfaces of the micro. I want to know how can I also use the
    USB interface that is on the micros -both LPC2148 and LPC2378- (pin USB_D + / D-, USB_UP_LED,
    USB_CONNECT, VBUS).
    Thanks in advance for your suggestions

    @chueco85
    If you've created an application in LabVIEW for ARM and you build it.
    you can go to tools >> ARM Module >> Show Keil uVision
    then go to he build options.
    the hex file will be created when you do a build.
    with flash magic :http://www.flashmagictool.com/
    you can program your device.
    Wouter.
    "LabVIEW for ARM guru and bug destroyer"

  • Can I use my custom board with LPC2378 processor with ULINK2 on Embedded module for ARM and LV.

    Issues in ARM and LV
    Can I use my custom board with LPC2378 processor with ULINK2 on Embedded module for ARM and LV.How can I create my elemental I/O vis or I have to use the existing Keil board vis. Confused. Please help.
    I have LV8.6. Which ver of embedded module for ARM should I buy. Website shows combined price for ARM module and LV. But I already have LV8.6 so what is the cost of module.
    Regards
    Shradha

              If the processor of your development board  is the cortex-M3 core, I think you do not have to buy keil board. Now, there are a lot of OS and emulator suitable for Cortex-M3.
              Operating system I am referring to  is the real time operating system such as keil RTX,uCOS,FreeRTOS,CooCox CoOS and so on. CooCox CoOS is very new, you can get more information from http://coocox.org/ .
              Emulator or debugging tools such as ULINK2,st-link,Jlink,CooCox Colink and so on. CooCox Colink is also very new.  You can download the Colink Plugin from here Colink Plugin . 

  • Programmin​g STM32 with LV for arm module?

    just asking if someone have experience with this.
    maybe you can give some tips?
    regards,
    Wouter.
    Wouter.
    "LabVIEW for ARM guru and bug destroyer"

    Almost 1,5 year later but,
    I'm working now with the EK-LM3S8962.
    you can programm the STM32 (primer) but you must be able to programm it with a keil debugger (JTAG)
    de primer has a build in debugger (RLINK) and there's no RLINK plugin in KEIL uVision, yes i did try with DLL's
    If I had time I would try it. But I am sure that it is possible
    Wouter.
    "LabVIEW for ARM guru and bug destroyer"

  • Can I target the STM32 Primer2 hardware with LabVIEW for ARM

    The STM32 Primer2 hardware looks very cool.  Can LabVIEW for Arm target this hardware?  From looking at the list of ARM devices supported by LabVIEW, this would appears to be a Tier 2 device (ARM Cortex-M3) with no support for TCP/IP or IO.
    Can anyone tell me the feasibility or effort required to get TCP/IP, IO, and maybe even display support for this device? 
    Message Edited by Jim Kring on 09-11-2009 10:46 AM

    Have you ever said something you wish you could take back after having time to reflect upon it?  Another forum I like, http://newsbusters.org lets the author edit his posts for a short time.  Maybe NI could to that and I would not be pulling out my foot so often.
    Well, perhaps I was a bit more "colorful" than I meant to be.  Frustration does that to me sometimes.  Still the idea of a strong rope covered with disgusting risks does get the point across magnificently.  I just wish I had saved it for something more suitable.
    Let me think back to some of the problems I've had in which I've lost hours trying to figure out...
    1.  Can't use the Wait ms function.  It halts the program.  Express wait works fine.  It was sprinkled throughout which made it hard to isolate.
    2.  Some sub VIs don't run unless they are checked as inline code.  I don't yet understand why.
    3.  At the beginning of my main vi there was a small cluster in which I filled the data from an SD card file.  I used a constant of the cluster on the input of the Bundle function, but because my program and variable sizes were near the max I changed a number of variable representations to save memory.  ...But I didn't replace the constant.  The program started exhibiting really strange behaviors.  I couldn't even get a simple state machine to run.  I was reduced to commenting out (disable structure) sections to find the problem before noticing the coercion dot on the input to the bundle (The dot against the red string color doesn't stand out very strongly which is why I missed it).  Apparently it overwrote memory since the older cluster was significantly larger than the new.
    4.  Spent a lot of time trying to get the SD card to work with SPI functions.  Even though I read that 2009 supported SD card file services I didn't intuitively understand how to wire up since the Open/Create/Replace function has a ref num output which actually connects to the file(use dialog) input of the read and write functions.
    5.  Had a problem with breakpoints and probes not working.  That apparently was caused by item #3.
    6.  Typo bug in the Arm_irq.c file  LM3Sxxxx_GPIOCAHandlerP to LM3Sxxxx_GPIOCHandlerP
    Some of these are of the rope variety. A few are actual bugs.  All probably could have been solved in moments had I a local guru.  Anyway, I've spent hours and my hands hurt.  I hope to have this little project working on the LM3s8962 today and after some hardware changes will port it over to the Primer2... Hopefully...
    This forum has been a real help... especially your quick responses.
    regards to all,
    David 

  • Accessing Onboard ADC with LabVIEW for ARM

    I am working with the LM3S9062 Evaluation board and LabView for ARM system, and want to measure an analog voltage using the ADC, however I cannot determine which of the Digital Inputs is linked to the ADC. I need to know how the gpio mapping corresponds to the pinout of the Device.  Any thoughts?

    Do you mean the LM3s8962 evaluation board?  If so, the pins should be labeled accordingly on the board - ADC0, ADC1, ADC2, etc.
    Drop an EIO node with the same name as the pin and it should work fine from there.
    Here are the schamtics :  http://www.realview.com.cn/UploadFile/2008111510295067433.pdf

  • How to scan with my deskjet f2480 in Windows RT for ARM-processor based tablets or computers.

    How do I scan a document with my HP Deskjet F2480  in Windows RT for ARM-processor based tablets or computers? I have a microsoft Surface tablet and have no problem printing  but it refuses to recognise my deskjet for scanning I have downloaded HP Scan and capture application but no joy

    Hi Billjames0151, welcome to the HP Forums. If one of these methods do not enable you to scan on RT:  How to Scan Windows RT or Windows 8 Tablets
    Then you should try reinstalling it using this method: Install the Printer Software in Windows RT or Windows 8 on a Tablet
    I hope that helps.
    TwoPointOh
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • Create a cross compiler for arm

    I am struggling with building a cross toolchain, essentially it boils down to building these packages (in thegiven order):
    binutils gcc-base newlib gcc
    When done I am trying to compile a dummy cpp algorithm (euler gcd/ggT search) with no includes.
    What the cross toolchain spits at me is the following:
    $ arm-unknown-eabi-gcc -march=armv5te ./euklidisch_ggt.c -o ./euklidisch_ggt.bin.armv5te
    /usr/bin/arm-unknown-eabi-ld: skipping incompatible /usr/lib/gcc/arm-unknown-eabi/4.5.2/../../../../arm-unknown-eabi/lib/libc.a when searching for -lc
    /usr/bin/arm-unknown-eabi-ld: skipping incompatible /usr/arm-unknown-eabi/lib/libc.a when searching for -lc
    /usr/bin/arm-unknown-eabi-ld: cannot find -lc
    collect2: ld returned 1 exit status
    I wrote a little script to build it (as I got pretty much fed up doing it all by hund, round #7 just failed again)
    Note: it is semi-automated, you will still be requested to give your passwd to agree with install and blah
    Note: use it with arg "cleanup" to get rid of old installed packages (run as root)
    Note: use it to compile as user
    #!/bin/bash
    BUILDERUSER=buildmonkey
    PREFIX="/usr"
    TARGET="arm-unknown-eabi"
    PKGBUILDDIR="/home/${BUILDERUSER}/PKGBUILD"
    PKGS="binutils gcc-base newlib gcc"
    export PREFIX
    export TARGET
    export BUILDERUSER
    export PKGS
    export PKGBUILDDIR
    function cleanup
    for j in ${PKGS}
    do
    export j
    echo "Removing package ${TARGET}-${j}"
    su -c'pacman -R ${TARGET}-${j}'
    done
    function compile_and_install
    cd ${PKGBUILDDIR}
    echo ""
    echo ""
    echo "Compileing ${TARGET}-${1} ... "
    echo ""
    echo ""
    cd ./${TARGET}-${1}
    rm ./${TARGET}-${1}*
    makepkg -f || return 1
    su -c 'pacman -U ./${TARGET}-${1}*'
    echo ""
    if [ "${1}" == "cleanup" ]; then
    echo "cleanup requested...."
    cleanup
    exit 0
    fi
    if [ "$(id -u)" == "0" ]; then
    echo "This script must not be run as root!!" 1>&2
    exit 1
    fi
    echo ""
    if [ -d "${PKGBUILDDIR}" ]; then
    echo "PKGBUILD directory is ${PKGBUILDDIR}"
    else
    echo "PKGBUILD directory ${PKGBUILDDIR} is missing!!"
    exit 1
    fi
    echo "PKGs are ${PKGS}"
    echo ""
    for i in ${PKGS}
    do
    compile_and_install ${i}
    done
    exit 0
    The packagebuilds are as following (hacked away versions of the ones existing in AUR, which give me linker errors)
    binutils
    pkgname=arm-unknown-eabi-binutils
    pkgver=2.21
    pkgrel=1
    pkgdesc="A set of programs to assemble and manipulate binary and object files"
    arch=(i686 x86_64)
    license=(GPL)
    options=(!libtool)
    url="http://sources.redhat.com/binutils"
    depends=('glibc' 'zlib')
    source=(ftp://ftp.gnu.org/gnu/binutils/binutils-${pkgver}.tar.bz2)
    md5sums=('c84c5acc9d266f1a7044b51c85a823f5')
    build() {
    cd $srcdir/binutils-${pkgver}
    [ $NOEXTRACT -eq 1 ] || ./configure\
    --prefix=${PREFIX} \
    --program-prefix=${TARGET}- \
    --enable-shared \
    --disable-multilib \
    --with-lib-path=${PREFIX}/lib/binutils/{TARGET} \
    --disable-nls \
    --target=${TARGET} \
    --build=${CHOST} \
    --host=${CHOST}
    # mkdir -p $pkgdir/${PREFIX}/lib/binutils
    sed -i 's|know (S_GET_VALUE (frag->tc_frag_data.last_map) < S_GET_VALUE (symbolP));|{know (S_GET_VALUE (frag->tc_frag_data.last_map) < S_GET_VALUE (symbolP));}|' gas/config/tc-arm.c || return 1
    make configure-host
    make tooldir=$pkgdir/${PREFIX}
    make prefix=$pkgdir/${PREFIX} tooldir=$pkgdir/${PREFIX} install
    mkdir -p $pkgdir/${PREFIX}/lib/binutils/${TARGET}
    cp -v include/libiberty.h $pkgdir/${PREFIX}/lib/binutils/${TARGET}
    rm -f $pkgdir/${PREFIX}/man/man1/{dlltool,nlmconv,windres}*
    rm -f $pkgdir/usr/bin/ar
    rm -f $pkgdir/usr/bin/as
    rm -f $pkgdir/usr/bin/ld
    rm -f $pkgdir/usr/bin/nm
    rm -f $pkgdir/usr/bin/objdump
    rm -f $pkgdir/usr/bin/ranlib
    rm -f $pkgdir/usr/bin/strip
    rm -f $pkgdir/usr/bin/objcopy
    rm -f $pkgdir/usr/lib/libiberty.a
    rm -rf $pkgdir/usr/share
    rm -rf $pkgdir/usr/lib/ldscripts
    gcc-base
    pkgname=arm-unknown-eabi-gcc-base
    pkgver=4.5.2
    pkgrel=1
    pkgdesc="The GNU Compiler Collection"
    arch=(i686 x86_64)
    license=('GPL' 'LGPL')
    url="http://gcc.gnu.org"
    depends=('arm-unknown-eabi-binutils' 'libmpc' 'libelf' 'cloog-ppl')
    options=(!libtool !emptydirs zipman docs !strip)
    source=(ftp://gcc.gnu.org/pub/gcc/releases/gcc-${pkgver}/gcc-core-${pkgver}.tar.bz2)
    md5sums=('aa9e36bec080452372bfba793428ee82')
    build() {
    cd $srcdir/gcc-$pkgver
    export CFLAGS="-O2 -pipe"
    export CXXFLAGS="-O2 -pipe"
    [ $NOEXTRACT -eq 1 ] || rm -rf build
    mkdir build
    cd build
    [ $NOEXTRACT -eq 1 ] || ../configure --prefix=${PREFIX} \
    --target=${TARGET} \
    --host=$CHOST \
    --build=$CHOST \
    --enable-shared \
    --disable-nls \
    --enable-languages=c \
    --enable-multilib \
    --with-local-prefix=${PREFIX}/lib/${TARGET} \
    --with-as=${PREFIX}/bin/${TARGET}-as \
    --with-ld=${PREFIX}/bin/${TARGET}-ld \
    --enable-softfloat \
    --with-float=soft \
    --with-newlib
    make all-gcc all-target-libgcc
    make DESTDIR=$pkgdir install-gcc install-target-libgcc
    rm -f $pkgdir/usr/share/man/man7/fsf-funding.7*
    rm -f $pkgdir/usr/share/man/man7/gfdl.7*
    rm -f $pkgdir/usr/share/man/man7/gpl.7*
    rm -rf $pkgdir/usr/share/info
    cp -r $pkgdir/usr/libexec/* $pkgdir/usr/lib/
    rm -rf $pkgdir/usr/libexec
    # strip it manually
    strip $pkgdir/usr/bin/* 2>/dev/null || true
    find $pkgdir/usr/lib -type f -exec arm-none-eabi-strip {} \; 2>/dev/null || true
    newlib
    pkgname=arm-unknown-eabi-newlib
    pkgver=1.19.0
    pkgrel=1
    pkgdesc="Newlib is a C library intended for use on embedded systems."
    arch=('i686' 'x86_64')
    groups=('devel')
    url="http://sourceware.org/newlib/"
    license=('GPL')
    depends=('arm-unknown-eabi-binutils' 'arm-unknown-eabi-gcc-base')
    source=(ftp://sources.redhat.com/pub/newlib/newlib-${pkgver}.tar.gz)
    md5sums=('0966e19f03217db9e9076894b47e6601')
    build() {
    cd ${srcdir}
    rm -rf build
    mkdir build
    cd build
    export CFLAGS="-O2"
    ../newlib-${pkgver}/configure \
    --target=${TARGET} \
    --prefix=${PREFIX} \
    --enable-interwork \
    --enable-multilib \
    --with-gnu-as \
    --with-gnu-ld \
    --with-float=soft \
    --disable-nls || return 1
    make || return 1
    make -j1 DESTDIR=${pkgdir} install || return 1
    rm -rf ${pkgdir}/usr/share/info
    return 0
    gcc:
    pkgname=arm-unknown-eabi-gcc
    pkgver=4.5.2
    pkgrel=1
    pkgdesc="The GNU Compiler Collection - Cross compiler for ARM target"
    arch=(i686 x86_64)
    license=('GPL' 'LGPL')
    url="http://gcc.gnu.org"
    #an installed libc/newlib is needed for libstdc++ compile
    depends=('arm-unknown-eabi-binutils>=2.18' 'cloog-ppl>=0.15.3' 'arm-unknown-eabi-newlib>=1.18.0')
    # cross-arm-none-eabi-gcc is an superset of cross-arm-none-eabi-gcc-base
    conflicts=('arm-unknown-eabi-gcc-base')
    provides=("arm-unknown-eabi-gcc-base=${pkgver}")
    options=(!libtool !emptydirs !strip zipman docs)
    source=(ftp://gcc.gnu.org/pub/gcc/releases/gcc-${pkgver}/gcc-${pkgver}.tar.bz2)
    md5sums=('d6559145853fbaaa0fd7556ed93bce9a')
    build() {
    cd ${srcdir}/gcc-$pkgver
    export CFLAGS="-O2 -pipe"
    export CXXFLAGS="-O2 -pipe"
    rm -rf build
    mkdir build
    cd build
    ../configure \
    --prefix=${PREFIX} \
    --target=${TARGET} \
    --build=${CHOST} \
    --host=${CHOST} \
    --disable-nls \
    --enable-multilib \
    --enable-languages=c,c++ \
    --enable-__cxa_atexit \
    --enable-interwork \
    --with-local-prefix=${PREFIX}/lib/${TARGET} \
    --with-as=${PREFIX}/bin/${TARGET}-as \
    --with-ld=${PREFIX}/bin/${TARGET}-ld \
    --with-newlib \
    --with-float=soft
    make all-gcc all-target-libgcc all-target-libstdc++-v3 || return 1
    make DESTDIR=${pkgdir} install-gcc install-target-libgcc install-target-libstdc++-v3 || return 1
    rm -f $pkgdir/usr/share/man/man7/fsf-funding.7*
    rm -f $pkgdir/usr/share/man/man7/gfdl.7*
    rm -f $pkgdir/usr/share/man/man7/gpl.7*
    rm -rf $pkgdir/usr/share/info
    rm -rf $pkgdir/usr/share/gcc-4.5.2
    cp -r $pkgdir/usr/libexec/* $pkgdir/usr/lib/ && \
    rm -rf $pkgdir/usr/libexec
    I already read linux from scratch howto for building cross compilers, though partly it contradicts with AUR comments especially in regard to --with-sysroot and --with-build-sysroot
    If someone can please shed some light on this, the gcc doc is not very helpfull
    Note: I know that a bare metal arm elf cross compiler exisis in the archlinux repository but that is not sufficient as I need different targets with some special options (where can I get the PKGBUILD from packages within the ABS?)

    Current targets are armv7vfpv3 and armv5te softfloat, this compiler(s) (afaik softfloat and hardfloat can not be put into one compiler, correct me if I am wrong) will be used as basis for kernel compileing for these architectures plus the basic packages (afaik called bootstrapping).
    And I knew it was not really newby stuff, but .. well .. after searching like 5 mins for an appropriate subforum I gave up and posted it just here, sorry
    The point is this is the basis for a lot of core packages and I just want to do it right (and atm it ain't working at all )
    Last edited by drahnr (2011-04-05 22:36:11)

  • Jave ME Embedded support KEIL MCBSTM32F200 and Raspberry Pi Model B ONLY???

    I am a JEE developer and quite new to Java ME Embedded ( just started 12 hours ago), I am confused in following questions, please help, thanks!
    1. Java ME Embedded 3.3 is support KEIL MCBSTM32F200 and Raspberry Pi Model B ONLY? Or any ARM Cortex M3/RTX and ARM 11/Linux architecture? Does if have supported embedded board/architecture list?
    2. If the answer to #1 is no, does that mean that I the reference implementation KEIL MCBSTM32F200 can be used on any ARM Cortex M3/RTX architecture and Raspberry Pi Model B can be used on any ARM 11 architecture?
    3. if the answer to #1 is no, how should i choose the embedded board for Jave ME Embedded for general purpose (give some recommendation is ok)?
    4. If the answer to #1 is YES, that should be limit usage of Jave ME Embedded on KEIL MCBSTM32F200 and Raspberry Pi Model B; and it can't be used on other embedded device. Or I have to choose Java ME Embedded Client or Java SE Embedded ( this will take more resource, but I only have limitted resource)? Is my understand correct? Does Java ME Embedded has roadmap to support wide embedded device?
    Thanks for your time!
    Best regards
    Michael

    Hi Michael,
    Sorry for the slow reply. Some answers:
    Our officially supported Cortex-M platform for Java ME Embedded 3.3 is the KEIL MCBSTM32F200, which is based on the STM32F207 chip. There is a very similar STMF32407 chip, which is used on KEIL MCBSTM32F400 and we've verified Java ME Embedded 3.3 works there as well. It is likely that Java ME Embedded runs on other platforms using the STM32F207 or 407 chips, but it is impossible for us to verify all these platforms. If you get a chance to try one of those we would love to hear about your experiences.
    For Java ME Embedded on ARM11/Linux: RasPi Mod B is our officially supported platform. Unfortunately, the Linux support for some of the peripherals needed by Java ME Embedded (such as GPIO and I2C) is inconsistent - this is a function of the state of the Linux device drivers, not of Java ME Embedded. We are looking into providing wider support for ARM/Linux platforms in the future, which isn't difficult, but we just haven't gotten around to it.
    Generally, when deciding on specific hardware for a particular use case it very much depends on the details. If it is a customized system based on the STM32F207 or 407 chips then the need for porting/customization of Java ME Embedded should be minimal. If it is a customized system based on ARM/Linux, please contact us as we are already looking into widening support for ARM/Linux. Finally, if you are targeting a system that is very different from the above, then you can work with Oracle or Oracle partners for an optimized port of Java ME Embedded to your platform.
    Finally, we are planning to provide support for additional platforms in the near future - stay tuned for announcements.
    Hope this helps. Let me know if you have more questions.
    Best,
    Terrence Barr
    Product Manager, Oracle

  • JRE OR JDK just for ARM processor

    Dear friends,
    Really need you help, please, please.
    Firstly, I need help to know where I can download a jre or jdk just for ARM 9 Processor. I found one on the website of http://www.blackdown.org, and I try to use tar to extract it in hyperterminal of Windows XP OS, but always problems. Do you know where I can get one which is good to use. Please, please, please
    Then, I want to ask if the file for ARM Processor "j2re-1.3.1-RC1-linux-arm.tar.bz2" is good to use, how can I install it in ARM Embedded Linux OS. What I did through hyperterminal which link to ARM Processor as follows:
    step 1: mkdir test
    step2: mount dev\sda1 \test
    step3: tar -xvf j2re-1.3.1-RC1-linux-arm.tar.bz2
    after this, it's always displayed as invalid magic, no such file or sth. like that.
    Please, please give me some suggestions, what's wrong with that? Really sad, sad, sad!!!
    Thank you very much.

    I need jvm for 32bit arm processor. Moreover the size of jvm must be small. Can anybody provide some information.
    Regards,
    Nitin

  • Did any body success to toggel Port0 and Port1 on MCB2300 board using LV for ARM?

    I am trying to toggel the GPIO (Port0, Port1) on MCB2300 evaluation kit with LPC2378 uController on board using LV8.6. these two ports seems to dont have any programmable functionalities using LV. Ports 2, 3 and Port4 are working good. If any body got these two ports in working, so it will be great if you could post a functional LV or C code here in the forum.
    I will be thankful for any suggestions or tips.
    Greetings
    Solved!
    Go to Solution.

    Thank you very much Gmg for
    this excellent answer.
    This modification makes
    also a +ve affect on the I2C port0.
    Where I had/have also a problem to communicate
    with a slave device using I2C. After this modification the I2C-CLK works, but I
    still getting no communication to my slave device. I think the problem is now
    how shall I use the I2C VIs shipped with LV for ARM embedded?
    I have posted this question
    here:
    http://forums.ni.com/ni/board/message?board.id=170&message.id=370126&jump=true#M370126
    so if you could answer me
    PLZ post your answer there. 

Maybe you are looking for