Within the SDK, under "Doc" directory, look out for a Smart-HW-interface pdf document. It has the details.
thanks, for reply at last i have got reply for one of my most.
i have followed the same document and made sample code for uart communication but i face some problem with uart read operation, write operation works fine. Please let me know is there any changes which i have missed.
i have made the following setup to test for uart communication.
1) Used 2 TAG boards
2) One board my sending 8 bytes of data on periodic events for every 7sec
3) Second board i m reading the data using puart
(both boards I have connected through uart)
Most of the time(98%) my uart communication never works as i expected.it is able to receive all the 8bytes.
But those values are not correct.
i am struggling to setup this basic uart communication for more than 2days.
For a tested, working sample app on PUART-PUART communication between two Tag boards, please see my posting below:
This post, however, does not incorporate use of the HCI UART. This way you can isolate the problem to the HCI UART if you still run into problems.
this post is also no use to me. with this example code i am seeing the same behavior.
on uart read side i m able to get all the characters which is sent from other tag.
but the main problem is each and every time the read value is not matching with the sent value.
my strong believe is some more settings, i might be missing which is not documented properly.
kindly help me in resolving the problem.
The sample code is PUART to PUART sending single bytes on the click of a button. Did you isolate the problem you're having to the PUART (I believe you're using HCI UART to PUART?)? If so, you may be running into problems with use of the FIFO, since my example code doesn't come close to testing the boundaries of the FIFO.
I believe that if you configured your PUART in the same manner as the test code, your problems are likely stemming from the HCI UART.
I'm confused regarding the references to the HCI UART. The HCI UART can ONLY be used to program the device, no exceptions.
To do this, you will need to use the SDK or the command line tools.
The PUART will not possess the needed protocol to talk to the HCI UART.
It seems I misread the second comment. I was under the impression that UART was referring to the HCI UART, versus the PUART.
If the communication is PUART to PUART, the test code should have worked. Was the code successful in sending single bytes exactly as its configured? Or did it stop working upon some alteration? If the code never worked perhaps there's a hardware problem.