#1478 closed bug (invalid)
Unreadable output from Haiku to SerialConnect
| Reported by: | meanwhile | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | - General | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Can't offer a clue about a non-working Haiku install by using SerialConnect: the output Haiku gives is unreadable. SerialConnect was set up on another BeOS machine and connected via null modem cable directly (from serialport to serialport). Settings were according to the BeOS Bible, as follows: Parity: none Databits: 8 Stopbits: 1 Baud Rate: 19200 Flow Control: RTS/CTS (also tried this with 'none'...same result)
Attachments (1)
Change History (4)
by , 17 years ago
| Attachment: | SerialConnect.jpg added |
|---|
comment:2 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
The baud rate is 115200, no flow control, no parity, 8 data bits, 1 stop bit.
comment:3 by , 17 years ago
Of course - I'm not sure what I was thinking :P
Clearly, it's been a while since I've run serial debug (fortunately I rarely have to!)
Note:
See TracTickets
for help on using tickets.
(Sorry, couldn't use another method than a camera "screenshot")