AM335x EVM won't boot: killed by signal 1?

Laurens Miers

Hi all,

I'm a student trying to set up the AM335x EVM for linux development. I ran the create-sdcard.sh script to use pre-build images and after that i ran the setup.sh script.

I'm trying to boot from SD, all goes well until the final step: when U-boot is writing to NAND it says:

writing to NAND..... done

but then it says "killed by signal 1" , "hanging up".

I ignored this at first and tried to boot from SD but when the kernel boots it just randomly stops after some time, sometimes it goes pretty far in the process of booting the kernel, and sometimes it stops after 1 second. I don't know but could this be because of the "killed by signal 1" when i ran the setup script?

I don't know if these problems are related but when i tried accessing the u-boot prompt when it says " hit any key to stop autoboot" i can stop the autoboot and i see the prompt "#U-boot" but i can't enter anything from the keyboard.

I can't seem to find anything related to my problem on the forum, please correct me if i'm wrong.

any help would be greatly appreciated.

over 11 years ago

0 Miroslav Kiradzhiyski XID over 11 years ago

TI__Mastermind 25235 points

Hi,

Please provide the whole log from running the scripts and experiencing the hangup signal error (please attach it as a text file).

Best regards,
Miroslav

0 Laurens Miers over 11 years ago in reply to Miroslav Kiradzhiyski XID

Intellectual 640 points

here are the logs:

running the setup.sh script:

Fullscreen 1464.setupLog.txt Download

-------------------------------------------------------------------------------
TISDK setup script
This script will set up your development host for SDK development.
Parts of this script require administrator priviliges (sudo access).
-------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Verifying Linux host distribution
Ubuntu 10.04 LTS or Ubuntu 12.04 LTS is being used, continuing..
--------------------------------------------------------------------------------

Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group.
A user must be apart of this group to have the proper permissions to access a serial device.

Are you running this script using sudo? The detected username is 'root'.
Verify and enter your Linux username below

User 'root' is already apart of the 'dialout' group

-------------------------------------------------------------------------------
setup package script
This script will make sure you have the proper host support packages installed
This script requires administrator priviliges (sudo access) if packages are to be installed.
-------------------------------------------------------------------------------
System has required packages!
--------------------------------------------------------------------------------
Package verification and installation successfully completed
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will extract the target filesystem to /home/myrmidon132/ti-sdk-am335x-evm-06.00.00.00/targetNFS

Note! This command requires you to have administrator priviliges (sudo access) 
on your host.
/home/myrmidon132/ti-sdk-am335x-evm-06.00.00.00/targetNFS already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
Old /home/myrmidon132/ti-sdk-am335x-evm-06.00.00.00/targetNFS removed

Successfully extracted tisdk-rootfs-image-am335x-evm.tar.gz to /home/myrmidon132/ti-sdk-am335x-evm-06.00.00.00/targetNFS
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the SDK to install binaries in to:
    /home/myrmidon132/ti-sdk-am335x-evm-06.00.00.00/targetNFS/home/root/am335x-evm

The files will be available from /home/root/am335x-evm on the target.

This setting can be changed later by editing Rules.make and changing the
EXEC_DIR or DESTDIR variable (depending on your SDK).

Rules.make edited successfully..
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will export your target filesystem for NFS access.

Note! This command requires you to have administrator priviliges (sudo access) 
on your host.
/home/myrmidon132/ti-sdk-am335x-evm-06.00.00.00/targetNFS already NFS exported, skipping..

 * Stopping NFS kernel daemon
   ...done.
 * Unexporting directories for NFS kernel daemon...
   ...done.
 * Exporting directories for NFS kernel daemon...
   ...done.
 * Starting NFS kernel daemon
   ...done.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Which directory do you want to be your tftp root directory?(if this directory does not exist it will be created for you)
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the tftp server in the /tftpboot directory.

Note! This command requires you to have administrator priviliges (sudo access) 
on your host.

/tftpboot already exists, not creating..

/tftpboot/uImage-am335x-evm.bin already exists. The existing installed file can be renamed and saved under the new name.
(r) rename (o) overwrite (s) skip copy 

Successfully overwritten uImage-am335x-evm.bin in tftp root directory /tftpboot

/etc/xinetd.d/tftp already exists..
/tftpboot already exported for TFTP, skipping..

Restarting tftp server
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xinetd stop

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the stop(8) utility, e.g. stop xinetd
xinetd stop/waiting
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service xinetd start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start xinetd
xinetd start/running, process 14380
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------"
This step will set up minicom (serial communication application) for
SDK development


For boards that contain a USB-to-Serial converter on the board such as:
	* BeagleBone
	* AM335x EVM-SK
	* OMAP5 uEVM

the port used for minicom will be automatically detected. By default Ubuntu
will not recognize this device. Setup will add a udev rule to
/etc/udev/ so that from now on it will be recognized as soon as the board is
plugged in.

For other boards, the serial will defualt to /dev/ttyS0. Please update based
on your setup.

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


NOTE: For boards with a built-in USB to Serial adapter please press
      ENTER at the prompt below.  The correct port will be determined
      automatically at a later step.  For all other boards select
      the serial port that the board is connected to
Which serial port do you want to use with minicom?

Copied existing /home/myrmidon132/.minirc.dfl to /home/myrmidon132/.minirc.dfl.old

Configuration saved to /home/myrmidon132/.minirc.dfl. You can change it further from inside
minicom, see the Software Development Guide for more information.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
This step will set up the u-boot variables for booting the EVM.
Becuase the not all AM335x devices have a NAND, the u-boot variables will
be stored in uEnv.txt on the boot partition. U-boot will read this
file on boot.

Autodetected the following ip address of your host, correct it if necessary

Select Linux kernel location:
 1: TFTP
 2: SD card


Select root file system location:
 1: NFS
 2: SD card

--------------------------------------------------------------------------------
Would you like to create a minicom script with the above parameters (y/n)?

Successfully wrote /home/myrmidon132/ti-sdk-am335x-evm-06.00.00.00/bin/setupBoard.minicom
Would you like to run the setup script now (y/n)? This requires you to connect
the RS-232 cable between your host and EVM as well as your ethernet cable as
described in the Quick Start Guide. Once answering 'y' on the prompt below
you will have 300 seconds to connect the board and power cycle it
before the setup times out

After successfully executing this script, your EVM will be set up. You will be 
able to connect to it by executing 'minicom -w' or if you prefer a windows host
you can set up Tera Term as explained in the Software Developer's Guide.
If you connect minicom or Tera Term and power cycle the board Linux will boot.

[!p[?3;4l[4l>[0m(B[?1h=[H[2J[?12l[?25h
Welcome to minicom 2.5

OPTIONS: I18n 
Compiled on May  2 2011, 10:05:24.
Port /dev/ttyUSB0

Press CTRL-A Z for help on special keys

bigger 50[11;10H
U-Boot SPL 2013.01.01 (Jun 25 2013 - 16:42:52)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO [14;1HRx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0 
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO [20;1HRx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0 
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
[23;80H [24;1HOMAP SD/MMC: 0
[23;80H [24;1Hreading u-boot.img
[23;80H [24;1Hreading u-boot.img
[23;80H [24;1H
[23;80H [24;1H
[23;80H [24;1HU-Boot 2013.01.01 (Jun 25 2013 - 16:42:52)
[23;80H [24;1H
[23;80H [24;1HI2C:   ready
[23;80H [24;1HDRAM:  512 MiB
[23;80H [24;1HWARNING: Caches not enabled
[23;80H [24;1HNAND:  256 MiB
[23;80H [24;1HMMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
[23;80H [24;1Hmusb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO
[23;80H [24;1HRx, HB-ISO Tx, SoftConn)
[23;80H [24;1Hmusb-hdrc: MHDRC RTL version 2.0 
[23;80H [24;1Hmusb-hdrc: setup fifo_mode 4
[23;80H [24;1Hmusb-hdrc: 28/31 max ep, 16384/16384 memory
[23;80H [24;1HUSB Peripheral mode controller at 47401000 using PIO, IRQ 0
[23;80H [24;1Hmusb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO
[23;80H [24;1HRx, HB-ISO Tx, SoftConn)
[23;80H [24;1Hmusb-hdrc: MHDRC RTL version 2.0 
[23;80H [24;1Hmusb-hdrc: setup fifo_mode 4
[23;80H [24;1Hmusb-hdrc: 28/31 max ep, 16384/16384 memory
[23;80H [24;1HUSB Host mode controller at 47401800 using PIO, IRQ 0
[23;80H [24;1HNet:   cpsw, usb_ether
[23;80H [24;1HHit any key to stop autoboot: 0 
[23;80H [24;1HU-Boot#setenv ip_method none
[23;80H [24;1HU-Boot#setenv bootfile uImage
[23;80H [24;1HU-Boot#bigger 100
[23;80H [24;18Hsetenv bootcmd 'mmc rescan 0; run loaduimagefat; run mmcboot'
[23;80H [24;1HU-Boot#saveenv
[23;80H [24;1HSaving Environment to NAND...
[23;80H [24;1HErasing Nand...
[23;80H [24;1HErasing at 0x260000 -- 100% complete.
[23;80H [24;1HWriting to Nand... done
[23;80H [24;1HU-Boot#[8;28H[?25l+-------------------------+[9;28H|                         |[10;28H|  Killed by signal 1 !   |[11;28H|                         |[12;28H+-------------------------+[11;29H[?25l[?12l[?25h[8;1HRx, HB-ISO Tx, SoftConn)                              [9;1Hmusb-hdrc: MHDRC RTL version 2.0                      [10;1Hmusb-hdrc: setup fifo_mode 4                          [11;1Hmusb-hdrc: 28/31 max ep, 16384/16384 memory           [12;1HUSB Host mode controller at 47401800 using PIO, IRQ 0 [24;8H[8;33H[?25l+---------------+[9;33H|               |[10;33H|  Hanging up   |[11;33H|               |[12;33H+---------------+[10;46H[?25l[?12l[?25h[8;1HRx, HB-ISO Tx, SoftConn)                         [9;1Hmusb-hdrc: MHDRC RTL version 2.0                 [10;1Hmusb-hdrc: setup fifo_mode 4                     [11;1Hmusb-hdrc: 28/31 max ep, 16384/16384 memory      [12;1HUSB Host mode controller at 47401800 using PIO, I[24;8H[H[2J[?12l[?25h[?1l>[!p[?3;4l[4l>/home/myrmidon132/ti-sdk-am335x-evm-06.00.00.00
You can manually run minicom in the future with this setup script using: minicom -S ./bin/setupBoard.minicom
--------------------------------------------------------------------------------
-------------------------------------------------------------------------------
TISDK setup completed!
Please continue reading the Software Developer's Guide for more information on
how to develop software on the EVM
-------------------------------------------------------------------------------

and here is a printscreen of the "killed by signal 1":

and starting the evm:

Fullscreen 0743.log.txt Download

U-Boot SPL 2013.01.01 (Jun 25 2013 - 16:42:52)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO                                                                                                                                                                                              Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO                                                                                                                                                                                              Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2013.01.01 (Jun 25 2013 - 16:42:52)

I2C:   ready
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  256 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO                                                                                                                                                                                              Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO                                                                                                                                                                                              Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net:   cpsw, usb_ether
Hit any key to stop autoboot:  0
reading uImage
3194336 bytes read in 363 ms (8.4 MiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.2.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3194272 Bytes = 3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Linux version 3.2.0 (jenkins@sdit-build02) (gcc version 4.7.3 201                                                                                                                                                                                             30226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC                                                                                                                                                                                              2013.03) ) #1 Tue Jun 25 16:40:47 CDT 2013
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instructio                                                                                                                                                                                             n cache
[    0.000000] Machine: am335xevm
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] AM335X ES1.0 (sgx neon )
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pag                                                                                                                                                                                             es: 130048
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 r                                                                                                                                                                                             o rootfstype=ext3 rootwait ip=none
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 512MB = 512MB total
[    0.000000] Memory: 513168k/513168k available, 11120k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0598000   (5696 kB)
[    0.000000]       .init : 0xc0598000 - 0xc05d3000   ( 236 kB)
[    0.000000]       .data : 0xc05d4000 - 0xc063e430   ( 426 kB)
[    0.000000]        .bss : 0xc063e454 - 0xc066d224   ( 188 kB)
[    0.000000] NR_IRQS:396
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrup                                                                                                                                                                                             ts
[    0.000000] Total of 128 interrupts on 1 active controller
[    0.000000] OMAP clockevent source: GPTIMER2 at 19200000 Hz
[    0.000000] OMAP clocksource: GPTIMER1 at 32768 Hz
[    0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 13                                                                                                                                                                                             1071999ms
[    0.000000] Console: colour dummy device 80x30
[    0.000122] Calibrating delay loop... 574.66 BogoMIPS (lpj=2873344)
[    0.094970] pid_max: default: 32768 minimum: 301
[    0.095123] Security Framework initialized
[    0.095214] Mount-cache hash table entries: 512
[    0.095581] CPU: Testing write buffer coherency: ok
[    0.113922] omap_hwmod: pruss: failed to hardreset
[    0.115081] print_constraints: dummy:
[    0.115447] NET: Registered protocol family 16
[    0.117553] OMAP GPIO hardware version 0.1
[    0.120208] omap_mux_init: Add partition: #1: core, flags: 0
[    0.122131]  omap_i2c.1: alias fck already exists
[    0.123016]  omap2_mcspi.1: alias fck already exists
[    0.123229]  omap2_mcspi.2: alias fck already exists
[    0.124145]  edma.0: alias fck already exists
[    0.124176]  edma.0: alias fck already exists
[    0.124176]  edma.0: alias fck already exists
[    0.150817] bio: create slab <bio-0> at 0
[    0.153076] SCSI subsystem initialized
[    0.154693] usbcore: registered new interface driver usbfs
[    0.154998] usbcore: registered new interface driver hub
[    0.155181] usbcore: registered new device driver usb
[    0.155487] registerd cppi-dma Intr @ IRQ 17
[    0.155487] Cppi41 Init Done Qmgr-base(e087a000) dma-base(e0878000)
[    0.155517] Cppi41 Init Done
[    0.155548] musb-ti81xx musb-ti81xx: musb0, board_mode=0x13, plat_mode=0x3
[    0.155822] musb-ti81xx musb-ti81xx: musb1, board_mode=0x13, plat_mode=0x1
[    0.156982] omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz
[    0.158721] tps65910 1-002d: JTAGREVNUM 0x0
[    0.160705] print_constraints: VRTC:
[    0.161895] print_constraints: VIO: at 1800 mV
[    0.163726] print_constraints: VDD1: 600 <--> 1500 mV at 1262 mV normal
[    0.165527] print_constraints: VDD2: 600 <--> 1500 mV at 1137 mV normal
[    0.166320] print_constraints: VDD3: 5000 mV
[    0.167480] print_constraints: VDIG1: at 1800 mV
[    0.168609] print_constraints: VDIG2: at 1800 mV
[    0.169738] print_constraints: VPLL: at 1800 mV
[    0.170898] print_constraints: VDAC: at 1800 mV
[    0.172058] print_constraints: VAUX1: at 1800 mV
[    0.173187] print_constraints: VAUX2: at 3300 mV
[    0.174346] print_constraints: VAUX33: at 3300 mV
[    0.175476] print_constraints: VMMC: at 3300 mV
[    0.175964] tps65910 1-002d: No interrupt support, no core IRQ
[    0.177368] Advanced Linux Sound Architecture Driver Version 1.0.24.
[    0.178527] Switching to clocksource gp timer
[    0.193878] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    0.194061] musb-hdrc musb-hdrc.0: dma type: dma-cppi41
[    0.194396] MUSB0 controller's USBSS revision = 4ea20800
[    0.195343] musb-hdrc musb-hdrc.0: USB OTG mode controller at e083c000 using                                                                                                                                                                                              DMA, IRQ 18
[    0.195526] musb-hdrc musb-hdrc.1: dma type: dma-cppi41
[    0.195800] MUSB1 controller's USBSS revision = 4ea20800
[    0.196289] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[    0.196380] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus numbe                                                                                                                                                                                             r 1
[    0.196502] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.196533] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=                                                                                                                                                                                             1
[    0.196533] usb usb1: Product: MUSB HDRC host driver
[    0.196533] usb usb1: Manufacturer: Linux 3.2.0 musb-hcd
[    0.196563] usb usb1: SerialNumber: musb-hdrc.1
[    0.197387] hub 1-0:1.0: USB hub found
[    0.197418] hub 1-0:1.0: 1 port detected
[    0.197967] musb-hdrc musb-hdrc.1: USB Host mode controller at e083e800 using                                                                                                                                                                                              DMA, IRQ 19
[    0.198425] NET: Registered protocol family 2
[    0.198669] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.199005] TCP established hash table entries: 16384 (order: 5, 131072 bytes                                                                                                                                                                                             )
[    0.199279] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[    0.199462] TCP: Hash tables configured (established 16384 bind 16384)
[    0.199493] TCP reno registered
[    0.199493] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.199523] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.199707] NET: Registered protocol family 1
[    0.199981] RPC: Registered named UNIX socket transport module.
[    0.199981] RPC: Registered udp transport module.
[    0.200012] RPC: Registered tcp transport module.
[    0.200012] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.200256] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.221374] VFS: Disk quotas dquot_6.5.2
[    0.221435] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.222015] msgmni has been set to 1002
[    0.225189] alg: No test for stdrng (krng)
[    0.225891] io scheduler noop registered
[    0.225891] io scheduler deadline registered
[    0.225952] io scheduler cfq registered (default)
[    0.229431] omap_uart.0: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
[    0.866333] console [ttyO0] enabled
[    0.870605] omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
[    0.878417] omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
[    0.886199] omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
[    0.893981] omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
[    0.901763] omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
[    0.910003] omap4_rng omap4_rng: OMAP4 Random Number Generator ver. 2.00
[    0.926391] brd: module loaded
[    0.934478] loop: module loaded
[    0.937927] i2c-core: driver [tsl2550] using legacy suspend method
[    0.944396] i2c-core: driver [tsl2550] using legacy resume method
[    0.950836] at24 1-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.963104] Detected a daughter card on AM335x EVM..
[    0.968078] Unknown CPLD version found
[    0.972229] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.985412] Board name: A33515BB
[    0.988769] Board version: 1.2A
[    0.992065] SKU: SKU#01
[    0.995025] The board is general purpose EVM in profile 0
[    1.001922]  da8xx_lcdc.0: alias fck already exists
[    1.007446] da8xx_lcdc da8xx_lcdc.0: GLCD: Found TFC_S9700RTWV35TR_01B panel
[    1.030761] Console: switching to colour frame buffer device 100x30
[    1.046417] omap-gpmc omap-gpmc: GPMC revision 6.0
[    1.051452] Registering NAND on CS0
[    1.055816]  omap_i2c.2: alias fck already exists
[    1.061126] omap_i2c omap_i2c.2: bus 2 rev2.4.0 at 100 kHz
[    1.067565] tsl2550 2-0039: standard operating mode
[    1.073242] tsl2550 2-0039: support ver. 1.2 enabled
[    1.079071]  davinci-mcasp.1: alias fck already exists
[    1.084930]  omap_hsmmc.0: alias fck already exists
[    1.090362]  omap_hsmmc.2: alias fck already exists
[    1.095733] Configure Bluetooth Enable pin...
[    1.103240] registered am33xx_sr device
[    1.107482] _regulator_get: 2-0018 supply Vdd not found, using dummy regulato                                                                                                                                                                                             r
[    1.115112] _regulator_get: 2-0018 supply Vdd_IO not found, using dummy regul                                                                                                                                                                                             ator
[    1.139404] lis3lv02d: 8 bits 3DLH sensor found
[    1.229553] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d                                                                                                                                                                                             /input/input0
[    1.241271] mtdoops: mtd device (mtddev=name/number) must be supplied
[    1.248565] omap2-nand driver initializing
[    1.253204] No NAND device found
[    1.256774] No NAND device found
[    1.260345] OneNAND driver initializing
[    1.265655] CAN device driver interface
[    1.269683] CAN bus driver for Bosch D_CAN controller 1.0
[    1.319183] davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
[    1.325622] davinci_mdio davinci_mdio.0: detected phy mask fffffffe
[    1.332977] davinci_mdio.0: probed
[    1.336517] davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
[    1.344207] usbcore: registered new interface driver zd1201
[    1.350219] usbcore: registered new interface driver cdc_ether
[    1.356445] usbcore: registered new interface driver cdc_eem
[    1.362518] usbcore: registered new interface driver dm9601
[    1.368377] cdc_ncm: 04-Aug-2011
[    1.371917] usbcore: registered new interface driver cdc_ncm
[    1.377838] Initializing USB Mass Storage driver...
[    1.383117] usbcore: registered new interface driver usb-storage
[    1.389404] USB Mass Storage support registered.
[

As i said earlier, here it stops working at "USB Mass Storage support registered." but it just randomly stops around this area.

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Laurens Miers

TI__Mastermind 25235 points

Hi,

Judging by the screenshot, the "Killed by signal 1!" message is overwriting the messages from the serial console meaning that this message is most probably coming from the host system. Also U-Boot doesn't have "signals" to kill processes - it's a kernel thing and the kernel hasn't started yet on the beaglebone, so the message should be coming from the host system kernel. Signal 1 is SIGHUP (hang up), so probably something went wrong with the minicom connection.

Please, next time the "Killed by signal 1!" message is displayed, exit the minicom and type this on your host PC:

dmesg | tail -20

then post the output here - if I'm right it should contain information on what went wrong with the minicom connection.

You can also try a different terminal emulator (picocom is very easy to use). Just type picocom -b 115200 /dev/ttyS0

Best regards,
Miroslav

0 Laurens Miers over 11 years ago in reply to Miroslav Kiradzhiyski XID

Intellectual 640 points

This is the output of dmesg | tail -20, i cleared dmesg before running the setup.sh script:

[ 1778.134511] nfsd: last server has exited, flushing export cache
[ 1780.462273] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 1780.462291] NFSD: starting 90-second grace period

Just a reminder, i'm using the EVM and not the beaglebone.

I tried using picocom but it was the same story.

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Laurens Miers

TI__Mastermind 25235 points

I just downloaded the minicom source code and the popup window showing the error message is generated from Minicom itself:

/*
* We've got the hangup or term signal.
*/
static void hangsig(int sig)
{
if (stdwin)
werror(_("Killed by signal %d !\n"), sig);
if (capfp)
fclose(capfp);

keyboard(KUNINSTALL, 0);
hangup();
modemreset();
leave("\n");
}

For some reason minicom is receiving a SIGHUP signal and the attached handler (shown above) is executed:

/* Signal handling */
signal(SIGHUP, hangsig);

The handler also stops the keyboard from sending anything to the serial connection, which explains why you are not able to type in anything.

This signal is issued by the host PC.

Please try the following without the need for a serial connection:
1. Connect your SD card to a card reader, run the create-sdcard.sh script located inside <sdk_folder>/bin/ and choose to have only 2 partitions and use the pre-built images included in the SDK.
2. Plug the SD card into the EVM slot and set the SYSBOOT swithes for SD card boot as shown here. (Please note that the SYSBOOT switches are labeled incorrectly - ON is on the wrong side.)
3. Power the board and wait for the LCD to show the Linux logo (note that the CPLD switch should be in a state which allows using the LCD - for example Profile 0).

This is the first time we encounter such an issue so I believe the EVM should boot just fine using the steps above and the problem is somewhere on the host PC, but I could be wrong. Please let me know about your progress so that I may investigate further.

Best regards,
Miroslav

0 Laurens Miers over 11 years ago in reply to Miroslav Kiradzhiyski XID

Intellectual 640 points

We connected the EVM to another computer, ran the scripts and tried what you suggested but encountered the same issue. We knew the EVM worked when running Android or Windows (we tested that a few weeks ago) but these failed to boot too now so our teachers examined the hardware. It turned out that some of the NAND memory was broken and maybe that's the reason for the signal 1.

We're going to wait for a new EVM to arrive and we will continue our research.

I would like to thank you Miroslav for the help and the thorough research you performed, it was very informative.

You'll continue to hear from us in future posts :).

0 Miroslav Kiradzhiyski XID over 11 years ago in reply to Laurens Miers

TI__Mastermind 25235 points

Hi,

Have you seen the AM335x GP EVM Pin Use Assignments spreadsheet? It can be downloaded from here (Pin Use Assignment). As you can see, in CPLD Profile #2 and CPLD Profile #3, the NAND pins are used for respectively MMC1 or NOR flash. You can try starting the EVM in one of these profiles to see if the error persists. Please note that the LCD won't work in Profile #3.

Best regards,
Miroslav

0 Laurens Miers over 11 years ago in reply to Miroslav Kiradzhiyski XID

Intellectual 640 points

Hi,

We investigated the profiles but it's no use. The NAND keeps behaving weird but we received our replacement yesterday and it worked fine.

Thanks for the information and help.

Processors

Processors forum

AM335x EVM won't boot: killed by signal 1?