Bug 204746 - [terminal][serial] Terminal should support entering custom port names not detected by RXTX
Summary: [terminal][serial] Terminal should support entering custom port names not det...
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: Terminal (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 2.0.1   Edit
Assignee: Michael Scharf CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-26 19:36 EDT by Martin Oberhuber CLA
Modified: 2007-09-26 19:36 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-09-26 19:36:13 EDT 
Some computers provide serial terminals over custom port names which are not detected by RXTX (for instance, the com0com virtual port from SourceForge provides CAN0A, CAN1B etc).

The Serial Terminal connector should support entering such custom port names in its dropdown.

Workaround: Launch Eclipse with

-vmargs -Dgnu.io.rxtx.SerialPorts=CAN0A;CAN0B

-----------Enter bugs above this line-----------
TM 2.0.1 Testing
installation : eclipse-SDK-3.3 (I20070625-1500), cdt-4.0.0, emf-2.3.0
RSE install  : Download RSE-2.0.1RC1: RSE-SDK,examples,tests,discovery,terminal
java.runtime : Sun 1.6.0_01-b06
os.name:     : Windows XP 5.1, Service Pack 1
------------------------------------------------
Comment 1 Martin Oberhuber CLA 2007-09-26 19:36:45 EDT 
Fix committed, comment:

Serial terminal now allows to specify a port manually (e.g. to access virtual devices that are not found by the port scan)