This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1002295] New: NTP Server Issues
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Wed, 01 Aug 2018 15:22:55 +0000
- Subject: [Bug 1002295] New: NTP Server Issues
- Auto-submitted: auto-generated
- Dkim-filter: OpenDKIM Filter v2.11.0 mail.ecoscentric.com 1A8D9A83256
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1002295
Bug ID: 1002295
Summary: NTP Server Issues
Product: eCos
Version: unknown
Target: Custom (Customer specific)
Architecture/Host_ ARM
OS:
Status: UNCONFIRMED
Severity: normal
Priority: low
Component: Other
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: cmcnab@idexcorp.com
QA Contact: ecos-bugs@ecos.sourceware.org
CC: ecos-bugs@ecos.sourceware.org
Custom Target: ATSAM9G45
Hello,
My name is Chris McNab and I'm part of Toptech Systems / Idex Corp working with
eCOS and the Atmel ATSAM9G45 microprocessor.
We're having an issue using the NTP server with eCOS. I'm using the following
functions:
cyg_ntpclient_start(&ntp_config); // where ntp_config has the IP address of an
NTP server (pool.ntp.org) and settime is 0.
And I'm then trying to read the status back with:
cyg_ntpclient_status_get(&ntp_status) // where ntp status is of type
cyg_ntpclient_status
What we're finding is that the status is returning an IP address from the NTP
pool correctly (which I can ping) but I have a trustLevel=2 and all other
values in the structure are 0. After calling cyg_clock_get_systime the time
itself is incorrect returning a time that's about 7 hours behind the current
time as well as an incorrect date (a day behind).
Are there any known issues with NTP server support? Anything I can try doing
differently to debug the issue. I'd appreciate any help or advice you can give
us!
Thanks,
Chris
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.