Debug via USB-OTG


Willhelm

Very Active Member
Joined
Aug 19, 2014
Messages
221
Location
Helmstedt
Hi all,

i searched to forums and manuals about the debug capabilites of the pyra.

As I connected my pyra to my laptop via USB-OTG i got on my laptop:

[ 1114.299316] wlp3s0: authenticate with 30:b5:c2:87:82:28
[ 1114.299328] wlp3s0: 80 MHz not supported, disabling VHT
[ 1114.304613] wlp3s0: send auth to 30:b5:c2:87:82:28 (try 1/3)
[ 1114.307758] wlp3s0: authenticated
[ 1114.309993] wlp3s0: associate with 30:b5:c2:87:82:28 (try 1/3)
[ 1114.312015] wlp3s0: RX AssocResp from 30:b5:c2:87:82:28 (capab=0x431 status=0 aid=1)
[ 1114.316081] wlp3s0: associated
[ 1114.362618] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready

from several Entries i tried to connect from my laptop to the pyra via:

minicom -b 115200 -D /dev/ttyUSB0
picocom -b 115200 /dev/ttyUSB0

however that did not work o_O

is there a wiki page or a forum entry about that topic?
 
In the future "that did not work" is a vague problem. Did you get an error? Did it try to do something then just return?

I had issues with minicom, I think it was a group issue.

Screen was my weapon of choice, from the forum .
I too had trouble with minicom. I found screen much easier to use from a linux machine (which I think you have based on that minicom error)

Is what I use to connect to the serial port of the Dev Board.
Control+a, then d to detach from that screen.
Control+a, then \ will kill a screen session if you run into trouble.
screen -r should be able to reattach.
screen -ls shows screen sessions available.

You should be able to see the pyra show up as a connectable device if you ls /dev/*USB*

Hopefully this is helpful information.
I should dig up how to save what is passed to screen to the host machine.

-edit-
Forgot that you need to run screen as sudo after seeing your post.
-edit 2-
You can also use Control-a + H to save logs into screenlog.n file. One more Control-a + H to turn off.
And this should make it to the wiki
-edit-
Attempted to add details to wiki, there are issues with the wiki :(
 
Last edited:
Is not a problem with RISC OS.
After you connect, you should found an FTDI Device...


term_1-jpg.38630
 
  • Like
Reactions: rSl
I believe on whatever system you're using minicom on, you will need to add yourself to the dialout group if you want to use serial, or just run it as root... I won't judge you...
 
Back
Top