labview for stm32f103 development board?

[ARM keiller]

Thanks for your answer

I saw that my program stopped on a breakpoint due to "semihosting_swi" so I modified my "retarget.c" file. And my program ran !!!

Now I'm trying to include the library of STM32_functions supplied by keil's libraries with LabVIEW. In order to use this function to 

configure my GPIO... But I don't succed !!! Because Inline C nodes are not enough powerful to make this.

And when I open uVision in debug mode I notice that my HCLK run at 8Mhz and not 72Mhz.... Is it normal ? I thought that RTX configure

automatically the clock at 72 Mhz ...???

Thanks for your answer.

[ARM keiller]

Hi aeolia

Why do you need to port LabVIEW on a STM32F103 ? Can you specify your application ?

Give me your email address and I will be able to give you my folder.rar .

I'm trying to configure my GPIO, but I haven't yet succedded. I hope that you will be able to help me later.

Best regards.

[DiscoBall]

Hello and you're welcome,

What do you mean that you did not succeed when trying to include the libraries? Did you get an error? Can you describe the process you are going through in more detail please? Perhaps you can help the community out and post what you have so far so that we all can see?

I am unsure about the clock issue, I will look more into that.

[ARM keiller]

Hello DiscoBall

I succedded to use my lybrary of function because I found how the files.c and .lib can be attached to the project when this latter is building.

I identified my problem : when you create a new ARM project with  EK-LM3S8962 or MCB2300 or MCB2400 and that you right-click on your target on "new" , you can select "Elemental I/O".

But if you create a project with a Philips NXP LPC2378, LPC2468 or with the luminary micro device and that you click on the name of your target in the Project Explorer on "new" you CAN'T create new "Elemental I/O" because there is NOT "Elemental I/O".

I modified my VI to configure my GPIO and I created my ressources and pins with the "Elemental I/O Device Wizard to create the eio.xml.

But I can't do anything because of the "Elemental I/O" doesn't exist.

Please have you an answer for my problem. Thank you.

Best Regards

[DiscoBall]

Hi,

What path do you have your eio.xml file in? Does the eio.xml specify the correct path to the VIs in the file? Did you change the name from "Other" in the project to the correct device?

[aeolia]

Hi ARM keiller 

Our ARM microcontroller will basically control the movement of the motors, gather data from the sensors and sends it to the PC wirelessly via zigbee. We already have the labview codes for all of this. We only just need the STM32F103RB target folder.

  Here's my email address: beniong@yahoo.com 

Thanks 

[随心]

Hi ARM keiller



 I knew how to drive GPIO/ADC/LCD and so on in labview ARM module by inline C CODE.Tell me your Email ,I will give it to you .I also ported STM32 in labview , it seems successed , but if I use inline C code in it ,it can not work.so can you send your STM32F103RB target folder to me ,and I send mine to you .



  Here's my email address: beniong@163.com 



Thanks

[ARM keiller]

Hi !

Thanks for your answer. I succeeded to configure my GPIO. 

I'm trying to modify the C source code which manage the different interrupt. I have an error which causes an Hard Fault interrupt .

How would you do to detect the source of this error ???

When I use µvision I can't go step by step because I'm stopped by this line : while(OCDI_RDMStart != 0x01);

 And I don't succeed to activate thiscondition from LabVIEW.

And if I use breakpoint on LabVIEW code I have an unknown exception....

If you have a great idea about this thanks to share it with me.

best regards 

[DiscoBall]

Hi Arm keller,

Can you post screenshots of your error and post your code. What did you modify?

[ARM keiller]

For everybody who want to port LabVIEW on a CORTEX M3 and use an interrupt . Please read this :

RTX Library version for Cortex™-M devices allows to select the running mode of all user tasks. User tasks may run in two modes:

• Unprivileged - Protected mode or
• Privileged - Unprotected mode.

In privileged mode user may access and configure the system and control registers like NVIC interrupt controller etc. This is however not allowed from unprivileged mode. An access to NVIC registers from unprivileged mode will result in Hard Fault.

 #define OS_RUNPRIV 1

• OS_RUNPRIV enables running of all tasks in Privileged mode. It must be set to 1 to enable it or 0 to disable it. It is disabled by default.

  You can enable the privileged mode for old projects. The existing code will run without any modifications when RTX_Config.c configuration file is replaced with a new one and a project is recompiled for a new Cortex™-M RTX Kernel library. Tasks are not protected in privileged mode and you may configure the system for example the interrupts from any task.

  Privileged mode is disabled by default. This allows all tasks to run in protected mode. The tasks are not allowed to change system settings, change interrupts etc.