Welcome to the Rockbox Technical Forums!
Not playing any audio in the fallback image is entirely expectedIt contains no codecs, so playback isn't actually possible in the fallback image at all. It exists only to facilitate USB access.
Additionally, restoring with iTunes and starting from scratch will do exactly nothing that formatting the storage volume didn't. It is functionally identical to doing so, except with a lot of needless steps in between.
It also pays to note that updating emCORE is relatively needless and offers very little.Especially if it was working perfectly as intended beforehand.
The current development image, as of this writing, behaves exactly as intended.
Quote from: [Saint] on October 06, 2014, 01:12:44 AMAdditionally, restoring with iTunes and starting from scratch will do exactly nothing that formatting the storage volume didn't. It is functionally identical to doing so, except with a lot of needless steps in between.I assumed this but as it was an ATA error and my searches turned up a few posts regarding these errors when changing or upgrading a HDD (not the iPod, other devices), my instinct was to get it back to stock to make sure that the hardware was functioning.
Quote from: [Saint] on October 06, 2014, 01:12:44 AMIt also pays to note that updating emCORE is relatively needless and offers very little.Especially if it was working perfectly as intended beforehand.Was just my thinking of the relationship between bootloader and installed software. Newer SW = Newer BL. Spend a lot of time tinkering with my Nexus devices and on certain software updates you need a newer BL and/or Radio to get it working.
Quote from: [Saint] on October 06, 2014, 01:12:44 AMThe current development image, as of this writing, behaves exactly as intended.It isnt a working dev build then its just to reproduce ATA Error -2147483542? Is this one of the unlogged changes as I didn't see anything in the tracker, forums, Google etc.
The fallback image behaviour you described in your initial post already verified that the hardware was functional.
Were this the case, we would make it known to you.We could easily check for version mismatch between bootloader and binary and prompt the user, but this is not the case.You seem to have misunderstood....
...Simply "failing" is not an accurate way to describe their behaviour, it is a prolonged suicide attempt beginning with the very first time the device is powered on.They're killing themselves.
So, for the rare chance anyone has the same error and finds this via Google, try booting to the fallback image and trying some older version.
ATA Error -2147483542
ATA error: -2147483542Press ON to debug
Data abortat 080536C0FSR0xF7(domain 15, fault 7)address 0xA4B18C1C
Page created in 0.082 seconds with 17 queries.