cancel
Showing results for 
Search instead for 
Did you mean: 

STM32F105 - USB OTG - BusFault at 0x1fff7a10

claudio23
Associate II
Posted on January 07, 2018 at 10:07

Hi

I try to implement a VCP on a STM32F105RB with the STM32_USB-Host-Device_Lib_V2.2.0

I was able to compile the Code sucessfully.

My Hardwareconfiguration is the following:

Mini USB directly (without series resistors) to D+ and D- of the STM32. +3.3V to PA9 (for BusSensing)

After debugging start in atollic, the host detects a new device but it is not listed in the device manager.

After few seconds, i get a BusFault on the STM. The BFARVALID is set and the BFAR is 0x1FFF 7A10

This is interessting, since the Addressspace between 0x0804 0000 - 0x1FFF AFFF is reserved.

If i restart the firmware 2-3 times (NOT the debugging process, only do a soft reset not a hard reset) and click run again, then it detects the VCP correctly after some tries. It shows a not working COM9 and a working COM10 in the device manager. And it does not end up in the bus fault anymore.

Can anybody help me solve this problem?

Thanks

Attached are the Registers at BusFault and the Dissassembly.

#usb-otg #busfault #atollic-truestudio #usb-device
1 ACCEPTED SOLUTION

Accepted Solutions
claudio23
Associate II
Posted on January 07, 2018 at 15:11

I found the problem.

It was in the file: usbd_desc.h

i missed to define the correct board.

So it tried to get the Device ID from a wrong address. -> BUS FAULT

View solution in original post

1 REPLY 1
claudio23
Associate II
Posted on January 07, 2018 at 15:11

I found the problem.

It was in the file: usbd_desc.h

i missed to define the correct board.

So it tried to get the Device ID from a wrong address. -> BUS FAULT