Labview arm spi protocol

Hi,
I`m trying to read out an Interpolation-Hardware using the SPI-Port of the lm3s8962-Eval-Board.
Does anybody know the type of SPI-protocol used in the Labview-ARM-Toolkit.
For my Slave-Hardware i need the Freescale-Protocol(16Bit)....
At the moment i can sent data but i dont recieve anything.
I also need to know if its possible to change the settings of the SPI-Configuration(maybe to change the time between data-packeges).
I`m using: Labview2011+Labview Embedded for ARM-Module+lm3s8962-Eval-Board(not the usb-type)+GEMAC IP2000 (Ipo-IC).
Thank you for help!

I think as SPI doesn´t specify a particular protocol so do the LabVIEW ARM SPI functions.
You are free to change all the parameters the Interface offers, so there is no special protocol used with the
LabVIEW ARM Module. Please check out the SPI-documentation of your slave with respect to timing and clock configuration.
I´m sorry, but thats all I can say.
Marco Brauner NIG

Similar Messages

  • Implementing SPI protocol using PXI-7833R

    Hello everyone,
    I'm trying to implement SPI protocol using PXI-7833R, so that it should behave as a SPI master and should be able to communicate with a SPI device (treated as slave).
    Now I already found an example, but the problem is, this example uses cRIO-9103 as FPGA target and in my case I'm going to use PXI-7833R as FPGA target, and when I'm changing the target (from cRIO-9103 to PXI-7833R), I dont know how to map I/O's listed under 'Chassis I/O' (under cRIO) to the new target (which is PXI-7833R).
    I am not allergic to Kudos, in fact I love Kudos.
     Make your LabVIEW experience more CONVENIENT.

    Hi All,
    Somehow I was able to change the target (from cRIO to PXI-7833R).... but now I'm getting an error while trying to compile the code.
    The error description is:
    "Multiple objects are requesting access to a resource through a resource interface from both inside and outside the single-cycle Timed Loop, which is not supported.
    Place all objects requesting access to the resource interface either inside or outside the single-cycle Timed Loop."
    I am not allergic to Kudos, in fact I love Kudos.
     Make your LabVIEW experience more CONVENIENT.

  • What is the pin map for chip select on LM3S8962 for "ARM SPI Create Configuration Reference.vi" ? (0 through n)

    Hello All,
    When the LM3S8962 is the master, what pin is used when chip
    select is the default (0), or another value ?
    Despite this question being asked a few ways in the forums,
    NI's "ARM SPI Create Configuration Reference.vi" documentation
    for chip select is unclear.
    TI's manual is no help for NI's implementation of chip select.
    NI's help for the above subvi seems not only too generic (perhaps
    written for the SDK ?),  but erroneous in that it reads:
    "chip select specifies the chip select line to assert during the
    SPI transfer. The chip select line must connect to the EEPROM
    on the
    microcontroller. Refer to the documentation for the SPI
    device for information
    about chip select lines."
    This is useless as the ARM microcontroller has no EEPROM and 
    the SPI slave device documentation only covers its own pins.
    The hope is to have more than one slave on the LM3S8962's single SPI bus,
    without chewing up a additional pin using elemental I/O like the splendid forum
    examples for ADC's and DAC's.  This would save diagram real estate compared
    with two sequence frames that are typically shown toggling a elemental I/O digital
    output before and after writing and/or reading from the slave.   It also would clarify
    what on chip resource trade offs there are for each chip select number chosen.
    (as most pins have multiple possible functions)
    Thanks in advance for any light on this.   Please don't post info on other processors
    to this thread as this taints future searches on this issue with this tier 1 target.
    Best,
    Davy

    Hi Davy,
    While doing research on this question, I was informed that you have been working with a colleague of mine, Joel, via email for this same question. So that we do not have multiple engineers working on the same issue, Joel will be your point of contact for this issue. I ask that when you have come to a resolution, that you post that resolution here so that other customers can reference this information.
    Thanks!
    Aaron P
    National Instruments
    Applications Engineer
    http://www.ni.com/support

  • Labview arm module

    hi every one,
            my project is remote patient monitoring using arm with labview based embedded plotform..I have the  arm7  LPC(2378)  processor  . can i use import labview arm module in that processor...also give some useful link to the project...

    Don't know about your project, but LabVIEW Embedded Module for ARM Microcontrollers "project" is here:http://www.ni.com/arm/

  • Program LPC2378 with code generated by LabView ARM embedded, without using LabView

    I would like to use the C files that are originally generated in LabVIEW ARM embedded module, and use Keil software (or other lower cost) to load these files into custom boards with LPC2378 controller without LabView.  Are there detailed instuctions for this?  I am using version 8.6 and the ARM embedded module is 1.1.  
    My reason for this task is boards are being made in a maufacturing facility oversees, and they need to be programmed at their end. 
    I read a forum describing the use of  hex files, but not enough detail for me to figure this out.
    Thanks in advance.

    Hey Bob,
    What you're looking to do should be possible. You'll just need to build the application in LabVIEW, then you should be able to use the uVisions command line to deploy the system. As for the C code itself, it gets generated when you build your build specification and you should see it placed in the same directory as your labview project in a folder named the name of your project. For example, if your project were called My ARM Project, you'll see a folder called "My ARM Project" created/updated whenever you build the build specification in that project and it will contain the C Code. To see the code organized logically, after building your build specification, right-click on the ARM target and select "Show Keil uVision". This will open a uVision window in "LabVIEW mode" and you'll be able to see all of the C files associated with you application; your VI specific code will be under a folder titled "VIs". You could also just open the C code files from disk in uVision, which is what you'll need to do if LabVIEW isn't installed. The main LabVIEW project can be found in the built directory described above as the LabVIEW.uvproj file in the "target"/Application/"uvision version"/Project directory. For example my main file was built in MyProject\EK_LM3S8962\Application\4.01\Project. From there, you'll need to follow uVision's process for compiling and deploying the target code from their command line:
    Command Line
    http://www.keil.com/support/man/docs/uv4/uv4_comma​ndline.htm
    Hope this helps!
    --Ryan_S

  • How can we store code permanent into lm3s8962 through labview arm module?

    I am using labview 2012with arm module.I got problem that my code is not store  permenent  into lm3s8962 luminary board so when i unpuggled the board then loaded code erased. so is their any setting should done which can store code permenent into the  lm3s8962 luminary board..?

    After a build in LabVIEW you can see the code in KEIL uVision. I think that your project is already set to download it to the flash.
    I think you have set the option in de LabVIEW build: enable debugging and Generate guard code.
    when you uncheck them, your application wont need a kick from your debugger to start the application..
    Wouter.
    "LabVIEW for ARM guru and bug destroyer"

  • Project build problem - Labview ARM STM32F103

    Hello,
    i`m trying to make project using LabVIEW Embedded Module for ARM Microcontrollers 2010 and my STM32F103 board. Everything is fine . I made new project, added some outputs, but when i try to build it, it stucks for a while and I get error:
    [17:38:59] Status: Error
    Unexpected error occurred.
    [Source: Cannot read project file 'C:\Users\Sh\
    Documents\Untitled Project 1\STM32F103x\
    Application\0.061\Project\LabVIEW.uvproj' !
    Timed out waiting for a response
    Detail: [UVSC_PRJ_LOAD, MSG: 0x201F, STATUS:
    0x1D] Code: 29]
    I`m using that target : http://forums.ni.com/ni/attachments/ni/420/2699/1/STM32F10x.zip
    Any ideas what might be wrong?
    Thanks.

    Hi mark331
    I would recommend You to go in details through forum http://forums.ni.com/ni/board/crawl_message?board.id=420&message.id=1886. There is multiple number of tips and instructions about ARM STM32F103 and LabVIEW.
    I am pretty sure, that You can find an answear there.
    Best regards
    Barbara

  • Labview ARM embedded Module

    I just watched the NI webcast of the ARM module for labview where it
    shows how you can download an application directly onto a target (NI)
    arm board...
    Anyone know if you can download it onto a non-NI arm board? Besides
    a usb-jtag connection, I would imagine that the user would need to
    program some sort of custom board support package in order for labview
    to know what variety of ARM processor its working with.
    Also, is there a way to hand tweak the generated c-code and compile
    it separately. Don't know what ARM compiler NI uses (probably gnu
    based), or if it's even selectable, but we use different arm compilers
    on different projects, so it would be nice to compile and link labview
    generated code to some of our existing code/libraries.

    Behind the scenes, the LabVIEW Embedded Module for ARM Microcontrollers
    uses the Keil uVision development toolchain to compile, download, and
    debug applications on ARM Microcontrollers.  Therefore, any devices
    that are supported by the RL-ARM Real-Time Library can be programmed
    with LabVIEW. Have a look at the following article:
    ARM Devices Supported by LabVIEW
    If you would like to run LabVIEW on another processor, read this tutorial on using a Tier2 ARM device with the LabVIEW Embedded Module for ARM Microcontrollers.
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • Portage Labview ARM module sur Atmel AT91SAM9263 - Problème de debug

    Bonjour, je suis actuellement en projet d'études et je doit utiliser Labview sur un ARM9 d'Atmel : le AT91SAM9263.
    J'ai suivi le tutoriel de NI pour effectuer le portage mais je n'arrivepas à debugger avec Labview.
    En compilant avec Labview puis en passant seulement par Keil j'arrive à debugger mais cela ne sert à rien car le code généré par Labview est difficilement compréhensible. L'intérêt est donc de passer par le debug via Labview mais cela ne marche pas.
    J'obtiens l'erreur suivante :
    [10:53:09] Status: Error
    Timed out waiting for a response
    Detail: [UVSC_DBG_ENTER, MSG: 0x500E, STATUS: 0x1D] (29)
    Status: Run failed.
    Est-ce que quelqu'un aurait une idée pour résoudre mon problème ?
    Peut être que quelqu'un a déjà effectué ce portage et pourrait m'aider.
    Merci d'avance

    Duplicate
    Benjamin R.
    R&D Software Development Manager
    http://www.fluigent.com/

  • LabVIEW ARM LPC2388

    Bonjour,
    Actuellement je travail avec une carte d'évaluation MCB2300 équipée d'un micro contrôleur LPC2388, celui-ci dispose de 64kB de SRAM au lieu de 32kB pour le LPC2378. Je souhaite créer une cible générique propre au micro contrôleur LPC2388. Pour cela j'ai besoin de recompiler plusieurs librairies afin de les adapter à ce micro contrôleur.
    1)CAN_LPC2378.lib et RLARM_CAN.lib situés LabVIEW2010\Targets\keil\Embedded\RealView\generic\LPC2378\Template\Drivers\CAN. Pour cela j'aurai besoin du fichier projet Keil afin de modifier le type du micro contrôleur dans le projet puis recompiler le projet afin de recréer les librairies adaptées au LPC2388. Où ce trouve les fichiers projet permettant de recompiler ces librairies ?
    2)MCB2300IO.lib située en LabVIEW2010\Targets\keil\Embedded\RealView\MCB2300\Template\Drivers\IO afin de faire la même operation qu'en 1)
    3)FS_ARM_L.lib et TCP_ARM_L.lib situées en Keil\ARM\RV31\LIB. Concernant ces librairies fournies par Keil, je pense qu'il n’est pas nécessaire de les recompiler. Mais quelqu'un pourrait-il me le confirmer.
    Merci d'avance pour vos réponses

    Bonjour,
    Effectivement, pour appeler une fonction C à partir d'un code inclu dans un fichier C, il suffit d'appliquer la méthode que vous avez décris. Par contre je me permet de vous exposer la méthode que vous avez utilisé en la completant et en donnant un Fichier projet exemple en pièce jointe.
    Le programme réalisé pour l'exemple consiste à realiser une addition et une soustraction à partir de 2 variables A et B. L'addition et la soustraction sont réalisées en utilisant 2 fonctions écrite en C. le code de ces fonctions est inclus dans le fichier operations_base.c. Les fonctions C d'addition et de soustraction sont appelées dans le VI principale par le VI appeler une fonction d'un DLL. L'exemple fonctionne pour une cible LPC2378. Voici la procédure à suivre pour réaliser le fichier projet ARM.
    1) Inclure dans le fichier projet LPC2378, le fichier operations_base.c contenant les fonctions. en faisant un clic droit sur la cible puis en sélectionnant Ajouter/Fichier...
    2) Dans le VI principal Test001.vi inserer le VI Appeler une fonction d'une DLL situé dans la palette fonction/Connectivit/Librairies and Executable.
    3) Configurer le VI Appeler une fonction d'une DLL en faisant un clic droit  Configuer...
    Onglet Fonction
    Dans le champ nom de fonction : mettre le nom de la fonction c appelée. Dans notre cas il s'agit de la fonction AdditionAB ou SoustractionAB
    Onglet Paramètres
    Ajouter les paramètres d'entrée/sortie de la fonction C
    -Paramètres entrés A et B
    Nom : A ou B
    Type : Numérique
    Type de données : Entier 32 bits signé
    Passer : Valeur
    -Paramètre de sortie resultat
    Nom : resultat
    Type : Numérique
    Type de données : Entier 32 bits signé
    Passer : Pointeur sur valeur
    Si le fonction a été correctement définie, nous devons avoir dans le champ prototype de la fonction en bas de la fenêtre
    void AdditionAB(int32_t A, int32_t B, int32_t *resultat)
    Cliquer sur OK pour terminer.
    4)Ajouter le fichier C dans les spécifications de construction  en faisant un clic droit sur Application/Properties
    Catégorie/Source File
    Ajouter le fichier C opérarions_base.c dans aditionalFiles (*.c, *.s, *.o, *.lib)
    Cliquer sur OK pour valider
    5) Sauvegarder tous le projet, compiler le tout et executer sur la cible LPC2378
    De même pour appeler une fonction c à partir d'un fichier librairie .lib. Il faut je pense ajouter ce fichier au projet, configurer le VI Appeler une fonction d'une DLL avec le paramètre d'entrée/sortie de la fonction C, inserer le fichier.lib dans les specifications de construction, sauvegarder le projet et compiler.
    Cordialement
    Pièces jointes :
    test001.zip ‏10 KB

  • MyDAQ to control a DAC using SPI protocol

    Hello,
    I'd like to control two DACs in daisy channel configuration with the NI-myDAQ. Both DACs are compatible with SPI standard. However, I'm not able to find any SPI drivers for myDAQ.
    Are there any SPi drivers for myDAQ? Is it possible to achieve my purpose?
    Thank you.

    Hello estefaniapc
    Why do you think there is SPI drivers for a DAQmx device?
    You can implement a SPI communication with timed digital lines (like HSDIO)
    http://zone.ni.com/devzone/cda/epd/p/id/6163
    but myDAQ cannot

  • How to access LPC 2368(NXP) board with Labview arm

    I have Lpc 2368(NXP) customize board. I want to access the board usng Labview. I have done this using Keil but not able to do this with Labview. There are lots of tutorial for lpc2138 but I am not able to find out for LPC 2368.

    Hi Kolakanuru,
    Thanks for using our discussion forums. How you connect your limit switches depends on what type of motion board you are using. For example, if you look at the connection diagram for a PCI-7344, you can see that Forward Limit switches connect to pins 39, 45, 51, and 57. These will then pin out directly to the UMI. For the connection diagram for your particular motion control board, you can go to www.ni.com/manuals and pull up the necessary information. In regards to reading this in LabVIEW, the first thing you will want to check out is Measurement and Automation Explorer. In the interactive windows for your board, you can check the limit switch status there- Press your limit switch on and off and make sure that it changes the LED in MAX. Once that i
    s all set, then you can go into LabVIEW and use the "Read Limit Status" VI which you can find in Functions>>All Functions>>NI Measurements>>Motion>>FlexMotion>>Motion I/O palette. Good luck with your application.
    Regards
    Dan
    National Instruments

  • Labview ARM embedded systems tutorial

    good day,
    I started working on a project using the LM3S8962 development board to work initially lencuaje C, is very economical and in many cases better than the Arduino
    but I see that you can also work with Labview, if someone worked on it and can give me some information would greatly appreciate it
    Atom
    Certified LabVIEW Associate Developer
    Solved!
    Go to Solution.

    Hi Tom,
    If you have questions about the hardware/pins itself, I would consult the user guide for this piece of hardware. For example, here: http://chess.eecs.berkeley.edu/eecs149/sp09/docs/EK-LM3S8962_EvalBoard_UM.pdf
    The software/hardware connection is mostly pretty straight forward. For example, if you create an Elemental I/O point and select PWM0, then whatever you send to that node will go to the pin labeled on your board as PWM0. Also, there are a number of properties in software that you can configure in software for the PWM output: http://zone.ni.com/reference/en-XX/help/372459E-01/lvarmhelp/arm_eio_prop_pwm/
    If you have specific questions or specific things that aren't working, I may be able to assist you, but I think that's all the general support material that we have.

  • LabVIEW ARM break after update Front Panel during debug

    I try to debug the vi by Ulink, the vi just show the LED blinking for 500ms on/off with while infinity loop, after click run button the loop continue working about 5 second and then break button actived with front panel update. Is this normal working?
    Thank you

    After I click Run button on the toolbar the vi start ranning, the LED blinking show on the hardware but not update to the vi front panel, around 3 second the vi stop (like a we click on Pause button on toolbar) and update the status LED to front panel.
    I used ULINK1 for this example, I don't know this cause of the problem or not.
    Thank you.
    Attachments:
    vi_stop.JPG ‏25 KB

  • Does LabVIEW support Mobile and Wireless Protocols?

    Does LabVIEW support these protocols;
    3G     GSM        PHS   
    4G     HCSD        TACS   
    CDMA     HSDPA        TDMA   
    CDMA2000     iDEN        TD-SCDMA   
    EV-DO     Mobitex        UMTS   
    FDMA     NMT        WCDMA   
    GAN     PCS        WiDEN   
    GPRS     PDC        WiMAX    
    If it does (some or all) of these protocols, what do I need to install to get VIs supporting these protocols (I mean which packag/ toolkit etc contians supporting VIs/ functions etc)?
    Thanks for your help!
    Have a very pleasant day!

    Most of these protocals are OS-supported. LabVIEW doesn't have lower level interface VIs.
    For instance LabVIEW doesn't build a TCP/IP stream with header and stuff, the OS TCP/IP stack deals with that stuff.
    For testing the quality of such network there are special hardware (most PXI) and software solutions.
    What is it that you want to achieve?
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

Maybe you are looking for