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:

Thank You for your continued support and contributions!

+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Hardware
| | |-+  Fuze and Griffin Dock line out
« previous next »
  • Print
Pages: 1 2 3 [4] 5

Author Topic: Fuze and Griffin Dock line out  (Read 33765 times)

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8963
Re: Fuze and Griffin Dock line out
« Reply #45 on: March 09, 2011, 12:35:05 PM »
Quote from: hynpin on March 09, 2011, 12:30:25 PM
Found out that:

LOD for FUZE has got jumper between pin #7 and #22.
Line-out is activated by 3V on pin #7.

Hope this will help  ;)

This thread is actually about how to detect that jumper.  

Edit:  see this post:  http://forums.rockbox.org/index.php/topic,22942.msg157862.html#msg157862
« Last Edit: March 09, 2011, 12:37:03 PM by saratoga »
Logged

Offline bilditup1

  • Member
  • *
  • Posts: 35
Re: Fuze and Griffin Dock line out
« Reply #46 on: March 09, 2011, 06:16:42 PM »
'Unfortunately, whatever pin it is, we apparently do not print it on the debug screen, so it'll take a bit more work for someone to find it.'

How can this be done? How do you know how to display a pin whose name you don't know/cannot see? I'll try to look at it later tonight (though I have no experience with rb development).
Logged

Offline soap

  • Member
  • *
  • Posts: 1678
  • Creature of habit.
Re: Fuze and Griffin Dock line out
« Reply #47 on: March 18, 2011, 12:23:53 PM »
Quote from: bilditup1 on March 09, 2011, 06:16:42 PM
How can this be done? How do you know how to display a pin whose name you don't know/cannot see? I'll try to look at it later tonight (though I have no experience with rb development).

Perhaps come onto IRC (we offer a web-client) and talk to funman about it.  Last he posted in this thread he said he did not have a fuze on hand but was willing to offer a patch to add to the debug screen.  ccfreak2k appeared to be willing to take him up on that, but has not come back with a working build environment.  Perhaps you could get with funman, and build some test builds to:  A - get the debug screen showing what needs showed, and B - find out if indeed the line-out dock can be detected.

EDIT:
funman is not in IRC very often.  ;)  Try expressing interest and intent in the thread. 
« Last Edit: March 18, 2011, 03:49:02 PM by soap »
Logged
Rockbox Forum Guidelines
The Rockbox Manual
How to Ask Questions the Smart Way

Offline tenfoot

  • Member
  • *
  • Posts: 5
Re: Fuze and Griffin Dock line out
« Reply #48 on: March 21, 2011, 09:16:29 AM »
I've got a fuze v2 that I'd like to get working with line out and I have a build environment for testing patches etc so I'm willing to test the extra debug info.

I've been using a custom patch to enable the line out when the volume's turned to the max setting, but keep getting deafened as I switch between the two modes!  I'll post it here if anyone's interested
Logged

Offline psgarcha92

  • Member
  • *
  • Posts: 36
Re: Fuze and Griffin Dock line out
« Reply #49 on: March 22, 2011, 07:26:59 AM »
Post it, ofcourse.
its working with the Fuze v2 right?
hell yeah post it.
Logged

Offline tenfoot

  • Member
  • *
  • Posts: 5
Re: Fuze and Griffin Dock line out
« Reply #50 on: March 24, 2011, 04:25:28 PM »
Here's my patch.  It's by no means the correct solution for this, but it works for me...
* fuze_lineout.txt (1.58 kB - downloaded 242 times.)
Logged

Offline Chronon

  • Rockbox Expert
  • Member
  • *
  • Posts: 4379
Re: Fuze and Griffin Dock line out
« Reply #51 on: March 24, 2011, 04:29:36 PM »
Thank you, but it would be much better to put it on the tracker. 
Logged
Sansa e280, Gigabeat F40, Gigabeat S60, Sansa Clip+, iPod Mini 2g

Offline tenfoot

  • Member
  • *
  • Posts: 5
Re: Fuze and Griffin Dock line out
« Reply #52 on: April 19, 2011, 04:31:49 PM »
I've put an updated version of this patch on the tracker at: http://www.rockbox.org/tracker/task/12074

Instead of using the max volume setting to enable the lineout, I've added a lineout setting - this can be added to the quickscreen so it's quite easy to switch between headphones and lineout.

I decided to change from the max volume setting as you get a loud burst when switching back to headphone mode before you can get back to a sane level.  Also I found I kept knocking it off lineout mode when changing tracks.
Logged

Offline bertrik

  • Developer
  • Member
  • *
  • Posts: 171
    • Homepage Bertrik Sikken
Re: Fuze and Griffin Dock line out
« Reply #53 on: April 19, 2011, 04:57:50 PM »
From a technical point of view, I think we should use a system message to be picked up by the default event handler in apps/misc.c when a dock gets connected or disconnected. Something like either a SYS_DOCK_CONNECTION message, with an associated boolean data item that indicates connection or disconnection, or alternatively two messages (SYS_DOCK_CONNECTED and SYS_DOCK_DISCONNECTED). This is analogous to how we handle headphone detection and charger detection.
For the fuze v1, we could detect dock (dis)connection in the button handler interrupt.
After catching SYS_DOCK_CONNECTION could we could then poke the audio hardware to set the proper audio routing and set volumes appropriately through one or more audiohw_XXX calls.
Logged
Meizu M6SP, Samsung YP-S3, iPod nano 1g, Sansa c200, Sansa e200, Sansa Clip, Sansa Clip+, Sansa Clip Zip
 

Offline zenki

  • Member
  • *
  • Posts: 2
Re: Fuze and Griffin Dock line out
« Reply #54 on: April 21, 2011, 02:32:18 AM »
Thanks for the update..
by the way I noticed from the last patch, that although this enables lineout in RB, the output volume to my amp is lower than the official FW.

Perhaps it's related to the volume scale of RB?
Anyway, the difference may be small but it makes me think the lineout from RB is not exactly the full output that the Fuze can handle..
Logged

Offline ardeeon

  • Member
  • *
  • Posts: 5
Re: Fuze and Griffin Dock line out
« Reply #55 on: April 22, 2011, 09:33:23 PM »
with this kind of patches, is it safe to say that we will see Line-Out to be fully supported on fuze v2?
Logged

Offline moxill

  • Member
  • *
  • Posts: 1
Re: Fuze and Griffin Dock line out
« Reply #56 on: October 25, 2011, 10:10:50 PM »
I just want to pass on a big up to tenfoot, you made me a very happy camper.  I can now hook my fuze up to my SET amp.  The sound from my sansa(s) is really clean, I can forget the usb dac for a while.

It took me a few minutes to find the LO setting:
Settings>General Settings>System>Line Out
And yes there is a little popping when toggling between on/off, so probs best not to do that live.
I made a DIY line out so I can fit both headphones and the LO cable at the same time.  I can confirm this patch shunts the headphone volume for those that were curious / concerned about battery life. 

Fuze/Clip + Yuin PK3 is still by far the cheapest ticket to audio nirvana, but now I can drive my Grados with my headphone amp using Rockbox in all its gapless glory.  This patch seals the deal, time to invest in a new fuze, the battery in mine is about cooked.
Logged

Offline esm

  • Member
  • *
  • Posts: 11
Re: Fuze and Griffin Dock line out
« Reply #57 on: December 02, 2011, 09:48:00 PM »
Quote
Unfortunately, whatever pin it is, we apparently do not print it on the debug screen, so it'll take a bit more work for someone to find it. 

Hi. Rockbox newbie here. I just bought a Fuze v2 + Griffin iTrip car adapter, and discovered this problem. tenfoot's lineout patch helps, but not quite enough. I would like Rockbox to automatically detect, on powerup, that it is connected to a car adapter (not a USB host) and that it should 1) boot itself, not the original FW, and 2) enable lineout automatically.

Working with the source and the 1.13 revision of the AS3525 datasheet, I've instrumented debug-as3525.c to print what I thought were some likely candidates: ENRD0-2, some USB_[IO]EP[0-3]_{CTRL,STS}, GPIO[A-D]_IS and _MIS. No joy. ENRD0 flips from 0x00 to 0x28 when plugged in to the Griffin, as expected, but that's indistinguishable from computer USB.

Can anyone suggest other registers to monitor? Other things to try? I am highly motivated to fix this. Thanks in advance.
Logged

Offline saratoga

  • Developer
  • Member
  • *
  • Posts: 8963
Re: Fuze and Griffin Dock line out
« Reply #58 on: December 03, 2011, 01:30:18 PM »
Booting into the original firmware is actually by design since USB is very unstable in rockbox on your player.you can disable that by editing mkamsboot and flashing a new bootloader. Be careful though a bad flash will brick your player.

Regarding line out, I always thought it was detrctedbby one of the dbop in pins like the buttons and wheel on the first fuze.
Logged

Offline esm

  • Member
  • *
  • Posts: 11
Re: Fuze and Griffin Dock line out
« Reply #59 on: December 03, 2011, 02:21:38 PM »
Quote from: saratoga on December 03, 2011, 01:30:18 PM
Booting into the original firmware is actually by design since USB is very unstable in rockbox on your player.

Understood. To clarify my earlier post, I don't necessarily want to boot in USB mass storage mode. I want Rockbox to detect the car adapter. I.e. "I sense USB (bit 3). Now: if connected to computer, boot into original FW (current behavior). If connected to car adapter, boot into Rockbox (music mode, not USB mode) and enable line out".

Quote
Regarding line out, I always thought it was detected by one of the dbop in pins

Will check those as soon as I have time. Thanks for the suggestion.
Logged

  • Print
Pages: 1 2 3 [4] 5
« previous next »
+  Rockbox Technical Forums
|-+  Support and General Use
| |-+  Hardware
| | |-+  Fuze and Griffin Dock line out
 

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

Page created in 0.238 seconds with 21 queries.