• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 1438 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Windows Embedded Compact 7 AND OMAP3530

syam krishnan
Prodigy 30 points
Other Parts Discussed in Thread: OMAP3530

Hi ,

Iam trying to boot OMAP 3530 EVB Rev G .Using latest BSP from TI for Windows Embedded Compact 7 .

Able to load XLDRUART.nb0 and OMAP35xx-nand.raw to board using pserial.exe tool.Using EVM_3530 workspace/ demo images from TI  I am able to download nk.bin using ethernet download (Platform builder).Same failed to load when I tried to add IMGNAND =1 and made it as NAND image. 

Also in boot options there is no menu related to SD CARD boot.

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

 Select Boot Device

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

 [1] LAN9115 MAC

 [2] USBFn RNDIS

 [3] NK from NAND

 [0] Exit and Continue

 Selection (actual LAN9115 MAC):

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

Following are my log messages :

 

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

 Main Menu

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

 [1] Show Current Settings

 [2] Select Boot Device

 [3] Select KITL (Debug) Device

 [4] Network Settings

 [5] Flash Management

 [6] Set Device ID

 [7] Save Settings

 [8] Enable/Disable OAL Retail Messages

 [9] Select Display Resolution

 [a] Select OPP Mode

 [0] Exit and Continue

 

 Selection: 0

OALFlashStoreOpen: 2048 blocks, 64 sectors/block

OALFlashStoreOpen: 2048 bytes/sector, 14 reserved blocks

INFO: Boot device uses MAC 00:50:c2:7e:92:7c

INFO: *** Device Name EVM3530-37500 ***

InitDHCP():: Calling ProcessDHCP()

ProcessDHCP()::DHCP_INIT

Got Response from DHCP server, IP address: 3.204.38.92

 

ProcessDHCP()::DHCP IP Address Resolved as 3.204.38.92, netmask: 255.255.255.0

Lease time: 691200 seconds

Got Response from DHCP server, IP address: 3.204.38.92

No ARP response in 2 seconds, assuming ownership of 3.204.38.92

+EbootSendBootmeAndWaitForTftp

Sent BOOTME to 255.255.255.255

Packet has the following data:

  boot.bin[NULL]octet[NULL]blksize[NULL]1024[NULL]

TFTP packet could have 2 name/value pairs

Locked Down Link 1

Src IP 3.204.38.92 Port Dest IP 3.204.38.127 Port Default TFTP block size set to: 512 bytes

This TFTP packet contains 1 options.

We currently only look at the first and expect it to be BLKSIZE.

The packet's option name is blksize.

The option's value is 1024

with a value that is in range.

BLKSIZE will be adjusted to 1024.

EthDown::TFTPD_OPEN::boot.bin

An OACK packet is the proper acknowledgement

-EbootSendBootmeAndWaitForTftp

 

BL_IMAGE_TYPE_BIN

 

Download file information:

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

[0]: Address=0xc8000000  Length=0x0413822c  Save=0xa0000000

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

Download file type: 6

....................................................................................................................................................................................................................................................................................................................................................................rom_offset=0x40000000.

..ImageStart = 0xc8000000, ImageLength = 0x413822c, LaunchAddr = 0xc800dec0

 

Completed file(s):

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

[0]: Address=0xc8000000  Length=0x413822c  Name="" Target=FLASH

 

Writing NK image to OS partition

 

ROMHDR (pTOC = 0x8c133ad0) ---------------------

  DLL First           : 0x4001eee0

  DLL Last            : 0x43adf000

  Physical First      : 0x88000000

  Physical Last       : 0x8c13822c

  Num Modules         :        423

  RAM Start           : 0x8c140000

  RAM Free            : 0x8c159000

  RAM End             : 0x90000000

  Num Copy Entries    :          2

  Copy Entries Offset : 0x88939e24

  Prof Symbol Length  : 0x00000000

  Prof Symbol Offset  : 0x00000000

  Num Files           :        166

  Kernel Flags        : 0x00000000

  FileSys RAM Percent : 0x80808080

  Driver Glob Start   : 0x00000000

  Driver Glob Length  : 0x00000000

  CPU                 :     0x01c2

  MiscFlags           :     0x0002

  Extensions          : 0x880049f4

  Tracking Mem Start  : 0x00000000

  Tracking Mem Length : 0x00000000

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

 

IsValidMBR: MBR sector = 0x380 (valid MBR)

OpenPartition: Partition Exists=0x1 for part 0x20.

BP_SetDataPointer at 0x413822c

BP_SetDataPointer at 0x0

WriteData: Start = 0x0, Length = 0x413822c.

NK image written

ROMHDR at Address C8000044h

Got EDBG_CMD_JUMPIMG

Got EDBG_CMD_CONFIG, flags:0x0

 

Load NK image from flash memory

IsValidMBR: MBR sector = 0x380 (valid MBR)

OpenPartition: Partition Exists=0x1 for part 0x20.

BP_SetDataPointer at 0x0

 

ROMHDR (pTOC = 0x8c133ad0) ---------------------

  DLL First           : 0x4001eee0

  DLL Last            : 0x43adf000

  Physical First      : 0x88000000

  Physical Last       : 0x8c13822c

  Num Modules         :        423

  RAM Start           : 0x8c140000

  RAM Free            : 0x8c159000

  RAM End             : 0x90000000

  Num Copy Entries    :          2

  Copy Entries Offset : 0x88939e24

  Prof Symbol Length  : 0x00000000

  Prof Symbol Offset  : 0x00000000

  Num Files           :        166

  Kernel Flags        : 0x00000000

  FileSys RAM Percent : 0x80808080

  Driver Glob Start   : 0x00000000

  Driver Glob Length  : 0x00000000

  CPU                 :     0x01c2

  MiscFlags           :     0x0002

  Extensions          : 0x880049f4

  Tracking Mem Start  : 0x00000000

  Tracking Mem Length : 0x00000000

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

 

NK Image Loaded

Launch Windows CE image by jumping to 0xa0000000...

Here loading is stopped .
Also when I created my own workspace and tried ,its showing 

 Selection: 0
Init HW: controller RST
Please help me with your valuable suggestions regarding this.
Regards,
SAM

 

 

 

  • 0
    TI__Expert 5320 points

    We have identified the issue in bootloader causing NAND image to not work. The issue will be fixed in next release. For now, please do the following fix in EVM_OMAP3530\SRC\BOOTLOADER\EBOOT\flash.c

    Function: ReadFlashNK

    Change (at the end of function):

     g_eboot.launchAddress = IMAGE_WINCE_CODE_CA;  // Remove OALVAtoPA((UCHAR*)IMAGE_WINCE_CODE_CA);

    Rebuild bootloader and try loading NK from NAND.

    -Madhvi

  • 0 in reply to Madhvi
    Expert 2280 points

    Hi Madhvi,

    Is this problem is also applicable to WinCE 6 ?   I see

    g_eboot.launchAddress = OALVAtoPA((UCHAR*)IMAGE_WINCE_CODE_CA);

    in the flash.c that I have.

    Thanks,

    Luan

  • 0 in reply to Luan Le
    TI__Expert 5320 points

    Yes but in CE6 we have been lucky that we don't see the side-effect of this issue because NK.bin is in bank 1 where PA=VA. In CE7 we moved NK to bank 2 and for OMAP3530, PA!=VA for bank2. So in CE6 you wont see the side effect unless you change the memory map.

    -Madhvi

  • 0 in reply to Madhvi
    Intellectual 895 points

    Where will the Embedded Compact 7 release for OMAP3530 be published? From TI, or from Microsoft?
    I read something about the first weeks of August, is this correct?

    Will the next release be able to boot from SD Card?

  • 0 in reply to MGun
    Prodigy 30 points

    MGun,

     

    Current releases (pre release or demo) versions also support SD BOOT.

    Try following procedure:

     

    1. Set Omap35xx evb SW4 settings as follows.

               1-ON , 2-ON , 3-ON , 4-OFF ,5- OFF , 6-ON , 7-OFF , 8-OFF

     

    2.Use TI SDCard boot  utility to format and copy MLO and then EBOOTSD.nb0 .(From my experiance only some sd cards work for SD BOOT.Tried Sandisk 2GB cards but

    failed.Now using Transcend 1 GB.

    3.Copy NK.BIN also to SD card ,you can select " NK From SD CARD "option from BOOTLOADER MENU.

     


     

  • 0 in reply to syam krishnan
    Intellectual 895 points

    I am able to load the X-Loader and then the Eboot from SD Card.
    But after loading the NK.bin, the screen remains black. I guess this thread is related to my problem: http://e2e.ti.com/support/embedded/f/353/t/101668.aspx

    Hardware: TI Mistral EVM3530 Rev G

  • 0 in reply to MGun
    TI__Expert 5320 points

    Which BSP release are you using? Can you build NK.bin with KITL and kernel debugger enabled and check which driver is getting stuck on bootup?

    -Madhvi

  • 0 in reply to Madhvi
    Intellectual 895 points

    I am using the BSP which is shipped with the Microsoft Windows Embedded Compact 7 Installation DVD.