Post Reply

Nook Touch kernel hacking

22nd April 2012, 04:03 AM   |  #91  
darkguy2008's Avatar
Senior Member
Flag Caracas
Thanks Meter: 224
 
645 posts
Join Date:Joined: Apr 2011
Donate to Me
More
I haven't investigated much on the recent posts, but I would strongly suggest compiling CM6 (or even Eclair or Froyo) since it's what the device currently runs, and then try CM7 and then CM9. CM9 isn't even ready for devices better than the NST (Defy?), it's buggy and HWA doesn't work very well, it would cause too much problems I think, rather than using a stable base.
22nd April 2012, 08:37 AM   |  #92  
Junior Member
Thanks Meter: 7
 
23 posts
Join Date:Joined: Apr 2012
Quote:
Originally Posted by klausef

You don't have to modify the provided source to get it to boot. At any rate, here is the guide:
http://nookdevs.com/Building_the_Noo...ile_the_Source

Thank you!
You say it boots, but what do you mean exactly? It works just like stock NST (excluding maybe some lack of speed because of SD card), or it is related to kernel only (say, before the init spawning point)?
In case of former I don't fully understand how it is possible without at least gpu modules.

EDIT: but maybe I understand ;) Produced uImage seems like only kernel proper, so needed modules may be still loaded from stock userspace FS.
If so, it will be a problem even for using Gingerbread (2.6.35 kernel).

Quote:
Originally Posted by klausef

Like the OP I am really not sure where to go here, although it is my intuition to get the latest and greatest Linux kernel to boot on it, then later try to get working whatever is the latest CyanogenMod 9 userland.

Quote:
Originally Posted by darkguy2008

I haven't investigated much on the recent posts, but I would strongly suggest compiling CM6 (or even Eclair or Froyo) since it's what the device currently runs, and then try CM7 and then CM9.

As for me, the point is also a HW requirements. NST has 800MHz single-core ARM and 256MB of RAM. Since the requirements of Android are a kind of secret, it is hard to guess, but ICS might be unsuccessful here, I think.
Anyway, the easiest and quite useful case may be a launching 2.1 Eclair because it is closest to stock. Next I am voting for CM7 (Gingerbread) :)
More contemporary Android versions might have bad performance for this case, I'm not sure 256MB RAM is enough.

ADD: some remarks to the new wiki page:
1) CROSS_COMPILE must be a arm-linux-androideabi-, not an arm-eabi- for that google toolchain, isn't it?
2) I was asked for some config options about MMC cards and FAT filenames with that config. Has anybody the same experience?
Last edited by corge; 22nd April 2012 at 03:43 PM.
The Following User Says Thank You to corge For This Useful Post: [ View ]
22nd April 2012, 05:18 PM   |  #93  
Senior Member
Thanks Meter: 132
 
208 posts
Join Date:Joined: Jun 2007
Donate to Me
BN released a new kernel source. http://images.barnesandnoble.com/PRe...ook2_1-1-5.tgz

The main difference seems to be the support for the backlight, but there are also some changes in the usb and touchscreen drivers.

I compiled the kernel without changes http://code.google.com/p/nst-recover..._1_5_stock.zip and one with multitouchsupport http://code.google.com/p/nst-recover...1_5_multitouch

Had no time to try to integrate usb-host. Source can be found at https://github.com/mali1/NST-kernel_115
The Following User Says Thank You to mali100 For This Useful Post: [ View ]
23rd April 2012, 02:18 PM   |  #94  
Junior Member
Thanks Meter: 7
 
23 posts
Join Date:Joined: Apr 2012
1.1.5 doesn't build for me with omap3621_gossamer_defconfig. Can it be a pre-release version (sw update and TOS pages at B&N still contain 1.1.2)?

omap3621_gossamer_evt1c_defconfig builds fine.

Also, after configuration like `make ARCH=arm CROSS_COMPILE=arm-linux-androideabi- omap3621_gossamer_evt1c_defconfig` additional questions don't appear.


ADD: no success with booting custom kernel. Nook still works fine even with "while (true) {ssleep(1);}" in rest_init() in init/main.c.

Has anyone any ideas? Shall uImage be written by cp, not by dd, for example?


ADD2: it may be related to SD card formatting, I'll check it.
Besides that, could anyone please tell what is a correct load address and entry point for uImage?
Last edited by corge; 30th April 2012 at 08:57 AM.
The Following User Says Thank You to corge For This Useful Post: [ View ]
10th May 2012, 11:02 AM   |  #95  
Junior Member
Thanks Meter: 7
 
23 posts
Join Date:Joined: Apr 2012
I still can't get a success with boot from SD.

Could anyone please show the following output for working card and confirm that valid load address and entry point is 0x80008000?

/dev/sdb should be replaced to your device (no trailing number):

Code:
# parted /dev/sdb print
Model: SanDisk uSD SDDR-289 (scsi)
Disk /dev/sdb: 1948MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      66.0kB  1948MB  1948MB  primary  fat32        boot, lba
The Following User Says Thank You to corge For This Useful Post: [ View ]
10th May 2012, 12:12 PM   |  #96  
Member
Flag Raleigh
Thanks Meter: 31
 
57 posts
Join Date:Joined: Jul 2011
Wassup corge,

Yeah, 0x80008000 is where you should make the uImage load and execute. When you put in the SD card, does it bootloop, or does it just continue to the internal uImage?

It sounds like it's just going to the internal storage and ignoring the SD card's kernel outright. If that is the case, I am guessing it is a problem with uBoot. Try recompiling it from the B&N source (using the omap_gossamer config IIRC), then stick the produced files in the SD card's boot partition. If you don't want to do that you could try taking all of the files ending in .bin from mali100's Nooter image and putting them in the boot partition.

Also, do you have a Nook Touch Old or a Nook Touch GlowWorm?
Last edited by klausef; 10th May 2012 at 12:31 PM.
The Following 2 Users Say Thank You to klausef For This Useful Post: [ View ]
10th May 2012, 01:16 PM   |  #97  
Junior Member
Thanks Meter: 7
 
23 posts
Join Date:Joined: Apr 2012
Quote:
Originally Posted by klausef

Yeah, 0x80008000 is where you should make the uImage load and execute. When you put in the SD card, does it bootloop, or does it just continue to the internal uImage?

It sounds like it's just going to the internal storage and ignoring the SD card's kernel outright.

Thanks!
You are right, I think—seems like it just ignores SD card and boots from internal uImage.
However it should be noticed that I have unrooted NST (old, without glow), so I've added an infinite loops to rest_init() in init/main.c and sys_open() in fs/open.c just to detect what kernel is loaded. I may be wrong here with detection method ;)

I've tried 1.1.2 sources with both arm-eabi-4.4.3 and arm-linux-androideabi-4.4.x toolchains from here: https://android.googlesource.com/platform/prebuilt

Quote:
Originally Posted by klausef

If that is the case, I am guessing it is a problem with uBoot. Try recompiling it from the B&N source (using the omap_gossamer config IIRC), then stick the produced files in the SD card's boot partition. If you don't want to do that you could try taking all of the files ending in .bin from mali100's Nooter image and putting them in the boot partition.

Hm, I didn't suspect that there is a possibility to boot from SD not just kernel but uboot too. Will it leave the internal uboot untouched? If so, I'll try it.

Finally, the partitioning at my SD card may be wrong (partition offset, flags, maybe something else), so I'd like to verify that too with somebody's listing.

ADD: it may be some watchdog there which reboots to internal uImage..

ADD2: no, it doesn't seems like device is rebooted by itself. I've changed also USB product and manufacturer names in board-3621_gossamer.c, but these changes are not shown while connecting Nook to PC.
Last edited by corge; 10th May 2012 at 02:13 PM.
10th May 2012, 04:06 PM   |  #98  
Member
Flag Raleigh
Thanks Meter: 31
 
57 posts
Join Date:Joined: Jul 2011
Quote:

Finally, the partitioning at my SD card may be wrong (partition offset, flags, maybe something else), so I'd like to verify that too with somebody's listing.

I posted mine here at NookDevs:

http://nookdevs.com/Nook_Simple_Touc...artition_table
The Following User Says Thank You to klausef For This Useful Post: [ View ]
10th May 2012, 04:38 PM   |  #99  
Junior Member
Thanks Meter: 7
 
23 posts
Join Date:Joined: Apr 2012
Thanks! It is useful too, but I've asked for SD card partitioning, not internal storage ;)
Just a same thing, but for card which is successfully booting with custom uImage on it.
10th May 2012, 05:14 PM   |  #100  
Senior Member
Thanks Meter: 132
 
208 posts
Join Date:Joined: Jun 2007
Donate to Me
Quote:
Originally Posted by corge

Thanks! It is useful too, but I've asked for SD card partitioning, not internal storage
Just a same thing, but for card which is successfully booting with custom uImage on it.

It's the same, because we just write a identical image from the internal storage to the SD-Card.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Nook Touch Android Development by ThreadRank