Support and General Use > Hardware

Fuze and Griffin Dock line out

<< < (8/14) > >>

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:

--- Quote from: mc2739 on August 17, 2010, 07:11:46 PM ---
--- Quote from: gurenko on August 17, 2010, 06:36:31 PM ---Hi!
there are any news about dock line out for fuze v2 in rockbox?
thank you.

--- End quote ---

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.

--- End quote ---
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:

--- Quote from: funman on September 19, 2010, 01:12:34 AM ---Read the post above yours and report the changes you see in View IO Ports screen (in debug menu) when plugging a dock

--- End quote ---
Did just that earlier:

Unplugged:


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

[CP15]
CP15: 0x0005107D

--- End code ---

Plugged USB:


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

[CP15]
CP15: 0x0005107D

--- End code ---

Plugged Wall:


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

[CP15]
CP15: 0x0005107D

--- End code ---

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:

--- Quote from: ccfreak2k on September 19, 2010, 01:37:49 AM ---
--- Quote from: funman on September 19, 2010, 01:12:34 AM ---Read the post above yours and report the changes you see in View IO Ports screen (in debug menu) when plugging a dock

--- End quote ---
Did just that earlier:

Unplugged:


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

[CP15]
CP15: 0x0005107D

--- End code ---

Plugged USB:


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

[CP15]
CP15: 0x0005107D

--- End code ---

Plugged Wall:


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

[CP15]
CP15: 0x0005107D

--- End code ---

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.


--- End quote ---

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. 

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version