public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Anders Holmberg (QMW)" <Anders.Holmberg@emw.ericsson.se>
To: "'ecos-discuss@sourceware.cygnus.com'"
	<ecos-discuss@sourceware.cygnus.com>
Subject: [ECOS] Serial tests fail on ARM AEB
Date: Thu, 22 Jun 2000 01:15:00 -0000	[thread overview]
Message-ID: <218E0A05F1A3D311B83F00508B6FAB814F806F@esemont200.gbg.edt.ericsson.se> (raw)

Hi, 

I am having problems running the serial tests on my ARM AEB revision C board. When serial2.exe is executed I receive the following message: 
 
  FAIL:<Can't lookup /dev/ser1> Line: 1118, File: //C/ecos/packages/io/serial/v1_3_1/tests/ser_test_protocol.inl
  EXIT:<done>

I am using eCos 1.3.1 and have only made the following changes to the ARM AEB default template: 
  - AEB board revision = C
  - Activate AEB serial port 0 and 1

When I look a bit closer using gdb it seems like there is no devices installed at all (__DEVTAB__ and __DEVTAB_END__ points to the same address in space, see below). 

  (gdb) info address __DEVTAB__
  Symbol "__DEVTAB__" is at 0x120f8 in a file compiled without debugging.
  (gdb) info address __DEVTAB_END__
  Symbol "__DEVTAB_END__" is at 0x120f8 in a file compiled without debugging.

and the variables aeb_serial_io0 and aeb_serial_io1 are undefined. This of course makes the function cyg_io_lookup fail which in the end gives me the error message above. 

Environment
- WinNT
- Cygwin 1.1.2
- eCos 1.3.1
- arm-elf-gcc 2.96

/Anders Holmberg

             reply	other threads:[~2000-06-22  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-22  1:15 Anders Holmberg (QMW) [this message]
2000-06-22  2:04 ` Jesper Skov
2000-06-22  3:37 Anders Holmberg (QMW)
2000-06-22  5:01 ` Jesper Skov
     [not found] <218E0A05F1A3D311B83F00508B6FAB814F8073@esemont200.gbg.edt.ericsson.se>
2000-06-22  5:13 ` 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=218E0A05F1A3D311B83F00508B6FAB814F806F@esemont200.gbg.edt.ericsson.se \
    --to=anders.holmberg@emw.ericsson.se \
    --cc=ecos-discuss@sourceware.cygnus.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).