这是怎么回事DTR / RTS后，发送到基于FTDI-Arduino板？ [英] What's going on after DTR/RTS is sent to an FTDI-based Arduino board?

问题描述

我在一个草图努力从Android设备的支持上载Arduino板，它适用于 Duemilanove （的 FTDI 基）和 Arduino的乌诺（的ATmega 基）使用的 RXTX （纯Java）。

I'm working over a sketch to enable uploading from an Android device to an Arduino board, and it works for Duemilanove (FTDI-based) and Arduino Uno (ATmega-based) when testing for PC/Arduino using rxtx (pure Java).

但使用的USB-的Andr​​oid库时不工作作为setDTR / setRTS方法尚未实现。

But it does not work when using the USB-Android library as the setDTR/setRTS methods are not yet implemented.

FTDI的Andr​​oid驱动程序允许setDTR / setRTS信号的发送，但未能发送/后读取数据。

FTDI Android drivers allow the sending of setDTR/setRTS signals, but it fails to send/read data after it.

所以，问题是Android USB API中，我无法弄清楚什么是错的。

So the problem is in the Android USB API and I can't figure out what's wrong..

在DTR / RTS被切换为基于FTDI-的Arduino板会发生什么？

What happens for FTDI-based Arduino boards after DTR/RTS are toggled?

我相信设备复位和引导程序的命令等待（ STK500 ）为〜50-250 NBSP;毫秒。我说得对不对？

I believe that the device is reset and waits for bootloader commands (STK500) for ~50-250 ms. Am I right?

推荐答案

答案是，主板复位。该示意图中的电路板上复位方式进行（RTD / DTR是有线到单片机的复位引脚不知）。

The answer is that the board resets. The schematic is made in the way it resets the board (RTD/DTR is wired to the microcontroller reset pin somehow).

这篇关于这是怎么回事DTR / RTS后，发送到基于FTDI-Arduino板？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！