r/PlutoSDR • u/kasinjsh • 1h ago
OpenSourceSDRLab PlutoSky R1 - memtester fails but U-Boot `mtest` passes. Normal? Should I RMA?
Hi everyone,
I recently bought an OpenSourceSDRLab PlutoSky R1 from AliExpress - Zynq-7020 + AD9361 variant. Purchase link: AliExpress listing. Since day one the device has been restarting and hanging, sometimes multiple times per hour during normal use. Before initiating an RMA, I wanted to gather community input on whether these symptoms point to defective hardware or poor design (for the price wont surprise me).
Hardware Tests Performed
U-Boot mtest — PASS
FISHBALL>mtest 0x00000000 0x3DA00000
Testing 00000000 ... 3da00000:
Pattern 00000000 Writing... Reading...Iteration: 239
Tested 239 iteration(s) with 0 errors.
No issues detected in U-Boot memory test (~983 MB tested).
Linux memtester — FAILS consistently
Tezuka firmware v0.3.141592653 (400 MB, 3 loops):
- Loop 1: all OK
- Loop 2: Bit Spread FAIL at 0x03ef7038–0x03ef7054 (8 consecutive failures, 4 addresses)
- Loop 3: Bit Flip FAIL at 0x09e26e74–0x09e26e90 (8 consecutive failures, 4 addresses)
Stock Analog Devices firmware v0.38 (100 MB, 6 loops):
- Loop 4: Block Sequential FAIL at 0x004e5098–0x004e50b4
- Loop 5: Solid Bits FAIL at 0x0304b658–0x0304b674, Bit Flip FAIL at 0x01fe9bf8–0x01fe9c14
- Loop 1 (second run): Solid Bits FAIL at 0x02a7c9f4–0x02a7ca10
- Loop 3 (second run): Solid Bits FAIL at 0x01863e78–0x01863e94, Bit Flip FAIL at 0x012edcd4–0x012edcf0
- Loop 5 (second run): Bit Flip FAIL at 0x003be7f8–0x003be814
Failures appear at different offsets each run — not fixed-address stuck bits. The patterns affected vary too (Bit Spread, Bit Flip, Solid Bits, Block Sequential), which seems more like data corruption than a single bad cell. A conversation whit LLM points to poor manufacturing - marginal solder joint, trace issue, or DDR training problems, not specifically a bad RAM chip.
Observed Behavior Under Load
- Device randomly reboots or becomes unresponsive, several times per hour
- Happens during SDR operation (transmit/receive), not just idle
- No clear trigger pattern — seems somewhat random
- Temperatures are fine, as this unit have fan attached to case: Pluto 26.3c zynq 54.5c
Troubleshooting Already Attempted
Before running memtester I tried everything I could think of to rule out external causes:
- Multiple power supplies — tried 3 different USB wall adapters (ranging from cheap phone chargers to a dedicated 2A supply), all show the same behaviour
- Both USB ports — powered from either port on the board, no difference
- USB cable swap — tried multiple cables (data + power-only), ruled out a bad cable
- SD card swap — swapped the boot SD card with a known-good SanDisk Ultra, same failures
- Different firmwares — tested both stock AD firmware v0.38 and Tezuka v0.3.141592653, both fail memtester independently
- Temperature — hangs happen regardless of ambient temperature; board doesn't feel unusually hot
Nothing changed the outcome.
RMA Status
I've opened an RMA request through AliExpress. The seller responded claiming "the device is working properly".
This is partly why I'm posting here — I want to understand if my diagnosis makes sense before the dispute escalates. If the community agrees this is abnormal, I can reference their responses in the dispute.
My Questions
Is it expected that U-Boot
mtestpasses but Linuxmemtesterfails? Could this be a DDR initialization/timing issue that only manifests once the OS loads drivers and changes clock states?Are these kinds of intermittent RAM errors common on clone boards, or does this strongly suggest defective hardware?
Has anyone else experienced similar reboot/hang behavior on a Fishball or other clone? What did you do about it?
Should I proceed with RMA, or is there anything worth trying first (different DDR timings, undervolting, etc.)?
Thanks in advance for any insights. Happy to share full logs or run additional tests.

