Part Number:TDA3XEVM

Dear TI'er:

Recently，I have some research base on TDA3 EVM ，so i download the VersionSDK “PROCESSOR_SDK_VISION_03_07_00_00” from yours websites,and Install it in win10 system. But follow your userguide （eve_starterware_userguide）to build EVE Starterware, some error happened，I need your give me some suggestion，THX.

1. I have already check out the compiler path in CCS，as picture shows：

2. when building EVE starterware library for vayu platform and eve as host，error happened，like this：

3. I have no idea to  fix the error, where the path need changed like: ""D:\work\vision\dsp_git\dsp_apps\algframework‘’. and i change the file "makerules_eve.mk” with my DMAUTILS_PATH,But the error still exists.

4. If i need Program with EVE Core, did I need to do this at first step? How Can I use the starterware kernel code(Examples) in alg_plugins directly and which Demo Can I get some integration methods to learn?

BR.

Part Number:DRA745

Tool/software: Linux

How to use hardware to decode H264 on J6 platform? Do you have relevant libraries and documents? Linux 3.14.49 is currently in use

Part Number:AMIC110

Hello,

I am trying to generate project for HSR application.

http://processors.wiki.ti.com/index.php/PRU_ICSS_HSR_PRP

i am facing below problem.

No products of type "com.ti.rtsc.SYSBIOS" are currently installed!.

PFA of screen shots.

Kindly help.

Regards

VR

Part Number:AM1806

Hi

Sector can be configurable on NOR Flash side.

How about AM1806? How does AM1806 handle the sector information from NOR Flash ? Is it fixed?

Best regards,

HaTa.

Part Number:TMS320C6678

Hi,

Do you have a list with approved\tested DDR3 devices for the C6678?  

Also, Is there an updated DDR3 Register Calculator XLS?

Thank you,

Amir

Tool/software: Linux

Hi,

I'm trying to run lvds_vip_single_cam_view_sgx_display usecase of linux.

My board is TDA2x and using vision SDK 3.6ver.

In the source code, there are some image sensors such as CHAINS_CAPTURE_SRC_OV10635 / CHAINS_CAPTURE_SRC_UB964_OV1063X / CHAINS_CAPTURE_SRC_IMX290ISP / etc.

The problem is my camera is using ISX 016 that is not contained in the cases of this usecase.

Could you suggest how can i run this usecase with my camera?

Besides, when i run this usecase without using any camera, this message is showed.

[HOST] [IPU2 ] 36.685536 s: src/bsp_deviceI2c.c @ Line 386:
[HOST] [IPU2 ] 36.685628 s: I2C1: DEV 0x74: RD 0x01 ... ERROR !!!
[HOST] [IPU2 ] 36.685719 s: src/bsp_deviceI2c.c @ Line 412:
[HOST] [IPU2 ] 36.685811 s: I2C1: Error timeout 625 ms!!!
[HOST] [IPU2 ] 36.685902 s: src/bsputils_lvds.c @ Line 919:
[HOST] [IPU2 ] 36.685994 s: device address - 74 i2c error - -21
[HOST] [IPU2 ] 37.317300 s: src/bsp_deviceI2c.c @ Line 748:
[HOST] [IPU2 ] 37.317361 s: GIO_submit Err num: -21 (Custom log i added)
[HOST] [IPU2 ] 37.317452 s: src/bsp_deviceI2c.c @ Line 766:
[HOST] [IPU2 ] 37.317544 s: I2C1: DEV 0x38: RD 0x300a ... ERROR !!!
[HOST] [IPU2 ] 37.317666 s: src/bsp_deviceI2c.c @ Line 837:
[HOST] [IPU2 ] 37.317727 s: I2C1: Error timeout 626 ms!!!
[HOST] [IPU2 ] 37.318215 s: Assertion @ Line: 616 in /home/yoo/TDA2xCam/vision_sdk/apps/src/rtos/video_sensor/src/vid_sensor.c: status == SYSTEM_LINK_STATUS_SOK : failed !!!

When i followed error log, i2c error code -21 means there is no acknowledgement. 

Is it because there is no device to send an acknowledgment message?

Thanks & Regards,

Yoo

Part Number:TMS320C6678

Hi,

I have downloaded processor sdk from TI website. But how to build example in pdk_c667x_2_0_11\packages\ti\csl\example. Please help provide related guide.

Part Number:TCI6638K2K

Tool/software: Linux

Hi,

We have changed the NAND flash in our custom board, which is having different part number and size.

Part number is: Cypress S34MS16G202BHI000

Nand size: 2GiB

Input / Output Bus Width: 8-bits
Page Size: (2048 + 128) bytes; 128-byte spare area
Block Size: 64 Pages or (128k + 8k) bytes
Plane Size: 2048 Blocks per Plane or (256M + 16M) bytes
Device Size: 2 Planes per Device or 512 Mbyte

We created the ubifs image with following commands,

./mkfs.ubifs -r tisdk-rootfs-rt-k2hk-evm/ -o k2k_rootfs.ubifs.img -F -m 2048 -e 126976 -c 16100
./mkfs.ubifs -r boot/ -o k2k_boot.ubifs.img -F -m 2048 -e 126976 -c 99

vi ubinize.cfg

[boot]
mode=ubi
image=k2k-boot.ubifs.img
vol_type=dynamic
vol_id=0
vol_name=boot
vol_size=10MiB
[rootfs]
mode=ubi
image=k2k_rootfs.ubifs.img
vol_id=1
vol_type=dynamic
vol_name=rootfs
vol_flags=autoresize

./ubinize -o k2k_BBM.ubi -m 2048 -p 128KiB -s 2048 -O 2048 ubinize.cfg

bootarg variable as:

setenv args_ubi 'setenv bootargs ${bootargs} rootfstype=ubifs root=ubi1:rootfs rootflags=sync rw ubi.mtd=2,2048'

boot log as follows:

U-Boot 2013.01 (Jun 07 2019 - 17:41:06)

I2C:   ready
DDR3 speed 1600

Reseting entire DDR3 memory to 0 ...
DRAM:  2 GiB
NAND:  pagesize 0
writesize 2048
erasesize 131072
oobsize 128
busw 0
2048 MiB
Net:   K2HK_EMAC
Warning: K2HK_EMAC using MAC address from net device
, K2HK_EMAC1, K2HK_EMAC2, K2HK_EMAC3
Hit any key to stop autoboot:  0
Creating 1 MTD partitions on "nand0":
0x000000180000-0x000080000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: volume 1 ("rootfs") re-sized from 3440 to 16117 LEBs
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=2"
UBI: MTD device size:            2046 MiB
UBI: number of good PEBs:        16367
UBI: number of bad PEBs:         5
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     2
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 16367
UBI: number of PEBs reserved for bad PEB handling: 163
UBI: max/mean erase counter: 1/0
UBIFS: mounted UBI device 0, volume 0, name "boot"
UBIFS: mounted read-only
UBIFS: file system size:   9269248 bytes (9052 KiB, 8 MiB, 73 LEBs)
UBIFS: journal size:       1904640 bytes (1860 KiB, 1 MiB, 15 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: LZO
UBIFS: reserved for root:  0 bytes (0 KiB)
Loading file 'securedb.key.bin' to addr 0x0c000000 with size 28 (0x0000001c)...
Done
Loading file 'uImage-k2hk-evm.dtb' to addr 0x87000000 with size 54332 (0x0000d43c)...
Done
Loading file 'skern-k2hk-evm.bin' to addr 0x0c5f0000 with size 45056 (0x0000b000)...
Done
Loading file 'uImage-keystone-evm.bin' to addr 0x88000000 with size 4158720 (0x003f7500)...
Done
## installed monitor, freq [200000000], status 0
## Booting kernel from Legacy Image at 88000000 ...
   Image Name:   Linux-3.10.72-rt77_BBM_V1.0.0
   Created:      2019-06-12   7:17:15 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4158656 Bytes = 4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 87000000
   Booting using the fdt blob at 0x87000000
   Loading Kernel Image ... OK
OK
   Using Device Tree in place at 87000000, end 8701043b

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.10.72-rt77_BBM_V1.0.0 (yash@yash) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.039
[    0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=30c7387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine: KeyStone2, model: Texas Instruments Keystone 2 SoC
[    0.000000] switching to high address space at 0x800000000
[    0.000000] cma: CMA: reserved 16 MiB at 2e800000
[    0.000000] Memory policy: ECC enabled, Data cache writealloc
[    0.000000] PERCPU: Embedded 9 pages/cpu @c1066000 s12480 r8192 d16192 u36864
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260624
[    0.000000] Kernel command line: console=ttyS0,115200n8 rootwait=1 rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1024MB = 1024MB total
[    0.000000] Memory: 1013844k/1013844k available, 34732k reserved, 270336K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc074be28   (7440 kB)
[    0.000000]       .init : 0xc074c000 - 0xc079a0c0   ( 313 kB)
[    0.000000]       .data : 0xc079c000 - 0xc0802c18   ( 412 kB)
[    0.000000]        .bss : 0xc0802c18 - 0xc083e2d4   ( 238 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] ipc irq: irqchip registered, range 512-539
[    0.000000] Main PLL clk (1200000000 Hz), parent (122880000 Hz),postdiv = 2, mult = 624, prediv = 31
[    0.000000] Generic PLL clk (1400000000 Hz), parent (125000000 Hz),postdiv = 1, mult = 55, prediv = 4
[    0.000000] Generic PLL clk (1228800000 Hz), parent (122880000 Hz),postdiv = 2, mult = 19, prediv = 0
[    0.000000] Generic PLL clk (400000000 Hz), parent (100000000 Hz),postdiv = 4, mult = 15, prediv = 0
[    0.000000] Generic PLL clk (400000000 Hz), parent (100000000 Hz),postdiv = 4, mult = 15, prediv = 0
[    0.000000] Architected local timer running at 200.00MHz (phys).
[    0.000000] Switching to timer-based delay loop
[    0.000000] sched_clock: ARM arch timer >56 bits at 200000kHz, resolution 640/128ns
[    0.000000] keystone timer clock @200000000 MHz
[    0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
[    0.000000] Console: colour dummy device 80x30
[   72.669469] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[   72.669471] pid_max: default: 4096 minimum: 301
[   72.669581] Mount-cache hash table entries: 512
[   72.677942] CPU: Testing write buffer coherency: ok
[   72.678091] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[   72.678107] psci: probing function IDs from device-tree
[   72.678120] Setting up static identity map for 0xc0524fa0 - 0xc0524ff8
[   72.793779] CPU1: Booted secondary processor
[   72.793804] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[   72.833819] CPU2: Booted secondary processor
[   72.833844] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[   72.873837] CPU3: Booted secondary processor
[   72.873862] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[   72.873978] Brought up 4 CPUs
[   72.873996] SMP: Total of 4 processors activated (1600.00 BogoMIPS).
[   72.874000] CPU: All CPU(s) started in SVC mode.
[   72.874424] devtmpfs: initialized
[   72.888149] NET: Registered protocol family 16
[   72.889563] DMA: preallocated 256 KiB pool for atomic coherent allocations
[   72.903895] No ATAGs?
[   72.903911] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[   72.903917] hw-breakpoint: maximum watchpoint size is 8 bytes.
[   72.914997] bio: create slab <bio-0> at 0
[   72.915415] keystone-pcie: keystone_pcie_rc_init - start
[   72.915437] keystone2_pcie_serdes_setup for domain 0
[   72.917557] keystone2_pcie_serdes_setup done domain 0, en_link_train = 1
[   72.917585] keystone-pcie: MEM 0x0000000050000000..0x000000005fffffff -> 0x0000000050000000
[   72.917594] keystone-pcie: IO 0x0000000023250000..0x0000000023253fff -> 0x0000000000000000
[   72.917625] keystone-pcie: pcie - number of legacy irqs = 4
[   72.917668] keystone-pcie: pcie - number of MSI host irqs = 8, msi_irqs = 32
[   73.019487] keystone-pcie: Doing PCI Setup...Done
[   73.019492] keystone-pcie: Starting PCI scan, nr 0...
[   73.019622] PCI host bridge to bus 0000:00
[   73.019632] pci_bus 0000:00: root bus resource [mem 0x50000000-0x5fffffff]
[   73.019639] pci_bus 0000:00: root bus resource [io  0x0000-0x3fff]
[   73.019645] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[   73.019678] PCI: bus0: Fast back to back transfers enabled
[   73.019694] keystone-pcie: Ending PCI scan...
[   73.019702] keystone-pcie: keystone_pcie_rc_init - end
[   73.019991] vgaarb: loaded
[   73.020322] SCSI subsystem initialized
[   73.020952] usbcore: registered new interface driver usbfs
[   73.021041] usbcore: registered new interface driver hub
[   73.021144] usbcore: registered new device driver usb
[   73.022648] pps_core: LinuxPPS API ver. 1 registered
[   73.022653] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[   73.022723] PTP clock support registered
[   73.022844] keystone-hwqueue hwqueue.8: qmgr start queue 0, number of queues 8192
[   73.022919] keystone-hwqueue hwqueue.8: added qmgr start queue 0, num of queues 8192, reg_peek f0040000, reg_status f0006000, reg_config f00080
[   73.022928] keystone-hwqueue hwqueue.8: qmgr start queue 8192, number of queues 8192
[   73.022998] keystone-hwqueue hwqueue.8: added qmgr start queue 8192, num of queues 8192, reg_peek f0100000, reg_status f000c400, reg_config f00
[   73.023627] keystone-hwqueue hwqueue.8: qos: sched port @8096, drop sched @8000
[   73.024118] keystone-hwqueue hwqueue.8: qos: sched port @6496, drop sched @6400
[   73.024927] keystone-hwqueue hwqueue.8: added pool pool-rio: 128 descriptors of size 256
[   73.024936] keystone-hwqueue hwqueue.8: added pool pool-xge: 1024 descriptors of size 128
[   73.024945] keystone-hwqueue hwqueue.8: added pool pool-crypto: 1024 descriptors of size 128
[   73.024953] keystone-hwqueue hwqueue.8: added pool pool-net: 11264 descriptors of size 128
[   73.024960] keystone-hwqueue hwqueue.8: added pool pool-udma: 1920 descriptors of size 256
[   73.027808] keystone-hwqueue hwqueue.8: registered queues 0-16383
[   73.028086] keystone-hwqueue hwqueue.8: qos version 0x200010b, magic valid
[   73.028571] keystone-hwqueue hwqueue.8: qos version 0x200010b, magic valid
[   73.035820] keystone-pktdma 2a08000.pktdma: registered 32 logical channels, flows 32, tx chans: 32, rx chans: 32, loopback
[   73.039681] keystone-pktdma 2004000.pktdma: registered 33 logical channels, flows 32, tx chans: 9, rx chans: 24
[   73.040229] keystone-pktdma 2fa1000.pktdma: registered 4 logical channels, flows 32, tx chans: 16, rx chans: 16
[   73.040399] Switching to clocksource arch_sys_counter
[   73.062638] NET: Registered protocol family 2
[   73.063117] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[   73.063231] TCP bind hash table entries: 8192 (order: 5, 229376 bytes)
[   73.063445] TCP: Hash tables configured (established 8192 bind 8192)
[   73.063487] TCP: reno registered
[   73.063496] UDP hash table entries: 512 (order: 3, 32768 bytes)
[   73.063534] UDP-Lite hash table entries: 512 (order: 3, 32768 bytes)
[   73.063739] NET: Registered protocol family 1
[   73.063922] RPC: Registered named UNIX socket transport module.
[   73.063927] RPC: Registered udp transport module.
[   73.063932] RPC: Registered tcp transport module.
[   73.063936] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   73.064281] hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available
[   73.118979] bounce pool size: 64 pages
[   73.127248] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   73.127319] NTFS driver 2.1.30 [Flags: R/O].
[   73.127566] jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
[   73.127906] msgmni has been set to 1484
[   73.128787] NET: Registered protocol family 38
[   73.128993] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[   73.129000] io scheduler noop registered
[   73.129005] io scheduler deadline registered
[   73.129241] io scheduler cfq registered (default)
[   73.130840] keystone-udma udma0.9: registered udma device udma0
[   73.190784] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[   73.192392] 2530c00.serial: ttyS0 at MMIO 0x2530c00 (irq = 309) is a 16550A
[   74.039871] console [ttyS0] enabled
[   74.044066] 2531000.serial: ttyS1 at MMIO 0x2531000 (irq = 312) is a 16550A
[   74.054653] loop: module loaded
[   74.057933] at24 0-0050: 131072 byte 24c1024 EEPROM, writable, 1 bytes/write
[   74.066498] Generic platform RAM MTD, (c) 2004 Simtec Electronics
[   74.073499] ONFI param page 0 valid
[   74.076996] erasesize 131072
[   74.079880] writesize 2048
[   74.082590] oobsize 128
[   74.085038] busw 0
[   74.087050] ONFI flash detected
[   74.090200] NAND device: Manufacturer ID: 0x01, Chip ID: 0xa5 (AMD/Spansion S34MS16G2), 2048MiB, page size: 2048, OOB size: 128
[   74.101717] 'erasesize 131072
[   74.104689] writesize 2048
[   74.107397] oobsize 128
[   74.109844] busw 0
[   74.111857] chunks 4
[   74.114317] Bad block table found at page 1048512, version 0x02
[   74.120721] Bad block table found at page 1048448, version 0x02
[   74.127133] nand_read_bbt: bad block at 0x000031440000
[   74.132388] 3 ofpart partitions found on MTD device 30000000.nand
[   74.138500] Creating 3 MTD partitions on "30000000.nand":
[   74.143917] 0x000000000000-0x000000100000 : "u-boot"
[   74.149637] 0x000000100000-0x000000180000 : "params"
[   74.155306] 0x000000180000-0x000040000000 : "ubifs"
[   74.161199] davinci_nand 30000000.nand: controller rev. 2.5
[   74.167449] spi_davinci 21000400.spi: master is unqueued, this is deprecated
[   74.174791] m25p80 spi32766.0: found n25q128a11, expected n25q128
[   74.180907] m25p80 spi32766.0: n25q128a11 (16384 Kbytes)
[   74.186243] 2 ofpart partitions found on MTD device spi32766.0
[   74.192094] Creating 2 MTD partitions on "spi32766.0":
[   74.197248] 0x000000000000-0x000000080000 : "u-boot-spl"
[   74.203248] 0x000000080000-0x000001000000 : "test"
[   74.209049] spi_davinci 21000400.spi: Controller at 0xf007a400
[   74.215215] spi_davinci 21000600.spi: master is unqueued, this is deprecated
[   74.222626] spi_davinci 21000600.spi: Controller at 0xf007c600
[   74.228780] spi_davinci 21000800.spi: master is unqueued, this is deprecated
[   74.235855] spi_davinci 21000800.spi: Controller at 0xf007e800
[   74.242878] tun: Universal TUN/TAP device driver, 1.6
[   74.247945] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   74.254693] keystone-netcp 2090000.netcp: number of serdeses 1
[   74.260559] keystone-netcp 2090000.netcp: Missing cpts_clock_mult property in the DT.
[   74.268416] keystone-netcp 2090000.netcp: Missing cpts_clock_shift property in the DT.
[   74.276361] keystone-netcp 2090000.netcp: Missing cpts_clock_div property in the DT.
[   74.285070] keystone-netcp 2090000.netcp: cpsw serdes 0 config done lanes(mask) 0xf
[   74.293644] keystone-netcp 2090000.netcp: Created interface "eth0"
[   74.299850] keystone-netcp 2090000.netcp: dma_chan_name nettx0
[   74.306582] keystone-netcp 2090000.netcp: Created interface "eth1"
[   74.312788] keystone-netcp 2090000.netcp: dma_chan_name nettx1
[   74.319488] keystone-netcp 2090000.netcp: Created interface "eth2"
[   74.325695] keystone-netcp 2090000.netcp: dma_chan_name nettx2
[   74.332411] keystone-netcp 2090000.netcp: Created interface "eth3"
[   74.338616] keystone-netcp 2090000.netcp: dma_chan_name nettx3
[   74.344601] keystone-netcp 2090000.netcp: pdsp 0 firmware: keystone/pa_pdsp0_classify1.fw
[   74.352809] keystone-netcp 2090000.netcp: pdsp 1 firmware: keystone/pa_pdsp1_classify1.fw
[   74.361018] keystone-netcp 2090000.netcp: pdsp 2 firmware: keystone/pa_pdsp2_classify1.fw
[   74.369226] keystone-netcp 2090000.netcp: pdsp 3 firmware: keystone/pa_pdsp3_classify2.fw
[   74.377433] keystone-netcp 2090000.netcp: pdsp 4 firmware: keystone/pa_pdsp45_pam.fw
[   74.385205] keystone-netcp 2090000.netcp: pdsp 5 firmware: keystone/pa_pdsp45_pam.fw
[   74.393158] keystone-netcp 2090000.netcp: could not find interface 2 node in device tree
[   74.401279] keystone-netcp 2090000.netcp: Attach of module keystone-qos declined with -19
[   74.409487] keystone-netcp 2090000.netcp: could not find interface 3 node in device tree
[   74.417607] keystone-netcp 2090000.netcp: Attach of module keystone-qos declined with -19
[   74.425830] keystone-netcp 2090000.netcp: Attach of module keystone-sa declined with -19
[   74.433950] keystone-netcp 2090000.netcp: Attach of module keystone-sa declined with -19
[   74.443162] dwc3 2690000.dwc3: no usb2 phy configured
[   74.448238] platform 2690000.dwc3: Driver dwc3 requests probe deferral
[   74.455293] usbcore: registered new interface driver usb-storage
[   74.461783] mousedev: PS/2 mouse device common for all mice
[   74.467598] i2c /dev entries driver
[   74.471763] watchdog 22f0080.wdt: heartbeat 60 sec
[   74.487755] keystone-crypto 20c0000.crypto: crypto accelerator enabled
[   74.494679] usbcore: registered new interface driver usbhid
[   74.500269] usbhid: USB HID core driver
[   74.504464]  remoteproc0: 2620040.dsp0 is available
[   74.509356]  remoteproc0: Note: remoteproc is still under development and considered experimental.
[   74.518345]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[   74.528760]  remoteproc0: no firmware found
[   74.533086] rproc-user 2620040.dsp0: registered misc device dsp0
[   74.539376]  remoteproc1: 2620044.dsp1 is available
[   74.544268]  remoteproc1: Note: remoteproc is still under development and considered experimental.
[   74.553259]  remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[   74.563675]  remoteproc1: no firmware found
[   74.567994] rproc-user 2620044.dsp1: registered misc device dsp1
[   74.574287]  remoteproc2: 2620048.dsp2 is available
[   74.579178]  remoteproc2: Note: remoteproc is still under development and considered experimental.
[   74.588168]  remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[   74.598580]  remoteproc2: no firmware found
[   74.602897] rproc-user 2620048.dsp2: registered misc device dsp2
[   74.609180]  remoteproc3: 262004c.dsp3 is available
[   74.614073]  remoteproc3: Note: remoteproc is still under development and considered experimental.
[   74.623064]  remoteproc3: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[   74.633475]  remoteproc3: no firmware found
[   74.637798] rproc-user 262004c.dsp3: registered misc device dsp3
[   74.644084]  remoteproc4: 2620050.dsp4 is available
[   74.648975]  remoteproc4: Note: remoteproc is still under development and considered experimental.
[   74.657965]  remoteproc4: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[   74.668376]  remoteproc4: no firmware found
[   74.672700] rproc-user 2620050.dsp4: registered misc device dsp4
[   74.678995]  remoteproc5: 2620054.dsp5 is available
[   74.683888]  remoteproc5: Note: remoteproc is still under development and considered experimental.
[   74.692879]  remoteproc5: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[   74.703293]  remoteproc5: no firmware found
[   74.707613] rproc-user 2620054.dsp5: registered misc device dsp5
[   74.713901]  remoteproc6: 2620058.dsp6 is available
[   74.718792]  remoteproc6: Note: remoteproc is still under development and considered experimental.
[   74.727782]  remoteproc6: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[   74.738199]  remoteproc6: no firmware found
[   74.742524] rproc-user 2620058.dsp6: registered misc device dsp6
[   74.748831]  remoteproc7: 262005c.dsp7 is available
[   74.753724]  remoteproc7: Note: remoteproc is still under development and considered experimental.
[   74.762714]  remoteproc7: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[   74.773125]  remoteproc7: no firmware found
[   74.777449] rproc-user 262005c.dsp7: registered misc device dsp7
[   74.783495] rproc-user dspmem.10: kick gpio
[   74.787817] rproc-user dspmem.10: registered misc device dspmem
[   74.794004] ipip: IPv4 over IPv4 tunneling driver
[   74.799129] gre: GRE over IPv4 demultiplexor driver
[   74.804022] ip_gre: GRE over IPv4 tunneling driver
[   74.809639] TCP: cubic registered
[   74.812961] Initializing XFRM netlink socket
[   74.817823] NET: Registered protocol family 10
[   74.823383] NET: Registered protocol family 17
[   74.827851] NET: Registered protocol family 15
[   74.832351] Bridge firewalling registered
[   74.836375] 8021q: 802.1Q VLAN Support v1.8
[   74.842425] sctp: Hash tables configured (established 32768 bind 37449)
[   74.849428] NET: Registered protocol family 41
[   74.854013] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[   74.861714] Registering SWP/SWPB emulation handler
[   75.068834] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[   75.074351] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[   75.082743] xhci-hcd xhci-hcd.0.auto: irq 425, io mem 0x02690000
[   75.088836] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   75.095648] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   75.102896] usb usb1: Product: xHCI Host Controller
[   75.107788] usb usb1: Manufacturer: Linux 3.10.72-rt77_BBM_V1.0.0 xhci-hcd
[   75.114687] usb usb1: SerialNumber: xhci-hcd.0.auto
[   75.120019] hub 1-0:1.0: USB hub found
[   75.123788] hub 1-0:1.0: 1 port detected
[   75.127908] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[   75.133418] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[   75.141173] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[   75.147984] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   75.155231] usb usb2: Product: xHCI Host Controller
[   75.160123] usb usb2: Manufacturer: Linux 3.10.72-rt77_BBM_V1.0.0 xhci-hcd
[   75.167020] usb usb2: SerialNumber: xhci-hcd.0.auto
[   75.172316] hub 2-0:1.0: USB hub found
[   75.176080] hub 2-0:1.0: 1 port detected
[   75.180448] UBI: attaching mtd2 to ubi0
[   78.761059] UBI: scanning is finished
[   78.764971] ai->vols_found 2
[   78.767856] ai->highest_vol_id 1
[   78.771089] ai->corr_peb_count 0
[   78.774322] ai->empty_peb_count 0
[   78.777641] ai->bad_peb_count 1
[   78.780786] ai->is_empty 0
[   78.783497] UBI error: ubi_read_volume_table: the layout volume was not found
[   78.793509] UBI error: ubi_attach_mtd_dev: failed to attach mtd2, error -22
[   78.800521] UBI error: ubi_init: cannot attach mtd2
[   78.809613] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
[   78.817217] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0): error -19
[   78.825247] Please append a correct "root=" boot option; here are the available partitions:
[   78.833637] 1f00            1024 mtdblock0  (driver?)
[   78.838709] 1f01             512 mtdblock1  (driver?)
[   78.843783] 1f02         1047040 mtdblock2  (driver?)
[   78.848854] 1f03             512 mtdblock3  (driver?)
[   78.853927] 1f04           15872 mtdblock4  (driver?)
[   78.858999] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   78.859003] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.10.72-rt77_BBM_V1.0.0 #5
[   78.859028] [<c0015c48>] (unwind_backtrace+0x0/0xf8) from [<c0011cdc>] (show_stack+0x10/0x14)
[   78.859040] [<c0011cdc>] (show_stack+0x10/0x14) from [<c05192b0>] (panic+0x98/0x1f8)
[   78.859050] [<c05192b0>] (panic+0x98/0x1f8) from [<c074cfa8>] (mount_block_root+0x184/0x230)
[   78.859058] [<c074cfa8>] (mount_block_root+0x184/0x230) from [<c074d1f4>] (prepare_namespace+0x8c/0x18c)
[   78.859064] [<c074d1f4>] (prepare_namespace+0x8c/0x18c) from [<c074cc48>] (kernel_init_freeable+0x180/0x1c8)
[   78.859075] [<c074cc48>] (kernel_init_freeable+0x180/0x1c8) from [<c0512760>] (kernel_init+0x8/0xe4)
[   78.859081] [<c0512760>] (kernel_init+0x8/0xe4) from [<c000ddb8>] (ret_from_fork+0x14/0x3c)
[   78.859087] CPU3: stopping
[   78.859091] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.10.72-rt77_BBM_V1.0.0 #5
[   78.859102] [<c0015c48>] (unwind_backtrace+0x0/0xf8) from [<c0011cdc>] (show_stack+0x10/0x14)
[   78.859110] [<c0011cdc>] (show_stack+0x10/0x14) from [<c0013f0c>] (handle_IPI+0xfc/0x160)
[   78.859115] [<c0013f0c>] (handle_IPI+0xfc/0x160) from [<c000858c>] (gic_handle_irq+0x54/0x5c)
[   78.859123] [<c000858c>] (gic_handle_irq+0x54/0x5c) from [<c051fd40>] (__irq_svc+0x40/0x84)
[   78.859125] Exception stack(0xee107f98 to 0xee107fe0)
[   78.859128] 7f80:                                                       00000003 00000000
[   78.859132] 7fa0: 00000a4e 00000000 ee106000 ee106000 ee106000 c07a7098 c07ffa30 c07ff25d
[   78.859136] 7fc0: c05274a0 00000000 00000000 ee107fe0 c000ef34 c000ef38 60000013 ffffffff
[   78.859142] [<c051fd40>] (__irq_svc+0x40/0x84) from [<c000ef38>] (arch_cpu_idle+0x28/0x30)
[   78.859151] [<c000ef38>] (arch_cpu_idle+0x28/0x30) from [<c005c830>] (cpu_startup_entry+0xa0/0x238)
[   78.859157] [<c005c830>] (cpu_startup_entry+0xa0/0x238) from [<80515ac4>] (0x80515ac4)
[   78.859160] CPU1: stopping
[   78.859163] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.10.72-rt77_BBM_V1.0.0 #5
[   78.859173] [<c0015c48>] (unwind_backtrace+0x0/0xf8) from [<c0011cdc>] (show_stack+0x10/0x14)
[   78.859180] [<c0011cdc>] (show_stack+0x10/0x14) from [<c0013f0c>] (handle_IPI+0xfc/0x160)
[   78.859184] [<c0013f0c>] (handle_IPI+0xfc/0x160) from [<c000858c>] (gic_handle_irq+0x54/0x5c)
[   78.859190] [<c000858c>] (gic_handle_irq+0x54/0x5c) from [<c051fd40>] (__irq_svc+0x40/0x84)
[   78.859192] Exception stack(0xee103f98 to 0xee103fe0)
[   78.859195] 3f80:                                                       00000001 00000000
[   78.859199] 3fa0: 00001a0e 00000000 ee102000 ee102000 ee102000 c07a7098 c07ffa30 c07ff25d
[   78.859202] 3fc0: c05274a0 00000000 00000000 ee103fe0 c000ef34 c000ef38 60000013 ffffffff
[   78.859208] [<c051fd40>] (__irq_svc+0x40/0x84) from [<c000ef38>] (arch_cpu_idle+0x28/0x30)
[   78.859215] [<c000ef38>] (arch_cpu_idle+0x28/0x30) from [<c005c830>] (cpu_startup_entry+0xa0/0x238)
[   78.859219] [<c005c830>] (cpu_startup_entry+0xa0/0x238) from [<80515ac4>] (0x80515ac4)
[   78.859222] CPU0: stopping
[   78.859226] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10.72-rt77_BBM_V1.0.0 #5
[   78.859236] [<c0015c48>] (unwind_backtrace+0x0/0xf8) from [<c0011cdc>] (show_stack+0x10/0x14)
[   78.859242] [<c0011cdc>] (show_stack+0x10/0x14) from [<c0013f0c>] (handle_IPI+0xfc/0x160)
[   78.859247] [<c0013f0c>] (handle_IPI+0xfc/0x160) from [<c000858c>] (gic_handle_irq+0x54/0x5c)
[   78.859252] [<c000858c>] (gic_handle_irq+0x54/0x5c) from [<c051fd40>] (__irq_svc+0x40/0x84)
[   78.859254] Exception stack(0xc079df68 to 0xc079dfb0)
[   78.859258] df60:                   00000000 00000000 00001640 00000000 c079c000 c079c000
[   78.859261] df80: c079c000 c07a7098 c07ffa30 c07ff25d c05274a0 00000000 00000000 c079dfb0
[   78.859264] dfa0: c000ef34 c000ef38 60000113 ffffffff
[   78.859270] [<c051fd40>] (__irq_svc+0x40/0x84) from [<c000ef38>] (arch_cpu_idle+0x28/0x30)
[   78.859276] [<c000ef38>] (arch_cpu_idle+0x28/0x30) from [<c005c830>] (cpu_startup_entry+0xa0/0x238)
[   78.859283] [<c005c830>] (cpu_startup_entry+0xa0/0x238) from [<c074ca70>] (start_kernel+0x300/0x358)
[   78.859288] [<c074ca70>] (start_kernel+0x300/0x358) from [<80008084>] (0x80008084)

Please help me sort out this issue. We struck here from many days.

With regards,

Yashavanth

Part Number:BEAGLEBK

Tool/software: Linux

I am working on BBB adding new h/w configurations with device tree. I do not want everytime to build a new image and again flash it to test a new feature(a very long process indeed). So what I was doing was updating the dts file and then creating a new dtb file with the latest features and using ssh to transfer the new dtb file to the boot folder of BBB(in other words replacing the old dtb file of BBB with a new one).
After doing all this, I performed a sync operation followed by a reboot.
Shouldn't this start the BBB with added features? Am I doing it the right way?

Part Number:AM3356

Tool/software: Linux

Hi, can I know how to let AM3356 USB2.0 Host port to output test pattern required by USB 2.0 compliance test in Linux?

Part Number:AM3357

Tool/software: TI-RTOS

Hello.

I'm building my application outside of CCS, by invoking XS command.

I see following message during evaluation of cfg file:

cd /home/wiesniak/projects/cmpc_cpu/cmake-build-debug/platform/Sysbios_psdk_AM335x && /home/rnd_share/ti//psdk_rtos_am335x_5_02_00_10_gh02/xdctools_3_50_08_24_core/xs --xdcpath="/home/wiesniak/projects/cmpc_cpu/platform/cmpc30/packages;/home/wiesniak/projects/cmpc_cpu/platform/Sysbios_psdk_AM335x;/home/rnd_share/ti//psdk_rtos_am335x_5_02_00_10_gh02/bios_6_73_01_01/packages/;/home/rnd_share/ti//psdk_rtos_am335x_5_02_00_10_gh02/pdk_am335x_1_0_13/packages/;/home/rnd_share/ti//psdk_rtos_am335x_5_02_00_10_gh02/ndk_3_40_01_01/packages/;/home/rnd_share/ti//psdk_rtos_am335x_5_02_00_10_gh02/edma3_lld_2_12_05_30C/packages/" xdc.tools.configuro -o configPkg -t gnu.targets.arm.A8F -p huettinger.cmpc30 -r debug -c /home/rnd_share/gcc_arm//gcc-arm-none-eabi-6-2017-q1-update app_dbg.cfg
making package.mak (because of package.bld) ...
configuring app_dbg.xa8fg from package/cfg/app_dbg_pa8fg.cfg ...
generating custom ti.sysbios library makefile ...
Inside EDMA3 Drv Sample getLibs
    will link with ti.sdo.edma3.drv.sample:lib/am335x-evm/a8/debug/edma3_lld_drv_sample.aa8fg
    Linking with library ti.board:./lib/cmpc30AM335x/a8/release/ti.board.aa8fg
    Linking with library ti.drv.spi:./lib/am335x/a8/release/ti.drv.spi.aa8fg
    Linking with library ti.drv.icss_emac:./lib/a8/release/ti.drv.icss_emac.aa8fg
    Linking with library ti.csl:./lib/am335x/a8/release/ti.csl.aa8fg
    Linking with library ti.drv.gpio:./lib/a8/release/ti.drv.gpio.aa8fg
    Linking with library ti.drv.pruss:./lib/a8/release/ti.drv.pruss.aa8fg
    Linking with library ti.drv.i2c:./lib/a8/release/ti.drv.i2c.aa8fg
    Linking with library ti.drv.uart:./lib/a8/release/ti.drv.uart.aa8fg
    Linking with library ti.osal:./lib/tirtos/a8/release/ti.osal.aa8fg
Inside EDMA3 Drv getLibs
    will link with ti.sdo.edma3.drv:lib/a8/debug/edma3_lld_drv.aa8fg
Inside EDMA3 RM getLibs
    will link with ti.sdo.edma3.rm:lib/am335x-evm/a8/debug/edma3_lld_rm.aa8fg

As you can see I selected debug build, but (-r debug) but most libraries selected by xs are release.

How can I convince build system to use debug libraries ?

Greg.

Part Number:TDA2EXEVM

Tool/software: TI-RTOS

Hi,

I want to build the opencvcanny use case which based on VSDK v3.6 using "tda2xx_evm_bios_all" configuration with ENABLE_OPENCV=yes option.

SDK version: v0306

Config: tda2xx_evm_bios_all

Platform: TDA2XX_EVM / rtos

But it outputs the following library linking error when run "make vision_sdk" command.

I know that both libraries (libm.lib and rts6600_elf.lib) default support from SDK.

Why does it result in the error of redefinition (atan2)?

Could you help teach me how to solve the problem? Thanks.

BRs,

Sam Hsieh

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

error: symbol "atan2" redefined: first defined in
   "/home/sam/test/TI_SDK_VISION_V03_06/ti_components/open_compute/opencl_rtos_
   am57xx_01_01_10_00/packages/ti/opencl/usr/share/ti/opencl/libm.lib<e_atan2.o
   >"; redefined in
   "/home/sam/test/TI_SDK_VISION_V03_06/ti_components/cg_tools/linux/ti-cgt-c60
   00_8.2.4/lib/rts6600_elf.lib<atan2.obj>"
error: symbol "cosh" redefined: first defined in
   "/home/sam/test/TI_SDK_VISION_V03_06/ti_components/open_compute/opencl_rtos_
   am57xx_01_01_10_00/packages/ti/opencl/usr/share/ti/opencl/libm.lib<e_cosh.o>
   "; redefined in
   "/home/sam/test/TI_SDK_VISION_V03_06/ti_components/cg_tools/linux/ti-cgt-c60
   00_8.2.4/lib/rts6600_elf.lib<cosh.obj>"

Tool/software: Linux

Hi,

I'm testing TIDL OD usecase in linux.

The format of chain is same with TIDL OD in BIOS except for TIDL Preprocessing. (It is running on DSP)

The problem is the performance of that converted usecase is different each time when i use another video.

The below video is normal case.

(Please visit the site to view this video)

And this is abnormal case. The usecase is running but all frames are dropped after showing some initial frames.

(Please visit the site to view this video)

And this is normal case that uses same video with upper case.

(Please visit the site to view this video)

I don't know why the results are different even though the input video was same.

Could you suggest any cause of this problem or solution?

Thanks & Regards,

Yoo

Part Number:TMS320C6748

Hi TI Team,

    Would you help to provide a detail  DMA configuration for reading data form eMMC?

   for example:

   1. the OPT channel options parametters

   2. SCR

   3. A_B_CNT

    4. DST

   5. SRC_DST_BIDX

    6. LINK_BCNTRLD

    7. SRC_DST_CIDX

    8. CCNT

   I have tried to set a different set for these,but I can't read the correclty data form DMA.

   I am looking forwrad for your response.

thanks.

Part Number:OMAP-L138

Tool/software: Code Composer Studio

Hi

I had connected device true UART to do flashing but i face this issue when i try to load in bin file., it will stop at Performing Start-Word Sync...for long time until terminate the port.

May i know this because of magic word or my .bin issue? How to verify this issue?

Log as below

(File IO): Read 308456 bytes from file C:\flasher\fzap_special_ram_dloader_hwinit_factory_128MB_rls.bin.
(Serial Port): Opening COM4 at 115200 baud...
(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(Serial Port): Read error! (The operation has timed out.)
(AIS Parse): I/O Error in read!
(AIS Parse): Boot aborted.
(Serial Port): Closing COM4.

Thanks

Part Number:PROCESSOR-SDK-AM437X

Tool/software: TI-RTOS

Hello Everyone,

I am trying to  run acontis ethercat master code  on my AM437x board. The RJ-45 cable connected between AM437x Ethernet port 0 (ETH0) of  and kollmorgan drive. 

CCS Version: 6.2.0.00050 

sdk：processor_sdk_rtos_am437x_3_03_00_06

sys\bios version 6.46.4.53

ethercat slave: kollmorgan drive(S700)

I download ESI.XML file from kollmorgan site and convert this xml file into c as per given in "http://software.acontis.com/EC-Master/2.9/EC-Master_V2.9-ClassB.pdf"(chapter 2.4.1.4.2).

but I got following output on Putty from serial:

SYS/BIOS EcMasterDemo CPSW Sample application
0000000057: Full command line: -auxclk 2000 -v 4 -t 10000 -perf -cpsw 1 1 0 m am 437x-idk
0000000057: Run demo now with cycle time 2000 usec
0000000057: Using AuxClock
0000000057: OsMeasGet100kHzFrequency(): 600 MHz
0000000057: ==========================
0000000057: Initialize EtherCAT Master
0000000057: ==========================
0000000057: EC-Master V3.0.1.12 (Protected) for SYSBIOS Copyright acontis techno logies GmbH @ 2018
0000000063: Port 1, Prio 0, Flags [Polling] [Master], Phy 0, PhyInterface 8, MA C 60:64:05:05:65:5b

0000000063: DMA buffer from uncached ram at 0x80391078
0000000072: VirtAddr: RegBase 0x4a100000, DmaDtorBase 0x4a102000, DmaBase 0x8039 2000
0000000072: PhysAddr: RegBase 0x4a100000, DmaDtorBase 0x4a102000, DmaBase 0x8039 2000
0000000079: CPSW3G found.
0000000079: HW-Id: 0x0019, RTL: 0, Major: 1, Minor: 0xf
0000000079: Tx Version 0x00180109
0000000079: Rx Version 0x00180109
0000000079: CPDMA_Rx_Ch_Map 0x77770000
0000000079: MDIO Version 0x40070106
0000000080: mdio ACK missing
0000000080: mdio reg 2 read error
0000000080: PHY initialization failed
0000000080: EtherCAT network adapter MAC: 60-64-05-05-65-5B
0000000084: CEcConfigXpat::StartElementHandler() - invalid first tag, expected E therCATConfig
0000000084: CEcConfigXpat::Init() Parse error at line 4 col 0
out of memory
0000000084: Data Length 691525 CurrentLength 6912
0000000084: ecatInitMaster() Cannot create EtherCAT device!
0000000084: ConfigLoad() Cannot initialize Master Stack!
0000000084: Disable running RX-DMA
0000000084: RX+TX DMA disabled. Delay 500
0000000084: ConfigureMaster(2, --, 691525) = ERROR: Wrong format of master XML f ile
0000000084: Cannot configure EtherCAT-Master: ERROR: Wrong format of master XML file (0x9811001b))
0000000084: ========================
0000000084: Shutdown EtherCAT Master
0000000084: ========================
0000000085: ==================================================================== ========
0000000085: PerfMsmt 'JOB_ProcessAllRxFrames' (min/avg/max) [usec]: 0.7/ 6. 5/ 6.6
0000000085: PerfMsmt 'JOB_SendAllCycFrames ' (min/avg/max) [usec]: 0.3/ 3. 4/ 3.5
0000000085: PerfMsmt 'JOB_MasterTimer ' (min/avg/max) [usec]: 0.3/ 20. 7/ 21.2
0000000085: PerfMsmt 'JOB_SendAcycFrames ' (min/avg/max) [usec]: 0.3/ 2. 8/ 2.9
0000000085: PerfMsmt 'Cycle Time ' (min/avg/max) [usec]: 388.5/ 413. 6/2001.9
0000000085: PerfMsmt 'myAppWorkPd ' (min/avg/max) [usec]: 0.8/ 1. 9/ 1.9
0000000094: EcMasterDemo stop.

So,Is anything going wrong? Please, suggest solution.

Thanks

Part Number:TMS320C6678

Hi,

We are trying to bring up TMS320C6678 - Evaluation Module with XDS560v2 Emulator & IP Address Acquisition is failing due to which we are unable to progress.

Kindly help on this.

Best Regards,

Umamahesh

Tool/software: TI-RTOS

Could anyone please help me out to get the USB-RNDIS API's for UCOS2 OS???

Part Number:DRA746

Hi,

We want to try out python on PSDK Linux. Is there any python library which is available or can be cross compiled for running python codes? Please help.

Thanks in advance,

Srinivasan

Part Number:AM4379

I am using an AM4379 on an AM437x-IDK-EVM to boot over the network interface, ETH0. The configuration pins on the AM4379 have been modified (using the 0ohm resisters on the board.) for the following configuration.

The AM437x-IDK-EVM board is connected to a network interface with bootp server (Ubuntu host) that has dhcpd and tftp sever started. The dhcp conf file is shown below:

When the AM327X-IDK-EVM is powered on it makes a bootp request and the bootp server responds but the AM437x-IDK-EVM does request the u-boot-spl.bin file from the tftp server? 

I have the WireShark capture of the two packets highlighted above, but I do not seem be able to attach it to this message?

I have used this Ubuntu server to boot another AM437x-IDK-EVM and it worked as expected, this EVM however appears to be interfacing/booting from the server differently? 

Is there a field in the Boot Reply that I may be missing that is not allowing this device to boot? (for example another Next Server type field or a Tftp server field?)

Thanks in advance,

Rob