Ok Giovanni..
BTW TIM5 16 bit should be ok for system timer.
Have a nice weekend ( it is not an urgent task )
Search found 16 matches
- Thu Jul 02, 2015 2:52 pm
- Forum: STM32 Support
- Topic: STM32F105RBT6 timer resolution for thickless mode
- Replies: 4
- Views: 3683
- Wed Jul 01, 2015 9:19 pm
- Forum: STM32 Support
- Topic: STM32F105RBT6 timer resolution for thickless mode
- Replies: 4
- Views: 3683
Re: STM32F105RBT6 timer resolution for thickless mode
Anyone ?
I depicted something really uncorrect ?
There is a reference in another thread?
I depicted something really uncorrect ?
There is a reference in another thread?
- Tue Jun 30, 2015 5:23 pm
- Forum: STM32 Support
- Topic: STM32F105RBT6 timer resolution for thickless mode
- Replies: 4
- Views: 3683
STM32F105RBT6 timer resolution for thickless mode
Good evening!
Free running mode starts with general purpose Timer 2 as timer for system timing..
st_lld.c reports a section where timer resolution capabilities are checked
#if STM32_ST_USE_TIMER == 2
#if (OSAL_ST_RESOLUTION == 32) && !STM32_TIM2_IS_32BITS
#error "TIM2 is not a 32bits timer ...
Free running mode starts with general purpose Timer 2 as timer for system timing..
st_lld.c reports a section where timer resolution capabilities are checked
#if STM32_ST_USE_TIMER == 2
#if (OSAL_ST_RESOLUTION == 32) && !STM32_TIM2_IS_32BITS
#error "TIM2 is not a 32bits timer ...
- Wed May 27, 2015 10:53 am
- Forum: ChibiOS/HAL
- Topic: stm32_gpio_setup_t pinout porting
- Replies: 0
- Views: 2658
stm32_gpio_setup_t pinout porting
Good morning,
For a while i used to work with old chibios version let's say 2.5 where for pad initialization we have :
typedef struct {
/** Initial value for MODER register.*/
uint32_t moder;
/** Initial value for OTYPER register.*/
uint32_t otyper;
/** Initial value for OSPEEDR ...
For a while i used to work with old chibios version let's say 2.5 where for pad initialization we have :
typedef struct {
/** Initial value for MODER register.*/
uint32_t moder;
/** Initial value for OTYPER register.*/
uint32_t otyper;
/** Initial value for OSPEEDR ...
- Wed Jan 29, 2014 10:52 am
- Forum: General Support
- Topic: C++ class::method() as driver callback
- Replies: 3
- Views: 3948
Re: C++ class::method() as driver callback
About casting , this works :
cfg.callback= (void(*)(GPTDriver*))&Protocol::method;
BUT IT IS USELESS , inside the call back you have no reference to your class members, complier won't complain but you cannot use you class::method or your class variable , for me it was not obvious ...
cfg.callback= (void(*)(GPTDriver*))&Protocol::method;
BUT IT IS USELESS , inside the call back you have no reference to your class members, complier won't complain but you cannot use you class::method or your class variable , for me it was not obvious ...
- Mon Jan 27, 2014 3:24 pm
- Forum: General Support
- Topic: C++ class::method() as driver callback
- Replies: 3
- Views: 3948
C++ class::method() as driver callback
I want to encapsulate for example the uart driver inside a protocol communication class :
class protocol{
UARTDriver *uart_drv;
UARTConfig uart_cfg;
public :
protocol(....){
...
uart_cfg.rxEnd = ( ? cast ? ) protocol::method;
}
private : ...
class protocol{
UARTDriver *uart_drv;
UARTConfig uart_cfg;
public :
protocol(....){
...
uart_cfg.rxEnd = ( ? cast ? ) protocol::method;
}
private : ...
- Thu Mar 14, 2013 3:29 pm
- Forum: General Support
- Topic: Just a simple hint on test suite executed via Shell..
- Replies: 1
- Views: 2164
Just a simple hint on test suite executed via Shell..
I report a case for people that want to execute test suite via shell cmd where program could stop under debug assert failure :
Here a block from thread test suite ..
static void thd1_execute(void) {
threads[0] = chThdCreateStatic(wa[0], WA_SIZE, chThdGetPriority()-5, thread, "E ...
Here a block from thread test suite ..
static void thd1_execute(void) {
threads[0] = chThdCreateStatic(wa[0], WA_SIZE, chThdGetPriority()-5, thread, "E ...
- Tue Feb 26, 2013 10:24 am
- Forum: STM32 Support
- Topic: EXTI same callback for differents pin - VT Instability
- Replies: 6
- Views: 8908
Re: EXTI same callback for differents pin - VT Instability
Hi,
after rigorous tests ...i found a terrific and sneaky disturb reentering unlikely in a time window corresponding to the exti signal operation..chip goes mad..resolved the hw issue..disappeared the sw instability!
Thi is the second post i wrote on this forum and this is the second time that is ...
after rigorous tests ...i found a terrific and sneaky disturb reentering unlikely in a time window corresponding to the exti signal operation..chip goes mad..resolved the hw issue..disappeared the sw instability!
Thi is the second post i wrote on this forum and this is the second time that is ...
- Thu Feb 21, 2013 8:32 pm
- Forum: STM32 Support
- Topic: EXTI same callback for differents pin - VT Instability
- Replies: 6
- Views: 8908
Re: EXTI same callback for differents pin - VT Instability
Hi Giovanni,
no the system is not in halt, port disable or similiar
I got 2 hang situations maybe due to the same issue maybe not :
a) System loop in some VT set ( for example after chThreadSleepMilliseconds() ) in chVTSetI( .. ) in :
while (p->vt_time < time) {
time -= p->vt_time;
p = p->vt ...
no the system is not in halt, port disable or similiar
I got 2 hang situations maybe due to the same issue maybe not :
a) System loop in some VT set ( for example after chThreadSleepMilliseconds() ) in chVTSetI( .. ) in :
while (p->vt_time < time) {
time -= p->vt_time;
p = p->vt ...
- Thu Feb 21, 2013 3:08 pm
- Forum: STM32 Support
- Topic: EXTI same callback for differents pin - VT Instability
- Replies: 6
- Views: 8908
Re: EXTI same callback for differents pin
Well,
-i separated the callback functions with a 1 to 1 relation
-i passed ref to VT directly and not through my encoder struct
RESULT : THE SAME ! -> Is not a cb simultaneous execution problem.
In fact when i comment those VT lines of code my system hang before or later in another virtual timer ...
-i separated the callback functions with a 1 to 1 relation
-i passed ref to VT directly and not through my encoder struct
RESULT : THE SAME ! -> Is not a cb simultaneous execution problem.
In fact when i comment those VT lines of code my system hang before or later in another virtual timer ...