VTUNE error and signal captured with low db value

Having issues with the site, hardware, source code, or any other issues?
Post Reply
frank2013
Posts: 5
Joined: Tue Aug 05, 2014 5:08 pm

VTUNE error and signal captured with low db value

Post by frank2013 »

I'm using windows 7 and I could run all the version, probe, info command, but when changing frequency an VTUNE error appears:

[ERROR] Invalid VTUNE value encountered

Will try to compile the latest version of bladeRF-cli from scratch and see if it fixes the problem :D :D :D



C:\Program Files (x86)\bladeRF\x64>bladeRF-cli -i -v debug
[DEBUG] bladerf_open_with_devinfo: fw=v1.7.1-git-ca697ee serial=71fc6640a15b03df7cba64fdbc5d56f8 trim=0x88c1 fpga_size=40
bladeRF> info

Serial #: 71fc6640a15b03df7cba64fdbc5d56f8
VCTCXO DAC calibration: 0x88c1
FPGA size: 40 KLE
FPGA loaded: no
USB bus: 1
USB address: 4
USB speed: Hi-Speed
Backend: libusb
Instance: 0

bladeRF> version

bladeRF-cli version: 0.10.3-git
libbladeRF version: 0.12.1-git

Firmware version: 1.7.1-git-ca697ee
FPGA version: Unknown (FPGA not loaded)

bladeRF> probe

Backend: libusb
Serial: 71fc6640a15b03df7cba64fdbc5d56f8
USB Bus: 1
USB Address: 4

bladeRF>
bladeRF>
bladeRF> load fpga c:\users\user\downloads\hostedx40.rbf
Loading fpga from c:\users\user\downloads\hostedx40.rbf...
[DEBUG] Raw FPGA Version: 0x00060000
[DEBUG] Setting integer sample rate: 1000000
[DEBUG] Found r value of: 4
[DEBUG] MSx a + b/c: 316 + 4/5
[DEBUG] MSx a + b/c: 316 + 4/5
[DEBUG] MSx P1: 0x00009c66 (40038) P2: 0x00000002 (2) P3: 0x00000005 (5)
[DEBUG] Calculated samplerate: 1000000 + 0/1
[DEBUG] Writing MS2
[DEBUG] Wrote enable register: 0x03
[DEBUG] Wrote regs[0]: 0x66
[DEBUG] Wrote regs[1]: 0x9c
[DEBUG] Wrote regs[2]: 0x08
[DEBUG] Wrote regs[3]: 0x00
[DEBUG] Wrote regs[4]: 0x00
[DEBUG] Wrote regs[5]: 0x00
[DEBUG] Wrote regs[6]: 0x05
[DEBUG] Wrote regs[7]: 0x00
[DEBUG] Wrote regs[8]: 0x00
[DEBUG] Wrote regs[9]: 0x00
[DEBUG] Wrote r register: 0xc8
[DEBUG] Set actual integer sample rate: 1000000
[DEBUG] Setting integer sample rate: 1000000
[DEBUG] Found r value of: 4
[DEBUG] MSx a + b/c: 316 + 4/5
[DEBUG] MSx a + b/c: 316 + 4/5
[DEBUG] MSx P1: 0x00009c66 (40038) P2: 0x00000002 (2) P3: 0x00000005 (5)
[DEBUG] Calculated samplerate: 1000000 + 0/1
[DEBUG] Writing MS1
[DEBUG] Wrote enable register: 0x01
[DEBUG] Wrote regs[0]: 0x66
[DEBUG] Wrote regs[1]: 0x9c
[DEBUG] Wrote regs[2]: 0x08
[DEBUG] Wrote regs[3]: 0x00
[DEBUG] Wrote regs[4]: 0x00
[DEBUG] Wrote regs[5]: 0x00
[DEBUG] Wrote regs[6]: 0x05
[DEBUG] Wrote regs[7]: 0x00
[DEBUG] Wrote regs[8]: 0x00
[DEBUG] Wrote regs[9]: 0x00
[DEBUG] Wrote r register: 0xc8
[DEBUG] Set actual integer sample rate: 1000000
[DEBUG] x : 4
[DEBUG] nint : 104
[DEBUG] nfrac : 1398101
[DEBUG] freqsel : 25
[DEBUG] reference: 38400000
[DEBUG] freq : 1000000000
[ERROR] Invalid VTUNE value encountered
[DEBUG] x : 4
[DEBUG] nint : 104
[DEBUG] nfrac : 1398101
[DEBUG] freqsel : 25
[DEBUG] reference: 38400000
[DEBUG] freq : 1000000000
[ERROR] Invalid VTUNE value encountered
Done.
bladeRF> set frequency 2000000000

[DEBUG] x : 2
[DEBUG] nint : 104
[DEBUG] nfrac : 1398101
[DEBUG] freqsel : 24
[DEBUG] reference: 38400000
[DEBUG] freq : 1999999999
[ERROR] Invalid VTUNE value encountered
Set RX frequency: 2000000000Hz
[DEBUG] x : 2
[DEBUG] nint : 104
[DEBUG] nfrac : 1398101
[DEBUG] freqsel : 24
[DEBUG] reference: 38400000
[DEBUG] freq : 1999999999
[ERROR] Invalid VTUNE value encountered
Set TX frequency: 2000000000Hz
Top
jynik
Posts: 455
Joined: Thu Jun 06, 2013 8:15 pm

Re: VTUNE error and signal captured with low db value

Post by jynik »

If you end up needing to post back some logs, mind running with bladeRF-cli -i -v verbose, and putting your log into a "code" block (see below)? As verbose mode generates a lot of output, the "code" block will cause all that text to be in a nice compact scrollable box.

Code: Select all

[code]
... log contents ...
[/code]

Good luck!
Jon
Top
frank2013
Posts: 5
Joined: Tue Aug 05, 2014 5:08 pm

Re: VTUNE error and signal captured with low db value

Post by frank2013 »

Tried compiled with latest version. The compilation failed because of error as warning problem but finally fixed by disabling the alert. I dump a screen so that if anybody face same issues he code follow the screen to try the fix.

Still facing the error at the end, any hints to fix it?

[ERROR] Invalid VTUNE value encountered: 0x03

Code: Select all


Microsoft Windows [版本 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\User\BladeRFBuild\bladeRF\build\output\Debug>bladeRF-cli.exe -i -v verbose
[VERBOSE] Using libusb version: 1.0.19.10905
[VERBOSE] Found a bladeRF (based upon VID/PID)
[VERBOSE] Changing to USB alt setting 0
[VERBOSE] Changing to USB alt setting 2
[VERBOSE] Changing to USB alt setting 3
[VERBOSE] Changing to USB alt setting 2
[VERBOSE] Changing to USB alt setting 3
bladeRF>

bladeRF>
bladeRF> info

  Serial #:                 71fc6640a15b03df7cba64fdbc5d56f8
  VCTCXO DAC calibration:   0x88c1
  FPGA size:                40 KLE
  FPGA loaded:              no
  USB bus:                  1
  USB address:              4
  USB speed:                Hi-Speed
  Backend:                  libusb
  Instance:                 0

bladeRF> probe
[VERBOSE] Found bladeRF (based upon VID/PID)
[VERBOSE] Added instance 0 to device list

    Backend:        libusb
    Serial:         71fc6640a15b03df7cba64fdbc5d56f8
    USB Bus:        1
    USB Address:    4

bladeRF> version

  bladeRF-cli version:        0.11.1-git-cef87c9-dirty
  libbladeRF version:         0.16.2-git-cef87c9-dirty

  Firmware version:           1.7.1-git-ca697ee
  FPGA version:               Unknown (FPGA not loaded)

bladeRF> load fpga c:\users\user\downloads\hostedx40.rbf
Loading fpga from c:\users\user\downloads\hostedx40.rbf...
[VERBOSE] Changing to USB alt setting 3
[VERBOSE] Changing to USB alt setting 1
[VERBOSE] Default GPIO value found - initializing device
[VERBOSE] usb_lms_read: 0x40 0x02
[VERBOSE] usb_lms_write: 0x40 0x00
[VERBOSE] usb_lms_read: 0x70 0x01
[VERBOSE] usb_lms_write: 0x70 0x00
[VERBOSE] usb_lms_write: 0x05 0x3e
[VERBOSE] usb_lms_write: 0x47 0x40
[VERBOSE] usb_lms_write: 0x59 0x29
[VERBOSE] usb_lms_write: 0x64 0x36
[VERBOSE] usb_lms_write: 0x79 0x37
[DEBUG] Setting integer sample rate: 1000000
[DEBUG] Found r value of: 4
[DEBUG] MSx a + b/c: 316 + 4/5
[DEBUG] MSx a + b/c: 316 + 4/5
[DEBUG] MSx P1: 0x00009c66 (40038) P2: 0x00000002 (2) P3: 0x00000005 (5)
[DEBUG] Calculated samplerate: 1000000 + 0/1
[DEBUG] Writing MS2
[VERBOSE] usb_si5338_read: 0x26 0x00
[DEBUG] Wrote enable register: 0x03
[VERBOSE] usb_si5338_write: 0x26 0x03
[VERBOSE] usb_si5338_write: 0x4b 0x66
[DEBUG] Wrote regs[0]: 0x66
[VERBOSE] usb_si5338_write: 0x4c 0x9c
[DEBUG] Wrote regs[1]: 0x9c
[VERBOSE] usb_si5338_write: 0x4d 0x08
[DEBUG] Wrote regs[2]: 0x08
[VERBOSE] usb_si5338_write: 0x4e 0x00
[DEBUG] Wrote regs[3]: 0x00
[VERBOSE] usb_si5338_write: 0x4f 0x00
[DEBUG] Wrote regs[4]: 0x00
[VERBOSE] usb_si5338_write: 0x50 0x00
[DEBUG] Wrote regs[5]: 0x00
[VERBOSE] usb_si5338_write: 0x51 0x05
[DEBUG] Wrote regs[6]: 0x05
[VERBOSE] usb_si5338_write: 0x52 0x00
[DEBUG] Wrote regs[7]: 0x00
[VERBOSE] usb_si5338_write: 0x53 0x00
[DEBUG] Wrote regs[8]: 0x00
[VERBOSE] usb_si5338_write: 0x54 0x00
[DEBUG] Wrote regs[9]: 0x00
[DEBUG] Wrote r register: 0xc8
[VERBOSE] usb_si5338_write: 0x21 0xc8
[DEBUG] Set actual integer sample rate: 1000000
[DEBUG] Setting integer sample rate: 1000000
[DEBUG] Found r value of: 4
[DEBUG] MSx a + b/c: 316 + 4/5
[DEBUG] MSx a + b/c: 316 + 4/5
[DEBUG] MSx P1: 0x00009c66 (40038) P2: 0x00000002 (2) P3: 0x00000005 (5)
[DEBUG] Calculated samplerate: 1000000 + 0/1
[DEBUG] Writing MS1
[VERBOSE] usb_si5338_read: 0x25 0x00
[DEBUG] Wrote enable register: 0x01
[VERBOSE] usb_si5338_write: 0x25 0x01
[VERBOSE] usb_si5338_write: 0x40 0x66
[DEBUG] Wrote regs[0]: 0x66
[VERBOSE] usb_si5338_write: 0x41 0x9c
[DEBUG] Wrote regs[1]: 0x9c
[VERBOSE] usb_si5338_write: 0x42 0x08
[DEBUG] Wrote regs[2]: 0x08
[VERBOSE] usb_si5338_write: 0x43 0x00
[DEBUG] Wrote regs[3]: 0x00
[VERBOSE] usb_si5338_write: 0x44 0x00
[DEBUG] Wrote regs[4]: 0x00
[VERBOSE] usb_si5338_write: 0x45 0x00
[DEBUG] Wrote regs[5]: 0x00
[VERBOSE] usb_si5338_write: 0x46 0x05
[DEBUG] Wrote regs[6]: 0x05
[VERBOSE] usb_si5338_write: 0x47 0x00
[DEBUG] Wrote regs[7]: 0x00
[VERBOSE] usb_si5338_write: 0x48 0x00
[DEBUG] Wrote regs[8]: 0x00
[VERBOSE] usb_si5338_write: 0x49 0x00
[DEBUG] Wrote regs[9]: 0x00
[DEBUG] Wrote r register: 0xc8
[VERBOSE] usb_si5338_write: 0x20 0xc8
[DEBUG] Set actual integer sample rate: 1000000
[VERBOSE] ---- Frequency ----
[VERBOSE]   x        : 4
[VERBOSE]   nint     : 104
[VERBOSE]   nfrac    : 1398101
[VERBOSE]   freqsel  : 0x25
[VERBOSE]   reference: 38400000
[VERBOSE]   freq     : 1000000000
[VERBOSE] usb_lms_read: 0x09 0x40
[VERBOSE] usb_lms_write: 0x09 0x45
[VERBOSE] usb_lms_read: 0x15 0xb1
[VERBOSE] usb_lms_read: 0x08 0x00
[VERBOSE] usb_lms_read: 0x46 0x00
[VERBOSE] usb_lms_write: 0x15 0x95
[VERBOSE] usb_lms_write: 0x10 0x34
[VERBOSE] usb_lms_write: 0x11 0x15
[VERBOSE] usb_lms_write: 0x12 0x55
[VERBOSE] usb_lms_write: 0x13 0x55
[VERBOSE] usb_lms_read: 0x16 0x8c
[VERBOSE] usb_lms_write: 0x16 0x8c
[VERBOSE] usb_lms_read: 0x17 0xe0
[VERBOSE] usb_lms_write: 0x17 0xe0
[VERBOSE] usb_lms_read: 0x18 0x40
[VERBOSE] usb_lms_write: 0x18 0x40
[VERBOSE] usb_lms_read: 0x19 0x94
[VERBOSE] usb_lms_write: 0x19 0xa0
[VERBOSE] usb_lms_read: 0x1a 0xc3
[ERROR] Invalid VTUNE value encountered: 0x03
[VERBOSE] usb_lms_read: 0x09 0x45
[VERBOSE] usb_lms_write: 0x09 0x40
Error: An unexpected error occurred
bladeRF>
Top
frank2013
Posts: 5
Joined: Tue Aug 05, 2014 5:08 pm

Re: VTUNE error and signal captured with low db value

Post by frank2013 »

I checked the document:
http://www.limemicro.com/download/LMS60 ... -1.1r1.pdf

And find that address 0x1a with default value 0x03

Tx: 0x1A, Rx: 0x2A
7 6 5–0
VTUNE_H (Read Only): Value from Vtune comparator
VTUNE_L (Read Only): Value from Vtune comparator
Reserved
000011 –(default)
Default: “00000011”

Should I modify the lms.c or lms_reg_info.c value to recompile?
Top
jynik
Posts: 455
Joined: Thu Jun 06, 2013 8:15 pm

Re: VTUNE error and signal captured with low db value

Post by jynik »

The VTUNE_H and VTUNE_L are registers used during an algorithm to tune the device to a requested frequency. They essentially mean "too high or too low," if I remember correctly.

From what I've heard, you're waiting on a replacement board to address this issue, correct? Did you receive that yet?
Top
frank2013
Posts: 5
Joined: Tue Aug 05, 2014 5:08 pm

Re: VTUNE error and signal captured with low db value

Post by frank2013 »

Not yet received. Waiting and waiting. But I've my
XB200 arrived :P :P
Top
frank2013
Posts: 5
Joined: Tue Aug 05, 2014 5:08 pm

Re: VTUNE error and signal captured with low db value

Post by frank2013 »

Just get update on the repaired board. Thx very much for all your support :D :D
Top
Post Reply

Return to “Troubleshooting”