I am working on stm32f769 project, running freeRTOS task, with stm32cubeIDE(1.7.0) debugger and freeRTOS NXP viewer.I would like do get backtrace and call stack of a fault happened in a freeRTOS task, without costly tools. I tried the MCU registers ...
Hi all, I am working on stm32f769 project, running freeRTOS task, with stm32cubeIDE(1.7.0) debugger.The debugger does not hit hard faults inside the faulty task , but later, reporting scheduler restart in debug calling stack. That way I completely...
Posted on April 23, 2014 at 15:33hi all, I'm new in the forum and I am experiencing a problem of ISR , which doesn't happen for TIM12 while, with same ch1 configuration register and same pwm signal input, set the ISR calling for TIM9, as expecte...
Hi TDK,I Have voluntarily driven the error just for debug purpose, because in past development activity I fall into a 'real' unlocated hard fault which takes me many hours to catch. This time I 'd like just to found the necessary debugging i...
Hi all,after some test I found NO scheduler restarting, as I supposed at first. The call stack simply remains freezed on freeRTOS scheduler first start, maybe because task activity is performed on private freeRTOS stack and no more 'traced' by G...
Posted on May 19, 2014 at 09:24Hi all, after some code refactor and keeping the measure context separated , I succeed in measuring 2 channel PWM input with TIM9 peripheral. I don't exclude also some bug in the reconfiguration code.I have applyed ...
Posted on May 13, 2014 at 12:03Hi, Because I found measurement issues when I switch the input peripheral, whereas I can get stable and correct ( uninfluenced by unused TIM input ) measurement when I do only startup configuration, after device rest...
Posted on May 10, 2014 at 09:55Hi, I made some further test on switching the input channel, (using TIM1 to trig the switching time). I could measure the two PWM channel, but, when I supply both inputs I was only able to get only one correct chan...
