Rockbox Development > New Ports
SanDisk Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2
mc2739:
I have added FS#10267 to address the FM radio problem. The patch increases the fm_delay(). The radio now functions properly on my e200v2.
kugel.:
--- Quote from: FlynDice on May 31, 2009, 04:08:58 AM ---Can't resist a new toy and I'm a visual type-o- guy so just to show what's possible once we figure this darned mmu thing out I got some screen shots to show you. Its running on 192/32/32 with mmu and both caches enabled, and as you can see it's only boosting 10% of the time and averaging a bit more than 48MHz while playing an mp3 file. You can see a bit of corruption in the screen but funman's last patch corrects this. Playback with cached memory is still not working reliably for me though. One interesting thing I have found also is that for some reason if I use a plugin that has playback controls to start playback I get a much higher chance of music playing for more than 4-5 minutes. Another thing is that as long as I don't attempt to play music, Rockbox runs very well. I can play games all day long and when I hold the power button down to power off it has a normal shutdown. Once I play music on it though I end up having to hold the power button for 10 secs to force it to turn off. I was wondering if the fact that things run better when started from a plugin point to a buffer conflict with the plugin & audio buffers?
--- End quote ---
Great! Can you upload your diff of this very setup to FS#10048? I think we're not too far away from the goal! 500+% real time seems very reasonable too compared to other targets.
jago:
--- Quote ---I have added FS#10267 to address the FM radio problem. The patch increases the fm_delay(). The radio now functions properly on my e200v2.
--- End quote ---
Unfortunately it doesn't work for my e200v2 (clean r21151).
I've played around a little with the values for the delay loop. I tried values from 200 up to 2000 but there was no change. Strange that it works for m2739 but not for me.
matsch:
--- Quote ---Maybe my clip has a different OLED compared to others which needs a higher driver strength from SSD1303. How can I change the contrast or brightness to a higher value?
At least I can see the info on the screen with USB connected, but with very weak conatrast.
You can edit .rockbox/config.cfg and add a line:
contrast: 28
--- End quote ---
config.cfg did not help, also tweaking some parameters in lcd-ssd1303.c was not successful.
Perhaps my OLED needs a special initialization which the OF makes. Fact is that the screen works with very low contrast which is enhanced if the Clip is connected/powered by USB.
I do not have time to go into into the LCD driver basics and stay with the OF of the Clip.
funman:
--- Quote from: matsch on June 01, 2009, 10:31:31 AM ---Perhaps my OLED needs a special initialization which the OF makes. Fact is that the screen works with very low contrast which is enhanced if the Clip is connected/powered by USB.
--- End quote ---
I noticed the same effect when working on the Clipv2 LCD, before finding the required i2c magic.
Perhaps your screen is powered by some combination, and plugging it on USB delivers some current to it.
When I find some time I'll look at the OF again to see if we didn't forgot some combination.
By the way some GPIO pins settings were removed since they had no effect (at least on the Clips tested so far). You could try to add them back (one by one and then the 2 of them)
Just add these lines at the top of lcd_init_device() after ams3525_dbop_init() :
--- Code: ---GPIOB_DIR |= 0x40; /* pin 6 out */
GPIOB_PIN(6) = (1<<6);
GPIOB_DIR |= 0x20; /* pin 5 out */
GPIOB_PIN(5) = 0;
--- End code ---
And if one day you open your Clip, please write down the numbers written behind the LCD display (not that it would be useful anyway, but extra information can not harm!).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version