Migrated from STM32C011J6M6 (SO8) to STM32C091FCP6 (TSSOP20), stlink device not finding MCU at power up
Having problem getting STM32C091FCP6 that is new (not otherwise programmed) to respond to STLINK device at power on.
Details-
Preparing to move a project from STM32C011J6M6 to STM32C091FCP6 to obtain larger pin count and larger memory capacity. On first attempt to attach STLINK V2 device to the target containing a new STM32C091FCP6 (SWDIO, SWCLK and GND to a device on 3.3V power), STLINK not starting as expected (power is being applied before STM32CubeProgrammer is commanded to “Connect.”
To rule out PCB layout error on the (new) STM32CX091FCP6-based version of project, I attached another (also new from supplier) MCU to STLINK V2 device attaching only SWDIO, SWCLK and GND to STLINK, applied 3.3V power (all other pins open), and again STLINK not handling “Connect” command as expected. STM32CubeProgrammer is reporting “unable to get core ID” and/or “DFU_TARGET_CMD_ERR.
The development environment (STM32CubeProgrammer) and STLINK device firmware are up-to-date.
The STM32C091FCP6 devices are from batches supplied by US distributor (as are STM32C011J6M6 devices being tested), so they are presumably in factory default configuration (option bytes/bits that would affect power-on behavior).
I can find on other culprit.
Asking here if there’s something I’m missing about power-on behavior or sequencing of the STM32C091FCP6 (expect that STLINK MCU pins are active at power-on. BOOT0 pin is shared with one of these two pins so I’m not sure if there is any other way to influence power-on behavior for a device in as-delivered/factory default configuration.
Thanks for any pointers/advice, and happy to provide any clarifying information requested.
