Part Number:PROCESSOR-SDK-AM65X

Tool/software: Linux

 Hi,

When I tried to build linux , it got stuck at

cloning repo meta-arago  this line.

./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-05.03.00.07-config.txt

I typed this command at last. While cloning into differnet repos it is stuck. From git it is fetching. But for arago repos it  is not cloning.

Is there any setting to changed in host system ?

Please help me on this.

Thanks and Regards,

Vishnu

Part Number:AM5718

Tool/software: Linux

Hi! Is there support for Alpine Linux for the AM57 platform **, if not, why, and support is expected? Thanks!

Part Number:AM3352

Tool/software: Linux

Hi Sir 

We used latest SDK in TI SK-EVM for test.

We used one USB device to let usb over-current phenomenon happened. 

         root@am335x-evm:~# [ 55.776691] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3, port1 00080108

And then unplug USB device. It seems we need to use below command to let USB port work normally.

    https://e2e.ti.com/support/processors/f/791/p/414696/1912906

   echo '47401c00.usb' > /sys/bus/platform/drivers/musb-dsps/unbind
   echo '47401c00.usb' > /sys/bus/platform/drivers/musb-dsps/bind

Does TI USB driver support recovery way automatically if it meets overcurrent issue ?

Otherwise, we may need to use above command to recover USB function in TI SK EVM ?

please advise

BR

Yimin

Part Number:AM5718

Tool/software: Linux

Hi!

1. I can not find an assembly from scratch for the distribution of Arago

2. Is it possible Arago to build a file system in RAM?

3. Does the current SDK for AM5718 use flash memory often?

4. What is the life cycle of flash memory on the current SDK.

Thanks!

Part Number:TMS320C6747

TMS320C6747DZKB3 + spartan3e (XC3SD1800A-4CSG484C) + flash (S29JL032J70TFI010) is running on one board. 

Development tools XDS510US and TMDSCCS-ALLN01-v4.0 (Code Composer Studio IDE V4) at this time, I do not have it now, but I have most of the source files.
Next time, I would like to continue with the development of new simple functions. Can I use CCS v9 and XDS 200 USB? , Can you write to the external flash?

Suddenly the job has fallen, so I am embarrassed and angry. Thank you in advance.

Part Number:DRA745

Tool/software: Linux

Hi,expert

I use vsdk0305 to run vdrm.

In customer board：

stop kmscube and run kmscube, found below error: could you please help to check?

root@dra7xx-evm:/opt/vision_sdk# 
root@dra7xx-evm:/opt/vision_sdk# /etc/init.d/weston stop
Stopping Weston
Terminated
root@dra7xx-evm:/opt/vision_sdk# /etc/init.d/[ 59.798957] random: nonblocking pool is initialized

root@dra7xx-evm:/opt/vision_sdk# 
root@dra7xx-evm:/opt/vision_sdk# 
root@dra7xx-evm:/opt/vision_sdk# 
root@dra7xx-evm:/opt/vision_sdk# 
root@dra7xx-evm:/opt/vision_sdk# kmscube -d /dev/dri/card0
### Display [0]: CRTC = 26, Connector = 24, format = 0x34325258
Mode chosen [640x1440] : Clock => 57096, Vertical refresh => 60, Type => 72
Horizontal => 640, 646, 647, 650, 0
Vertical => 1440, 1454, 1457, 1464, 0
### Primary display => ConnectorId = 24, Resolution = 640x1440
loaded module : gbm_pvr.so
found valid GBM backend : gbm_pvr.so
PVR:(Error): OpenServices: PVRDRMOpenRender failed [0, ]
PVR:(Error): PVRSRVConnect: Unable to open connection. [0, ]
PVR:(Error): Couldn't connect to services [0, ]
failed to initialize
failed to initialize EGL

Best regards,

Fredy

Part Number:DRA80M

Hi,

Could you answer the questions I marked as green below?

Part Number:TMDSIDK574

Tool/software: Linux

Hi!

I have the AM574x Industrial Development Kit (IDK), sdk 5.01, Linux Arago.

The question is from here 

So, when I setup a single prp interface, I have use 2 different firmware files.

Then, I have to setup 2 prp interfaces. But there are only 2 different firmware files in sdk: am57xx-pru0-pruprp-fw.elf and am57xx-pru1-pruprp-fw.elf.

Do I need in 4 different firmware files for 2 prp interfaces?

Part Number:TDA2PXEVM

Tool/software: TI-RTOS

Dear,

The TDA2Px have 2 EVEs.

In usecase of the tidl_DO, it need 4 EVEs.

I removed the chain related with EVE3 and EVE4.

After I run the modified usecasen the error is shwon like below.

Assertion @ Line: 191 in system_linkApi.c: procId < SYSTEM_PROC_MAX : failed !!!

Is this usecase need for EVE3 and EVE4?

Cannot be run with TDA2Px?

My usecase is here.

UseCase: chains_tidlOD

//NullSource -> Decode -> VPE -> Dup
IssCapture -> IssM2mIsp -> IssM2mSimcop -> Dup

Dup -> Merge

Dup -> Alg_tidlpreproc (A15)

Alg_tidlpreproc (A15) -> Alg_tidl_Eve1 (EVE1)
Alg_tidlpreproc (A15) -> Alg_tidl_Eve2 (EVE2)

Alg_tidl_Eve1 (EVE1) -> Merge_OD (DSP1)
Alg_tidl_Eve2 (EVE2) -> Merge_OD (DSP1)
Merge_OD (DSP1) -> Alg_tidl_Dsp (DSP1) -> Merge

Merge -> Sync -> Alg_tiop (DSP1) -> Alg_ObjectDraw -> Display

GrpxSrc -> Display_Grpx

Thanks,

Heechang

Part Number:PROCESSOR-SDK-AM437X

Tool/software: TI-RTOS

Hello,

    We have Am437x board interfaced with kollmorgen drive through ethercat cable. we get following output on putty during power on board:

Trying to boot from MMC2

SPL: Please implement spl_start_uboot() for your board

SPL: Direct Linux boot not active!

reading u-boot.img

reading u-boot.img

reading u-boot.img

reading u-boot.img

U-Boot 2016.05 (Mar 01 2017 - 14:44:57 +0800)

I2C: ready

DRAM: 512 MiB

PMIC: TPS65218

MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1

Card did not respond to voltage select!

** Bad device mmc 0 **

Using default environment

Net: <ethaddr> not set. Validating first E-fuse MAC

Could not get PHY for cpsw: addr 0

Could not get PHY for cpsw: addr 1

Could not get PHY for cpsw: addr 1

Could not get PHY for cpsw: addr 6

cpsw, usb_ether

Hit any key to stop autoboot: 0

Card did not respond to voltage select!

Card did not respond to voltage select!

Card did not respond to voltage select!

Card did not respond to voltage select!

switch to partitions #0, OK

mmc1(part 0) is current device

switch to partitions #0, OK

mmc1(part 0) is current device

SD/MMC found on device 1

4527760 bytes read in 519 ms (8.3 MiB/s)

48868 bytes read in 16 ms (2.9 MiB/s)

Booting from mmc1 ...

Kernel image @ 0x82000000 [ 0x000000 - 0x451690 ]

## Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000

Loading Device Tree to 8fff1000, end 8ffffee3 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0

[ 0.000000] Initializing cgroup subsys cpu

[ 0.000000] Initializing cgroup subsys cpuacct

[ 0.000000] Linux version 4.1.18 (sunny@myir-server1) (gcc version 5.4.0 (Buildroot 2017.02-git-00458-g3a0e257) ) #1 PREEMPT Wed Mar 1 14:42:44 CST 2017

[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d

[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

[ 0.000000] Machine model: MYIR-TECH MYD_C437X_PRU Industrial Development Kit

[ 0.000000] cma: Reserved 24 MiB at 0x9e800000

[ 0.000000] Memory policy: Data cache writeback

[ 0.000000] CPU: All CPU(s) started in SVC mode.

[ 0.000000] AM437x ES1.2 (neon )

[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129920

[ 0.000000] Kernel command line: console=ttyO0,115200n8 root=PARTUUID=00000000-02 rw rootfstype=ext4 rootwait

[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)

[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

[ 0.000000] Memory: 484792K/524288K available (6407K kernel code, 258K rwdata, 2392K rodata, 276K init, 234K bss, 14920K reserved, 24576K cma-reserved, 0K highmem)

[ 0.000000] Virtual kernel memory layout:

[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)

[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)

[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)

[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)

[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)

[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)

[ 0.000000] .text : 0xc0008000 - 0xc08a005c (8801 kB)

[ 0.000000] .init : 0xc08a1000 - 0xc08e6000 ( 276 kB)

[ 0.000000] .data : 0xc08e6000 - 0xc0926bf0 ( 259 kB)

[ 0.000000] .bss : 0xc0929000 - 0xc0963bec ( 235 kB)

[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

[ 0.000000] Preemptible hierarchical RCU implementation.

[ 0.000000] Additional per-CPU info printed with stalls.

[ 0.000000] NR_IRQS:16 nr_irqs:16 16

[ 0.000000] L2C: platform modifies aux control register: 0x0e030000 -> 0x3e430000

[ 0.000000] L2C: DT/platform modifies aux control register: 0x0e030000 -> 0x3e430000

[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9

[ 0.000000] OMAP L2C310: ROM does not support power control setting

[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines

[ 0.000000] L2C-310 dynamic clock gating disabled, standby mode disabled

[ 0.000000] L2C-310 cache controller enabled, 16 ways, 256 kB

[ 0.000000] L2C-310: CACHE_ID 0x410000c9, AUX_CTRL 0x7e430000

[ 0.000000] OMAP clockevent source: timer2 at 24000000 Hz

[ 0.000013] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns

[ 0.000035] clocksource timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns

[ 0.000047] OMAP clocksource: timer1 at 24000000 Hz

[ 0.001207] Console: colour dummy device 80x30

[ 0.001244] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)

[ 0.090229] pid_max: default: 32768 minimum: 301

[ 0.090341] Security Framework initialized

[ 0.090392] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)

[ 0.090406] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)

[ 0.091176] Initializing cgroup subsys blkio

[ 0.091203] Initializing cgroup subsys memory

[ 0.091256] Initializing cgroup subsys devices

[ 0.091276] Initializing cgroup subsys freezer

[ 0.091293] Initializing cgroup subsys perf_event

[ 0.091323] CPU: Testing write buffer coherency: ok

[ 0.091709] Setting up static identity map for 0x80008200 - 0x80008270

[ 0.093659] devtmpfs: initialized

[ 0.108204] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

[ 0.190569] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns

[ 0.192676] pinctrl core: initialized pinctrl subsystem

[ 0.194044] NET: Registered protocol family 16

[ 0.195861] DMA: preallocated 256 KiB pool for atomic coherent allocations

[ 0.220220] cpuidle: using governor ladder

[ 0.250209] cpuidle: using governor menu

[ 0.252583] omap_l3_noc 44000000.ocp: L3 debug error: target 8 mod:0 (unclearable)

[ 0.252659] omap_l3_noc 44000000.ocp: L3 application error: target 8 mod:0 (unclearable)

[ 0.258158] OMAP GPIO hardware version 0.1

[ 0.259565] omap_gpio 481ae000.gpio: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/gpio3_pins_default, deferring probe

[ 0.259932] omap_gpio 48320000.gpio: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/gpio4_pins_default, deferring probe

[ 0.267859] No ATAGs?

[ 0.267900] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.

[ 0.267913] hw-breakpoint: maximum watchpoint size is 4 bytes.

[ 0.311080] edma 49000000.edma: TI EDMA DMA engine driver

[ 0.315655] vgaarb: loaded

[ 0.316244] SCSI subsystem initialized

[ 0.316935] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/i2c0_pins_default, deferring probe

[ 0.316995] omap_i2c 4819c000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/i2c2_pins_default, deferring probe

[ 0.317140] media: Linux media interface: v0.10

[ 0.317219] Linux video capture interface: v2.00

[ 0.317297] pps_core: LinuxPPS API ver. 1 registered

[ 0.317307] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>

[ 0.317347] PTP clock support registered

[ 0.318242] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400

[ 0.318541] Advanced Linux Sound Architecture Driver Initialized.

[ 0.319382] Switched to clocksource timer1

[ 0.331329] NET: Registered protocol family 2

[ 0.332254] TCP established hash table entries: 4096 (order: 2, 16384 bytes)

[ 0.332321] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)

[ 0.332387] TCP: Hash tables configured (established 4096 bind 4096)

[ 0.332495] UDP hash table entries: 256 (order: 0, 4096 bytes)

[ 0.332518] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

[ 0.332706] NET: Registered protocol family 1

[ 0.333095] RPC: Registered named UNIX socket transport module.

[ 0.333111] RPC: Registered udp transport module.

[ 0.333119] RPC: Registered tcp transport module.

[ 0.333127] RPC: Registered tcp NFSv4.1 backchannel transport module.

[ 0.335713] futex hash table entries: 256 (order: -1, 3072 bytes)

[ 0.335815] audit: initializing netlink subsys (disabled)

[ 0.335877] audit: type=2000 audit(0.310:1): initialized

[ 0.343304] VFS: Disk quotas dquot_6.6.0

[ 0.343537] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

[ 0.345842] NFS: Registering the id_resolver key type

[ 0.345913] Key type id_resolver registered

[ 0.345923] Key type id_legacy registered

[ 0.346003] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.

[ 0.348021] NET: Registered protocol family 38

[ 0.348097] io scheduler noop registered

[ 0.348116] io scheduler deadline registered

[ 0.348189] io scheduler cfq registered (default)

[ 0.350825] pinctrl-single 44e10800.pinmux: 199 pins at pa f9e10800 size 796

[ 0.353543] backlight supply power not found, using dummy regulator

[ 0.355604] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle

[ 0.356949] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled

[ 0.360976] omap_uart 44e09000.serial: no wakeirq for uart0

[ 0.361023] omap_uart 44e09000.serial: No clock speed specified: using default: 48000000

[ 0.361206] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 30, base_baud = 3000000) is a OMAP UART0

[ 1.113815] console [ttyO0] enabled

[ 1.118121] omap_uart 481a6000.serial: no wakeirq for uart3

[ 1.124124] omap_uart 481a6000.serial: No clock speed specified: using default: 48000000

[ 1.132893] 481a6000.serial: ttyO3 at MMIO 0x481a6000 (irq = 31, base_baud = 3000000) is a OMAP UART3

[ 1.143242] omap_uart 481aa000.serial: no wakeirq for uart5

[ 1.149594] [drm] Initialized drm 1.1.0 20060810

[ 1.167389] brd: module loaded

[ 1.176675] loop: module loaded

[ 1.181257] mtdoops: mtd device (mtddev=name/number) must be supplied

[ 1.249446] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6

[ 1.255913] davinci_mdio 4a101000.mdio: detected phy mask ffffffef

[ 1.263473] libphy: 4a101000.mdio: probed

[ 1.267723] davinci_mdio 4a101000.mdio: phy[4]: device 4a101000.mdio:04, driver Atheros 8035 ethernet

[ 1.278328] cpsw 4a100000.ethernet: Missing slave[1] phy_id property

[ 1.285174] cpsw 4a100000.ethernet: Detected MACID = 60:64:05:05:65:5b

[ 1.294146] mousedev: PS/2 mouse device common for all mice

[ 1.300264] i2c /dev entries driver

[ 1.306066] omap_hsmmc 48060000.mmc: Got CD GPIO

[ 1.369814] ledtrig-cpu: registered to indicate activity on CPUs

[ 1.376870] remoteproc0: wkup_m3 is available

[ 1.381675] remoteproc0: Note: remoteproc is still under development and considered experimental.

[ 1.391204] remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.

[ 1.404586] oprofile: no performance counters

[ 1.409337] oprofile: using timer interrupt.

[ 1.414341] Initializing XFRM netlink socket

[ 1.418913] NET: Registered protocol family 17

[ 1.423746] NET: Registered protocol family 15

[ 1.428567] Key type dns_resolver registered

[ 1.433407] omap_voltage_late_init: Voltage driver support not added

[ 1.440606] cpu cpu0: of_pm_voltdm_notifier_register: Failed to get cpu0 regulator/voltdm: -517

[ 1.449912] cpu cpu0: cpu0 clock notifier not ready, retry

[ 1.456130] ThumbEE CPU extension supported.

[ 1.460745] Registering SWP/SWPB emulation handler

[ 1.468645] GPIO line 104 (EMMC_RST) hogged as output/high

[ 1.475426] GPIO line 147 (SelPRUorLCDEN) hogged as output/low

[ 1.481718] GPIO line 149 (SelPRUorLCDSEL) hogged as output/low

[ 1.509620] rtc-rx8025t 0-0032: power-on reset was detected, you may have to readjust the clock

[ 1.518839] rtc-rx8025t 0-0032: a power voltage drop was detected, you may have to readjust the clock

[ 1.528740] rtc-rx8025t 0-0032: bad conditions detected, resetting date

[ 1.536638] rtc-rx8025t 0-0032: rtc core: registered rx8025t as rtc0

[ 1.554776] omap_i2c 44e0b000.i2c: bus 0 rev0.12 at 400 kHz

[ 1.561980] omap_i2c 4819c000.i2c: bus 2 rev0.12 at 100 kHz

[ 1.568995] omap_uart 481aa000.serial: no wakeirq for uart5

[ 1.574994] remoteproc0: powering up wkup_m3

[ 1.579720] omap_uart 481aa000.serial: No clock speed specified: using default: 48000000

[ 1.588438] remoteproc0: Booting fw image am335x-pm-firmware.elf, size 219803

[ 1.596936] remoteproc0: remote processor wkup_m3 is now up

[ 1.602993] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x191

[ 1.610346] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 32, base_baud = 3000000) is a OMAP UART5

[ 1.622174] omap_hsmmc 48060000.mmc: Got CD GPIO

[ 1.699813] cpu cpu0: of_pm_voltdm_notifier_register: Fail calculating voltage latency[1100000<->1325000]:-22

[ 1.710701] cpu cpu0: of_pm_voltdm_notifier_register: Fail calculating voltage latency[1100000<->1325000]:-22

[ 1.723704] rtc-rx8025t 0-0032: setting system clock to 1970-01-01 00:00:00 UTC (0)

[ 1.741054] ALSA device list:

[ 1.744195] No soundcards found.

[ 1.748307] Waiting for root device PARTUUID=00000000-02...

[ 1.773078] mmc1: MAN_BKOPS_EN bit is not set

[ 1.780856] mmc1: new high speed MMC card at address 0001

[ 1.787034] mmcblk0: mmc1:0001 Q2J54A 3.59 GiB

[ 1.792012] mmcblk0boot0: mmc1:0001 Q2J54A partition 1 16.0 MiB

[ 1.798376] mmcblk0boot1: mmc1:0001 Q2J54A partition 2 16.0 MiB

[ 1.805859] mmcblk0: p1 p2

[ 1.873158] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)

[ 1.881830] VFS: Mounted root (ext4 filesystem) on device 179:2.

[ 1.890730] devtmpfs: mounted

[ 1.894345] Freeing unused kernel memory: 276K (c08a1000 - c08e6000)

INIT: version 2.88 booting

[ 2.068797] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro,data=ordered

INIT: Entering runlevel: 3

Starting logging: OK

modprobe: module mmc_core not found in modules.dep

modprobe: module mmc_block not found in modules.dep

modprobe: module omap_hsmmc not found in modules.dep

Populating /dev using udev: [ 2.942005] ov2659 0-0030: Sensor detection failed (3030, 0)

[ 3.248437] PM: bootloader does not support rtc-only!

[ 3.566789] prueth 54400000.pruss:pruss1_eth: port 1: using random MAC addr: ea:83:66:31:90:ab

[ 3.670730] prueth 54400000.pruss:pruss1_eth: port 2: using random MAC addr: 26:d1:41:cb:e6:c6

done

Initializing random number generator... done.

Starting network: [ 4.730356] libphy: PHY not found

[ 4.733936] net eth0: phy not found on slave 1

udhcpc: started, v1.25.1

udhcpc: sending discover

udhcpc: sending discover

udhcpc: sending discover

udhcpc: no lease, failing

FAIL

Starting sshd: OK

Initializing SGX graphics driver PVR:(Error): OpenServices: Cannot open device driver /dev/omapdrm_pvr. [140, /pvr_bridge_u.c]

PVR:(Error): PVRSRVInitSrvConnect: PVRSRVConnect failed [2572, /bridged_pvr_glue.c]

PVR:(Error): SrvInit: PVRSRVInitSrvConnect failed (4) [37, /srvinit.c]

PVR:(Error): main: SrvInit failed (4) [49, /pvrsrvinit.c]

FAIL

please suggest what to be done.

Part Number:AM3354

Tool/software: Linux

Dear TI team, 

We are using a usb hub(Microchip USB2517) connected to our USB0 interface, and then plug a USB storage.

But it cannot be detected. (Linux Kernel: Ubuntu 3.14.26)

Kernel dmesg shows below

   1.154909] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/usb@47400000/usb-phy@47401300[0]'
[    1.154987] 47401300.usb-phy supply vcc not found, using dummy regulator
[    1.166291] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    1.166313] musb-hdrc: MHDRC RTL version 2.0
[    1.166322] musb-hdrc: setup fifo_mode 4
[    1.166341] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    1.166455] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
[    1.173014] musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1
[    1.181415] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.188540] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.196090] usb usb1: Product: MUSB HDRC host driver
[    1.201269] usb usb1: Manufacturer: Linux 3.14.26-dirty musb-hcd
[    1.207545] usb usb1: SerialNumber: musb-hdrc.0.auto
[    1.213732] hub 1-0:1.0: USB hub found
[    1.217716] hub 1-0:1.0: 1 port detected

It seems that USB hub is detected, but USB device is not.

When I changed it to Kernel to 4.10, everything is fine.

dts configuration of USB is as below:

&usb {
        status = "okay";
};

&usb_ctrl_mod {
        status = "okay";
};

&usb0_phy {
        status = "okay";
};

&usb0 {
        status = "okay";
        dr_mode = "host";
};

&cppi41dma  {
        status = "okay";
};

Could you please help us to resolve this?

Thanks.

Part Number:DRA746

Tool/software: Linux

Hello Team,

As per the suggestions given for this E2E "e2e.ti.com/.../764022 we have added "wl_display_dispatch_pending" in our mirror link app.

After that we are facing one issue for the following use case:

1. connect the phone and then open any mirror link app.

2. disconnect the phone

3. connect again and start mirror link app.

For this use case sometime we are getting hazy screen when we starts the app in 3rd step and it hangs there for some time later our mirror link app crashed.

Below is the bcaktrace for crashed app.

(gdb) bt
#0 0xb6a5417c in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#1 0xb6a57f24 in __GI_abort () at abort.c:89
#2 0xb03edce0 in wl_abort (fmt=0xb03ee928 "listener function for opcode %u of %s is NULL\n") at /usr/src/debug/wayland/1.11.0-r0/wayland-1.11.0/src/wayland-util.c:411
#3 0xb03eccd4 in wl_closure_invoke (closure=<optimized out>, flags=<optimized out>, target=0xb6f19ce8 <__stack_chk_guard>, opcode=2874283420, data=0xab57a2a0)
at /usr/src/debug/wayland/1.11.0-r0/wayland-1.11.0/src/connection.c:932
#4 0xb03e9710 in dispatch_event (display=<optimized out>, queue=0xab54982c) at /usr/src/debug/wayland/1.11.0-r0/wayland-1.11.0/src/wayland-client.c:1310
#5 0xb03ea930 in dispatch_queue (queue=0xab54982c, display=0xab5497c0) at /usr/src/debug/wayland/1.11.0-r0/wayland-1.11.0/src/wayland-client.c:1456
#6 wl_display_dispatch_queue_pending (display=0xab5497c0, queue=0xab54982c) at /usr/src/debug/wayland/1.11.0-r0/wayland-1.11.0/src/wayland-client.c:1698
#7 0xb03ea98c in wl_display_dispatch_pending (display=<optimized out>) at /usr/src/debug/wayland/1.11.0-r0/wayland-1.11.0/src/wayland-client.c:1761
#8 0xb04992b4 in PAL::Graphic::CWindowManagerEGLWaylandMMT2020::DispatchPendingEvents (this=<optimized out>)

when app is crashing we also get this log on terminal:

scp: eurasiacon/lws/dbm/dbm.c:238: dbm_buffer_destroy: Assertion `!buf->ptr' failed.

Also, if we remove this api call "wl_display_dispatch_pending" we are not getting any crash. but hazy screen comes very rarely.

Could you please help us in root causing this issue?

Regards,

Ikshwaku

Part Number:TMDSICE3359

Tool/software: TI-RTOS

Hello,

Part Number:TMDX654IDKEVM

Tool/software: Code Composer Studio

Hello,

I installed CCS v8 on my windows 10 and tried to create an C application in order to run on my board.

I changed the path for the gcc from project properties but when I try to build it, it shows me that nothing is to build 

Then when I try to compile I have the following error.

Can you help me to resolve this issue?

Best regards!

Part Number:AM5728

Tool/software: Linux

I want t use the openCL to accelerate  my program. And I read the guide http://downloads.ti.com/mctools/esd/docs/opencl/compilation.html

Part Number:AM5748

Tool/software: TI-RTOS

My customers are checking I2C on the AM5748 custom board.
Using the I2C1 port, they have confirmed both 100kHz and 400kHz modes.

They feel there is a problem with the I2C specification (TRM) and driver(SW).

The first one,
they set the duty ratio to be 50/50 by looking at Table 24-6.

■100kHz
・I2C_PSC ：13h（I2Ci_INTERNAL_CLK frequency 4.8MHz）
・I2C_SCLL：11h（17d+7=24cycles）
・I2C_SCLH：13h（19d+5=24cycles）
total 48cycles
 
■400kHz
・I2C_PSC ：07h（I2Ci_INTERNAL_CLK frequency 12MHz）
・I2C_SCLL：08h（8d+7=15cycles）
・I2C_SCLH：0Ah（10d+5=15cycles）
Total 30cycles

They considered NOTE in Table 24-6. But apparently Low level time seems to be long.
(Especially, it can be confirmed clearly by 400 kHz communication)

The second,
the total cycles at 400kHz settings is calculated to be 30 cycles.
But when I measure it, it is 387.6kHz.

We suspect that we are incorrectly setting to 31 cycles because TRM is wrong.
(12 MHz / 31 cycles = 387 kHz)

Question:

Are there any incorrect information or driver issue related to I2C?

AM5748
pdk_am57xx_1_0_11

Part Number:AM5728

Tool/software: TI-RTOS

Hello,

We are working on a custom board carrying AM5728 SOM Module from Phytec with following setup,

- Board carries Xilinx Artix-7 connected over PCIe bus (containing FPGA endpoint) to the SOM module

- ARM on AM5728 is used to load DSP firmware using remoteproc method

- DSP firmware running SYS/BIOS enumerates the endpoint using the provided pcie libraries

On the software front,

- Linux 4.9.41 used is for booting is from Phytec GIT-repo (stash.phytec.com/.../browse

- The default device-tree has been updated to disable PCIe Root complex (pcie1_rc, pcie2_phy in am572x-pcm-948.dtsi file) so when lspci is run, we see empty output on command line

- This (pcie root-complex 1) is used on the DSP core for communication with endpoint implemented in FPGA

In this setup, the link training has completed and is in L0 state (0x11). But when we start configuration read for device ID and Vendor ID of Endpoint, the link state changes from L0 state to Link Recovery ready (0x10) and back to L0 state. After some time configuration access stops and link-state is seen to be in Detect-QUITE state (0x0). But on evaluation board with same FPGA, link state will remain in L0 state over entire access.

In a separate run, after link training completion, if we don't do any configuration read access, the link state continues to remain in L0 state on our board.

Can you please help to understand under what circumstances, link state changes from L0 to Link recovery ready state?

thanks--

Somesh

Part Number:PROCESSOR-SDK-AM335X

Tool/software: TI-RTOS

hi.,

I need DMTimer code ,I searched in "ti-processor-sdk-rtos-am335x-evm-05.03.00.07-Windows-x86-Install" this SDK code. in this on example code is there for timers "timeSync_BasicExample_icev2AM335x_wSocLib_armExampleproject" in this how there using dmtimers I am not getting please any one can example me.

Regards

chandana

Part Number:AM4379

Tool/software: TI-RTOS

Hi,

  I try to use Am437x board for ethercat communication between PC and drive. I have taken EcMAsterDemo code from acountis site. However, I encountered the problem "No source available for "0x35aaa"  when entering the CCS debug mode. Why such time of errors occurred?? What does this error mean?? How to resolve it??

Part Number:AM3359

Tool/software: Linux

Hello,

I would like to report some issues with the icss-emac-lld-test application at first, but I still have some questions about the dts I cloned from am335x-pru-uio.dtsi.
I am on a yocto-sumo setup using the meta-ti repository on the thud branch.

I tried to get icss-emac-lld-test up and running on my custom board. At first the application consistently crashed with a segmentation fault. I checked with valgrind and found an issue in the icss-emac-lld driver itself (src/icss_emacDrv.c) and another one in the test program (test/src/test_common_utils.c). There have been used some memory cells without initialization (random content). I would supply patches suitable for "git am" but I don't know how to append these to this forum post. After applying these patches my self-built icss_emacMainTest_am335x.out doesn't crash any more.

But I still have a problem to understand the dts file I needed to create for my custom board. I'm using the uio-module-drv to access the PRU from user space. I derived my custom dts from the am335x-pru-uio.dtsi of the yocto meta-ti layer here: 

The part of the file (quoted below) which I don't understand is the base address and size allocation for the OCMC RAM of the am335x device:

uio_pruss_mem2: uio_pruss_mem2 {
	compatible = "ti,uio-module-drv";
	mem = <0x4a328000 0xd4>,
	      <0x4a330000 0x174>,
	      <0x4a332400 0x90>,
	      <0x40302000 0x0e000>;
	mem-names = "uart", "ecap", "mdio", "ocmc";
	status = "okay";
};

This assigns a base address for the OCMC of 0x2000 bytes above the real hardware address and cuts the size down from the real 0x10000 to 0xE000. I would suspect that this a bug. Especially when I'm looking at the line below in firmware/icss_dualemac/config/icss_emacFwConfig.h of the icss-emac driver package, which is beyond the size of 0xe000:

#define ICSS_EMAC_FW_P0_COL_BUFFER_OFFSET        (0xEE00U) /* 1536 byte collision buffer for port 0 send queue  */

And the icss_emacFwDynamicCfg structure from icss_emacFwConfig.c is used unchanged in the icss-emac-lld-test application. Therefore I think the line for the memory configuration for OCMC should supply a base address of 0x40300000 and a size of 0x10000. This configuration I used successfully.

Please advise which version I should use and why.

Best regards,

    Stefan Mätje