yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] jwxuan:
This is my nook g2 test result

I just download a htc mobile fastboot driver and modified it as your command，it give me the information which is a little different ！

Microsoft Windows XP [版本 5.1.2600]
(C) 版权所有 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>f:

F:\>omap3630.exe omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage uRamdisk
Waiting for bootloader... ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v03.bin, 175048 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... ok
product 3621GOSSAMER
version 0.5
Making boot image...
Could not find kernel file uImage

F:\>
[Nook Touch General] straygecko:
Woo hoo! We've got fastboot on an NG2. That means I can quit compiling u-boot.:cool:

What uImage and uRamdisk were you using? What did your NG2 screen show?
[Nook Touch General] Renate:
As far as the two UMS disk drives that present themselves when the NG2 is in USB mode:

It appears that 1.3 is designed to be compatible with the NST and NG1.

The 2nd disk is the SD card, which doesn't exist on the NG2.

I would guess that shanks7777 is trying to load uImage and uRamdisk from stock.

You need to use the CWM image and ramdisk.

Playing with this some more on my NST I have problems getting fastboot working, even when using u_boot12.bin

It appears that it tries to go to the next boot device (the internal storage).

We still haven't gotten the console to work out of the u-boot yet.

Yes, we have the boot args passed down and can put in ttyS1, but that only applies to the image that is loaded.

(Note: The latest u-boot still has ttyS0 in it, I manually change it.)

I tried simplifying the boot script and just putting in for bootcmd:

bootcmd=run setbootargs; fastboot

I can't get it to fastboot.
[Nook Touch General] straygecko:
Possibly or he could be using the CWM uImage & uRamdisk I included early on. Honestly, I think its a long shot that the CWM for the NST will work on the NG2. I see enough differences in u-boot, like a different offset to the USB device and different MUX config, that it has a good probability of failing. Then again, the kernel is a lot smarter than u-boot and may deal with the differences. I looked at the kernel changes and ended up unsure if the changes there are critical to getting CWM to work.

Hmm... I can consistently boot into CWM. Is this random for you?

I was doing very minimal changes to isolate the problem with bad u-boot builds so I left any ttys1 stuff out. Now that I can consisently build u-boot I'll make you a test build with my best guess at UART2 support. I reviewed the kernel source and think I know what to do.

I tried that too and it didn't work. I also tried going to fastboot in main.c where its normally done but the code was ifdef'd out. Wouldn't work. B&N has somehow put some initialization it needs pretty late in the game. Not sure what in that bootcmd chain of commands is necessary but I think you need run autodetectmmc and run readtokens - everything else seems like recovery boot or update zip stuff that should be able to be ripped out. B&N reads files from the rom & boot partitions in lots of places and may not like it if mmcbootdev and mmcromdev aren't set by autodetectmmc. The display driver or one will try reading boot.scr if vcom isn't set by readtokens. Why this stuff is happening so late I haven't sorted out.
[Nook Touch General] straygecko:
Another try for a console in u-boot

Renate, here's a build of u-boot with the bootargs defaulted to ttys1 and config changes hopefully to get it to output its console messages to uart2. I also eliminated all of the checking for recovery boot and update image stuff - bootcmd is just autodetectmmc, readtokens & fastboot. Boots to CWM on my NST. Give it a whirl.

There is nothing new for anyone else in this build - its for Renate's testing only.
[Nook Touch General] shanks7777:
Sorry for late reply.

I first tried with the uImage and uRamdisk from NookManager.img

Then, I tried with the uImage and uRamdisk from CWM on this link ( http://xdaforums.com/showthread.php?t=1675706 ).

Both case showed exactly same result.

My NG2 was stopped at the booting screen.

---------- Post added at 04:55 PM ---------- Previous post was at 04:00 PM ----------

I tried little bit differently, by separating to two procedure.

D:\성산\nook>omap3630.exe omap3_aboot.bin u-boot-ng2-exp-v03.bin
Waiting for bootloader... ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v03.bin, 175048 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... ok
product 3621GOSSAMER
version 0.5

D:\성산\nook>fastboot devices
[DEVICE NUMBER OR SOMETHING HERE] fastboot

D:\성산\nook>fastboot boot uImage_cwm uRamdisk_cwm
creating boot image...
creating boot image - 4079616 bytes
downloading 'boot.img'...
OKAY [ 0.219s]
booting...
OKAY [ 0.000s]
finished. total time: 0.219s

D:\성산\nook>fastboot devices
???????????? fastboot

After the NG2 got fastboot, my PC seems to recognized NG2.

However, after downloading uImage and uRamdisk from CWM, it didn't recognized it anymore.

And still not boot into CWM.
[Nook Touch General] Renate:
[MENTION=1584045]straygecko[/MENTION]

The best way to get a good mux config is to look at one that works.

I figured that this one works because I dumped it using my console plug. :silly:

# ./muxdebug
OMAP36XX Mux Debugger

McBSP3_DX 4800216C 010C Mode 4, input, pulldown
McBSP3_DR 4800216E 010C Mode 4, input, pulldown
[b]McBSP3_CLKX 48002170 0001 Mode 1, output
McBSP3_FSX 48002172 0109 Mode 1, input, pulldown[/b]

UART2_CTS 48002174 010C Mode 4, input, pulldown
UART2_RTS 48002176 010C Mode 4, input, pulldown
UART2_TX 48002178 010C Mode 4, input, pulldown
UART2_RX 4800217A 010C Mode 4, input, pulldown

[b]UART1_TX 4800217C 0000 Mode 0, output
UART1_RTS 4800217E 0000 Mode 0, output
UART1_CTS 48002180 0118 Mode 0, input, pullup
UART1_RX 48002182 4118 Mode 0, input, pullup[/b]

UART3_CTS_RCTX 4800219A 010C Mode 4, input, pulldown
UART3_RTS_SD 4800219C 010C Mode 4, input, pulldown
UART3_RX_IRRX 4800219E 010C Mode 4, input, pulldown
UART3_TX_IRTX 480021A0 010C Mode 4, input, pulldown

HSUSB0_DATA0 480021AA 0100 Mode 0, input
HSUSB0_DATA1 480021AC 0100 Mode 0, input
HSUSB0_DATA2 480021AE 0100 Mode 0, input
HSUSB0_DATA3 480021B0 0100 Mode 0, input
[Nook Touch General] straygecko:
LOL, that's exactly what an unmodified u-boot sets it to. :D No need to mess with MUX settings. Now I don't understand why my first attempt to just set output to COM2 without altering the MUX settings didn't work. I'll take another look at u-boot while I try to sort out compiling a NG2 kernel to used with CWM.
[Nook Touch General] straygecko:
Another try for NG2 CWM

OK, I compiled a couple of kernels from the B&N 1.3.0 source. The NST kernel I compiled mostly successfully booted CWM. Everything but the display worked. ADB worked fine, even the n key selected reboot for me. Just never saw anything on the screen. Looking through the kernel source it may not have been completely updated to compile properly for the NST. Some changes that look like they should be configuration dependent (like panel resolution) appear to be hard coded to NG2 hardware. That may explain why the display didn't work. So cross your fingers, my NG2 kernel might boot CWM for you. Even if it works like my NST without the screen display at least we'll have ADB. I've attached the NG2 uImage and CWM ramdisk for our adventurers to try out.
[Nook Touch General] jwxuan:
I hope the result is good

I take a test ，it gave me the information like before，and the NG2 stopped at the boot interface.

Microsoft Windows XP [版本 5.1.2600]
(C) 版权所有 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>f:

F:\>omap3630.exe omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-evt1b-exp
-v00 uRamdisk-cwm-nst-rc2
Waiting for bootloader... ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v03.bin, 175048 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4007936 bytes... ok
Waiting for disconnect... ok
Waiting for ADB...

Then I open the adb.exe, and a window flashed and gave some information which is too fast to remember anything!
[Nook Touch General] Renate:
adb.exe is a command line application, not a GUI application.

You need to run it in a "MS-DOS" window, a command line, a shell.

It was probably just listing its help, which is what it does when you type just "adb".

It's better to look on your Device Manager.

From the command line, that's devmgmt.msc

Do you see something with yellow exclamation marks?

Do you see under "Android Phones" "Android Composite ADB Interface"?
[Nook Touch General] Renate:
Ok, a bit of a different concept here.

The new version is called omaplink.exe

Keep your old omap3630.exe around if there are any problems, but this should be the master branch from now on.

Whenever you do the full load process on your Nook your PC probably sounds like a pinball machine on steroids.

You are probably wondering what it's doing. I did.

omaplink.exe works the same as the old omap3630.exe except it has a little popup.

It will show what interfaces it detects.

It will also show the number of storage volumes that are mounted.

The base number depends on your system, mine shows 6 until a Nook is plugged in when it turns to 8.

I hope that this makes things easier to follow the progress along with the command line.

P.S. Make sure that ADB is not running beforehand by using adb kill-server.
[Nook Touch General] usenothing:
hi, Renate:

I do a test just now. I worked out the driver on win7_x64 . as the shut below:

then I power off the NOOK GL completely ,and run "adb kill-server" in CMD window, as the shut below:

then run omaplink.exe in CMD window, as the third shut below:

I run "adb devices" , then got this:

I don't know why this happened ? why did adb not run normally ?
[Nook Touch General] shanks7777:
I just tried this one with experiment7.

Result shown in command console was just same as before. (Stopped at Waiting for adb....)

However, when I pressed the 'n button' NG2 rebooted.

So I think NG2 was successfully booted in to CWM except the display. (I guess this is a good thing!)

Though, weird thing is that even in this step, adb server was offline.
[Nook Touch General] Renate:
For all those who get to "Waiting for ADB" and no further:

We are getting very close.

Let's not be too quick to think that the ADB is not there.

There could be something wrong with my ADB detector or something confusing us.

So when we get to the end and it says, "Waiting for ADB", let's look carefully.

[MENTION=5591880]jwxuan[/MENTION] I see that there is an "Android ADB Interface" showing.

Is that the Nook? Do you have another device plugged in?

Go to Properties in Device Manager and look at the VID/PID.

Are they 2080/0007 ?

What does adb devices say?

There are 3 possibilities:

No devices found

Device found with id listed, but offline

Device found with id listed and online

At anytime you can run omaplink.exe with no arguments.

It will display what it sees.

Unless something shows a bootloader interface it will just sit there and display interfaces.

You can take your cell phone and plug it in and out and the ADB led should go on and off.

[MENTION=4388886]shanks7777[/MENTION] I would guess that your Nook opened the interface for ADB but is not responding.

omaplink should be showing the led if the interface is visible but not responding.
[Nook Touch General] shanks7777:
This is my last state when I used omaplink.exe
[Nook Touch General] usenothing:
Hik Renate:

I pluged my Nook GL to PC and checked the VID.

Your idea was verified : the VID/PID is 2008/0007 .

Here is the screen-shut
[Nook Touch General] usenothing:
I have the same result when tried this morning : http://xdaforums.com/showthread.php?p=48949273#post48949273

It stayed at the "waiting for adb..." interface without the popup led lighted.
[Nook Touch General] shanks7777:
Of course, I tried "adb devices", but only got the message that adb server is starting and there is no device connected.
[Nook Touch General] Renate:
[MENTION=4388886]shanks7777[/MENTION] Are you seeing an Android ADB Interface under Android Phones in Device Manager?

If you can't see one, then we are just dealing with the problem of getting CWM to work correctly.

The fact that the "n" button reboots would seem to indicate something is working.

Something weird is going on if both omaplink and the ADB server can't see it when it's in the Device Manager.

Do you have another Android device that works in ADB?

Does it cause the ADB led to go on and off when plugged/unplugged?

The only thing that I can think of off-hand is if the Interface does not have the correct DeviceInterfaceGUID.

In this case it could not be enumerated correctly.
[Nook Touch General] jwxuan:
There is no android device

The result is

Microsoft Windows XP [版本 5.1.2600]
(C) 版权所有 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>f:

F:\>adb kill-server
* server not running *

F:\>omaplink.exe omap3_aboot.bin u-boot-ng2-exp-v03.bin uImage-ng2-130-evt1b-exp
-v00 uRamdisk-cwm-nst-rc2
Waiting for bootloader... ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot-ng2-exp-v03.bin, 175048 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4007936 bytes... ok
Waiting for disconnect... ok
Waiting for ADB...

View attachment 2483355

There is a weird thing，after fastboot，omaplink fist displayed 6 volumes，then it turned to 8 volumes，soon it became 6 volumes again，and then it turned to 8 volumes forever！But there is no android device fund! Maybe this is because I am not good at using adb program，there is something wrong！

View attachment 2483377
[Nook Touch General] shanks7777:
Actually, nothing showed up in Device Manger.

As jwxuan said, it was rather recognized as "Disk drive", or "USB mass storage device".

My Samsung GS3 and Galaxy Nexus just works fine with the ADB things.
[Nook Touch General] Renate:
Well, I'm still confused.

jwxuan is showing two different DevMgmt screen shots, one with Android ADB, one without.

shanks7777 says there is nothing in DevMgmt.

Here's how CWM boots up:

First nothing

Then 2 disk drives on a simple USB device

Disk drives disappear

Then 2 disk drives plus ADB on a composite USB device

It seems that CWM is stopping when the disk drives appear.

Does omaplink and DevMgmt show up correctly when plugging in an Android Phone?
[Nook Touch General] shanks7777:
This is the result when I connected SGS3.

In case of NG2, only 2 disk drives showed up on step 4, but NO ADB composite device.
[Nook Touch General] Renate:
It looks like shanks7777 is having problem getting CWM started ok.

CWM does have console output that I can see on my NST.

I'll try to look at this on my NST and see if I can see what could be the problem.

Of course a console output on a NG2 would be even better.

Ok, I know that this is "polishing the cannonball" but here's a new version of omaplink.exe

It does some basic probing of the ADB link (without the adb.exe running).

It will ID as "recovery" on CWM or "device" on a regular device.

[i]... same stuff you've seen pasted before ...[/i]

Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect... ok
Waiting for ADB... ok
[b]Version: 01000000, payload: 4096, ack: recovery::[/b]
[Nook Touch General] Renate:
I got CWM in landscape mode!

Oh, no, I have yet another new version of omaplink.

This adds command line override options to the kernel.

It means that you can play and experiment with parameters easily.

A proof of principle is getting CWM in landscape mode.

Since the NG2 has a different display, the values will be different.

Also the NG2 has gone to a TPS65185 eInk PMIC instead of the old TPS65181.

I don't think that they are software compatible.

For me to boot my NST into CWM I can use this:

C:\C\OmapLink>omaplink omap3_aboot.bin u-boot12.bin uRecImg uRecRam /c"console=ttyS1,115200n8 initrd rw init=/init vram=16M video=omap3epfb:mode=800x600x16x14x270x0,pmic=tps65180-1p2-i2c,vcom=-1900 androidboot.console=ttyS1"

The pmic chunk refers to the driver to control the PMIC over I2C.

My first guess with the NG2 would be tps65185-1p2-i2c, but that's just a shot in the dark.

OTOH, our CWM probably has nothing in it for the TPS65185.

The vcom is the default value in millivolts for the eInk backplane.

You should probably just leave vcom as it is.

Maybe the faulty video is locking up the Nook and preventing ADB from working.

Maybe try it with the entire video chunk of args missing?

To make CWM in landscape mode on the NST, I change the 270 to 0.

Edit: I tried my NST without any video params and the ADB works but the screen is blank.

Maybe we should try to get the NG2 on CWM without any screen?
[Nook Touch General] straygecko:
Both the 1.2.0 kernel source and the 1.3.0 kernel source include the drivers for both PMIC and it looks like they should both compile into the kernel. u-boot is supposed to setup the boot arguments for the vcom and pmic. Both 1.2.0 & 1.3.0 u-boot probes for the PMIC and adds pmic=tps65185-i2c or pmic=tps65180-1p2-i2c to the boot arguments. Assuming it works correctly. It also reads the vcom value from the rom partition devconf/EpdVcom on the device and adds it to the boot arguments which on my device is -2030. Again, assuming it works properly. I'll try your new kernel options override and see if I can get my 1.3.0 NST kernel to display with CWM. Perhaps its u-boot that is a problem - B&N did a fair amount of changes in the display area including some changes to probing. If the proper environment variables don't get set it could leave those parameters empty. OTOH CWM displays fine with the CWM kernel but not with my compiled 1.3.0 NST kernel.

It sounds like shanks7777 may have got there. Pressing the n key rebooted his NG2 after booting with my NG2 1.3.0 kernel and the CWM ramdisk. CWM has the reboot option highlighted when it first starts up so pressing the n key reboots. That's what confusing me the most about this. My NG2 1.3.0 kernel with the CWM ramdisk seems to get far enough to present the NG2 as disk drives over USB and probably gets the CWM menu displayed (even if it can't be seen) but no ADB.

Another idea I'm toying with is building a u-boot with a hacked fastboot to load the kernel from the device instead of using what's passed to it so we know we're getting a good NG2 kernel. I'd still use the ramdisk passed to fastboot. It should be pretty simple to do and will eliminate another variable. I could add a getvar for pmic & vcom too.
[Nook Touch General] Renate:
Oops, I missed seeing "tps65185-i2c" in the u-boots, that's the one.

The funny thing is, on the standard Nook boot I don't get anything out of the console until 20 seconds in.

With CWM I get console output from the get-go:

[ 0.000000] Linux version 2.6.29-omap1 (build@dhabuildimage16) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #1 PREEMPT Sat Oct 29 00:45:49 PDT 2011
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] Machine: OMAP3621 GOSSAMER board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] L2 CACHE is enabled in bootloader
[ 0.000000] OMAP3630 ES1.2
[ 0.000000] OMAP: omap_rev:0x36300234 omap_chip.oc:0x00000704
[ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xfc800000 size: 0x100000
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048
[ 0.000000] Kernel command line: console=ttyS1,115200n8 initrd rw init=/init androidboot.console=ttyS1
[ 0.000000] Unknown boot option `androidboot.console=ttyS1': ignoring

You can see that androidboot.console=ttyS1 is not a valid option.
[Nook Touch General] straygecko:
Why compile a kernel when we've already got a known good one?

One more time with feeling...

I've hacked u-boot so that fastboot will ignore the kernel you pass it and use the kernel on your device. It will use the ramdisk you pass it so we can get CWM up. This should get rid of any kernel incompatibilities that may be causing us problems. I have also added the ability to display any u-boot environment variables using the fastboot getvar command. If you try to getvar anything other than version, product, serialno or downloadsize it will return the value of the corresponding environment variable. On my NST I have verified that the correct environment variables are getting set for the display so I think uboot is doing its job properly and we've been seeing a kernel issue causing CWM not to display and possibly causing ADB problems. No need to worry about doing any getvar's at this point but I might ask for some later.

So extract the attachment and try this (uImage must point to a valid uImage but won't be used):

omaplink omap3_aboot.bin u-boot-ng2-exp-v05.bin uImage uRamdisk-cwm-nst-rc2

Lets hope we see CWM on your displays. :fingers-crossed:
[Nook Touch General] shanks7777:
Okay. So I tried two things.

Experiment8 (First version of omaplink.exe) with this u-boot.

Experiment10 with this u-boot w/o any additional args (I mean... /c"console=ttyS1,115200n8 initrd rw ... kinda things).

For both case, it ended up exactly same as before.

No ADB, frozen screen, however rebooted when I press the "n button".
[Nook Touch General] Renate:
Just a bit more "window-dressing" on omaplink.exe

The functionality is the same as before.

C:\>omaplink omap3_aboot.bin u-boot12.bin uRecImg uRecRam
Waiting for bootloader... 0451:D00E, OMAP3630, pbi, ok
Received ASIC id, 69 bytes
OMAP36XX, rev 07
Unlocked
ID12: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ID14: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
CRC1: EF3EBF13, CRC2: 00000000
Sending image file omap3_aboot.bin, 3480 bytes... ok
Ack: AABBCCDD
Sending image file u-boot12.bin, 170572 bytes... ok
Waiting for disconnect... ok
Waiting for fastboot... 0451:CAFE, 3621GOSSAMER, Android Fastboot, ok
product 3621GOSSAMER
version 0.5
Making boot image... ok
Sending boot image, 4087808 bytes... ok
Waiting for disconnect... ok
Waiting for ADB... 2080:0003, NOOK, ok
Version: 01000000, payload: 4096, type: recovery