¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: 5105 Locked?

 

?the lock function next to the tuning knob.

That's what I was thinking and that would be a great easy fix.?


Re: 5105 Locked?

riushr
 

This is a long shot but just in case you have forgotten about the lock function next to the tuning knob. Little red button.

Regards,
Rick


On Fri, Jul 15, 2022 at 12:58, DougVL
<K8RFTradio@...> wrote:
I would suggest that you (also) email Radioddity support.? They are Xiegu dealers and have pretty good tech support.
--------
Doug, K8RFT


Re: 5105 Locked?

 

I would suggest that you (also) email Radioddity support.? They are Xiegu dealers and have pretty good tech support.
--------
Doug, K8RFT


5105 Locked?

W6JIM
 

Hello,

I haven't used my 5105 in a few years.? Charged it up and powered it on, but that is all I can do.

It seems as if the rig is locked and non of the buttons respond, except for the power button.

It powers on, receives and transmits.? But I can not change frequency, mode, volume or anything other than power-on/power-off.

Thanks for any help.

73, Jim
W6JIM


Re: Low headphone volume?

 

Different headphones might be more sensitive (louder).
I usually use an external speaker, for better sound.
--------
Doug, K8RFT


Low headphone volume?

Nick Marsh
 

Playing with my new to me 5105 tonight. Headphone volume seems extremely low, even with my hearing deficiency. I¡¯ve searched these archives and the web but not finding a solution. The phones drive my hearing aids into feedback so that isn¡¯t a solution.?


Re: Great Rig

 

Hi 73 to all
Have X5105 two weeks..?I immediately noticed the wrong cw monitorig !??although in the description?
with new firm V3-008 says it's a solved .. not in my case...
Yes if you listen on another device its OK..? so monitoring is problem...

I experimented a bit and put it old firm V 1_0_6 and cw monitoring is?quite good now (fast, exact and no extra dots)
So?quite different from others? !!
There are several revew on youtube?no one is mentioned this.. ?!?

The X5105 is great for portable operation and?worth the money.
Thanks

Ivica 9a6cw






Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

Joe K9SZ
 

¿ªÔÆÌåÓý

That is fantastic news, Eric!

For those that are interested...

It has been a while since I¡¯ve worked with these devices in product development, but `back in the day` I also found working with USB posed some very interesting challenges.

I found that it was common for the prolific adapters to toss data when flow control (software or hardware) was being held for long periods of time (several seconds). It was after days of frustration looking at the layers of the system trying to find the lost data that I learned to use do loop back test on the hardware.

We then insisted that our products be used with FTDI adapters but the system integrators always supplied other equipment with Prolific adapters because they were cheaper and worked with their products.?

I agree that FTDI is great to work with but not without issues. A one time they released a driver that also dropped data after several seconds of holding flow control. To FTDI's credit it was fixed quickly rather than letting it become a new feature of these devices. :-) ?Later we customized the FTDI driver with our VID and PID info to remove plug and play and ensure that we had control only to discover the version actually used might be for some newer generic FTDI product.

At the end of the day, I decided to use echo data from our device to monitor the buffer fill levels. Sales, purchasing, and the customers were much happier.

Joe K9SZ




On Jun 16, 2022, at 7:11 AM, DougVL <K8RFTradio@...> wrote:

On Wed, Jun 15, 2022 at 11:29 PM, Tony G1HMO wrote:
USB to serial adapter which was PL2303 based, and started having issues when they 'upgraded' from Windows 7 to Windows 10.
When I first "upgraded" (I had no choice about that!), WIndows 10 "bricked" my clone PL2303? chip!? An internet search found the method to re-enable it, though.? Win10 loaded a new, factory official driver, and that driver recognized the chip as a clone and changed an ID number in it.? That rendered the chip useless, until I found the way to repair it.
?

--
Doug, K8RFT


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

On Wed, Jun 15, 2022 at 11:29 PM, Tony G1HMO wrote:
USB to serial adapter which was PL2303 based, and started having issues when they 'upgraded' from Windows 7 to Windows 10.
When I first "upgraded" (I had no choice about that!), WIndows 10 "bricked" my clone PL2303? chip!? An internet search found the method to re-enable it, though.? Win10 loaded a new, factory official driver, and that driver recognized the chip as a clone and changed an ID number in it.? That rendered the chip useless, until I found the way to repair it.
?

--
Doug, K8RFT


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

Good to hear, Eric.

Still ... if you have the JTAG reader, and the radio is in pieces already ...


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

The PL2303 based USB to serial are a real problem, I have had many of them and almost every one has been thrown in the bin!
The problam is that nowadays they are nearly all Chinese clones that do not work reliably with modern Windows versions.
One of my customers had several systems that used a USB to serial adapter which was PL2303 based, and started having issues when they 'upgraded' from Windows 7 to Windows 10.
I spend a lot of time with him trying to find out what the issue was, their system had the USB to serial in an always up 19200 baud link and intermittently the link would drop and then stop receiving, he was adamant it 'is not the adapter, we've used them for years without any issue'.
After much testing, I found the adapter would not receive at all at 115200 baud, below that it became more reliable the slower the baud rate, at 1200 baud, I could not get it to fail.

We swapped the adapters out for initally FTDI ones, and the problem went away, since then we've tried the CH340 based ones which are much cheaper , they too work perfectly well at 115200 baud which I think is what is used by the G90 / X5105.

Tony G1HMO


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

SUCCESS!

What led me to the solution was your comment, Joe.

I had never thought to do a loopback test, since the radio appeared to be connecting from what I saw in the terminal (i.e. I was getting the appropriate 'C' response from the radio when plugging the cable in).

Well, as it turns out, none of the USB/Serial devices I had around here passed the loopback test, so it's no wonder things weren't working.?

I hunted around in my parts bin and found a little FDTI board with a USB port on it and a set of header pins.? So, after hooking up TX, RX, and GND on the FDTI board to a 3.5mm headphone plug (Thanks again for the pinout, Joe), everything was good to go.? It passed the loopback test and when connected to the radio, the transfer began instantly and completed with no hesitation or errors!

I guess there is a wide variance in USB/Serial cables.? All of the serial cables I had been trying were PL2303 based and worked perfectly with the devices I had originally bought them for.? In fact, I had used one of them earlier this morning to clone a couple of my ICOM HTs, and the cable did its job just fine.? The X5105 however, didn't any of them.? I guess the Xiegu is picky about its serial port, and really wanted an FDTI serial port.

Anyhow, thank you to all who pitched in with ideas.? It's great to have the radio up and running again, and a great relief to know that it didn't need a new bootloader flash on JTAG, lol.

73 de W1JH
Eric


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

Joe K9SZ
 

¿ªÔÆÌåÓý

That is good to know.

Since you seems to be receiving okay, I assume this would work fine but...

Did you try a loopback test jumping TX and RX on the plug end of the USB to Serial cable where you get back what you type?

Here is a pic of the insides of the USB to Serial dongle that came with mine.



TXD (Green) is tip
RXD (White) is ring
GND (Black) is base

The 5V wire is connected to nothing. I don¡¯t know why it is wired up actually...

Is your dongle 5V?

73 Joe




On Jun 15, 2022, at 12:31 PM, Eric W1JH <ekeppel31@...> wrote:

Hi Joe,

Yes, I've actually tried not only that build, but the version 3 beta and even the older version 1.0.x listed elsewhere on that same page.
Unfortunately, the LEDs have never blinked during any of my transfer attempts thus far.
I'm using Teraterm v4.96 at the moment, but have also tried an older version of Teraterm as well as Hyperterminal for good measure.

Eric W1JH


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

Hi Joe,

Yes, I've actually tried not only that build, but the version 3 beta and even the older version 1.0.x listed elsewhere on that same page.
Unfortunately, the LEDs have never blinked during any of my transfer attempts thus far.
I'm using Teraterm v4.96 at the moment, but have also tried an older version of Teraterm as well as Hyperterminal for good measure.

Eric W1JH


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

Joe K9SZ
 

¿ªÔÆÌåÓý

Are you trying the build 008 found here?


In the pdf file it shows the Data LED blinking when uploading the code.?

I also noticed that there is a version of TeraTerm shipped in that zip file. I didn¡¯t recall that before with the current beta 006 that I am running now. I don¡¯t know if there is anything special about v4.96 perhaps??

Joe K9SZ



On Jun 15, 2022, at 11:34 AM, Eric Keppel <ekeppel31@...> wrote:

Hi Cesar,

Yes, I've followed those same instructions to the letter, but on my radio it doesn't work.? The radio has been running on a nice heavy duty 13.8V Daiwa power supply.? I did double check the PSU with a multimeter to be sure that it matches the readout on the PSU itself as well.

With Xmodem, I always use 1K mode. :-(

Eric W1JH


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

Hi Cesar,

Yes, I've followed those same instructions to the letter, but on my radio it doesn't work.? The radio has been running on a nice heavy duty 13.8V Daiwa power supply.? I did double check the PSU with a multimeter to be sure that it matches the readout on the PSU itself as well.

With Xmodem, I always use 1K mode. :-(

Eric W1JH


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

As James says, it is necessary to power the X5105 with 13.8 volts and update as indicated in:



it is very important to mark? [x] 1K

I had the same problem until i used 13.8 power


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

Hi James,

Yes, I'm trying to move from 1.0.x to the 3.0.0.? I've tried the method you describe with the battery disconnected, but it didn't seem to make any difference.? The terminal ignores the Xmodem transfer and continues to send 'C'.

I agree that the loss of the text menu system is a step backwards.? It's a lot easier to know you have a good connection when there is some actual text coming across the terminal, lol.

Eric W1JH


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

Oh, and I'm using a ?USB adapter. Needs to be TTL levels I believe.


Re: Tried to upgrade firmware and radio is bricked. Anyone know how to JTAG this to get it running again?

 

This sounds very like the surprise I described in my recent post here? "Firmware update / semi-bricking" ... Bootloader Version B behaves this way - there are two Update Instruction files in the firmware archive. I think the "no menu" version is the "new" one ... seems like a backward step. Maybe they added something else and had to drop that from the limited bootloader space.

Are you upgrading from 1.0.x to 3.0.0?

I was only able to reflash by having the battery disconnected and external power applied (holding the vol keys).