cancel
Showing results for 
Search instead for 
Did you mean: 

bootloader in STM32F105VCT7 rev Z date 038

Fristedt.Jan
Associate II
Posted on August 03, 2011 at 14:45

I can't get in contact with the bootloader neither via USART1 nor CAN2.

I read this thread with great interest:

https://my.st.com/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=%2Fpublic%2FSTe2ecommunities%2Fmcu%2FLists%2Fcortex_mx_stm32%2Fbootloader%20in%20STM32f107&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B&currentviews=1090

I can't find AN2662 mentioned in the thread on ST.COM.

I have read the errata for rev Z, Doc ID 15866 Rev 7 published Feb 2011.

PA10, PA11, PA12, PB5 and PD6 are pulled high.

Any help?

TIA

/Janne

#bootloader-stm32f105
5 REPLIES 5
Fristedt.Jan
Associate II
Posted on August 04, 2011 at 11:17

Thank you for your input.

I have read AN2606 a dozen times. OK, maybe not a dozen but many times. I'm missing AN2662 mentioned in the thread i referred to. The errata has also been studied.

My problem is that I can't even get in contact with the bootloader. Everything looks good, that is pins that need to be high are high. There is no problem running the debugger via JTAG.

We used STM32F107 for experimenting and there it was no problem getting in contact with the bootloader via USART1. The only thing I can think of that is different on this board is the processor and the crystal frequency, 8MHz vs 25MHz on the development board. But that shouldn't be the problem since the USART use the HSI oscillator. At least according to the documentation.

Can the problem be that we inject about 45uA in the BOOT0 pin? Probably not.
Fristedt.Jan
Associate II
Posted on August 08, 2011 at 10:14

I still have no solution to this problem.

Anyone out there with a solution or the same or similar problem?

Fristedt.Jan
Associate II
Posted on September 13, 2011 at 10:54

We still have no solution to this problem! We have tried to get help through our distributor but they can't get any serious answers from ST.

We have a ''blinky'' application loaded into flash and can see that the processor doesn't jump to the application when BOOT0 is high and BOOT1 is low.

We have even lowered our expectations and tried to get in contact with the bootloader via USART1 on PA9/PA10.

ARE WE ALONE WITH THIS PROBLEM?
support
Associate
Posted on May 03, 2012 at 02:31

Hi, Any luck on your issue. I'm having the same issues like you having. Hope you can share some light. The F105 date code is 206.