NAND boot testing. Test 5: SOUND!!!!/Test 7: Single NBH/Serialno/tilt2 fix

[natemcnutty]

Wirelessly posted (Opera/9.80 (Android; Opera Mini/5.1.21126/20.2463; U; en) Presto/2.5.25)

Originally Posted by butler360

Holy f*ck...

Right there with ya. Just about shot scotch through my nose.

Dude. When you launch using Heret (which belongs in the other thread btw), you are pulling a lot of things from wince. If you have a super-light wince, Andriod will see more available RAM. Any further questions, just make a new thread.

I was wondering if someone could help me out here, Im trying to flash back to winmo rom via sd. I made sure the partition was fat32, I renamed the nbh to "RHODIMG.NBH" and start up the bootloader by holding vol down and power. Everytime I do this I get this very quick message that says "no image found", i am using 1.00.Olinex (H?)spl. Can someone help me in the right direction?

edit: Also, the reason I'm posting this here is because I tried the nbh from here for RHOD400.

[[ACL]]

Originally Posted by natemcnutty

I've compiled linux kernels in the past, though I have yet to do one for Andriod. Let me run through this and see if I have the right process, and maybe give me a refresher.

I'm cloning git://gitorious.org/linux-on-qualcomm-s-msm/linux-msm.git
Then checkout htc-msm origin/htc-msm
Then make defconfig (What defconfig are we using?)
Then clean
Then cross compile zImage (What is the path to the toolchain we are using?)

Do we care about cleaning compiled files and rebuilding from scratch? I've got a Core i7 930 machine with a Vertex 2 SSD to crunch this on. I'm totally willing to help. Just need specifics

Wrong kernel. We have our own clone since haret version is different.
linux-msm-rhod-nand in ACL - Gitorious

htc_msm_android_defconfig is our def config

the standard android toolchain. I dont know the specifics of that.

[natemcnutty]

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/20.2463; U; en) Presto/2.5.25)

Originally Posted by [ACL

]

Wrong kernel. We have our own clone since haret version is different.
linux-msm-rhod-nand in ACL - Gitorious

htc_msm_android_defconfig is our def config

the standard android toolchain. I dont know the specifics of that.

Sounds good. I'll give it a shot tomorrow and let you know if I run into issues. Once I get it down, I'll set up a script to do it for me

[StarLite]

Originally Posted by natemcnutty

Wirelessly posted (Opera/9.80 (Android; Opera Mini/5.1.21126/20.2463; U; en) Presto/2.5.25)
Dude. When you launch using Heret (which belongs in the other thread btw), you are pulling a lot of things from wince. If you have a super-light wince, Andriod will see more available RAM. Any further questions, just make a new thread.

That simply not true.
When I launch android via HaReT, I have about 40MB of RAM free in windows. In Android I have about 90-105 MB free, so the free RAM in android has nothing to do with the free RAM in wince...

[[ACL]]

Originally Posted by natemcnutty

Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/20.2463; U; en) Presto/2.5.25)



Sounds good. I'll give it a shot tomorrow and let you know if I run into issues. Once I get it down, I'll set up a script to do it for me

That would help out a lot thanks.

[natemcnutty]

Originally Posted by [ACL]

That would help out a lot thanks.

OK, so I got everything set up and grabbed google's android toolchain. When compiling, it seemed to be going OK with a few warnings until it hit board-htcrhodium.c

I have attached the log file. I also tried using the code sourcery toolchain (both 2008q3 and 2010q1), and they both had fatal errors compiling board-htcrhodium.c as well.

[[ACL]]

Originally Posted by natemcnutty

OK, so I got everything set up and grabbed google's android toolchain. When compiling, it seemed to be going OK with a few warnings until it hit board-htcrhodium.c

I have attached the log file. I also tried using the code sourcery toolchain (both 2008q3 and 2010q1), and they both had fatal errors compiling board-htcrhodium.c as well.

Can you verify that the following are set

CONFIG_USB_GADGET=y
CONFIG_USB_GADGET_VBUS_DRAW=500
CONFIG_USB_GADGET_SELECTED=y
CONFIG_USB_GADGET_MSM_72K=y
CONFIG_USB_MSM_72K=y

CONFIG_USB_GADGET_DUALSPEED=y
CONFIG_USB_ANDROID=y
CONFIG_USB_ANDROID_ACM=y
CONFIG_USB_ANDROID_ADB=y
CONFIG_USB_ANDROID_DIAG=y
CONFIG_USB_ANDROID_MASS_STORAGE=y
CONFIG_USB_ANDROID_RNDIS=y

CONFIG_USB_FUNCTION is not set <-- must be disabled
CONFIG_USB_FUNCTION_MSM_HSUSB is not set <-- must be disabled

[natemcnutty]

Originally Posted by [ACL]

Can you verify that the following are set

CONFIG_USB_GADGET=y
CONFIG_USB_GADGET_VBUS_DRAW=500
CONFIG_USB_GADGET_SELECTED=y
CONFIG_USB_GADGET_MSM_72K=y
CONFIG_USB_MSM_72K=y

CONFIG_USB_GADGET_DUALSPEED=y
CONFIG_USB_ANDROID=y
CONFIG_USB_ANDROID_ACM=y
CONFIG_USB_ANDROID_ADB=y
CONFIG_USB_ANDROID_DIAG=y
CONFIG_USB_ANDROID_MASS_STORAGE=y
CONFIG_USB_ANDROID_RNDIS=y

CONFIG_USB_FUNCTION is not set <-- must be disabled
CONFIG_USB_FUNCTION_MSM_HSUSB is not set <-- must be disabled

Everything in my defconfig looks exactly as you have it here. The last two items are indeed commented out.

Here's what I've done so far:

git clone git://gitorious.org/~acl/linux-on-qualcomm-s-msm/linux-msm-rhod-nand.git
cd kernel
git checkout -b htc-msm origin/htc-msm
make ARCH=arm htc_msm_android_defconfig
make ARCH=arm CROSS_COMPILE=/home/nathan/toolchains/google/arm-eabi-4.4.0/bin/arm-eabi- zImage

I just tested building the main git and everything compiled perfectly. I'll take a look through the code when I get home to see if I can notice a missing bracket anywhere. I would say I have somewhere between beginner and intermediate Java coding skills, so it probably won't be too helpful, but it seems it is always an ending quote, parenthesis, or bracket...

[arrrghhh]

Originally Posted by natemcnutty

I would say I have somewhere between beginner and intermediate Java coding skills, so it probably won't be too helpful, but it seems it is always an ending quote, parenthesis, or bracket...

Ha, I'm not much of a programmer anymore, but this used to drive me NUTS in C++... the error was always so vague, but it was usually right near the problem line - so I guess in that sense it was fairly easy to debug