2018-12-05 07:01 AM
After upload my program into a stm32F103C8T6, the program doesn't start. I just use STM32CUBE-MX to configure my mcu, and I just add some blinking on 5 output (push/pull). But after reset my output seems to stay in high inpedance ? Does Mcu start itself ? Do I miss a configuration step in STM32CUBE-MX ?
regards
2018-12-05 08:22 AM
CubeMX is not a compiler, you need to build the project in a tool chain, and download and debug it from there.
2018-12-05 08:48 AM
(I never thought I would actually recommend this)
2018-12-05 08:52 AM
Yes of course, Sorry I didn't mentioned it. I obviously Build project without error, before uploading. I hadn't choice I need .hex file or .bin :)
2018-12-05 09:27 AM
If this is a custom board be wary that BOOT0 needs to be pulled LOW. The chip should run code out of FLASH at reset, and starting a debugger should initiate a "run to main()" to allow you to start your session.
Recommend stepping the code, and reviewing the peripheral settings for RCC, GPIO, etc through debugger's "Peripheral View"
Using PA13/PA14 and other SWD/JTAG pins on F1 can interfere with the ability to debug.
2018-12-05 11:37 PM
There's a beginning to everything, but it's not help ! I already done basic steps, this is the reason why I ask help, to have a higher level of help !
2018-12-05 11:44 PM
My (other) problem is I reuse a board and debug pins are not welded ! I just added 4 pins to upload with st-link. I haven't quartz on board so I need to use internal clock, Is there something special to start it ?
2018-12-06 06:13 AM
The part starts running from the 8 MHz HSI, if you do nothing it will continue with that clock.
If you want the part to run at 64 MHz you'd need to configure the PLL parameters, picking the HSI as the source, and not attempt to start the HSE which you don't have.