Search found 8 matches
- Tue Oct 06, 2020 7:18 am
- Forum: General discussion
- Topic: Change clock, from external 72MHz to internal 48MHz
- Replies: 2
- Views: 5989
- Mon Oct 05, 2020 11:43 am
- Forum: General discussion
- Topic: Change clock, from external 72MHz to internal 48MHz
- Replies: 2
- Views: 5989
Change clock, from external 72MHz to internal 48MHz
Hello,
I want to use an STM32F103 without external oscillators. My experiments are on a Bluepill and I am trying to change the clock from external clock 72MHz to internal clock 48MHz. I know which registers i have to change, but i don't think that it is so easy. I can't make it to work.
What is ...
I want to use an STM32F103 without external oscillators. My experiments are on a Bluepill and I am trying to change the clock from external clock 72MHz to internal clock 48MHz. I know which registers i have to change, but i don't think that it is so easy. I can't make it to work.
What is ...
- Tue Apr 28, 2020 10:31 pm
- Forum: General discussion
- Topic: Migration to STM32 Cores. Changes in Interrupts.
- Replies: 13
- Views: 16060
Re: Migration to STM32 Cores. Changes in Interrupts.
Thank you for your answers.
I used "extern "C" void TIM1_UP_TIM10_IRQHandler(void)" and my scetch is working fine, with timer1 also.
Why you don't use the CMSIS devide definition of the MCU instead of defining manually each registers?
They are all available without any specific include, simply ...
I used "extern "C" void TIM1_UP_TIM10_IRQHandler(void)" and my scetch is working fine, with timer1 also.
Why you don't use the CMSIS devide definition of the MCU instead of defining manually each registers?
They are all available without any specific include, simply ...
- Mon Apr 27, 2020 9:50 pm
- Forum: General discussion
- Topic: Migration to STM32 Cores. Changes in Interrupts.
- Replies: 13
- Views: 16060
Re: Migration to STM32 Cores. Changes in Interrupts.
What about the same set up for Timer 1 ?
The handler "extern "C" void TIM1_IRQHandler(void)" is not working.
Here is my code:
//Toggling the onboard led on PC13 every 1 sec.
volatile boolean led = 1 ;
#define RCCAPB2ENR_ (*((volatile uint32_t *) (0x40021000+0x18)))
#define GPIOLC (*((volatile ...
The handler "extern "C" void TIM1_IRQHandler(void)" is not working.
Here is my code:
//Toggling the onboard led on PC13 every 1 sec.
volatile boolean led = 1 ;
#define RCCAPB2ENR_ (*((volatile uint32_t *) (0x40021000+0x18)))
#define GPIOLC (*((volatile ...
- Mon Apr 27, 2020 7:57 pm
- Forum: General discussion
- Topic: Migration to STM32 Cores. Changes in Interrupts.
- Replies: 13
- Views: 16060
Re: Migration to STM32 Cores. Changes in Interrupts.
It works.
Thank you all !!!
Thank you all !!!
- Mon Apr 27, 2020 7:30 pm
- Forum: General discussion
- Topic: Migration to STM32 Cores. Changes in Interrupts.
- Replies: 13
- Views: 16060
Re: Migration to STM32 Cores. Changes in Interrupts.
I did the changes that you suggest me in analog.h file. Now the sketch was uploaded with success but the timer interrupt, still is not working. When it enters in the interrupt it stops responding.
Here is my sketch
//Toggling the onboard led on PC13 every 2 sec.
volatile boolean led = 1 ...
Here is my sketch
//Toggling the onboard led on PC13 every 2 sec.
volatile boolean led = 1 ...
- Sun Apr 26, 2020 3:38 pm
- Forum: General discussion
- Topic: Migration to STM32 Cores. Changes in Interrupts.
- Replies: 13
- Views: 16060
Re: Migration to STM32 Cores. Changes in Interrupts.
Hi, and thank you for your response.
So, I add a new tab called build-opt.h, and i typed inside -HAL_TIM_MODULE_ONLY.
When i compile it, it gives me an error "arm-none-eabi-g++: error: unrecognized command line option '-HAL_TIM_MODULE_ONLY'"
I replaced -HAL_TIM_MODULE_ONLY with -DHAL_TIM_MODULE ...
So, I add a new tab called build-opt.h, and i typed inside -HAL_TIM_MODULE_ONLY.
When i compile it, it gives me an error "arm-none-eabi-g++: error: unrecognized command line option '-HAL_TIM_MODULE_ONLY'"
I replaced -HAL_TIM_MODULE_ONLY with -DHAL_TIM_MODULE ...
- Sat Apr 25, 2020 1:48 pm
- Forum: General discussion
- Topic: Migration to STM32 Cores. Changes in Interrupts.
- Replies: 13
- Views: 16060
Migration to STM32 Cores. Changes in Interrupts.
Recently i add from the board manager the STM32 Cores.
I used to work with low level programming and at this time i don't want to change it.
Using the STM32 Cores the code below is not working. It hang after a while, when it enter in the interrupt. I suppose i have to replace the interrupt vector ...
I used to work with low level programming and at this time i don't want to change it.
Using the STM32 Cores the code below is not working. It hang after a while, when it enter in the interrupt. I suppose i have to replace the interrupt vector ...