Fuze and Griffin Dock line out

[Avalon]

Just an update on the Fuze V1 used with the Griffin Dock.

I have used it extensively and as far as I can tell, it works perfectly!!!

The only difference with the E200 series is that the Fuze V1 outputs a constant line out level independent of volume adjustment while the E200 series output changes with volume adjustment.  Since Griffin Sansa Docks (without remote) can be picked up for under $10, this is really very convenient for inputting to stereos and other amplifiers.

This is a great feature and I would like to thank all who contributed.

[gurenko]

Hi!
there are any news about dock line out for fuze v2 in rockbox?
thank you.

[mc2739]

The only difference with the E200 series is that the Fuze V1 outputs a constant line out level independent of volume adjustment while the E200 series output changes with volume adjustment. 

Thus is true only with the e200v1.  The e200v2 has a constant line out level.

Hi!
there are any news about dock line out for fuze v2 in rockbox?
thank you.

Before support for the Fuze v2 can be added, it needs to be determined how to detect a dock attachment.  This is necessary on the Fuze v2 since the headphones need to be disabled so that the line out can be enabled.

[gurenko]

hi!
and there's not possible a manual option for disable headphone and enable dock line out?
it would be a temporaly solution during determinating how to detect dock attachment.

thanks.

[saratoga]

hi!
and there's not possible a manual option for disable headphone and enable dock line out?
it would be a temporaly solution during determinating how to detect dock attachment.

Its probably not much more or less effort to just figure out how the OF detects the line out.  But if you want to take a shot at it, go for it.

[Avalon]

Hi, I'm not a developer, but at the beginning of this subject post, I provided the bit changes via the View IO Ports Screen for GPIOA  and DBOP_DIN. 

It was very easy to check these with the Fuze V1 in the dock and out.  If that helped in establishing the code for the Fuze V1, then the same may be true for the V2. 

If one of the software gurus could offer some advice here, you may be able to move this along.  The code is written for the V1, so the V2 may not require as great a modification.  I don't have a V2, so I can't help.

[ccfreak2k]

Hi!
there are any news about dock line out for fuze v2 in rockbox?
thank you.

Before support for the Fuze v2 can be added, it needs to be determined how to detect a dock attachment.  This is necessary on the Fuze v2 since the headphones need to be disabled so that the line out can be enabled.

It seems to me that the easiest way to do this is to enable it when power is applied since it's likely that if the user wants line-level audio they'll have a powered dock. The actual enable could be delayed while Rockbox figures out if it's a real USB connection or just power. The only problem case I can think of is if line-level audio is desired without power available.

EDIT: I have a Fuze v2, so I can offer some help here.

[funman]

Read the post above yours and report the changes you see in View IO Ports screen (in debug menu) when plugging a dock

[ccfreak2k]

Read the post above yours and report the changes you see in View IO Ports screen (in debug menu) when plugging a dock

Did just that earlier:

Unplugged:

Code: [Select]

GPIOA: A5/65/25/E5 DIR: 21
GPIOB: FE          DIR: 3F
GPIOC: 00          DIR: 00
GPIOD: 9F          DIR: 00

[CP15]
CP15: 0x0005107D

Plugged USB:

Code: [Select]

GPIOA: AD/6D/2D/ED DIR: 21
GPIOB: FE          DIR: 3F
GPIOC: 00          DIR: 00
GPIOD: 9F          DIR: 00

[CP15]
CP15: 0x0005107D

Plugged Wall:

Code: [Select]

GPIOA: AD/6D/2D/ED DIR: 21
GPIOB: FE          DIR: 3F
GPIOC: 00          DIR: 00
GPIOD: 9F          DIR: 00

[CP15]
CP15: 0x0005107D

GPIOA bit 3 is high when power is applied, and bits 6/7 of GPIOA changed based on scrollwheel movement, but I don't know the pattern. Everything else doesn't seem to change at all. As for DBOP, I couldn't find any references to it.

EDIT: I should probably point out that the "dock" I have in my car (which works as expected in OF) doesn't have any values other than those for USB/wall.

[saratoga]

Read the post above yours and report the changes you see in View IO Ports screen (in debug menu) when plugging a dock

Did just that earlier:

Unplugged:

Code: [Select]

GPIOA: A5/65/25/E5 DIR: 21
GPIOB: FE          DIR: 3F
GPIOC: 00          DIR: 00
GPIOD: 9F          DIR: 00

[CP15]
CP15: 0x0005107D

Plugged USB:

Code: [Select]

GPIOA: AD/6D/2D/ED DIR: 21
GPIOB: FE          DIR: 3F
GPIOC: 00          DIR: 00
GPIOD: 9F          DIR: 00

[CP15]
CP15: 0x0005107D

Plugged Wall:

Code: [Select]

GPIOA: AD/6D/2D/ED DIR: 21
GPIOB: FE          DIR: 3F
GPIOC: 00          DIR: 00
GPIOD: 9F          DIR: 00

[CP15]
CP15: 0x0005107D

GPIOA bit 3 is high when power is applied, and bits 6/7 of GPIOA changed based on scrollwheel movement, but I don't know the pattern. Everything else doesn't seem to change at all. As for DBOP, I couldn't find any references to it.

This is in line with what other people have reported, so my guess is that some other pin is used to detect the dock connection (perhaps over DBOP which i believe is currently thought to be unused on the fuzev2?).  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. 

[funman]

Currently we don't read on DBOP because all the buttons can be read on GPIO but it should work easily.

Unfortunately I don't have my fuzev2 to test.

ccfreak2k can you make your own build and try patches?

EDIT: when you plug the dock, is the charging icon present?

[ccfreak2k]

ccfreak2k can you make your own build and try patches?

I don't have the toolchain installed on any of my computers. Will the VMWare image work?

EDIT: Tried VMWare image, didn't work, presumably because of the switch to EABI that happened at some point.

EDIT: when you plug the dock, is the charging icon present?

Charge icon does appear when plugged in.

[saratoga]

EDIT: Tried VMWare image, didn't work, presumably because of the switch to EABI that happened at some point.

If you run 'sudo tools/rockboxdev.sh' from the root of your source code check out it should upgrade your image to EABI.

[ccfreak2k]

Looks like the virtual machine ran out of space while compiling the toolchain, so I'm going to just use my Slackware box for compiles. Set up a seperate user with its own copy of the toolchain and made what seems to be a working build, so I should be all set.

[hynpin]

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