Hi everyone,

I'm trying to load a new kernel since I made some changes.

So after I save my new configurations (make config) I compile it (make)

then on a separate teminal window I set up picocom and boot my leopard board. I stop it before autoboot completes.

picocom v1.4

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
escape is      : C-a
noinit is      : no
noreset is     : yes
nolock is      : yes
send_cmd is    : ascii_xfr -s -v -l10
receive_cmd is : rz -vv

Terminal ready
DM36x initialization passed!
UBL customized by RidgeRun
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000004.
   DONE
Jumping to entry point at 0x81080000.

U-Boot customized by RidgeRun


U-Boot 1.3.4-svn66 (Nov 27 2010 - 20:05:46)

I2C:   ready
DRAM:  128 MB
NAND:  NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Bad block table not found for chip 0
Bad block table not found for chip 0
nand_bbt: Error while writing bad block table -5
256 MiB
In:    serial
Out:   serial
Err:   serial
Ethernet PHY: GENERIC @ 0x00
Hit any key to stop autoboot:  0
DM365 LEOPARD # 
Skipping tty reset...
Thanks for using picocom


==============================================

Now I go to the first terminal window and run make install and it seems to work but it stops arbitrarily.   in the paste below I seemed to get pretty far until it got stuck yet again.

Any ideas on what I need to do?

also any ideas why my leopardboard prompt ends with a # instead of a :> ?

 

Below is the last attempt at loading the kernel.

:~/work/leo365$ make install
  Ridgerun Linux SDK
  Board configuration: Leopard Board DM365

   Installation system of uboot images over serial port /dev/ttyUSB0
  Please be sure u-boot is running on port /dev/ttyUSB0 and none process (like minicom) is using it
  u-boot port /dev/ttyUSB0

  Performing handshake with u-boot...  Trying to identify NAND block size... detected 0x20000


  Verifying if file system needs to be installed...
  File system doesn't needs to be loaded

  Verifying if kernel command line needs to be installed...
  Kernel command line doesn't need to be installed

  Verifying if the boot command needs to be installed...
  Boot command doesn't need to be installed
  Verifying if kernel needs to be installed...
  Loading Kernel image...
     Uboot <= loady 0x82000000
Sending: kernel.uImage
Ymodem sectors/kbytes sent: 29095/3636kRetry 0: Timeout on sector ACK
Retry 0: Timeout on sector ACK