On Mon, Jan 18, 2016 at 8:35 AM, Ben Coman <btc at openinworld.com> wrote:
> On Mon, Jan 18, 2016 at 7:38 AM, tim Rowledge <tim at rowledge.org> wrote:
>>
>>> On 14-01-2016, at 5:51 AM, Jon Hylands <jon at huv.com> wrote:
>>>
>>>
>>> Hi everyone,
>>>
>>> I'm trying to use the SerialPort class on my Raspberry pi 2, to access the UART on the pi.
>>>
>>> I've successfully accessed the port from python, using pyserial. On the pi, the port name is '/dev/ttyAMA0’.
>>
>> The only thing I can offer is that Scratch finds a serial port as /dev/ttyAMA0 as well, implying that on at least one Pi it finds the same port that python does. I don’t think I have any devices that I could even try to connect to. Any suggestions for things that might be around the office?
>>
>> I do faintly recall some discussions about Pi serial stuff and having to use the rasp-config utility but that was a long time ago and I don’t seem to have any emails referring to it.
>>
>>
>> tim
>> --
>> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
>> Strange OpCodes: EOS: Erase Operating System
>>
>>
>>
>
> Maybe you could just loop back...
> http://unix.stackexchange.com/questions/117037/how-to-send-data-to-a-serial-port-and-see-any-answer

Whoops, sent too soon - just a potential problem...
http://unix.stackexchange.com/questions/42964/unexpected-results-testing-serial-loopback-using-echo-and-cat

Loopback with SoCat
http://myrobotlab.org/content/serial-terminal-loopbacks-linux

Hardware loopback
http://serial-lines.blogspot.com.au/2011/04/for-this-post-were-going-to-send-some.html

Toubleshooting...
http://www.ee.ryerson.ca/~phiscock/papers/serial.pdf

cheers -ben