IAR Help error Failed to setup call to 'FlashInit'"

[diyaudio]

Hi Guys.

I'm trying out a stm32f103c8t6 mini dev board with an ST-Link/V2 programmer.
http://www.ebay.com/itm/ARM-Development-Board-Cortex-M3-STM32F103C8T6-STM32-Module-8Mhz-USB-JTAG-ISP-USA-/161213419355

I'm having trouble using IAR 6.5 when debugging. I get this error "Failed to setup call to 'FlashInit' " when the use flash loader is checked.

Fri Aug 22, 2014 13:41:47: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 6.5\arm\config\flashloader\ST\FlashSTM32F10xxx.mac
Fri Aug 22, 2014 13:41:47: Selecting SWD as current target interface.
Fri Aug 22, 2014 13:41:47: Hardware reset with strategy 0 was performed
Fri Aug 22, 2014 13:41:47: Initial reset was performed
Fri Aug 22, 2014 13:41:47: -I- execUserFlashInit!
Fri Aug 22, 2014 13:41:47: 456 bytes downloaded (5.71 Kbytes/sec)
Fri Aug 22, 2014 13:41:47: Loaded debugee: C:\Program Files (x86)\IAR Systems\Embedded Workbench 6.5\arm\config\flashloader\ST\FlashSTM32F10xxxRAM32K.out
Fri Aug 22, 2014 13:41:47: Target reset
Fri Aug 22, 2014 13:41:47: Flash loader: Failed to setup call to 'FlashInit'"


Can some point me in the right direction please.

[zarta]

i think you must change the settings in below picture.



start with debug interface. switch it to JTAG from SWD.
and try other reset options like connect during reset.

these changes worked for me before.

[dannyf]

The usual stuff: check the wiring, power supply, boot setup, etc. Start with the ones that you are sure to be correct and work your way down.

[diyaudio]

i think you must change the settings in below picture.



start with debug interface. switch it to JTAG from SWD.
and try other reset options like connect during reset.

these changes worked for me before.

I resolved this problem some time ago, as im new to the STM / IAR world, I used the recommended approach by using the IAR templates and slowly breaking up the project into logical fragments I now have a fully working project using the templates and another one built from scratch as a learning exercise, that error has since vanished.


 

[dannyf]

I use templates too. I would have one for each chip family, loaded with most of the middlewares that I need. To create a new project, I just need to copy the whole template and rename it and I am in business.

Setting up a fresh project in Keil / MDK can be fairly repeatitive -> that's where CoIDE is nice. Keil5 is taking a similar approach as well.

The downside is disk size - my templates range from 30MB/project to 70MB/project, . And the initial compilation takes some time too.