[srslte-users] srsLTE on Ettus E310

[Ismael Gomez]

Hi Tom,

That indicates that the UE can not successfully decode the PBCH.

Can you check if the pos=1545 is repeated in all messages? If not that
would mean that sync is lost, probably because the ARM9 can not process
fast enough.

Have you compiled srsLTE in the ARM9 with VOLK support?

Also, can you run it without -v and see if you see "O" messages on the
console output? You should see them on the left of the screen.

Thanks

On Tue, 31 Mar 2015 at 16:21 Tom Chatt <tom.j.chatt at gmail.com> wrote:

> I had moderate success yesterday running srsLTE on the Ettus Research USRP
> E310.  I compiled LibFFTW and srsLTE on the ARM9, and was able to build
> srsLTE successfully.  However, when I ran the pdsch_ue demo program, I had
> a problem with the software hanging up during the sync process.  The
> following output was repeated several hundreds of times (while running with
> the -v option enabled):
>
> [INFO]: SYNC ret=0 N_id_2=1 find_offset=0 pos=1545 peak=1.16
> threshold=4.00 sf_idx=0, CFO=0.005 KHz
> [INFO]: Resetting PBCH decoder after 0 frames
>
> and finally the program terminated with "Cell not found".  I verified
> using a USRP B200 and srsLTE running on my PC that there is a cell at the
> frequency I checked (739MHz, in Maryland, USA) and srsLTE was able to
> decode it with no trouble.  I dug into the source code a bit and found on
> lines 130-133 of ue_mib.c:
>
> /* Reset decoder if we missed a frame */
> if (q->frame_cnt > 8) {
>     INFO("Resetting PBCH decoder after %d frames \n", q->frame_cnt);
>     srslte_ue_mib_reset(q);
> }
>
> However, in the printout pasted above, q->frame_cnt appears to be 0 every
> time.  I can investigate further, but I wonder if this is an issue anyone
> has encountered before?
>
> Tom Chatt
> _______________________________________________
> srslte-users mailing list
> srslte-users at lists.softwareradiosystems.com
> http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20150331/aa46ed24/attachment.htm>