This means that communication with the serial port isn't working right.
1. It could mean that there isn't any serial port at the IO address that setserial thinks your port is at.
2. It could also be an interrupt conflict (or an IO address conflict).
3. It also may mean that the serial port is in use (busy or opened) and thus the attempt to get/set parameters by setserial or stty failed.
4. It will also happen if you make a typo in the serial port name such as typing "ttys" instead of "ttyS".
1. It could mean that there isn't any serial port at the IO address that setserial thinks your port is at.
2. It could also be an interrupt conflict (or an IO address conflict).
3. It also may mean that the serial port is in use (busy or opened) and thus the attempt to get/set parameters by setserial or stty failed.
4. It will also happen if you make a typo in the serial port name such as typing "ttys" instead of "ttyS".
'QnA' 카테고리의 다른 글
cat /dev/null > a.txt 2>&1 (0) | 2009.07.27 |
---|---|
Re: rs_init() (0) | 2009.07.26 |
BTUART사용시 질문 (0) | 2009.07.16 |
external memory interface (0) | 2009.07.16 |
UART 콘트롤러 칩 추가.. (0) | 2009.07.16 |
WRITTEN BY
- RootFriend
개인적으로... 나쁜 기억력에 도움되라고 만들게되었습니다.
,