During the i2c write or read operation , why the gpio write execution is stoped.

[premkumar]

Hello Mates,

                   What you are viewing in the image is the cyan(bue colour) is i2c clk  an yellow pulse is an gpio trigger mechanisim 

.You can see that the low pulse is i2c clk that means an operation read or write , in that particular case the is no gpio triger is working why what is the reason. 

                 → the i2c is running in the polling mode

                 → the gpio triger is in the timer interrupt in 20hz

                 → what acutally done in the gpio is trigger in the 5hz enable the flag inside the 20hz timer trig.

                 → using the mcu stm32h503rbt6

 

[Andrew Neil]

yellow pulse is an gpio trigger mechanisim

Please tell more about this!

Also, how is the I2C operating: interrupt? DMA?

A minimum but complete example which illistrates the issue would help.

 

 

Your scope has a USB socket for capturing screenshots:

Please use it - it will give far better results than trying to photograph the screen!

• No glare
• No wonky angles
• Perfectly focussed
• Just the screen - no unnecessary extras

[premkumar]

Hello ​@Andrew Neil 

 

→ i2c is running in polling

→ actually i implemnted fat 12 in the device , i2c is used for that 

→ i2c is used to write log in eeprom , and read and give data to the usb msc class

[Andrew Neil]

 i2c is running in polling

What does that actually mean?

If you’re doing blocking waits, that could well explain why your GPIO stops.

 

You still haven’t said how you generate that “gpio trigger mechanisim”

 

Again, please see:

How to write your question to maximize your chances to find a solution