Rockbox Technical Forums

Support and General Use => Hardware => Topic started by: Petmetroid on September 18, 2008, 12:04:23 PM

Title: H320 won't leave USB mode! Inappropriate voltage reads.
Post by: Petmetroid on September 18, 2008, 12:04:23 PM
>>NVM, I formated the HDD and reinstalled everything.  No problem here.  Since I cannot delete this, I will leave this here for the modifiers to delete or for others to investigate further for their own recreation.

*NVM the NVM.  It's doing it again.  I am quite sure it's a charging issue in the new battery.  I finished giving it a full charge, and that's probably the problem.  It charged up to a voltage of 4.12 volts.  Now draining to less than four volts, it is slowly but surely reaching a manageable voltage, while as I am typing right now it is switching on and off between USB mode and normal... mode.  The problem seems to be that Rockbox (and the bootloader) thinks that the overloaded battery is a USB charger.
Does anyone know the appropriate maximum battery voltage I need to run Rockbox on an H300?
If this is the problem, would someone be able to help me patch a Rockbox mod to fix this?

>I just installed a new battery last night, charged it while I was sleeping.  It was working perfectly, even when I unplugged the power using the new battery.  I unplugged it this morning, turned it off, and when I turned it back on again, it won't leave USB mode.  It will go into USB bootloader, before I have to restart it into its original firmware, where it works perfectly.  Once after I return from its original firmware and boot into Rockbox, it will then boot past the loader, but directly afterward will go into USB mode.  I just fixed my iriver and now it's not working again!  ARG!
Long story short, my iriver was working last night, I charged it, and now it won't leave USB mode.
BTW, NOTHING is plugged in, and nothing happens when I do plug it in (other that it charges.)
Any help, please?  I will format and reinstall everything later if I have to, but I cannot do that now.

**I determined a temporary fix to this problem and have addressed it on the bug tracker with Linus.  Somebody can delete this if necessary, I'm done here.