Rockbox Technical Forums
Support and General Use => Hardware => Topic started by: qorx on June 26, 2016, 05:56:20 PM
-
Hi,
I'm unable to update my Clip+ from several builds back.
After updating either manually or with rbutil, an ATA error: -2 is shown in rolo. Latest builds all give same error so I reverted to the one I had as backup: c90d42d-160408 which runs fine.
This happens even with all default settings set.
Formatted, checked for file system errors and reinstalled everything again but nothing seems to get past the boot error unless reverting..
If I update to the latest build and replace "Rockbox.sansa" file with the one from my backup, it starts normally, no error shown.
saratoga said in irc that I'm the first to report this error, so as he suggested here's the forum topic.
-
I believe ATA error -2 just means that the storage couldn't be read. This is likely due to the recent changes to voltage and frequency scaling.
What was the oldest build you tried that did not work?
-
All builds from here: http://www.rockbox.org/dl.cgi?bin=sansaclipplus did not work, so I gave up and installed my backup but it seems that it was around May because the one I have is from 160408 and I've another from 160414 that also runs fine.
If you can get me some builds prior to the ones in that page, I can test more if you want.
-
We don't have download links for old builds, they must be compiled. Post the build number for the last build that worked correctly.
-
Hi,
here is the build that has all the voltage and frequency scaling (rockbox-sansaclipplus.18fecd9.zip 160422). All of my clip+es work fine with it.
https://app.box.com/s/tbii7up8i2btfgegqc3g624igv6yjx4n
Regards
johnb
-
saratoga, the last one that works in my Clip+ is: c90d42d-160408
johnb, thanks for the build upload, unfortunately the same error is shown with that build too.
-
The only substantial change between those builds is that we enabled voltage scaling, so here is the current git but with voltage scaling disabled:
http://mit.edu/mgg6/www/rockbox-c7a561e-noVoltage-clip+.7z
-
That one runs fine, thanks for compiling it. So it must be something with voltage scaling in my player.
How can I help debug?
-
saratoga: I think we should try slightly rise (48 - 50) CVDD1 at boost. If it help we can add special case for clip+ as we already have for clip zip at normal freq.
-
Here is a build with voltage scaling enabled but a slightly higher boost voltage:
http://mit.edu/mgg6/www/rockbox-clipplus-49-voltage.7z
-
Here is a build with voltage scaling enabled but a slightly higher boost voltage:
http://mit.edu/mgg6/www/rockbox-clipplus-49-voltage.7z
Same error as before
-
Here is a build with the unboosted voltage register increased from 22 to 25:
http://mit.edu/mgg6/www/rockbox-clipplus-25-voltage.7z
By the way, if you have a smartphone could you load a working build without voltage scaling, go to System -> Debug -> View IO Ports and then hit down until you see the screen with "CVDD2" on it and take a picture? I'm curious if your player has similar voltages as mine does.
-
That seems to fix it as it runs without any error anymore.
The "CVDD2" value fluctuates between 2705 and 2720
-
Can you try this one as well?
http://mit.edu/mgg6/www/rockbox-clipplus-23-voltage.7z
Your voltages look identical to mine at least.
Edit: If that fails, here is 24:
http://mit.edu/mgg6/www/rockbox-clipplus-24-voltage.7z
Lower will use less power, so its worth finding the minimum.
-
23-voltage is running ok, it gives an estimated 26h of battery :) Thank you!
I've tried 24 as well and it displayed 25h...
If the voltages are identical to yours, what may be causing the error on mine with a lower value? Any idea?
-
Let me know if 23 has any problems, I will commit if it's OK.
Could just be a little weaker flash memory chip.
-
I put my settings back on and got a panic, I'll have to check if it's the EQ...
-
That was with 23?
-
Yes it was.
-
Sounds like 24 might be needed then. I just want to be careful since this will decrease everyone's battery life by a little bit, but if devices are occasionally crashing, it should be fixed.
-
I've been trying to reproduce the error again because it occurred a few times earlier but then I reset and started playing with the settings one at a time, enabled/disabled EQ, changed themes and it's holding up.
Let me test it for consistency some more before you commit.
I'm with 23-voltage and noticed that CVVD2 now goes even lower/higher, it goes to 26xx something and 2730. CVDD1 is also lower than the previous picture I've uploaded, it's between 895/950 with peaks reaching 1xxx something (can't read it as it's too fast).
If it fails again with ata error -2 and/or *panic*, I'll go to 24-voltage and see if it's more stable.
-
saratoga, here's my findings:
23-voltage isn't stable enough for my player, it runs fine once, then it gives an error, then it runs fine, I've to reset and reinstall so it isn't usable.
24-voltage so far looks stable, so it may be the minimum for this player.
I've another Clip+ (a refurb) which was running a build from 2015, so prior to the frequency and voltage scalling patches.. Yesterday I updated it to rev 0f89b04 and runs stable and don't share any of the symptoms of the other one.
An issue I see on both players is a ~15sec delayed boot time showing the rockbox logo if a card is inserted, if I remove the card and boot again all is normal.
As for boot settings, I've both set up to boot right to the wps screen (Resume Playback)
The card is a 128GB if it means anything...
-
New update regarding the Clip+ with errors.
So, since running 24-voltage for a few days without any issues, it all come back again but happens randomly.
Installed build with 25-voltage and same thing, sometimes runs normally, sometimes error. I reset it and boot again, error... reset and boot again, error... boot into OF, shutdown and boot rockbox, no error... shutdown and boot again, error...
Guess I need to forget about voltage scaling with this unit..
-
Probably we should try also rise CVDD2 ( 0x80 | 115) with CVDD1=25.
-
Mihail, I can test it if you want.
-
Ok, try this: http://knk.square7.ch/rockbox-clipplus_25_115.zip
-
Thanks, will test and report back.
-
I'll be following this :)
I've run in to the exact same problem :P
I'm not much of a tester though; I wouldn't be knowing what I was doing xD
But know.. That you will have helped me too :D
-
Mihail, since the day you posted the build to today, I had only 2 occurrences of the ata error -2 at boot, one was the first time I installed your build and the second yesterday, but with both it was just a matter of resetting and boot again without problems, so it's more stable for sure.
Djudge_Katt, good to know I'm not the only one running into this issue. Thanks for reporting it.
-
Good, new build for test: http://knk.square7.ch/rockbox-clip_plus_25_116.zip
-
Thank you, installed and testing :)
-
Hi, I'm new here. :)
I just tried updating my Clip+ to the latest build offered by the Rockbox Utility, since I had a problem with playback stopping in the middle of files. Now I also have the ATA error shown in the picture.
The problem is I don't know how to go back to the latest stable (or any other) version, since the player is not recognized and therefore doesn't get a drive letter, so the Utility doesn't work anymore. I thought I had bricked it but this thread gave me new hope. How can I try the versions mentioned here or go back to stable? Thanks a lot!
-
Bitstream, boot the sansa firmware (hold left+power), then connect the player to the pc, save your settings configuration file "config.cfg" to the pc if you want to restore them later, delete the folder ".rockbox".
> download the last build Mihail posted
> move the folder .rockbox inside the .zip to the player
> safely unplug it from pc
> turn it off
> boot it (it'll boot rockbox again)
> run it and if any issues arise, report it to the devs.
edit: don't know if it was clear but do not use Rockbox Utility in this case
-
Thank you very much! :) This was already the second time I thought the Clip+'s days were over. The first time was about 2 years ago when the original firmware was always hanging at "Refreshing your media". It was only when I was looking for a new Sansa player that I learned of Rockbox, tried it out, and it gave it a second life. It's fantastic that people are still working on improved software for such an old player. Keep it up please!
-
no problem, glad you're enjoying it again :)
-
Unfortunately I keep having problems with the latest version posted. For example, I haven't been able to access the Clip+ as USB drive(s) anymore. This has always been slow for me (sometimes it took 10 mins until the drive names showed up, so I'm used to it), but now it doesn't work with neither Rockbox nor stock firmware. Sansa firmware again hangs on "Refreshing..." forever - even when I take out the SD card before boot. Booting Rockbox I have several problems, for example "Error accessing playlist control file". The database doesn't seem to work, I can only play by file. And playback sometimes "hangs" like a broken CD (short loop)...
So to put it short, I'd rather return to the stable version I've been using for years. While playback sometimes ended mid-track, it was stable otherwise. But I cannot change firmwares as long as the Clip+ doesn't show up as drive, can I? The drive letters sometimes appear, but with no content. Sometimes Windows reports "Device not recognized". Maybe there is something broken after all?
On a side note, if I were to purchase a new, affordable, tiny FLAC player that supports Rockbox (I read that new Sansas don't), what would be the recommendation?
Thanks!
-
Unfortunately I keep having problems with the latest version posted. For example, I haven't been able to access the Clip+ as USB drive(s) anymore. This has always been slow for me (sometimes it took 10 mins until the drive names showed up, so I'm used to it), but now it doesn't work with neither Rockbox nor stock firmware. Sansa firmware again hangs on "Refreshing..." forever - even when I take out the SD card before boot. Booting Rockbox I have several problems, for example "Error accessing playlist control file". The database doesn't seem to work, I can only play by file. And playback sometimes "hangs" like a broken CD (short loop)...
I think you have another issue (not directly related to freq scaling) - hardware or software problem with file system.
When player off - try hold select (middle button) and connect it to usb. Then try check disk for errors.
-
Thanks for the hint. I tried that but the drive keeps disappearing even during CheckDisk, also the checking takes very long... I made one last attempt to get the old firmware back onto it during a period where the drive was visible (in Bootloader mode, it appears sometimes at least), but it seems this only killed the bootloader - boot is now hanging at Rockbox logo... The periods where I see the real drive name SANSA CLIP have become shorter and shorter.
Maybe it's really time for a new player, the Clip+ has served me many years of daily use, and I'm not disappointed at all. Before that I already had a Clip, which I only sold because it didn't have an SD slot.
-
Try rebooting into the firmware and checking the disk for error.
-
I did that too in the meantime (been trying for 2 hours), the drive sooner or later always disappears during any operation. No matter if Checkdisk or trying to delete anything. MUSIC folder is corrupted, Rockbox folder is not. But trying to delete it (I'll just try anything now) I get an error about the files not being accessible.
Using the Utility I also get an error (with or without also installing bootloader) about drive not being writable, this seems to be the relevant part:
[rbutil\rbutilqt\base\utils.cpp:194 INFO] free disk space for "D:/" 154972160
[rbutil\rbutilqt\base\ziputil.cpp:80 INFO] extractArchive "D:/" ""
[rbutil\rbutilqt\base\ziputil.cpp:133 INFO] creating output file failed: "D://.rockbox/docs/sample.icons"
[rbutil\rbutilqt\gui\selectiveinstallwidget.cpp:195 INFO] continuing install with stage 2
[rbutil\rbutilqt\gui\selectiveinstallwidget.cpp:197 ERROR] Last part returned error.
Are there any players with Rockbox support still on the market that could replace a Clip+? Is the Clip Zip (still available from some sources) any good?
-
I did that too in the meantime (been trying for 2 hours), the drive sooner or later always disappears during any operation. No matter if Checkdisk or trying to delete anything.
Does the Sandisk firmware's reformat option work?
MUSIC folder is corrupted, Rockbox folder is not. But trying to delete it (I'll just try anything now) I get an error about the files not being accessible.
Using the Utility I also get an error (with or without also installing bootloader) about drive not being writable, this seems to be the relevant part:
If you can't access the disk there is no point in trying to copy over files with rockbox utility.
-
I did that too in the meantime (been trying for 2 hours), the drive sooner or later always disappears during any operation. No matter if Checkdisk or trying to delete anything.
Does the Sandisk firmware's reformat option work?
As stated above, I haven't been able to get into the Sandisk firmware since 2014, it always hung at "Refreshing your media", and still is. Booting Rockbox now says "File Not found..." and then "Plug USB cable". Which I've been doing all day. ;)
The reformat, can it also be triggered by button combinations?
MUSIC folder is corrupted, Rockbox folder is not. But trying to delete it (I'll just try anything now) I get an error about the files not being accessible.
Using the Utility I also get an error (with or without also installing bootloader) about drive not being writable, this seems to be the relevant part:
If you can't access the disk there is no point in trying to copy over files with rockbox utility.
The drive sometimes looks normal for short periods of time (appears with correct name and capacity in explorer and can be accessed), so I was trying to get it done during one of those, but it never lasted long enough. Most of the time, I see no drive name, no capacity... I'm no expert at all, but considering that USB access has been very slow for me for years, I'd guess something is wrong with the hardware?
-
Bitstream, sorry to hear you're running into issues.
Mihail, so far my player is working fine with build 25_116, I had only one time the ata error but I can see a pattern now and hope it helps in any way:
If I use it frequently I don't have any errors, however, if I let it sit for a day and then power it on, the ata error may appear. (it happened once so far)
-
Ok, try this: http://knk.square7.ch/rockbox-clip_plus_26_116.zip
-
Ok, try this: http://knk.square7.ch/rockbox-clip_plus_26_116.zip
Installed and ready to go testing.
-
Mihail, almost one week with daily use and no errors so far. Hope it continues that way as it seems we have reached stable status with build 26_116.
Thank you!
-
Good! Can you also test this build: http://knk.square7.ch/rockbox-clip_plus_26_115.zip ? After this we would know right way to fix and can commit changes to rockbox.
-
Sure. Installed and testing.
-
Good! Can you also test this build: http://knk.square7.ch/rockbox-clip_plus_26_115.zip ? After this we would know right way to fix and can commit changes to rockbox.
One week of daily use and no errors with this build too. :)
-
I commit this changes for Clip+ only. If someone have same problem on another AMSv2 (Zip, Clip v2, Fuze v2) player - let me know.
-
Hey Mihail, I saw your comment in another thread how to check the different versions of the player hw, in system > debug > view hw info
So, since I have 2 clip+'s and I only had the frequency scaling problem with one, here's both versions:
Clip+ without issues (AMSv2 Variant 1)
Clip+ that had the errors (AMSv2 Variant 0)
Hope it helps..
-
Yes, it useful: in this case we can rise voltage only for Clip+ variant 0 and have better battery life time for variant 1. I commit this checking.
-
Cool!
If you need any further testing, let me know.
-
I just faced the same problem when updating my Sansa+ from 3.13 to 3.14. Restored the older build and now everything is OK but is there a way to fix this as I want to use the new features and improvements?
-
I just faced the same problem when updating my Sansa+ from 3.13 to 3.14. Restored the older build and now everything is OK but is there a way to fix this as I want to use the new features and improvements?
Try this build: http://web.mit.edu/mgg6/www/rockbox-clip+-275v.7z
-
Same thing :(
-
Which exactly variant of clip+ you have (system > debug > view hw info)?
-
web.mit.edu/mgg6/www/rockbox-fef736be4ab1c2df33d15715badd6b5ff04c2285.7z
This build is right before frequency scaling was enabled. Does it work?
-
Which exactly variant of clip+ you have (system > debug > view hw info)?
It says AMSv2 variant 0
-
Try this: http://knk.square7.ch/rockbox-clipplus_v0_27.7z
-
Same results.
I'm replacing .rockbox folder with the new one - am I doing this right? After that Sansa shows the error and is not recognized by the computer anymore. I need to shut it down by holding power button and then boot the original firmware to show in Explorer and revert to v3.13.
-
Is build from saratoga post (http://web.mit.edu/mgg6/www/rockbox-fef736be4ab1c2df33d15715badd6b5ff04c2285.7z) work?
-
Yes, that version works.
-
http://knk.square7.ch/rockbox-clipplus_v0_28.7z
-
This again leads to ATA error 2 on startup.
-
http://knk.square7.ch/rockbox-clipplus_v0_30.7z
-
This works.
-
Good. Last test build: http://knk.square7.ch/rockbox-clipplus_v0_29.7z
-
Works. Few seconds after startup there was kernel panic but after restart everything seems to be fine.
-
Ok. It is not completely stable. So switch to previous build (http://knk.square7.ch/rockbox-clipplus_v0_30.7z) and check it for few days. If it stable, I'll commit this changes.
-
I just faced the same problem when updating my Sansa+ from 3.13 to 3.14. Restored the older build and now everything is OK but is there a way to fix this as I want to use the new features and improvements?
Try this build: http://web.mit.edu/mgg6/www/rockbox-clip+-275v.7z
I committed that patch today since it helped some people.
-
Good. I still don't have time to finish my work for CVDD2 scaling :(
-
Hi, I'm getting the same ATA error -2 on a Fuze v2, both with v3.14 and the latest dev build. Reverting to v3.13 fixes the problem.
If I'm reading the wiki correctly, Fuze v2 and Clip+ have the same SoC, so perhaps the same changes are needed?
-
Hi, I'm getting the same ATA error -2 on a Fuze v2, both with v3.14 and the latest dev build. Reverting to v3.13 fixes the problem.
If I'm reading the wiki correctly, Fuze v2 and Clip+ have the same SoC, so perhaps the same changes are needed?
Try this build: http://knk.square7.ch/rockbox-fuzev2_26.7z
-
Hi, I'm getting the same ATA error -2 on a Fuze v2, both with v3.14 and the latest dev build. Reverting to v3.13 fixes the problem.
If I'm reading the wiki correctly, Fuze v2 and Clip+ have the same SoC, so perhaps the same changes are needed?
Try this build: http://knk.square7.ch/rockbox-fuzev2_26.7z
I'm still getting ATA error -2 with that build
-
http://knk.square7.ch/rockbox-fuzev2_30.7z
-
http://knk.square7.ch/rockbox-fuzev2_30.7z
That one works. Thanks!
-
Which exactly variant of Fuze v2 you have (system > debug > view hw info)?
-
AMSv2 variant 0
-
OK. Thanks for report!
-
Thanks for looking at this, I have been away from my computer. What did you change to fix the problem? CVDD2?
-
I rise CVDD1 at low frequency. I not sure why sd controller (or nand) depend on CVDD1.
We have to many #ifdef for CVDD1 so I want define it in firmware/export/config/sansaclipplus.h and for other AMSv2. I'll post a patch for review in gerrit later.