Welcome to the Rockbox Technical Forums!
With recent revisions the radio of my e200 isn't working anymore.If I switch to radio mode it shows only the status bar on top and freezes then.After some investigation it seems that rev 21088 is messing something up.
You should try earlier revisions (bissecting) until you get display working, or perhaps tweak the delays in firmware/target/arm/as3525/sansa-clip/lcd-ssd1303.c
QuoteYou should try earlier revisions (bissecting) until you get display working, or perhaps tweak the delays in firmware/target/arm/as3525/sansa-clip/lcd-ssd1303.cMaybe 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.
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?
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.
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
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.
GPIOB_DIR |= 0x40; /* pin 6 out */GPIOB_PIN(6) = (1<<6);GPIOB_DIR |= 0x20; /* pin 5 out */GPIOB_PIN(5) = 0;
For any e200v2 users who are comfortable changing the frequency settings I have found that changing the frequencies in funman's latest mmu patch at FS#10048 to DRAM=PCLK=31 and DBOP = PCLK/1 solves a whole lot of problems for us right now until things get tested more! LCD works fine with these settings!#define AS3525_FCLK_FREQ 248000000 /* Boosted FCLK frequency */#define AS3525_DRAM_FREQ 31000000 /* Initial DRAM frequency */ /* AS3525_PCLK_FREQ != AS3525_DRAM_FREQ/1 will boot to white lcd screen */#define AS3525_PCLK_FREQ (AS3525_DRAM_FREQ/1) /* PCLK divided from DRAM freq */#define AS3525_DBOP_FREQ (AS3525_PCLK_FREQ/1) /* DBOP divided from PCLK freq */
But the menus seems to react slowlier than before and the wheel is not very reliable in spacerocks and pictureflow (spacerocks at all and pictureflow on fast turns).
I can confirm that unboosted the UI responsiveness is suboptimal.I hope we can find a setting for ~40-45MHz for unboosted (that would also let run mp3 unboosted).
Page created in 0.381 seconds with 17 queries.