Openmoko - User contributions [en]

Talk:Wishlist/Mesh Networking

2008-12-15T06:10:49Z

Sdhillon: New page: Coming with the GTAv03

Coming with the GTAv03

Talk:GTA03

2008-12-15T06:05:17Z

Sdhillon:

Is it possible for this revision to move the speaker near to the aux button instead of near the microphone?
like this it will avoid the echo when you put a discussion in speaker mode.
perhaps it had already been ask before...

Why are we adding a camera? Also, I personally don't care miniaturize the device. I'd prefer a full-sized SDHC slot, and then I could just add my own camera.

Openmoko Local Groups: San Francisco

2008-12-13T01:24:06Z

Sdhillon:

Are there any other Openmoko community members here?

{|border=1
!Name
!Skills
!Interest
!Location
!Has Device
!Has Debug Board
|-
|[http://www.asheesh.org/ Asheesh Laroia]
|Programming, sysadminning
|Whatever it takes to enjoy using it every day ;-)
|San Francisco, CA (live and work in the city)
| [[Image: Moko.jpg|center]]
|
|-
|[[User:captain_morgan|Morgan]]
|programming/some hardware
|Hardware development
|Mountain View/Oakland, CA
|
|
|-
|[[User:codyl|J.Cody]]
|programming
|Application development
|Mountain View, CA
|
|
|-
|[[User:csnellman|Carl Snellman]]
|Programming
|Application development/Location based services
|Palo Alto, CA
|
|
|-
|[[User:krid|Dirk Bergstrom]]
|programming
|"Procmail" for incoming calls/messages; GPS tracking
|Mountain View, CA
|
|
|-
|[[User:samhiatt|Sam Hiatt]]
|Application Development
|FOSS, GIS/Navigation, Cartography
|Mountain View, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:xyphus|Marco Barreno]]
|programming
|Power user/app development
|Berkeley, CA
|
|
|-
|[[User:Elektrolott|Lothar]]
|programming
|Waiting for GTA02
|Morgan Hill, CA
|
|
|-
|[[User:rabble|Rabble]]
|programming
|App Development & Geowanking
|San Francisco, CA
|
|
|-
|[[User:rtyler|R. Tyler Ballance]]
|Development
|Mobile Mono Applications
|San Francisco, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:cfl|Cfl]]
|Software/Architecture
|Mobile Applications
|San Jose, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:Pdesai|Pranav]]
|programming, linux, sysadmin.
|Applications, GPS, bluetooth
|Sunnyvale, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:Michaelshiloh|Michael Shiloh]]
|Programmer, teacher
|Developer Relations and Evangelist for Openmoko
|San Francisco, CA (live and work in the city)
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:Maratgothix|Omar Green]]
|Architect/Technologist
|H/W, S/W, Intelligent services
|San Francisco, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:mgoff|Michael Goff]]
|Software Programmer
|Applications
|San Francisco, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:wisp|Joshua Layne]]
|Programming
|GPS/mapping/location aware apps, intelligent time/date mgmt
|Half Moon Bay, CA
|
|
|-
|[[User:GrecoJava|David Pearson]]
|Software Programmer
|Applications
|Petaluma, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:Rjt|Oldman]]
|Computer/Network Engineer
|System/Network Programming
|Half Moon Bay, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-
|[[User:raels|raels]]
|Programming, Management, Technologist
|Applications, Linux compatible apps -- waiting for next HW release
|Half Moon Bay, CA
|
|
|-
|[[User:jonathan.tsai|Jonathan Tsai]]
|Software Engineering Grad Student [http://west.cmu.edu/ Carnegie Mellon West] Participant of class project MobileAdvisor.org [http://www.mobileadvisor.org/ Join]
|Openmoko Evaluator
|San Jose, CA
|
|-
|[[User:yochaigal|Yochai Gal]]
|Application Testing
|Linux Admin/Technician
|San Francisco, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:wolfmanjm|Jim Morris]]
|Programming,Networks
|Ruby,remote access
|San Jose, CA
| [[Image: Moko.jpg|center]]
|
|-
|[[User:Vvaidy|Vijay Vaidyanathan]]
|Programming
|Command Line Phone!
|Los Altos, CA
|Y, FreeRunner
|N
|-
|[[User:WilliamMorgan|William Morgan]]
|programming
|apps, ruby
|San Francisco, CA
| [[Image: Moko.jpg|center]] (freerunner)
|
|-
|[[User:Frang|Frang]]
|Software architect, large-scale distributed systems
|A new device to explore possibilities with.
|Palo Alto, CA
| [[Image: Moko.jpg|center]] (freerunner)
|
|-
|[[User:mmargushsf|Matthias Margush]]
|Programming
|Application programming, system testing, and documentation.
|San Francisco, CA
| [[Image: Moko.jpg|center]] (freerunner)
|
|-
|[[User:ieatlint|Jeffrey Malone]]
|Programming
|app dev
|San Francisco, CA
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|
|-
|[[User:chgros|Charles-Henri Gros]]
|Programming (C/C++ mostly)
|Application development, phone calls
|San Francisco, CA
| [[Image: Moko.jpg|center]] (freerunner)
|
|-
|[[User:smokinggoat|Greg Beuthin]]
|Evangelising / Offer of meeting space
|Evangelising / general use
|San Francisco, CA
|
|
|-
|[[User:nvanfossen|Nick Van Fossen]]
|SW/HW Testing
|Programming/Hacking Linux
|Petaluma, CA
| [[Image: Moko.jpg|center]] (freerunner)
|
|
|-
|[[User:Owen|Owen Pietrokowsky]]
|Editing
|Editing / general use
|San Francisco, CA
|
|-
|[[User:Sdhillon|Sargun Dhillon]]
|Programmer, Systems/Network administrator
|Developing infrastructure around Openmoko
|San Jose, CA (work) - Pleasanton, CA (live)
| [[Image: Moko.jpg|center]]
| [[Image: MokoBox.jpg|center]]
|-

[[Category:Openmoko Local Groups]]

User:Sdhillon

2008-12-13T01:23:47Z

Sdhillon: New page: Hello, I am a system/network engineer living and working in the Bay Area. I've had some past experience with Xbox "hacking" Addr: xbmodder gmail com Phone: +1.925.202.9485

Hello, I am a system/network engineer living and working in the Bay Area. I've had some past experience with Xbox "hacking"

Addr: xbmodder gmail com
Phone: +1.925.202.9485

GPRS FSO

2008-11-20T01:17:52Z

Sdhillon:

{{FSO}}
This page documents the GSM networking solutions (commonly known as GPRS) using the [[OpenmokoFramework|FreeSmartphone.Org]] framework (FSO).

There are other ways to enable wireless communications on the smartphone, including [[Bluetooth]] and [[Wireless_Networking|WLAN]].

== Current state ==

Since milestone 2 the system dbus has been extended with methods that enables connectivity using GPRS. The functionality is available under <code>org.freesmartphone.frameworkd</code> at <code>/org/freesmartphone/GSM/Device</code>.

The implementation should not interfer with other phone functionality, such as placing calls. In other words: you can use GPRS while talking on the phone without hanging up.

Currently, there's no GUI available but it's fairly easy to use the methods available using any dbus tool.

The methods available:
[METHOD] org.freesmartphone.GSM.PDP.ActivateContext( s:apn, s:user, s:password )
[METHOD] org.freesmartphone.GSM.PDP.DeactivateContext()
[METHOD] org.freesmartphone.GSM.PDP.GetCurrentGprsClass()
[METHOD] org.freesmartphone.GSM.PDP.ListAvailableGprsClasses()
[METHOD] org.freesmartphone.GSM.PDP.SetCurrentGprsClass( s:class_ )
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus( i:index, s:status, a{sv}:properties )

Use ''mdbus -s -l'' to monitor the emitted signals. Signals will look like this:

:ActivateContext( s:apn, s:user, s:password )
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'outgoing'), dbus.Dictionary({}, signature=dbus.Signature('sv')))</code>
:Once the connection is established (takes 3-4 seconds for me) a new signal is emited
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'active'), dbus.Dictionary({}, signature=dbus.Signature('sv')))
:DeactivateContext
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'release'), dbus.Dictionary({}, signature=dbus.Signature('sv')))

== Using scripts ==

While we wait for the preferences part of FSO to be completed (and a GUI), we can use two shell scripts. You need to know three things to successfully connect via GPRS (your carrier should provide this information to you):
* the APN to use,
* the username, and
* the password.
If your APN has no username or password, you must still provide a string to satisfy the framework's input requirements. Entering bogus data, such as the "x" above, will suffice.

To connect, put the following in a file and make it executable (<code>chmod +x gprs-on.sh</code>):
<pre>
#!/bin/sh
APN="internet.parlino.se"
USERNAME="x"
PASSWORD="x"
BUSNAME="org.freesmartphone.frameworkd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.ActivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME $APN "$USERNAME" "$PASSWORD"
</pre>
To disconnect, use the following method instead (<code>chmod +x gprs-off.sh</code>):
<pre>
#!/bin/sh
BUSNAME="org.freesmartphone.frameworkd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.DeactivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME
</pre>
The ''on'' script, using the ActivateContext method, will:
* setup a ppp interface (normally ppp0) (and assign IP address)
* setup (replace) the default route
* setup DNS
with settings received from the ISP.

For a list of known APN:s, see the [[GPRS#Some_APN_names_for_reference|main GPRS page]].
== Using a GUI ==
[[Framework-settings]]

== See also ==
* [[GPRS]]
* [[OpenmokoFramework/mdbus]]

[[Category:FSO]]
[[Category:Networking]]
[[Category:Advanced End User]]

GPRS FSO

2008-11-20T01:17:03Z

Sdhillon:

{{FSO}}
This page documents the GSM networking solutions (commonly known as GPRS) using the [[OpenmokoFramework|FreeSmartphone.Org]] framework (FSO).

There are other ways to enable wireless communications on the smartphone, including [[Bluetooth]] and [[Wireless_Networking|WLAN]].

== Current state ==

Since milestone 2 the system dbus has been extended with methods that enables connectivity using GPRS. The functionality is available under <code>org.freesmartphone.frameworkd</code> at <code>/org/freesmartphone/GSM/Device</code>.

The implementation should not interfer with other phone functionality, such as placing calls. In other words: you can use GPRS while talking on the phone without hanging up.

Currently, there's no GUI available but it's fairly easy to use the methods available using any dbus tool.

The methods available:
[METHOD] org.freesmartphone.GSM.PDP.ActivateContext( s:apn, s:user, s:password )
[METHOD] org.freesmartphone.GSM.PDP.DeactivateContext()
[METHOD] org.freesmartphone.GSM.PDP.GetCurrentGprsClass()
[METHOD] org.freesmartphone.GSM.PDP.ListAvailableGprsClasses()
[METHOD] org.freesmartphone.GSM.PDP.SetCurrentGprsClass( s:class_ )
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus( i:index, s:status, a{sv}:properties )

Use ''mdbus -s -l'' to monitor the emitted signals. Signals will look like this:

:ActivateContext( s:apn, s:user, s:password )
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'outgoing'), dbus.Dictionary({}, signature=dbus.Signature('sv')))</code>
:Once the connection is established (takes 3-4 seconds for me) a new signal is emited
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'active'), dbus.Dictionary({}, signature=dbus.Signature('sv')))
:DeactivateContext
[SIGNAL] org.freesmartphone.GSM.PDP.ContextStatus from :1.3 /org/freesmartphone/GSM/Device
(dbus.Int32(1), dbus.String(u'release'), dbus.Dictionary({}, signature=dbus.Signature('sv')))

== Using scripts ==

While we wait for the preferences part of FSO to be completed (and a GUI), we can use two shell scripts. You need to know three things to successfully connect via GPRS (your carrier should provide this information to you):
* the APN to use,
* the username, and
* the password.
If your APN has no username or password, you must still provide a string to satisfy the framework's input requirements. Entering bogus data, such as the "x" above, will suffice.

To connect, put the following in a file and make it executable (<code>chmod +x gprs-on.sh</code>):

#!/bin/sh
APN="internet.parlino.se"
USERNAME="x"
PASSWORD="x"
BUSNAME="org.freesmartphone.frameworkd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.ActivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME $APN "$USERNAME" "$PASSWORD"

To disconnect, use the following method instead (<code>chmod +x gprs-off.sh</code>):
</pre>
#!/bin/sh
BUSNAME="org.freesmartphone.frameworkd"
OBJECTPATH="/org/freesmartphone/GSM/Device"
METHODNAME="org.freesmartphone.GSM.PDP.DeactivateContext"
mdbus -s $BUSNAME $OBJECTPATH $METHODNAME
</pre>
The ''on'' script, using the ActivateContext method, will:
* setup a ppp interface (normally ppp0) (and assign IP address)
* setup (replace) the default route
* setup DNS
with settings received from the ISP.

For a list of known APN:s, see the [[GPRS#Some_APN_names_for_reference|main GPRS page]].
== Using a GUI ==
[[Framework-settings]]

== See also ==
* [[GPRS]]
* [[OpenmokoFramework/mdbus]]

[[Category:FSO]]
[[Category:Networking]]
[[Category:Advanced End User]]

User talk:Dolfje

2008-08-20T17:59:28Z

Sdhillon:

Hi,
I notice that you do pretty much editing work on this page. But , You also delete some information other people need. For example , you delete the data sheet's link, so other people who deal with hardware drivers will feel confused.
So I roll back them.

[[User:coolcat| Brenda Wang]]

I have changed it into a
table, so the data was organized.
The second thing I did, was putting all data of the chip itself to
another wiki page. (bv. [[Samsung_S3C2442B_B54]])
Then all the data about one chip is centralized and can be interesting
for many phones. If Openmoko has 7 devices, it will be handy to know
in which devices you used for example the Samsung S3C2442B and how
they were connected. So I have not deleted one single bit of
information, they only stand on the page about the chip itself.
[[User:Dolfje|Dolfje]] 11:22, 18 August 2008 (UTC)

Who are you? Why do you keep removing data?
--[[User:Sdhillon|Sdhillon]]

HXD8

2008-08-20T16:21:19Z

Sdhillon:

HXD8 is the codename of a device that is going to be developped by Openmoko. For more information about other phones in development, visit [[Phone Development]].

On May 26th 2007 (GMT) Sean [http://lists.openmoko.org/pipermail/community/2007-May/005407.html confirmed] the existence of the device, said hardware support was almost done and cleverly told us to wait anxiously.

According to [http://lists.openmoko.org/pipermail/community/2007-October/011324.html this post] the device is a networked collaborative automotive GPS unit, from http://dash.net/ .

{{Speculations}}

It has been confirmed that the DE is based off of the HXD8.

==Hardware==
From the information found in the [https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/ hardware documentation] and [https://svn.openmoko.org/trunk/src/target/kernel/patches/ kernel patches] parts of the subversion repositories, the following specifications can be predicted. The HXD8v2 has shipped under the FCC ID [https://fjallfoss.fcc.gov/oetcf/eas/reports/GenericSearchResult.cfm?RequestTimeout=500 EUNHXD8V2]

===Processor===
According to https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2440-nand-disable-hwecc.patch the HXD8 will feature an [http://www.samsung.com/Products/Semiconductor/common/product_list.aspx?family_cd=MSC0102 S3C2440], capable of running up to 400MHz. The features are the same as the [http://www.samsung.com/products/semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2410/S3C2410.htm S3C2410] plus a camera interface.
*GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/gpio.txt

===Flash===
According to a currently available hardware patch, the device supports 1 NAND Flash device of up to 4G. (uncertain about what kind of G that is. Could be 4Gb (which makes about 0,5GB), could be 4GB).

The DE has 3G of Flash, and there is no NOR.

Some other patch implies that there is the possibility of connecting 3 NAND Flash chips.

===RAM===
128MB Random Access Memory, of which 2MB is used as a Framebuffer. https://svn.openmoko.org/trunk/src/target/u-boot/patches/uboot-hxd8.patch

===GSM/GPRS===
Using same GSM modem on GTA01 and GTA02, TI Calypso with 850/1800/1900 configuration.

=== SD-Card ===
The HXD8 features either an SD, miniSD or microSD-card slot.
* Connected to: S3C2410 MMC/SD controller
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c_mci.patch

===LCD Module (LCM)===
The HXD8 features a 480x272 pixel LCD (which is a widescreen (16:9) ratio) with PWM-controlled backlight.

===Light Sensor===
The HXD8 features a light sensor by TAOS Inc. (Texas Advanced Optoelectronic Solutions). It's either a [http://www.taosinc.com/product_detail.asp?cateid=4&proid=59 TLS2560] or a [http://www.taosinc.com/product_detail.asp?cateid=4&proid=60 TLS2561]. This light sensor will be included to measure ambient illuminance to control the LCM backlight illumination, or for exposure control for the camera (depends on location of the chip).
*Datasheet: [http://www.taosinc.com/images/product/document/tsl2560-e53.pdf tsl2560-e53.pdf]

===Power Management===
A Philips PCF50606 is used for power management.

* Data Sheet: [http://www.nxp.com/acrobat/literature/9397/75009763.pdf PCF50606/605]
* User Manual: [http://www.rockbox.org/twiki/pub/Main/DataSheets/pcf50606.pdf pcf50606.pdf]
* Connected to: S3C2440 via I2C.

===WiFi===
HXD8 features an SPI-connected Marvell 8686 based WiFi module.

===GPS===
The PMU chip's config contains a voltage group called GPS_3V3, and the [https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/gpio.txt gpio.txt] a set of GPS UART data pins. HXD8 using SirfSTAR III based module solution

[[Category:Hardware]]
[[Category:Hardware Support]]

Dash Express

2008-08-20T16:08:19Z

Sdhillon:

The Dash Express is based off of the legendary [[HXD8]]. The FCC ID is: EUNHXD8V2. It does have a debug port that is compatible with the OpenMoko FR debug board. It is fairly hard to get to (for a FR). It sits underneath the screen.

It has 3GB of internal flash. The DFU map is below:

<code>
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=1, name="u-boot"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=2, name="u-boot_env"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=3, name="config"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=4, name="factory"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=5, name="splash"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=6, name="kernel"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=7, name="alt_kernel"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=8, name="rootfs"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=9, name="alt_rootfs"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=10, name="dash_app"
Found Runtime: [0x0a5c:0x2110] devnum=5, cfg=0, intf=3, alt=0, name="UNDEFINED"
</code>

The serial interface is available only for u-boot. You can put it into DFU mode, and change the authorized_keys file to log into the unit.

I need to add more information to this page. I'm lazy. Hit me on irc: Sargun.
--[[User:Sdhillon|Sdhillon]] 18:20, 11 August 2008 (UTC)

HXD8

2008-08-19T19:21:55Z

Sdhillon:

HXD8 is the codename of a device that is going to be developped by Openmoko. For more information about other phones in development, visit [[Phone Development]].

On May 26th 2007 (GMT) Sean [http://lists.openmoko.org/pipermail/community/2007-May/005407.html confirmed] the existence of the device, said hardware support was almost done and cleverly told us to wait anxiously.

According to [http://lists.openmoko.org/pipermail/community/2007-October/011324.html this post] the device is a networked collaborative automotive GPS unit, from http://dash.net/ .

{{Speculations}}

It has been confirmed that the DE is based off of the HXD8.

==Hardware==
From the information found in the [https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/ hardware documentation] and [https://svn.openmoko.org/trunk/src/target/kernel/patches/ kernel patches] parts of the subversion repositories, the following specifications can be predicted.

===Processor===
According to https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2440-nand-disable-hwecc.patch the HXD8 will feature an [http://www.samsung.com/Products/Semiconductor/common/product_list.aspx?family_cd=MSC0102 S3C2440], capable of running up to 400MHz. The features are the same as the [http://www.samsung.com/products/semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2410/S3C2410.htm S3C2410] plus a camera interface.
*GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/gpio.txt

===Flash===
According to a currently available hardware patch, the device supports 1 NAND Flash device of up to 4G. (uncertain about what kind of G that is. Could be 4Gb (which makes about 0,5GB), could be 4GB).

The DE has 3G of Flash, and there is no NOR.

Some other patch implies that there is the possibility of connecting 3 NAND Flash chips.

===RAM===
128MB Random Access Memory, of which 2MB is used as a Framebuffer. https://svn.openmoko.org/trunk/src/target/u-boot/patches/uboot-hxd8.patch

===GSM/GPRS===
Using same GSM modem on GTA01 and GTA02, TI Calypso with 850/1800/1900 configuration.

=== SD-Card ===
The HXD8 features either an SD, miniSD or microSD-card slot.
* Connected to: S3C2410 MMC/SD controller
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c_mci.patch

===LCD Module (LCM)===
The HXD8 features a 480x272 pixel LCD (which is a widescreen (16:9) ratio) with PWM-controlled backlight.

===Light Sensor===
The HXD8 features a light sensor by TAOS Inc. (Texas Advanced Optoelectronic Solutions). It's either a [http://www.taosinc.com/product_detail.asp?cateid=4&proid=59 TLS2560] or a [http://www.taosinc.com/product_detail.asp?cateid=4&proid=60 TLS2561]. This light sensor will be included to measure ambient illuminance to control the LCM backlight illumination, or for exposure control for the camera (depends on location of the chip).
*Datasheet: [http://www.taosinc.com/images/product/document/tsl2560-e53.pdf tsl2560-e53.pdf]

===Power Management===
A Philips PCF50606 is used for power management.

* Data Sheet: [http://www.nxp.com/acrobat/literature/9397/75009763.pdf PCF50606/605]
* User Manual: [http://www.rockbox.org/twiki/pub/Main/DataSheets/pcf50606.pdf pcf50606.pdf]
* Connected to: S3C2440 via I2C.

===WiFi===
HXD8 features an SPI-connected Marvell 8686 based WiFi module.

===GPS===
The PMU chip's config contains a voltage group called GPS_3V3, and the [https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/gpio.txt gpio.txt] a set of GPS UART data pins. HXD8 using SirfSTAR III based module solution

[[Category:Hardware]]
[[Category:Hardware Support]]

HXD8

2008-08-19T19:20:52Z

Sdhillon:

HXD8 is the codename of a device that is going to be developped by Openmoko. For more information about other phones in development, visit [[Phone Development]].

On May 26th 2007 (GMT) Sean [http://lists.openmoko.org/pipermail/community/2007-May/005407.html confirmed] the existence of the device, said hardware support was almost done and cleverly told us to wait anxiously.

According to [http://lists.openmoko.org/pipermail/community/2007-October/011324.html this post] the device is a networked collaborative automotive GPS unit, from http://dash.net/ .

{{Speculations}}

It has been confirmed that the DE is based off of the HXD8.

==Hardware==
From the information found in the [https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/ hardware documentation] and [https://svn.openmoko.org/trunk/src/target/kernel/patches/ kernel patches] parts of the subversion repositories, the following specifications can be predicted.

===Processor===
According to https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2440-nand-disable-hwecc.patch the HXD8 will feature an [http://www.samsung.com/Products/Semiconductor/common/product_list.aspx?family_cd=MSC0102 S3C2440], capable of running up to 400MHz. The features are the same as the [http://www.samsung.com/products/semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2410/S3C2410.htm S3C2410] plus a camera interface.
*GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/gpio.txt

===Flash===
According to a currently available hardware patch, the device supports 1 NAND Flash device of up to 4G. (uncertain about what kind of G that is. Could be 4Gb (which makes about 0,5GB), could be 4GB).

The DE has 3G of Flash.

Some other patch implies that there is the possibility of connecting 3 NAND Flash chips.

===RAM===
128MB Random Access Memory, of which 2MB is used as a Framebuffer. https://svn.openmoko.org/trunk/src/target/u-boot/patches/uboot-hxd8.patch

===GSM/GPRS===
Using same GSM modem on GTA01 and GTA02, TI Calypso with 850/1800/1900 configuration.

=== SD-Card ===
The HXD8 features either an SD, miniSD or microSD-card slot.
* Connected to: S3C2410 MMC/SD controller
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c_mci.patch

===LCD Module (LCM)===
The HXD8 features a 480x272 pixel LCD (which is a widescreen (16:9) ratio) with PWM-controlled backlight.

===Light Sensor===
The HXD8 features a light sensor by TAOS Inc. (Texas Advanced Optoelectronic Solutions). It's either a [http://www.taosinc.com/product_detail.asp?cateid=4&proid=59 TLS2560] or a [http://www.taosinc.com/product_detail.asp?cateid=4&proid=60 TLS2561]. This light sensor will be included to measure ambient illuminance to control the LCM backlight illumination, or for exposure control for the camera (depends on location of the chip).
*Datasheet: [http://www.taosinc.com/images/product/document/tsl2560-e53.pdf tsl2560-e53.pdf]

===Power Management===
A Philips PCF50606 is used for power management.

* Data Sheet: [http://www.nxp.com/acrobat/literature/9397/75009763.pdf PCF50606/605]
* User Manual: [http://www.rockbox.org/twiki/pub/Main/DataSheets/pcf50606.pdf pcf50606.pdf]
* Connected to: S3C2440 via I2C.

===WiFi===
HXD8 features an SPI-connected Marvell 8686 based WiFi module.

===GPS===
The PMU chip's config contains a voltage group called GPS_3V3, and the [https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/gpio.txt gpio.txt] a set of GPS UART data pins. HXD8 using SirfSTAR III based module solution

[[Category:Hardware]]
[[Category:Hardware Support]]

Talk:HXD8

2008-08-19T19:19:53Z

Sdhillon:

are there any pictures of this device available? --[[User:Minime|Minime]] 13:28, 30 May 2007 (CEST)

Maybe this [http://www.flickr.com/photos/semiot/1471861932/] is HXD8? --[[User:Hanscats|Hanscats]] 20:45, 5 October 2007 (CEST)

Hello Dolfje, why did you roll back?

HXD8

2008-08-16T23:32:22Z

Sdhillon:

{{Hdsupport}}
like FIC is going to develop another device for OpenMoko quite soon, with the (code)name HXD8. On May 26th 2007 (GMT) Sean [http://lists.openmoko.org/pipermail/community/2007-May/005407.html confirmed] the existence of the device, said hardware support was almost done and cleverly told us to wait anxiously.

According to [http://lists.openmoko.org/pipermail/community/2007-October/011324.html this post] the device is a networked collaborative automotive GPS unit, from http://dash.net/ .

It has been confirmed that the DE is an HXD8

{| style="background-color:#EFEFFF;color:#000;border:1px solid #9F9FFF;margin:1em 5% 1em 5%;"
| style="padding:0.5em 0.5em;" |
| style="padding:0.5em 0.5em;" | Speculations: This {{{1|article or section}}} documents a device that is not yet confirmed formally and the device (if even released) may differ from the specifications given here. This page is based on well educated guesses, not facts.
|}
It looks
==Hardware==
From the information found in the [https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/ hardware documentation] and [https://svn.openmoko.org/trunk/src/target/kernel/patches/ kernel patches] parts of the subversion repositories, the following specifications can be predicted.

===Processor===
According to https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c2440-nand-disable-hwecc.patch the HXD8 will feature an [http://www.samsung.com/Products/Semiconductor/common/product_list.aspx?family_cd=MSC0102 S3C2440], capable of running up to 400MHz. The features are the same as the [http://www.samsung.com/products/semiconductor/MobileSoC/ApplicationProcessor/ARM9Series/S3C2410/S3C2410.htm S3C2410] plus a camera interface.
*GPIO Assignments: https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/gpio.txt

===Flash===
According to a currently available hardware patch, the device supports 1 NAND Flash device of up to 4G. (uncertain about what kind of G that is. Could be 4Gb (which makes about 0,5GB), could be 4GB).

The DE has 3G of Flash.

Some other patch implies that there is the possibility of connecting 3 NAND Flash chips.

===RAM===
128MB Random Access Memory, of which 2MB is used as a Framebuffer. https://svn.openmoko.org/trunk/src/target/u-boot/patches/uboot-hxd8.patch

===GSM/GPRS===
Using same GSM modem on GTA01 and GTA02, TI Calypso with 850/1800/1900 configuration.

=== SD-Card ===
The HXD8 features either an SD, miniSD or microSD-card slot.
* Connected to: S3C2410 MMC/SD controller
* Driver: https://svn.openmoko.org/trunk/src/target/kernel/patches/s3c_mci.patch

===LCD Module (LCM)===
The HXD8 features a 480x272 pixel LCD (which is a widescreen (16:9) ratio) with PWM-controlled backlight.

===Light Sensor===
The HXD8 features a light sensor by TAOS Inc. (Texas Advanced Optoelectronic Solutions). It's either a [http://www.taosinc.com/product_detail.asp?cateid=4&proid=59 TLS2560] or a [http://www.taosinc.com/product_detail.asp?cateid=4&proid=60 TLS2561]. This light sensor will be included to measure ambient illuminance to control the LCM backlight illumination, or for exposure control for the camera (depends on location of the chip).
*Datasheet: [http://www.taosinc.com/images/product/document/tsl2560-e53.pdf tsl2560-e53.pdf]

===Power Management===
A Philips PCF50606 is used for power management.

* Data Sheet: [http://www.nxp.com/acrobat/literature/9397/75009763.pdf PCF50606/605]
* User Manual: [http://www.rockbox.org/twiki/pub/Main/DataSheets/pcf50606.pdf pcf50606.pdf]
* Connected to: S3C2440 via I2C.

===WiFi===
HXD8 features an SPI-connected Marvell 8686 based WiFi module.

===GPS===
The PMU chip's config contains a voltage group called GPS_3V3, and the [https://svn.openmoko.org/trunk/doc/hardware/HXD8v011/gpio.txt gpio.txt] a set of GPS UART data pins. HXD8 using SirfSTAR III based module solution

[[Category:Hardware]]
[[Category:Hardware Support]]

Dash Express

2008-08-11T18:20:24Z

Sdhillon: New page: The Dash Express is based off of the legendary HXD8. It does have a debug port that is compatible with the OpenMoko FR debug board. It is fairly hard to get to (for a FR). It sits unde...

The Dash Express is based off of the legendary [[HXD8]]. It does have a debug port that is compatible with the OpenMoko FR debug board. It is fairly hard to get to (for a FR). It sits underneath the screen.

It has 3GB of internal flash. The DFU map is below:

<code>
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=1, name="u-boot"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=2, name="u-boot_env"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=3, name="config"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=4, name="factory"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=5, name="splash"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=6, name="kernel"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=7, name="alt_kernel"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=8, name="rootfs"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=9, name="alt_rootfs"
Found DFU: [0x1cd8:0x511a] devnum=13, cfg=0, intf=0, alt=10, name="dash_app"
Found Runtime: [0x0a5c:0x2110] devnum=5, cfg=0, intf=3, alt=0, name="UNDEFINED"
</code>

The serial interface is available only for u-boot. You can put it into DFU mode, and change the authorized_keys file to log into the unit.

I need to add more information to this page. I'm lazy. Hit me on irc: Sargun.
--[[User:Sdhillon|Sdhillon]] 18:20, 11 August 2008 (UTC)