Re: How to preserve personal settings between R1CBU firmware upgrades?
Let me add, if you are using Windows, when you put the card back in your PC to copy back your backed up data, the Data partition may not show up as a drive.? That is a Windows issue.? You need to go into Disk Management, find the correct drive, right click on the Data partition and add drive letter.? You can now copy back the data to it.
?
Also note that this does not back up Wifi passwords.? That is covered in another message thread.??
|
Re: How to preserve personal settings between R1CBU firmware upgrades?
Randy,
if you are familiar with Linux, you could add these few lines to the '/etc/init.d/S01create_data' script that should hopefully preserve the existing DATA partition on your SD card:
?
These lines need to be added after you write a new R1CBU firmware upgrade to the SD card, and before you put that card with the new firmware in the X6100.
?
Basically right after you write the SD card, you have to mount /dev/sdX2 somewhere on your Linux PC, edit the file <mountpoint>/etc/init.d/S01create_data, add those lines in the same place as in the link above, and finally eject the card (eject /dev/sdX).
?
You may want to make a backup first, should something go wrong.
?
73,
Franco K4VZ
?
|
Re: How to preserve personal settings between R1CBU firmware upgrades?
Thank you, Lance!
73, Randy K7RAN
|
Re: How to preserve personal settings between R1CBU firmware upgrades?
Hi Randy,
You probably didn't get much traction before because it's been mentioned many times on the mailing list. Before you flash your SD card with the new firmware version, put the SD card *into your computer* and you should see a disk appear named "DATA". Copy all the files off of that drive somewhere else, like on your main computer.
Then, flash the SD card with the new firmware and boot the SD card in the radio at least once. Yes, your settings will appear to be reset.
Then, put the SD card *back* into your computer and copy the saved files back into the DATA drive. This restores your settings.
I have a question... I upgraded to v0.28 and love it a lot. But every time I upgrade I have to redo all my settings. I understand that there's a way to backup and then reload my settings... Someone suggested backing up ¡°data¡±? Can somebody give a summary on how to do that? Would be grateful... redoing it every time is no fun.
73, Randy K7RAN
P.S. I previously buried this question in a barely-related thread and got no traction, so I thought it better to create a topic.
-- J. Lance Cotton, KJ5O joe@...Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat the cookies.
|
How to preserve personal settings between R1CBU firmware upgrades?
I have a question... I upgraded to v0.28 and love it a lot. But every time I upgrade I have to redo all my settings. I understand that there's a way to backup and then reload my settings... Someone suggested backing up ¡°data¡±? Can somebody give a summary on how to do that? Would be grateful... redoing it every time is no fun.
73, Randy K7RAN
P.S. I previously buried this question in a barely-related thread and got no traction, so I thought it better to create a topic.
|
Firmware 1.1.9 - lower Buttons problem
Yesterday I updated to firmware 1.1.9 but now the lower buttons have a malfunction. If I press RADIO SETTING1 the SYSTEM SETTING menu appears.. if I press EXIT .. the RADIO SETTING1 menu appears regularly. If I press RADIO SETTING2 the MEMORY menu appears.. if I press EXIT RADIO SETTING2 appears regularly. Unfortunately, as regards the CW menu (KEY button) now the two buttons on the left do not work correctly and I cannot change the type of button or speed. If instead I connect a mouse to the USB port and select the various menus from the display .. everything works regularly. I also tried to do a FACTORY RESET and return to the old firmware (1.1.7) but the problem remains. Has this happened to anyone of you?
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Tonight I figured out that the problem with the soundcard not being identified as 'alsa.platform-sound' was actually a problem due to udev (which in buildroot is implemented by 'eudev') where one of the rule files: '78-sound-card.rules' had a line that made it skip assigning ID_PATH and ID_PATH_TAG to the platform sound card. The offending line was introduced by this commit:
Reverting that commit for that specific udev rule file (i.e. commenting out line 56 in '78-sound-card.rules') fixes the problem with the PulseAudio sound device name that I found over the weekend.
?
To work around the circular dependency between libsndfile and lame/mpeg123, I also created a new package called 'libsndfile-with-lame-and-mpeg13', which uses the same version number and all the other attributes of 'libsndfile' but has additional dependencies on lame and mpeg3:
This way the package 'libsndfile-with-lame-and-mpg123' gets built (and installed in the target directory) after lame and mpg123 have been built, and therefore has everything it needs to work with those libraries. I then made x6100-gui select the new 'libsndfile-with-lame-and-mpg123' package.
?
I just committed these two changes to the x6100-buildroot repository:
?
73,
Franco
|
Re: Radio gets noise on RX when on Battery Alternative Firmware v0.28.0
I have seen this problem on my x6100 from day one with all of the software versions I have used?
This is a hardware design issue. I just live with it?
On Tuesday, December 17, 2024, 5:49 PM, Roberto - YS1RS via groups.io <ys1rs@...> wrote: The problem is that I have that strong noise you saw on the video in all bands and, when moving the VFO, both signals, the one at the beginning of the band width shown in the screen and the one at the end, both follows the movement up or down. Those two are always present on the screen, no matter which band you are on. Again, this only happens when on battery and only when the alternative firmware is in use.
?
73
Rob
YS1RS
|
Re: Radio gets noise on RX when on Battery Alternative Firmware v0.28.0
The problem is that I have that strong noise you saw on the video in all bands and, when moving the VFO, both signals, the one at the beginning of the band width shown in the screen and the one at the end, both follows the movement up or down. Those two are always present on the screen, no matter which band you are on. Again, this only happens when on battery and only when the alternative firmware is in use.
?
73
Rob
YS1RS
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
On Tue, Dec 17, 2024 at 04:13 PM, Franco Venturi wrote:
the issue with libsndfile and lame (and mpeg123) is that in buildroot lame has a dependency on libsndfile (), so that when both BR2_PACKAGE_LAME=y and BR2_PACKAGE_LIBSNDFILE=y, then buildroot builds libsndfile first (which gets built without lame) and then lame (because of that dependency). I haven't looked at mpeg123, but I suspect there might be something similar going on there too.
I know, but I thought there is a better solution.
--
Georgy // R2RFE
|
Hi Gang,? ?I'm loving the R1CBU et al firmware running on a memory card.? Since I started playing with it I've logged 288 FT8 contacts.? It's surprising what 5 watts can do and it will be great for POTA and other uses.? No extra toys other than an antenna required.
Thanks to all who worked on this project and continue working.
?
73, Gregg W9DHI
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Markus,
thanks for reporting the problem with FT8 TX. Last night I started looking at why in the new buildroot the sun8i-a33-audio soundcard gets reported as 'alsa_card.0' instead of 'alsa_card.platform-sound' like in Georgy's buildroot. Hopefully when I figure that out, I'll also be able to explain the problem with TX. I am starting to see that the Linux sound system is rather complex.
?
Frank,
thanks for the nice words. Unfortunately I don't have a GSOC and my free time is very limited these days, so I won't be able to help you much, but hopefully someone else with a GSOC can take a look at what we found out and did so far and figure out the changes to make it work with the GSOC. Also I suspect that most of this work applies to the new X6200 as well - I am not in that group but hopefully someone there is already making progress on something similar for the X6200.
?
Georgy,
the issue with libsndfile and lame (and mpeg123) is that in buildroot lame has a dependency on libsndfile (), so that when both BR2_PACKAGE_LAME=y and BR2_PACKAGE_LIBSNDFILE=y, then buildroot builds libsndfile first (which gets built without lame) and then lame (because of that dependency). I haven't looked at mpeg123, but I suspect there might be something similar going on there too.
?
73,
Franco
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Hi Franco,
unfortunately I had not tested everything with ft8, the transmission does not work, there is no sound on the signal.
?
?
73 de Markus, DB2ZW
|
Re: Setting FT8 with firmware v0.28.0
Have you set up your callsign AND your locator ?
Regards Dave G4UFS
toggle quoted message
Show quoted text
On 16 Dec 2024, at 15:13, HB9FBG via groups.io <hb9fbg@...> wrote:
?
Hello, everyone,
I need a little help.
To be honest I've only been using the x6100 on CW but as I'll probably be taking a few days holiday I'd like to do FT8 with firmware v0.28.0. I have everything configured and everything seems to work very well in reception... but I can't get it to transmit.
It doesn't seem to take the impulse to go to transmit (the TC tag appears).
I guess it's stupid but I've tried several ways and can't get it to transmit.
I also looked for a manual but couldn't find it
Thanks in advance for any indication
73
Mauro HB9FBG
|
Setting FT8 with firmware v0.28.0
Hello, everyone,
I need a little help.
To be honest I've only been using the x6100 on CW but as I'll probably be taking a few days holiday I'd like to do FT8 with firmware v0.28.0. I have everything configured and everything seems to work very well in reception... but I can't get it to transmit.
It doesn't seem to take the impulse to go to transmit (the TC tag appears).
I guess it's stupid but I've tried several ways and can't get it to transmit.
I also looked for a manual but couldn't find it
Thanks in advance for any indication
73
Mauro HB9FBG
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Franco and others,
?
Thank you all for your work on improving the abilities of the x6100 hardware. It is much appreciated!
?
A wish for the New Year: similar efforts applied to the GSOC device, now gone into non-supported mode by Xiegu.
?
73,
?
Frank
K4FMH
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Hi Georgy,
you are right, the recorder does not work.
I build it again with your workaround and now the recorder works.
?
73 de Markus, DB2ZW
|
Re: Problems charging internal battery / R1CBU/R2RFE firmware
Thanks to all for your suggestions! Everything very interesting!
?
My X6100 still has a valid warranty so I'll try Radioddity first before opening the seals...
We'll see and I'll let you know about every good solution.
?
Tnx again and a merry xmas - Uli / DK9TZ
?
?
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Hi.
Could you also check recorder functionality? Previous version of buildroot built libsndfile without LAME/MPG123 support, event if these packages was selected. I used as a workaround.
Wonder, if it fixed in the new buildroot?
--
Georgy // R2RFE
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Hi Franco,
with this patch CW Decode and FT8 is working again.
?
For me, I like it when a newer buildroot is used, because the currently used one needs e.g. patches to work with actual Compilers, here gcc-14.2
Thanks for your work.
?
And of course thanks to all the people you have already mentioned here to make the x6100 a better device.
?
73 de Markus, DB2ZW
|
Randy K7RAN
Roberto - YS1RS
W9DHI, Gregg Lengling
HB9FBG
Frank K4FMH