labview for stm32f103 development board?

[mat2_chan2]

hi,

good afternoon. it's been a while since i visited this thread. i was wondering if anybody can help me create the target folder for our STM32F103RB board. i'm currently stuck in the Programming Additional ARM Microcontrollers (without SDK) with LABVIEW part of the turorial. we copied the LPC2378 folder in the Generic folder and renamed it as STM32F103RB. we don't know what the necessary #defines, paths and libraries are, and we don't know how to update the files in the folder.

we need to fix the target folder before we can use our ULINK JTAG adapter to our board. can anybody please help us?

thank you very much for your cooperation. 

[DiscoBall]

Howdy,

It looks like you are in the same position as aeolia was a little while ago. Can you please tell me what version of the Porting Guide you are using (link please). I believe message 7 of this forum answers your questions. Do this help?

[mat2_chan2]

hi,

i'm currently following the instructions in this link http://zone.ni.com/devzone/cda/tut/p/id/7152 i downloaded all the files in the firmware section from http://www.st.com/mcu/devicedocs-STM32F103RB-110.html but i'm confused if i'm supposed to copy every single header file into the template\include folder. i also don't know how i'm going to integrate the standard peripheral library folder into the  template\drivers folder.

i'm not used to modifying files so i'm afraid i might accidentally delete some crucial parts of the target folder. i would appreciate any help with this problem.

thanks 

[mat2_chan2]

hi, regarding my problem earlier with the target folder, is there anybody who can accept my target folder and fix it? i really need help with the interfacing because we are also using labview to program our STM32F103RB development board. our thesis basically needs to use labview to drive motors based from input sensors. we also bought a ULINK JTAG adapter because we thought it would help us with the interfacing.

thanks, 

mat2_chan2 

[DiscoBall]

Hi,

Here is how I would modify the default TargetConfig.ini...

[INCLUDE_PATH]
add the path to the folder that contains the .h files for folder that you download from STM (usually inc folder)

[INCLUDES]
add the names of the files that you are needing, if you need the ADC then it is probably prudent to add the stm32f10x_adc.h in this list, etc.

[FILE]
this are the links to C files that are use, usually found in the src folder (for example stm32f10x_adc.c)

Don't be afraid to try and make some mistakes, if you can always start again, you shouldn't be able to make irreversible damage

[mat2_chan2]

Hi DiscoBall,

thanks for helping me modify the TargetConfig.ini file. when i run the labview program, i can now select the STM32F103RB folder.

how do i test if the target folder's working properly to interface with our board?

thank you very much.

[DiscoBall]

Are you unable to make a simple VI and attempt a deployment? Do you not have the hardware yet?

[mat2_chan2]

we're working on it. we're currently stumped how to assign the gpio ports of the board using labview. we are new to the labview environment and we do not know how to program our C-Language algorithms with it. we tried following the basic tutorial in programming but didn't help us much in porting our board. we are open to suggestions to help us interface the labview program and our board. thanks.

[DiscoBall]

Hi,

If you are dealing with GPIO, you will need to use the GPIO wizard and will need to have some C code that you can call into. What exact issues are you having with the GPIO, are you encounter errors? Can you be more specific? What is the goal of your application? What are you needing to accomplish with the STM and LabVIEW?

[OllieHaselden]

Hi,

Did you ever manage to port this processor into LV, I have the same problem and was hoping someone could guide me. I have tried following the porting guide but get totally confused with the where to Obtain certain files... Please Help!!

Thanks