Database Users

Any questions for microsoft

Any questions for microsoft
Hi all,
On Monday week - ie 11th July I will be meeting with microsoft and hopefully looking at the HTC Universal in detail. I will take my camcorder along so hopefully they will let me take some footage.
Does anyone have any questions they want asked?
Also I will try to take a "origami size pattern" of the universal as many prople are worried about the size. ie you can print, fold and glue to get an accurate feel of its volume.
Any other suggestions on information that can be gained from this meeting?
Jayman
Edit: I will also try to get a couple of sample photos/video from the cameras

Ask about WM5 for other HTC devices. That would be cool to know what MS says about it.

Do you mean upgrades for existing HTC models (this is a carrier decision not m$) or do you mean new models yet to be announced such as the galaxy/wizard?

Jayman said:
or do you mean new models yet to be announced such as the galaxy/wizard?
Click to expand...
Click to collapse
... which is also a question to ask manufacturers and not Microsoft.

Stateside
I wouldn't expect them to have any information on this either, but it's worth a shot. Ask if they have any information when we might be able to see this device in the US. Even ballpark figures will do. I need something to keep me away from the Samsung i730.
Also, if it is a working device, I'd be interested to know how it performs as a phone (without headset/speakerphone) in both the open and closed screen position. (i.e. are the speaker and microphone positioned to work well in both configurations?). Check out the memory configuration as well, see how much ROM is left for storage.
One more thing...WM5 seems to lend itself to easier one handed usage. I'm not sure it will be possible with the Universal, but I'd be interested in your interpretation.
It sounds like a great opportunity, have fun!
Shawn

1)
Will there be a HotFix system for the WM2005, or is there any plans for it.
2)
Will M$ Relase Rom, Radio etc. upgrades/Fixes directly in the future for WM 2005.
3)
What is M$ doing about the fact that installed programs can make the device general unstable. Are you looking into this problem and plan to solve this issue.
I'm no programmer and don't know why this happends, but i guess it the same story as Windows for desktops in earlier years?

Good luck fella.
Ask them when they are finally going to solve the microphone support issues with the phone application, why the same mic works perfectly well with speakerphone, voice recorder ect but is far too low on phone.
Maybe they could add a volume slider for the Mic in the phone app (and here's another tip, if they do, they current level should be the bottom setting!!)

Take the invisible Rom-Grabber with you and ask for a Blue Angel with WM 5.0...

USB Host
Can you find out if they have any plans to include USB host drivers so that we can use our windows mobile devices with portable hard drives. The form factor of the Universal can only be justified (by me) if I can get rid of my pc on many trips. To do that, I need access to files on my portable hard drive. Would be nice if they supported this functionality.
Ray

USB Host
Can you find out if they have any plans to include USB host drivers so that we can use our windows mobile devices with portable hard drives. The form factor of the Universal can only be justified (by me) if I can get rid of my pc on many trips. To do that, I need access to files on my portable hard drive. Would be nice if they supported this functionality.
Ray

did the meeting happen?
hi friends,
did someone actually meet ms people!
:twisted: :shock: :idea:

it's not software which limit devices from being masters and using external harddisks or the like

It's all gone very quiet, surely the rumours about the Redmond mafia's business dealings can't be true ...... can they?
Maybe we should have just suggested questions like "Is it true Bill Gates gives lots of money to charity?", or maybe "Tell me more about Microsoft's work in the third world". Poor old Jayman!

Rudegar said:
it's not software which limit devices from being masters and using external harddisks or the like
Click to expand...
Click to collapse
Oh, yes it is software: they're called 'drivers', because the programs 'steer' the data to the correct controlling program.
The Universal has a USB port, so it should have a driver on it somewhere. The question would be, is the divice loaded with a driver to allow it to 'master' other devices, or is it just the syncing point?

Maybe he meant it's more likely to be HTC that can answer that question?
Of far more importance to me is does the device have a suitable method of connecting to an LCD projector? IMHO, this is the absolute killer app for a "laptop replacement" & it's pretty much the only thing I miss from the Xda II.

its more likely that ms and htc is the same, if you know what i mean. and its very likely that there is no company called htc in reallity. maybe a post box hanging in taiwan is called htc and a website hosted (???) in taiwan. but noone is working for a company called htc. i can assure you in that point. and even if there is a hand full of people claiming them selfe working for a company called htc - they are not located in taiwan. need more info about that? go to china and find out yourself, best to start your research is at a company called dopod!
cheers, lutz

lutzh said:
its more likely that ms and htc is the same, if you know what i mean. and its very likely that there is no company called htc in reallity. maybe a post box hanging in taiwan is called htc and a website hosted (???) in taiwan. but noone is working for a company called htc. i can assure you in that point. and even if there is a hand full of people claiming them selfe working for a company called htc - they are not located in taiwan. need more info about that? go to china and find out yourself, best to start your research is at a company called dopod!
cheers, lutz
Click to expand...
Click to collapse
Please tell me more about this, lutz. I don't have the means to go to China and research it, but I always like to hear a good conspiracy theory.

Oh, yes it is software: they're called 'drivers', because the programs 'steer' the data to the correct controlling program.
The Universal has a USB port, so it should have a driver on it somewhere. The question would be, is the divice loaded with a driver to allow it to 'master' other devices, or is it just the syncing point?
Click to expand...
Click to collapse
if you found a way to make a usb peripheral a master using software
then contact www.usb.org i'm sure they will be impressed
the universal if it have usb support contain a usb chip which can act as master
much like my gf's old acer pda which also have such a chip
htc would have gotten a better usb interface had they used the usb interface from the ati chip insted of the nativ xcale usb interface

Please tell them
F*******************KING SOLVE BLUETOOTH PROBLEMS, AT LEAST MAKE IT WORKING PROPERLY...........
regards
Gugi
-- sorry for swearing but ......

@gugi_sat: The meeting is over!
It happened on the 11th..

Need some USB HOST driver dev help

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

USB host

Does any know if is possibile to connect a pen USB to HD2?
Sent from my HTC HD2 using XDA App

leo usb host (sponsored by google) gives THIS xda thread from feb last year,
(not very easily, is the actual answer)

i wanna bring this up again. would it be possible to port the usb host kernel patch from the nexus one or desire hd to the hd2 kernel?

+1 bump, i would be interested in this as well. The wiki states current kernel is the problem
http://htc-linux.org/wiki/index.php?title=Leo/Status
Code:
USB
Android Debug (ADB) works
Normal USB Ethernet works with patch from mobile-linux-discuss Mailing List - see Contact
USB Host is broken in current kernel (due to battery driver detection not working). see mailing list Contact
but i'm not sure which branch it refers to, .32 should have no problem with this. Should be portable from the N1, since it's the same SoC. We would also need an app for switching between Host and Slave mode

+1 for this feature, would love to copy the camera HQ snaps and upload to flickr while on the move. ALso keeping a backup pendrive with songs/videos will be wonderful too. The possibilities are actually endless

USB OTG / Host thread bump
I would like to bump the thread.
I recall USB host funcionality was successfully implemented to ubuntu distros kernel...
It was ported to android distros with loosing the USB gadjet funcionality (desire and nexus)
... but now there is a new light...
It is fully working on SGS2! this means no more: "android is not built for this"
are there any kernel devs interested in USB OTG for leo?
Is there anyone familiar how it's done in SGS2 kernel and android build so that it just works?

I thought it was the case that Leo does not supply any power to the USB port = tough to power devices :-(
Sent from my HTC HD2 using XDA App

smeddy said:
I thought it was the case that Leo does not supply any power to the USB port = tough to power devices :-(
Click to expand...
Click to collapse
Available information says it does not.
Possibly there are some microp commands to trigger some power when OTG is supposed to be active...
After all, power could be injected from an external source (this is how it works under linux distros: Ubuntu on Leo, Debian) so i think this would be the smallest problem

Today I saw that DFT has made the USB host working on WM6.5, so it is only a software limitation , and it is in the current kernel.
I've used an USBHost mode onmy DHD (with a patched kernel for USB host). Actually it can''t provide enough power to other devices, but with some power injection cable the Mass Storage works fine.
Also i saw in the EVO forum a guy who ported a DirectLink Display Drivers, so this will give us a TV-Out option.
So is there anyone working for solution?

Leo usb host development
Although I have not much experience in kernel development I will put all my efforts on figuring out a solution on this issue.
I have a question to ported Host mode to your DHD.
I have heard that when host mode is implemented to the kernel, one must sacrifice USB gadget (on this kernel only). Did you try ADB or multimount to connect to pc?
Host mode was successfully implemented into linux distro kernel and I may be wrong but I recall Dan1j3l mentioned somewhere that he was able to port the Sven Killig's host mode to Leo android kernel as well.
Besides, in the 2.6.37 kernel (CM) for Leo developent tree there are all of the files included, but the problem is that the kernel does not boot yet :/

ogonzuhnina said:
Although I have not much experience in kernel development I will put all my efforts on figuring out a solution on this issue.
I have a question to ported Host mode to your DHD.
I have heard that when host mode is implemented to the kernel, one must sacrifice USB gadget (on this kernel only). Did you try ADB or multimount to connect to pc?
Host mode was successfully implemented into linux distro kernel and I may be wrong but I recall Dan1j3l mentioned somewhere that he was able to port the Sven Killig's host mode to Leo android kernel as well.
Besides, in the 2.6.37 kernel (CM) for Leo developent tree there are all of the files included, but the problem is that the kernel does not boot yet :/
Click to expand...
Click to collapse
Since there are many (including myself) who are interested in this, maybe we should open a thread for DEVs (tag it with [DEV]) to see who can help with this. Hope that you will be successful with this.

separate [DEV] thread
sure, why not.
One thing I would suggest though
As i hate endless talks in threads (making them hard to get condenced info on the subject) maybe it would make sense to have a pair of threads: one with babbling, second with pure technical info and conclusions.
in case of my progress I am at the stage of reading, pulling trees, setting up environments, reading, reading, reading...
since there is a number of trees with host included I am planning to setup some sort of code visualisation tools to look for similarities and system solutions - will try to implement it further into our Leo kernel
... dont know where it will lead me, but with a little luck...

Just a little update (for those interested)
I managed to succesfully compile and boot a kernel with host patch roughly integrated.
I did not test if the host features worked or not, but at least the process is somehow working, and the source code is not totally messed up.
The symptoms observed within android are USB connection not recognized and no charging (effect of usb gadget functions being cut off; battery/charging driver dependent on usb connection state).
It is obvious that the way is still long, but at least there is some minor progress
I am not going to give up...yet
Whish me luck ;-)
(It's time to setup some gear and read lots more...)
Sent from my HD2 using XDA App

Thanks for your efforts I am definitely following this closely. Having USB Host would up the usability of this device hundred folds!!!!!
All the best!!!!!!!
ogonzuhnina said:
Just a little update (for those interested)
I managed to succesfully compile and boot a kernel with host patch roughly integrated.
I did not test if the host features worked or not, but at least the process is somehow working, and the source code is not totally messed up.
The symptoms observed within android are USB connection not recognized and no charging (effect of usb gadget functions being cut off; battery/charging driver dependent on usb connection state).
It is obvious that the way is still long, but at least there is some minor progress
I am not going to give up...yet
Whish me luck ;-)
(It's time to setup some gear and read lots more...)
Sent from my HD2 using XDA App
Click to expand...
Click to collapse

no major updates yet :/
for anyone following...
Sorry for not giving any major update.
I did setup all required hardware, tested, but (as suspected) it didn't work yet.
I had to suspend host related activities due to uni stuff.
I expect to close my remaining issues within a week and get back to getting this bastard to work
cheers

ogonzuhnina said:
for anyone following...
Sorry for not giving any major update.
I did setup all required hardware, tested, but (as suspected) it didn't work yet.
I had to suspend host related activities due to uni stuff.
I expect to close my remaining issues within a week and get back to getting this bastard to work
cheers
Click to expand...
Click to collapse
Well, you have one person here faithfully following the progress All the best!

ogonzuhnina said:
for anyone following...
Sorry for not giving any major update.
I did setup all required hardware, tested, but (as suspected) it didn't work yet.
I had to suspend host related activities due to uni stuff.
I expect to close my remaining issues within a week and get back to getting this bastard to work
cheers
Click to expand...
Click to collapse
Hey, how are things coming along? I, for one, am very interested to see the results of your experimentation

why wont devs help u?
erlern said:
Hey, how are things coming along? I, for one, am very interested to see the results of your experimentation
Click to expand...
Click to collapse
+1 here too but i cant understand y devs are helping him with getting usb working especially with so many brilliant devs on here!!
---------- Post added at 07:36 PM ---------- Previous post was at 07:31 PM ----------
maddoc1007 said:
+1 here too but i cant understand y devs are not helping him with getting usb working especially with so many brilliant devs on here!![/really meant y devs are not elping him me bad
Click to expand...
Click to collapse

Hi guys,
Thanks for the support.
Unfortunately I had no time to move anywhere forwards due to tough times at work :/
Comming week is (hopefuly) the last one, as next weekend I am planning to be a master in engineering
To explain the other devs:
the host capabilities of our android device seams a minor benefit, esspecially in comparison to 2.6.35 or .37 ongoing developments.
Let them do these serious stuff and left these /fairly/ simple ports to greenhorns
cheers

ogonzuhnina said:
Hi guys,
Thanks for the support.
Unfortunately I had no time to move anywhere forwards due to tough times at work :/
Comming week is (hopefuly) the last one, as next weekend I am planning to be a master in engineering
To explain the other devs:
the host capabilities of our android device seams a minor benefit, esspecially in comparison to 2.6.35 or .37 ongoing developments.
Let them do these serious stuff and left these /fairly/ simple ports to greenhorns
cheers
Click to expand...
Click to collapse
Thanks for updating us Take your time then... you are starting your Masters or you are graduating?
Btw, I believe that the devs are not 'helping' because they do not know about this thread in the Q&A... would be nice if you can start a thread with a [DEV] tag. That would really get their attention. Just my 2 cents. I could gladly come up with one if you don't have the time.
Thanks.

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.

[SGH-T589] Finding/reading the UART

I've hit a wall in my quest to improve the Samsung Gravity Smart (SGH-T589). The kernel source that Samsung released for it doesn't quite work right (no wifi, broken touchscreen drivers). I'm trying to do something about it, but my test kernels hang before ADB is able to detect and connect to the phone.
The phone is powered by the Qualcomm MSM 7227 (S1 Snapdragon @800Mhz), which I understand is supposed to have a debug UART. How do I access it?

Reading the Google Nexus i9250 thread, I took a closer look at the system board. I've highlighted what I suspect is the JTAG header (see attachment).
However, I lack both the tools and expertise to determine if that is the header, and what the pinout is (most jtag pinouts I see pictures of online are in 2-column layout).
But, I might not need that. If I understand the discussion in the i9250 thread correctly, what I need is a combination of this miniUSB breakout kit, a 619Kohm resistor, and the FTDI Friend to use to connect the UART to my PC. I'm not quite sure where I go from there, but I expect that Windows will detect the serial port and give me something to connect to via SecureCRT or the like.
Is this correct? I'd kinda like to know before I spend any money on parts
Alternately, if anyone wants to take a crack at wiring up the JTAG port, I have a spare (broken) phone I can ship out. Screen doesn't work, but it still boots which will make it perfect for testing with!

Now, if you had bothered to SEARCH you'd have found THIS post in this thread with this picture!

I actually did come across that thread, however that particular post would not have come up in a search and you'll forgive me for missing a post in a 25-page thread However, I appreciate your help nonetheless.
Next question: I have 2 conflicting schematics for wiring an LPT JTAG cable. One shows TDO wired to pin 13, the other has it wired to pin 11. Which is correct? Or should I just try it both ways?

Try both. Shouldn't happen anything bad until you connect it to 12V or so.

I'm banging my head against a wall here, trying to figure things out but not finding clear instructions.
Is it true that, in order to perform JTAG, I need to use some kind of adapter (i.e. RiffBox), or can I connect it directly to the LPT port of my PC? If I can use my PC, what software do I use to read the debug output? I'm less concerned with recovering from hard brick than I am with getting the early debug output.
I'm thinking a hacked USB approach might be simpler and less expensive. My problem is lack of tools. If anyone else has made such a cable, could I buy it off you for a reasonable price?

Hello, i have a semi bricked Samsung Galaxy S5770 Mini/Pop/Next. It is a Qualcomm MSM7227 board. I have tryied the usb UART approach, but the only thing i can get from it is AST-POWERON, and it repeats (i think it bootloops)
I am trying to find UART on board, there are some little pads around the CPU.
Sent from my GT-I9003 using XDA

Ah my TDO is wired to pin 11. You don't need riffbox if you make a LPT JTAG adapter such as the Wiggler (low voltage variant 3.3V).
There are many softwares that can handle the wiggler, such as H-JTAG, openocd and urjtag.
I used "H-JTAG" and "NoICE for ARM" on windows. It's easy to setup H-JTAG for the wiggler and you don't have to do anything from the command line.
The msm7227 platform is multi-cpu (modem cpu, applications cpu).
With the JTAG port you saw, you can access the modem cpu, which is a ARM926ej-s.
Sent from my GT-I9003 using XDA

tanks for you

Another way, without looking for UART is just comparing what you've changed in kernel, revert it all and apply changes one by one until it stops booting again. You might also find/create some proper thread for that and ask for help. With original repo pulled from opensource.samsung and your changes applied on it commit by commit.

Rebellos said:
Another way, without looking for UART is just comparing what you've changed in kernel, revert it all and apply changes one by one until it stops booting again. You might also find/create some proper thread for that and ask for help. With original repo pulled from opensource.samsung and your changes applied on it commit by commit.
Click to expand...
Click to collapse
The issue here is that I'm trying to backport the MXT224 driver because the driver that's in the Samsung release is butchered beyond repair--the orientation is wrong, the resolution is wrong, the alignment is wrong.
My backported driver either fails to recognize the hardware (which is odd, because the init code uses the exact same kernel calls as the FUBAR driver for the I2C transfers), or locks up the boot process too early to get any useful debug output.
Anyway, I have the parts I need on order, all I need is for the orders to show up and a decent soldering iron and I should be in business.

Ah! The MXT224. I know this one pretty well, aswell as messup that Samsung does, configuring it in hundreds of different ways, with usually same result.
I think you don't need to port anything there. There's parameter table passed to MXT224 during init, that's probably only one thing you need to setup. You might want to reverse driver from some stock kernel, or adjust it experimentally, or simply request Samsung for proper parameter table.
There are many helping examples in various kernel arounds, sometimes it's called MXT224, and sometimes it's QT602240. This is in fact 100% same thing.
I'm not sure if any datasheet is publicily available. Though setup structures explaination should be enough, there it is:
https://bitbucket.org/gokhanmoral/s.../drivers/input/touchscreen/qt602240.h#cl-4848
For example flipping it would be changing "orient" byte in T9 structure. Probably all othere parameters you need to change are also in T9.

Thanks for the link. I managed to figure out the correct "orient" value by trial-and-error, but the screen alignment is screwed up. On a stock kernel, the top-left is 0,0. On a compiled kernel, top-left doesn't even register properly (none of the edges do). I've tried a few experimental things but nothing helped so far. I'll check out that link when I get home and hopefully find something useful.

You might also want to look into mach_aries.c and mach_herring.c files from I9000 and I9020 kernel sources. These shows pretty good how very similiar results can be done in pretty different set of T9 parameters.

I appreciate your input. I'm experimenting with different T9 values. I found a partial datasheet that shed a little light into some of the parameters.
I've managed to strip out the "piggy" (uncompressed vmlinux) from the stock kernel. Is there anything I can do with that to somehow find out what T9 parameters are used by the actual stock kernel (as opposed to what Samsung released)? I did some searching for kernel disassembly but didn't find anything that looked promising.

Can you upload it somewhere? I'd take a look into it.

Sure thing. I'll upload it tonight when I get home. Thanks!

Here it is, gzipped:
http://min.us/mrUKEtr7W

Thanks, one more request - could you also upload .map file generated during your kernel compilation? I don't remember what was the full name of it, AFAIR it's ~70meg textfile in kernel source root or arch/arm/bin dir. Not sure though.
Also, are sources for this kernel available on github somewhere? Downloading tarball but this will take few hours more. :\
Ty in advance.

Rebellos said:
Thanks, one more request - could you also upload .map file generated during your kernel compilation? I don't remember what was the full name of it, AFAIR it's ~70meg textfile in kernel source root or arch/arm/bin dir. Not sure though.
Also, are sources for this kernel available on github somewhere? Downloading tarball but this will take few hours more. :\
Ty in advance.
Click to expand...
Click to collapse
It's not on github at the moment. I'm just working from the kernel sources posted on opensource.samsung.com for the SGH-T589. I'll start an account tonight when I get home and upload what I have. I'll get the map file you're after uploaded too.