yashsingh1/xdaforums huggingface dataset:
[Touch HD Android Development] xdmcdmc:
Hi ACL,

I have reached that point only compiling rhod sources and generating nbh and module file. No changes to tinboot except adding settings for blackstone. I will make public tinboot.s file and scripts to generate xip and nbh.

The good news is that I have also tried with linux-msm sources and I had the great surprise to see verbose mode displayed on screen, but the kernel wasn't able to go that far as rhod kernel (actually only was loaded and that's it). So I look at differences and just updated the video drivers and blackstone panel.c from linux-msm to rhod kernel. With those changes now I have verbose displayed on screen. I think will be a good idea to bring rhod kernel sources up to date of course keeping the changes made for rhodium (that also make blackstone go so far).
[Touch HD Android Development] Ghostface1979:
This forum makes me happy :)

Can't wait till u guys finally make a good and stable rom 4 my touch hd...

Then I can lose that sh***y WinMo6.5.. tried several roms by haret but didn't work.

If U need help by testing etc.. I'm available ! !
[Touch HD Android Development] xdmcdmc:
Blackstone nandboot with panel fixed

Hi guys, here you have the latest nbh and module files for test.

Let me know how is doing for you.

Also the latest log file for developers.

Regards

@Ghostface1979 If you can test with this files will be great. Thanks
[Touch HD Android Development] [ACL]:
Ok, if there were no changes to the kernel then this weekend i can make the changes needed. I'll let you know when i get it done.
[Touch HD Android Development] xdmcdmc:
@ACL Thanks
[Touch HD Android Development] Srage87:
Awesome, finally some activity on Blackstone's side of android development! Can't wait to have a stable release working!
[Touch HD Android Development] Thegn:
That is excellent news! :) Looking forward to more development for the Blackstone!
[Touch HD Android Development] am20033:
ok here is my dmesg log file
[Touch HD Android Development] Stickman89:
Ok guys I have cloned ACL's repository 'linux-msm-rhod-nand', atm that's all it is so nothing has been committed yet.

Got my children at the moment so finding time very scarse, they go back to their mother tomorrow so should have time then.

Here is the link:

http://gitorious.org/~stickman89/linux-on-qualcomm-s-msm/linux-msm-blac-nand

I will commit my build scripts shortly...

Best Regards,

ST1Cl<^^aN
[Touch HD Android Development] xdmcdmc:
@am20033 Thank you for testing the kernel. I see the same progress like on my Blackstone. The kernel will need some changes to get further.

Regards
[Touch HD Android Development] mitikos:
i have the

[ 20.296905] mdp irq already on 4 4

[ 20.296936] mdp_dma: busy

i have the problem also booting this:

http://www.neopeek.com/viewtopic.php?f=14&t=6209

Then it boots

do u know what is it ?
[Touch HD Android Development] g3rm0:
Don't worry about it. It's just a debug spam. It should be commented out in future commits.
[Touch HD Android Development] xdmcdmc:
Hi, here are my latest modified scripts used to build Blackstone nbh.

There are both versions of scripts:

1. in the root of zip file "makeall.zip" is the script that builds the zImage and modules and also creates the nbh file in one package.

2. in tinboot-linux-msm folder if you have already built the zImage and modules, just use the makexip.sh and after that makenbh.sh to create only the nbh.

Also good news about camera for blackstone, already test the latest files from http://xdaforums.com/showthread.php?t=883966 and camera works even if still camera app crashes.

If you want to help, please visit that thread and try to test and report as much as possible.

Thanks,

xdmcdmc
[Touch HD Android Development] :..MeSho..::
so is it work nand now ? or just trying ?
[Touch HD Android Development] Eodun:
It's WIP, just developing. Don't try this at home (unless you know what you're doing)
[Touch HD Android Development] xdmcdmc:
Exactly, those files are for developers to play with. Nand is not yet functional, still changes have to be made to kernel.
[Touch HD Android Development] Kapie:
wow, working camera! it doesn't in the xdandroid which is only usefull to **** around in android :D
[Touch HD Android Development] Eodun:
Ehm, I'm not sure I've understood you. The build with the camera working is

XDAndroid. It's a kernel not commited in the main development one, but fully functional.

I've been using XDAndroid 2.2.1 FRX03 and 04 for 5 days and still haven't launched WM but for updating and helping debug.
[Touch HD Android Development] [ACL]:
Commited some changes on my git. Most changes were on the boardfile to get usb working. I'm afraid some panel changes are still needed but give this a try. See how far we get.

If this boots, then the raphael will most likely boot as well. Since yall have your own clone now, i guess i wont make any more changes on my end.
[Touch HD Android Development] xdmcdmc:
Hi ACL,

Thanks for the update. As soon as I can I will give it a try.

Don't know why Sickman has cloned your git. I believe the idea was to have a source for all devices, but anyway I will work with your sources and if needed I will send you the changes for blackstone.

AlsoI think we shall modify the scripts to work for multiple devices.

What do you think?

Thanks
[Touch HD Android Development] [ACL]:
Since we arent passing and device specific parameters on the cmdline i dont see why we cant use the same nbh. This is usually the bottle neck since you cant modify the cmdline for values needed by the kernel. On the Rhod, we append values to the cmdline for the rootfs to do all the dirty work like keyboard language and such. I'm not sure what params the blackstone itself needs to pass down to the kernel or rootfs. Let me know what you think.

Its a free country .. lol everyone can clone anything. But its all on you guys. If you guys want to dev your own kernel, by all means you are free to use what i have. I'm just afraid the rest of the device (raph, topaz, diam) will come bug me to help too ..lol. But im sure if we have some talented guys i can patch the kernel for all the devices assuming the patches given to me arent horrible.
[Touch HD Android Development] forrest05:
Hey guys,

i hope u all will get a running nand - rom for the touch hd!

if u need some support f.e. testing/reporting/financial give a call! i think the whole touch hd/blackstone community is going to support this!

What are the problems in developing right now? whats the status?
[Touch HD Android Development] xdmcdmc:
Hi forrest05,

For now, I have to get latest version of kernel from ACL, build nbh and test with new XAndroid release FRX04.

Currently we are able to nand boot, verbose is visible on screen but just before the android wants to load the animation, the boot process stops. Need to debug that part but only after I get the latest updates and run a few more tests with new xAndroid release. For now it's not clear for me what stops android booting as log file is not very helpfull.

Regards
[Touch HD Android Development] xdmcdmc:
Hi ACL, you are right, basically we can use same scripts to generate nbh but only with small modifications (model type for script and some commands for tinboot file). For now I think we don't need other commands for blackstone except those put in tinboot file.

So for tinboot this are the new lines that have to be appended:

.ifdef blac100

.asciz "gsensor_axis=-2,-1,3 msmvkeyb_toggle=off"

.endif

As for the script file for blackstone we need to use:

# compile tinboot XIP

echo "Start compiling tinboot/xip for $1....."

$TOOLCHAIN_PATH-as tinboot/tinboot2.S -o tinboot.o --defsym $1=1 --defsym MTYPE=2030 --defsym hw3d=1

$TOOLCHAIN_PATH-objcopy tinboot.o -O binary tinbootxip

mv tinbootxip xip/$1

and

wine tools/yang.exe -F ruu_signed.NBH -f OS-new.nb -t 0x400 -s 64 -d BLAC10000 -c 11111111 -v Tinboot -l WWE >> $DIRECTORY/tools/log

I had in mind something like:

if [ $1 == "BLAC100" ]

...

fi

if[ $1 == "RHODxxx" ]

...

fi

and so on for each device added, the same like for tinboot file.

That way we could have one script for all devices and just execute the script with model type.

Also I'm not up to date with rhodium status. Are you able to fully nand-boot? Or you have reached the same point as we have with our blackstone using your sources?

I will try the newest sources as soon as I get home (about 8 hours).

Thanks
[Touch HD Android Development] g3rm0:
Hi, xdmcdmc.

Could you post your changes to kernel to enable verbose log? I've just tried [ACL]'s branch with new patches but it doesn't show console. I'm just not sure what I'm doing wrong.
[Touch HD Android Development] [ACL]:
So once you take my changes and build off it we will see how far you get into the boot. If you are successful, then i can see if we can add you to my auto-build. There i can make an NHB just for blackstone since it looks like diff params need to be passed down.

Someone was able to fully nand boot i believe. I havent been doing much work on it lately due to the .35 kernel migration. But Wozzer before he left had done some good research about it and i think got close. But im not sure what kernel changes needed to be done to get it to work. I guess if someone knows how to do the partitioning portion we might as well venture and try ..lol
[Touch HD Android Development] xdmcdmc:
Hi ACL,

I have build your latest sources and for now it's a no go. Exactly, Android boots to the same point as old sources but screen doesn't work. Also I have tried to replace only the panel and still no go.

I will have to run more tests and find where is the problem (weekend will be a very good candidate for this as I'm short on time this days).

Thank you very much for your help and I will keep you up to date with any progress I'm able to do.

Regards
[Touch HD Android Development] xdmcdmc:
Hi, for now with latest changes I couldn't boot myself with verbose visible.

If you want to debug further just let me know and I can post the old sources + my modifications and use that as a start point to integrate new updates (the same I will do when I have time).

Regards
[Touch HD Android Development] g3rm0:
I would really like to see your changes. I can revert [acl] latest commits locally, reproduce your results and investigate which one broke our panel. Than we can see what to do next.

@[acl]: I wasn't able to ADB with your commits but... Win7 discovered my phone as HTC XDA Device (it works great with haret kernel). Maybe I should try one more time with ubuntu but I'm not sure if it changes anything.
[Touch HD Android Development] Stickman89:
Hmmm I have already reviewed and made the relevant changes to board-htcblackstone-panel.c and msm_fb.h and unless I am missing something vital framebuffer is still borked for me.

Mind sharing your patch with everyone else xdmcdmc?

Best Regards,

ST1Cl<^^aN
[Touch HD Android Development] xdmcdmc:
Hi Stickman,

No problem, as soon as I get home from work, I will upload everything I have here.

Regards
[Touch HD Android Development] [ACL]:
I need to check to see if my branch even has the epson driver. After all when we moved to .35 i wiped everything out. So i need to visit all of this or just move blackstone to mddi_simple to have the console up.

If ADB doesnt work as well, it may be crapping out somewhere in between. I'll make some more changes.
[Touch HD Android Development] xdmcdmc:
Hi ACL, for Blackstone, epson driver is indeed needed.
[Touch HD Android Development] xdmcdmc:
@Stickman89

Hi, the link to modified sources that have verbose mode visible.

http://www.megaupload.com/?d=LW9DH6NW

Please compare those sources with original sources from rhodium nand.

I remember I have overwrited drivers\video\msm and arch\arm\mach-msm\board-htcblackstone-panel.c.

Regards
[Touch HD Android Development] [ACL]:
yeah i totally forgot that i don't have that file.

Either that or the panel.c file needs to be modified to use the mddi_simple since that is the new default for .35

You can use this as a template since the kov used to use the epson but was moved to simple for .35

http://gitorious.org/~ast/linux-on-....35/arch/arm/mach-msm/board-htckovsky-panel.c
[Touch HD Android Development] Spige:
Nice work

Keep it up boys!!!Nice work!! Maybe soon we have full working android!!
[Touch HD Android Development] [ACL]:
pushed some more changes.. let me know fellas.
[Touch HD Android Development] mybetrayal:
ping

All sounds a bit beyond my experience, but I like the goal! :D

I'll keep checking back for testing when required... I need to use the phone day to day, so I'd best wait a little while yet!
[Touch HD Android Development] [ACL]:
**** my push failed.. i'll repush tonight.. :-\
[Touch HD Android Development] g3rm0:
I've made a quick look at xdmcdmc's sources and compared them against linux-msm-rhod-nand w/o two latest patches (those probably broke our panel again). Changes are massive, but most of it is just rhod related so we can safely assume those parts can be ignored. For those of you interested here's the diff:

pastebin

I will dig little deeper when I have more time. Next weekend probably :)
[Touch HD Android Development] xdmcdmc:
Hi, changes are not so massive as it looks.

I just copied the drivers and blackstone panel source from #linux-msm branch. There the necessary drivers were already write for blackstone. My merit was only to figure out this and replace the video drivers and the panel and run a lot of tests ;)

But with latest changes for rhodium, I wasn't lucky so I believe all changes must be compared in order to find what broke the verbose mode.

This will most probably imply lots of tests.

Regards
[Touch HD Android Development] [ACL]:
i was finally able to commit last night.

sorry i cant be much help fellas. Trying to do this without a test device is really hard.
[Touch HD Android Development] Ghostface1979:
I'd like 2 help but please make a step by step guide for installing etc...

at the moment my Blackstone is running on 5.2.21916 09.nov.2010 WWE

I tried the partitioned version but it freezed every 5 min ( so not suitable for daily use).. If I know how then I'm glad to help banning WinMo from my phone
[Touch HD Android Development] Kapie:
any luck now? cant wait to have this on my blackstone :)
[Touch HD Android Development] raistlin74:
Hi all,

I have a blackstone for test.

If you need me, just let me know ;)
[Touch HD Android Development] Ghostface1979:
Correct me if I'm wrong, but only thing I have to do is use the Blackstoneuuwrapper

and flash my phone... bu t what happens if it does'n work...Can I flash back to my working WM-rom ??

Because I have to wait a couple of months before I can pick up my new phone cause of contract renewal..It's my only phone
[Touch HD Android Development] Kapie:
same here. if flashing works like WM rom, i would like to do it
[Touch HD Android Development] am20033:
devs have a blackstone, too. no need to flash it, because everyone will get the same result. the first step is done! now we have to wait for a better kernel.

please correct me if iḿ wrong!
[Touch HD Android Development] Lothaen:
Wow sounds like a cool project.
[Touch HD Android Development] nasko_spasko:
The project is great! But it needs 'some' time. I hope the developers can manage this :)
[Touch HD Android Development] helicopter88:
I know this isn't the right section,and maybe you could call me noob or anything else but to make a nbh for diamond i should only need to change mtype and other values or i should give up because it will be really hard?
[Touch HD Android Development] Eodun:
For XDAndroid? Give up for now if you don't know what you're doing, it's still under development
[Touch HD Android Development] helicopter88:
I'm not completely noob,i make ext2 bulid and some times ago i made for myself a wmrom and i found the diamond's ram addresses,but i want to know if it's a matter of changing that mtype and some other things + compiling the kernel or something harder that requires a better knowledge
[Touch HD Android Development] Eodun:
Sorry, no offense, I just wanted to stop anyone before bricking their phone if not knowing what they're doing ;)

Hope someone can enlighten you.
[Touch HD Android Development] helicopter88:
I didn't take offence of your post,don't worry
[Touch HD Android Development] g3rm0:
You need to change some values in tinboot.S and build script for your device (compare files from rhodium and blackstone to see what needs to be changed). It should be enough to build your NBH. You can accidentally brick your phone in the worst case scenario but you probably know that. I'm 100% sure you won't be able to fully boot Android so you will have to patch kernel by yourself - and this is the hardest part. We're not able to boot Android either but I hope we can figure it out soon.
[Touch HD Android Development] detlef25:
HELICOPTER88, I have a spare Diamond here. If the xdandroid devs don't need it, I could risk it for a quick test run of the NBH, if you are interested. What tinboot variables would have to be changed? ramsize, obviously - to 0x10000000? Anything else?

I had a quick look at the diamond panel code from the rhod-nand repo and it's virtually identical to the code from linux-msm, so I have some hope that the panel will just work right away :)

I suppose we'd need to adapt the changes ACL did to the rhod-nand branch for rhods board file to diamond, mostly USB changes I see. ACL, is this correct?
[Touch HD Android Development] helicopter88:
Tomorrow maybe i can try to do a nbh if kernel compiling doesn't require too much time,but i found those things when dumping a rom so i think that we have the ram addresses,we have the ram size,we know the mtype so a nbh could be bulit

RAMStart : 0x80329000
RAMFree : 0x803B4000
RAMEnd : 0x83000000
[Touch HD Android Development] Stickman89:
Won't work as those are not the correct addresses, those are values you got from a sys dump utility.

Sorry can't explain now I have my kids with me...

Best Regards,

ST1Cl<^^aN
[Touch HD Android Development] g3rm0:
Those values are incorrect! Do not use them. Use those already present in tinboot code. You only need to add kernel parameters for your device in tinboot.S and mtype in build script. Than build your NBH and see how far it goes. I heard about at least two guys who already bricked their devices trying NAND and you don't want to be next.
[Touch HD Android Development] detlef25:
Ok, thanks. Yes, I read e334s nand thread (shame about the brick). I assume that the memory is remapped by WinMo so that the first 2GB are mapped above 0x80000000, or something like that. So the values in tinboot fit HELICOPTERs values mostly if you subtract 0x80000000.

I'll see how much time I can sink into this today. I propose that we stop hijacking Blackstones NAND thread :)

Should we carry this on here: http://xdaforums.com/showthread.php?t=894014, or maybe better here, this threads is quite fresh: http://xdaforums.com/showthread.php?t=921820
[Touch HD Android Development] nasko_spasko:
Hi guys! It's getting too quiet here. :D

Any success?
[Touch HD Android Development] detlef25:
So I tried it on my RAPH300. Didn't want to risk the DIAM as it has totally different memory layout as far as I can see. Set MTYPE and kernel command line, double checked with strings that right kernel command line is included. Flashed alright.

When booting, the display only shows the HTC splash screen. After a few seconds, it vibrates once. Doesn't show up in adb. Nothing more happens.

EDIT: Took ACLs patch from here http://gitorious.org/linux-on-qualc...mmit/a80f99caa9252250055ea9c5ca871ba6a2c0a59c and massaged it into board-htcraphael.c.

Now it vibrates twice, which AFAICT means that it at least initializes the vibrator? Still nothing on the screen though. My patch up to now can be found here: http://pastebin.com/kMwZFPqA

EDIT2: Tinbooting an FRX03-era non-NANDed zImage (I think it was 01231-gfca2168 according to the modules.tgz) results in a HTC logo with a small black band on the left side... Kinda hard to describe. It doesn't change much visually, there is just this small black band which is about 10px wide and goes from top left corner to the left center. BTW, no dmesg.txt on the sdcard, so it doesn't seem to find that :(
[Touch HD Android Development] g3rm0:
Finally I had some time to play with NAND kernel. I've managed to enable panel using linux-msm-blac-nand repo and files xdmcdmc posted. Unfortunately with my changes I wasn't able to go any further than before (well one time it has stopped at "Welcome to Vogue Linux" line but it happened only once). Also I think most of my changes are unnecessary so I need to do some cleanup.

BUT... with untouched kernel (linux-msm-blac-nand) I was able to go as far as building data.img (yeah... only once)! My objective for now is to get to the point where data.img is being build with panel enabled. Maybe I'll have some time tomorrow :)

@detlef25:

Two vibs and nothing on display means that kernel was loaded successfully but panel wasn't enabled properly. For some reason our panel works fine with haret kernel on nand (kernel hangs quickly) but not with nand kernel (well not without modifications). You'll need to dig around your panel code to see what's going on.

PS. I've attached a blurry photo of my device stopped @ "Welcome to Vogue Linux". It was made using a webcam so it's not really readable but I can assure you it's real :)
[Touch HD Android Development] nasko_spasko:
Hi, g3rm0!

Do you mean that the problem with the nandboot and the ram addresses is now solved or I am missing something?

Best regards, FLeX!
[Touch HD Android Development] g3rm0:
For Touch HD we had correct addresses from the beginning (they were confirmed by [ACL] ) but we couldn't tell for sure because display wasn't initialized by the kernel. Later xdmcdmc replaced some files with the ones from haret kernel and he got panel to work (but we didn't exactly know WHY it worked). Now when I reproduced his changes I'm going to find what was the cause of this "panel trouble". After that there's still a long way before we can get usable nand Android (or even to boot it fully) but we're already further than I expected. Just keep in mind that I'm new to the linux kernel development so don't expect miracles anytime soon.
[Touch HD Android Development] detlef25:
The strange thing is that it won't even show much with a non-nand kernel. I guess its missing initialization that WinMo code does. I'm out of my depth here, no SD, no USB, no panel. I'll play with it more next week.

Great to hear of progress on Blackstone.
[Touch HD Android Development] nasko_spasko:
Ok, mate :) Thanks for explanation! :D
[Touch HD Android Development] neo_zycho:
hello guys, i know its not the right time to ask for this because you're all busy developing NAND. i just want to learn this also to help, hope you guys can point me to a tutorials, resources which i can develop and debug android. i'm a .net programmer and want to learn Anroid. i had downloaded the android sdk, but didn't know where to start. hope you guys are so kind enough to point me on the right direction. thank you
[Touch HD Android Development] Eodun:
Well, I'm not a dev, but I think a good place to get the basics is http://developer.android.com/guide/index.html, where you got the sdk, as it explains the Android system basics. Being a programmer, Java should be no challenge for you.

Have you downloaded Eclipse too?