stm32

问题 I have two ARM Cortex-M3 chips: STMF103C8T6 and STM32F103VET6 . When set to boot from RAM, initial state of STMF103C8T6 PC register is 0x20000108 ; 0x200001e0 for STM32F103VET6 . I am unable to find and information about these addresses in the datasheets. Why are they booted this way and where I can find some information about it? Edit: To clarify. When chip set to boot from flash, PC register points to the location of the Reset Handler. This address is provided in the reset vector table at

问题 I want to log out from stm32f405 via usart. In my syscall.c file i realize function to print via usart: int _write(int file, char *ptr, int len) { int todo; for (todo = 0; todo < len; todo++) { usart_send_char( *ptr++ ); } return len; } Function usart_send_char( *ptr++ ); work as expected. But when i call: printf("%s, %d, %3.2f\r\n", "asd", 777, 13.2 ); I get: asd, 777, 0.00 The float variable not printed correctly. Makefile: PROCESSOR = -mcpu=cortex-m4 -mthumb -mfloat-abi=softfp -mfpu=fpv4

问题 I want to log out from stm32f405 via usart. In my syscall.c file i realize function to print via usart: int _write(int file, char *ptr, int len) { int todo; for (todo = 0; todo < len; todo++) { usart_send_char( *ptr++ ); } return len; } Function usart_send_char( *ptr++ ); work as expected. But when i call: printf("%s, %d, %3.2f\r\n", "asd", 777, 13.2 ); I get: asd, 777, 0.00 The float variable not printed correctly. Makefile: PROCESSOR = -mcpu=cortex-m4 -mthumb -mfloat-abi=softfp -mfpu=fpv4

问题 I want to log out from stm32f405 via usart. In my syscall.c file i realize function to print via usart: int _write(int file, char *ptr, int len) { int todo; for (todo = 0; todo < len; todo++) { usart_send_char( *ptr++ ); } return len; } Function usart_send_char( *ptr++ ); work as expected. But when i call: printf("%s, %d, %3.2f\r\n", "asd", 777, 13.2 ); I get: asd, 777, 0.00 The float variable not printed correctly. Makefile: PROCESSOR = -mcpu=cortex-m4 -mthumb -mfloat-abi=softfp -mfpu=fpv4

问题 I have a ChibiOS 3.x program on a STM32F4 microcontroller where I use the IWDG watchdog to reset the MCU on errors like this: int main() { iwdgInit(); iwdgStart(&IWDGD, &wd_cfg); while(true) { // ... do stuff } } If I now attach my debugger and, at any point, stop the program (manually or via a breakpoint), the microcontroller will reset after the timeout defined by the watchdog configuration (and therefore cause issues in my debugging process) How can I disable this behaviour, i.e. how can I

问题 I have a ChibiOS 3.x program on a STM32F4 microcontroller where I use the IWDG watchdog to reset the MCU on errors like this: int main() { iwdgInit(); iwdgStart(&IWDGD, &wd_cfg); while(true) { // ... do stuff } } If I now attach my debugger and, at any point, stop the program (manually or via a breakpoint), the microcontroller will reset after the timeout defined by the watchdog configuration (and therefore cause issues in my debugging process) How can I disable this behaviour, i.e. how can I

问题 I have a ChibiOS 3.x program on a STM32F4 microcontroller where I use the IWDG watchdog to reset the MCU on errors like this: int main() { iwdgInit(); iwdgStart(&IWDGD, &wd_cfg); while(true) { // ... do stuff } } If I now attach my debugger and, at any point, stop the program (manually or via a breakpoint), the microcontroller will reset after the timeout defined by the watchdog configuration (and therefore cause issues in my debugging process) How can I disable this behaviour, i.e. how can I

来源： https://stackoverflow.com/questions/45964607/quadrature-signal-generation-with-bit-manipulation

来源： https://stackoverflow.com/questions/45964607/quadrature-signal-generation-with-bit-manipulation

来源： https://stackoverflow.com/questions/42225069/method-execution-from-another-object-in-c