Project

General

Profile

Actions

Feature #4917

open

reporting of alarms/errors known to the icE1usb

Added by laforge about 3 years ago. Updated almost 2 years ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
icE1usb
Target version:
-
Start date:
12/18/2020
Due date:
% Done:

70%

Spec Reference:

Description

Now that the device firmware is exposing error situations / counters via a dedicated interrupt endpoint, we should make use of this in osmo-e1d.

See https://gerrit.osmocom.org/c/osmo-e1d/+/21782 and https://gerrit.osmocom.org/c/osmo-e1d/+/21783 for a start.

We should also consider if and how to report such errors to the clients (libosmo-e1d users).

Furthermore, there is also important knowledge to be gained from parsing the TS0, such as
  • does the remote end indicate alarm via A bit
  • does the remote end report CRC errors via E bits

Checklist

  • receive and report device-reported errors in VTY+LOG
  • pass error informatio n to clients/users
  • process TS0 to learn about reported remote errors
Actions #1

Updated by laforge about 3 years ago

  • Checklist item process TS0 to learn about reported remote errors set to Done

https://gerrit.osmocom.org/c/osmo-e1d/+/21808 adds reporting of E and A bits to VTY and log

Actions #2

Updated by laforge almost 2 years ago

  • Checklist item receive and report device-reported errors in VTY+LOG set to Done
Actions #3

Updated by laforge almost 2 years ago

  • % Done changed from 20 to 70
Actions #4

Updated by laforge almost 2 years ago

  • Status changed from In Progress to Stalled
Actions #5

Updated by laforge almost 2 years ago

  • Category set to icE1usb
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)