Rockbox Development > New Ports
TempoTec V3
7o9:
If you are looking at a hosted port (Rockbox app on top of Linux) the other hosted ports are good for inspiration. Surfans F28 is the most recent.
Also, if you are looking at a hosted port, any FPGA stuff might not be relevant as the existing Linux firmware has drivers for all hardware. If you are looking at a native port, it will probably be very relevant.
Tempotec v3 Blaze run Linux-4.4.94+, which seems the platform for the X1600E HiBy firmware devices.
Flipp3rix:
--- Quote from: 7o9 on June 09, 2025, 03:21:42 AM ---If you are looking at a hosted port (Rockbox app on top of Linux) the other hosted ports are good for inspiration. Surfans F28 is the most recent.
Also, if you are looking at a hosted port, any FPGA stuff might not be relevant as the existing Linux firmware has drivers for all hardware. If you are looking at a native port, it will probably be very relevant.
Tempotec v3 Blaze run Linux-4.4.94+, which seems the platform for the X1600E HiBy firmware devices.
--- End quote ---
I'm talking about native porting, also because I don't think there's a way to run the rockbox applet on the tempotec right now. Also, does it make sense to talk about the V3 Blaze here? I understand that it's a revision of the original V3-A, but I think we have to get there step by step (keeping in mind that many people on headfi were unhappy with it). Then, if there are elements like the aforementioned *.ko files that can help with the development of the V3-A too, that's another matter :D
vitt13:
--- Quote from: Flipp3rix on June 08, 2025, 04:36:11 PM ---But I understand that it is relatively simple, also because I imagine that the sequence of steps to get to the porting is something like:
--- End quote ---
I think those will be last steps.
I'm not good in programming but I watched for developing FiiO M3K native port steps because I own this DAP.
amachronic done a lot of work to allow use the general code in future X1000/E based ports.
* it needs to port bootloader
* it needs to know about key mapping, LCD driver and GPIO. There is guide howto find out that from RE kernel image https://forums.rockbox.org/index.php/topic,53896.0.html (it starts here https://forums.rockbox.org/index.php/topic,53601.msg248763.html#msg248763 )
My guess about useful *.ko from V3 Blaze fw was just guess to simplify this step of RE kernel image. And may be irrelevant if hardware is different in real.
V3-A has not enough hardware keys to control Rockbox without touchscreen so it will be hard to do everything touch-controlled.
Even Surfans F28 hosted port has struggled with touchscreen use
--- Quote from: speachy on May 06, 2025, 10:07:33 AM ---
--- Quote from: speachy on May 05, 2025, 10:12:58 PM ---(Audio works but is quite distorted, rotary wheel isn't working yet, very crude keymap, touchscreen hooked up but not being utilized, no plugins enabled, etc etc etc..)
--- End quote ---
The rotary wheel now works, audio quality (and volume control) fixed. Given that I have no desire to use a touchscreen-based player like the F28 myself, I don't have the patience to rework the very crude global keymap to incorporate the touch screen, implement keymaps for the bajillion plugins, and tweak the default theme to be less ... BIG.
--- End quote ---
And what about hosted port there is the answer
--- Quote from: speachy on April 08, 2025, 09:39:54 PM ---All of the non-Android Hiby devices (and many more from other manufacturers) are built on the same underlying software framework ("hibyos"), with the messy details nearly entirely handled by custom, per-device kernel drivers and existing platform daemons+scripts.
Rockbox has already been ported to multiple hibyos devices. To port it to another one just needs to handle:
* Display properties
* Button layout
* Audio output switcher and mixer names
* Power management properties (battery and charging device names, plus discharge curves)
--- End quote ---
--- Quote from: speachy on April 09, 2025, 06:46:36 PM ---
--- 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 ---
Navigation
[0] Message Index
[*] Previous page
Go to full version