开云体育

Hi. I describe changes on the release page (link below).
Just want to pay attention than this release is beta - some features might not works as expected.

?

https://github.com/gdyuldin/x6100_gui/releases/tag/v0.29.0

--

Georgy // R2RFE

I just tried running this new version using the exact same methods that I've always used to up the X6100 alternative software and for the first time that I can remember, the s/w will not load on my radio,,,, no familiar splash screen - just a black screen - nothing to indicate that it's loading.

?

I am running slightly older X6100 firmware - but that's never been a problem before: APP V1.1.7 Aug 25 2023 and BASE V1.1.6 Mar 7 2023.

?

I tried loading the software twice on the SD card using the exact same methods that I've always used - same result. I went ahead and loaded v.0.28.0 on the same SD card and tried it - loaded perfectly - no issues observed.

?

Anyone else seeing this?

?

Tnx -

?

Daniel/K4DB

Hi Daniel.
I have no ideas. Could you collect some more data:

* Turn off X6100
* Connect you X6100 to PC/Mac

* Start PuTTY (for windows) or screen (terminal utility for linux, hope it works on Mac too), connect to the radio

* Start X6100, wait some time and save all output.

Putty might be to logging, for screen you might add -L flag :
screen -L -U /dev/ttyACM0 115200

Logs will be saved to screenlog.0 file.

--

Georgy // R2RFE

Hi, i have the same Problem as Daniel and i think it is the same Thing as described here: /g/xiegu-x6100/message/2301 and here:

?

It is the commit , switch to GCC-12, on some newer x6100 Devices uboot will not boot if compiled with GCC-12.

I have changed the bootloader to the previous version and it boots fine, also i found out if you use GCC-14 this Problem ist gone, i can boot with a self compiled 2025.01 uboot Version.

?

73 de Markus, DB2ZW

Thanks for information, Markus.

I built u-boot 2025.1 with GCC-12 from the buildroot.
Could you, please, check it.

--

Georgy // R2RFE

Strange, my booted OK from fresh SD. Manufactured June 2023, latest OEM firmwares.

Hi Georgy,

your 2025.01 does not boot.

There are probably different hardware versions of the x6100, one does boot the another not....

It's GCC-12, i and Oleg also tested different u-boot versions and no Success.

With GCC-14 this Problem has gone is my experience.

?

Here my Version u-boot 2025.01, compiled with GCC-14, i can boot without Problems.

?

73 de Markus, DB2ZW

?

I have no problem with boot, otherwise I had fixed it)
Current Buildroot version have no support GCC14. Seems, it's time to migrate to the next version.

--

Georgy // R2RFE

Great Job, Georgy, after second img to SD write i can confirm that DATA is restored, wifi/ssh keys also OK. MFK func customisation changed, but no problem assigned again. No change in VOL customisation. ATU can`t load previously tuned values. New tuned freqs works OK. Now they enters atu table in full Hz values, e.g. 21447000 what previously was 428 - assume (int)freq/50000. I wonder if this is just a bug or new standard.

Thanks for information. I forgot to notice about ATU - It stores a full frequency and applied within +- 25 kHz of saved frequency. Previously, if you tune on 21 200 kHz - tuner parameters was applied for range 21 200-21 250,? now - for range 21 175-21 225.
I'll try to add a migration, which will correct saved ATU frequencies.

--

Georgy // R2RFE

Good idea Georgy, so atu table now shows in clear what was tuned. Opened params.db with SqliteBrowser to execute: UPDATE atu SET freq=freq*50000+25000 and now ATU works like before.

Georgy -

?

Any ideas when v.0.29.0 compiled with the newer buildroot version for the rest of us to test out?

?

Thanks & 73 -

?

Daniel/K4DB

Hi Georgy,

Thank you for new release! I’m testing your changes for a few days with no issues so far. To me, 0.29 is a huge improvement!?

Not sure if it has been changed with 0.29, but I like the way how waterfall is now rendered (no “slant” when tuning). Also, I see no more “ghosts” on waterfall.

Good job! Thanks!

Jarek SP9HGN

?

On Mon, Feb 17, 2025 at 10:42 PM, Daniel Baker wrote:

Any ideas when v.0.29.0 compiled with the newer buildroot version for the rest of us to test out?

Well, I spend a day trying few newer versions of the buildroot (with helps of the Franco Venturi repo). Unfortunately, every time something doesn't work.
Now I replaced uboot within 0.29.0 image from the releases page on github with Markus version. I uploaded it to the same releases page (name - sdcard_fixed_boot.zip).
Could you try?
If it helps - I just add a step to replace uboot of the prepared image on the GitHub Actions.

--

Georgy // R2RFE

On Mon, Feb 17, 2025 at 11:25 PM, Jarek SP9HGN wrote:

Not sure if it has been changed with 0.29, but I like the way how waterfall is now rendered (no “slant” when tuning). Also, I see no more “ghosts” on waterfall.

Yes, it's changed on the 0.29. The reason of "ghosts" was a spectral leakage. It was a bit annoying, when strong station hided weak one on waterfall/spectrum.

--

Georgy // R2RFE

Can occur in different Band (DOWN/UP) and Vfo (A/B) combinations and A/B result can be opposite, but after EVERY these 8 clicks:

A/B, BandUP, A/B, BandDOWN, A/B, BandUP, A/B, BandDOWN

radio goes to the point when:

Audio/Specrtrum/Waterfall "play" VfoA things, but indicators (vertical line shadow, VFO-B, Mode, Freq) show VfoB things. Tuning VFO knob only change Freq display and new VfoB value. Point also present at BandUP. Was thinking about database corruption, but deleting params.db not helped.

Hmm. Can't reproduce. Maybe I press these buttons not so fast? Someone else can check this?

--

Georgy // R2RFE

Georgy -

?

The sdcard_fixed_boot.zip fixed my reported issue - my X6100 is now able to successfully boot into v.0.29.0!

?

Many thanks & 73 -

?

Daniel/K4DB