Skip to main content
Associate
May 21, 2024
Question

STM32F407 discovery board: USB and I2C issue

  • May 21, 2024
  • 6 replies
  • 1755 views

Is there anyone who experience this issue?

 

I use eeprom with I2C and USB OTG communication in STM32F407 discovery board. There is no common GPIO pin.

 

whenever I use USB OTG to write something in eeprom through I2C, USB and I2C looks disabled in same time. 

 

I googled it and found there are similar issue but no solution at all.

 

is there any solution?

 
This topic has been closed for replies.

6 replies

Andrew Neil
Super User
May 21, 2024

@Jimmy_LEE wrote:

USB and I2C looks disabled in same time. 


What do you mean by that?

What investigation/debugging have you done to find out what's going on ?

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Jimmy_LEEAuthor
Associate
May 24, 2024

literally looks all function stop. No usb communication response to PC and no I2C response.

 

I have debugged them but I have no idea about this issue...

Andrew Neil
Super User
May 24, 2024

You've marked this as solved - but it doesn't seem to be?

See this to un-mark a solution:

https://community.st.com/t5/stm32-mcus-embedded-software/sd-card-no-file-system-error/m-p/641422/highlight/true#M45514

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
Muhammed Güler
Senior III
May 21, 2024

Are you sure there is no problem with interrupt management?
I felt that you were trying to perform long operations within the interrupt without seeing your code.

Jimmy_LEEAuthor
Associate
May 24, 2024

I think there is no problem with interrupt management. This is really weird. I have checked I2C interrupt couple of times..

 

 
 
ST Technical Moderator
May 21, 2024

Hi @Jimmy_LEE 

Would you provide a minimum example to replicate this issue? you can check if it's applicable on specific I2C / OTG instance?

To give better visibility on the answered topics, please click on "Best answer" on the reply which solved your issue or answered your question.Best regards,FBL