Welcome to the Rockbox Technical Forums!
I'd like to Rockbox the D2+ but note that the D2 port is currently unstable. Given that the D2 seems to be making way for the D3, what are the chances of the port progressing to a stable state and further developed?Also, just how usable is the unstable build, and is there any risk associated with installing it at this point? Is it correct that I will need to get an SD card if I want to be able to save any changes I make to Rockbox (should I install it) at this point?
wouldn't it be more effective to find out about the exact shematic? Look for some defect D2s or buy one (everyone interested spents a few $) or even use the own one cautiously and disassemble it (like the guys from anythingbutipod)? Measure each pin of a chip with an ohmeter and look where it is connected to and during that tipping the information into Eagle layout designer?
I am curious: there were so many hours and days of work spent on backwards-engineering the D2 by disassembling the firmware; wouldn't it be more effective to find out about the exact shematic? Look for some defect D2s or buy one (everyone interested spents a few $) or even use the own one cautiously and disassemble it (like the guys from anythingbutipod)? Measure each pin of a chip with an ohmeter and look where it is connected to and during that tipping the information into Eagle layout designer?
1) Not every component in a given player has a public datasheet, or can even be identified at all. It doesn't help to know how something is connected if you don't know what it *is*.
3) Testing with an ohmmeter doesn't actually guarantee there's a plain trace between two things.
4) You have to basically destroy the player to be able to get anything like a full picture, since there's no other way to get to the contacts of a BGA package
5) It's really time-consuming and tedious. It's not at all guaranteed to be faster than disassembling the firmware...Occasionally it's useful to know how certain things are connected (e.g. GPIOs that have no obvious function) and someone will investigate the hardware, but generally a schematic would add little value, and it's really not as easy to produce one as you suggest.
About 99% of the interesting stuff is all on the main system on a chip, so the traces wouldn't tell you much.
You mean, it's in the software for the TCC processor?
What I mean is: there are people in this forum speaking about building an own DAP dedicated for rockbox (which is amazing!)What would be the difference between this player and the D2? Isn't it, that you know every connection and the intention of every single part?
guys in the last few weeks I cant use new rockbox builts, mostly they don't boot any more, can anyone give me a clue what to do ?!
There's no reason why this behaviour would have changed between r27860 and r27864, so the problem is not "fixed" - it's just not manifesting itself at the moment. r27646 did change some drivers, but the code changes are trivial and won't have caused the problem.I think these kind of issues started happening intermittently after the build was switched to the EABI compiler - I've also seen reports of strange things like one or both earphones sometimes not having any sound.But at the moment I don't have the time to investigate and fix it, unfortunately.
But at the moment I don't have the time to investigate and fix it, unfortunately.
Do you know at which point / in which driver it fails?
Revision 27090 is what I'm using, and have been using since whenever it was it was committed. I've tried various times to update to newer builds, but I've intermittently experienced one of the following:1) Freezing on a black (but backlight on) screen immediately after the bootloader2) Muted audio, despite all functions seemingly working fine3) Audio heavily panned to one channel, output volume lower than usualUsually hard-resetting (holding power switch for 10 seconds), then switching on again worked to get it to boot normally, but sometimes it would require several of these reset cycles before it would work, "several" ranging from 1 to 20.This frustrated me enough to revert to an older build, in my case 27090.
Page created in 0.225 seconds with 67 queries.