RS232/UART communication problems using ARYGON µC equipped readers (APDB2UA33)

[nfc-tools]

RS232/UART communication problems using ARYGON µC equipped readers (APDB2UA33)

[GoogleCodeExporter]

In r112, delays have been extended to 70ms (20 more ms). This way, we are able 
to run
device at 9600 bauds, unfortunately, devices that are faster will be slow as 
9600
bauds device is, but is it a problem ?

Original comment by [email protected] on 17 Sep 2009 at 10:05

• Changed state: Fixed

[GoogleCodeExporter]

Reopen this issue: 70ms doesn't fixed this problem for all cases...

Original comment by [email protected] on 17 Sep 2009 at 11:09

• Changed state: Accepted

[GoogleCodeExporter]

I'm not able to have a truly stable communication between host (PC) and device
(ARYGON APDB µC equipped (APDB2UA33)) only by tweaking delays. So, I wrote a
bufferred rx (but not a circular like previously suggested) and a frame checker 
to be
able to fetch clean and valid frames. Unfortunately, even using this way there 
are
some corner cases where one TAMA frame can be dropped...
I'm now thinging about NOT support APDB2UA33, which is an PN532 + ARYGON µC 
where
ARYGON µC is not used by libnfc...
BTW, I have attached a patch against r113, which allow APDB2UA33 to work almost
correctly.

Original comment by [email protected] on 17 Sep 2009 at 3:15

Attachments:

• arygon-low-speed-devices-support.patch

[GoogleCodeExporter]

I've attached these pathces:

- "rs232.h" & "rs232.c" patches add the "rs232_get_speed" function for both 
Linux e
Windows systems (not tested) and implement the "rs232_set_speed" function on 
Windows
(not tested).

- The "dev_arygon.c" patch removes the last 20ms delay from ARYGON code if the 
port
speed value is greater than 9600.

Original comment by emanuele.bertoldi on 18 Sep 2009 at 10:35

Attachments:

• rs232.c.patch
• rs232.h.patch
• dev_arygon.c.patch

[GoogleCodeExporter]

...And if you add this line, you should have the read buffer reset on Windows
platform too (untested):

PurgeComm(sp->hPort, PURGE_RXABORT | PURGE_RXCLEAR);

Original comment by emanuele.bertoldi on 21 Sep 2009 at 1:14

[GoogleCodeExporter]

Thanks Zuck !

Your work have been added in r114.
Unfortunately, like previously said, adding more delays doesn't fix all 
communication
problem with ARYGON reader with µC + PN523. So, I have removed 20ms delay in
dev_arygon.c, ARYGON PN532 devices which run at 115200 bauds runs fine and 
APDB2UA33
support is actually dropped.

Original comment by [email protected] on 21 Sep 2009 at 3:06

• Changed title: RS232/UART communication problems using ARYGON µC equipped readers (APDB2UA33)
• Changed state: WontFix