Programming STM32F103C8 over USART with UM0462 program

[y11leongyusiang]

Posted on January 01, 2014 at 14:22

Hi all,

I am a student who wishes to start off in ARM uCs with a small budget.I would like to know whether the STSW-MCU005 is supposed to be used with the AN2606 USART1 bootloader, so that i can use a USB-Serial device to program the STM32F103C8?The development board is 

http://www.ebay.com/itm/390712526711

, which breaks out the BOOT0 pin and Tx/Rx pins.Thanks for the clarification.

[Tesla DeLorean]

Posted on January 01, 2014 at 16:34

While the Flash Demonstrator is the right for USART connectivity, your cited board does not have a readily accessible USART, not one at RS232 levels at least.

You do have a USB port, you'd want to use DFU mode

http://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/CD00264379.pdf

STSW-STM32080

DfuSe USB device firmware upgrade STMicroelectronics extension: contains the demo GUI, debugging GUI, all sources files and the protocol layer (UM0412)

http://www.st.com/web/en/catalog/tools/PF257916

[Andrew Neil]

Posted on January 01, 2014 at 16:53

For the price of that board (or very little more), can't you get a Discovery board?

Certainly, by the time you've added a debug (''JTAG'') probe, the Discovery option would work out cheaper.Developing without a debug probe is just making your life unnecessarily difficult!The Discovery board gives you a proper debug probe & programming adaptor built in;  so no need to mess with bootloaders - which is not really a beginner's  task anyhow!

[y11leongyusiang]

Posted on January 02, 2014 at 14:01

Ahh! I thought that ST didn't have a low cost eval board. However i just saw the ARM mbed platform, and i think i'll go with one of those instead, if anything for the online compiler (i much prefer to use linux). ST seems to be un(der)represented there, though...

Thanks anyway.

[Tesla DeLorean]

Posted on January 02, 2014 at 14:45

http://www.mouser.com/Search/Refine.aspx?Keyword=stm32+discovery

Problem with Linux is there is no money in it, there are dozens of distributions, and if I picked one to support people would complain that wasn't the one they wanted. Supporting and creating tools is a money sucking exercise, and so the target market is generally the business/professional one. In a model where you only consume and don't contribute, the choices will be what they are. If I had a Mac I could run OSX, Linux and Windows on it, any cheap PC I could buy would have Windows on it and Virtual Box + Linux could be added freely. Stop being trapped by the ''platform'' being used.

[okelly]

Posted on January 16, 2015 at 03:29

Hello all,

I am tasked with implementing DFU on STM32F103, so I thought I would jump on this thread. I like clive1's suggestion to use STSW-STM32080. Should I be concerned that STM32F103 appears to be explicitly not mentioned in the documents?

http://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/CD00264379.pdf

Table 1. Applicable products [ ... ] STM32F1 series: – STM32F105xx, STM32F107xx [ ... ] Changelog of that doc shows Table 1 was updated 30-Apr-2014. Hmmm... ...and I just noticed this thread is a year old, not a week old 🙂 Regards, Owen

[okelly]

Posted on January 19, 2015 at 19:52

I found the answer:

AN2606 describes which chips have which internal bootloader software.STM32F103 chips have USART (V2.2) bootloader.F2 chips (Rev X or Y) and F4 chips have USART (V3.1) and DFU (V2.2).So although you could write DFU device class on an STM32F103 chip, there would be no support within the chip to move the data from USB peripheral into code flash; that is the job of the DFU bootloader which is absent on that chip. On to the next design.