N900 Hardware USB - Revision history

joerg_rw: /* USB Phy */ FUSB2600

2018-08-21T04:01:09Z

USB Phy: FUSB2600

← Older revision		Revision as of 04:01, 21 August 2018
Line 38:		Line 38:
	There is no published datasheet for this chip. It may be available under another name.		There is no published datasheet for this chip. It may be available under another name.

-	A reasonably similar chip (compare chips: [http://www.ebv.com/fileadmin/products/Products/ST-Ericsson/Flyer_USB_Transceivers_1.pdf]) is the 1704 which has a datasheet [http://www.stericsson.com/technical_documents/CD00222700.pdf]	+	A reasonably similar chip (compare chips: [http://www.ebv.com/fileadmin/products/Products/ST-Ericsson/Flyer_USB_Transceivers_1.pdf]) is the 1704 which has a datasheet [http://www.stericsson.com/technical_documents/CD00222700.pdf]
		+
		+	Another equivalent chip seems to be the https://www.startpage.com/do/search?query=FUSB2500 - see http://talk.maemo.org/showthread.php?p=643577#post643577

	For more information see [[N900 Hardware USB PHY]]		For more information see [[N900 Hardware USB PHY]]

pali at 09:28, 30 July 2012

2012-07-30T09:28:17Z

← Older revision		Revision as of 09:28, 30 July 2012
Line 26:		Line 26:
	====USB battery charger====		====USB battery charger====

-	The [http://focus.ti.com/docs/prod/folders/print/~~bq24150~~.html ~~bq24150~~] charger from TI is a flexible charger. It, along with the PHY chip - support charging without the intervention of the SoC when the system is charging from a completely dead battery. The PHY chip detects a charger (shorted D+ and D- pins) and the charger uses this information to charge more rapidly.	+	The [http://focus.ti.com/docs/prod/folders/print/bq24150a.html bq24150a] charger from TI is a flexible charger. It, along with the PHY chip - support charging without the intervention of the SoC when the system is charging from a completely dead battery. The PHY chip detects a charger (shorted D+ and D- pins) and the charger uses this information to charge more rapidly.

	It also features reverse boost mode - which enables power to be supplied to a USB device connected to the N900. (up to a limit of 200mA)		It also features reverse boost mode - which enables power to be supplied to a USB device connected to the N900. (up to a limit of 200mA)
Line 46:		Line 46:
	* The SoC has the USB protocol controller - this is the 'high level' controller - it implements most of the USB protocol. This is a [http://www.mentor.com/products/ip/usb/usb20otg/ Mentorgrafix MUSBMHDRC-core] IntelectualProperty function block licenced for the OMAP.		* The SoC has the USB protocol controller - this is the 'high level' controller - it implements most of the USB protocol. This is a [http://www.mentor.com/products/ip/usb/usb20otg/ Mentorgrafix MUSBMHDRC-core] IntelectualProperty function block licenced for the OMAP.
	* The PHY (physical layer) chip connects to the world through the USB socket. This is not the normal companion chip - but the NXP part, and is connected to the SoC via a standard ULPI interface. It does the very lowest level USB hardware protocol. Also it detects chargers (by sensing D+/D- short). It also has a connection to VBUS, via a 1k resistor, to do certain probing.		* The PHY (physical layer) chip connects to the world through the USB socket. This is not the normal companion chip - but the NXP part, and is connected to the SoC via a standard ULPI interface. It does the very lowest level USB hardware protocol. Also it detects chargers (by sensing D+/D- short). It also has a connection to VBUS, via a 1k resistor, to do certain probing.
-	* The [[N900 Hardware Battery Charger\|~~bq24150~~ Battery charger]]. This is connected to the battery, and the PHY chip, as well as to the SoC though I2C. It handles (with the PHY chip) charging from dead. It also implements boost mode, to enable powering things through the USB socket. Of course it detects when external VBUS is applied.	+	* The [[N900 Hardware Battery Charger\|bq24150a Battery charger]]. This is connected to the battery, and the PHY chip, as well as to the SoC though I2C. It handles (with the PHY chip) charging from dead. It also implements boost mode, to enable powering things through the USB socket. Of course it detects when external VBUS is applied.
	* Gaia. The [[N900_Hardware_Power_management/I2C\|TWL4030]] is used to sense the value of the ID pin. It also has a connection to VBUS, to power up the device on charger insertion and inform a running system about changes in VBUS state. Though TWL4030 has a function similar to PHY chip as well, the original design using this function had to change as early chip revisions had problems with charger detection (so the rumour). Driver sourecode is full of cruft from that original design.		* Gaia. The [[N900_Hardware_Power_management/I2C\|TWL4030]] is used to sense the value of the ID pin. It also has a connection to VBUS, to power up the device on charger insertion and inform a running system about changes in VBUS state. Though TWL4030 has a function similar to PHY chip as well, the original design using this function had to change as early chip revisions had problems with charger detection (so the rumour). Driver sourecode is full of cruft from that original design.

	===The Software===		===The Software===

-	* [[N900 Software BME\|BME]] - the battery managment entity. This has its hands in everything, especially the ~~bq24150~~, and is split into	+	* [[N900 Software BME\|BME]] - the battery managment entity. This has its hands in everything, especially the bq24150a, and is split into
	** charger detection (via PHY) in kernel MUSB_HDRC driver, exposing /sys/devices/platform/musb_hdrc/charger		** charger detection (via PHY) in kernel MUSB_HDRC driver, exposing /sys/devices/platform/musb_hdrc/charger
	** BME - userspace driver for the charger chip, as well as monitoring battery voltage through Gaia.		** BME - userspace driver for the charger chip, as well as monitoring battery voltage through Gaia.

qhubekela: /* Compatible devices */

2012-06-02T20:24:13Z

Compatible devices

← Older revision		Revision as of 20:24, 2 June 2012
Line 102:		Line 102:
	\|+ Compatible USB devices		\|+ Compatible USB devices
	\|-		\|-
-	! USB ~~NIC~~ name	+	! USB device name
	! Status		! Status
	! class="unsortable" \| Additional information		! class="unsortable" \| Additional information
Line 109:		Line 109:
	\|-		\|-
	\| Edimax EU-4207 \|\| Working \|\| no problems found \|\| <code>no</code> \|\| http://talk.maemo.org/showthread.php?t=66667		\| Edimax EU-4207 \|\| Working \|\| no problems found \|\| <code>no</code> \|\| http://talk.maemo.org/showthread.php?t=66667
		+	\|-
		+	\| ZTE-AC2766 \|\| Working \|\| no problems \|\| <code>no, uses usbserial.ko</code> \|\| http://talk.maemo.org/showpost.php?p=1198785&postcount=13
	\|-		\|-
	\|}		\|}

	[[Category:N900 Hardware]]		[[Category:N900 Hardware]]

joerg_rw: Undo revision 45988 by 114.79.28.10 (Talk) vandalism/spam

2011-12-15T06:24:08Z

Undo revision 45988 by 114.79.28.10 (Talk) vandalism/spam

← Older revision		Revision as of 06:24, 15 December 2011
Line 72:		Line 72:
	* the ID pin is not connected to PHY, but it is connected to GAIA		* the ID pin is not connected to PHY, but it is connected to GAIA
	* MUSB-core has a hw statemachine that reacts on a telegram from PHY, telling MUSB-core about ID pin grounded and to enter OTG_A hostmode now.		* MUSB-core has a hw statemachine that reacts on a telegram from PHY, telling MUSB-core about ID pin grounded and to enter OTG_A hostmode now.
-	* Other PHY chips (e.g. in N810) ~~[http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm]~~ have a command to make them send this telegram, so you can switch MUSB-core to hostmode under software control (go figure!). 1707 is missing this function.	+	* Other PHY chips (e.g. in N810) have a command to make them send this telegram, so you can switch MUSB-core to hostmode under software control (go figure!). 1707 is missing this function.
	* There is apparently no way to tell MUSB-core directly to switch to hostmode in a natural way.		* There is apparently no way to tell MUSB-core directly to switch to hostmode in a natural way.
	* However there is a bit in MUSB-core registers called FORCE_HOST, which is switching MUSB-core into a semi-lobotomized test mode and allowed us to implement h-e-n.		* However there is a bit in MUSB-core registers called FORCE_HOST, which is switching MUSB-core into a semi-lobotomized test mode and allowed us to implement h-e-n.

114.79.28.10: /* Host mode details. */

2011-12-15T03:04:26Z

Host mode details.

← Older revision		Revision as of 03:04, 15 December 2011
Line 72:		Line 72:
	* the ID pin is not connected to PHY, but it is connected to GAIA		* the ID pin is not connected to PHY, but it is connected to GAIA
	* MUSB-core has a hw statemachine that reacts on a telegram from PHY, telling MUSB-core about ID pin grounded and to enter OTG_A hostmode now.		* MUSB-core has a hw statemachine that reacts on a telegram from PHY, telling MUSB-core about ID pin grounded and to enter OTG_A hostmode now.
-	* Other PHY chips (e.g. in N810) have a command to make them send this telegram, so you can switch MUSB-core to hostmode under software control (go figure!). 1707 is missing this function.	+	* Other PHY chips (e.g. in N810) [http://goo.gl/Dg36c youtube] [http://goo.gl/16GT5 idm] have a command to make them send this telegram, so you can switch MUSB-core to hostmode under software control (go figure!). 1707 is missing this function.
	* There is apparently no way to tell MUSB-core directly to switch to hostmode in a natural way.		* There is apparently no way to tell MUSB-core directly to switch to hostmode in a natural way.
	* However there is a bit in MUSB-core registers called FORCE_HOST, which is switching MUSB-core into a semi-lobotomized test mode and allowed us to implement h-e-n.		* However there is a bit in MUSB-core registers called FORCE_HOST, which is switching MUSB-core into a semi-lobotomized test mode and allowed us to implement h-e-n.

93.142.129.232: /* Compatible devices */

2011-03-17T15:33:03Z

Compatible devices

← Older revision		Revision as of 15:33, 17 March 2011
Line 108:		Line 108:
	! class="unsortable" \| Discussion link		! class="unsortable" \| Discussion link
	\|-		\|-
-	\| Edimax EU-4207 \|\| Working \|\| ~~out-of-the-box~~ \|\| <code>no</code> \|\| http://talk.maemo.org/showthread.php?t=66667	+	\| Edimax EU-4207 \|\| Working \|\| no problems found \|\| <code>no</code> \|\| http://talk.maemo.org/showthread.php?t=66667
	\|-		\|-
	\|}		\|}

	[[Category:N900 Hardware]]		[[Category:N900 Hardware]]

93.142.129.232: /* Compatible devices */

2011-03-17T15:27:01Z

Compatible devices

← Older revision		Revision as of 15:27, 17 March 2011
Line 108:		Line 108:
	! class="unsortable" \| Discussion link		! class="unsortable" \| Discussion link
	\|-		\|-
-	\| ~~No name Davicom~~ \|\| ~~Not~~ Working \|\| ~~does not work on N900. It is reconized on Ubuntu but doesn't work~~ \|\| <code>~~dm9601.ko~~</code> \|\| http://talk.maemo.org/showthread.php?t=66667	+	\| Edimax EU-4207 \|\| Working \|\| out-of-the-box \|\| <code>no</code> \|\| http://talk.maemo.org/showthread.php?t=66667
	\|-		\|-
	\|}		\|}

	[[Category:N900 Hardware]]		[[Category:N900 Hardware]]

amigadave: remove horizontal rule

2011-03-17T13:04:59Z

remove horizontal rule

← Older revision		Revision as of 13:04, 17 March 2011
Line 96:		Line 96:

	{{main\|N900 Hardware USB Socket}}		{{main\|N900 Hardware USB Socket}}
-
-	~~[[Category:N900_Hardware]]~~

	===Compatible devices===		===Compatible devices===
-
-

	{\| class="wikitable sortable"		{\| class="wikitable sortable"
Line 115:		Line 111:
	\|-		\|-
	\|}		\|}
		+
		+	[[Category:N900 Hardware]]

193.108.34.254: /* USB socket */

2011-03-17T12:00:33Z

USB socket

← Older revision		Revision as of 12:00, 17 March 2011
Line 101:		Line 101:
	===Compatible devices===		===Compatible devices===

-	~~----~~

193.108.34.254: /* Compatible devices */

2011-03-17T12:00:00Z

Compatible devices

← Older revision		Revision as of 12:00, 17 March 2011
Line 100:		Line 100:

	===Compatible devices===		===Compatible devices===
		+
		+	----
		+

	{\| class="wikitable sortable"		{\| class="wikitable sortable"