无法在STM8S-discovery中清除I2C BUSY位

我们也面临同样的问题。我们使用的是STM32F103R8控制器。
 
我们尝试执行超时，然后重置I2C总线，但这无助于恢复。我们首先想到的是奴隶没有回应，但我们花了很多时间才发现控制器是罪魁祸首。在发送总线上的从机地址后，我们看到I2C在while循环中等待来自从机（EV6）的ack。
 
 
如果你发现这个I2C在EV6循环问题中陷入困境，你能告诉我们吗？



以下为原文






We too are facing the same problem as you do. We are using STM32F103R8 controller.


We tried to do timeouts and then reset the I2C bus, but that does not help it recover. We first thought it was the slave not responding but it took us a lot of time to find that the controller is the culprit. We see that the I2C is stuck up in the while loop waiting for the ack from the slave (EV6) after sending the slave address on the bus.



Could you please tell us if you have found a soultion to this I2C stuck up in EV6 loop issue.

你好，
同样的hiere。我正在使用带有I2C的stm8s003，有时I2C状态机会被卡住。 Osci告诉我同样的事情：发送地址但随后停靠。将总线速度从100 kHz降低到50 Hz有助于降低所有其他中断的中断优先级，从而有所帮助。看起来像是时间问题。
然而，有时控制器会挂起。到目前为止，我没有找到解决方案。



以下为原文




Hello,
same hiere. I am using a stm8s003 with I2C sometimes the I2C statemachine get stuck. The Osci tells my the same: Address sent but then bus stops. Reducing the bus speed from 100 kHz to 50 Hz helps a bit and reducing the interrupt priority of all other interrupts helps a bit. Looks like a timing issue though.
Nevertheless, sometimes the controller hangs. So far I did not find a solution.

嗨托比亚斯，
你能解决BUSY_Flag问题吗？我也有同样的问题。



以下为原文




Hi Tobias,
were you be able to solve the BUSY_Flag issue? I have the same problem.

大家好，这里也一样。这些STM uC和工具是多么废话。我与德州仪器，Microchip，瑞萨一起使用。我在嵌入式世界中拥有10年以上的编程和硬件设计经验。我试图给STM一个机会并用它为RC车制造一个陀螺稳定器，因为它很便宜，而且我有几个套件放置在周围。过去3天尝试过STM8S103和STM8S105。在某些时候，I2C可以工作，但大部分时间都没有。 105上没有通过忙碌标志。 ST Visual Develop不断崩溃。文档很糟糕。支持是垃圾。我放弃了这个。这是浪费我的时间。我将使用5倍昂贵的uC，但至少我不想让我的电脑挫败沮丧。远离STM。



以下为原文




Hi guys, same thing here. What a piece of crap these STM uC and tools are. I am used with Texas Instruments, Microchip, Renesas. I have 10 years + experience in embedded world both programming and HW design. I tried to give a chance to STM and use it to build a gyro stabilizer for an RC car because it was cheap and i had a few kits laying arround. Tried both STM8S103 and STM8S105 the past 3 days. On 103 somethimes the I2C works but most of the time it does not. On 105 does not pass the busy flag. The ST Visual Develop keeps crashing. The documentation is crap. The support is crap. I am giving up on this. It is a waste of my time. I am going to use a 5 times more expensive uC but at least I am not going to want to smash my computer out of frustrations. Stay away from STM.

请确保遵循数据表，特别是EV5 / EV6。 SPL不正确，不符合数据表。然而，数据表是正确的，至少在标准速率下。
如果你愿意，我可以发一段演示代码。



以下为原文




make sure you follow the datasheet, particularly about EV5/EV6. The SPL is incorrect not in compliance with the datasheet on that. The datasheet however is correct, at least at the standard rate.
I can post a piece of demo code on that if you want.

当从SEEED多通道气体传感器读取时，我发现间歇性I2C CLK被卡在低电平。我很确定STM8S将时钟线驱动为低电平，因为我已经拔掉了从端，但仍然很低。我虽然试图找到一个固件解决方案来清除这个错误并释放CLK线，但唯一可靠的方法是重置STM8，这不是一个理想的解决方案。我更愿意找出为什么这样做......任何想法，任何人？



以下为原文

I am getting an intermittent I2C CLK being stuck low when reading from a SEEED multi-channel gas sensor. I'm pretty sure it is the STM8S driving the clock line low, as I have unplugged the slave end and it's still low. I though about trying to find a firmware solution to clear this error and release the CLK line, but the only certain way is to reset the STM8, which is not an ideal solution. I'd prefer to find out why it is doing this... any ideas, anyone?​