Sansa Clip + USB issues

[oblivion]

Currently running v7292254-120617 in the hope that sticking with recent builds will eventually fix this, but I'm starting to wonder if the problem might be something else...

If I connect my Clip + to my (32-bit Win7) PC without forcing a connect with the OF,  the player powers up, shows the currently playing track momentarily, puts up the USB graphic then, after maybe a second, crashes thusly:

Code: [Select]

Undefined instruction
bt pc: 0000003C, sp: :
bt end

I'm sure USB connectivity worked okay for a while, at least. But I find it difficult to believe that it's broken after it was eventually got working -- could it be something else doing this? Some odd setting, maybe related to a theme or something?

[cs96and]

I just upgraded to 3.12 hoping the USB issues had been fixed on the Clip+ but it seems not.

The first time I plugged it in (from a powered off state), no drives appeared in windows, but the Clip+ appeared in the "Safely remove hardware" list.

So I unplugged it and plugged it back in (from a powered on state), and it worked fine.

Tried again from a powered off state and I got the same "Undefined instruction" error as oblivion above.

Pressed the power button, the device restarted and the drives mounted OK.

Tried again from off, and "Undefined instruction" again.

So it seems that as long as you power on the Clip+ first, USB works OK, otherwise it is broken.

[Zian]

I've been able to reproduce this issue on my Clip+ running Rockbox 3.12.

Is there any plan to fix this issue?

[AlexP]

If someone works out what the problem is, sure.

[batman52]

I think I have fallen into the same issue with my clip v2. I comment in case some clever developer can get from this some useful hints.

I wanted to use my player attached to the aux input of my car stereo in "car adapter mode", therefore I have enabled the car adapter function, and the resume playing feature at the same time. The idea was to attach a cigarette lighter power supply to the player, which would have woken up the player when turning on the car (apparently the hardest feature to find on whatever other player...), and then thank to the car adapter mode gently shut down when the car was turned off.

What happens instead is that when I turn on the car, the device sticks with the rockbox splash screen showing a message "loading firmware not found", then after a few seconds goes automatically to the "bootloader USB mode", then when removing power a thrilling panic message appears.

*PANIC*
Unhandeld masked IRQ 03: INT_USB (status0x00000008)

then pressing play resumes playing normally.

The strange bit is that there seems to be some kind of timeout, meaning if you turn off the player and re-attach it in a short delay (I'd say less than 2 mins), the thing does not happen, and it just resumes playing normally.

My feeling is that due to the unstable power supply when attaching the player, the bootloader may detect a false keypress of the "upload firmware mode" (power+left if I remember well). If that assumption is true, a solution could be to add some delay time (0.5 sec?) before doing the check for the keypress in the bootloader - but this is just a guess, and there's obviously people more skilled than me out there who have done this wonderful job of porting rockbox even on my really cheap music player - thank you all for this (still hope someone can work on this bug)!

[saratoga]

Your issue isn't really related to usb. Is your adapter actually plugged into a cigarette lighter and not a USB port? 

[Zian]

If someone works out what the problem is, sure.

What do you mean by that?

I thought that this thread already shows what the problem is, at least to a certain degree.

[saratoga]

If someone works out what the problem is, sure.

What do you mean by that?

I thought that this thread already shows what the problem is, at least to a certain degree.

I don't think anyone has a good idea what the problem is.  Or more likely, what the various problems are.

[AlexP]

If someone works out what the problem is, sure.

What do you mean by that?

I thought that this thread already shows what the problem is, at least to a certain degree.

It shows what the symptoms are, not the cause (or solution).

[whiskers75]

I can report USB glitchiness on my clip+, using Ubuntu 12.10. Plugging it in does not mount a drive, and it seems to disconnect (after looking at /var/log/kern.log) after a few seconds. I have to force-power it every time, so use the OF for USB transfer.

[AlexP]

Yes, we know USB is buggy.

[batman52]

Your issue isn't really related to usb. Is your adapter actually plugged into a cigarette lighter and not a USB port?

Yes: it is plugged to the car lighter... I believe it's a power-up sequence issue: should not be related to any USB fw.

[batman52]

It shows what the symptoms are, not the cause (or solution).

Well I actually proposed as a solution of adding some delay time before checking for button presses in the bootloader when looking for  fw updates.

[saratoga]

It shows what the symptoms are, not the cause (or solution).

Well I actually proposed as a solution of adding some delay time before checking for button presses in the bootloader when looking for  fw updates.

The thing you're talking about has nothing to do with this thread.