RPI3 Heat Sinks on Limesdr-mini

Projects LimeSDR
1

2018-10-09 Raspbian Stretch Lite GQRX_Testing_800MHz_800MHzAntenna directly connected to laptop usb 3.0 port
‘gqrx -r’
“soapy=0,driver=lime”
gains = 9, 5 and -8
21C laser aimed at wall. current temp outside is 17C/61F
installed rpi3 stock heatsinks and stock pad (no fan or wind) numbers are the highest i seen after watching for a bit).
started at 10msps and worked my way toward 65msps. warmed up for 10mins then each time i went up 10msps ran 5mins each.
aimed laser in middle of heatsinks (topside of board). big chip first then little chip

10msps FM Stereo fft_8192 lap_cpu_90% Temp_BigLil Temp_small_left_Right
10msps dmod_off fft_8192 lap_cpu_29% Temp_50C_47C Temp_42C_53C
20msps dmod_off fft_8192 lap_cpu_42% Temp_51C_48C
30msps dmod_off fft_8192 lap_cpu_61% Temp_50C_47C
40msps dmod_off fft_8192 lap_cpu_68% Temp_51C_46C
50msps dmod_off fft_8192 lap_cpu_67% Temp_50C_47C
60msps dmod_off fft_8192 lap_cpu_69% Temp_50C_47C Temp_43C_53C

Why are the temps not really moving when i increase sample rate?
where is most the heat generated?
i havent checked the bottom side of board and all along the metal shielding on top its 38C to 42C

CdXKph0.jpg4656×3492

need to do same tests without heat sinks but not sure if i want to take them off if its working well

one more thing i had these on the rpi3 and just pulled em off after i heated the pi3 up.
so its the same sticky.
i have some Arctic Silver but not sure if i want to use it if it dont do no good when i change sample rate from 10msps to 60msps
i use a laser temp gun and its accurate with a couple degrees F

2

Something went wrong right after these tests.
i dont get any lights on the limesdr-mini
this is what SoapySDRUtil --info, --find and --probe

en1gma@en1gma–lap:~$ SoapySDRUtil --info
######################################################

Soapy SDR – the SDR abstraction library

######################################################

Lib Version: v0.6.1-2
API Version: v0.6.0
ABI Version: v0.6
Install root: /usr
Search path: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6
Search path: /usr/local/lib/x86_64-linux-gnu/SoapySDR/modules0.6
Search path: /usr/local/lib/SoapySDR/modules0.6
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libHackRFSupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libLMS7Support.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libRedPitaya.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libairspySupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libaudioSupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libbladeRFSupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libmiriSupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libosmosdrSupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libremoteSupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/librfspaceSupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/librtlsdrSupport.so
Module found: /usr/lib/x86_64-linux-gnu/SoapySDR/modules0.6/libuhdSupport.so
Loading modules… linux; GNU C++ version 7.3.0; Boost_106501; UHD_003.010.003.000-0-unknown

done
Available factories…airspy, audio, bladerf, hackrf, lime, miri, null, osmosdr, redpitaya, remote, rfspace, rtlsdr, uhd,
en1gma@en1gma–lap:~$

en1gma@en1gma–lap:~$ SoapySDRUtil --find
######################################################

Soapy SDR – the SDR abstraction library

######################################################

linux; GNU C++ version 7.3.0; Boost_106501; UHD_003.010.003.000-0-unknown

Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Found device 0
default_input = True
default_output = True
device_id = 0
driver = audio
label = hw:HDA Intel PCH,0

Found device 1
default_input = False
default_output = False
device_id = 1
driver = audio
label = default

Found device 2
addr = 24607:1027
driver = lime
label = LimeSDR Mini [USB 3.0] 1D3BD0C4F0CDFF
media = USB 3.0
module = FT601
name = LimeSDR Mini
serial = 1D3BD0C4F0CDFF

en1gma@en1gma–lap:~$

en1gma@en1gma–lap:~$ SoapySDRUtil --probe
######################################################

Soapy SDR – the SDR abstraction library

######################################################

Probe device
linux; GNU C++ version 7.3.0; Boost_106501; UHD_003.010.003.000-0-unknown

Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

– Device identification

driver=Audio
hardware=Audio
device_id=0
origin=https://github.com/pothosware/SoapyAudio

– Peripheral summary

Channels: 1 Rx, 0 Tx
Timestamps: NO
Other Settings:
* Stereo Sample Offset - Offset stereo samples for off-by-one audio inputs.
[key=sample_offset, default=0, type=string, options=(-2, -1, 0, 1, 2)]
* Rig Control - Select hamlib rig control type.
[key=rig, type=string, options=(2901, 2516, 2517, 2513, 2518, 508, 506, 505, 504, 514, 503, 515, 502, 501, 513, 516, 1701, 2506, 2503, 2303, 2304, 902, 903, 221, 229, 238, 2501, 2507, 2512, 2301, 236, 2515, 1, 2, 354, 302, 303, 372, 304, 306, 307, 360, 355, 309, 310, 311, 312, 370, 313, 361, 314, 315, 316, 373, 319, 320, 321, 322, 367, 323, 346, 324, 326, 327, 347, 357, 363, 328, 329, 362, 330, 345, 356, 331, 332, 334, 344, 368, 365, 335, 3001, 3003, 3002, 402, 401, 403, 404, 336, 358, 340, 337, 341, 338, 339, 343, 366, 369, 342, 371, 605, 606, 607, 2511, 1801, 215, 233, 217, 219, 220, 223, 226, 234, 227, 230, 225, 214, 202, 203, 228, 201, 204, 216, 231, 237, 224, 205, 206, 207, 208, 209, 210, 222, 211, 213, 239, 1004, 374, 2514, 353, 352, 2801, 2401, 1105, 1103, 804, 2702, 2701, 2502, 232, 1404, 1402, 2509, 2201, 364, 351, 1603, 1612, 1604, 1605, 1607, 1602, 1601, 1608, 1609, 1611, 1613, 802, 806, 801, 803, 812, 810, 811, 133, 2601, 2602, 1204, 1501, 1502, 1503, 1504, 1505, 1506, 1507, 1509, 117, 119, 118, 121, 103, 124, 134, 129, 127, 110, 105, 106, 107, 109, 120, 111, 101, 122, 115, 123, 113, 114, 128, 131, 116, 135, 132, 130, 104, 125, 126, 2508)]
* Rig Serial Rate - Select hamlib rig serial control rate.
[key=rig_rate, default=57600, type=string, options=(1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200, 128000, 256000)]
* Rig Serial Port - hamlib rig Serial Port dev / COMx / IP-Address
[key=rig_port, default=/dev/ttyUSB0, type=string]

– RX Channel 0

Full-duplex: YES
Supports AGC: YES
Stream formats: CS8, CS16, CF32
Native format: CS16 [full-scale=65536]
Stream args:
* Channel Setup - Input channel configuration.
[key=chan, default=mono_l, type=string, options=(mono_l, mono_r, stereo_iq, stereo_qi)]
Antennas: RX
Full gain range: [0, 0] dB
Full freq range: [0, 6000] MHz
RF freq range: [0, 6000] MHz
Sample rates: 0.0441, 0.048, 0.096, 0.192 MSps

en1gma@en1gma–lap:~$

‘gqrx -r’ with selecting limesdr-mini and i set device string to “soapy=0,driver=0”

en1gma@en1gma–lap:~$ gqrx -r
linux; GNU C++ version 7.3.0; Boost_106501; UHD_003.010.003.000-0-unknown

Controlport disabled
No user supplied config file. Using “default.conf”
“/home/en1gma/.config/gqrx/default.conf” deleted
gr-osmosdr v0.1.x-xxx-xunknown (0.1.5git) gnuradio 3.7.11
built-in source types: file osmosdr fcd rtl rtl_tcp uhd plutosdr miri hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp
FM demod gain: 3.05577
Resampling audio 96000 -> 48000
IQ DCR alpha: 1.04166e-05
Using audio backend: auto
BookmarksFile is /home/en1gma/.config/gqrx/bookmarks.csv
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

RtApiAlsa::getDeviceInfo: snd_pcm_open error for device (hw:0,0), Device or resource busy.

Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

RtApiAlsa::getDeviceInfo: snd_pcm_open error for device (hw:0,0), Device or resource busy.

getDeviceList : Available input devices:
“Ettus SOAPY”
“Ettus SOAPY”
“Ettus SOAPY (LimeSDR Mini) 1D3BD0C4F0CDFF”
“PlutoSDR”
“RFSPACE SDR-IQ Receiver”
“RFSPACE SDR-IP Receiver”
“RFSPACE NetSDR Receiver”
“RFSPACE Cloud-IQ Receiver”
“hw:HDA Intel PCH,0”
“default”
“LimeSDR Mini [USB 3.0] 1D3BD0C4F0CDFF”
“RTL-SDR Spectrum Server”
“Red Pitaya Transceiver Server”
“Complex Sampled (IQ) File”
Loading configuration from: “default.conf”
Configuration file: “/home/en1gma/.config/gqrx/default.conf”
No change in output device:
old:
new:
New FFT rate: 25 Hz
Requested bandwidth: 0 Hz
Actual bandwidth : 0 Hz
setFreqCorr : 0 ppm
New LNB LO: 0 Hz
updateHWFrequencyRange failed fetching new hardware frequency range
New mode index: 2
Filter preset for mode 2 LO: -5000 HI: 5000
Generating taps for new filter LO:-5000 HI:5000 TW:2000 Taps: 115
setFftRate to “25 fps”
New FFT rate: 25 Hz
New FFT rate: 25 Hz
setFftSize to “8192”
New FFT rate: 25 Hz
Launching I/O device editor
firstTimeConfig
CIoConfig : Available output devices:
0 : “Built-in Audio Analog Stereo”
New input device selected: 3
Label: “LimeSDR Mini [USB 3.0] 1D3BD0C4F0CDFF”
Devstr: “addr=24607:1027,driver=lime,media=‘USB 3.0’,module=FT601,name=‘LimeSDR Mini’,serial=1D3BD0C4F0CDFF,soapy=2”
saveConfig
Loading configuration from: “/home/en1gma/.config/gqrx/default.conf”
Configuration file: “/home/en1gma/.config/gqrx/default.conf”
gr-osmosdr v0.1.x-xxx-xunknown (0.1.5git) gnuradio 3.7.11
built-in source types: file osmosdr fcd rtl rtl_tcp uhd plutosdr miri hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp
[INFO] Make connection: ‘LimeSDR Mini [USB 3.0] 1D3BD0C4F0CDFF’
[ERROR] Read(64 bytes) failed
[ERROR] Read(64 bytes) failed
[ERROR] Read(64 bytes) failed
[ERROR] Write(64 bytes) failed
[ERROR] Write(64 bytes) failed
[ERROR] Write(64 bytes) failed
[INFO] Device name: UNKNOWN
[INFO] Reference: -1e-06 MHz
[ERROR] Write(64 bytes) failed
[ERROR] Write(64 bytes) failed

just repeats this over and over. all while limesdr has no power light
tested it on my rpi3 and it also has no power light when connected to it

tested with LimeSuiteGUI too
when i try to connect it says this
21:12:42] INFO: Disconnected control port
[21:12:49] ERROR: Read(64 bytes) failed
[21:12:49] ERROR: Read(64 bytes) failed
[21:12:49] ERROR: Read(64 bytes) failed
[21:12:49] ERROR: Write(64 bytes) failed
[21:12:53] ERROR: Write(64 bytes) failed
[21:12:53] ERROR: Write(64 bytes) failed
[21:12:53] ERROR: Write(64 bytes) failed
[21:12:53] INFO: Connected Control port: UNKNOWN FW:0 HW:0 Protocol:0 GW:0.0 Ref Clk: -0.00 MHz

en1gma@en1gma–lap:~$ LimeQuickTest
[ TESTING STARTED ]
->Start time: Mon Oct 22 21:21:03 2018

Read(64 bytes) failed
Read(64 bytes) failed
Read(64 bytes) failed
Write(64 bytes) failed
->Device: LimeSDR Mini, media=USB 3.0, module=FT601, addr=24607:1027, serial=1D3BD0C4F0CDFF
Serial Number: 1D3BD0C4F0CDFF
Write(64 bytes) failed
Write(64 bytes) failed
Failed to connect
libusb: warning [libusb_exit] application left some devices open

en1gma@en1gma–lap:~$

please help

3

Hi,

According to my measurements, the peak temperature (near FPGA) rises to ~80C on a stock mini when receiving 30MHz bandwidth. These small heat sinks are not going to help too much, you need to slam more metal to it.

You probably heat-damaged your board, maybe you can revive it by manually reprogramming the FPGA…

4

do you think you might be able to help me manually reprogram it?

it happened when running gqrx at actually 10msps with heat sinks off.
i was going to repeat all tests with no heat sinks and it just went out but while gqrx was running

5

Take a look:

7

It is likely that you have caused unrecoverable damage to your board. But there is a small chance that only the FPGA configuration suffered, that’s why i suggested to reprogram it manually - and for that you need to use the USB-Blaster.

1 Like
8

ok im gonna order one off amazon.

do you think this will be compatible?

what makes you think what i did makes the board unrecoverable?
i can still talk to it with LimeUtil --find and SoapySDRUtil --find
even Limesuitegui will connect to it. i can “Read Temp” and "[17:20:08] INFO: Connected Control port: UNKNOWN FW:0 HW:0 Protocol:0 GW:0.0 Ref Clk: -0.00 MHz
“.
it is in some kind of a loop in limesuitegui because if i click a “button” like Read Temp” it takes a certain amount of time to actually execute it. when it gets to a certain point in the loop and it tries to execute the “button” command and usually replies with “[17:20:08] ERROR: Read(64 bytes) failed”

No LED lights on board show up no matter what.

if board is broken what part you think it is?
LM7 chip?

9

@en1gma
In the following post it was the FX3 chip that needed to be reworked: LimeSDR-USB gateware version is not recognizeable (temperature related)

1 Like
10

Actually, you should start by measuring the board voltages. There are test points on the board labeled VCC3P3 and VCC1P8.

1 Like
11

Awesome.
im descent with a volt meter.
can you link me to where the info is to the test points and voltage they should be and hopefully isolate the problem down to the area if a test point isnt measuring what it should be.
thanks

12

Here is the PCB drawing: LimeSDR_Mini_1v2_PCB_Drawings_r1.PDF
here is the schematic: LimeSDR_Mini_1v2_schematic_r1.PDF

But this version from the Wiki is a bit more readable:

image
image

IC12 IC Switching regulator (1.8V)
IC13 IC Switching regulator (3.3V)
IC14 IC Linear regulator (2.5V)
IC15 IC Linear regulator (12.5V)
IC16 IC Linear regulator (1.4V)
https://wiki.myriadrf.org/LimeSDR-Mini_v1.2_hardware_description
1 Like
13

mine says its hardware v1.1
should the voltages be the same as listed above?

14

IC 15 and IC 16 aren’t in the same place between the v1.1 and the v1.2 PCB.
Here is the PCB drawing: LimeSDR_Mini_1v1_PCB_Drawings_r0.PDF
here is the schematic: LimeSDR_Mini_1v1_schematic_r1.PDF

Which makes testing the voltage rails even easier. LimeSDR-Mini v1.1 has 1.8V, 3.3V and 2.5V. The 1.8V and 3.3V test points are labeled on the board. The 2.5V is relabeled as VDIO_LMS_FPGA and VDIO_LMS on the schematic; the FPGA and the LMS7002M and the LMS EEPROM all connect to 2.5V.

15

great info! thanks very much,
will be checking this out later tonight as i got a lil work to do right now.
hope my board isnt fried.
was really learning alot about RF.
was just about ready to schedule a technician test.
:frowning:

16

i could find 5.0v, 3.3v, 2.5v but i dont think i can get 1.8v
could you tell me where to put my leads to my volt meter?
if the voltage regulator for 1.8v isnt working what are my options?

17

Look at the holes in the board labeled FPGA JTAG. 1.8V should be second from the right.

18

thats what i was afraid of.
the 1.8v on edge connector holes on top and bottom show .14v or something
i think on the edge that has the most holes the 1.8v is next to the 5v and the opposie side the 1.8v is next to the 3.3v

if those are supposed to be 1.8v while connected to a computers usb 3.0 port they ate not.
i get .14v

the altera chip programmer wont help me?

19

the altera chip programmer wont help me?

I dont think so…:frowning:

So, two possible problems now:

  1. The 1.8V regulator is broken, thus not providing enough current
  2. Something feeding from 1.8V is broken

You could do some debugging to find out, but this now involves soldering off components and/or breaking the PCB rails. Another option would be to blindly replace the 1.8V regulator.
But i guess a cheapest way (if you count the work hours) is to just buy a new Mini.

20

crowdsupply cant fix?

21

No, there isn’t a repair service, as it wouldn’t prove cost effective with a board using this sort of technology.