超级终端不与STM8通信

你好Stefano，
 
 
 感谢您的相关反馈。你是对的，引脚3和引脚7和8之间没有连接。
 
 我们会尽快修改此文档。
 
 感谢您的帮助
 
 问候
 
 格罗姆



以下为原文





Hello Stefano ,


Thanks for this relevant feedback . You're right , there is no connection beetween pin 3 and pin 7 and 8.

We will modify this documentation ASAP.

Thank you for your help

Regards

Grom

亲爱的格罗姆，
 
 
 感谢您的回复-
 我尝试将引脚＃3从7和8断开，但保持7和8连接在一起，不幸的是还没有通信。
 
 你的意思是说＃7和8引脚也必须相互断开吗？
 
 在您的意见中，原理图中是否还有其他错误？
 
 提前致谢
 斯特凡诺



以下为原文





Dear Grom,


thanks for your reply-
I've tried by disconnecting pin#3 from 7 and 8, but keeping 7 and 8 connected together and unfortunately no communication yet.

Did you mean that pins# 7 and 8 have to be disconnected from each other too?

Are there any other mistakes in the schematic, in your opinon?

Thanks in advance
Stefano

我通过连接测试了应用程序
 
 
 Pin2 - ＆gt; ST232B引脚13（R1in）
 Pin3 - ＆gt; ST232B引脚14（T1out）
 Pin5 - ＆gt; GND
 
 在许多应用案例中，其他连接不是强制性的。
 希望它能解决你的问题
 
 问候
 
 格罗姆



以下为原文





I've tested the application by just connecting


Pin2 -> ST232B pin 13 (R1in)
Pin3 -> ST232B pin 14 (T1out)
Pin5 -> GND

Other conections are not mandatory in many Application case .
Hope it will solve your problem

Regards

Grom

嗨格罗姆，
 
 
 我已经测试了应用程序示例，它现在可以根据您的建议正常工作。
 
 尽管微控制器UART实际配置为ODD奇偶校验，但超级终端必须配置为9600，N，8,1-无奇偶校验。如果我将ODD奇偶校验置于超级终端中，则通信无法显示错误的字符，或者超级终端客户端窗口仍然停留在光标处。
 
 我还尝试在NO或ODD中更改微控制器Uart初始化参数。这对超级终端没有任何影响，超级终端只想要不进行奇偶校验。
 
 谢谢
 斯特凡诺
格罗姆
2010年5月13日星期四下午2:18
STM8发现 - 超级终端示例故障
 
我通过连接测试了应用程序
 
 
 Pin2 - ＆gt; ST232B引脚13（R1in）
 Pin3 - ＆gt; ST232B引脚14（T1out）
 Pin5 - ＆gt; GND
 
 在许多应用案例中，其他连接不是强制性的。
 希望它能解决你的问题
 
 问候
 
 格罗姆



以下为原文





Hi Grom,


I've tested the application example and it now works fine with the connection according to your suggestion.

The hyperterminal must be configure as 9600, N, 8, 1 - NO parity, despite the microcontroller UART is actually configured as ODD parity. If I put ODD parity in the hyperterminal the communication fails displaying wrong characters or the hyperterminal client window remains stucked at the cursor.

I've also tried to change the microcontroller Uart initialization params in NO or ODD. This has no still effects on hyperterminal, which wants NO parity only.

Thanks
Stefano



Grom
Thursday, May 13, 2010 2:18 PM
STM8 Discovery - Hyperterminal example trouble


I've tested the application by just connecting


Pin2 -> ST232B pin 13 (R1in)
Pin3 -> ST232B pin 14 (T1out)
Pin5 -> GND

Other conections are not mandatory in many Application case .
Hope it will solve your problem

Regards

Grom

大家好。
 
 第一次来这里。
 我刚刚开始工作了。
 除了2 RX，3TX＆amp;之外，我没有连接任何引脚。 5Gnd。
 PINS 2＆amp;如果你没有使用NULL调制解调器电缆（有一个扭曲），我们大多数人都不会，需要反转3。
 在我能找到的任何地方都没有提到它。
 文档将TX发送到TX，RX发送到RX。
 至于奇数奇偶校验，我也有这个问题。
 当您在Hyperterminal pdf的底部配置Hyperterminal时，它表示使用7位和奇校验。不是8位而是没有。
 它还显示了一些其他差异，例如ASCII输入力7。
 当你做这一切时，它的工作原理。
 干杯
 关口



以下为原文





Hi all.

First time on here.
I just got it working.
I didnt connect any pins other than 2 RX, 3TX & 5Gnd.
The PINS 2 & 3 need to be reversed if you are not using a NULL modem cable (with a twist in it) as most of us would not.
No mention of that anywhere I could find.
The documentation puts TX to TX and RX to RX.
As for the odd parity, I had this problem too.
When you configure Hyperterminal as it says .. down the bottom of the Hyperterminal pdf , it says to use 7 bits and odd parity. Not 8 bits and none.
It also shows a few other differences such as ASCII input force 7.
When you do all this it works.
Cheers
Col

06/29/2010
 
 我刚检查了um0884文档（RS232 Comms）是否有任何变化。
 仍然不正确
 只是想知道如何阅读这份文件。
 干杯
 关口



以下为原文





06/29/2010

I just checked the um0884 document (RS232 Comms) for any changes.
Still incorrect  
Just wondering how everone reading this document is getting on.
Cheers
Col

嗨格罗姆，
 
 刚检查了UM0884 Doc。仍然不正确。
 只是想知道这个UM0884文件什么时候会被纠正，因为它会导致很多压力。
 干杯
 关口



以下为原文





Hi Grom,

Just checked the UM0884 Doc. Still incorrect.
Just wondering when this UM0884 Document will be corrected as it would be causing a lot of stress out there.
Cheers
Col

如果指定了任何奇偶校验，则字节将在UART发送时进行修改。您可以通过配置超级终端（或minicom）来指定7个数据位来解决这个问题，因为这会掩盖奇偶校验位。我发现这是一个问题，当我创建一个与Windows的SLIP连接，因为我找不到指定7个数据位（或以其他方式屏蔽奇偶校验位），因此Windows从未正确接收确认字符串，因为一些字符有额外的位，并且与预期的解释不同。我修复它的方法是在main.c：68指定NO奇偶校验：UART2_Init（（u32）9600，...，UART2_PARITY_NO，......）;这是非常常见的（例如9600 8N1）。这允许在不改变的情况下传输字符，并且能够建立SLIP连接。



以下为原文





If any parity is specified, the bytes will be modified as they are transmitted by the UART.  You can get around this by configuring hyperterminal (or minicom) to specify 7 data bits, since that will mask off the parity bit.  I found this to be a problem when I created a SLIP connection with Windows, since I could find no way to specify 7 data bits (or otherwise mask off the parity bit), and so Windows never correctly received the acknowledgment string, because some of the characters had extra bits and were interpreted differently than intended.  The way I fixed this was to specify NO parity, at main.c:68:UART2_Init((u32)9600, ..., UART2_PARITY_NO, ...);, which is very common (e.g. 9600 8N1).  This allowed the characters to be transmitted with no alteration, and the SLIP connection was able to be established.