L1 corruption?

suraev at stud.ntnu.no suraev at stud.ntnu.no
Fri May 13 17:45:36 UTC 2011


Hi.

I'm trying to follow the logic described in app_ccch_scan to send RACH bursts to my
openbts.

First 2-2 goes fine but after that I got constant errors - see below.

It looks like after I've sent couple of packets something got corrupted in L1.

How can I debug this and understand what causing all the errors?

LOG:

<0001> app_rach_send.c:227 registering signal handler...
<0001> app_rach_send.c:229 resetting L1...
<0001> app_rach_send.c:231 L3 init...
<0001> app_rach_send.c:190 requesting FBSB from L1...
<0001> app_rach_send.c:200 unhandled callback 1 <S_L1CTL_FBSB_RESP> fired...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:73 SI2 on the wrong TC: 0
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:75 SI3 on the wrong TC: 0
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:75 SI3 on the wrong TC: 0
<0001> app_rach_send.c:200 unhandled callback 5 <S_L1CTL_CCCH_MODE_CONF> fired...
<0001> app_rach_send.c:200 unhandled callback 5 <S_L1CTL_CCCH_MODE_CONF> fired...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:86 SI4 on the wrong TC: 0
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:86 SI4 on the wrong TC: 0
...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:86 SI4 on the wrong TC: 0
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:70 SI1 received.
<0001> app_rach_send.c:127 sending RACH #0 on ARFCN 21...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:127 sending RACH #1 on ARFCN 21...
<0001> app_rach_send.c:111 obtained BCCH, dumping...
<0001> app_rach_send.c:127 sending RACH #2 on ARFCN 21...
<0000> rslms.c:136 unknown RSLms msg_discr 0x0c
<0000> rslms.c:136 unknown RSLms msg_discr 0x0c
<0000> rslms.c:136 unknown RSLms msg_discr 0x0c
<000b> l1ctl.c:210 Dropping frame with 80 bit errors
<000b> l1ctl.c:210 Dropping frame with 80 bit errors
<000b> l1ctl.c:210 Dropping frame with 80 bit errors
<000b> l1ctl.c:210 Dropping frame with 59 bit errors
<000b> l1ctl.c:210 Dropping frame with 59 bit errors
<000b> l1ctl.c:210 Dropping frame with 59 bit errors
<000b> l1ctl.c:210 Dropping frame with 58 bit errors
<000b> l1ctl.c:210 Dropping frame with 58 bit errors
<000b> l1ctl.c:210 Dropping frame with 58 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
<000b> l1ctl.c:210 Dropping frame with 62 bit errors
<000b> l1ctl.c:210 Dropping frame with 60 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors
<000b> l1ctl.c:210 Dropping frame with 61 bit errors





More information about the baseband-devel mailing list