Hi, On Sun, Feb 1, 2015 at 5:05 PM, Jason White wrote: > I have a STM32F4Discovery development board and have been getting > comfortable enough with ARM processors to start considering a serious > project. In preparation for that, I recently ordered a bunch of ST > micros and a ST-Link programmer. > > My development board works great. However, I built two hand-wired > prototypes with the 20 and 32 pin version of the STM32F030 and I found > I was unable to program them. I read ST's "getting started" > application note [1] could not find anything with my prototypes that > would cause an issue. > I have a cheap st-link v2 clone, and a bunch of stm32f030f4p6 micros. I use st-util software from https://github.com/texane/stlink I connected pins: - 1 (boot0), directly to ground, - 4 (NRST) to st-link NRST output - 5 (VDDA) to st-link 3.3V -15 (VSS) to st-link GND - 16 (VDD) to st-link 3.3V - 17 (bootloader TX) by 10k to st-link 3.3V - 18 (bootloader RX) by 10k to st-link 3.3V - 19 (SWDIO) to st-link SWDIO - 20 (SWCLK) to st-link SWCLK When loading st-util, the micro is detected and using GDB I can examine the registers and flash firmware. The two 10k resistors to 3.3V are there because previously I tried loading firmware via the rom bootloader, using the https://code.google.com/p/stm32flash/ software, a cheap USB to 3.3V 232 and holding pin 1 to 3.3V. It worked, but it was much more complicated than simply using the st-link. > > Does anyone have any ideas as to what might be wrong? No, I hope my simplified connections work with your devices. > Other miscellaneous notes: > * It seems when the device boots, the reset pin NRST (which is also an > IO) goes low. I'm not sure if that is normal. Yes, this is normal, the NRST pin is held low by at least 20us whenever the micro reset itself. > * The open source utility reports the chip id as bouncing in between > 0xe0042000 when disconnected and 0x20002e60 (0x2000 -> revision 2, > then the rest is garbage) when all of the connections are right. It > reports the same value for multiple types of chips and for both > programmers. I think that this is wrong, should be 0x20006444. Daniel. --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .