System Bootloader for STM32F107xx

[ramadevi]

Posted on February 04, 2010 at 11:15

System Bootloader for STM32F107xx

#dfuse-v3.0.0 #stm32 #stm32-usb-flash-update #bootloader

[aleksey]

Posted on May 17, 2011 at 13:38

I have a similar [DEAD LINK /public/STe2ecommunities/mcu/Lists/ARM%20CortexM3%20STM32/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/ARM CortexM3 STM32/STM32F10x connection via USART problem&FolderCTID=0x01200200770978C69A1141439FE559EB459D758000626BE2B829C32145B9EB5739142DC17E]problem. I tried to use my eval board(STM32F107) in DFU mode and write internal flash with DFuSe. Connected board to PC via USB. And PC viewed unknown device with PID=0000&VID=0000! But need VID=0483 & PID=DF11 as in STDFU.inf.

May be board have a bad bootloader and problem with USART connection associated with this?

Excuse me for my English.

[Tomas DRESLER]

Posted on May 17, 2011 at 13:38

The date code 961 tells that this chip comes from very first batch and the bootloader is not present. Contact your ST marketing for replacement.

[Tomas DRESLER]

Posted on May 17, 2011 at 13:38

Check whether you've downloaded the DFU for proper family. Next, does your board implement the USB D+ disconnect? I remember on some boards the disconnect had a jumper, that permanently shortcutted the transistor and the USB host recognized the device instantly & too early before DFU code booted.

[tkjmail2]

Posted on May 17, 2011 at 13:38

If the issue isn't that there is no bootloader in the chip, then I've found out that I had to lower the connection speed to 57600 bps, as it gave me connection errors most of the time when I was using 115200 bps!

[Tomas DRESLER]

Posted on May 17, 2011 at 13:38

Nope, date codes before 937 (year [20x]9, week 37) have no bootloader. Ask your ST marketing for replacement. Btw. 961 is obviously not a valid week in any year, it's a pilot version.

[aleksey]

Posted on May 17, 2011 at 13:38

Chip on my board marked as STM32F107VCT6 Z 99056 VC MYS99 923. Does bootlader present in this version?

USB D+ connected. The board work correctly with my firmwares which use HID and CCID protocol. I have a problem when board booting from system memory only. USART connection don't work too.

[ramadevi]

Posted on May 17, 2011 at 13:38

Hi,

Thanks for the replies.It took sometime to get another board and now I have STm32 board with 923 marking. But I am able to use flash loader demo and write the kernel bootloader to the flash.

When I connect the board to PC through a USB, it is not detected.'Found new hardware' is not working and 'Add new hardware' feature not lists the STM board.

My settings:Boot mode in User flash and JP14 in connected mode.

Any help is much appreciated.

Thanks a lot.

[aleksey]

Posted on May 17, 2011 at 13:38

Edison, thanks for your answers.

I dumped memory 0x1fffb000-0x1ffff7ff (system memory area). It's contains some code. In this code VID (0x0483) have offset 0x1fffeae8 and PID (0xdf11) have offset 0x1fffeaea.

Conclusion: chip have bootloader, but it don't work!

[ramadevi]

Posted on May 17, 2011 at 13:38

Is there a way to flash the board using ST-Link JTAG and KEIL/IAR IDE? How can we make use of this board?

I am little confused about the usage?

[aleksey]

Posted on May 17, 2011 at 13:38

Hi,

STM support replied to me about this problem.

STM

32

F

107

VCT

6 with data code before 941 have a bootloader's problem with USB and USART connections.