Thank You for your continued support and contributions!
vodi, it's probably the same problem that we've been talking about earlier: the lack of single-bit error correction. I presume that SD cards are quite capable of generating single-bit errors as well
Also this kind of New D2+ can only flash the FW of 3.11/2.11,even with the help of TCC Tool.Neither does the bootloader with SD Driver work.
Quote from: alfchin on August 11, 2009, 10:15:56 AMAlso this kind of New D2+ can only flash the FW of 3.11/2.11,even with the help of TCC Tool.Neither does the bootloader with SD Driver work.So you're saying for example that the D2+ firmware 3.02 doesn't work on your player? I think this might be the same issue seen here: http://iaudiophile.net/forums/showthread.php?t=30037Can you try shining a bright light at your D2+ and see if anything is visible with either FW 3.02 or Rockbox?If so we can be sure there are different variants of the D2+ that have different LCD backlight handling. If that's the case, someone will need to sit down with a disassembly of 3.02/3.11 and work out what the difference in backlight handling is...
Ok, so we know there's a difference in LCD and/or backlight handling in some newer D2+ units. Firmware 3.11 works with these as well as older players, so it obviously has a mechanism to detect and work with both types. Someone needs to do some disassembly to work out how this is done in the new firmware.I'd look into it myself, but I'm about to go away for 2 weeks and I already have plenty of other things to do before then!
r22284 implements ECC correction for files read from NAND, which should solve problems with tracks skipping unexpectedly when played from the internal memory.
Followers of this thread might be interested in a couple of recent changes:r22283 re-enables the SD driver, since there have been no more reports of damaged cards.r22284 implements ECC correction for files read from NAND, which should solve problems with tracks skipping unexpectedly when played from the internal memory.
That's pretty bonkers, I don't know what could cause that... maybe you could try to find if any particular track / combination of tracks triggers the problem?
Ok, I spent a couple of hours looking into this today and it looks like some new D2+ units have an entirely different power management chip, instead of the PCF50606 used by older D2+'s and the 'classic' D2.Looking at firmware 4.11+ (since that is what I use on my player) it shows some interesting changes almost straight away:- Follow the branch at 0x200000F8 (LDR PC,=0x20009BD4)- In older firmwares, the first call in this routine starts writing to the PCF50606 almost immediately (using I2C slave address 0x10)- In 4.11, this now tests the value of GPIOA6 (used for backlight control on older D2s) and stores a flag depending on its value- Depending on this flag, the next routine (at 0x200722E4) either calls the PCF50606 init routine (0x200BD1C8) or another init routine (0x200BDBE8)- The new init routine makes numerous I2C writes to slave address 0xE6, with completely different register addresses to the PCF chip.Similarly, the backlight control routine (0x20072320) checks this flag, and calls either the PCF routine (0x200BD5C4) or a new one (0x200BE19C). To control the backlight brightness, this new routine writes registers 0x28 and 0x29 to I2C address 0xE6.I don't know what this new chip is - anyone fancy opening their D2+ to find out? Although having said that, this disassembly should give us enough information to get Rockbox working eventually... it's just that I won't be around for the next couple of weeks to look into it.
Page created in 0.041 seconds with 21 queries.