Rockbox.org home
Downloads
Release release
Dev builds dev builds
Extras extras
themes themes
Documentation
Manual manual
Wiki wiki
Device Status device status
Support
Forums forums
Mailing lists mailing lists
IRC IRC
Development
Bugs bugs
Patches patches
Dev Guide dev guide
Search



Donate

Rockbox Technical Forums


Login with username, password and session length
Home Help Search Staff List Login Register
News:

Rockbox Ports are now being developed for various digital audio players!

+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Rockbox General Discussion
| | |-+  Sansa e260 wicked errors
« previous next »
  • Print
Pages: [1]

Author Topic: Sansa e260 wicked errors  (Read 2326 times)

Offline JoChn

  • Member
  • *
  • Posts: 32
Sansa e260 wicked errors
« on: March 18, 2012, 02:51:30 PM »
Hey,
maybe a week ago my player has started to display "data abort at (hex code)".
Earlier errors display when I was playing music and then I add some music to queue...
I've read few topics and I load stable version + new bootloader, and problems with adding music past.
I'm using 16Gb microSD card, and when I plug player (with card in) to computer I see (not always) that error:
[God dammit! Now I plug player 4-5 times and there is no errors]
Data abort
at 000609DC (0)
[Ok. Problem seems to appear when I turn off device, then turn on (wait until HDD stops working) then plug in it]
Good idea (I think) it is write the list with code errors, so people can see what's wrong when some data abort error appear.
Please help.
Logged

Offline Llorean

  • Member
  • *
  • Posts: 12931
Re: Sansa e260 wicked errors
« Reply #1 on: March 18, 2012, 02:54:49 PM »
That's not an error code, that's a memory address.
Logged

Offline JoChn

  • Member
  • *
  • Posts: 32
Re: Sansa e260 wicked errors
« Reply #2 on: March 18, 2012, 03:15:31 PM »
So is there any solution to get rid of that errors??
Logged

Offline demon_firefox

  • Member
  • *
  • Posts: 2
Re: Sansa e260 wicked errors
« Reply #3 on: March 18, 2012, 07:00:45 PM »
I've got exactly the same issue with my E280.
At the beginning Windows didn't recognizes the whole device if the 8GB SD-Card was plugged in.

Now I nearly get everytime the 000609DC "error" if I connect the Sansa to my PC even if the SD-Card isn't plugged in.

Could it be that either the USB-Cable is broken or the internal storage is somehow damaged?

Thanks in advance,
demon_firefox
Logged

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8974
Re: Sansa e260 wicked errors
« Reply #4 on: March 18, 2012, 07:18:31 PM »
What version, and does it happen if you try an older build?
Logged

Offline demon_firefox

  • Member
  • *
  • Posts: 2
Re: Sansa e260 wicked errors
« Reply #5 on: March 19, 2012, 06:38:07 AM »
Interesting. It seems to work much better now after I updated from 3.10 to the latest nightly version. I'll keep an eye on it and report if the issue still occurs in the near future.

Thanks a lot,
demon_firefox
Logged

Offline JoChn

  • Member
  • *
  • Posts: 32
Re: Sansa e260 wicked errors
« Reply #6 on: March 20, 2012, 01:51:13 PM »
If I want to load new build to sansa I must simply overwrite old version?? Or first delete old .rockbox folder and then load a new version?

edit.
Hey, there is another problem... my sansa won't start... Starting stops at rockbox logo with version build number.
When I try to start with (REC) pressed, it stops at "Scanning disk".
Few times it won't start, but after few attempts it start and I see menu, everything works exclude files and now playing. I've read something about it (about sansa Fuze freeze), but even if I plug my sansa to PC it freeze and nothing works... It means that my player died? Or maybe is there some solution to rescue it?
« Last Edit: March 22, 2012, 12:26:13 PM by JoChn »
Logged

  • Print
Pages: [1]
« previous next »
+  Rockbox Technical Forums
|-+  Rockbox General
| |-+  Rockbox General Discussion
| | |-+  Sansa e260 wicked errors
 

  • SMF 2.0.17 | SMF © 2019, Simple Machines
  • Rockbox Privacy Policy
  • XHTML
  • RSS
  • WAP2

Page created in 0.079 seconds with 14 queries.