Anyone know any details about the modem in the Universal? Specifically, AT Command set, how it interfaces with the OS, etc.... I see that it uses a Qualcomm modem that looks to be embedded in some larger Qualcomm chipset. Anyone have any technical details about the modem in this thing? Thanks!
Related
Does anybody have diagnostic and application interface drivers for xda exec (Octek 900)? THose drivers help to get certain parameters out from the phone over USB interface to PC. Basically, I would need to get RF parameters out from the Qualcomm 6250 chipset used for GSM/WCDMA communication in the phone. Those drivers are available for all the QUalcomm chipset based phones, but normally need to get them from the manufacturer (HTC).
Jari
ryyna said:
Those drivers are available for all the QUalcomm chipset based phones, but normally need to get them from the manufacturer (HTC).
Click to expand...
Click to collapse
Where one can get them for other phones ?
some operators seem to get them from manufacturer directly. with some phones, there are some distributors which sell the phone and drivers together for testing companies. for this O2 (dopod 900, JASJAR, etc.) I haven't been able to find any source for the drivers.
Normally HTC only supplies the default parameters and builds to order some RF configurations...
Bye,
Ricardo
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
Hi, all.
Lately I've been trying to build a linux driver to an accelerometer chipset, LIS331DL, embedded to a certain motherboard. System's BIOS has not been updated as to fit current gsensors linux drivers in (communities releases and so). We are positive that the device naturally inputs/outputs info through very specific I/O ports, namely the 0x6C and 0x68 ones. The problem is that I am able to access the device data through those ports in Windows,but not in Linux. Moreover, there's no real datasheet to help us through.
Here I have some few questions:
1) Is there, by any sort, a software kit which could possibly help us into diagnosing the motherboard as to provide more info about the device (LIS331DL accelerometer chip)?
2) Provided that there's already a windows driver that's fully functional and easily gets to send/retrieve data to/from the gsensor, under linux the management of those same I/O ports would end up into same results? In short, is there any difference between Linux and Windows I/O ports access (logical and addressing shifts perhaps)?
Any help would be much appreciated. Thanx in advance.
I managed to successfully get access to the gsensor device. Hope any other won't face the problems I had to, but just in case, I will now provide feedback to my own questions:
1) Is there, by any sort, a software kit which could possibly help us
into diagnosing the motherboard as to provide more info about the
device (LIS331DL accelerometer chip)?
Yes. A very good one called ECTOOL.
It probes the EC-RAM memory, which's quite a good start on taking notice of how bits are behaving and, later on, making decisions on that!
2) Provided that there's already a windows driver that's fully
functional and easily gets to send/retrieve data to/from the gsensor,
under linux, the management of those same I/O would end into same
results? In short, is there any difference between Linux and Windows I/
O ports access (logical and addressing shifts perhaps)?
Yes, same results. No difference. The gsensor got to output the same values (three-axial coordinates) as in windows. Hurray!
On the Galaxy Nexus there runs a SiRFStarIV GSD4t GPS chip, which needs a host processor to run. This host processor must implement the SirfHost software, as stated in the product details of the GSD4t on the CSR website.
Where can I find the files related to this SirfHost software? I am trying to implement some gps features which go beyond the normal positioning applications and for these I need to fully understand how the chip is communicating with the host processor.
Can anybody help me with that?
Hello!
I have an embedded device with an Infineon Aurix CPU, and it has what looks like "normal" 24xx/25xx (SPI?) flash memory. My flash reading clip fits on them perfectly (-: However, the numbers on it indicate that it's some unknown (to me) 27xx version of memory. Since this thing has an infineon chip, I'm kind of assuming the flash memory is some proprietary "pflash" (it was referred to as pflash at one point as well). I've tried looking at what infineon sells and while there's 24xx/25xx/29xx chips, I don't see anything with 27xx.
My question is has anyone seen flash memory chips like this? I think that they are protected against reading/writing/erasing/reflashing but would like to make sure there's not some 'simple' wiring tricks I can use to enable them to act like normal eeprom/flash chips.
Alternatively, anyone seen something that looks like flash/eeprom but is something else with a 27xx XXXX identifier on it?
Thanks in advance if anyone has any ideas