helmi_c has been kind enough to create a kitchen for the HTC Apache for the Apache commnity to play with. We have a working 3.3 that helmi gave to us and we are playing around with the helmi's BA 3.5 kitchen (OS and LOC) files trying to get 3.5 working on the Apache. ImaCokeMan believes that the usb support is the last hurdle.
I do not know enough about the other HTC devices to know which ones might use the same usb chipset (maybe all the more recent ones do?) or how to isolate the 3.5 usb drivers.
Any help or ideas would be appreciated.
Related
Does anyone know when is the update coming out to enable BT 2.0 on wizard or if a hack is available to achieve the same.
does the wizard have bluetooth 2.0 compatible hardware???? if so, we need it cause transfer rate is too slow!!!
Any ideas?
Almost all the sites I've visited so far say that Wizard has BT 2.0 hardware but currently software supports only 1.2 and 2.0 capability is to be provided in a future ROM update...
http://www.pocketnow.com/index.php?a=portal_detail&t=reviews&id=710
Take alook at this it say that after rom update it would be 2.0
I have a problem that I hope some of the code gurus here can help me with. I have an HTC PDA that was codenamed Colorado. The Colorado is actually the Dell Axim X50 series. I have a thread on Aximsite http://www.aximsite.com/boards/showthread.php?t=140071 where I am trying to add a USB host hardware interface to the PDA. I have done quite a bit of hardware reverse engineering of the X50v device (I'm a old-time hardware hacker) and have been able to bring out the PXA270 USB host port1 interface to the outside world via two unused pins on the sync connector.
I originally noticed that the X50v A02 ROM had the OHCI driver included, so I rolled back to that release on my test PDA and have been attempting to get the interface operational. In my quest, I have determined that I need the usbd.dll driver as well as any client device drivers for HID, mass storage, etc.
I've used a number of the great utilities I've found on this site (thank you very much) to grab a copy of the Axim ROM and pull it apart. I consider myself great at working on hardware but my software skills have become rusty over the years (hey - I started by building this system a 'few' years ago: http://www.sol20.org/ )
What do I need?
I would appreciate getting some guidance on how to dissassemble the ohci.dll module so I can see if in fact, it was designed for the X50 or if it was left in by accident by HTC as the later ROM updates for the X50 series had the ohci.dll module replcaed with one named peripheral.dll which was about 1/5th the size.
Also, I'm wondering if either the ohci or usbd drivers require the irq and/or the membase of the PXA270 USB host port1 interface and if so, how do I determine those.
My original idea was to use a simple 2 port hub to bring out the interface. Unfortunately, I recently discovered that a hub requires a hub client driver. Because of that, I will settle on getting a USB flash memory key to interface directly as the drivers are already available. One of the problems I have is interfacing the 3v USB host lines on the PDA to the 5v data signals that may be present on the client device. The PXA270 USB host lines are already terminated on the PCB with 15K resistors. All that is needed is a transient protection chip and/or port driver chip.
I have installed the free Microsoft WinCE dev environments which I thought contained the source for the generic ohci driver, but I can't find it anywhere so I guessing it's not included in the free dev s/w.
Although this is only my 2nd post here, I do hope to be able to contribute technical information going forward. What I'm doing on the Aximsite is quite advanced as far as hardware hacking goes and I hope to be able to simplify it so a few others can 'play'.
Thanks in advance for any help and I wish everyone here a great New Year!
Wow. Well this is a bit over my head, but does sound great.
I will try pointing you toward a couple of useful tools:
1st is IDA probably the most powerful disassembler for ARM code. The free evaluation works fine, but won't save and closes about every 30 min. Still should do the trick if you just want to look at the code.
2nd to get sample driver code, you need Platform Builder. Not sure if that is what you downloaded, but try the provided link. Evaluation version contains all the source code MS is willing to give, it just has some limitations on ROM compilation (which you should not care about).
The only problem is, it's a real b*** to install. Takes hours even if you have a goo internet connection.
Hope this helps.
Thanks for the quick reply.
Do you know if there is anyone who knows a little on how the low level device drivers actually interact with the hardware ports?
Also, I assume that with just the ohci and usbd drivers, if the port is actually activated by pulling one of the data lines high, I should get the popup box asking for the name of the device driver. correct?
how to determine I/O base offset?
In trying to reverse engineer the ohci driver for a couple for the HTC units, I need to figure out where the I/O register base starts.
Are there any memory dump utils, like dumprom, that would indicate that?
I've installed platform builder and want to try compiling the standard ohci driver, but I need to know how to determine the start of the I/O registers on a given WM2003SE platform.
Any assistance would be greatly appreciated.
thanks
Hey all,
I've just got hold of a HTC Alpine and was looking to get either WM5 or WM6 working on it. (Don't stop reading this isn't a "is there a rom update available? question").
I've noticed that people have sucessfully developed new osroms for others like the Blue Angel (I used to have one , but obviously nobody has for the Alpine, so I thought I'd try to knock one up myself.
However, I've fallen quite out of my depth. Can anybody provide some bullets about how the Blue Angel osroms were produced, in fact any guidance or "don't even bother" flames are appreciated.
So far I have done this:
1) I've run up my own extrom and upgraded the radio so I now have a feel for flashing it and such.
2) I've got the old osrom and tried to extract it (hoping for salvagable drivers from wince 4 that might port across) - unfortunatly I can't figure out how to pull the thing apart. I've seen some perl scripts floating about, but if anybody could point me to the latest version of the right one it would be appreciated.
3) I've got my hands on a copy of the platfrom builder for wince 5 (I know both WM5/WM6 are based upon it) - however have now discovered that windows mobile itself isn't included :-(.
I'm probably not even going through the right motions, or it might be plain impossible, but at least I'll know.
Thanks in advance,
Josh
As far as I know they got the rom from another phone with a newer os, transfered the drivers and removed some things that would not work with the ba.
I'm pretty sure that isn't this simple but is something like this
Unfortunately this is a "don't even bother" post.
ROMs are cooked for devices that either:
a) Have a brother with almost identical hardware that got a newer OS. (like prophet / wizard duo)
b) Have a test version of newer OS leaked but never released.
Because driver architecture is different between WM 2003 and WM 5 even if you could take the ROM apart you could not just take the WM 2003 drivers and use them with WM 5 OS .
As for Platform Builder - nothing there. To build a ROM for a device you need its BSP (Board Support Package) which is what lets you compile a ROM for specific hardware. As far as I know one of those has never ever been leaked from HTC (or other OEM).
Plus, to get your hands on a Windows Mobile version of PB (yes it is actually a different version) you need to be an OEM or a "MS partner" company.
Right, well if the driver architecture has changed then I'm pretty much buggered for plan a.
The blue angel is pretty similar driver wise, isn't it? As far as I can tell the only differences are the camera and the lack of a keyboard (obviously ram/proc too). But I suppose the ASICs/CPLDs are nothing like each other. So that plan's probably out of the window too.
It's not looking too hopeful at the moment....
Josh
jleahy said:
Right, well if the driver architecture has changed then I'm pretty much buggered for plan a.
Click to expand...
Click to collapse
The drivers are completely different between the two devices. While you probably would be able to extract a number of drivers from the Alpine WM2003 ROM, and while (with luck) they could/should work in the (ported) WM5 OS ROM, there is another MAJOR hurdle which would need to be overcome ...
jleahy said:
The blue angel is pretty similar driver wise, isn't it? As far as I can tell the only differences are the camera and the lack of a keyboard (obviously ram/proc too). But I suppose the ASICs/CPLDs are nothing like each other. So that plan's probably out of the window too.
Click to expand...
Click to collapse
That's exactly the issue - the Alpine, while being VERY similar to the Blue Angel is different enough in the hardware to not be able to use the same code. In every ROM there is a Boot portion which is device specific (XIP section), which initializes the hardware before the OS starts - very similar to the BIOS in your PC. There has been (very) limited success in getting the Alpine to boot using a Blue Angel based ROM, but it HAS been done.
The largest problem is that there is no support for initializing the Radio ROM - i.e. phone support. So, while we MIGHT be able to make a ROM which can boot on the Alpine, we would only be able to make one which (MOSTLY) worked, and would NOT have any Phone/Radio/BT/etc. capabilities. Basically, your Alpine would become a glorified PDA ... only.
jleahy said:
It's not looking too hopeful at the moment....
Click to expand...
Click to collapse
Nope ... as said before - without the BSP, and hardware initialization ... it'd be like trying to boot your Mac using a PC BIOS. (Although, scarily - that's getting closer and closer to be the truth ... !!!)
Anyone got anywhere running Any sort of Quake on Athena?
I have ....lol....literally a million editions that have been made for XX devices over the years....the best one being I think Dutty Quake.
I used to play against PC's on my old Magician running wm 2003 through Wifi. Almost competitivly.
I have had limited success on Athena, nothing great.
I would love to be in a position to do some work on a port to configure it correctly, there is a great *white screen fix* version for Universals which is VGA and Keyboard ready but it wont run on Athena just bombs. This used to rock on my MDA PRO
I hope someone has already got a perfect version.
LOL, I have probably asked before.
With Michys new ROM running SO F'ing fast - compare it to original windows mobile 5!! My god!!- and with mouse and keyboard through USB host.
I think this would be a good platform for the soft.
How nice it would be if we could get GL quake running on the Chipset *sighs*
I have a great version of GL quake on my N95 8GB, just cant control the fecker properly.
Looks nice when plugged into TV though
Any info would be more than welcome.
Many thanks all, and blessings to MiChY
So, some exciting new for those of us who like low-level stuff,
I figured out how to get USB-RNDIS KITL working with, at least the HTC Titan. It should work with at least the Kaiser, not so sure about Diamond and TP yet.
http://www.nuerom.com/BlogEngine/post/2009/03/05/CE-KITL-instructions.aspx
Instructions are mainly intended for experienced people, so don't bother if you can't follow it, as you wont be able to activesync anymore unless you disable the patch. So uh, if you're still under the impression that you have to be in WM to flash a ROM , definitely don't do it =).
can't wait to play with this, I'll try my TP..