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.

Kernel build/boot issue on DM814x EVM.

Howdy.

I'm just getting started with the DM814x EVM and am having trouble rebuilding the kernel & basic demo software provided in the Mistral kit. My process was as follows:

  1. The default (SD) solution from the box boots and runs just fine.
  2. Enabled the NAND chip.
  3. Switched to booting the kernel from tftp and the filesystem from NFS based on  ezsdk_dm814x-evm_5_02_02_60. This too works fine (though, there are plenty of errors in the setup script that took a while to find and fix).
  4. Downloaded TI814X-LINUX-PSP-04.01.00.05 and built the kernel from the instructions provided here (http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_User_Guide#Compiling_Linux_Kernel). The build was successful without warnings.
  5. uImage moved from arch/arm/boot to my tftp root.
  6. Rebooted EVM and didn't get too far before seeing a fatal error which cascades into a list of related issues:

syslink: disagrees about version of symbol clk_set_rate
syslink: Unknown symbol clk_set_rate (err -22)
syslink: disagrees about version of symbol clk_get_rate
syslink: Unknown symbol clk_get_rate (err -22)
syslink: disagrees about version of symbol clk_disable
syslink: Unknown symbol clk_disable (err -22)
syslink: disagrees about version of symbol clk_enable
syslink: Unknown symbol clk_enable (err -22)
FATAL: Error inserting syslink (/lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko): Invalid argument

The entire log is here

U-Boot 2010.06 (Aug 30 2011 - 02:19:02)

TI8148-GP rev 2.1

ARM clk: 600MHz
DDR clk: 400MHz

DRAM:  2 GiB
Using default environment

The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is alr
eady flashed
Hit any key to stop autoboot:  0 
mmc1 is available
reading u-boot.bin

179200 bytes read
## Starting application at 0x80800000 ...


U-Boot 2010.06 (Aug 30 2011 - 02:14:50)

TI8148-GP rev 2.1

ARM clk: 600MHz
DDR clk: 400MHz

I2C:   ready
DRAM:  2 GiB
NAND:  HW ECC Hamming Code selected
256 MiB
                          .:;rrr;;.                   
                    ,5#@@@@#####@@@@@@#2,             
                 ,A@@@hi;;;r5;;;;r;rrSG@@@A,          
               r@@#i;:;s222hG;rrsrrrrrr;ri#@@r        
             :@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:      
            B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B     
           @@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@    
          @@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@   
         @@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@  
        G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G 
        @9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@ 
       X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X
       @#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@
       @A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@
       @&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@
       @#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@
       M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#
       :@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,
        @@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@ 
         @A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@  
         ;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@;  
          r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r   
           ,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,    
             B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H      
              .@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.       
                .A@@#5r;;;r;;;rrr;r:r#AsM@@H.         
                   ;&@@@@MhXS5i5SX9B@@@@G;            
                       :ihM#@@@@@##hs,                

Net:   <ethaddr> not set. Reading from E-fuse
Detected MACID:40:5f:c2:22:4c:de
cpsw
Hit any key to stop autoboot:  0 
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 192.168.1.89
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 192.168.1.138; our IP address is 192.168.1.89
Filename 'uImage-dm814x-evm.bin'.
Load address: 0x81000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ########################
done
Bytes transferred = 2449188 (255f24 hex)
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2449124 Bytes = 2.3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (chris@lucy) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-2
03) ) #2 Tue Oct 18 16:06:11 EDT 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
bootconsole [earlycon0] enabled
vram size = 52428800 at 0
reserved size = 52428800 at 0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 52224
Kernel command line: console=ttyO0,115200n8 rootwait rw mem=256M earlyprintk not
ifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs
 nfsroot=192.168.1.138:/home/ubuntu/targetfs ip=192.168.1.147:192.168.1.138:192.
168.1.1:255.255.255.0:DaVinci::off
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 206MB = 206MB total
Memory: 203424k/203424k available, 58720k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
    lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0037000   ( 188 kB)
      .text : 0xc0037000 - 0xc04a2000   (4524 kB)
      .data : 0xc04a2000 - 0xc04e5140   ( 269 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy: 
NET: Registered protocol family 16
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 4
registered ti814x_vpss device
registered TI814x on-chip HDMI device
pm_dbg_init: only OMAP3 supported
Registered ti81xx_fb device
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d080c000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d081e800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 397
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst 
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x00000cee0000 : "File System"
0x00000cee0000-0x000010000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffc
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0x
bf900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
  #0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Detected MACID=0:0:0:0:0:0
ata1: SATA link down (SStatus 0 SControl 300)
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB 
 mmcblk0: p1 p2 p3
usb 2-1: new low speed USB device using musb-hdrc and address 2
usb 2-1: New USB device found, idVendor=04f3, idProduct=0234
usb 2-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 2-1: Product: OM
input: OM as /devices/platform/musb-ti81xx.1/musb-hdrc.1/usb2/2-1/2-1:1.0/input/
input0
generic-usb 0003:04F3:0234.0001: input: USB HID v1.11 Mouse [OM] on usb-musb-hdr
c.1-1/input0

CPSW phy found : id is : 0x4dd074
IP-Config: Complete:
     device=eth0, addr=192.168.1.147, mask=255.255.255.0, gw=192.168.1.1,
     host=DaVinci, domain=, nis-domain=(none),
     bootserver=192.168.1.138, rootserver=192.168.1.138, rootpath=
PHY: 0:00 - Link is Up - 100/Full
VFS: Mounted root (nfs filesystem) on device 0:14.
devtmpfs: mounted
Freeing init memory: 188K
INIT: version 2.86 booting
Error opening /dev/fb0: No such file or directory
Please wait: booting...
Starting udev
udevd (79): /proc/79/oom_adj is deprecated, please use /proc/79/oom_score_adj in
stead.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.
EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
ISOFS: Unable to identify CD-ROM format.
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is rec
ommended
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is rec
ommended
EXT3-fs (mmcblk0p3): using internal journal
EXT3-fs (mmcblk0p3): recovery complete
EXT3-fs (mmcblk0p3): mounted filesystem with writeback data mode
Root filesystem already rw, not remounting
Caching udev devnodes
Populating dev cachemv: cannot rename '/tmp/devices': No such file or directory
NET: Registered protocol family 10
ALSA: Restoring mixer settings...
NOT configuring network interfaces: / is an NFS mount
No state is present for card EVM
Found hardware: "" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card EVM
hwclock: can't open '/dev/misc/rtc': No such file or directory
Thu Sep  8 17:37:00 UTC 2011
hwclock: can't open '/dev/misc/rtc': No such file or directory
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
        PRCM for IVHD0 is in Progress, Please wait.....  
                        BW Phy Addr : 0x48180600 Data : 0x00000002
                        AW Phy Addr : 0x48180600 Data : 0x00000002
                        Phy Addr : 0x48180c04 Data : 0x00000037
                        BW Phy Addr : 0x48180620 Data : 0x00070000
                        AW Phy Addr : 0x48180620 Data : 0x00070002
                        BW Phy Addr : 0x48180624 Data : 0x00030000
                        AW Phy Addr : 0x48180624 Data : 0x00010002
                        Phy Addr : 0x48180600 Data : 0x00000102
                        BW Phy Addr : 0x48180c10 Data : 0x00000007
                        AW Phy Addr : 0x48180c10 Data : 0x00000003
                        Phy Addr : 0x48180c14 Data : 0x00000004
                        BW Phy Addr : 0x58088000 Data : 0xfcdf46de
                        AW Phy Addr : 0x58088000 Data : 0xeafffffe
                        BW Phy Addr : 0x58098000 Data : 0xa31fbdd8
                        AW Phy Addr : 0x58098000 Data : 0xeafffffe
                        BW Phy Addr : 0x48180c10 Data : 0x00000003
                        AW Phy Addr : 0x48180c10 Data : 0x00000000
                        Phy Addr : 0x48180c14 Data : 0x00000007
        PRCM for IVHD0 is Done Successfully  
PRCM Initialization completed 
syslink: disagrees about version of symbol clk_set_rate
syslink: Unknown symbol clk_set_rate (err -22)
syslink: disagrees about version of symbol clk_get_rate
syslink: Unknown symbol clk_get_rate (err -22)
syslink: disagrees about version of symbol clk_disable
syslink: Unknown symbol clk_disable (err -22)
syslink: disagrees about version of symbol clk_enable
syslink: Unknown symbol clk_enable (err -22)
FATAL: Error inserting syslink (/lib/modules/2.6.37/kernel/drivers/dsp/syslink.k
o): Invalid argument
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Loca
tion of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
OsalDrv driver close: /dev/syslinkipc_Osal: Bad file descriptor
/dev/syslinkipc_MultiProc: No such file or directory
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such file or directory
SharedRegion driver close: : Bad file descriptor
/dev/syslinkipc_GateMP: No such file or directory
/dev/syslinkipc_MessageQ: No such file or directory
MessageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc_Notify: No such file or directory
Notify driver close: /dev/syslinkipc_Notify: Bad file descriptor
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
/dev/syslinkipc_HeapBufMP: No such file or directorsyslink: disagrees about vers
ion of symbol clk_set_rate
y
/dev/syslinkisyslink: Unknown symbol clk_set_rate (err -22)
pc_HeapMemMP: No such file or directory
/dev/syslinkipc_ListMP:syslink: disagrees about version of symbol clk_get_rate
 No such file orsyslink: Unknown symbol clk_get_rate (err -22)
 directory
/dev/syslinkipc_Ringsyslink: disagrees about version of symbol clk_disable
IO: No such filesyslink: Unknown symbol clk_disable (err -22)
 or directory
RingIO driver closyslink: disagrees about version of symbol clk_enable
se: : Bad file dsyslink: Unknown symbol clk_enable (err -22)
escriptor
/dev/syslinkipc_RingIOShm: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_ClientNotifyMgr: No such file or directory
ClientNotifyMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQBufMgr: No such file or directory
FrameQBufMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQ: No such file or directory
FrameQ driver close: : Bad file descriptor
/dev/syslinkipc_Ipc: No such file or directory
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
FIRMWARE: Could not open ProcMgr: ProcMgr status 0xfffffff8
Starting telnet daemon.
Loading HDVPSS Firmware
FATAL: Error inserting syslink (/lib/modules/2.6.37/kernel/drivers/dsp/syslink.k
o): Invalid argument
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Loca
tion of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
OsalDrv driver close: /dev/syslinkipc_Osal: Bad file descriptor
/dev/syslinkipc_MultiProc: No such file or directory
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such file or directory
SharedRegion driver close: : Bad file descriptor
/dev/syslinkipc_GateMP: No such file or directory
/dev/syslinkipc_MessageQ: No such file or directory
MessageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc_Notify: No such file or directory
Notify driver close: /dev/syslinkipc_Notify: Bad file descriptor
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
/dev/syslinkipc_HeapBufMP: No such file or directory
/dev/syslinkipc_HeapMemMP: No such file or directory
/dev/syslinkipc_ListMP: No such file or directory
/dev/syslinkipc_RingIO: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_RingIOShm: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_ClientNotifyMgr: No such file or directory
ClientNotifyMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQBufMgr: No such file or directory
FrameQBufMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQ: No such file or directory
FrameQ driver close: : Bad file descriptor
/dev/syslinkipc_Ipc: No such file or directory
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
FIRMWARE: Could not open ProcMgr: ProcMgr status 0xfffffff8
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
ti81xxfb ti81xxfb: no grpxs
ti81xxfb: probe of ti81xxfb failed with error -22
Configuring fb0 to LCD
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sy
s/devices/platform/vpss/graphics0/nodes: nonexistent directory
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sy
s/devices/platform/vpss/display1/enabled: nonexistent directory
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sy
s/devices/platform/vpss/display1/timings: nonexistent directory
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sy
s/devices/platform/vpss/display1/output: nonexistent directory
/etc/init.d/rc: /etc/rc5.d/S15load-hdvpss-firmware.sh: line 60: can't create /sy
s/devices/platform/vpss/display1/enabled: nonexistent directory
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
cat: write error: No space left on device
cat: write error: No space left on device
.

Do I need to rebuild syslink for some reason? Where can I get a copy?

Or do I need to rebuild the root NFS filesystem with a matching version? But then why doesn't my rebuild (with no modifications) not match?

 

Thanks in advance,

Christopher

 

  • Hello again.

    This time I tried to rebuild the kernel from the EZSDK src instead of the PSP source. Comparing the two sets of instructions, it appears that the PSP instructions lack information regarding the "install" step. Where are the kernel modules output? What other modules (e.g., syslink) am I required to rebuild and where are the source tarballs?

    The EZSDK kernel build and install steps went smoothly. As did the rebuild of the cmem and syslink dsp drivers. However, this time, the kernel boot failed with "FATAL: Module syslink not found." Obviously, I checked the file location -- reverting to the default EZSDK filesystem results in the same "file not found" error instead of the "invalid argument" issue found with the PSP src.

     

    Any ideas?

    Christopher

     

     

  • You could rebuild the kernel and other software from the EZSDK toplevel itself. This makefile does have an install step that copies over .kos and any other software that's built.

    To build syslink, you can run 'make syslink'. More information is available via 'make help'.

  • Okay, let's ignore building the kernel from LINUX-PSP-04.01.00.05 for now and concentrate on rebuilding from EZSDK-05.02.02.60.

    I followed the instructions to the letter in DM814x_AM387x_EZ_Software_Developers_Guide.pdf  Creating your own Linux kernel image: I rebuilt the kernel, I did the install, I rebuilt the kernel modules individually (cmem and syslink), and I copied all of the files to the correct places, as described. However, again, I got "FATAL: Module syslink not found." during boot. I have attached the full boot log.

    3247.syslink_not_found.txt

    So, what am I doing wrong here? Am I missing some kind of depmod/insmod type step? Where is syslink.ko even being told to load?

    Has anyone else gotten this to work?

     

    Thanks,

    Christopher

  • Hi Christopher,

    Chris Pattenden said:
    So, what am I doing wrong here? Am I missing some kind of depmod/insmod type step? Where is syslink.ko even being told to load?

    We use modprobe to load different kernel objects. Modprobe expect syslink.ko to be present under /lib/modules/<Kernel Version>/.... Please see the directory structure of the EZSDK filesystem to see how we have installed it. It should find it as long as syslink.ko is present in the right location.

    In the next EZSDK release, we are working on updating make install so that all the modules, go into a directory structure that matches the filesystem that's shipped in the EZSDK.

     

     

  • I placed syslink.ko into /lib/modules/2.6.37/kernel/drivers/dsp/ (right where the original file was located). I assume that 2.6.37 is the correct kernel version. That is the version that EZSDK 5.2.2.60 uses and that's what's in the kernel header in the board-support directory, but I can't boot far enough to be able to run "uname -r" to make sure.

    Am I using the correct patch/kernel version number? If you build the kernel from the instructions like I did (and then tftp/nfs boot), does it work for you?

    I tried disabling the syslink module to get a shell and run 'uname -r', but I either didn't properly remove the module or don't understand the other module dependencies.

     

    Thanks again,

    Christopher

     

  • Hi Christopher,

    Chris Pattenden said:

    Am I using the correct patch/kernel version number? If you build the kernel from the instructions like I did (and then tftp/nfs boot), does it work for you?

    I tried disabling the syslink module to get a shell and run 'uname -r', but I either didn't properly remove the module or don't understand the other module dependencies.

    We did test this out and it seems to work on my board. One of the things you could try is to boot without loading any of the init scripts that load syslink, firmware etc. If you use the smaller arago-base-tisdk-image-<platform>.tar.gz then it will boot without any init scripts or firmware. Once that's done, you could manually insmod syslink. More information on the EZSDK filesystems are available at http://processors.wiki.ti.com/index.php/EZSDK_Filesystems

  • Removing the initscripts in rc5.d that modeprobe syslink allowed me to boot to the login prompt. From there I was able to run depmod to properly configure modules.dep. I was then able to replace the initscrips and boot as expected.

    So, the question is when should depmod be run? Is it possible to generate modules.dep while performing the cross-compilation step or does depmod have to be run on the target system after it's booted?

     

    Thanks,

    Christopher