2010-10-11 08:28 AM
Unable to download and debug flash
2011-05-17 05:10 AM
You sure it's using 5.50? ''Embedded Workbench 5.4_2''
I haven't bothered with IAR/EWARM, but the Keil 4.12 demo is working with the discovery board.2011-05-17 05:10 AM
I don't know why but in uVision 4 i get this message in build output
Build target 'DISCOVER' compiling system_stm32f10x.c... compiling core_cm3.c... assembling startup_stm32f10x_md_vl.s... compiling stm32f10x_pwr.c... compiling stm32f10x_rcc.c... compiling misc.c... compiling stm32f10x_exti.c... compiling stm32f10x_gpio.c... compiling STM32vldiscovery.c... compiling stm32f10x_it.c... compiling main.c... linking... Program Size: Code=1628 RO-data=348 RW-data=52 ZI-data=1028 ''.\Debug\DISCOVER.axf'' - 0 Error(s), 0 Warning(s). Load ''D:\\Project\\Project\\Demo\\MDK-ARM\\Debug\\DISCOVER.AXF'' Load ''D:\\Project\\Project\\Demo\\MDK-ARM\\Debug\\DISCOVER.AXF'' but it does't flash the MCU do you know why?2011-05-17 05:10 AM
Hi,
This is a known bug in EWARM 5.50 with value line flashloader. It is fixed in EWARM5.50.5.
I advise you, if possible, to upgrade your EWARM version to 5.50.5 (available on IAR web site: www.iar.com).
Else , you can use the attached patch to fix this problem with your installed version. It contains a readme that explains hosw to use it.
Hope this helps,
regards, VLINE.
2011-05-17 05:10 AM
I don't know why but in uVision 4 i get this message in build output
Build target 'DISCOVER'
compiling system_stm32f10x.c...
compiling core_cm3.c...
assembling startup_stm32f10x_md_vl.s...
compiling stm32f10x_pwr.c...
compiling stm32f10x_rcc.c...
compiling misc.c...
compiling stm32f10x_exti.c...
compiling stm32f10x_gpio.c...
compiling STM32vldiscovery.c...
compiling stm32f10x_it.c...
compiling main.c...
linking...
Program Size: Code=1628 RO-data=348 RW-data=52 ZI-data=1028
''.\Debug\DISCOVER.axf'' - 0 Error(s), 0 Warning(s).
Load ''D:\\Project\\Project\\Demo\\MDK-ARM\\Debug\\DISCOVER.AXF''
Load ''D:\\Project\\Project\\Demo\\MDK-ARM\\Debug\\DISCOVER.AXF''
but it does't flash the MCU do you know why? LOAD means it sent it to the device. There is a problem with the ST-LINK using the Flash->Download menu, but if you select Debug->Start/Stop and you have enabled ''Update Target before Debugging'' option, it will flash the device before it starts debugging. If you want to write a specific .HEX file to the device, you can download and use the ST-LINK Utility program outside of Keil.
2011-05-17 05:11 AM
Hello,
Having the same problem flash loader. If possible let me have the patch in .zip format. I dont have rar in my machines. Also I couldnot find the exact place where I can download EWARM version to 5.50.5. Is it freely available? Now I am using IAR Enbedded workbench 5.4 kickstart. Thank you.2011-05-17 05:11 AM
Hello VLINE,
Is such patch file is available for STM32L1XX versions? Thanks.2011-05-17 05:11 AM
I have a similar problem, Using Embedded Workbench 6.0 Evaluation Edition:
Thu Feb 10 12:12:33 2011: C:\Program Files\IAR Systems\Embedded Workbench 6.0 Evaluation\arm\config\flashloader\ST\FlashSTM32F10xxx.mac(5,20): Error: Operation error.
Thu Feb 10 12:12:33 2011: Error while calling macro execUserFlashInit
Thu Feb 10 12:12:33 2011: Failed to load flash loader: C:\Program Files\IAR Systems\Embedded Workbench 6.0 Evaluation\arm\config\flashloader\ST\FlashSTM32F100xB.flash
This occurs when using the STM32Discovery SWD ports to flash an external STM32F103VB. I wonder if the wires are a problem, as I have a relatively long squid (>20cm). However STM's ST-Link Utility has absolutely no problem flashing the chip and verifying, so this would seem to indicate a problem with EW.Any ideas?
2011-05-17 05:11 AM
C:\Program Files\IAR Systems\Embedded Workbench 6.0 Evaluation\arm\config\flashloader\ST\FlashSTM32F100xB.flash
Any ideas? Perhaps you have not selected the correct target device for the project? ie an F103, not the F100