Radios: hardware survey and port plan

Status: research, 2026-10-10. This page collects the main chips of every radio RadioFoundry supports or plans to support, plus close relatives, from public sources only. It also says which RadioFoundry platforms and drivers each radio could reuse and suggests an order for the ports. Register-level facts live in the per-radio specs (hardware-dm1701.md, hardware-dm32.md, hardware-md380.md, hardware-mduv380.md, hardware-gd88.md, hardware-db25d.md, hardware-dm1801pro.md, hardware-anytone.md). This page is the overview.

Facts are not copyrightable. Claims come from public sources (manufacturer pages, FCC filings, datasheets, retailer listings) or from measurements on the radio. A value marked (unverified) is reported by a retailer, review or forum and not confirmed on a radio, in a datasheet or in a filing; ? means not found or contradictory. Check both before a port starts.

FCC internal photos. FCC IDs are listed per radio, but the fccid.io and fcc.report exhibit PDFs couldn't be fetched by script for this survey. Opened in a browser, they download fine. So far the DB25-D PRO, DB40-D, DM-1801 (2026) and DR-1801 chips below are confirmed from FCC photos. Reading the internal-photo exhibits by hand is the cheapest way to confirm the unverified chips, and it should happen before a port starts.

Summary table

The Port column says how far each radio's port is. A row that names a board in boards/ gets its cell from the board's [status] (tools/boards.py docs writes it). Every other row's cell is one of Planned, Planned, hardware needed, In progress, #N (the pull request) or Not planned, then an optional . note. The README's radio table, the user manual's planned radios and the web site list the planned and in-progress rows with that note, so it is written for readers of all three (tools/registry_docs.py).

An in-progress cell can say what the pull request already has before the note: In progress, #N, builds, host tests, on the radio, any of the three. The README marks each ◐ until the board merges and its [status] takes over.

Per-radio notes

Baofeng DM-1701 / Retevis RT84

• Bands 136–174 / 400–480 MHz, 1/2/5 W, 1.77" color TFT, no GPS (baofengradio.com). A search snippet from the same site said 400–520 MHz; the product page itself says 400–480 MHz.
• FCC ID 2AJGM-DM1701, granted 2018-12-22. Internal photos exist but are too low resolution to read parts (fccid.io).
• STM32F405 + HR_C6000 + AT1846S + 160x128 color LCD + 16 MB SPI NOR: confirmed by our own bring-up (hardware-dm1701.md). No public teardown names the DM-1701's chips. Public sources only say it shares the MD-UV380 platform (unverified) (w0chp supported radios).
• Programming: USB D+/D- on the K-plug straight to the MCU. D+ and D- are swapped compared with the RT3S cable (unverified).
• Vendor images are wrapped (the format is in hardware-dm1701.md).
• Reuses platform/stm32f4, drivers/modem/hrc6000, drivers/rf/at1846s, drivers/display/st7735, drivers/flash/spi_nor, drivers/input/keymatrix.

The Ailunce HD1 is not a DM-1701 relative. It's a GD-77 class radio: MK22FN512, HR_C6000, AT1846S, 160x128 color TFT, 25Q80BV + AT24C512, ST-26-U7L GPS, serial YMODEM bootloader over a PL2303 cable (unverified). A forum thread reports a 2023+ HD1 v2 on the HR_C7000, but posters contradict each other .

TYT MD-UV380 / MD-UV390 / Retevis RT3S

• STM32F405VG (Cortex-M4F, 1 MB flash, 192 KB SRAM including 64 KB CCM st.com), HR_C6000, AT1846S, HX8302A display controller, 25Q128FV SPI flash, JS-H210 GPS on G models (unverified). 160x128 color TFT. The vendor bootloader takes the first 48 KB of internal flash, and the app starts at 0x0800C000 (unverified).
• The AT1846S is on I2C. The MD-UV390 Plus (10 W) board layout differs somewhat (unverified).
• The MD-UV390 is the same radio in a waterproof case. GPS is a hardware option; GPS firmware doesn't add GPS to a non-GPS radio (unverified).
• FCC IDs POD-MDUV380 (granted 2018-10-19) and POD-MDUV390 (unverified).
• DFU entry: hold PTT and the button above it at power-on, see hardware-mduv380.md.
• A repair-guide snippet claims the dual-band radios use an NXP MK22. That contradicts every other source and is almost certainly wrong.
• RadioFoundry: the same board family as the DM-1701 (hardware-mduv380.md lists every difference). It needs a key map, no LCD row offset and its own panel-type table, battery and volume ADC scaling, power tables (5 W and Plus 10 W, whose PA band select and backlight pins are swapped), its own DFU key and GPS on USART1 (PA10, power PA9; an earlier note here said USART3, which is the MD-380's). No new drivers.
• Codec: the TYT 19.26 files (V/D non-GPS, P/S GPS) carry the same codec library as the DM-1701, with the same entry offsets, in the same flash sectors (codec-mduv380.md).

TYT MD-9600 / Retevis RT90

• STM32F405VG, HR_C6000 (bit-banged SPI), two SKY72310 PLLs (one VHF, one UHF) with a 16.8 MHz TCXO "at least in the older models", ST7567 128x64 mono LCD sharing SPI2 with a W25Q128 flash, calibration in the flash security registers, from the reference port (hardware-md9600.md).
• Several PLL and IF chips were used in production. Board versions V2 (the first V1 boards were labeled V2), V3, V4, V4A (same as V5) and V5 exist, and a build for the wrong version boots but won't transmit or receive (unverified). A retailer ties V4/V5 to "PLL 2571" (unverified) (passion-radio). The reference port's register writes give: V1-V3 SKY72310 x2 with AK2365A IF chips, V4 a "PLL1590" synthesizer (TYT's V4 firmware folder name; exact part ?) with AK2365A, V4A/V5 the LMX2571 register set (unverified) and no programmable IF chip. Details, pin map and per-revision programming: hardware-md9600.md; codec: codec-md9600.md (V26.45 is the radio's own donor).
• Front 4x3 key matrix, channel encoder, and hand-mic keys read as analog levels. The mic has 16 keys on an RJ-45 jack (unverified).
• 136–174 / 400–480 MHz (unverified). Spec power is 50 W VHF and 45 W UHF; the same retailer page also says 40 W UHF (unverified). One review measured 44 W at 146 MHz and 40 W at 446 MHz (unverified).
• Mini-USB goes to the MCU's own USB, which enumerates as STM32 DFU 0483:df11. A claim of a "UART chip inside" is contradicted by that.
• FCC ID POD-DMR3 (TYT), granted 2017-12-28, with class II changes in 2020 and 2021 (MD-9600-5P GPS), three internal-photo exhibits (fccid.io). No separate RT90 FCC ID was found.
• RadioFoundry: reuses platform/stm32f4, drivers/modem/hrc6000, drivers/flash/spi_nor, the 128x64 display class already in the UI (ui.md). New: a SKY72310 synthesizer driver plus the per-band receive chain, an ST7567 display driver, analog mic-key decoding, and a board-version probe or per-version builds.

TYT MD-380 / MD-390 / Retevis RT3

• STM32F405VGT6 with 1 MB flash and 192 KB RAM, and an HR_C5000 DMR baseband (unverified).
• RF: SKY72310 synthesizer and a GT3136 receiver IC (unverified). There's no AT1846S. The schematic notes warn the schematic "is known to be not correct" (unverified).
• Display: 160x128 color TFT (unverified) on the FSMC 8-bit bus. The controller is reported as HX8302A (unverified) or possibly an ILI9481 (unverified). RT3 and MD-380 panels are "slightly incompatible" (unverified). Controller unconfirmed.
• SPI flash: W25Q128FV 16 MB, but some VHF radios are reported to have only 1 MB (unverified).
• One band per radio: UHF 400–480 or VHF 136–174 MHz, 1/5 W (unverified). GPS on "G" models. The module is reported as both JS-H210 and JS-M710.
• Update path: a 48 KB Tytera bootloader at 0x08000000, app at 0x0800C000. USB DFU (0483:df11) with non-standard commands. Read-out protection level 1. Images are encrypted with a key held in the bootloader (unverified).
• FCC ID PODMD-380, granted 2015-07-22, with an 8-page internal-photos exhibit (unverified) (fccid.io).
• RadioFoundry: boards/md380 builds (UHF and VHF images), passes its host tests and has run on a radio (hardware-md380.md, md380-bringup.md). It reuses platform/stm32f4, drivers/flash/spi_nor and drivers/display/st7735 (HX8302A assumed compatible, ?). The HR_C5000 is a variant of drivers/modem/hrc6000 (a chip flag selects the register differences). New: drivers/rf/sky72310 (shared with the MD-9600 later), drivers/gps/nmea_line, run-time GPS detection (board.gps_present). DMR voice uses the codec of the vendor D002.032 file, merged at build time and run in place (codec-md380.md); untested on a radio.

Radioddity GD-77 family

• MK22FN512 MCU, HR_C6000, AT1846S, UC1701 display controller, 25Q80BV SPI flash + AT24C512 I2C EEPROM, no GPS (unverified). The MK22FN512VLL12 is a 120 MHz Cortex-M4F with 512 KB flash and 128 KB SRAM (Keil device page); that exact suffix on the GD-77 board is not confirmed.
• 128x64 mono display, the size our UX specs assume (information-architecture.md). No public spec sheet found states the panel resolution.
• 136–174 / 400–470 MHz, 1/5 W (unverified). USB cable with a K1 plug and no UART chip in the cable (unverified).
• FCC ID 2AN62-GD77 (manufacturer listing).
• Update mode: hold S1 + Fn at power-on. Firmware updates over USB HID, no driver. Images are .sgl files (unverified). No public description of the .sgl encryption was found.
• Rebadges: the TYT MD-760 is the GD-77 (three sources agree). The GD-77S is the TYT MD-750 (keyless, no display). The DM-1801 is also sold as the DM-860, and only its version 1 hardware is in this family; the 2022 DM-1801 and DM-1801A are reported different, and the DM-1801 sold in 2026 is an HR_C7000 radio (Baofeng DM-1801 Pro and DM-1801 (current)). The DR-1801 has the same case but no part of this platform (Baofeng DR-1801). The RD-5R is the DM-5R Tier II in a new case (unverified). Sources contradict each other on the DM-1801A.
• RadioFoundry: reuses drivers/modem/hrc6000, drivers/rf/at1846s, drivers/flash/spi_nor and the 128x64 display class. New: a platform/mk22 (Kinetis start-up, clocks, SPI, I2C, USB device for TinyUSB), a UC1701 display driver, an I2C EEPROM driver for settings, and an .sgl image tool. The 512 KB of internal flash is half the STM32 radios' 1 MB, so check RadioFoundry's image size with codec early. The HD1 v1 is the same platform with a color display and a serial bootloader.

Radioddity GD-88

• 136–174 / 400–480 MHz, 2.5/7 W, 2" color TFT, built-in GPS and APRS, dual VFO, 3000 mAh, FCC ID 2AN62-GD88 (radioddity.com).
• "2 separate transceivers both usable at same time, even on same band" (Radioddity blog).
• Uses "the new C7000, DMR and combined CPU chip" (unverified). No public source confirms two HR_C7000 chips (hardware-gd88.md). The RF chip and display controller aren't confirmed; the FCC internal photos are the next thing to read.
• Shares a CPS with the Retevis RT73 / Kydera CDR-300UV / Radioddity DB25-D and DB40-D, which points to one OEM platform (unverified) (codeplugs.rats.net).
• Programming and updates go over a USB-serial cable (FTDI-class chip in the cable) into the K1 jack, to SoC A's UART1 at 115200. The radio has no USB port (hardware-gd88.md).
• RadioFoundry: reuses platform/hrc7000 and drivers/modem/hrc7000 from the DM-32UV. New: the RF chip(s), the display, and core support for two simultaneous receivers if the hardware really has two independent DMR paths.

Baofeng DM-32UV

• TX 136–174 / 400–470 MHz. RX adds 400–480, AM air band 108–136 and FM broadcast 65–108 MHz. 10/4/1 W, 2.0" color screen, built-in GPS, USB-C charging (the socket is on the battery pack, no data). FCC ID 2AJGM-DM32UV (baofengradio.com).
• The radio receives air band AM. Which chip demodulates it (the FD6818's AF output is the working guess) and the broadcast chip (an RDA5807M on the pin map) are open: airband-and-broadcast.md.
• K1-style programming cable, with FTDI preferred (unverified).
• The HR_C7000 integrates a CK803S MCU, according to a vendor quote about a different radio (unverified).
• PCB revisions DM32_UV_V1.2 (2024-08) and V1.4 (2024-12). Factory firmware 048/049 (unverified) (M7OCM/DM-32UV). Update mode is PTT + SK1 at power-on (unverified).
• Flash: hardware-dm32.md has a 1 MB XIP program flash and a 16 MB data flash. A forum snippet names a 25Q16 (2 MB) and a 25Q128 (16 MB) as the chips reported for it (unverified). The program flash part and size are unconfirmed.
• FD6818 RF, ST7789-class 240x320 panel and ATGM336H GPS are in hardware-dm32.md. No public teardown ties them to the radio.

Baofeng DM-1801 Pro and DM-1801 (current)

Two listings sold new in 2026 under the DM-1801 name. Neither is the DM-1801 v1 of the GD-77 family.

• DM-1801 Pro:
  • TX 136–174 / 400–470 MHz; RX adds AM air band 108–136 MHz and FM broadcast 65–108 MHz.
  • 1.77" display, 7.4 V 2200 mAh battery, Kenwood 2-pin accessory jack, no GPS, no USB-C charging.
  • Records DMR calls (about 10 hours) and exports them as WAV through the CPS (V1.60).
  • FCC ID 2AJGM-DM1801PRO; the English manual is dated 2026-09-16 (baofengradio.com, manual, fccid.io).
• Chips: an HR_C7000 is on the PCB in the FCC internal photos. The RF chip, the broadcast receiver, the flash and the display controller aren't identified yet.
• Same hardware as the DM-1801: the filing includes an attestation that the DM-1801 and the DM-1801 Pro are identical except for color and distributor (FCC filing). The listings' different power, memory and key counts don't fit "identical" unless they're firmware and marketing differences.
• Which DM-1801 revision this is: the hardware matches neither v1 (MK22 + HR_C6000) nor the 2022 redesign described as a single module (unverified). It may be a third revision, or the 2022 redesign may already have used the HR_C7000. Buying "a DM-1801" new doesn't get the v1 board.
• Telling them apart: v1 has a 128x64 mono display. The model and FCC ID label under the battery is the reliable check; the case alone isn't (see the DR-1801 below).
• RadioFoundry: reuses platform/hrc7000, drivers/modem/hrc7000, the FD6818 driver (own register set) and the shared factory calibration reader. New: the ST7567 display driver and the board. The hardware is in hardware-dm1801pro.md; the radio is not yet run on a bench. Needs: the key map, the update path and the codec's location.

Baofeng DR-1801 / DR-1801UV

• FCC ID 2AJGM-DR1801 (fccid.io).
• Chips: one large LCC module marked "Auctus AM6102". Under the module's RF shield is an IC marked "EP8277 ABE10" (FCC internal photos). What the AM6102 integrates (MCU, DMR baseband, RF) and what the EP8277 is are not documented. Auctus also makes the AT1846S.
• Easily mistaken for a DM-1801: the case looks identical (FCC photos). A forum claim that the DR-1801 is completely different hardware from the DM-1801, and that Baofeng renamed the redesigned DM-1801 to DR-1801, is unverified.
• RadioFoundry: not planned. Nothing in RadioFoundry drives an Auctus DMR module, and no public documentation for it was found.

Radioddity DB25-D / DB25-D PRO / Retevis RT73 / Kydera CDR-300UV

The DB25-D is Kydera's CDR-300UV under Radioddity's name. Radioddity's FCC ID 2AN62-DB25D is a change in ID of VO6CDR-300UV (Fujian New Century Communications, granted 2021-08-19). That filing keeps its internal photos, schematics and parts list confidential (fccid.io 2AN62-DB25D, fccid.io VO6CDR-300UV). The 2025 DB25-D PRO has its own filing, 2AN62-DB25DPRO, with public internal photos. Those photos are the source of the C tags below, so they hold for the PRO. Its display board is dated 2020.08.21 and carried over, but its control, RX and TX boards are 2024 redesigns ("CDR300UV-MCU-BT-AI-TDA-1.0", "C7DR300UV-RX-BT-AD-3.0", "C7DR300UV-TX-RD35-BT-AD-3.5") (2AN62-DB25DPRO internal photos). One firmware image covers the DB25-D and the DB25-D PRO (readme in the 2025-02-10 package). The Retevis RT73 is reported as the same radio (unverified) (kydera-ham forum). No RT73 FCC ID was found.

• MCU and DMR: one HR_C7000, marked "HR_C7000 D56323MP1" (FCC photo). The HR_C7000 integrates a C-SKY CK803S core, as on the DM-32UV (hardware-dm32.md). The vendor's update guide is on radioddity.com. Program flash part: ?. It's larger than 1 MB: the firmware keeps data above 0x0310C000.
• RF: the PRO's RF board has two Beken BK4819 transceivers with a TCXO (FCC photo). The receiver IF is 51.550 MHz (extended manual v3.4, section 18.2). The release notes' batches D64, D66 and D6T are the FD6818 boards; the PRO is DBB. On the PRO, one BK4819 is the LO synthesizer at f_RX + 51.55 MHz and the other works at the IF in receive. BK4819 support first appears in the 2024-05-09 build, so older vendor images must not be loaded on a PRO. Both chips share one 3-wire bus with separate enables.
• Bands and power: 136–174 / 400–480 MHz, 20 W or 5 W, 13.8 V (radioddity.com). The FCC grant lists 19.7 W conducted. The PA is a discrete RF MOSFET on the TX board (photo). PA power is set by DAC B with a ramp at each burst, as on the DM-32.
• Display: 1.77" color TFT (radioddity.com). An RT73 review says 2" diagonal (unverified). The init sequence is an ST7735S-class controller in landscape on a 4-wire serial bus, not the DM-32's 8080 bus. An ADC strap picks bit-banged GPIO or the SoC's SPI2 on the same pins. Radioddity's "white screen after update" fix fits that (manual 14.4).
• Controls: front keys power, P1, P2, P3, VOL/SQL, TONE/T.SEL, B/E and Menu/OK, plus one push encoder. The 16-key hand mic adds PTT and P4–P7 (DTMF A–D) (extended manual v3.4, section 5.5). The mic board ("CKS-10A-2") carries a small QFN, likely an MCU, so the keys probably reach the radio as serial codes on RJ-45 pin 2.
• Mic connector: RJ-45. 1 power off (to ground), 2 PTT / radio RXD, 3 mic audio, 4 shield, 5 radio TXD, 6 ground, 7 +8 V, 8 speaker. 3.3 V logic, 115200 baud (extended manual v3.4, section 17.6). The side K1 jack has the same serial pair (3.5 mm sleeve RXD, 2.5 mm ring TXD) (section 17.5).
• Audio: NXP TDA8542AT (2 x 1.5 W BTL) speaker amplifier (FCC photo). An "AI" noise-reduction daughter module ("CC1157G") sits between the C7000 and the mic and speaker paths. Its pads read AFES_IN/OUT, MICES_IN/OUT, SCL, SDA, NR_ON/OFF, ES_SW (FCC photo). Mic and speaker otherwise go through the C7000's codec as on the DM-32.
• Storage: Kioxia TC58CVG1S3HRAIJ, a 2 Gbit (256 MB) 3.3 V SPI NAND (FCC photo; part decode Elnec). The firmware's storage code is NAND with a bad-block table on SPI0. Calibration is a 2 KB page at NAND byte address 0x280000 with a second copy in program flash; the firmware repairs one from the other at boot. The layout is decoded (hardware-db25d.md 6).
• Other: RDA5802N FM broadcast receiver (FCC photo). GPS: built in, SMA antenna port, module ?. Bluetooth: none on the DB25-D per the product page. The PRO's board name says "BT", but no module was fitted in the FCC unit. Coin-cell RTC backup (photo).
• Programming and update: the vendor "IAP" Windows tool over a serial cable. Hold P1 and press power, and the display stays blank with the backlight on (update guide). The original cable has a Prolific PL2303 (2021 addendum). FTDI cables work since firmware 909E.D4.EARSAB.018 (release notes). A ".flash" file mode updates the IAP loader itself (manual 14.6).
• Image format: raw code with no header, checksum or encryption, linked at 0x0300C000 behind a 48 KB loader, as on the DM-32. The PC link and the debug output are both UART1 at 115200 (hardware-db25d.md).
• Codec: the AMBE+2 vocoder is software on the CK803S core, and no vocoder chip shows in the photos. The per-radio codec model of the DM-32UV carries over: the codec comes from the user's own DB25-D file, at a different address in every image, so each file needs its own recipe (hardware-db25d.md 8). AMBE frames pass through the CPU.
• Codeplug tools: qdmr's support request has been open since 2021 (qdmr #165).
• Not DMR: the DB25-G, DB20-G, DB40-G and DB35-G GMRS mobiles and the "DB25 Pro" (no D) are analog FM radios (radioddity.com DB25-G). They aren't RadioFoundry targets.
• RadioFoundry: bring-up started, make BOARD=db25d (hardware-db25d.md 9): FM receive, nothing run on a radio yet. It reuses platform/hrc7000 (shared with the DM-32), the st7735 driver on a bit-banged serial bus, drivers/rf/bk4819 for both chips (receiver and LO synthesizer), the shared calibration curve, and drivers/flash/spi_nand (read side) for the NAND. The calibration reader takes the newer of the NAND and program-flash copies and never writes either. Still to do: TX (refused until a real calibration page has been seen), DMR (the DM-32's modem glue shared, plus a codec recipe for a vendor image from 2024-05 or later), the NAND's write side and a storage adapter (RadioFoundry's stores assume NOR sectors), the mic keypad protocol, the FD6818 boards, and an unbrick path (the JTAG pins look untouched by the app; the ROM serial boot needs checking on this board).

Radioddity DB40-D / Kydera CDR-700UV

• The DB40-D's FCC ID is VO6CDR-700UV, the Kydera CDR-700UV, granted 2023-08-16 with Bluetooth (2402–2480 MHz) in the grant (radioddity.com, fccid.io). The internal photos are public (internal photos).
  • Processors: the main board has two identical large packages marked "A" and "B" on the silkscreen. Their markings can't be read in the photos (two, from the photos; ? for the part). Updates take two files, (A) and (B), written separately in IAP_A and IAP_B mode, and the B update shows no progress on the radio (extended manual v3.4, section 14.3). So the radio very likely has two HR_C7000 SoCs, one per VFO, like the GD-88. The DB40-D's B firmware shares the GD-88's B49C prefix (release notes).
• RF: separate VHF and UHF receive chains and two PA modules, one per band. Shielded cans hide the RF chips (photos). RF chip: ?. 136–174 / 400–480 MHz, 40 W or 25 W (extended manual v3.4, section 18.6). The product page says 20/40 W. Fan cooled.
• Display and controls: 2.4" color TFT (radioddity.com), controller ?. The front has three push encoders (VFO A volume, VFO B volume, channel), PF1, PF2, on-hook and off-hook keys, Back/Zone and Menu/OK (extended manual v3.4, section 5.6; photo). The mic is the same 16-key RJ-45 mic as the DB25-D's, with P5–P8.
• Storage: TC58-family SPI NAND per the firmware strings, part ?.
• Other: GPS (active antenna supported), Bluetooth 5.0 module with an external antenna, RDA5802 FM broadcast ("rda5802" string), external speaker jack. The CDR-700UV board has a SIM footprint for an LTE option the DB40-D doesn't use (photo).
• Programming and update: only through the RJ-45 at 3.3 V and 115200 baud (extended manual v3.4, section 17.6). The box contains an FTDI cable. IAP mode: hold the on-hook key and press power. The images are raw, plain and headerless like the DB25-D's: A is 814 KB, B is 419 KB.
• Codec: software in each C7000, so extraction from the user's own files works as for the DB25-D, once per image if both processors decode voice.
• RadioFoundry: needs two cooperating images (A runs the UI, GPS and Bluetooth; B is a second modem and receiver) and an A↔B link protocol. That's the GD-88's problem too, so it should follow the GD-88 port. New beyond the DB25-D: the dual-SoC core support, the 2.4" panel, two PA power tables and fan control. Effort: months. Blockers: the two chips' identity, the A↔B protocol and hardware.

Relatives worth supporting

Not DMR candidates: the BK4819 and BK4829 are analog FM transceivers, and the BK4829 adds only an FSK modem (datasheet listing). The Radtel RT-4D does DMR through a BK4819 plus an HF6853 vocoder module (unverified), a different architecture from anything in RadioFoundry. The Retevis C62 and Quansheng-style radios are FM only.

What exists and what's new

Suggested port order

By effort, then by how many radios a port unlocks and how popular they are:

1. TYT MD-UV380 / MD-UV390 / RT3S. It's a board variant of the DM-1701, very popular, and needs no new chip drivers. Effort: days.
2. Radioddity GD-77 family (GD-77, MD-760, DM-1801 v1, RD-5R, GD-77S, then HD1 v1). It has the largest user base of any open-firmware DMR radio. It reuses the HR_C6000 and AT1846S drivers and the existing 128x64 UI class, but needs a new MK22 platform and a mono display driver, and has a tight 512 KB of flash. Effort: weeks.
3. TYT MD-9600 / RT90. STM32 + HR_C6000 again. New are the SKY72310 driver, the ST7567 display (shared work with the GD-77's mono driver) and the board-version problem. Effort: weeks, and the V4/V5 PLL needs identifying first.
4. TYT MD-380 / MD-390 / RT3. Builds now, with the SKY72310 driver the MD-9600 can reuse, and runs the vendor D002.032 codec in place for DMR voice (codec-md380.md); it needs a radio for bring-up.
5. HR_C7000 family after the DM-32UV is on air: the DM-1801 Pro (air band and broadcast like the DM-32UV, chip list still open), then the DB25-D (one HR_C7000, but a new RF chip and SPI NAND), then the GD-88, then the DB40-D (two SoCs, reusing the GD-88's A/B work). All four are wish list items until hardware is on the bench. Start by reading the FCC internal photos, since the GD-88's chip list is mostly unknown.
6. Opportunistic: CS7000-M17 (nearly free after step 3), MD-2017 (dual receive) and DM-1702. The Anytone family is the biggest prize by popularity, but it needs a new MCU platform and a new DMR chip driver for the SCT3258, so it comes last.

View the source of this page