Reboot of Blaze Tablet fails after flashing Android JB4.2 images

[Narasimha Bashyam]

Hi,

I have built the kernel, uboot, xloader, Android FS as per the release notes

http://www.omappedia.org/wiki/4AJ.2.3_OMAP4_Jelly_Bean_Release_Notes

for Android JB 4.2 for Blaze Tablet (GP).

Flashing the images via fastboot goes fine. However when the blaze tablet

reboots it says following:

Texas Instruments Inc X-Loader 1.41.0-gdd880470 (Feb 26 2013 - 19:16:27)

Starting OS Bootloader from EMMC ...


U-Boot 1.1.4-g2af35fca (Feb 26 2013 - 19:29:58)

Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB

Using default environment

In: serial
Out: serial
Err: serial

efi partition table:
ptbl slot: EMMC:(1).
256 128K xloader
512 256K bootloader
1024 128K misc
204
8 16M efs
34816 16K crypto
34848 8M recovery
51232 8M boot
67616 512M system
1116192 256M cache
1640480 29630M userdata

Net: KS8851SNL
Hit any key to stop autoboot: 3
\0x08\0x08\0x08 2
\0x08\0x08\0x08 1
\0x08\0x08\0x08 0

kernel @ 80308000 (4671984)
ramdisk @ 81300000 (185343)


Starting kernel ...

Uncompressing Linux...
done, booting the kernel.



Texas Instruments Inc X-Loader 1.41.0-gdd880470 (Feb 26 2013
- 19:16:27)

Starting OS Bootloader from EMMC ...


U-Boot 1.1.4-g2af35fca (Feb 26 2013 - 19:29:58)

Load address: 0x80e80000
DR
AM: 1024 MB
Flash: 0 kB
Using default environment

In: serial
Out: serial
Err: serial

efi partition table:
ptbl slot: EMMC:(1).
256 128K xloader
512
256K bootloader
1024 128K misc
2048 16M efs
34816 16K crypto
34848 8M recovery
51232 8M boot
67616 512M system
1116192 256M cache
1640480 29630M userdata

Net: KS8851SNL

reboot command
[\0xe9\0xf6^]\0xd6\0xed\0xee\0xfe\0x80Yx\0x1d\0x84\0x83\0x14\0xdc\0xc9S

\0xb4\0x81\0xcaR\0x06H\0xa5\0xc1?\0xb1\0xb7V\0xe9\\0xcbR\0xcdd\0x9d\0x9b!

\0xefw9?\0xd5\0xab*-\0xcb"?\0xf9\0x84e\0xbd\0xaf\0xb4

\0xf8\0x02\0x18\0x0c\0xb6\0xd3]\0x04\0xc1\0xe4,gL\0x9e\0xae\0xa6\0xec\0xae\0xb2%

\0xfa\0x81\0xf5\0xbf\0xbcr\0x95\0xc5\0x1fW}\0xba%\0xf9\0x84\0xf0\0x80D+

\0xc2\0xb5\0xbe\0x85\0xf6\0xf0\0xaf\0xd3~\0x14\0xb2\0x05\0xa5\0xb2\0x94

\0xb4\0x1b\0xd7\0xd9\0x80K\0x01U\0xafw\0xe8\0x0c\0xa77\0xd7.\0x16L\0x08\0xf2

\0x18f\0x99\0xa2\0xc4m\0xa4I1(s\0xf3\0x868\0xe9\0x13\0xcd\0xbd\0x1f`\0x96-

\0xa9\0xf4c\0x83\0x15hj\0xd3\0xb9\0xe6c\0x85\0x83\0xcd\0xa8\0xc9X\0x8a?5

\0xc4\0xcd\0xb5\0x9f\0xfb\0xcd\0xbc#oi{]Z\0x82\0xa0\0xe4q-|\0xab\0xdb\0xa2x6

\0x95\0xaf\0xa1Nf\0x17O\0x12\0xc4=\0x94Lt\0x0e\0x05Y9%\0x09\0xc1\0xb5\0xec\0xf5Z

\\0x033W\0xe7k\0x19\0x9e9\0xf68\0x92\0xc3[\0xaa\0x1a{\0xbb0\0xf7\0xb0\0xa3\0xf4

\0xba\0xe5\0xc0\0xa4\0xe1:\0x1a

\\0xb7CR[U\0xbf\0x02\0xf3\0x95\0x0c\0xe1\0xbc0\0xa8\0xb2\0xb7u\0xcd\0xe4W\0x99!q

\0xd4+@f\0x02%]\0xf9\0xb9/S\0xd6\0xa5\0xc1\0xce\0x865\0xca\0xdc\0xeb\0xb1\0x8d]

\0xb6\0xaam\0x84Z\0x1dL\0xd7\0xcfo\0x07P_G\\0x96-\0xd0\0x08\0x14@\0xa6\0xaf

\0xa2&>x\0x7f\0xee\0xf2\0xc1\0x1d\0xd0

\0xa3\0x05,\0xc4\0x1d\0xe0\0xa4\0xe7\0x99\0x9a\0xae\0xdc\0xe0\0x1c\0x7f

\0xde\0xf0\0x0f\0x11J\0xf5\0x0f\0xe49S\0xe2\0xbfm\0xda\0xbb\0xe3n\0xb7\0xa3

\0xd5X\0xa8V\0xa5\0xeab\0xac+\0xc0\0x91]

undefined instruction
pc : [<219957e8>] lr : [<219957e4>]
sp : 80e3fef8 ip : 00000000 fp : 0002ffd0

r10: 80e80000 r9 : 12345678 r8 : 80e3ffdc

r7 : 80e80320 r6 : 80e3ffbd r5 : 00000006 r4 : 4a31c000

r3 : 00000020 r2 : 80eae84c r1 : 00000000 r0 : 00000000

Flags: nZCv IRQs off FIQs off Mode SVC_32

Resetting CPU ...


and loops on rebooting.

Please let me know if this issue has been faced earlier and let me know of any

solution for the same.

Thanks,
Regards,
Narasimha