@Filip
This would be great.
Search found 14 matches
- 06 Nov 2014 14:09
- Forum: mikroC PRO for ARM General
- Topic: Interrupt priority setting
- Replies: 5
- Views: 2972
- 28 Oct 2014 08:45
- Forum: mikroC PRO for ARM General
- Topic: Interrupt priority setting
- Replies: 5
- Views: 2972
Interrupt priority setting
Hi, I have one question, does anyone know how to set up the priority level for different interrupt routines on STM F1x -STM F4x (MikroC arm)? For example, I am enabled interrupts on timer 2, timer 4 and Rx receive. How can I know which one is on the priority 0,1, or in which sub- group they belong e...
- 09 Jun 2014 14:22
- Forum: mikroC PRO for ARM General
- Topic: How to read quad encoder interface!
- Replies: 7
- Views: 4416
Re: How to read quad encoder interface!
Example for F405 and F407 //**************** PORT PC6 and PC7 ********************************************** GPIOCEN_bit=1; // Enable clock on port C // Alternate function enable on GPIO PC6 and PC7 GPIOC_MODER|=0x0000A000; //Alternate function '10' //Connect timer 3 to the port PC6 and PC7 GPIOC_AF...
- 04 Jun 2014 18:11
- Forum: mikroC PRO for ARM General
- Topic: How to read quad encoder interface!
- Replies: 7
- Views: 4416
Re: How to read quad encoder interface!
Hi, There is many ways to do this. I know for ARM M4 F4XXX Try this code for mod x2. Make change in register TIM4_SMCR TIM4_SMCRbits.SMS void QEI_TIM4_Init() { RCC_APB1ENR.TIM4EN = 1; TIM4_CCMR1_Inputbits.CC1S = 1 ; TIM4_CCMR1_Inputbits.CC2S = 1 ; TIM4_CCER.CC1P = 0 ; TIM4_CCER.CC2P = 0 ; TIM4_SMCRb...
- 04 Jun 2014 07:19
- Forum: mikroC PRO for ARM General
- Topic: 2x Encoders initialization problem on DiscoveryF4
- Replies: 0
- Views: 1212
2x Encoders initialization problem on DiscoveryF4
Can someone help me please I don’t find a mistake in my code. I try to use two separate encoder units for two motors but encoder with timer 3 work fine but second one with timer 4 do not work (i also use example from LIBSTOCK and do not work - Pascal project) I have also a question how I know which ...
- 04 Jun 2014 07:19
- Forum: mikroC PRO for ARM General
- Topic: 2x Encoders initialization problem on DiscoveryF4
- Replies: 0
- Views: 1280
2x Encoders initialization problem on DiscoveryF4
Can someone help me please I don’t find a mistake in my code. I try to use two separate encoder units for two motors but encoder with timer 3 work fine but second one with timer 4 do not work (i also use example from LIBSTOCK and do not work - Pascal project) I have also a question how I know which ...
- 29 Oct 2013 12:30
- Forum: mikroC PRO for ARM General
- Topic: Mikromedia STM32 CDC Example Application
- Replies: 21
- Views: 13642
Re: Mikromedia STM32 CDC Example Application
Yes, you have right it's simpler.
- 29 Oct 2013 10:36
- Forum: Libstock Discussion
- Topic: CDC Class added to USB Device Library!
- Replies: 71
- Views: 607057
Re: CDC Class added to USB Device Library!
I solved a problem with new settings of PLLx for 8MHz Xtal ,
i use PLLN=420, PLLM=10, PLLP=2, PLLQ=7, Frequency = 168MHz.
i use PLLN=420, PLLM=10, PLLP=2, PLLQ=7, Frequency = 168MHz.
- 29 Oct 2013 10:20
- Forum: mikroC PRO for ARM General
- Topic: Mikromedia STM32 CDC Example Application
- Replies: 21
- Views: 13642
Re: Mikromedia STM32 CDC Example Application
Thanks Toley, i change frequency settings accordingly to the above formula for the 8MHz Xtal, and it works fine.
I use PLLN=420, PLLM=10, PLLP=2, PLLQ=7, Frequency = 168MHz.
I tested both ME and STe VCP drivers for win7,and both are working well.
I use PLLN=420, PLLM=10, PLLP=2, PLLQ=7, Frequency = 168MHz.
I tested both ME and STe VCP drivers for win7,and both are working well.
- 28 Oct 2013 20:53
- Forum: Libstock Discussion
- Topic: CDC Class added to USB Device Library!
- Replies: 71
- Views: 607057
Re: CDC Class added to USB Device Library!
Thanx Milos for the suggestion, but still no success, still appear -unknown device. If i select wrong settings of
frequency , PLL etc..the device stay unrecognizable. I think it's problem in WIN7- VPC drivers.
frequency , PLL etc..the device stay unrecognizable. I think it's problem in WIN7- VPC drivers.
- 28 Oct 2013 14:35
- Forum: mikroC PRO for ARM General
- Topic: Mikromedia STM32 CDC Example Application
- Replies: 21
- Views: 13642
Re: Mikromedia STM32 CDC Example Application
Toley thanks, but the same result, USB device is still unknown.
I think, i have a problem with the VCP drivers for WIN7x64 (VCPDriver.inf). The drivers cannot be installed (Win7 message: The drivers are not suitable for connected device ).
I think, i have a problem with the VCP drivers for WIN7x64 (VCPDriver.inf). The drivers cannot be installed (Win7 message: The drivers are not suitable for connected device ).
- 28 Oct 2013 09:21
- Forum: mikroC PRO for ARM General
- Topic: Mikromedia STM32 CDC Example Application
- Replies: 21
- Views: 13642
Re: Mikromedia STM32 CDC Example Application
Hi there, I have also a small problem in MikroC Arm compiler. I try to run a VCP example on board F4Discovery with STM32F407VG mcu. For a starting point I used a project which can be founded in examples from USB library 1.1.0.0 and was dedicated for STM32F107VC. I simple load the scheme ‘STM32F407VG...
- 25 Oct 2013 13:10
- Forum: Libstock Discussion
- Topic: CDC Class added to USB Device Library!
- Replies: 71
- Views: 607057
Re: CDC Class added to USB Device Library!
Hi there, I have a small problem in MikroC Arm compiler. I try to run a VCP example on board F4Discovery with STM32F407VG mcu. For a starting point I used a project which can be founded in examples from USB library 1.1.0.0 and was dedicated for STM32F107VC. I simple load the scheme ‘STM32F407VG_PLL_...
- 25 Oct 2013 11:27
- Forum: Libstock Discussion
- Topic: CDC Class added to USB Device Library!
- Replies: 71
- Views: 607057
Re: CDC Class added to USB Device Library!
Hi, I use F4Discovery board and try to run example (MikroC ARM)for VCP with loaded scheme ‘STM32F407VG_PLL_25_to_120MHz_USB’ but doesn’t work. Project is compiled fine, but when F4-board is in running mode, than Win7-x64 doesn’t recognized the USB device? I also try to install attached drivers from ...