Also it may be a question what is right from this two cases. Could anyone please show the `cat /proc/cpuinfo` output? "Revision" there is indicating a needed config.Y'all used `omap3621_gossamer_defconfig` and `omap3621_gossamer_evt1c_defconfig` but do any of the others work? (boot)
# cat /proc/cpuinfo
Processor : ARMv7 Processor rev 2 (v71_
BogoMIPS : 597.64
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture : 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2
Hardware : OMAP3621 GOSSAMER board
Revision : 0005
Serial : 3014430162723006
Could you please describe more exactly whan you've done with GPU and WiFi modules?I've finally gotten to the point where the OP was; I was able to compile the kernel provided by nook source and run it off of the SD card.
BOARD_ENCORE_REV_EVT1A 0x1
BOARD_ENCORE_REV_EVT1B 0x2
BOARD_ENCORE_REV_EVT2 0x3
BOARD_ENCORE_REV_DVT 0x4
BOARD_ENCORE_REV_PVT 0x5
BOARD_ENCORE_PROD_3G 0x8
BOARD_ENCORE_REV_UNKNOWN 0x6
BOARD_GOSSAMER_REV_EVT1A 0x1
BOARD_GOSSAMER_REV_EVTPRE1C 0x2
BOARD_GOSSAMER_REV_EVT1C 0x3
encore_board_evt2: revision >= BOARD_ENCORE_REV_EVT2
gossamer_board_compatible_evt_pre1c: revision <= BOARD_GOSSAMER_REV_EVTPRE1C
Please post here a link then.
Thank you!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_Nook_Touch_stock_kernel#Step_3:_Configure_and_Compile_the_Source
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.
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.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.
# 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
Thanks!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.
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.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.
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.
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.
drew@master: nook_touch$ adb shell cat /proc/version
Linux version 2.6.29-omap1 (drew@master) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #3 PREEMPT Tue Oct 4 14:37:59 CDT 2011
drew@master: nook_touch$ adb shell cat /proc/mounts
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext4 ro,barrier=1,data=writeback 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
Correct, the kernel is a compiled binary and not packed, so no way to unpack it.It seems I was unpacking the wrong files which were so hard to unpack I couldn't unpack them. I guess the uImage is a binary kernel not able to be unpacked? I tried lots of cpio/gunzip commands and scripts online to unpack u-boot files but they didn't work .
I also think hhe sourcecode released by BN isn't enough to build android, and there is no configuration that you could use, so you have to start from scratch.I have a question now though: In order to get the uRamdisk, I need to build an android system. The thing is... B&N didn't give sources for an android version, it seems. They only gave sources for a kernel, which is okay but it isn't enough (I think??) to build an android filesystem from the ground zero, right?
I'm wondering, if I want to build Eclair (for example, which is the current working version in the NST), which config should I use? I've seen I could use something like "encore" or "zoom2" (as the same build.prop in the NST states, "zoom2") to build /system and mix it with B&N's kernel? or am I wrong?
It should be possible, but I never tried it:my objective is to build, aside from a kernel, a pure android ROM too.Hm, but that would still run /system from the nook. My idea was to make a SD that would boot -and- use the files from itself instead of touching the NST's files. That way, I could happily work on a custom android version without having to mess with my NST's filesystem and risk messing it up and having to restore it again with dd.
A lot of information about the sgx kernel-modules can be found on http://omapedia.org/wiki/Graphics
Omappedia is a really great source for us. There is also a git repo for the dsp-bridge.