Database Users

Help Neaded to Upgrade The PPC 6800 RAM

...............................

I'm not sure but I think it needs special tools... at least a lot of other PPCs do.

So it is possible??
I want to upgrade my 6700 to the 6800 but the lack of RAM has going for the Touch, I don't want to give up the keyboard and wifi but it seems worth the sacrifice. But if it is possible to upgrade the RAM on the 6800 well that changes everything.
Could someone with experience pls give some feedback on the matter.
Thanks

Yes it is posible everything is posible I'm not an expert means I'm not an ingenier but I'm IPC 610 Certified I Know A+ and Network + and more..I have work directly with ingeniers developing and designing all kinds of mother boards I kow the tools needed and I also know that may be we will need to buy a hi amount of chips to the fabric I am intereste in kowing if any one can tell me before boyding my waranty what it is the exact chip and who is the vendor so I can start working with some of my friends soldering and unpgrading the RAM...

you need to be able to reliably solder mBGA components and be able to modify the bootloader/kernel to use that amount of ram

I know How to soler SMT componets... that is not a problem I worked as QC inspector of SMT components....

how did you manage to transpose your accent in your post?

I think the possible destruction of your Device is not worth the hassle... but you're welcome to try.
Do tell if you manage to pull it off successfully

Yeah, it is possible. Since you seem to already know about SMT rework and have access to proper tools, there's a fair chance you actually succeed. To get the proper chip you would probably need to open up your device and see the part number of your current RAM chip and search for its datasheet. Based on that, you'll need to choose exactly the same kind (same memory type, same timings, same pinout, preferably the same manufacturer) of memory, but of bigger capacity.
There are even some companies offering PocketPC upgrade service (just run a google search for PocketPC RAM upgrade).
And as far as i know, WinMo will use the bigger ram chip without any bootloader/kernel modifications, just like your PC (at least a winCE 4 Simpad did) - but you'll need to do some more research here since i never tried it personally and can't guarantee anything.
Unfortunately, BGA chip type limits you to 128MB ram (as far as i know, it's the biggest capacity you'll get in a single chip). In case of SOT/TQFN memory it was possible to solder a second chip on top of the old one (however i don't remember the exact details), therefore doubling the RAM size. Obviously, it's not possible with BGA, and even if it was, there's simply no room for that inside a modern device

HP IPAQ 310 Hacking

I just picked up an HP IPAQ 310 GPS device based on Windows CE 5.0. As far as standalone GPS devices go this one is very highly spec'ed:
http://www.amazon.com/310-Bluetooth-4-3-Inch-Widescreen-Navigator/dp/B000VRYLU2
600Mhz DualCore Centrality Titan Platform with on-chip GPS
300Mhz DSP
128MB RAM
2GB Flash
4.3" 800x480 LCD display
Bluetooth 2.0+EDR
USB 2.0
Windows.CE 5.0
It currently runs a variant of IGO 2008 navigation program and has some onboard games from PDAMill.
This is my first Window.CE project. Does anyone know where I can get the appopriate BSPs etc.. to allow me to build a bootable/working CE Image from Platform Builder 5 or 6 with full driver support?
My dream is to put a Microsoft Automotive software stack on this see how close I can get to a converged device like the Microsoft/Ford Sync. It will also be a learning experience.
In particular my end goal is to enable the following scenarios:
Voice recognition
Bluetooth DUN/PAN
Bluetooth Handsfree and voice dialing
Information Services (via web services interface to online services from Google & Microsoft). Think of movie times/locations, traffic, gas prices,address/phone/poi lookup etc..
Full fidelity video/audio player
Launch native and emulated games
Plug-in framework to extend the features
Navigation

The spec of the HP 310 Travel Companion is very impressive and I like the idea of it being a multi-purpose device. The 4.3 inch display is large enough for use as a GPS as well as watching videos. Seriously I wouldn't need GPS function every day so it is great be able to use it for other purposes. I wish one day it would be able to receive free digital TV signal like those from DVB-T or DVB-H. That would make it a truly Travel Companion.

Wow you really are dreaming if you think you can get a BSP for this device.
Or for any device for that matter.
These are never released and I never even heard of one being leaked! Just like any other proprietary code BSPs are highly guarded.
What you are trying to do is pretty ambitious, but if you want to rebuild OS for something by your self you better get a Linux device.
Sorry.

levenum said:
Wow you really are dreaming if you think you can get a BSP for this device.
Or for any device for that matter.
These are never released and I never even heard of one being leaked! Just like any other proprietary code BSPs are highly guarded.
What you are trying to do is pretty ambitious, but if you want to rebuild OS for something by your self you better get a Linux device.
Sorry.
Click to expand...
Click to collapse
Okay. Does anyone know much about the Microsoft Sync / Microsoft Automative software stack for Windows CE?

Regarding Windows Automotive:
You must be dreaming if you think you can source an Windows Automotive (or is it Microsoft Auto now?) OEM Adaptation Kit to do this!
As I understand, you need to be a huge OEM/ODM or car manufacturer like Ford and sign an NDA to even get any kind of access to it.
Considering its difficult enough to even source a Windows Mobile kit, I'd imagine its even harder to get Windows Automotive considering the circumstances...
However, there may be another way to source the Windows Automotive OS components besides obtaining an official kit...
Perhaps if there are some firmware updates for one of the Windows Automotive devices from Fiat, Ford, Clarion, etc. you can dump the ROM image and extract the files. Now, even if you do that you might still need to fix the relocations of every dll file...but it still might work on your HP after all that. I'd imagine you would also need to manually figure out the skin format of the Windows Automotive apps since you don't have the actual desktop tools to generate them...
I doubt you would really even need to source a BSP and build an image once you get this far. Chances are the apps you extract will run just fine from an SD card or the internal flash disk of your device if configured properly.

Off topic...
I managed to brick one of these today within the first hour. Just testing out Flux Challenge when it threw up a Please Wait screen. Soft-reset and now it sticks at the HP splash screen; had to get it sent back. Thank goodness I was only testing it.
Given this plus its molasses-slow performance, I think I'd choose something else if I really wanted to do any sort of modding...

Hi i have a 314 UK Version and wants to flash it with the german version.
Has anybody tried it ?

modellbobby said:
Hi i have a 314 UK Version and wants to flash it with the german version.
Click to expand...
Click to collapse
Where did you get the ROM ?

some sort of firmware update is on the HP FTP server (also includes newer maps)
Use the engineering mode to dump and restore the ROM.

have an Ipaq 310 running igo8 and finean4, like to get garmin but seems to have a resolution problem, anyboby can help plz"
[8/23/08 21:36:29 67512KB 4.20.50wp]
GFX_buf_alloc: Invalid area (-20048 480)
[8/23/08 21:36:29 67508KB 4.20.50wp]
Failure 87 allocating bitmap of size (-20048,480) 16 bpp (0)
[8/23/08 21:36:29 67448KB 4.20.50wp]
Read Access violation at data address 0xFFFFFFFC.
Program address 0x00058080 in background thread NULL (CSubAppThread::Run Garmin Mobile XT)
[8/23/08 21:36:30 67440KB 4.20.50wp]
CALL STACK:
0x18156EC0
0x182B7104
0x029FC9C4
0x02A03D24
0x93C0A090
0x93C33EA8
0x93C0DEB4
0x93C09FA8
0x18058080
0x18059900
0x180D18B8
0x180D1CEC
0x182B71E0
0x182B7010
0x182B6C54
0x029DDF04

klingklang01 said:
have an Ipaq 310 running igo8 and finean4, like to get garmin but seems to have a resolution problem, anyboby can help plz"
[8/23/08 21:36:29 67512KB 4.20.50wp]
GFX_buf_alloc: Invalid area (-20048 480)
[8/23/08 21:36:29 67508KB 4.20.50wp]
Failure 87 allocating bitmap of size (-20048,480) 16 bpp (0)
[8/23/08 21:36:29 67448KB 4.20.50wp]
Read Access violation at data address 0xFFFFFFFC.
Program address 0x00058080 in background thread NULL (CSubAppThread::Run Garmin Mobile XT)
[8/23/08 21:36:30 67440KB 4.20.50wp]
CALL STACK:
0x18156EC0
0x182B7104
0x029FC9C4
0x02A03D24
0x93C0A090
0x93C33EA8
0x93C0DEB4
0x93C09FA8
0x18058080
0x18059900
0x180D18B8
0x180D1CEC
0x182B71E0
0x182B7010
0x182B6C54
0x029DDF04
Click to expand...
Click to collapse
Is seem to be the resolution problem of our GPS... I'm having the same issue also. We need to find some doc to change the resolution... I'm still searching for the solution, any1 know how to cange it???
Regards,
Jeff

iPAQ 3xx Series
This is an old post but I thought I'd confirm a couple things for the record, should anybody be looking into this kind of info in future although the device is technically EOL.
40th Floor said:
As far as I know, this iPAQ is the only device to have ever even used the (exact) processor it's using.
Click to expand...
Click to collapse
Yes this is the only iPAQ with a dual core processor for that matter.
40th Floor said:
And funny? Funny is that when it's on a charger (any external power at all) it runs at half speed (300 MHz) but when completely on battery it runs at 600 MHz.
Click to expand...
Click to collapse
The original USB 2.0 spec called for no more than 500ma to be pumped through the USB line. Around the time WM5 was being rolled out, HP had to wrestle with the USB klan to convince them that wasn't enough to run a device and charge it. HP was making better use of the standard by doing more with it than the authorities thought was needed. They eventually backed off and HP up through the time I'm writing this ships an AC adapter with each device that has a mini or micro USB connector; obviouisly needed since the 22-pin connector died with the 6900 (Moose) device. The adapters provide up to 1000ma of juice.
Now consider this: Prior to dropping the 22-pin connector HP shipped 2amp chargers which provided enough juice to run the device and charge the battery at the same time. The 22-pin standard came out with the h3800 Series which ran a 400MHz ARM single core and didn't have fancy stuff like WiFi built in, and only had a standard QVGA (320x240) screen.
So how could a device with a GPS, such a larger screen, and a dual core 600MHz CPU be expected to even operate with a 1amp charger, let alone charge the battery?
Playing with the OS - Differences between WinCE platforms
For those who would like to play with the OS, understand this device runs Windows Mobile 5 for devices and NOT the Pocket PC OS. Pocket PC was a platform, just like SmartPhone was a platform. Although Microsoft changes the names to confuse the innocent, we're still talking about a few significant differences.
Consider Pocket PC (or WinMo or WinMo classic depending on the wind and Microsoft's mood), a superset of WinCE that adds a few other things to the core WinCE 5 platform. Search the web for posts by people who have managed to get PocketPC apps to run on their Handheld PC (HPC) such as the MobilePro 900c. The same kind of things would apply to the iPAQ 300. The differences are not all that significant if you know which DLLs need to be added.
In short, the iPAQ 300 Series is closer to a HPC than PocketPC OS-wise. The good news is, this version of Platform Builder can be purchased, whereas the one for WinMo is strictly guarded by Microsoft and released only to OEMs like HP and Dell.
The hardest thing you'll run across is that the digitizer drivers were not optimized for fine work, just for finger use. When you bypass the NavNGo "OS" to run the underlying WinCE OS and try to use a soft keyboard, for example, you'll see the jitter I'm talking about.
The iPAQ 300 Series could have been more but it was designed to compete with other GPS devices and that's really all. The hardware was really pretty great, but the device shipped with significant bugs that were addressed post-release.
If you want a PocketPC that also has GPS, the h5900 Series was a better choice. Not dual core CPU though

Anyone still running this fine device?
I've got mine running Igo8.3, works pretty good.
I'd be interested to hear if anyone is running Primo on it.
Also, anyone know where to get a TMC antenna for this unit?
Cheers

i still have a working one
unfortunately i think it have gone into battery shutdown to little charge in the battery for an extended period of time,
it will however come to life if i plug it into the car
i was thinking tonight it would be cool to hack droid onto it

GPS activation

Hello !
I will get my shift this week.
I have read, that there is a GPS integrated.
Does anybody know how I can activate it within WM so that I will be able to run TOMTOM ?
Here are the specs : ( german )
in the 3rd line you can read GPS
Betriebssystem: Windows Vista® Business, Deutsch
Prozessor: Intel® Stealey 800MHz + 945GMS + ICH7U; Qualcomm® MSM 7200, 400MHz
GPS
Fingerabdrucksensor
Speicher: ROM: 128 MB for SnapVUE RAM: 1GB DDR2 microDIMM RAM for Vista + 64 MB for SnapVUE?
Hard Disk: 1.8-inch 40 GB or 60 GB hard disk (manufacturer`s option)
SD Speicherkarte (SD 2.0 kompatibel)
Größe: 207 mm (L) x 129 mm (W) x 25 mm (T)
Gewicht: 800g mit Akku
QWERTZ Tastatur
Fortschrittliche Touchscreen Technologie:
7" TFT-LCD mit Hintergrundbeleuchtung und TouchFLO Bedienung
800 x 480 Bildpunkte
Kommunikation:
HSDPA/UMTS: Tri-band 850, 1900, 2100 MHz
GSM/GPRS/EDGE: Quad-band 850, 900, 1800, 1900 MHz
SIM Kard Slot
Kamera: VGA Kamera für WEB / Videotelefonie
Audio:
Microfone / Receiver
Lautsprecher für die Handsfree-Unterstützung
Verbindungen und Anschlüsse:
Bluetooth® 2.0
Wi-Fi: IEEE 802.11 b/g
HTC ExtUSB (11-Pin mini-USB und Audiokarte in einem)
Stromversorgung:
Wiederaufladbares und auswechselbares Lithium-Ion Polymer Akku
Kapazität: 2700 mAh
AC Adapter
AC Eingangsspannung: 90 ~ 265V AC, 47/63Hz
DC Ausgangsspannung: 12Vdc, 3A

I think you may be a little disappointed with the GPS side of things? I don't think people have had much headway with restrictions the shift currently offers. First the integrated GPS is somewhat of an urban myth? It could be accessible, but I've not seen a 100% success story yet. Second if integrated GPS was present, you need to open up SnapVu to full WM6, then I understand that it does not currently have much space to put software? Thirdly If you managed to fit it on and can not access GPS then you also can not access either the bluetooth or USB through the SnapVu side. It does sound a little grim and I may be wrong? But that being said I love my Shift!!! and I'm sure before long the XDA Developer GOD's will sort out all of these downsides.

shift FAQ
Q: Does the Shift have a GPS module ?
A: Yes the shift have a build in GPS chip, but since we don't have any drivers for it yet, we are not sure if antenna etc. are there. (on the prototype units it was working so there is a good chance it will work on production models to)
NOTE: After i opened up my shift i can confirm the GPS antenna is there !!

here is the test of SHIFT with QSTARZ GPS
http://www.umpcfever.com/news/?postid=705
I think we can use the external GPS instead till the enabling of the internal one!

In the video, he is using Vista side - not SnapVu side! I don't think you are able to access either the USB or bluetooth on the Snapvu side.

kitkat_dave said:
In the video, he is using Vista side - not SnapVu side! I don't think you are able to access either the USB or bluetooth on the Snapvu side.
Click to expand...
Click to collapse
that should all be changing very soon. gps should be pretty easy to enable since it was in the test versions.

There is no special GPS chipset in the Shift - GPS functionality is just one of the many functions provided by the Qualcom MSM7200 - yeah, basically the chip that powers the WM part of the shift, including GSM/3G Radio. By the way: SnapVUE with the WindowsMobile-Like stuff is just a cheap side product of using the MSM7200: The processor is already there... even graphics and sound is embedded in the MSM7200 - in fact, HTC just needed to add some cheap ram, some cheap flash, and some glue logic (imagine a simble console switch that switches the screen, keyboard and touchscreen between Vista and SnapVue).
Regarding GPS, the "problem" is: The technology (drivers) for GPS are there - in the WindowsMobile/SnapVUE-Part (propably not implemented in the final ROM version, but at least, HTC has it available). BUT: SnapVue is not sold as WindowsMobile, but as SnapVue, without any support for 3rd party applications - it would not make sense to provide GPS within WindowsMobile/SnapVue (especially as there is no connection to the SD slot... yeah, stop dreaming, there is really no way to access SD or the HardDisk from SnapVue).
So, why is the GPS antenna there?? Well, there IS an potential option to use the GPS: HTC might (!) develop a software that provides a (virtual) GPS within VISTA - using a connector software in SnapVue. So, easy way to add another sales argument later (to prevent price dropping to fast) - and hey, they obviously just had not the necessary resources to get that software developed. Look at ShagControl.... instable, not really SP1 capable... they have more important stuff to get fixed than enabling the embedded GPS.

skin57 said:
There is no special GPS chipset in the Shift - GPS functionality is just one of the many functions provided by the Qualcom MSM7200 - yeah, basically the chip that powers the WM part of the shift, including GSM/3G Radio. By the way: SnapVUE with the WindowsMobile-Like stuff is just a cheap side product of using the MSM7200: The processor is already there... even graphics and sound is embedded in the MSM7200 - in fact, HTC just needed to add some cheap ram, some cheap flash, and some glue logic (imagine a simble console switch that switches the screen, keyboard and touchscreen between Vista and SnapVue).
Regarding GPS, the "problem" is: The technology (drivers) for GPS are there - in the WindowsMobile/SnapVUE-Part (propably not implemented in the final ROM version, but at least, HTC has it available). BUT: SnapVue is not sold as WindowsMobile, but as SnapVue, without any support for 3rd party applications - it would not make sense to provide GPS within WindowsMobile/SnapVue (especially as there is no connection to the SD slot... yeah, stop dreaming, there is really no way to access SD or the HardDisk from SnapVue).
So, why is the GPS antenna there?? Well, there IS an potential option to use the GPS: HTC might (!) develop a software that provides a (virtual) GPS within VISTA - using a connector software in SnapVue. So, easy way to add another sales argument later (to prevent price dropping to fast) - and hey, they obviously just had not the necessary resources to get that software developed. Look at ShagControl.... instable, not really SP1 capable... they have more important stuff to get fixed than enabling the embedded GPS.
Click to expand...
Click to collapse
snapvue is windows mobile. everything just has been made hidden. everything can be done with the proper time. gps anyway when enabled will be in the wm side. thats because there are better apps there and it will use less power then.

Pawel062 said:
snapvue is windows mobile. everything just has been made hidden. everything can be done with the proper time. gps anyway when enabled will be in the wm side. thats because there are better apps there and it will use less power then.
Click to expand...
Click to collapse
There is no way (really!) to access SD or HDD from SnapVue (without running VISTA at the same time). So, GPS is mostly useless in SnapVue/WM. The only usefull way to use the GPS would be an GPS driver that pipes the GPS from WM side (SnapVue) to VISTA.
Remember: HTC doesn't sold you a WindowsMobile implementation, but SnapeVue. Period.

Pawel062 said:
snapvue is windows mobile. everything just has been made hidden. everything can be done with the proper time. gps anyway when enabled will be in the wm side. thats because there are better apps there and it will use less power then.
Click to expand...
Click to collapse
+1 and we could get it soon .. with the Shift Project

skin57 said:
There is no way (really!) to access SD or HDD from SnapVue (without running VISTA at the same time). So, GPS is mostly useless in SnapVue/WM. The only usefull way to use the GPS would be an GPS driver that pipes the GPS from WM side (SnapVue) to VISTA.
Remember: HTC doesn't sold you a WindowsMobile implementation, but SnapeVue. Period.
Click to expand...
Click to collapse
wow u people know lots about the shift *rollseyes* snapvue is wm!!! i'm not going to keep explaining myself to people who don't have a clue.

Pawel062 said:
wow u people know lots about the shift *rollseyes* snapvue is wm!!! i'm not going to keep explaining myself to people who don't have a clue.
Click to expand...
Click to collapse
Of course SnapVUE is WM, no question - but HTC sells it as SnapVUE. By doing so, they don't support ANY third party application...
The main limitation of WM on the Shift is storage space: There is no way to add more space (e.g. by using an SD card...), as WM don't has an physical connection to the SD port, the Harddisk, the USB port... but without additional storage space, the use of WM is really limited. I've installed Opera to be able to surf without VISTA, that's enough for me. All i'd be happy about is a connection app/driver that makes the GPS (part of the MSM7200, thus, the WM part) available in Vista.
I bought a VISTA machine, not a WM device.

skin57 said:
...
The main limitation of WM on the Shift is storage space: There is no way to add more space (e.g. by using an SD card...), as WM don't has an physical connection to the SD port, the Harddisk, the USB port...
...
Click to expand...
Click to collapse
Everyone keeps talking about no physical connection.
Guys, I talked to some technical ppl and they say it's possible to use the SD card under WM.
Please wait for the Shift project team finds a solution and stop telling people that there is no connection.

michael85 said:
Everyone keeps talking about no physical connection.
Guys, I talked to some technical ppl and they say it's possible to use the SD card under WM.
Please wait for the Shift project team finds a solution and stop telling people that there is no connection.
Click to expand...
Click to collapse
Which technical people? What do they know that the rest of us don't and how?
If you look at the SD card under Vista you will see that it is on the PCI bus. As far as I can see, the only real connection between the Vista and WM sides is via the USB bus and the SD card isn't on that. Now, I wouldn't stick my neck out and say that it definitely isn't connected to the WM side, but it certainly seems very likely to me.
It is always better to err on the side of caution - telling people that the Shift project team *will* find a solution is worse than telling people that they won't, since if you buy the device believing that SD card access will become available you may end up being sorely disappointed! In this case, it is better to buy with a pessimistic attitude, and then be pleasantly surprised if SD card access is made available.
Regards,
Dave

skin57 said:
Of course SnapVUE is WM, no question - but HTC sells it as SnapVUE. By doing so, they don't support ANY third party application...
The main limitation of WM on the Shift is storage space: There is no way to add more space (e.g. by using an SD card...), as WM don't has an physical connection to the SD port, the Harddisk, the USB port... but without additional storage space, the use of WM is really limited. I've installed Opera to be able to surf without VISTA, that's enough for me. All i'd be happy about is a connection app/driver that makes the GPS (part of the MSM7200, thus, the WM part) available in Vista.
I bought a VISTA machine, not a WM device.
Click to expand...
Click to collapse
correct but with time most of those things can be brought back to the shift. one of things we will try to do is to get the hd or sd back so u can all install more stuff.

foxmeister said:
Which technical people? What do they know that the rest of us don't and how?
If you look at the SD card under Vista you will see that it is on the PCI bus. As far as I can see, the only real connection between the Vista and WM sides is via the USB bus and the SD card isn't on that. Now, I wouldn't stick my neck out and say that it definitely isn't connected to the WM side, but it certainly seems very likely to me.
It is always better to err on the side of caution - telling people that the Shift project team *will* find a solution is worse than telling people that they won't, since if you buy the device believing that SD card access will become available you may end up being sorely disappointed! In this case, it is better to buy with a pessimistic attitude, and then be pleasantly surprised if SD card access is made available.
Regards,
Dave
Click to expand...
Click to collapse
no one is saying u should buy it bc it will be coming soon. we are saying it isnt impossible to bring it back. if i remember correctly the sd is tied into wm actually but on the very low level.

Pawel062 said:
correct but with time most of those things can be brought back to the shift. one of things we will try to do is to get the hd or sd back so u can all install more stuff.
Click to expand...
Click to collapse
Of course i correct you: SD and HDD are connected to the PC-Side only. Hey, how would you implement a device-sharing on storage devices between two systems?? Imagine accessing the SD-Card from VISTA and WM at the same time... That's stuff that is implemented in Cluster-Solutions with SANs - but not in an UMPC, especially not by HTC.
Stop dreaming.

skin57 said:
Of course i correct you: SD and HDD are connected to the PC-Side only. Hey, how would you implement a device-sharing on storage devices between two systems?? Imagine accessing the SD-Card from VISTA and WM at the same time... That's stuff that is implemented in Cluster-Solutions with SANs - but not in an UMPC, especially not by HTC.
Stop dreaming.
Click to expand...
Click to collapse
I think the only way is to open shift, and solder inside an SD-CARD..

I'd be up for a little soldering, and I'd happily lose the SD card from Vista to gain it on the WinMo side. But I won't be doing any hardware mods until the warranty has expired, by then I'll have newer, better toys and won't mind risking the Shift so much.

skin57 said:
Of course i correct you: SD and HDD are connected to the PC-Side only. Hey, how would you implement a device-sharing on storage devices between two systems?? Imagine accessing the SD-Card from VISTA and WM at the same time... That's stuff that is implemented in Cluster-Solutions with SANs - but not in an UMPC, especially not by HTC.
Stop dreaming.
Click to expand...
Click to collapse
Yeah right. You seems like a big boy knowing big thinks about clusters and SANs, but nobody is talking about simultaneous access. SD drivers can be disables on one side or one other depending on the needs.
And just to clear up thinks, debug tools are able to log to the sd card on WM side. It means lower level access does indeed exist.
There is no signal or proof that it is possible for the HDD, but I'm sure nobody was really hopping for this to happen.

Porting Android to HP iPAQ 310 Series Travel Companion

Hello everyone,
I am interested in a port of Android for the HP iPAQ 310 Series Travel Companion. It seems like a fairly capable piece of hardware, but HP dropped the product and hampered by some buggy software issues. It normally runs Windows CE 5.0 with a custom shell. I am trying to find out if it is feasible, any interest, and if there are any previous Linux ports that might make a Android port feasible. This is what I have found out so far:
Here are the product features from HP:
Processor Titan 600 MHz ARM11 Dual-Core Processor
Display 4.3" WVGA 800x480 TFT with touch screen, antiglare, landscape oriented, 16bit RGB depth
Memory Up to 2.0 GB flash ROM for persistent storage, depending on model 128 MB SDRAM for running applications
External Power AC Input: 100~240 Vac, 50/60 Hz, AC Input current: 0.2 A ac max Output Voltage: 5Vdc (typical)
SD Slot Supports SD memory
Antenna Internal Bluetooth antenna
Audio Integrated microphone, speaker, and one 3.5–mm stereo headset jack, 5–band equalizer and 3D sound adjustment
Battery 1,700 mAh Li-ion removable/rechargeable battery
Bluetooth Bluetooth 2.0 with Enhanced Data Rate, typical 10 meter range (approximately 33 feet)–High-speed, low-power, shortrange wireless communication with other Bluetooth devices
GPS Receiver SiRF embedded GPS receiver with InstantFix(TM) time to first fix acceleration
GPS Antenna Internal patch antenna
Physical specifications
Width US: 4.3 in
Metric: 110.2 mm
Height US: 3.4 in
Metric: 86.8 mm
Depth US: 0.7 in
Metric: 18.2 mm
Weight US: 6.6 oz
Metric: 187 g
The screen is beautiful on the thing, the hardware seems to have potential, although it does lack Wifi and WWAN. An SD Wifi card can always be added or it could be tethered via Bluetooth for network access. But never the less, I think it would be a wonderful Android device, especially if there were some way of caching Google Map data on SD or in the 2GB of built-in SLC memory.
I tried to dig up what I can on the internals. I have not been able to find a Linux port specifically to the Centrality Titan processor. Centrality was purchased by Sirf. Since it is ARM11 based, I imagine it shouldn't be too difficult to get Linux up and running.
The GPS receiver is the SE4110L.
I/O is handled by the Wolfson Microelectronics WM9712:
Voice processing is handled by the Fortemedia FM1182.
Bluetooth is handled by the Cambridge Silicon Radio BlueCore 4.
What do you guys think? Would this be feasible to pull off? Are there any other Android based devices that have similar hardware that make make this possible?

Still no updates?
I am going to try Andromnia Port for Samsung Omnia on this device. Just for start.

Try something with a WVGA resolution. Only other 4.3 inch screen device is the hd2.... Never heard of this, is it old?

froggylover1345 said:
Try something with a WVGA resolution. Only other 4.3 inch screen device is the hd2.... Never heard of this, is it old?
Click to expand...
Click to collapse
It is about 2 years old, great device but so stupidly abandoned by HP (along with entire iPaq brand)...
Great 800x480 screen, 600Mhz CPU with both GPU and GPS. Perfect ground for Android!

bump
I own 2 of these lol. I also abandoned it when i started buying android phones. I am interested in this as well.

Hello everyone,
I am glad to see there is some interest in an Android port to this device. I wasn't sure I would receive any replies at first. Now that I see a few of us would like a port lets see what we need to do to accomplish this. I will investigate a few venues for us this afternoon. It is damn shame to let a capable hardware device like this fall by the wayside. It really seemed to have great potential.
I would imagine their are two routes to take. One would be to natively boot Android on the device. This would require the most work and I do not know if all of the hardware would be supported.
The other option would be to go the route of booting Android from a Windows CE based boot loader, similar to other Windows Mobile to Android ports. I think this would probably be the easier route to take.
Does anyone know of any other Windows Mobile or native Android devices with similar components?

Michael.Rose said:
The other option would be to go the route of booting Android from a Windows CE based boot loader, similar to other Windows Mobile to Android ports. I think this would probably be the easier route to take.
Does anyone know of any other Windows Mobile or native Android devices with similar components?
Click to expand...
Click to collapse
As far as I know, Centrality (SIRF) Titan is used in only one type of device - out poor Travel Companion.
Though, I could be compatible with some other CPUs. I'll try to find out.

Hi guys, I've got one of these devices, for some time now,
I've mannaged to hack it, by changing registry settings in
HKLM\INIT and put explorer as an extra launch.
I did find something here:
http://www.smartqmid.com/phpBB3/viewforum.php?f=12
There is simmilar device running linux
and they trying android to boot from SD card:
http://www.jiongtang.com/blog/html/smartq5/boot-the-smartq-5-from-sd-card.html
You have to partition SD card, like here:
http://www.jiongtang.com/blog/html/...-install-software-on-sd-card-for-smartq5.html
There is more info there.

So any luck with running Android on iPAQ?

Vadimus_ca said:
So any luck with running Android on iPAQ?
Click to expand...
Click to collapse
I think, you have to install Linux first and then load Android.
Go here and start reading:
handhelds.org/handhelds-faq/handhelds-faq.html
just add www at the front, someone stuffed something up and
I cannot post url's
I have already started, very interesting article, scroll down and get
PDF file.

Hey guys,
has anybody, by any chance, got the data sheets for this Titan processor,
some owners managed to brick the devices beyond repairs, I think it was due to very low temperature last winter, and the NAND, and boot loader were erased.
Someone is trying to develop some dumper, which would allow to dump the bootloader from working unit and then load it back by JTAG, and then all the rest by normal way from SD card, but he needs these Data Sheets.
HP is not interested in helping, they want money.
One of the rom cooking Gurus has developed simple tool to convert DiskRW's
image dump to the working boot files, which are TINYNK.bin, CHAIN.bin and NK.bin, I have managed to add some .dll files from MioPocket to NK.bin, I think
something about 20 files including all WiFi dlls.
There is big potential here.

hey nice people,
I have managed to install and run DOS on my 312 model,
there is only small problem, the very small keyboard, which pops up
as a part of the DOS screen. We can use PC's keyboard or maybe some
USB one.
There is no far to install Linux and Android, just have to find one.
Sorry, didn't put any links and names:
I've installed PcketDOS_1123 from here:
http://www.pocketdos.com/download.htm
The OEM version is not free, the other one is.

Look at this:
http://dev.openaos.org/browser/trun...-4.1.2_glibc-2.5_linux-2.6.18.ptxconfig?rev=6

interesting thread. Anyone still tinkering with their 310's?

yeah another bump
I'm an interested 310 owner

A101it mainboard hacking and chipset information

Hi,
as i wrote in another thread, i purchased a bricked A101.
There's no response from the system so i decided to start investigation on the hardware .
A101it chipset information:
Processor
• Ti OMAP3630 (515-pin CBB/P BGA package) ARM Cortex A8 at 1 GHz with DSP
• POWERVR SGX530 Graphic accelerator: 3D OpenGL ES 2.0
Memory
• 256MB LPDDR SDRAM (168-pin PoP BGA package) soldered on top of OMAP3630
• 8/16GB eMMC (169-pin BGA package) connected to OMAP3630 internal mmc2 interface
Interfaces
• USB slave 2.0 (OMAP3630 internal interface, MicroUSB connector)
• USB host interface (TPS65921 host interface, TYP A connector)
• Micro SD slot (OMAP3630 internal mmc1 interface, SDHC compatible)
Display subsystem
• ChiMei 10.1" TFT-Display N101L6-L02 (18Bit-LVDS interface)
• Ti SN75LVDS83B LVDS transmitter (56-pin BGA package)
Touchscreen subsystem
• Pixcir capacitiv touchscreen unit (TR16C0 controller, USB interface)
• Ti TUSB2551A USB transceiver (16-pin QFN package)
HDMI subsystem
• NXP TDA19989AET 24-Bit HDMI transmitter
• HDMI output (19-pin Mini HDMI connector)
Communication
• Ti WL1270/1 WiFi (802.11 b/g/n)
• Ti WL1270/1 Bluetooth 2.1 EDR
Miscellaneous
• Built-in speaker
• Built-in Microphone
• Freescale MMA7660FC G-sensor
• Omnivison OV7675 VGA camera (0.3M)
Power source
• Ti TPS65921 power management chip
• Intersil ISL9220 LiPo charger
• Internal: Lithium Polymer battery
• External: 5V/1A Power adapter/charger
To get some detailed informations about these chips, i made a sweet datasheet collection.
Grab the zip-file here.
TBC...
EDIT: The brick issue is solved.
The platform did not boot up due to a broken connection to onboard RAM.
This thread will present various hacks and other stuff a geek might have fun with
Read on for some more information.
So here's my first result:
I successfully located the sys_boot signals of the OMAP3630.
I made a first test by changing the default boot mode.
With sys_boot5 pulled high the boot order changes to peripheral boot first.
In other words you may use this tool to directly access the OMAP memory (e.g. RAM).
In theory it should alos be possible to boot the device form external microSD as well, but at factory default the microSD slot is covered by power management. In other words, power is switched off at boot time.
This could be hacked as well
My attempt will be to un-brick my device by using external boot mechanism.
Maybe i'll need some help at a later point!
EDIT: Peripheral boot modes had successfully been verifed.
It definitely works on the Archos 101. Perhaps this may be useful for some open bootloader project.
Aynway, i already discovered some other things, that might be helpful for hardware hackers. So if you are kind leave a comment or ask some questions.
Stay tuned!
scholbert

Oh, that's interesting ... I don't know anything about hardware hacking but I'd like to learn hope you will show us ... keep on the good effort ... and I'll keep an eye on this tread .... might come handy ... jejeje

sounds great, keep on rolling

peripheral boot
Hi,
thanks for your replies.
So as expected using peripheral boot over USB/UART is working (sys_boot5 pulled high).
At least the ASIC ID is send correctly and the initial communication starts.
See the screenshot attached.
Flash V1.6 also got a eMMC driver included.
So this could be the way .
Right now there's an error message:
Code:
Unknown status message 'dKAYd 2nd stdrted?' during peripheral boot (waiting for 2nd)
I guess the response should be: OKAY! 2nd started?
EDIT:
MMMh strange... i'll have to find out who is generating this message.
If it is comming from OMAP the SDRAM setup should be verified.
Seems that the LSB byte stuck @ 0x64.
Code:
dKAYd 2nd stdrted?
ascii = dKAY -> hex = 0x59414b64 (msb..lsb)
ascii = d 2n -> hex = 0x6e322064
ascii = d st -> hex = 0x74732064
ascii = drte -> hex = 0x65747264
ascii = d? -> hex = 0x00003F64
See the session log file for more details!
Anyway i justed started to play around... maybe some tweaks in the configuration are needed
Have fun!
scholbert

Pretty Cool

Thanks for attesting coolness
Made some further tests... though my time is really limited right now.
I found out that the message is send from 2nd loader which is used for Ti's Flash tool.
So this might indicate that there's something wrong with my memory or memory bus.
I re-checked the RAM setup sripts for the Ti tool again but could not find any error. Reduced the timing as well. Still got that message...
It's very strange that the pattern really seems to stick, which is unusual for damaged memory... i will report further findings.
Anyway this is open discussion, feel free to post
Cheers,
scholbert

Nice try. Can you tell us about the RAM, it's built in the mainboard or changable?

We already know that, it's built-in ^^
(some have opened their Archos before ^^)

trungvn1988 said:
Nice try. Can you tell us about the RAM, it's built in the mainboard or changable?
Click to expand...
Click to collapse
http://forum.archosfans.com/viewtopic.php?f=74&t=42806
Soldered on, not changable by anyone with home soldering tools. Very small ball soldering. I gave it an attempt, even got a replacement 1GB RAM module as a test piece... Didn't work out well for me.
I'll definitely be keeping an eye on this topic, seems like some good information might come of it.

.............yippie yeah it's working out!!!!
Thanks for the feedback
First i'll have to quote myself:
It's very strange that the pattern really seems to stick, which is unusual for damaged memory... i will report further findings.
Click to expand...
Click to collapse
Guess what...... it's fixed!!!!!
I really go crazy. See attached log file.
External boot over USB and 2nd loader started up successfully, using the Ti tool.
So RAM is working now!
This definitely saved my day...
What happened exactly?
As i pointed out, the data on memory bus stucked at 0x64, so i assumed there was an issue with DQM/DQS signals on PoP memory.
See some related documents about the function of these signals on RAM chips.
The DQM/DQS where not toggled in the right way because of bad soldering at the PoP memory chip.
See the attached pic for the excact position of these signals (marked in red).
The chip itself is soldered on top of the OMAP3630.
In the end i used a hot-air solder gun and soem soldering flux and fixed the broken connection. In fact i used this "technique" some time ago to fix a "No GSM" issue on HTC Hermes.
Though i'm very excited right know, i'll have to make a break for today, because i have a date
Harfainx said:
I'll definitely be keeping an eye on this topic, seems like some good information might come of it.
Click to expand...
Click to collapse
Yes i'll try my very best
Kind regards,
scholbert

Guy, it's so nice! Keep up the good work!

datasheet collection
Hey,
i was lucky last week. My device is up and running.
Fortunately the eMMC data structure was O.K. In the end my device refused to boot, because of that broken connection to the RAM.
So there'd been no need to fiddle around with eMMC for now.
Maybe i'll do some investigation at a later point.
Feel free to set up your device for peripheral boot and try the Ti Flash tool debugging possibilities.
Right now i decided to re-assemble the device and use it for a while.
I must assume that i know nothing about the internal structure of the firmware. So it would be essential to get some insights
I got some additional information about the eMMC/microSD data lines.
If there's some interest i might post further pics.
To get some background about the chips on the A101 mainboard, i collected some datasheets of the main components.
Grab the zip-file here.
Most of them are easy to find other's are not
Anyway, saves your time i guess.
BTW, is there any tool to unpack gen8 AOS files?
Regards,
scholbert

yes it would be great if we could find one, maybe we could find a way to get inside and change some things

scholbert said:
...
Most of them are easy to find other's are not
Anyway, saves your time i guess.
BTW, is there any tool to unpack gen8 AOS files?
Regards,
scholbert
Click to expand...
Click to collapse
As far as i know we can't extract aos files since they are encrrypted and we don't have they proper KEY - its saved inside the device somewhere
But good luck with going on! Rly sounds interesting who knows what it's good for in future

good news - check out:
http://forum.xda-developers.com/showthread.php?t=1214674
seems we got a way to extract soon

..... uuuh great!!!
FrEcP said:
good news - check out:
http://forum.xda-developers.com/showthread.php?t=1214674
seems we got a way to extract soon
Click to expand...
Click to collapse
Yupp, that's awesome. I just joined that thread.
In the meantime i disassembled my device again, because i want to spent some more time on research.
I found out some more details about the chips and the design in general.
The A101 seems a pretty neat device for extensive hacking, because archos did a good job and made a very clear design.
I started to prepare a pin map by looking at the kernel sources again.
Maybe i'll be able to find some other useful testpoints on the mainboard (e.g. UART2)
As you might know, the touchscreen is connected to USB using OHCI mode.
To attach it to the OMAP ports they also used a chip from Ti.
See this datasheet for more information:
http://focus.ti.com/docs/prod/folders/print/tusb2551a.html
If i'll find some time i'll try to make kind of a floor plan from the mainboard and post some pics as well.
P.S.: If someone knows the manufaturer of the speaker drivers, please tell me! The parts are marked as 8JAM892 and are located near the soldering points for the speaker.
Keep on hackin'
scholbert

What I would like to find out is what component it is that dies when the USB port fails (and it stops sleeping as well). Maybe it's replaceable (if you can do SMD soldering).

pbarrett said:
What I would like to find out is what component it is that dies when the USB port fails (and it stops sleeping as well). Maybe it's replaceable (if you can do SMD soldering).
Click to expand...
Click to collapse
Mmmh... without being affected by this issue it's hard to tell.
If the port dies, there could be many reasons of course.
Maybe the 5V power supply for Vbus is dying on these devices, due to "over-current" issue. I have not identified that part right now.
The signal lines itself usually won't be harmed... apart from injecting ESD pulses right to the connector.
The USB host port is directly connected to data lines of the USB PHY inside TPS65921 (Power Management chip).
OMAP3630 itself uses ULPI mode to connect to this part.
That's all i could say for now.
Regards,
scholbert

FrEcP said:
good news - check out:
http://forum.xda-developers.com/showthread.php?t=1214674
seems we got a way to extract soon
Click to expand...
Click to collapse
If we can't extract those AOS files - how are custom ROM builders such as $auron getting their hands on the upper layer of the firmware? I know I am not expressing myself technically correct, but what I understand is that for instance $auron's UrukDroid is a custom Linux kernel etc. with on top of it the modules, GUI etc of the official Archos packages...

you don't need to extract the aos file to get the filesystem of the archos android. you simply have to root your device or just install angstrom (which comes with SDE) and then you can copy the squashfs file to your computer so you can extract whatever you need. it's not encrypted but signed, you only have to skip the first 256 bytes (if I remember correctly) of the file to get a valid squashfs image.