From: "Ling Su" <lingsu@palmmicro.com>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Test Serial Port 2 on NEC vrc4373 target.
Date: Tue, 24 Oct 2000 16:05:00 -0000 [thread overview]
Message-ID: <001c01c03e0f$5aae0740$1201a8c0@crusoe> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
Hi,
Â
I am trying to test the serial port 2 on my board working properly. I
wrote some programs and connect my PC and the board using a direct serial cable
(not null modem, since I found GDB doesn't use null modem, I guess the two
serial ports are in same configuration). Unfortunately, I don't read
out anything although on the PC side I wrote a program to keep writing to the
this serial port.
Â
I have ever tried the serial port test cases in eCos with
"ser_filter" for serial port 1. I think I might be able to run the test cases on
serial port 2, so I did following things and try to run one
of the test cases,
Â
<1>. I modified the ser_test_protocol.inl, change the "TEST_SER_DEV"
from "CYDAT_IO_SERIAL_MIPS_VRC4373_SERIAL0_NAME"Â to
"CYDAT_IO_SERIAL_MIPS_VRC4373_SERIAL1_NAME". Supposely the test case will use
"/dev/ser1" instead of "/dev/ser0".
Â
<2>. On PC side, I run following command in seperate console,
       ser_filter -t 9001 /dev/ttyS0
38400
       ser_filter -t 9000 /dev/ttyS1
38400
Thus two program will monitor both of the two ports.
Â
<3>. Using GDB to load the test case "serial3" to "remote
localhost:9001", it was successfully loaded. But when I let the program run, it
halts on "NOT APPLICABLE: no host side harness dectect". Apparently it tried to
read reply from HOST, nothing read in and timer timeout was triggered .
Â
So more specifically, my question is, anything wrong with my assumption and
procedure? or any method to test serial port 2?
Â
Thanks for anyone who can shed me some light!
Â
Regards,
-Ling
next reply other threads:[~2000-10-24 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 16:05 Ling Su [this message]
2000-10-24 19:01 ` Jonathan Larmour
2000-10-24 23:48 ` Jesper Skov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001c01c03e0f$5aae0740$1201a8c0@crusoe' \
--to=lingsu@palmmicro.com \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).