Skip to content

Maia SDR Pluto firmware v0.5.0
Compare
Choose a tag to compare
@daniestevez daniestevez released this 23 Feb 18:49
· 2 commits to maia-sdr since this release
maia-sdr-v0.5.0
This tag was signed with the committer’s verified signature.
daniestevez Daniel Estévez
GPG key ID: B45C2B937941C329
Learn about vigilant mode.
790fb89

Changelog

Added

  • Update Maia SDR to v0.7.0. Adds IQEngine to view IQ recordings done in the DDR.

Potential problems

Updates from an older version of Maia SDR to Maia SDR v0.5.0 by copying pluto.frm to the USB mass-storage method will fail and leave the device in a state that can only be recovered using DFU. This problem happens only when flashing from an older version of Maia SDR. It does not happen when flashing from the ADI firmware.

The problem is that the ADI update.sh script that is used to perform the update copies the file pluto.frm in the ramfs. Since this Maia SDR firmware is slightly larger than the previous ones, this will lead to an out-of-memory error during the update, leaving the update partially written to flash.

Any of the following workarounds can be used to solve this problem (each is a complete solution; they are not steps in the same solution):

  1. Flash the Maia SDR v0.5.0 firmware using DFU instead of the USB mass-storage method. To do this, the device must be power-cycled while pressing the DFU button, and then dfu-util -a firmware.dfu -D pluto.dfu must be run. After this finishes, the device must be power-cycled again.
  2. Revert first to the ADI firmware by using the ADI pluto.frm, and then flash Maia SDR v0.5.0 while running the ADI firmware. This will not lead to the out-of-memory error.
  3. Login into the device using ssh or serial and kill the maia-httpd process (locate its PID with ps) and run rm -rf /root/* to free up space on the ramfs. Then perform the update using USB mass-storage.

In the Maia SDR v0.5.0 firmware, the update.sh script has been modified to avoid copying the pluto.frm file, so flahsing firmware while running Maia SDR v0.5.0 will not lead to this problem (for instance, when updating to future versions of Maia SDR).

Assets 8