Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
FlynDice:
I posted FS#10270 dbop_button_lcd_delays.patch which adds some dbop related delays into the e200v2 Button & LCD drivers. I believe the lcd delay fixes the "white screen" failures we've been seeing and the button delay will hopefully fix the spacerocks bug at low pclk settings. I will accept a big "I told you so" from kugel on the button delay even though he was nice enough not to say so... :P I believe the lcd delay is not present in the e200v2 OF but is in the fuze OF lcd driver.
funman:
--- Quote from: fuflo on June 02, 2009, 08:51:29 PM ---
--- Quote from: matsch on June 02, 2009, 06:15:58 PM ---OLED Driver of my Clip is supplied by as3514 DCDC. Screen is now bright with code above and X = 0x10. Will test other values for X. Thanks for the tip.
--- End quote ---
i can confirm this as well. i also have european clip v1 without FM. i'm not much of a developer, especially with this low level coding, but i can help test patches :)
--- End quote ---
Can you confirm that you have no radio chip (radio not detected by rockbox) ?
You can check in debug menu -> FM radio.
Perhaps this is the way to detect the Clips which needs this special screen powering.
fuflo:
--- Quote from: funman on June 03, 2009, 03:16:58 AM ---Can you confirm that you have no radio chip (radio not detected by rockbox) ?
You can check in debug menu -> FM radio.
Perhaps this is the way to detect the Clips which needs this special screen powering.
--- End quote ---
yeah, debug menu says "hw detected: no"
funman:
I thought that all Sansa AMS had a FM radio chip built in, and that it was disabled by software.
Probably because it was simpler to have only one board design, and so they avoided to pay taxes for devices using FM reception.
Sandisk released "different" firmware upgrades by providing identical files with a one letter extension indicating region and FM chip presence.
Recently they released firmwares for "all regions" (at least 0x.01.32 , last Clip firmware available today).
So I suppose (without proof) that they built newer boards without a FM chip, and that on these new boards they changed the way the LCD screen is powered. My 2 disassembled clips are "ver 1.5", and the Clip disassembled by anythingbutipod is "ver 1.3".
Note : the OF (verified v29, 30, 32) sets the DCDC15 register to 1, in its lcd_enable() implementation, so if we can't identify models which need this powering we would only "waste" 1.25mA on models which don't need it.
@fuflo & matsch : is your LCD functional when setting the register to 1 ? Is there any visible difference with higher values (up to 31 == 0x1f) ?
If you have disassembled your Clip (if you didn't, no need to open it), what's the hardware revision printed on the board? (between the home button and the directional keypad)
fuflo:
well i tried 0x1, 0x11 and 0x1f and didn't see any visual difference, works with all of them.
my clip was manufactured in 2007 but i don't know what's the revision of it.
the serial/model no. on the box is: SDMX11N-2048K-E70, maybe that helps
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version