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.

OMAP3530 and AMDM37xx Boot device driver Init call failed

Hi I am trying load EBOOT from nadflash with help of received demo files with EVM board.

Currently I am using flash tool and OMAP35xx-nand.raw files to flash EBOOT files in to OMAP3530 board.

boot loader is writing is successful.

but while running boot loader I am facing Error (ERROR: Boot device driver Init call failed)

serial log as fallow:

  

Texas Instruments Windows CE NAND X-Loader for EVM 3730
Built Mar  8 2017 at 11:41:36
Version BSP_WINCE_ARM_A8 3.00.00.01
..
Jumping to bootloader

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Mar  8 2017 11:
39:49

Texas Instruments Windows CE EBOOT for OMAP35xx/37xx, Built Mar  8 2017 at 11:41
:31
EBOOT Version 0.0, BSP BSP_WINCE_ARM_A8 3.00.00.01

TI OMAP3730 Version 0x00000012 (ES1.2)
TPS659XX Version 0x30 (ES1.3)
System ready!
Preparing for download...
INFO: Predownload....
Checking bootloader blocks are marked as reserved (Num = 494)

WARN: Boot config wasn't found, using defaults
INFO: SW4 boot setting: 0x35
IsValidMBR: MBR sector = 0x7b80 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.

>>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<

Hit space to enter configuration menu 5...
Hit space to enter configuration menu 4...
Hit space to enter configuration menu 3...
Hit space to enter configuration menu 2...
Hit space to enter configuration menu 1...
OALFlashStoreOpen: 4096 blocks, 64 sectors/block
OALFlashStoreOpen: 2048 bytes/sector, 494 reserved blocks
Link not detected!!  Aborting
ERROR: Boot device driver Init call failed

--------------------------------------------------------------------------------
 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: 1

 Main:
  Boot device:   LAN9115 MAC
  Debug device:  LAN9115 MAC
  Retail Msgs:   disabled
  Device ID:     0
  Display Res:   LCD  480x640 60Hz
  Flashing NK.bin:   enabled
  OPP Mode:   MPU[1000Mhz @ 1.375V], IVA2[800Mhz @ 1.375V]

 Network:
  KITL state:    enabled
  KITL type:     active
  KITL mode:     interrupt
  DHCP:          enabled
  IP address:    0.0.0.0
  IP mask:       0.0.0.0
  IP router:     0.0.0.0
  Eth MAC Addr:  da:00:00:00:00:00 (EEPROM)
  VMINI:         enabled
  Note: USBFN RNDIS MAC Addr cannot be changed.

--------------------------------------------------------------------------------
 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: 4

--------------------------------------------------------------------------------
 Network Settings
--------------------------------------------------------------------------------
 [1] Show Current Settings
 [2] Enable/disable KITL
 [3] KITL interrupt/poll mode
 [4] KITL Active/Passive mode
 [5] Enable/disable DHCP
 [6] Set IP address
 [7] Set IP mask
 [8] Set default router
 [9] Enable/disable VMINI
 [a] Set MAC address
 [0] Exit and Continue

 Selection: 1

 Network:
  KITL state:    enabled
  KITL type:     active
  KITL mode:     interrupt
  DHCP:          enabled
  IP address:    0.0.0.0
  IP mask:       0.0.0.0
  IP router:     0.0.0.0
  Eth MAC Addr:  da:00:00:00:00:00 (EEPROM)
  VMINI:         enabled
  Note: USBFN RNDIS MAC Addr cannot be changed.

please provide the support to get it working.

Thanks

Rupesh