-
Notifications
You must be signed in to change notification settings - Fork 438
Support more debugger protocol in IoT.js #1876
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support more debugger protocol in IoT.js #1876
Conversation
LaszloLango
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the related documentation as well (docs/devs/Use-JerryScript-Debugger.md).
830a361 to
a98ee7b
Compare
|
@LaszloLango : Thanks for the review, I've updated it accordingly. |
LaszloLango
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
|
||
| #### Select transport and protocol layers | ||
|
|
||
| There are two available extension-provided transport layers, websocket and rawpacket, and two procotol layers, tcp and serial. Each initializes the debugger and blocks until a client connects. If you want to specify the debugger transmission layer (default: websocket) or transmission protocol (default: tcp) over the communication you can do with the `--debug-channel [websocket|rawpacket]` and `--debug-protocol [tcp|serial]` options: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The title is a bit confusing. There are many terms here. (transport layer, protocol layer, transmission layer, and transmission protocol.) How about using only channel and protocol?
e.g) Select transport and protocol layers - > Select Channel and Protocol
a98ee7b to
36fbb5f
Compare
|
@daeyeon : You're right, thanks. I've changed it. |
|
|
||
| #### Select channel and Protocol | ||
|
|
||
| There are two available extension-provided channel, websocket and rawpacket, and two procotol, tcp and serial. Each initializes the debugger and blocks until a client connects. If you want to specify the debugger channel (default: websocket) or protocol (default: tcp) over the communication you can do with the `--debug-channel [websocket|rawpacket]` and `--debug-protocol [tcp|serial]` options: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found a typo: procotol -> protocol. Please also check the plural form for channel and protocol.
Adding new options to select serial protocol and rawpacket communcation channel. IoT.js-DCO-1.0-Signed-off-by: Robert Sipka rsipka.uszeged@partner.samsung.com
36fbb5f to
0a8f2f8
Compare
daeyeon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Adding new options to select serial protocol and rawpacket communcation channel.