Icom Firmware Reverse Engineering: AI, Custom Firmware and a New Era for Amateur Radio

The amateur radio community is witnessing an interesting development. Firmware for some modern Icom transceivers has been decoded, and, for supported models, modified and rebuilt, opening possibilities that were previously beyond the reach of most radio amateurs. At the same time, artificial intelligence is transforming how engineers approach complex reverse-engineering projects.

For decades, amateur radio has been built around experimentation. We modify equipment, develop software, construct interfaces and push the boundaries of what our radios can do.

But modern transceivers are no longer simply collections of RF circuits and analogue controls. They are sophisticated embedded computing platforms, often running proprietary software that determines much of their functionality.

Until recently, investigating that software required considerable specialist knowledge, expensive tools and potentially months of painstaking analysis.

That landscape is beginning to change.

SQ6EMM’s breakthrough: Custom firmware for Icom radios

Polish radio amateur Dawid, SQ6EMM, has published a remarkable project involving the firmware of the Icom IC-705, IC-9700 and IC-905.

His work demonstrates that the firmware update containers used by these radios can be decoded and their internal structure investigated.

More importantly, in the case of the IC-705 and IC-9700, the firmware can be modified, rebuilt and packaged into an update file accepted by the radio’s normal firmware update mechanism.

This is considerably more significant than changing a few configuration parameters or sending undocumented CI-V commands.

It involves understanding the underlying firmware format, extracting executable code, analysing its operation and introducing modifications into the software running on the transceiver itself.

The project is publicly documented on GitHub, together with utilities for decoding, rebuilding and patching supported firmware images.

Project: https://github.com/sq6emm/icom-custom-firmware

What new features are possible?

The custom firmware project introduces functionality particularly relevant to operators using transverters and microwave equipment.

Some of the documented enhancements include:

  • Support for up to eight transverter configurations.
  • RF frequency displays extending to 122 GHz.
  • CI-V frequency translation for external software.
  • Configurable maximum transmission power for individual transverters.
  • TX delay and PTT inhibit controls.
  • Additional spectrum scope settings.
  • A/B firmware booting, allowing an alternative firmware image to be retained.

The IC-705 modifications also include extended transmission frequency ranges, although the hardware’s capabilities and applicable licensing restrictions remain important considerations.

For microwave enthusiasts, especially those using transverters with the IC-9700, these are potentially valuable improvements.

They demonstrate how additional functionality can be introduced without changing the underlying RF hardware.

How was the firmware reverse engineered?

One of the most interesting aspects of the project is the documentation describing the Icom firmware update format.

The firmware containers contain several software components, including executable images for the main processor and other subsystems.

The research identified two important transformations used to encode the firmware:

1. An autokey byte transformation

A reversible operation obscures the firmware data using relationships between consecutive bytes and their positions within the image.

2. LZSS compression

The firmware also uses a variant of the LZSS compression algorithm, which must be reversed to recover the original executable image.

Once these operations are understood, the firmware can be extracted into a form suitable for conventional reverse-engineering tools.

The recovered main processor images contain ARM executable code that can be investigated using tools such as Ghidra.

The repository includes scripts and documentation covering the firmware layout, decoding process and reconstruction of update files.

Why the IC-905 is different

An important distinction emerged during the investigation.

The IC-705 and IC-9700 firmware update formats use unkeyed MD5 integrity checks, allowing modified firmware images to be rebuilt with valid checksums.

The IC-905 update format includes RSA-2048 digital signatures; the published research describes signature verification by the radio as a remaining question.

This means that although the IC-905 firmware can be decoded and analysed, rebuilding a modified update with a valid manufacturer signature is a different challenge.

A valid manufacturer signature cannot be recreated without the private signing key. Whether and where a particular device enforces signature verification must be established separately; decoding alone does not answer that question.

This illustrates the difference between a checksum designed to detect accidental corruption and a cryptographic signature intended to authenticate software.

Where does artificial intelligence fit into all this?

This is perhaps the part that interests me most.

Modern AI-assisted development tools are changing how engineers approach complex software problems.

Reverse engineering has traditionally involved manually analysing disassembled instructions, following function calls, identifying memory structures and gradually reconstructing undocumented behaviour.

Tools such as Ghidra have made this work possible for many years.

AI introduces another layer of assistance.

A capable coding assistant can help interpret decompiled functions, suggest relationships between unfamiliar code sections, generate analysis scripts and assist with repetitive investigation.

It can also help developers understand processor architectures, binary formats and unfamiliar software structures.

For example, an engineer might use Ghidra to extract a function from an ARM firmware image, then ask an AI assistant to explain its likely purpose, identify relevant memory operations or suggest how to investigate the surrounding code.

The results still require careful verification.

AI can misunderstand assembly instructions, invent relationships or propose changes that would be unsafe on real hardware.

Nevertheless, it can significantly accelerate the investigative process.

An important distinction: SQ6EMM’s published repositories establish the technical reverse-engineering achievements, but they do not independently establish which AI tools, if any, were used to produce those results.

The broader significance is that projects of this complexity are becoming increasingly approachable when conventional engineering tools are combined with AI-assisted analysis.

Our own experiments at 9H1LO: Exploring firmware emulation

At 9H1LO, we have also been experimenting with Icom firmware investigation and emulation. Our work uses the open-source IC-7300 homebrew project by Jarkko Vääräniemi, a separate project from SQ6EMM’s IC-705 and IC-9700 modifications.

Our interest is not simply in modifying a radio to unlock additional features.

We want to understand how these embedded systems operate, how their firmware interacts with hardware and whether portions of that behaviour can be studied in a controlled virtual environment.

Our experiments run the project’s IC-7300 emulator in an Ubuntu virtual machine. We verified its reference display and MENU control, and explored a virtual SD card and homebrew app loader. These are emulator experiments; we have not validated the loader on a physical radio.

The idea is to create a development environment in which firmware components can be investigated without exposing an expensive transceiver to unnecessary risk.

IC-7300 emulator main screen
Upstream IC-7300 emulator reference screenshot by Jarkko Vääräniemi, showing the emulated main display. This is a project reference image, not a capture of our VM. Source: IC-7300 homebrew, © 2026 Jarkko Vääräniemi; MIT license.

Why use an emulator?

Modern Icom transceivers incorporate specialised embedded processors, memory devices, DSP components and interfaces to RF hardware.

Running firmware designed for these systems on a conventional computer is not as straightforward as executing a normal application.

An emulator must reproduce enough of the original processor and hardware environment for the firmware to execute meaningfully.

Depending on the level of emulation, this may involve processor instruction emulation, memory mapping, interrupt handling and simulated peripherals.

Not every hardware function needs to be reproduced immediately.

Even limited execution and debugging capabilities can provide useful insights into the firmware’s internal behaviour.

IC-7300 emulator synthetic spectrum
Upstream IC-7300 emulator reference screenshot by Jarkko Vääräniemi. The spectrum and waterfall use synthetic signals from a simulated FPGA; they are not live RF reception. Source: IC-7300 homebrew, © 2026 Jarkko Vääräniemi; MIT license.

Combining emulation with AI-assisted development

Our experimentation also explores the use of AI coding tools to assist with the development and investigation process.

AI can help examine firmware structures, explain unfamiliar routines and develop the scripts and supporting software needed for experimentation.

However, the real challenge remains ensuring that the results correspond to the actual behaviour of the embedded system.

An AI-generated explanation is not proof that a particular function behaves as described.

Similarly, successfully loading firmware into an emulator does not necessarily mean that the firmware is executing correctly or that the complete transceiver has been emulated.

At this stage, our work remains experimental.

We are not claiming to have developed a fully operational virtual Icom transceiver.

The objective is to build an understanding of the firmware and investigate what may eventually become possible through emulation, debugging and controlled experimentation.

As the investigation progresses, we intend to share further technical findings and practical experiences on 9H1LO.

A particularly interesting development: The A/B bootloader

Another significant aspect of SQ6EMM’s work is the custom A/B firmware bootloader.

The concept allows an alternative firmware image to be retained on the radio, giving operators a means of switching between firmware slots.

For experimental development, this is an important capability.

However, it should not be confused with a completely risk-free recovery mechanism.

Installing the modified bootloader requires rewriting a critical part of the radio’s firmware.

An interruption during this process could leave the equipment unable to boot normally, potentially requiring direct access to the flash memory using external programming equipment.

The project’s documentation specifically warns users about this risk.

Anyone considering installing modified firmware should understand the implications and ensure that suitable recovery arrangements are available.

The browser-based firmware patcher

Rather than distributing complete modified Icom firmware images, SQ6EMM provides a web-based patching utility.

Users download the official firmware from Icom and supply it to the patcher.

The patching operation takes place locally within the browser.

The tool checks the supplied firmware against supported versions and applies the available modifications.

This is an interesting approach because it avoids redistributing complete proprietary firmware images.

It also provides a more accessible interface for technically capable users who may not want to execute the individual decoding and rebuilding tools manually.

The patcher is available at:

https://sq6emm.github.io/icom-custom-firmware/

Of course, users should understand the risks before installing any unofficial firmware.

What does this mean for Icom and other manufacturers?

Modern amateur radio equipment is increasingly defined by software.

The hardware may remain capable of operating for many years, but the functionality available to the operator is often determined by the manufacturer’s firmware development priorities.

Once a product reaches the end of its commercial development cycle, additional features may never arrive, even when the underlying hardware could potentially support them.

Community-driven firmware research introduces another possibility.

It raises questions about the extent to which owners should be able to inspect, understand and modify the software running on equipment they have purchased.

Manufacturers have legitimate concerns about safety, regulatory compliance, intellectual property and product reliability.

At the same time, amateur radio has always encouraged technical experimentation and innovation.

Finding a reasonable balance between these interests will become increasingly important.

Is this the beginning of community-developed amateur radio firmware?

It is still too early to say.

Reverse engineering a firmware format is one achievement. Maintaining reliable alternative firmware for a complex commercial transceiver is another challenge entirely.

There are many practical difficulties, including undocumented hardware, compatibility between firmware versions, RF safety, testing and long-term maintenance.

Nevertheless, the work demonstrated so far is impressive.

It shows that modern amateur radio firmware is not necessarily beyond the reach of independent researchers.

And with AI-assisted development tools becoming increasingly capable, the number of people able to contribute to these investigations may continue to grow.

Final thoughts from 9H1LO

For me, this development represents something fundamental about amateur radio.

Our hobby has never been solely about purchasing equipment and using it exactly as supplied.

It has always been about understanding technology, experimenting with new ideas and finding ways to improve what already exists.

The work carried out by SQ6EMM is an excellent example of that spirit.

The combination of firmware reverse engineering, emulation and AI-assisted development opens some fascinating possibilities for future experimentation.

Our own work at 9H1LO is still in its early stages, but it is an area I intend to continue exploring.

Whether these developments eventually lead to more community-developed firmware, improved interoperability or simply a better understanding of the equipment we use, they are certainly worth following.

73 de 9H1LO


References and further reading

SQ6EMM: Icom Custom Firmware

https://github.com/sq6emm/icom-custom-firmware

SQ6EMM: Firmware Reverse Engineering Tools

https://github.com/sq6emm/ic705-ic9700-ic905-bring-your-own-firmware

Web-Based Firmware Patcher

https://sq6emm.github.io/icom-custom-firmware/

Community Discussion

https://mikrofale.cafe/showthread.php?tid=1296

Official Icom Website

https://www.icomjapan.com/


Disclaimer: This article is intended for technical discussion and educational purposes. Firmware modifications can cause equipment failure, affect regulatory compliance and potentially void warranties. The projects discussed are independent of Icom and are not officially endorsed by the manufacturer. The 9H1LO emulator experiments described here are preliminary research, not a claim of completed firmware emulation.

AI on the Air: A Practical Assistant for Amateur Radio and Electronics

Amateur radio workbench with SDR waterfall display, DATV test pattern, microwave dish, RF instruments and coding laptop
An AI-assisted radio and electronics workbench, from software to signals on the air.

Artificial intelligence is becoming a useful bench companion. For amateur radio and electronics, its value is practical: it can help turn an idea into a first working program, explain unfamiliar protocols, organize measurements, and make it easier to explore software-defined radio (SDR), digital amateur television (DATV), and microwave operation.

It is not a substitute for an operator’s judgement, a datasheet, or a measurement. Think of it as an assistant that can speed up research and development while the radio amateur remains responsible for checking the result.

This post was made with an AI agent

This article is also a small demonstration of the workflow. I used an AI agent connected to this self-hosted WordPress site through the Inviso MCP interface. With permission, the agent prepared the text, generated an illustration, and submitted the post through WordPress. The same kind of agent can help with routine publishing and site tasks, while a human chooses the subject, reviews the content, and decides what goes live.

A useful partner for software development

Many radio projects are software projects too: logging utilities, CAT control, digital-mode tools, station dashboards, antenna rotator interfaces, and scripts that turn raw measurements into something understandable. An AI assistant can scaffold a small application, explain an error message, help trace a bug, or suggest how to split a large program into manageable parts.

It can also help with data handling—for example, parsing a file format, converting measurement logs, or writing a utility around an existing library. A good workflow is to describe the hardware and software environment, ask for a small change, inspect the proposed code, then compile and test it with known inputs. The assistant can help draft tests and documentation, but those still need to reflect the project’s real requirements.

Exploring signals with SDR

SDR makes radio signals visible and programmable. An AI assistant can help explain a waterfall or spectrum capture, sketch a signal-processing chain, write a GNU Radio block or analysis script, or troubleshoot sample-rate and data-format problems. It can be a patient tutor when learning filtering, modulation, decimation, or demodulation.

For a practical project, an operator might use AI to generate a first-pass Python script that reads captured samples and plots a spectrum, then compare the result against a trusted tool and a known signal. Describing the receiver, sample rate, bandwidth, and expected signal makes the conversation more useful. The assistant’s interpretation remains a hypothesis until checked against the actual signal and equipment.

DATV: making the digital chain easier to understand

Digital amateur television brings together video, encoding, transport streams, modulation, RF hardware, and reception. AI can explain the role of each stage, turn notes into a block diagram, review a script that checks a transport stream, or help interpret logs from an encoder or receiver.

It can also help build setup checklists: confirm the video source, inspect the stream, verify symbol rate and modulation against equipment documentation, and check transmitted and received signals with suitable instruments. Settings depend on the system, band plan, local rules, and hardware; generated suggestions are not authoritative configuration.

Microwave projects and careful measurement

Microwave work rewards careful preparation. AI can assist with unit conversions, link-budget calculations, cable-loss estimates, documenting a feed or dish setup, and writing scripts to collect readings from supported test equipment. It can help compare a measurement with an expected range or organize a repeatable bench procedure.

At these frequencies, connectors, adapters, cable loss, alignment, calibration, and instrument limits all matter. A plausible calculation can still be wrong if an assumption is missing. Check values against component datasheets, instrument specifications, and measurements made with appropriate calibrated equipment.

Electronics learning and troubleshooting

When a circuit does not behave as expected, an AI assistant can help interpret a schematic, explain a component’s role, suggest measurements that distinguish between possible faults, or summarize a datasheet. It can be a useful study partner for topics spanning RF and software, including mixers, filters, converters, embedded control, and digital interfaces.

For safety-critical, high-power, or transmit-related changes, use established engineering practice and relevant regulations. AI-generated circuit values or operating advice are starting points for investigation, not a reason to skip design checks or testing.

Keep the operator in the loop

The strongest results come from a clear description of the goal, hardware, software versions, constraints, and evidence. Share an error log or measurement rather than asking the assistant to guess. Ask it to state assumptions and identify what needs checking. Then verify the answer with primary documentation, simulation where appropriate, and the actual equipment.

Used this way, AI can lower the friction of learning and building. It can help an amateur radio operator move from an idea to a prototype, understand a new signal path, or spend less time on repetitive coding and more time experimenting. SDR, DATV, microwave, and everyday station software all offer room for practical collaboration—provided the human remains at the controls.

LOTW

Logbook Of The World

This is my preferred QSL confirmation method, especially with the costs of cards and postage nowadays.

I will NOT entertain any requests for payment for you to confirm our contact via LOTW, if I want to donate to your expedition, I will, but I will not be held “hostage” to getting a DXCC with a PayPal payment. If this is your requirement, the contact will remain unconfirmed, I am not a DXCC or award chaser.

Info about LOTW on Wikipedia: https://en.wikipedia.org/wiki/Logbook_of_The_World

Official ARRL LOTW site: https://www.arrl.org/logbook-of-the-world

For those who need to learn about LOTW, start here:

Arduino and Touch Screen Based LDMOS SSPA Contoller

Code available here: https://github.com/9H1LO/Arduino-LDMOS-SSPA-Controller

Haier DC Inverter Airconditioner Repair

Model 1U71SABFRA

Not amateur radio related but might serve as a reference for someone, and a future reference for me as I have 4 of these.

The indoor unit started giving an error E7 flashing on the display and no cooling or heating – the outdoor fan was not starting at all.

I managed to find the service manual online, the PCB layout was not a 100% match but very similar, looks like some through-hole parts are SMD on my version, not to worry.

My usual disclaimer and WARNING – this time more severe than usual, usually I warn you that a mistake may damage your radio or device more, a mistake on this WILL KILL YOU ! If you are not confident with working on mains connected rectified DC (+330V at mains current), and do not have means to isolate the mains, your equipment and yourself and any other instrument you may use, DO NOT ATTEMPT this repair, engage a professional or someone who is capable of working on this. I will not be held responsible for any damage you cause to the unit, your equipment or your life, no one, including your next of kin or insurer will not hold me responsible for any damage you cause, including killing yourself by electrocution. Proceed at your own risk, or just read this article for educational purposes.

The unit uses 2 boards, a mainboard that seems to do all the control, and another board that drives the fan motor with PWM – I’m assuming this is a VFD controller – Variable Frequency Drive.

I did some quick checks before removing the boards from the outdoor unit, the service manual advises doing various checks, with most being a flow-chart, with most flows ending in “board fault – replace”, one check is if 330V DC is present on the 2 large smoothing capacitors, which there was, it was windy and cold out so I just removed the boards for inspection on the bench, hopefully, it can power up without many ancillary items. I was wrong, on the bench, rectified mains wasn’t available! looking at the layout, it seems the bridge rectifier is on the VFD board, with the mains filter caps on the mainboard, however, there was no power still, looking again it seems that an off-board PFC choke is connected to the VFD board, which remained in the unit on the roof, a quick bridge with crop-clips lead took care of that, hopefully, the PFC circuit won’t explode! – Note – Apart from using an isolated mains transformer, I current limit with a 100W light bulb in series when doing these checks, I learnt the hard way with MOSFET’s running off with fire trails on the bench!

After powering up I checked the main DC low voltages, 5V and 15V, they were not present, connected an (ISOLATED!) scope to the main switcher FET gate, and there was some pulsing, the SMPS was trying to start but was dribbling off, checked the datasheet for the NCP1200 SMPS controller, and it should have HV DC on pin 8 and a smoothing capacitor on pin 6, pin 8 was at around 290V DC and pin 6 at around 2V DC and “twitching”, hmm, let’s check the cap !

Main SMPS for AUX voltages – This is ALWAYS ON when mains is ON

This is the part where I remember that I keep telling everyone, DO NOT test electrolytic capacitors with your multimeter or capacitor meter, 99% of the time they will test good, I keep telling this to a ham friend in particular ! mehhhh — Read about ESR https://en.wikipedia.org/wiki/Equivalent_series_resistance

Cap looks good right ?? Looks even better than it should be !

Now lets test it as we should do an electrolytic ! Lets look at its ESR at 100KHz

20 ohms !! That is VERY high for a 22uF capacitor
Compared to a new 22uF capacitor ! 0.018 ohms !

Replaced the capacitor and the SMPS kicked back into life, +5V and +15V now present, some relays even started to click on the board. I gave a good check to most other susceptible components, but all looked fine, there was some corrosion on the VFD board which I cleaned up and I installed the board back in the unit, I am now writing this article in a nice and warm room 🙂

Icom IC-7300 Over Voltage Repair

Parts of this repair could also be valid if you reversed polarity to the radio, though the survival for reverse polarity should be better as a diode (marked C further down) should just blow the fuses on your DC cable.

Now to the over-voltage bit….

A linear power supply without a crowbar protection circuit is a bad idea, I supply kits on Tindie to avoid this situation. A high current linear PSU with output pass transistors (usually some 2N3055) going short circuit from Emitter to Collector could possibly feed your radio with a high current supply anywhere from 20 to 30 volts ! OUCH ! – Get a crowbar for linear PSU or go SMPS. Click HERE for Crowbar kits.

Now to this poor fellow who went through it and survived, with minor injuries, and fully repaired.

This is quite an easy fix though some care must be taken. Not all radios may fail the same, so your mileage may vary, maybe you have fewer components damaged, maybe more. The parts are cheap and easily available, I would just change them all.

The main symptom will usually be blown in-line fuses and no power. Make sure your PSU did really go high voltage. Disconnect the radio from this PSU!

Do NOT replace the internal 5 Amp fuse and connect to a power supply.

“Blowing” a fuse takes quite a bit of current (usually more than it’s rating) and quite a bit of time, the fuse is the “last-resort”, so if fuses have blown, (i shall say this in CAPS AND BOLD) THERE IS A SERIOUS SHORT CIRCUIT, DO NOT ATTEMPT TO “JUST CHANGE THE FUSE”, more damage could surely happen, semiconductors could burn out in microseconds with microamps, do you think keep putting 10’s of amps for nearly a second is going to keep them working long ? Fuses don’t blow for fun, take note !

1st, the “wash my hands” bit – DISCLAIMER

Any mistake can cause serious damage to your radio. So if you are not experienced in SMD soldering or using a soldering iron in a very FRAGILE environment – do not try to perform this fix yourself, buy the parts and a 6 pack of beer and give them to someone who can do it for you ! I will not be held responsible for any damage you cause to your radio based on this article.

On with it…..

A typical check is a multimeter on resistance/continuity/diode test mode, “beeper” will do. Check across the DC input connector on the radio, you will probably find it shorted or very low resistance, good ! hopefully the fast diodes at the DC input side have probably gone short circuit and acted before the CPU and PA transistors went bang !

Damaged Components
Schematic Reference
My MarkingPart NumberUsage
ADZ2J18018.9v Zener diode, this would probably pop first, but can’t carry enough current to blow the main fuses, it will probably go short then open circuit with high voltage at high current
B1/2/3470μF 25v3 pcs of 470μF 25v electrolytic capacitors, if they blew or not just change them ! This radio got 30v and they out-gassed. Yes ! LOTS OF MAGIC SMOKE !
CDF30SC4M40V 30A Schottky diode, this is the reverse polarity protection in fact, the surge of current still made it go short circuit in this failure
DFuse 5AMini blade flus protecting the low current side, i.e. anything not the PA, so CPU, accessories etc
E50S06I used a 50N05, a pretty common MOSFET, this going short blows the 5A fuse. This MOSFET “powers” on the main radio circuits, it is a “software controlled” switch as the radio by design is in sort-of “standby” let say, the PA is always “ON ” across the input power source, as is with most radios.
*FTPSMD15AVoltage transients suppressor, this can take quite a beating and is what probably saves the rest of the radio in this situation. I have marked it with a * simply because it is a star! well, strangely it doesn’t show up anywhere in Icom’s service manual !

All parts can be obtained from common sources, I used Mouser.

Following this repair, apply power the radio using a current limited power supply, start at 50mA to make sure there are no shorts, take it up to 500ma, then power on the radio, it should turn on and work normally, then you can move to use a high current PSU and test it on transmit, luckily the PA transistors are fine.

LimeSDR Mini Repair

Having been one of the initial backers on CrowdSupply, I received the LimeSDR Mini around mid-2019 and started playing with in the 2020 lock-down.

Link to LimeSDR on Crowd Supply

Lime SDR Mini – Block Diagram

I was noticing that after using it for around 15 minutes, the received signal levels were getting lower and lower until eventually disappearing, the chips got quite warm and some forums suggested passive and/or active cooling should help with this issue. Support from Lime directly was not answered though there is a forum https://discourse.myriadrf.org with what seems to be unofficial support and user community support. I attached some mini heatsinks to the 3 chips and indeed it worked fine for many hours. The plan was to enclose the whole thing in an aluminium shielded case and put some heat transfer pads from the board to the aluminium case, with the option of adding a fan for additional cooling.

image
Tested with 3 mini heatsinks which made a big difference.

then it happened !

Since this was a “temporary, proof of concept”, I was trying it out to ensure it really helped, then it happened ! the mini heatsink on the USB 3 chip accidentally came loose and shorted the back of the USB 3 connector. The PC did the USB disconnect sound and the Lime disappeared from the device list 🙁

image

The Lime LED always powered up but the USB device could not be detected in any way. I resorted to the aforementioned forum but didn’t get many useful answers, I had to dig down to component level. Luckily the Lime is an “open” hardware project, even though they have a custom silicon, and all schematics are available on their website, though somewhat confusing sometimes with the page not always working right, but that’s another story.

My suspicions was a dead USB 3 FIFO chip, since that’s where the short happened with the heatsink. This is an FT601Q device from FTDI

Datasheet Link: https://ftdichip.com/products/ft601q-b/

Capture4

By referring and comparing to the Lime schematics and FTDI FT601Q datasheet, I was finding VCCIO and VCC33 are good but VD10 which should be +1v from an internal LDO on FT601 is not present, actually the line was short circuit to GND, to verify I checked across C147 which is on AVDD_FT line on this power bus and it shows 0 ohms to ground so was am thinking either some capacitor is SC or the FT601. I posted all this on the forum, but I didn’t get much response, maybe no hardware-level gurus on there ? Don’t know, one user did reply but responses were barely helpful, so I had to keep digging myself.

Capture5
Capture6

I removed the FTDI chip from the board, and alas, the short circuit on DV10, VD10 and across C147 was gone so it looks like the chip has internal SC, so I decided to replace the chip. I tried ordering this directly from FTDI, which have an online store, though they said they couldn’t sell or ship it to me ! Very strange, I tried all the usual “catalog” of suppliers but all were out of stock, though Farnell could do it on back order with a lead time of 8 months ! WOW, I bit the bullet and ordered 2. In the mean time I bought an Adalm Pluto SDR kit from Mouser, made by Analog Devices, and I totally forgot about the Lime, €200 useless module in the back of the drawer. About 6 months down the line I get an email from Farnel with a tracking number, the FT601Q was on its way and would be here in 2 days ! I ordered 2 pieces just in case.

image
FT601Q USB 3 FIFO chip in QFN76 package – QFN = quad-flat no-leads ! and 76 of them 🙁

I heat shielded up the board well and soldered on the chip.It went better than I thought, lots of flux helps!

It was now or never, I made sure there were no obvious shorts, however, in the process of removing the old chip with the hot-air station, I managed to also remove C122 and C121, these are feed-through 100nF capacitors on the USB3 data lines, so it should still work in USB 2.0 mode. They are 0201 size, which is really really small, I left them out for the time being. Plugged in the USB and got the USB sound ! The FTDI chip was detected in its “unprogrammed” state

The chip can be configured using an application from FTDI. Zack on the Myriadrf forum advised the parameters used for the Lime Mini

image

It took some messing about to get it up and running but in the end all worked fine. I installed the 2pcs 0201 100nF capacitors and even got USB 3.0 working which is needed for larger RF bandwidth captures.

0201 are really small, could only manage them with the microscope
The location of the 2 capacitors and the empty pad is where an ESD7016 ESD Protection Diode pack goes, which I temporarily removed for ease of access

Detected and working in SDR Console and DATVExpress

Conclusions…

The Lime is now working again and I still intend to put it in an aluminium case. Though the Lime has much better specs especially on bandwidth, personally, I prefer the Adalm Pluto. I think these are nice gadgets to experiment and play with, though you cannot really compare them to shack-in-a-box SDR transceivers, especially since there is no filtering on RX and TX paths. Many people operate successfully with the Lime and Pluto on QO100, personally, I find the IC-9700 way better and much more practical.

Hopefully, this article will be of help and encouragement to someone else that comes across this issue as I didn’t find much support and assistance on the matter, by the way, I have a spare FT601Q in stock just in case anyone has difficulties like I did getting one quickly !

Icom IC-7300 Clock Repair

The Icom IC-7300 has an internal rechargeable battery to retain the running of the Real Time Clock – RTC. The battery charges when connected to your power supply, however drains deeply when left un-powered for a while. The issue seems to be that this Lithium Ion battery has a limited number of deep cycles and will eventually no longer be able to hold enough charge to keep the RTC running.

This is more of a nuisance and doesn’t really hinder the normal operations of the radio, except time-stamps on recordings or screenshots will all be labelled with the wrong date and time, typically starting at 1st January at 00:00.

Icom UK Official notice on mitigating the issue

1st, the “wash my hands” bit – DISCLAIMER

Quite a bit of heating is needed to remove the battery, and you are very close to other components, critical ones even, such as the main CPU. Any mistake can cause serious damage to your radio. So if you are not experienced in SMD soldering or using a soldering iron in a very FRAGILE environment – do not try to perform this fix yourself, buy the parts and a 6 pack of beer and give them to someone who can do it for you ! I will not be held responsible for any damage you cause to your radio based on this article.

My Solution

The best way, in my opinion, to solve this once and for all, is to replace the battery type. A non-rechargeable CR-2032, as used for the RTC on most PC motherboards should do the trick. Using a CR-2032 battery socket would make swapping the battery a 5 minute job a few years down the line.

The normal CR-2032 is NOT rechargeable, you may use a rechargeable type, but not really worth the risk of matching the charge profile and current, so an in-series diode will keep a non-rechargeable type like the CR-2032 from getting charged. The 0.6v voltage drop of the diode doesn’t bother the RTC, but may stop a few months earlier when the battery gets depleted, even though a little juice might still be there. I don’t see this as an issue, A quality branded CR-2032 is around €2 from most shops, even stationaries.

upload_2018-7-26_8-37-50.png
The battery is located just in the corner of the mainboard, next to the CPU
Original schematic of RTC circuit from Icom service manual
The diode shown in series with the non-rechargeable CR-2032A

A common diode such as a 1N4148 or 1N4001 may be used and is simply connected to the battery holder and covered in some heat shrink.

Affix the battery holder with some good double -sided tape to some place it cannot short anything, the top of the FPGA “screen” seems like a good place.

Website move

As you might have noticed, I have moved the website to wordpress.com. Having starting with my first website back in 1997 written in raw HTML on an Amiga 1200, this page has always been kept running over the years, either hosted on my own home server or in the last few years, on a rented VPS. I could have hosted the “free-ish” WordPress framework directly on the VPS, but in all honesty, having everything directly on WordPress itself saves me lots of hassle and time with keeping it updated, secure, patched etc so maybe I can dedicate more time to content than fiddle with raw HTML & CSS, php-extensions, packages that got deprecated over the years, but I never bothered to evolve my code etc etc. Should the need arise to integrate to any custom pages that need to really be on my own server, such as when I ran the DX cluster and QRSS grabber a couple of years ago, the option still exists. Oh well, I made it to web 2.0 I guess, took a while 🙂

Update 2022: Page moved back to my own server at Akamai, wordpress charge silly fees, I can manage a LAMP server myself, thank you 🙂

Ready for 10GHz tropo season…

Skeds via email please

10GHz to 144Mhz Transverter using Icom IC-705 as IF transceiver

9H1LO 10.368GHz contact with SV3/SV1EBS in Greece on 20th June 2021:

QSO with IW0RAF 25th July 2021

Local testing with 9H1BN: