Rockbox Development > New Ports
HiBy R3Pro Saber 2022
7o9:
You make it sound relatively easy.
I have tried (failed) to repack the firmware for the HiBy R1 in an attempt to run something custom on it.
The information in the list you provide would be enough for a hosted port?
I am sure I can provide most of that for the R1 based on disassembly of the firmware/driver .ko’s. All drivers are provided as modules and decompile very well.
speachy:
--- Quote from: 7o9 on April 09, 2025, 10:34:08 AM ---You make it sound relatively easy.
--- End quote ---
It is, relatively. :D
--- Quote from: 7o9 on April 09, 2025, 10:34:08 AM ---I have tried (failed) to repack the firmware for the HiBy R1 in an attempt to run something custom on it.
--- End quote ---
The usual reason for this failing is because you didn't extract (or repack) the firmware as root. If you don't, certain files will not end up with the correct permissions.
--- Quote from: 7o9 on April 09, 2025, 10:34:08 AM ---The information in the list you provide would be enough for a hosted port?
--- End quote ---
The AGPTek Rocker was the first port to hibyos, and the X3II, X20, and hosted ErosQ/K ports were relatively minor tweaks from there.
You only need to build enough to get the "bootloader" (ie a glorified boot menu) to build, for this you need to have the basic display stuff (eg dimensions, resolution) and how to map the various buttons (ie /dev/input*) into something useful. Next you'll need to figure out power management and how to talk to the audio hardware, and from there you should be able to do a plugin-less build. Getting the plugins building will require creating keymaps for many (if not most) of them. It's still a bit of work, but far, far less than a native port would be.
--- Quote from: 7o9 on April 09, 2025, 10:34:08 AM ---I am sure I can provide most of that for the R1 based on disassembly of the firmware/driver .ko’s. All drivers are provided as modules and decompile very well.
--- End quote ---
To create a new native port, you need to effectively reverse-engineer the hardware schematic to figure out how things are connected. Disassembly of the original firmware can help with that, and of course it should hopefully be able to tell you how to talk to some of the custom hardware. FWIW it's possible (if not likely) that the FPGA stuff is handled by the bootloader before Linux ever starts.
( See https://www.rockbox.org/wiki/NewPort )
Milardo:
--- Quote from: speachy on April 09, 2025, 06:46:36 PM ---
--- Quote from: 7o9 on April 09, 2025, 10:34:08 AM ---You make it sound relatively easy.
--- End quote ---
It is, relatively. :D
--- Quote from: 7o9 on April 09, 2025, 10:34:08 AM ---I have tried (failed) to repack the firmware for the HiBy R1 in an attempt to run something custom on it.
--- End quote ---
The usual reason for this failing is because you didn't extract (or repack) the firmware as root. If you don't, certain files will not end up with the correct permissions.
--- Quote from: 7o9 on April 09, 2025, 10:34:08 AM ---The information in the list you provide would be enough for a hosted port?
--- End quote ---
The AGPTek Rocker was the first port to hibyos, and the X3II, X20, and hosted ErosQ/K ports were relatively minor tweaks from there.
You only need to build enough to get the "bootloader" (ie a glorified boot menu) to build, for this you need to have the basic display stuff (eg dimensions, resolution) and how to map the various buttons (ie /dev/input*) into something useful. Next you'll need to figure out power management and how to talk to the audio hardware, and from there you should be able to do a plugin-less build. Getting the plugins building will require creating keymaps for many (if not most) of them. It's still a bit of work, but far, far less than a native port would be.
--- Quote from: 7o9 on April 09, 2025, 10:34:08 AM ---I am sure I can provide most of that for the R1 based on disassembly of the firmware/driver .ko’s. All drivers are provided as modules and decompile very well.
--- End quote ---
To create a new native port, you need to effectively reverse-engineer the hardware schematic to figure out how things are connected. Disassembly of the original firmware can help with that, and of course it should hopefully be able to tell you how to talk to some of the custom hardware. FWIW it's possible (if not likely) that the FPGA stuff is handled by the bootloader before Linux ever starts.
( See https://www.rockbox.org/wiki/NewPort )
--- End quote ---
Looking at the Hiby R1, it has some sort of "developer mode" ?
https://www.amazon.com/HiBy-Bluetooth-Certified-Touchscreen-Expanded/dp/B0DKTF38HX?th=1
Would that help in getting rockbox on that player?
Also, would the touchscreen pose any large problems since there aren't physical buttons for mapping? I don't know of any player that is touchscreen based that is rockbox compatible, maybe there is a cowon one?
It would be nice to have more options for rockbox compatible players especially since the Hiby R1 is lower priced than AIGO EROS Q / AIGO EROS K / IRULU Surfans F20 / AGPTek H3 / HIFI WALKER H2
7o9:
The ‘developer mode’ is nonsense, all it does is let you raise the volume limit. There is nothing ‘developer’ about it.
The R1 has a touchscreen but also physical buttons on the side.
The Shanling Q1 is a touch screen device that runs Rockbox great.
Navigation
[0] Message Index
[*] Previous page
Go to full version