yashsingh1/xdaforums huggingface dataset:
[Touch Diamond2, Pure Android Development] shavenyaknz:
Hi iceman198, thanks for all your help on this. I just downloaded the haret that you posted and it looks like the same one I've been using all along. That being said I tried it and it still freezes at the 'HaRET: Booting Linux ...' screen.

Also my home machine is WinXP and I have transferred Android to it plenty of times and it didn't seem to make any difference so I don't think it's a Windows 7 thing.
[Touch Diamond2, Pure Android Development] elmmis:
me too

my phone can't reading too:D my e is not very good:D
[Touch Diamond2, Pure Android Development] iceman198:
Ok...just for kicks, try an older version of haret!...couldn't hurt, right? =) It's attached.
[Touch Diamond2, Pure Android Development] Spitfire128:
Couldn't hurt, no. =) Here goes..

Alright, I tried and.. No luck. Just the usual soft reset. Too bad.
[Touch Diamond2, Pure Android Development] iceman198:
Ok...go back to the latest version of Haret...

Open up your STARTUP.TXT and where it says:

set mtype 2293

Change it to:

set mtype 1952

That's a different mtype for topaz...well...I think...shouldn't hurt anything....emphasis on "shouldn't"....

Found it here:

http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/arch/arm/tools/mach-types#L1943
[Touch Diamond2, Pure Android Development] Spitfire128:
Alright, thanks, I did. But.. Now it freezes at the "HaRET: Booting Linux ..." screen just as the bar is full: it doesn't soft reset anymore.

There seem to be some other Topaz mtypes there, would it be of any use to try those? EDIT: Wups, nevermind, got the numbers wrong. ^^'
[Touch Diamond2, Pure Android Development] iceman198:
Did you try it maybe a second time as 1952 as the mtype?

You can try others I guess...but there are A LOT!...

So...I'm kind of at a loss...=(...I'm having a little vacation but will be back next week and will continue investigating with you once I'm back.
[Touch Diamond2, Pure Android Development] shavenyaknz:
Just tried that. It's weird, even with the good zImage changing to 1952 seems to make the black screen appear but only about 1/4 of the size. You just get this black panel and it hangs there.
[Touch Diamond2, Pure Android Development] Spitfire128:
Just did, no change. Already tried a few, still just freezes.. Well, have a nice vacation. Thanks a lot for all the effort so far, I'm sure everyone appreciates it a lot.
[Touch Diamond2, Pure Android Development] shavenyaknz:
Yeah have a good vaction iceman198, I sure do appreciate your time and effort on this.
[Touch Diamond2, Pure Android Development] shavenyaknz:
I've been playing with a donut buil and I'm starting to wonder if the reason it seems so slow is just that the touchscreen isn't responding properly. Whenenver I hit the menu button or phone button it responds pretty quick. I've got the calibration line 'msmts_calib=0x395.0x3d5.0x79.0xa0' in my startup.txt but wonder if we need to change this to get it working better ?
[Touch Diamond2, Pure Android Development] iceman198:
When I use the donut build, I don't even have that in...

So...do all the zimage files work with the donut build and just not with the eclair build?
[Touch Diamond2, Pure Android Development] salvatore057:
Hi all,

I have a TOPA100 too and I also have the same problem.

iceman198, I tried the new zimages with the donut build but again it is a soft reboot after Haret finished loading.
[Touch Diamond2, Pure Android Development] Spitfire128:
I also tried the 1.6 package from the main thread's OP, and it gave me the same result.
[Touch Diamond2, Pure Android Development] iceman198:
When i run haret (renaming my STARTUP.TXT to something else) it says that "Found machine Generic MSM7xxxA"....so maybe try mtype=1916?

Trying different mtypes is really all I can think of. Of course, where you only have one zimage that boots, that is probably the true issue. In order to resolve this though, we would have to rope in a developer who has one of your devices for testing...unfortunately, I am not that man as I'm not very familiar with java.

// EDIT // I just looked up and the Topa100 has an MSM7200A so that would be mtype=1321...maybe try that?
[Touch Diamond2, Pure Android Development] Spitfire128:
Well, as I posted in the other thread... If we're going to need a developer with one of the problematic Topa100s, I fear this might get to a standstill..

Anyway, I will try that tomorrow. I really hope it works.

EDIT: Turns out I still had 1.6 on the device. Using mtype 1321 results in HaRET freezing at the loading bar-part, as usual with other mtypes so far. Guess I'll try 1321 and 1916 on Eclair tomorrow just to be sure but I have doubts it'll work.
[Touch Diamond2, Pure Android Development] salvatore057:
Hi Guys,

I found that:

Added build: htc-msm-android timestamp: 20100314_151151 changes: commit 9ffcf0950447934ff982063cd2b12e0f44063290

Author: mweirauch <dev@m-phasis.de> Date: Sun Mar 14 15:07:07 2010 +0100

* topa100: use PCOM_NOTIFY_ARM9_REBOOT like rhod

It's way more convenient when the phone resets than freezes.

What does the "topa100: use PCOM_NOTIFY_ARM9_REBOOT like rhod" mean?

Is there a patch that need to be added to the zimage?

By the way, I am about to go on holiday but I will tru to change the mtype in the startup.txt as suggested.

Cheers
[Touch Diamond2, Pure Android Development] insanemal:
If there was a change in memory type.. and it caused grief for the windows rom cooks, then I would say this is the cause of the issue. What you are looking for is not a new commit, possibly an exclusion of a driver from the build.

This would give you a situation similar to what is being seen. "I'm a loading....... WTF LOL HAX REBOOT". I had the same issue booting a Linux install that had a monolithic kernel on different hardware. So what we are looking for is a change in build scripts.. or Kernel config script to be precise!
[Touch Diamond2, Pure Android Development] scarface5323:
booting normaly with this zimage, but when open, anywhere i tap, nothing happens.., and dont look that freeze because when i press power button it switch from landscape to portrait..:S
[Touch Diamond2, Pure Android Development] Spitfire128:
Try a different Android package with the zImage. Some work better than others. I'd be surprised if any package turned out truly usable though.
[Touch Diamond2, Pure Android Development] scarface5323:
basically i try this zimage with rhoubntu and not with android because there i have problem and not to android..
[Touch Diamond2, Pure Android Development] Spitfire128:
I'm not sure if I fully understand you.. I guess you mean you don't have a problem booting Android using the zImage from the beginning of the thread, but you do otherwise, and that that zImage doesn't work with Rhobuntu? I'm actually not even really sure what a zImage is, but it seems unlikely that you're supposed to use an Android zImage with Ubuntu.. Though I may be wrong.

If you don't have any problems booting Android with other zImages, then you're not having the same problem as us so the same 'solution' wouldn't work either.
[Touch Diamond2, Pure Android Development] scarface5323:
i just try to boot rhobuntu with zimage from firts post, and i think zimages are all the same between android and rhobuntu because to the rhobuntu page the link to zimages are the same that android are..
[Touch Diamond2, Pure Android Development] jupppo:
Not sure whether it is right here or in the wrong thread. But my Android 2.1 boot up and then shows the lock and asks me to enter the pind. But screen is unresponsive and I can't enter anything.

In a different forum I read to deactivate the WM lock. I did, but w/o success.

Is that the same issue (I have a Topaz100)?
[Touch Diamond2, Pure Android Development] Spitfire128:
If Android is booting at all for you with (most) zImages other than those in the first post it's not the same problem.

Anyway, disabling PIN security in Windows Mobile may solve your issue.
[Touch Diamond2, Pure Android Development] salvatore057:
Hi all,

I tried several mtype and still the same problem: soft reset or freeze after loading :(
[Touch Diamond2, Pure Android Development] johcarlos:
hello

new member here.

like the site.

sorry for my english.

i am trying to program android on my htc touch diamond 2 tpas 100 ,but always i get this message

failed,to find rootfs on sd card. you need to unzip a rootfs bin sh ,cant access tty;job control turned off.. .

what is going wrong here.

can someone help me.
[Touch Diamond2, Pure Android Development] salvatore057:
Hi,

I think that either you put rootfs in the wrong location or you did not specify the location in the startup.txt file in the command line.

Where did you put this file? (root or android folder)
[Touch Diamond2, Pure Android Development] ReWind402:
So what are the changes in hardware terms between the old and the new one TOPA100's?
[Touch Diamond2, Pure Android Development] Spitfire128:
No specifics have been posted yet, but:

I've done a bit of research on Google and it seems correct. But that's all I found out really.
[Touch Diamond2, Pure Android Development] ReWind402:
So the only solution is to decompile the kernel and add memory instructions, we need to decompile those kernels that are working on the newest topaz and try to figure out whats causing reboots on boot up.

BTW does anyone knows if any of the XDANDROID devs have a TD2?
[Touch Diamond2, Pure Android Development] Wildfires:
Managed to get my Topaz working using zimage found earlier in this thread, but it just gets to the XDAndroid screen and keeps repeating it.

Perhaps a step in the right direction?
[Touch Diamond2, Pure Android Development] ReWind402:
Do u gave the latest rootfs? Old ones seems to have some problem with an infinite loop of animation :S

P.S.: Dont use the latest rootfs becouse its an Froyo addition, use the one before him.
[Touch Diamond2, Pure Android Development] lobfredd:
I have 2 TOPA100 and now i get everything booting..

a month ago nothing was booting, (only with the zimage in 1st post...)

weird uh?
[Touch Diamond2, Pure Android Development] ReWind402:
Huh, both of them are newest ones? Which build did u used and which zImage?
[Touch Diamond2, Pure Android Development] lobfredd:
Yep, both are the newst ones. I have tried the package from ur stickie thread and the XDAndorid CAB install i found on the Touch HD section of the forum. I tried today also many of the zImage autobuilds u have linked to in ur stickie thread. (all i have tried today have worked.. :)
[Touch Diamond2, Pure Android Development] Spitfire128:
That's very odd.. I've tried booting the package from the sticky, but no luck.. Are you sure you were having the same problem as us? Did you do anything worth noting to your phone in the past two months that could've caused this? Do older zImages that did not work still not work or are they 'fixed' as well?
[Touch Diamond2, Pure Android Development] salvatore057:
Hi guys,

I started to investigate when the kernel stopped working with the mweirauch's advices and I finally got to the point that, so far none of the kernel works (from the linux-msm git). Some boot to linux but reboot after the 2 vibrations, some go a little bit further but freeze, some freeze after haret and other directly reboot after haret.

I finally got to the point to use the work done by mweirauch, i.e. using the 18/12/2009 files from the git and apply the diff mweirauch added in his zip.

I have a now on my hard drive a kernel that works and I will try to apply the different patches that were made in order to make it works better.

Hopefully, even if I am not a developper, i will be able to come up with a more up to date kernel for the TOPA100.

Cheers
[Touch Diamond2, Pure Android Development] mweirauch:
I think this might actually hint at the problem: It could be that HTC soldered one 256MB bank instead of two 128MB banks. Just an assumption.

If that is the case, than this is the culprit, as the two 128MB banks are not physically adressed contiguously. There's actually an "address hole" between those.

Perhaps it's worth a try setting up only one memory bank with 128MB size in the topaz board file,

and adjusting the pmem setup to reflect that contiguous layout.

If that actually get's it to work, one could try to set up the memory layout (bank- and pmem-setup) for the newer topaz. And that should be ideally done dynamic. Dunno on how to identify the different device/memory types, yet though. But I think I've something similar in the Hero kernel.

mrpippy (Brendan Shanks) started commiting the multi bank support after he (and also me) did some research on February 2nd 2010. A day after, with this commit, phhusson enabled second memory bank support for all supported devices. Perhaps it's worth trying some or one commits before that one. Would be really nice to know if that works out.

Michael
[Touch Diamond2, Pure Android Development] mweirauch:
a try...

Please find attached a kernel package with only 128MB enabled and pmem disabled.

Edit: Also added a package with 256MB (contiguous) enabled and pmem disabled.

When booting, there will be NO bootscreen nor anything else. You will only see the last output of haret on the display. After some time one can connect to the device via adb and do some remote info querying like 'adb shell dmesg' or 'adb shell free'.

So if somebody with adb-access could test this kernel on a newer topa100 which is known to not boot at all/reset immedeately?

Remember: THIS IS A TESTING KERNEL ONLY! YOU WILL SEE NOTHING! TEST 128MB-VERSION FIRST!
[Touch Diamond2, Pure Android Development] test222:
i tried both of the kernel,both froze after 2 Vibration,and can't connect via adb
[Touch Diamond2, Pure Android Development] ReWind402:
What about contacting kernel devs to try fix this problem with the memory addressing over irc channel? Link Those more kernel experienced guys here :) feel free to speak with developers about that and other things maybe we can all benefit of your question ;).

Edit: those with adb-access try with adb logcat with one of those unusable kernel so we can see what the log says about that.
[Touch Diamond2, Pure Android Development] mweirauch:
What it boils down to is getting more information out of such a failing device. Will try to post another version later this evening with enabled GPU0 and ramconsole, so one could dump it with haret. (Hopefully.)

Dunno if any of the other devs has yet worded some other assumptions than I explained earlier.
[Touch Diamond2, Pure Android Development] salvatore057:
I don't know if it helps but when I apply this patch:

Topaz has 107MB available RAM, not 89MB

http://gitorious.org/linux-on-qualc...mmit/f6012fa05357fe6afe73808b26a3d53d77a9a457

to my working kernel, it freezes after rebooting to linux (after the two vibrations)
[Touch Diamond2, Pure Android Development] mweirauch:
Ah, nice hint. Thanks for evaluation.
[Touch Diamond2, Pure Android Development] mweirauch:
89MB only

Hiho,

another one with limited setup. Please try. (graphics enabled)

Thx to salvatore057 for the hint.

EDIT: reported to work
[Touch Diamond2, Pure Android Development] salvatore057:
Wow, it boots but my cyanogen is a little bit strange and I cannot unlock it using the touchscreen which is unresponsive.
[Touch Diamond2, Pure Android Development] mweirauch:
Nice! The slowness is expected as it has to work with 89MB only. Which is really less. Have the same "slowness" on my XDANDROID 2.1 with 89MB here.

Ok, now it's time to figure out the correct memory setup. ;)
[Touch Diamond2, Pure Android Development] salvatore057:
I tried with 95 MB and it boots, I will increase it little by little and then try to activate the second memory bank.

105MB is the maximum, it freezes with 106MB.
[Touch Diamond2, Pure Android Development] Spitfire128:
This is all great news/progress! I wish I could contribute somehow, but I don't know all this atb-access and pmem and logcat. If there's any way for me to help I gladly would.

Thanks a lot everyone, for putting so much time and effort into this.
[Touch Diamond2, Pure Android Development] mweirauch:
Nice! Could you do me a favour and try the attached zImage. Isn't much different except that it performs a monodie check and prints it to dmesg.

Grep it via adb shell dmesg. At the very beginning you should see something like this:

[ 0.000000] parse_tag_monodie: mono-die = 0x0

Feel free to paste until it prints out the total memory config. (

[ 0.008728] Memory: 89MB = 89MB total

)
[Touch Diamond2, Pure Android Development] mweirauch:
In the "current" pmem setup, at offset 107MB, 8MB are reserved for GPU1. The remaining "space" (115MB-128MB) is left untouched in the memory setup.

I don't know offhand what resides there, but IIRC "touching" that memory - in this case by allocating some GPU memory into it - the devices halts. Judging from my notes of the days back when we only had one bank supported ("120/115/110 crash 108 seems ok") at least seems to underline that assumption.
[Touch Diamond2, Pure Android Development] salvatore057:
Oups, this starts to be very complicated for me ;)

Do I need a special cable or only the adb package and the normal HTC cable?
[Touch Diamond2, Pure Android Development] mweirauch:
Just a regular usb cable and your topaz attached to it. And yes, "adb" is required, too. If you don't have it, phhusson once posted the SDK 1.6 version here. Dunno if it works standalone, though. Otherwise get and install the android SDK. 'adb shell dmesg' prints you the whole kernel log.

If that doesn't work out, you could try to have a look at it within Android with some market apps. Dunno if AndroidSystemInfo is capable of showing dmesg.
[Touch Diamond2, Pure Android Development] salvatore057:
I installed it from the android website but when I launch the command adb shell dmesg, I have "device not found" :(
[Touch Diamond2, Pure Android Development] oicq55555:
Use this zimage can work with TOPAZ100, but can not to star wifi .anyone has this problem?
[Touch Diamond2, Pure Android Development] Spitfire128:
The zImages in the first post have a lot of problems, as is stated there. There's people working on this right now, when we get a better zImage I'll put it up in the first post.
[Touch Diamond2, Pure Android Development] ReWind402:
Well, some time ago i found somewhere a dev comment about those untouched "space" and how it is configured in the android kernel, i will try to find it but i cant promise anything.

Anyway good job guys with the kernel. We needed a wake up in the Android section :)

What do you guys think about forming an TD2 dev team so we can join the devs at XDAndroid development?
[Touch Diamond2, Pure Android Development] mweirauch:
Have you actually booted into android? adb only works when android is at least starting up. Are you using a linux distribution in vmware or on real hardware?
[Touch Diamond2, Pure Android Development] ReWind402:
Found it!

Here is how is memory managed in linux kernel ( Writen by phhusson ) :

The phone really has 288MB RAM (+ some kB for some external devices), with 256MB in DDR EBI, and 32MB SMI (stacked memory, said to be faster than EBI).

The diamond has 196MB: 64MB in SMI, 128MB in DDR EBI.

But these 288MBs are shared among all the internal devices, like 2D/3D/video acceleration, camera handling, and especially modem stuff.

I don't know how much they account for in windows mobile, but current linux layout is this:

2D: 19MB for diamonds, 32MB for others

adsp(=mostly video): 2MB (we might have to increase it for video decoding.)

camera: 1MB (I don't know if it's enough either)

ram_console: 1MB

GPU (ie 3D): 16MB (8MB in SMI and 8MB in EBI bank 1)

framebuffer: 2MB

modem: 24MB in SMI + 13MB in EBI bank 1

Here is the link to the discussion: http://pjottrr.no-ip.org:81/redmine/issues/show/48
[Touch Diamond2, Pure Android Development] mweirauch:
The question is rather if that device has a mono die or a dual die memory setup. There is space which mustn't be touched, but that doesn't hurt, as there is plenty of memory around when one can use at least that amount of memory that is available for the already working devices. Alas, there is already a good memory setup for all working devices. Only the newer topa100 seem to be different from a hardware or set-up point of view. If you can dig up the info you mean, I am happy to read it :)

Puh. No idea. Dunno what Markinus is up to. He's been relatively quiet commit-wise recently. I do have commit access to linux-msm and am happy when I can apply any fixes we can create for the newer topa100.
[Touch Diamond2, Pure Android Development] salvatore057:
Yes, I have booted to android and then plugged the phone to my computer. I use Ubuntu 9.10 on real hardware.

I think the problem comes from my computer because I tried before plugging the computer and it was looking for a device.
[Touch Diamond2, Pure Android Development] mweirauch:
There it is. The 13MB at the end of bank1 are apparently the baseband-data which is used by the modem to actually work. That memory mustn't be touched.

The memory layout described there is more or less set-up in linux-msm for some time already: here.
[Touch Diamond2, Pure Android Development] mweirauch:
Please plug in the usb-cable *before* you boot into android. Just set the device into ActiveSync mode. Then run haret and after some time, try adb when android starts to boot up.

Somebody wrote it is not necessary to have the phone connected before using haret, never tried myself, though ;)

Just tried plugging in the cable when android starts... Can't establish a connection. So please start haret with the USB cable plugged in.
[Touch Diamond2, Pure Android Development] mweirauch:
I am sorry to say, but unfortunately this is 178 seconds too late ;) The log line I am interessted in is at the very beginning of the dmesg output. The 4th or 5th line IIRC.
[Touch Diamond2, Pure Android Development] shavenyaknz:
Ah, nevermind guess I'll have to try again. That being said though, I tried your zimage in linux-msm-topa100-2010-06-29-89mb-test-monodie.zip and it works pretty well with froyo. It's not quick but it's much more usable than any of the other builds so far, Thanks !
[Touch Diamond2, Pure Android Development] salvatore057:
Hi,

Thank you for your help, it works and the file is attached. I hope it is what you need.
[Touch Diamond2, Pure Android Development] mweirauch:
Yap, thank you!

[ 0.000000] parse_tag_monodie: mono-die = 0x0

Unfortunately not what I hoped for. :( No mono-die detected. So I'd go for experimenting with the memory setup.
[Touch Diamond2, Pure Android Development] tc423:
Thanks a lot,the boot is working.i can see the welcome page now.:D.but unfortunately,the touchscreen is out of service,cannot get the feedback,and showing the screen is not responsive.:(
[Touch Diamond2, Pure Android Development] salvatore057:
Have you tried to remove the ts-calibration file?

I had a similar problem and I had to do the touchscreen calibration.

By the way, which zimage did you use? the last one that was posted by mweirauch ?
[Touch Diamond2, Pure Android Development] tc423:
i uesd 89mb zimage by mweirauch,the screen's check is inside the zimage,i cannot remove it,but may be we can ask mweirauch for removing it..:D
[Touch Diamond2, Pure Android Development] mweirauch:
The screen calibration app is in rootfs. If you have a file called ts-calibration(?) on your SD-card, remove it, if the screen doesn't work at all.

Please be said that Android is very very unresponsive with such low memory configuration. You will have to be patient when touching around.

The situation will hopefully change soon for newer topa100.
[Touch Diamond2, Pure Android Development] test222:
the 89m monodie kernel can boot through,and it's really working,howerver,slow,very slow
[Touch Diamond2, Pure Android Development] salvatore057:
It is strange, it is not that slow on my phone.

A lot of things work like the bluetooth, teh power off, the g-sensor, ... but not the wifi.

mweirauch, like I said earlier I used 105MB and the kernel booted but I haven't tried to use the second bank memory because it start to be very complicated with pmem.c and board_htctopaz.c