Latest Rockbox WORKING on Nano

[oblib__]

I have found a valid fix for the Nano problem (at least on my Nano). There is a bit that needs to be set in the IDE config if the CPU is > 65 MHz. I added code to set and unset that bit. See http://www.rockbox.org/tracker/task/7510
Please test the patch:

Code: [Select]

Index: firmware/target/arm/system-pp502x.c
===================================================================
--- firmware/target/arm/system-pp502x.c (revision 15653)
+++ firmware/target/arm/system-pp502x.c (working copy)
@@ -178,6 +178,7 @@
       case CPUFREQ_MAX:
         CLOCK_SOURCE = 0x10007772;  /* source #1: 24MHz, #2, #3, #4: PLL */
         DEV_TIMING1  = 0x00000303;
+        IDE0_CFG |= (0x10000000); /* Set CPU > 65MHz bit */
 #ifdef IPOD_MINI2G
         MLCD_SCLK_DIV = 0x00000001; /* Mono LCD bridge serial clock divider */
 #endif
@@ -199,6 +200,7 @@
       case CPUFREQ_NORMAL:
         CLOCK_SOURCE = 0x10007772;  /* source #1: 24MHz, #2, #3, #4: PLL */
         DEV_TIMING1  = 0x00000303;
+        IDE0_CFG &=~(0x10000000); /* clear > 65MHz bit */
 #ifdef IPOD_MINI2G
         MLCD_SCLK_DIV = 0x00000000; /* Mono LCD bridge serial clock divider */
 #endif
@@ -229,6 +231,7 @@
 #ifdef IPOD_MINI2G
         MLCD_SCLK_DIV = 0x00000000; /* Mono LCD bridge serial clock divider */
 #endif
+        IDE0_CFG &=~(0x10000000); /* clear > 65MHz bit */
         PLL_CONTROL &= ~0x80000000; /* disable PLL */
         cpu_frequency = CPUFREQ_DEFAULT;
         PROC_CTL(CURRENT_CORE) = 0x4800001f; nop;
Index: firmware/target/arm/ata-pp5020.c
===================================================================
--- firmware/target/arm/ata-pp5020.c    (revision 15653)
+++ firmware/target/arm/ata-pp5020.c    (working copy)
@@ -44,7 +44,7 @@
 {
     /* From ipod-ide.c:ipod_ide_register() */
     IDE0_CFG |= (1<<5);
-    IDE0_CFG &=~(0x10000000);   /* cpu < 65MHz */
+    IDE0_CFG |= (0x10000000);   /* cpu > 65MHz */

     IDE0_PRI_TIMING0 = 0x10;
     IDE0_PRI_TIMING1 = 0x80002150;

File attached

Updated to fix dumb problems

Updated again to fix maraz's problem

[danhibiki]

Everyone who had trouble with newer revisions of Rockbox should test this fix by oblib__

Rockbox seems to be running fine now on my Nano, which was probably one of the most affected by this issue.

But, as always, more testing is needed, so I think everyone should try, even those who didn't have any problems with recent revisions.

For the developers, will this patch be commited to the SVN? Or it still is not considered a "proper" fix?

[Llorean]

We're not happy with not knowing the exact reason why this fix works or exactly what that bit is (The ">65 Mhz bit" name is a little vague, you understand) but at the same time, assuming testing shows that it doesn't cause any worse problems, it's incredibly likely that we'll commit this soon, as it seems likely it's either a proper fix or a step in the right direction.

Considering this seems to fix people who had problems with this problem even with 75mhz builds, it seems to be an actual solution, even if we're not entirely sure what's being solved at a lower level yet.

[first500]

Nano Fixed.  . Voicing Files and Directories Broken?

Thanks to all who worked on getting Nano up to date.  Having installed r15752, I can't seem to get file/dir voicing going.  I have the .talk files exactly as they were when they used to work ok, and checked that "Use Directory .talk Clips" and "Use File .talk Clips" are set to "Yes"

Am I missing something? (Nano, not me personally)

[Llorean]

Did you create the files recently, or are you trying to use old ones? We use speex for voicing now, and previously use MP3. Speex allows for higher quality (or smaller size) voice files.

[first500]

Hi Llorean.  Yes - these are not new files.  They are .mp3.talk files created using instructions posted on the site about a year ago.

I presume from your reply that these are no longer compatible.

[Llorean]

Nope. But the process hasn't really changed, honestly. The only difference is one of the utilities the script calls (rbspeexenc.exe instead of lame.exe) so if you managed it before, doing it again shouldn't be too difficult.

[first500]

Llorean - many thanks for the guidance.  Speech now working as before.

Good work by all involved in getting the Nano working.  My experience mirrors all who posted on the Flyspray thread.  And it is now working again quite happily in all respects.