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.

Linux/TMDXEVM8148: vmap allocation for size 197136384 failed: use vmalloc=<size> to increase size.

Part Number: TMDXEVM8148

Tool/software: Linux

Set up the development environment as per the instructions documented in: DM814x_EZ_Software_Developers_Guide.pdf

While booting the Kernel there is a vmap allocation failure.

Running Ubuntu 11.10. 

Not sure the origin of the failure since it is being loaded off the shelf with no modifications?

Are there Kernel parameters that need to be passed or switch settings of some type that would resolve the issue.

Need guidance.

Steve

U-Boot 2010.06 (Nov 10 2011 - 23:50:16)

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 already flashed
MMC:   OMAP SD/MMC: 0
Hit any key to stop autoboot:  0
reading u-boot.bin

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


U-Boot 2010.06 (Nov 10 2011 - 23:45:47)

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,                

MMC:   OMAP SD/MMC: 0
Net:   Detected MACID:0:18:32:61:3d:e8
cpsw
Hit any key to stop autoboot:  0
link up on port 0, speed 1000, full duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
*** Unhandled DHCP Option in OFFER/ACK: 46
*** Unhandled DHCP Option in OFFER/ACK: 46
DHCP client bound to address 192.168.0.11
link up on port 0, speed 1000, full duplex
Using cpsw device
TFTP from server 192.168.0.2; our IP address is 192.168.0.11
Filename 'uImage-dm814x-evm.bin'.
Load address: 0x81000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###########################
done
Bytes transferred = 2796444 (2aab9c hex)
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Arago/2.6.37-psp04.04.00.01/dm81
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2796380 Bytes = 2.7 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 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Dec 26 18:11:35 IST 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.1
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 160648
Kernel command line: console=ttyO0,115200n8 rootwait rw mem=364M@0x80000000 mem=320M@0x9FC00000 root=/dev/nfs nfsroot=192.168.0.2:/home/steve/targetfs ip=dhcp
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 364MB 270MB = 634MB total
Memory: 636932k/636932k available, 63484k reserved, 10240K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xf0800000 - 0xf8000000   ( 120 MB)
    lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc003d000   ( 212 kB)
      .text : 0xc003d000 - 0xc0549000   (5168 kB)
      .data : 0xc054a000 - 0xc05970c0   ( 309 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
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 IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
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_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
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
NOR: Can't request GPMC CS
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xf0820000
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea2080b
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
pcf857x 1-0021: gpios 128..143 on a pcf8575
regulator: VRTC: 1800 mV
regulator: VIO: 1500 mV
regulator: VDD1: 600 <--> 1500 mV at 1200 mV
regulator: VDD2: 600 <--> 1500 mV at 1200 mV
regulator: VDDCTRL: 600 <--> 1400 mV at 1200 mV
regulator: LDO1: 1100 <--> 3300 mV at 1800 mV
regulator: LDO2: 1100 <--> 3300 mV at 1800 mV
regulator: LDO3: 1100 <--> 3300 mV at 3300 mV
regulator: LDO4: 1100 <--> 3300 mV at 1800 mV
regulator: LDO5: 1100 <--> 3300 mV at 3300 mV
regulator: LDO6: 1100 <--> 3300 mV at 3300 mV
regulator: LDO7: 1100 <--> 3300 mV at 3300 mV
regulator: LDO8: 1100 <--> 3300 mV at 1800 mV
tps65910 1-002d: No interrupt support, no core IRQ
omap_i2c omap_i2c.3: bus 3 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
MUSB controller-0 revision 4ea20800
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 f081e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
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 f0826800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 512 (order: 1, 8192 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
highmem bounce pool size: 64 pages
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 1224
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
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
ONFI flash detected
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
CAN device driver interface
CAN bus driver for Bosch D_CAN controller 1.0
d_can d_can: d_can device registered (irq=52, irq_obj=53)
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
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
ata1: SATA link down (SStatus 0 SControl 300)
qt602240_ts 1-004a: Family ID: 128 Variant ID: 1 Version: 22 Build: 171
qt602240_ts 1-004a: Matrix X Size: 18 Matrix Y Size: 12 Object Num: 17
input: AT42QT602240/ATMXT224 Touchscreen as /devices/platform/omap/omap_i2c.1/i2c-1/1-004a/input/input0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
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
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
  #0: TI81XX EVM
nf_conntrack version 0.5.0 (9952 buckets, 39808 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
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
Power Management for TI81XX.
Detected MACID=0:18:32:61:3d:e8
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
 mmcblk0: p1 p2 p3

CPSW phy found : id is : 0x4dd074

CPSW phy found : id is : 0x4dd074
Sending DHCP requests .
PHY: 0:01 - Link is Up - 0/Half
PHY: 0:01 - Link is Down
.
PHY: 0:00 - Link is Up - 1000/Full
.., OK
IP-Config: Got DHCP answer from 192.168.0.1, my address is 192.168.0.11
IP-Config: Gateway not on directly connected network.
VFS: Mounted root (nfs filesystem) on device 0:15.
devtmpfs: mounted
Freeing init memory: 212K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udevd (74): /proc/74/oom_adj is deprecated, please use /proc/74/oom_score_adj instead.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mmcblk0.
EXT3-fs: barriers not enabled
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
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 recommended
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
NET: Registered protocol family 10
ALSA: Restoring mixer settings...
No state is present for card EVM
NOT configuring network interfaces: / is an NFS mount
Found hardware: "" "" "" "" ""
Hardware is initialized using a generic method
No state is present for card EVM
Mon Dec 31 10:37:00 UTC 2012
INIT: Entering runlevel: 5
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 : 0x00000001
                        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 : 0x4981e772
                        AW Phy Addr : 0x58088000 Data : 0xeafffffe
                        BW Phy Addr : 0x58098000 Data : 0x551f2f4b
                        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 version : 2.20.02.20
SysLink module created on Date:Dec 26 2012 Time:18:39:49
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id>         0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop>           to start/stop the firmware
===Optional arguments===
-mmap                  input memory map bin file name
-i2c                   0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.2.1
vmap allocation for size 197136384 failed: use vmalloc=<size> to increase size.
Unable to handle kernel paging request at virtual address 40000010
pgd = eedf0000
[40000010] *pgd=aed19031, *pte=00000000, *ppte=00000000
Internal error: Oops: 817 [#1]
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in: syslink ipv6
CPU: 0    Not tainted  (2.6.37 #1)
PC is at HeapMemMP_postInit+0x178/0x228 [syslink]
LR is at GateMP_getSharedAddr+0x4c/0x60 [syslink]
pc : [<bf099d84>]    lr : [<bf095f38>]    psr: 80000013
sp : ef1cdd78  ip : 00000000  fp : ef1cddb4
r10: 00000001  r9 : ef1cde14  r8 : ef1cde00
r7 : f0807000  r6 : f080a000  r5 : 40000000  r4 : 0bbfff80
r3 : 00000580  r2 : 00000580  r1 : 00060000  r0 : 00000580
Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 10c5387d  Table: aedf0019  DAC: 00000015
Process firmware_loader (pid: 1250, stack limit = 0xef1cc2e8)
Stack: (0xef1cdd78 to 0xef1ce000)
dd60:                                                       00000002 00000004
dd80: ef1cddb4 ef1cdd90 ef1cddb4 ef1cdd98 bf083264 bf074358 40000000 f080a000
dda0: f0807000 00000000 ef1cddf4 ef1cddb8 bf09b63c bf099c18 ef1cde00 00000001
ddc0: ef1cddf4 00000000 bf0809ac ef1cde00 ef1cde44 f0b51048 00000000 00000002
dde0: 00000048 00000000 ef1cde2c ef1cddf8 bf09bfa0 bf09b250 f0b51048 00000002
de00: 00000000 00000000 40000000 0bbfff80 00000000 f0807000 0bc00000 ef1cde44
de20: ef1cde84 ef1cde30 bf085764 bf09be74 ef1cdeb8 eedf1330 ef1cdea4 f0b51000
de40: 00000001 00000000 00000000 40000000 0bbfff80 00000000 bf075630 c024f2a0
de60: ef311d00 bea2da64 00000009 bea2da64 ef1cc000 00000000 ef1cdef4 ef1cde88
de80: bf0c8218 bf085488 c024f2a0 bea2da64 ef1cdeac ef1cdea0 c00bc1dc c00b3214
dea0: ef1cdecc ffffffff 41063000 b3d00000 b3d00000 bea2da9c 40000000 0bc00000
dec0: 00010003 00000000 00000080 00000001 00000000 00000000 00000000 ef311d00
dee0: 00000009 00000009 ef1cdf04 ef1cdef8 c00d76ec bf0c7dcc ef1cdf74 ef1cdf08
df00: c00d7dfc c00d76d0 000000fb 000000fb 41063000 eee1bc00 ef0d0600 0bc00000
df20: 0000bc00 000b3d00 ef1cdf74 ef1cdf38 c00be258 c00bdbe0 000000fb 000b3d00
df40: ef1cc000 eee1bc00 00000001 00000000 bea2da64 c024f2a0 00000009 ef311d00
df60: ef1cc000 00000000 ef1cdfa4 ef1cdf78 c00d7e94 c00d7908 00000001 00000001
df80: 00000003 00046ee8 00000000 00008e20 00000036 c0047fa8 00000000 ef1cdfa8
dfa0: c0047e00 c00d7e48 00046ee8 00000000 00000009 c024f2a0 bea2da64 00000009
dfc0: 00046ee8 00000000 00008e20 00000036 00000000 00000000 40089000 bea2da4c
dfe0: 00000000 bea2da00 0002e33c 40258aec 20000010 00000009 00000000 00000000
Backtrace:
[<bf099c0c>] (HeapMemMP_postInit+0x0/0x228 [syslink]) from [<bf09b63c>] (_HeapMemMP_create+0x3f8/0x5e0 [syslink])
 r7:00000000 r6:f0807000 r5:f080a000 r4:40000000
[<bf09b244>] (_HeapMemMP_create+0x0/0x5e0 [syslink]) from [<bf09bfa0>] (HeapMemMP_create+0x138/0x1bc [syslink])
[<bf09be68>] (HeapMemMP_create+0x0/0x1bc [syslink]) from [<bf085764>] (SharedRegion_setEntry+0x2e8/0x414 [syslink])
 r5:ef1cde44 r4:0bc00000

  • Apparently, the issue is related to the default Linux configuration not matching that of the EVM.

    How are the menuconfig items such as menuconfig->Kernel Features->HIGH Memory Support accessed and set?

    The SDK build system uses Make files and Make options to build specific components. There is no mention of how to access the items

    via the standard menuconfig utilities like shown below:

    To invoke the kernel configuration you simply use a command like:

    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- <config type>

    i.e. for menuconfig the command would look like

    make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- menuconfig

    .
    From DM814x_EZ_Software_Developers_Guide.pdf

    Modifying the EZSDK Memory Map
    By Default, the EZSDK Ships with a memory map that is configured for 1GB of DDR. More details on how
    to configure the memory map to different memory sizes or to even change the partitioning is available on TI's
    Processor Wiki at processors.wiki.ti.com/.../EZSDK_Memory_Map.
    There is a document related to this issue:
    processors.wiki.ti.com/.../EZSDK_Memory_Map
    States:
    Modifying Memory Map
    Linux Kernel Memory

    Linux size is passed though the mem parameter in the bootargs environment variable, base address is always <LINUX_MEM_1> -

    % setenv bootargs 'console=ttyO2,115200n8 root=/dev/nfs nfsroot=<nfs-server-ip>:<path-to-nfs-share>,nolock rw mem=<size of LINUX_MEM_1>@<addr of LINUX_MEM_1> mem=<size of LINUX_MEM_2>@<addr of LINUX_MEM_2>'

    For 1GB default memory map,

    % setenv bootargs 'console=ttyO2,115200n8 root=/dev/nfs nfsroot=<nfs-server-ip>:<path-to-nfs-share>,nolock rw mem=364M'

    The second partition can be added to linux mem=320M@0x9FC00000 Ex: mem=364M mem=320M@0x9FC00000

    When the 2 partition is set it throws below error while running EZSDK. "vmap allocation for size 197136384 failed: use vmalloc=500M to increase size."

    To solve this rebuild the kernel with HIGHMEM support enabled. This can be enabled by menuconfig->Kernel Features->HIGH Memory Support. Please note Linux partiton memory needs to start and end at 4MB boundary.

    For quick check you can pass vmalloc=500M to bootargs, but note that the actual physical memory which can be managed by Linux would less that what is passed via mem= bootargs.
  • Hello,

    What is the EZSDk version that you are using?
    Are you using EVM?
    Can you boot the board with the default bootargs:
    console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M vmalloc=500M ti814xfb.vram=0:16M,1:16M,2:6M ip=off noinitrd

    BR
    Margarita
  • Hi Margarita,

    Using ti-ezsdk_dm814x-evm_5_05_02_00.

    Was able to identify where to add the menuconfig option to the appropriate place in the EZSDK make system to be able to pull up a Linux configuration menu.

    It was realized, after reviewing the documentation about configuring memory to support different versions of the Eval board, that the instructions were written to configure support for the default memory configuration of 1GB. We were then able to modify the default configuration and boot Linux on the Eval board. This is a good baseline for development.

    The default arguments that you provided are not in the same format as the default arguments generated when building the EZSDK.

    Steve
  • modules_generated.dep.txt
    kernel/crypto/aes_generic.ko:
    kernel/drivers/video/ti81xx/vpss/vpss.ko:
    kernel/drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/tlc59108/tlc59108.ko:
    kernel/drivers/scsi/scsi_wait_scan.ko:
    kernel/drivers/media/video/tvp7002.ko:
    kernel/drivers/media/video/ti81xx/ti81xxvo.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/media/video/ti81xx/ti81xxvin.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/ssb/ssb.ko:
    kernel/net/ipv4/tunnel4.ko:
    kernel/net/ipv6/ipv6.ko:
    kernel/net/ipv6/xfrm6_mode_transport.ko:
    kernel/net/ipv6/xfrm6_mode_tunnel.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/xfrm6_mode_beet.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/sit.ko: kernel/net/ipv4/tunnel4.ko kernel/net/ipv6/ipv6.ko
    
    modules_orig.dep.txt
    updates/drivers/net/wireless/wl12xx/wl12xx.ko: updates/net/mac80211/mac80211.ko updates/net/wireless/cfg80211.ko updates/compat/compat.ko
    updates/drivers/net/wireless/wl12xx/wl12xx_spi.ko: updates/drivers/net/wireless/wl12xx/wl12xx.ko updates/net/mac80211/mac80211.ko updates/net/wireless/cfg80211.ko updates/compat/compat.ko
    updates/drivers/net/wireless/wl1251/wl1251.ko: updates/net/mac80211/mac80211.ko updates/compat/compat.ko updates/net/wireless/cfg80211.ko
    updates/drivers/net/wireless/wl1251/wl1251_spi.ko: updates/drivers/net/wireless/wl1251/wl1251.ko updates/net/mac80211/mac80211.ko updates/compat/compat.ko updates/net/wireless/cfg80211.ko
    updates/net/mac80211/mac80211.ko: updates/compat/compat.ko updates/net/wireless/cfg80211.ko
    updates/net/wireless/cfg80211.ko:
    updates/compat/compat.ko:
    kernel/drivers/media/video/ti81xx/ti81xxvo.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/media/video/ti81xx/ti81xxvin.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/media/video/tvp7002.ko:
    kernel/drivers/scsi/scsi_wait_scan.ko:
    kernel/drivers/ssb/ssb.ko:
    kernel/drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/tlc59108/tlc59108.ko:
    kernel/drivers/video/ti81xx/vpss/vpss.ko:
    kernel/drivers/gpu/pvr/pvrsrvkm.ko:
    kernel/drivers/gpu/pvr/omaplfb.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko kernel/drivers/gpu/pvr/pvrsrvkm.ko
    kernel/drivers/gpu/pvr/bufferclass_ti.ko: kernel/drivers/gpu/pvr/pvrsrvkm.ko
    kernel/drivers/dsp/cmemk.ko:
    kernel/drivers/dsp/syslink.ko:
    kernel/net/ipv6/xfrm6_mode_beet.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/ipv6.ko:
    kernel/net/ipv6/sit.ko: kernel/net/ipv4/tunnel4.ko kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/xfrm6_mode_transport.ko:
    kernel/net/ipv6/xfrm6_mode_tunnel.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv4/tunnel4.ko:
    

  • Hello,

    What exactly is the the question here?
    Are you able to boot the EVM?

    BR
    Margarita
  • Hi Margarita,

    No, Linux does not boot on the EVM as built.

    FATAL: Module syslink not found.

    Steve

    .., OK                                                                          
    IP-Config: Got DHCP answer from 192.168.0.1, my address is 192.168.0.11         
    IP-Config: Gateway not on directly connected network.                           
    VFS: Mounted root (nfs filesystem) on device 0:15.                              
    devtmpfs: mounted                                                               
    Freeing init memory: 208K                                                       
    INIT: version 2.86 booting                                                      
    Please wait: booting...                                                         
    Starting udev                                                                   
    udevd (70): /proc/70/oom_adj is deprecated, please use /proc/70/oom_score_adj in
    stead.                                                                          
    FAT: bogus number of reserved sectors                                           
    VFS: Can't find a valid FAT filesystem on dev mmcblk0.                          
    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                
    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                
    Root filesystem already rw, not remounting                                      
    Caching udev devnodes                                                           
    NET: Registered protocol family 10                                              
    ALSA: Restoring mixer settings...                                               
    No state is present for card EVM                                                
    Found hardware: "" "" "" "" ""                                                  
    Hardware is initialized using a generic method                                  
    NOT configuring network interfaces: / is an NFS mount                           
    No state is present for card EVM                                                
    Mon Dec 31 10:37:00 UTC 2012                                                    
    INIT: Entering runlevel: 5                                                      
    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 : 0x00000001              
                            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 : 0x4981e532              
                            AW Phy Addr : 0x58088000 Data : 0xeafffffe              
                            BW Phy Addr : 0x58098000 Data : 0x151b274b              
                            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                                                   
    FATAL: Module syslink not found.                                                


  • Hello,

    Please when you rebuild the kernel execute this also:
    make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm modules
    make ... install

    Cp the /path to install folder/lib/modules to /rootfs/lib

    Let me know the result.

    BR
    Margarita
  • make clean
    make all
    make install
    Cp the /path to install folder/lib/modules to /rootfs/lib

    This is what I did.

    module dependencies are not the same as the original delivered with the kit.
  • Default for make all:

    make -C /home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01 ARCH=arm CROSS_COMPILE=/home/steve/CodeSourcery/Sourcery_G++_Lite//bin/arm-none-linux-gnueabi- ti8148_evm_defconfig
    make[1]: Entering directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'

    Will try to add modules
  • make -C /home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01 ARCH=arm CROSS_COMPILE=/home/steve/CodeSourcery/Sourcery_G++_Lite//bin/arm-none-linux-gnueabi- modules
  • make -C /home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01 ARCH=arm CROSS_COMPILE=/home/steve/CodeSourcery/Sourcery_G++_Lite//bin/arm-none-linux-gnueabi- INSTALL_MOD_PATH=/home/st
    eve/targetfs/home/root/dm814x-evm/ modules_install

    The files being generated do not match that which are in the original folder prior to build.
  • make -C /home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01 ARCH=arm CROSS_COMPILE=/home/steve/CodeSourcery/Sourcery_G++_Lite//bin/arm-none-linux-gnueabi- modules
  • Output of operations:

    steve@steve-VirtualBox:~/ti-ezsdk_dm814x-evm_5_05_02_00$
    steve@steve-VirtualBox:~/ti-ezsdk_dm814x-evm_5_05_02_00$ make -C /home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01 ARCH=arm CROSS_COMPILE=/home/steve/CodeSourcery/Sourcery_G++_Lite//bin/arm-none-linux-gnueabi- modules
    make: Entering directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'
    CHK include/linux/version.h
    CHK include/generated/utsrelease.h
    make[1]: `include/generated/mach-types.h' is up to date.
    CALL scripts/checksyscalls.sh
    Building modules, stage 2.
    MODPOST 16 modules
    make: Leaving directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'
    steve@steve-VirtualBox:~/ti-ezsdk_dm814x-evm_5_05_02_00$ make -C /home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01 ARCH=arm CROSS_COMPILE=/home/steve/CodeSourcery/Sourcery_G++_Lite//bin/arm-none-linux-gnueabi- INSTALL_MOD_PATH=/home/steve/targetfs/home/root/dm814x-evm/ modules_install
    make: Entering directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'
    INSTALL crypto/aes_generic.ko
    INSTALL drivers/media/video/ti81xx/ti81xxvin.ko
    INSTALL drivers/media/video/ti81xx/ti81xxvo.ko
    INSTALL drivers/media/video/tvp7002.ko
    INSTALL drivers/scsi/scsi_wait_scan.ko
    INSTALL drivers/ssb/ssb.ko
    INSTALL drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko
    INSTALL drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko
    INSTALL drivers/video/ti81xx/tlc59108/tlc59108.ko
    INSTALL drivers/video/ti81xx/vpss/vpss.ko
    INSTALL net/ipv4/tunnel4.ko
    INSTALL net/ipv6/ipv6.ko
    INSTALL net/ipv6/sit.ko
    INSTALL net/ipv6/xfrm6_mode_beet.ko
    INSTALL net/ipv6/xfrm6_mode_transport.ko
    INSTALL net/ipv6/xfrm6_mode_tunnel.ko
    DEPMOD 2.6.37
    make: Leaving directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'
    steve@steve-VirtualBox:~/ti-ezsdk_dm814x-evm_5_05_02_00$
  • The dependency file looks like it lines up with the make script. How do I change the make script to INSTALL the appropriate drivers/modules?

    From the make script:

    INSTALL crypto/aes_generic.ko
    INSTALL drivers/media/video/ti81xx/ti81xxvin.ko
    INSTALL drivers/media/video/ti81xx/ti81xxvo.ko
    INSTALL drivers/media/video/tvp7002.ko
    INSTALL drivers/scsi/scsi_wait_scan.ko
    INSTALL drivers/ssb/ssb.ko
    INSTALL drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko
    INSTALL drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko
    INSTALL drivers/video/ti81xx/tlc59108/tlc59108.ko
    INSTALL drivers/video/ti81xx/vpss/vpss.ko
    INSTALL net/ipv4/tunnel4.ko
    INSTALL net/ipv6/ipv6.ko
    INSTALL net/ipv6/sit.ko
    INSTALL net/ipv6/xfrm6_mode_beet.ko
    INSTALL net/ipv6/xfrm6_mode_transport.ko
    INSTALL net/ipv6/xfrm6_mode_tunnel.ko
    DEPMOD 2.6.37


    From modules.dep

    kernel/crypto/aes_generic.ko:
    kernel/drivers/video/ti81xx/vpss/vpss.ko:
    kernel/drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/tlc59108/tlc59108.ko:
    kernel/drivers/scsi/scsi_wait_scan.ko:
    kernel/drivers/media/video/tvp7002.ko:
    kernel/drivers/media/video/ti81xx/ti81xxvo.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/media/video/ti81xx/ti81xxvin.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/ssb/ssb.ko:
    kernel/net/ipv4/tunnel4.ko:
    kernel/net/ipv6/ipv6.ko:
    kernel/net/ipv6/xfrm6_mode_transport.ko:
    kernel/net/ipv6/xfrm6_mode_tunnel.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/xfrm6_mode_beet.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/sit.ko: kernel/net/ipv4/tunnel4.ko kernel/net/ipv6/ipv6.ko
  • The installed drivers from the make and install are the same as what is in the dependency file. How do these modules get specified to install?

    steve@steve-VirtualBox:~/targetfs/home/root/dm814x-evm/lib/modules/2.6.37$ make -C /home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01 ARCH=arm CROSS_COMPILE=/home/steve/CodeSourcery/Sourcery_G++_Lite//bin/arm-none-linux-gnueabi- modules
    make: Entering directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'
    CHK include/linux/version.h
    CHK include/generated/utsrelease.h
    make[1]: `include/generated/mach-types.h' is up to date.
    CALL scripts/checksyscalls.sh
    Building modules, stage 2.
    MODPOST 16 modules
    make: Leaving directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'
    steve@steve-VirtualBox:~/targetfs/home/root/dm814x-evm/lib/modules/2.6.37$ make -C /home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01 ARCH=arm CROSS_COMPILE=/home/steve/CodeSourcery/Sourcery_G++_Lite//bin/arm-none-linux-gnueabi- INSTALL_MOD_PATH=/home/steve/targetfs/home/root/dm814x-evm/ modules_install
    make: Entering directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'
    INSTALL crypto/aes_generic.ko
    INSTALL drivers/media/video/ti81xx/ti81xxvin.ko
    INSTALL drivers/media/video/ti81xx/ti81xxvo.ko
    INSTALL drivers/media/video/tvp7002.ko
    INSTALL drivers/scsi/scsi_wait_scan.ko
    INSTALL drivers/ssb/ssb.ko
    INSTALL drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko
    INSTALL drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko
    INSTALL drivers/video/ti81xx/tlc59108/tlc59108.ko
    INSTALL drivers/video/ti81xx/vpss/vpss.ko
    INSTALL net/ipv4/tunnel4.ko
    INSTALL net/ipv6/ipv6.ko
    INSTALL net/ipv6/sit.ko
    INSTALL net/ipv6/xfrm6_mode_beet.ko
    INSTALL net/ipv6/xfrm6_mode_transport.ko
    INSTALL net/ipv6/xfrm6_mode_tunnel.ko
    DEPMOD 2.6.37
    make: Leaving directory `/home/steve/ti-ezsdk_dm814x-evm_5_05_02_00/board-support/linux-2.6.37-psp04.04.00.01'


    modules.dep:

    kernel/crypto/aes_generic.ko:
    kernel/drivers/video/ti81xx/vpss/vpss.ko:
    kernel/drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/tlc59108/tlc59108.ko:
    kernel/drivers/scsi/scsi_wait_scan.ko:
    kernel/drivers/media/video/tvp7002.ko:
    kernel/drivers/media/video/ti81xx/ti81xxvo.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/media/video/ti81xx/ti81xxvin.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/ssb/ssb.ko:
    kernel/net/ipv4/tunnel4.ko:
    kernel/net/ipv6/ipv6.ko:
    kernel/net/ipv6/xfrm6_mode_transport.ko:
    kernel/net/ipv6/xfrm6_mode_tunnel.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/xfrm6_mode_beet.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/sit.ko: kernel/net/ipv4/tunnel4.ko kernel/net/ipv6/ipv6.ko

    From original installation:

    updates/drivers/net/wireless/wl12xx/wl12xx.ko: updates/net/mac80211/mac80211.ko updates/net/wireless/cfg80211.ko updates/compat/compat.ko
    updates/drivers/net/wireless/wl12xx/wl12xx_spi.ko: updates/drivers/net/wireless/wl12xx/wl12xx.ko updates/net/mac80211/mac80211.ko updates/net/wireless/cfg80211.ko updates/compat/compat.ko
    updates/drivers/net/wireless/wl1251/wl1251.ko: updates/net/mac80211/mac80211.ko updates/compat/compat.ko updates/net/wireless/cfg80211.ko
    updates/drivers/net/wireless/wl1251/wl1251_spi.ko: updates/drivers/net/wireless/wl1251/wl1251.ko updates/net/mac80211/mac80211.ko updates/compat/compat.ko updates/net/wireless/cfg80211.ko
    updates/net/mac80211/mac80211.ko: updates/compat/compat.ko updates/net/wireless/cfg80211.ko
    updates/net/wireless/cfg80211.ko:
    updates/compat/compat.ko:
    kernel/drivers/media/video/ti81xx/ti81xxvo.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/media/video/ti81xx/ti81xxvin.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/media/video/tvp7002.ko:
    kernel/drivers/scsi/scsi_wait_scan.ko:
    kernel/drivers/ssb/ssb.ko:
    kernel/drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko
    kernel/drivers/video/ti81xx/tlc59108/tlc59108.ko:
    kernel/drivers/video/ti81xx/vpss/vpss.ko:
    kernel/drivers/gpu/pvr/pvrsrvkm.ko:
    kernel/drivers/gpu/pvr/omaplfb.ko: kernel/drivers/video/ti81xx/vpss/vpss.ko kernel/drivers/gpu/pvr/pvrsrvkm.ko
    kernel/drivers/gpu/pvr/bufferclass_ti.ko: kernel/drivers/gpu/pvr/pvrsrvkm.ko
    kernel/drivers/dsp/cmemk.ko:
    kernel/drivers/dsp/syslink.ko:
    kernel/net/ipv6/xfrm6_mode_beet.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/ipv6.ko:
    kernel/net/ipv6/sit.ko: kernel/net/ipv4/tunnel4.ko kernel/net/ipv6/ipv6.ko
    kernel/net/ipv6/xfrm6_mode_transport.ko:
    kernel/net/ipv6/xfrm6_mode_tunnel.ko: kernel/net/ipv6/ipv6.ko
    kernel/net/ipv4/tunnel4.ko:
  • Hello,

    make syslink_clean

    make syslink

    make syslink_install

    cp the new syslink.ko

    If this is already being done, and still having issues, please take a look at this post for some more suggestions:

    e2e.ti.com/.../140714.aspx

    BR
    Margarita