Nand Boot, OS partition too small!

Mar 26, 2010 at 8:40 PM

Well i have finally got my build all designed the way i want with CE 6.0 R3, and I wanted to now boot NK.bin from the NAND. I first used EVMFlash to erase the nand and download TIEVM3530-nand.raw over serial to the board. Then, I booted ebootnand.nbo off the sd card (relabled as ebootsd.nb0, and used RNDIS to download the ebootnand.bin to the board using vs2005. So far so good... Finally, I attempted to use the RNDIS to download the NK.bin to the board and after downloading the image, received the following error off of the serial port:

BP_SetDataPointer at 0x33569c8

ERROR: OS partition too small! Aborting...

 

I realize my NK.bin is quite large (~52 mb or so, bulky, but suites my needs for now), but I was wondering how I can overcome this error. Thanks in advance for the advice.

Mar 29, 2010 at 8:08 AM

Turns out I'm learning more then i thought... I edited a few sections to specify the os partition size and poof, the situation is resolved...

Jan 24, 2012 at 10:05 AM

I am facing a problem while loading WEC7 on Beagleboard RevC3 using SD card. I used 3 files to load the image: MLO, ebootSD.nb0 and nk.bin.

Issue:

The Image is being loaded in RAM and the WinEC7 kernel starts to execute. But it gets stuck while loading 'mspart.dll'. I also tried using another beagleboard but the same problem arises.

Next I tried loading the Linux image (Angstrom) and it was loaded successfully. This confirmed that there is no problem with the board.

But the strange thing is that, I am getting the same problem with many of my backup images wich were working fine previously.

 

Following are the Debug messages:

 <> Record [ 218 ] dwRecAddr = 0x90d454a0, dwRecLen = 0x12434
 <> Record [ 219 ] dwRecAddr = 0x90d578d4, dwRecLen = 0x3b1b4
 <> Record [ 220 ] dwRecAddr = 0x90d92a88, dwRecLen = 0x20fd0
 <> Record [ 221 ] dwRecAddr = 0x90db3a58, dwRecLen = 0x25e308
 <> Record [ 222 ] dwRecAddr = 0x91011d60, dwRecLen = 0x1b820
 <> Record [ 223 ] dwRecAddr = 0x9102d580, dwRecLen = 0x54
rom_offset=0x0.
 <> Record [ 224 ] dwRecAddr = 0x9102d5d4, dwRecLen = 0x292c
 <> Record [ 225 ] dwRecAddr = 0x0, dwRecLen = 0x8c00de40
ImageStart = 0x8c000000, ImageLength = 0x502ff00, LaunchAddr = 0x8c00de40
Computing checksum: image start = 0xa0000000, len = 0x502ff00
Checksum = 0xfc71c4cc (0x502ff00 bytes)

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x8c000000  Length=0x502ff00  Name="" Target=RAM
ROMHDR at Address 8C000044h
Launch Windows CE image by jumping to 0xa000de40...

Windows CE Kernel for ARM (Thumb Enabled) Built on Oct  3 2011 at 19:02:23
ProcessorType=0c08  Revision=3 CpuId=0x411fc083
OEMAddressTable = 8c00dee0
CPU CP15 Control Register = 0xc5387f
CPU CP15 Auxiliary Control Register = 0xe3
Initializing VFP, FPSID=410330c1
--- High Performance Frequecy is 32768 khz---
NKStartup done, starting up kernel. nCpus = 1
Windows CE KernelInit
Error Reporting Memory Reserved, dump size = 0004b000
Booting Windows CE version 7.00 for (ARM)
OEMGetExtensionDRAM: *pMemoryStart = 0x84001000; *pMemoryLength = 0x47ff000
Memory Configuring: Total pages: 30470, Filesystem pages = 1190
Booting kernel with clean memory configuration:
Total Memory Sections:2
[0] (static): start: 910aa000, extension/attributes: 0000c000, length: 02f07000
[1] (static): start: 84001000, extension/attributes: 00012000, length: 047ff000
Scheduling the first thread.
PID:00400002 TID:00410002 PGPOOL: Reserved 768 pages for Loader pool
PID:00400002 TID:00410002 PGPOOL: Reserved 256 pages for File pool
PID:00400002 TID:00410002 OSAXST0: Platform Name = EVM3530
PID:00400002 TID:00410002 OSAXST1: >>> Loading Module 'kd.dll' (0xC040209C) at address 0xEFFE0000-0xEFFFE000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00410002 KD: Starting kernel debugger software probe (KdStub) - KD API version 27
PID:00400002 TID:00410002 OSAXST1: >>> Loading Module 'NK.EXE' (0x9108CAD0) at address 0x8C000000-0x8C046000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00410002 Message Queue support initialized, g_hMsgQHeap = c44c0010
PID:00400002 TID:00500002 OSAXST1: >>> Loading Module 'filesys.dll' (0xC0402D8C) at address 0xEFC70000-0xEFD3A000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00500002 OSAXST1: >>> Loading Module 'fsdmgr.dll' (0xC0402EC4) at address 0xEF7C0000-0xEF808000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00520002 FileSystem Starting - starting with clean file system
PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'romfsd.dll' (0xC0403538) at address 0xEFC60000-0xEFC67000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.locale.dll' (0xC0405B38) at address 0xEFDB0000-0xEFDF1000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00520002 Warning! Kernel DLL 'k.locale.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from inside DPID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.normalize.dll' (0xC0406000) at address 0xEFD60000-0xEFD80000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00520002 Warning! Kernel DLL 'k.normalize.dll' is registered for thread creation/deletion notification.  To improve performance if you dont need thread notifications call DisableThreadLibraryCalls from insidPID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'relfsd.dll' (0xC0406160) at address 0xEF840000-0xEF852000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'device.dll' (0xC0406628) at address 0xEF9B0000-0xEF9B5000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'devmgr.dll' (0xC0406760) at address 0xEF970000-0xEF9A4000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'k.ceddk.dll' (0xC0406898) at address 0xEE990000-0xEE9A1000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00520002 OSAXST1: >>> Loading Module 'pm.dll' (0xC0406A08) at address 0xEF920000-0xEF94E000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00A40006 OSAXST1: >>> Loading Module 'pmext.dll' (0xC0407F58) at address 0xEE910000-0xEE920000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00A40006 OSAXST1: >>> Loading Module 'bus.dll' (0xC040AEF0) at address 0xEE960000-0xEE971000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00A40006 InitializePMExtension: Can't find 'PmExtPath' key.
PID:00400002 TID:00A40006 OSAXST1: >>> Loading Module 'ccfgsvc.dll' (0xC040B880) at address 0xEEAE0000-0xEEB0D000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00A40006 OSAXST1: >>> Loading Module 'nand.dll' (0xC040BE20) at address 0xEE930000-0xEE950000 in Process 'NK.EXE' (0x9108CAD0)
PID:00400002 TID:00A40006 media contains 1 flash regions:
PID:00400002 TID:00A40006     Type=2, StartP=0x0, NumP=0x800, NumL=0x0, Sec/Blk=0x40, B/Blk=0x20000, Compact=4.
PID:00400002 TID:00A40006 media contains 0 reserved regions:
PID:00400002 TID:00A40006 FLASHDRV.DLL:BuildupMappingInfo() - Enter.
PID:00400002 TID:00A40006 DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\MUsbOtg\DllName) returned 2
PID:00400002 TID:00A40006 DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\MUsbOtg'
PID:00400002 TID:00880002 OSAXST1: >>> Loading Module 'mspart.dll' (0xC040C868) at address 0xEF7A0000-0xEF7B0000 in Process 'NK.EXE' (0x9108CAD0)

--------------------------------------------------------------

Has anyone encountered such error before??

 

Thanks,

kensas

 

Jan 7, 2013 at 1:31 PM

Hi I am also getting the same problem.

So how you resolved that problem.

What was the root cause for that.