Recent Posts
11
Hardware / Re: AIGO EROS Q / AIGO EROS K / IRULU Surfans F20 / AGPTek H3 / HIFI WALKER H2
« Last post by kylemsguy on December 01, 2024, 08:02:42 PM »Not sure if anybody's mentioned this yet, but I recently managed to install the native port on a Hifi Walker H2 v2.0 using the hw4 bootloader. Seems like nothing important's changed since v1.9.
I've also emailed the manufacturer asking for an upgrade package. Will report back if they get back to me.
I've also emailed the manufacturer asking for an upgrade package. Will report back if they get back to me.
12
Hardware / Re: AIGO EROS Q / AIGO EROS K / IRULU Surfans F20 / AGPTek H3 / HIFI WALKER H2
« Last post by dconrad on December 01, 2024, 10:44:51 AM »Native Port users:
I haven't updated this thread in a while, so I should probably do so - there's some churn in the codebase going on at the moment with these devices that may require updating bootloaders. This is to hopefully get these devices to a genuine "Stable" state.
Hardware 4 devices are now supported on native, please see the wiki page for the bootloader update file and grab the latest daily build. https://www.rockbox.org/wiki/AIGOErosQK
Due to some changes needed to support hardware 4, early players (hw1, hw2) may need an updated bootloader if the current one was installed before hw3 was introduced. If you update rockbox and get just a white screen at boot, you'll need to do so. You can boot into the bootloader's menu with (Pwr + VolUp), go into USB mode and put the correct update.upt file on the card, and then run the Aigo Recovery system and the new build should now work.
We're reworking the hw1/hw2 bootloaders slightly in preparation to hopefully get this player to a genuine "Stable", so please keep an eye on this patchset: https://gerrit.rockbox.org/r/c/rockbox/+/6132. When it gets merged, the check for the newer DAC with hardware volume scaling will be moved to the bootloader. I believe this should only really affect hw2 units - when this gets merged, hw2 units may fall back to using software volume until they get their bootloader updated.
Also please keep an eye on this patchset: https://gerrit.rockbox.org/r/c/rockbox/+/6133. It will allow you to manually select headphone or line output. The default is the current operation, automatic detection. Jack detection for automatic play/pause on plug and unplug will not work if the output is manually selected.
Also, if we ever get a new rbutil release, the native port will become the default for these players. The hosted port will still be there, you'll just need to go into the settings and enable "disabled" players. I think it will be rbutil version 1.5.2.
I haven't updated this thread in a while, so I should probably do so - there's some churn in the codebase going on at the moment with these devices that may require updating bootloaders. This is to hopefully get these devices to a genuine "Stable" state.
Hardware 4 devices are now supported on native, please see the wiki page for the bootloader update file and grab the latest daily build. https://www.rockbox.org/wiki/AIGOErosQK
Due to some changes needed to support hardware 4, early players (hw1, hw2) may need an updated bootloader if the current one was installed before hw3 was introduced. If you update rockbox and get just a white screen at boot, you'll need to do so. You can boot into the bootloader's menu with (Pwr + VolUp), go into USB mode and put the correct update.upt file on the card, and then run the Aigo Recovery system and the new build should now work.
We're reworking the hw1/hw2 bootloaders slightly in preparation to hopefully get this player to a genuine "Stable", so please keep an eye on this patchset: https://gerrit.rockbox.org/r/c/rockbox/+/6132. When it gets merged, the check for the newer DAC with hardware volume scaling will be moved to the bootloader. I believe this should only really affect hw2 units - when this gets merged, hw2 units may fall back to using software volume until they get their bootloader updated.
Also please keep an eye on this patchset: https://gerrit.rockbox.org/r/c/rockbox/+/6133. It will allow you to manually select headphone or line output. The default is the current operation, automatic detection. Jack detection for automatic play/pause on plug and unplug will not work if the output is manually selected.
Also, if we ever get a new rbutil release, the native port will become the default for these players. The hosted port will still be there, you'll just need to go into the settings and enable "disabled" players. I think it will be rbutil version 1.5.2.
13
Rockbox General Discussion / Re: HIFI Walker H2 hw3 aux plug not working
« Last post by dconrad on December 01, 2024, 10:26:57 AM »Please keep an eye on this patchset: https://gerrit.rockbox.org/r/c/rockbox/+/6133
When it gets merged, it will add a setting to allow you to manually select the output mode.
When it gets merged, it will add a setting to allow you to manually select the output mode.
14
Starting Development and Compiling / Re: rockboxdev.sh doesn't seem to run on Mac OS?
« Last post by rockbox_dev123 on November 30, 2024, 09:38:57 PM »Major version bumps in these libraries could introduce codegen differences versus what's already in use, I don't want to bump those requirements for consistency's sake.
(They're already bumped as part of the GCC 9.5 toolchain upgrade, but there are still some issues there)
Meanwhile, I've applied all of the other changes in a way that preserves the ability to build on Linux. Here's the patch; I'd appreciate someone making sure it actually works on MacOS too (after applying those two changes above manually)
I downloaded an archive of your patch from Gerrit and replaced tools/rockboxdev.sh and added the tools/toolchain-patches/apple_silicon.patch file.
I also did these manual changes:
Code: [Select]sed -i '' 's/mpfr-3.1.6/mpfr-4.1.0/g' ../tools/rockboxdev.sh
sed -i '' 's/mpc-1.0.1/mpc-1.2.1/g' ../tools/rockboxdev.sh
I can confirm that I am able to build the toolchain on macOS.
Looking forward to the eventual GCC 9.5 toolchain upgrade. But until then I am happy to be able to build and I'm aware that I should probably switch to rockbox built on Linux (with the correct mpfr and mpc versions) before submitting any bug reports.
Thanks to all for your work.
15
Starting Development and Compiling / Re: rockboxdev.sh doesn't seem to run on Mac OS?
« Last post by speachy on November 30, 2024, 08:26:10 PM »Code: [Select]sed -i '' 's/mpfr-3.1.6/mpfr-4.1.0/g' ../tools/rockboxdev.sh
sed -i '' 's/mpc-1.0.1/mpc-1.2.1/g' ../tools/rockboxdev.sh
Major version bumps in these libraries could introduce codegen differences versus what's already in use, I don't want to bump those requirements for consistency's sake.
(They're already bumped as part of the GCC 9.5 toolchain upgrade, but there are still some issues there)
Meanwhile, I've applied all of the other changes in a way that preserves the ability to build on Linux. Here's the patch; I'd appreciate someone making sure it actually works on MacOS too (after applying those two changes above manually)
https://gerrit.rockbox.org/r/c/rockbox/+/6134
EDIT: I'm 98% sure that the "hosted" (ie X / Y ) tooclchains will not build properly under MacOS, due to their reliance on having system libraries present.
16
Starting Development and Compiling / Re: rockboxdev.sh doesn't seem to run on Mac OS?
« Last post by chris_s on November 30, 2024, 03:26:40 PM »That's awesome! 
Can confirm this works for MIPS, too. An additional requirement in that case seems to be having gsed (GNU sed) installed and making sure it is used over the MacOS-provided one.
This has only been tested for the arm targets.
Can confirm this works for MIPS, too. An additional requirement in that case seems to be having gsed (GNU sed) installed and making sure it is used over the MacOS-provided one.
17
Starting Development and Compiling / Re: rockboxdev.sh doesn't seem to run on Mac OS?
« Last post by rockbox_dev123 on November 30, 2024, 12:33:33 PM »When I try to run tools/rockboxdev.sh on my M2 MacBook Pro running Senoma, I get no output from my terminal.For a little more info, this is becase tools/rockboxdev.sh has "set -e" on line 7. This means that Bash will exit immediately if (to simplify) a command fails. The failure and exit happens before anything is printed.
See here for more info.
As well as making many commits to update the toolchain, speachy has good advice:
Try running it with 'bash -x rockboxdev.sh' instead and see where it stops.
Another way to do the same thing is to change the "set -e" line to "set -ex" and we see that in this case, chris_s is right that the calls to readlink are failing:
replace readlink with greadlink
I have successfully compiled rockbox for an ipodvideo on macOS Sequoia 15.1.1
I'm listening to music on the device now, so it has worked.
I have provided some steps below that can be followed.
I assume you are already using homebrew.
This has only been tested for the arm targets.
Steps to compile the gcc cross compiler with clang on macOS (from the latest master):
Code: [Select]
mkdir -p build && cd build
sed -i '' 's/readlink/greadlink/g' ../tools/rockboxdev.sh
sed -i '' 's/mpfr-3.1.6/mpfr-4.1.0/g' ../tools/rockboxdev.sh
sed -i '' 's/mpc-1.0.1/mpc-1.2.1/g' ../tools/rockboxdev.sh
sed -i '' "s/CXXFLAGS='-std=gnu++03' run_cmd/CXXFLAGS='-std=gnu++03 -fbracket-depth=512' run_cmd/" ../tools/rockboxdev.sh
sed -i '' 's/"isl"/"gmp isl"/g' ../tools/rockboxdev.sh
sed -i '' 's%-/tmp%-$TMPDIR%g' ../tools/rockboxdev.sh
You can now run ../tools/rockboxdev.sh as normal e.g.:
Code: [Select]
../tools/rockboxdev.sh --target="a"
Personally, I prefer to put the compiled binaries in a custom directory and add it to PATH manually e.g.
Code: [Select]
rockbox_cross_compiler_dir=$HOME/some/path
../tools/rockboxdev.sh --target="a" --prefix="$rockbox_cross_compiler_dir"
export PATH="${rockbox_cross_compiler_dir}/bin:$PATH"
This has the benefit of not requiring root to build (as you don't need to access the default prefix directory /usr/local).
I haven't tested running ../tools/rockboxdev.sh as root, but it probably works.
Once you get to the compilation stage for gcc, it will fail.
cd into the build directory (this will be $TMPDIR/rbdev-build/build-gcc/ by default if you didn't specify --builddir to override).
You will need to manually apply the patch here to $TMPDIR/rbdev-build/gcc-4.9.4/gcc/config/host-darwin.c.
You can skip the patch changes to $TMPDIR/rbdev-build/gcc-4.9.4/gcc/config/aarch64/aarch64.h.
After patching, run make. Compilation takes a phenomenally long time on my M1 Macbook Pro. So instead of making a coffee, consider cooking some dinner!
After compilation finishes, run (sudo) make install.
Finally, you can now compile rockbox (optionally specifying the prefix if you used a custom one):
Code: [Select]
target="ipodvideo"
../tools/configure --target="$target" --type="n" --prefix="$rockbox_cross_compiler_dir"
make fullzip
You should now have a build/rockbox-full.zip !
EDIT: gcc compilation time:
Code: [Select]
real 25m6.665s
user 74m47.146s
sys 32m44.817s
18
Plugins/Viewers / Re: mapping unmapped keys/wheels?
« Last post by bubuz0 on November 30, 2024, 10:26:55 AM »..
19
Rockbox General Discussion / Re: USB multimedia Keypad Mode on 6g ipod classic
« Last post by speachy on November 30, 2024, 09:22:22 AM »i want to use my ipod as physical media controls for my pc, but when i plug it in it does nothing on the pc side, months back i done something on my pc to get it working, but since then ihave forgotten what i had done, and also reinstalled windows on the pc, grateful for any help
https://download.rockbox.org/daily/manual/rockbox-ipod6g/rockbox-buildch8.html#x15-1650008.6.12
20
Rockbox General Discussion / USB multimedia Keypad Mode on 6g ipod classic
« Last post by emeryvr on November 29, 2024, 05:59:46 PM »i want to use my ipod as physical media controls for my pc, but when i plug it in it does nothing on the pc side, months back i done something on my pc to get it working, but since then ihave forgotten what i had done, and also reinstalled windows on the pc, grateful for any help