New features

Two more of hardware platforms (SoCs) that the SoftRF technology is able to operate on:

• NXP Semiconductors LPC4320          - dual ARM Cortex-M4F and M0 cores
• STMicroelectronics     STM32WLE5   - ARM Cortex-M4F core with sub-1Ghz radio

NXP Semiconductors LPC4320

• very first Release for SoftRF ES Edition

• base component: HackRF One
  
• modes: Normal (default)
• hardware:
  • NXP Semiconductors LPC4320 MCU
  • GNSS: optional Ublox or MTK based module
  • Radio: built-in Software Defined Radio (SDR)
  • Output:
         default: USB CDC ACM
         optional: UART 38400, 8N1
         optional: Wi-Fi UDP
         optional: Bluetooth SPP
  • Display:
         optional: 3.2" TFT ( PortaPack H2+ ) or
         optional: 0.96" I²C OLED
  • Sensor(s):
         optional: Bosch BMP280

STMicroelectronics STM32WLE5

• very first Release for SoftRF Balkan Edition
• base component: Olimex LoRa-STM32WL-DevKit
  

• modes: Normal (default)
• hardware:
  • STMicroelectronics STM32WLE5 SoC
  • GNSS: external Ublox-7 module
  • Radio: built-in Semtech SX1262
  • Output:
         default: USB CDC ACM
  • Display:
         optional: 0.96" I²C OLED
  • Sensor(s):
         air pressure:      Bosch BME280
         magnetometer: STMicroelectronics IIS2MDCTR
• certificate: CE

Major improvements

Common

• apply NMEA compliance filter to ADS-B callsign
• certain improvements of 'legacy' radio protocol implementation
• better NMEA data compliance to FTD-12/14 specs
• Ublox M9 and M10 GNSS modules detect logic
• update of device Id mapper
• PGRMZ NMEA sentence is better compliant to Garmin specs

ESP32

• build with most recent Arduino Core for ESP32 2.0.5 ( when necessary )
• support for AXP2101 PMU ( T-Beam V1.2 )
• support for ESP32-S3 SoC
• emit traffic alert events over Bluetooth LE MIDI
• build of D1090 input data parser ( ESP32-S2/3 only )
• fix for OTA firmware update function ( with espota.py )
• compute maximum sketch space applicable for Wi-Fi OTA firmware update

nRF52

• MPU9250 IMU sensor detect logic
• 'G load' meter function and the EPD screen
• emit traffic alert events over Bluetooth LE MIDI
• build of GxEPD2 driver for DEPG0150BN e-Paper display
• fix of improper date in PCF8563 RTC library
• fix for improper aircrafts data scroll function ( by the sensor touch )

CC13x2

• support for Texas Instruments CC1312R SoC ( Ebyte E70-900M14S1B module )

STM32

• build with most recent Arduino Core for STM32 2.3.0 ( when necessary )
• support for STM32WLE5 SoC ( BB-STM32WL , Ebyte E77 , Seeed E5 , AcSiP ST50H , RAK 3172 )
• update of RTC and LowPower libraries

RP2040

• transition on Arduino Core for RP2040 2.2.2

SAMD21

• USB to Bluetooth adapter

BCM283X

• receive of 1090 MHz ES (ADS-B) air traffic with RTL, HackRF One or MIRI SDR USB devices
• make use of 'libmodes' library to demodulate and decode 1090 ES (ADS-B) air traffic
• D1090 input data parser

LPC4320

• make use of 'libmodes' library to demodulate and decode 1090 ES (ADS-B) air traffic

Please, read commits history for more information.

Known issues

• same that previous Release 1.1 has ;
• USB data I/O may fail on ESP32-S3 platform. It may cause a complete stop of NMEA output. It may cause a system reboot. Thus, use with caution.

Binary downloads and flashing instructions

WARNING

1. This upgrade may reset your SoftRF settings down to factory default values. Please, follow these "backup and restore" procedures prior to executing the update
2. ESP32 only: you may try "Web update" method if your current firmware version is rc7-9 or 1.0-1, otherwise do:
   • follow First-time firmware installation procedure instructions instead, and
   • make full flash ERASE prior to firmware write operation, and
   • disconnect any of I2C devices from ESP32's GPIO2 pad. See this ticket for details.
3. S76G only: follow these instructions to update your Dongle Edition firmware. It is also recommended to reset your SoftRF Dongle settings back to factory default values by following this procedure.

Prime MkII, Badge or Dongle owners! I will reject any claims if you, by any reason, will fail to upgrade or fail to recover after un-successful update!
If you are not sure that you can manage the update successfully - think about to stay on 1.1 or to buy a new board with pre-installed 1.2.

Source code build instructions