Part Number: TMDXIDK5718

Hi TI.

I’m trying to get familiar with the IPC examples in http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_IPC.html.

I'm using IDK572 and SDK6.0.

It seems that doc hasn’t been updated for a while and there is a crash and build error.

1. Getting a build error when issuing “make ti-ipc-linux”

linux_devkit/environment-setup, line 24  sets “--sysroot=/home/chchlee/ti-processor-sdk-linux-rt-am57xx-evm-06.00.00.07/linux-devkit/sysroots/armv7at2hf-neon-linux-gnueabi'”

But  configure (in ipc_3_50_03_05) expects “–with_sysroot” and therefor complains. (autoconf) version issue?

So temporarily set

export CC="${TOOLCHAIN_PREFIX}gcc --with-sysroot=$SDK_PATH_TARGET

Now I can at least build the example.

2. Boot issue

When the I make, install the DSP1 and DSP2 code for ex02_messageq Linux often freezes while booting….

[  OK  ] Found device /dev/ttyS2.

[    9.524350] remoteproc remoteproc2: powering up 40800000.dsp

[    9.540460] remoteproc remoteproc2: Booting fw image dra7-dsp1-fw.xe66, size 4311468

[    9.584396] remoteproc remoteproc3: powering up 41000000.dsp

[    9.584416] remoteproc remoteproc3: Booting fw image dra7-dsp2-fw.xe66, size 4156096

[    9.584590] omap-iommu 41501000.mmu: 41501000.mmu: version 3.0

[    9.584627] omap-iommu 41502000.mmu: 41502000.mmu: version 3.0

[    9.618452] virtio

 (Please visit the site to view this file)

…or endlessly outputs console messages, see attached file.

About every 3rd times it boots properly and I can successfully run "./app_host DSP1" and output is as expected.

My best guess is that there a race condition: there is a FW running on arm which expects the original dra7-dsp1/2-fw.xe66 (dra7-dso1-fw.xe66.opencl-monitor ?)

 3. The “Multi-core demonstration are not anymore found in SDK6.0 matrix launcher

 4. The related documentation is somewhat confusing:

 There is s section “Build IPC Linux examples”: This builds the Arm part with Linux and DSP part with RTOS. Right?

There is s section “Build IPC RTOS examples”: This builds the Arm part with TI RTOS and DSP part with RTOS. Right?

Before these two section there is “Rebuilding the demo”: this seems to be doing the same “Build IPC Linux examples”?

6. Documentation:

Ok: this “IPC Linux Library” is built. But there is no info if it is statically linked to the demo apps, or how it can be installed after making it. It seems that the library is already part of the rootfs.

ldd app_host

        linux-vdso.so.1 (0xbee8c000)

        libpthread.so.0 => /lib/libpthread.so.0 (0xb6ea7000)

        libc.so.6 => /lib/libc.so.6 (0xb6d65000)

        librt.so.1 => /lib/librt.so.1 (0xb6d4e000)

        libtiipc.so.1 => /usr/lib/libtiipc.so.1 (0xb6d34000)

        libtiipcutils.so.1 => /usr/lib/libtiipcutils.so.1 (0xb6d20000)

        libtitransportrpmsg.so.1 => /usr/lib/libtitransportrpmsg.so.1 (0xb6d0a000)

        /lib/ld-linux-armhf.so.3 (0xb6ee4000)

7. Documentation

In section “Run IPC Linux examples”, after building “make ti-ipc-linux” and “make ti-ipc-linux-examples”

But I get:

chchlee@ubuntu:~/ti/ipc_3_50_03_05/examples$ ls -l

total 40

drwxr-xr-x 4 chchlee chchlee 4096 Jul 23 15:10 AM571X_bios_elf

drwxr-xr-x 4 chchlee chchlee 4096 Jul 23 15:10 AM572X_bios_elf

drwxr-xr-x 2 chchlee chchlee 4096 Jul 23 15:10 DRA7XX_android_elf

drwxr-xr-x 6 chchlee chchlee 4096 Jul 23 15:10 DRA7XX_bios_elf

drwxr-xr-x 6 chchlee chchlee 4096 Jul 23 15:10 DRA7XX_linux_elf

drwxr-xr-x 2 chchlee chchlee 4096 Jul 23 15:10 DRA7XX_qnx_elf

So the Linux examples are found under DRA7XX_linux_elf, not AM57…

Best regards, Chris

Part Number: TMS320C6657

Hi,

I want to boot a custom c6652 board from Direct SPI NOR boot.

I am able to boot EVM in direct spi nor boot. On reset i notice that the processor is at  0x20b00000 and executs some ROM code before loading the NOR code using SPI.

Can need more inforamtion on the above ROM coded and how i can use this on custom c6652 board.

Thanks

Bhaskar 

Part Number: AM5728

Hi Application specialists.  My customer get issue

Regarding the AM572xEVM camera module (Rev.A1) purchased the other day,
The operation was confirmed multiple times using the following procedure, but the camera module could not be recognized.

Looking at E2E below, the log display (Product ID error ffffff87) is answered that the sensor board is defective.
https://e2e.ti.com/support/processors/f/791/p/754231/2788548#2788548

How can I make the camera module of ev.A1 available?
The new camera module (Rev.C) purchased last time has been confirmed to work properly.

If there is no way to make it available, could you exchange Rev A1 to Rev.C?

[Operation check environment]
PSDK Linux: 05.03.00.07
Image: Pre-build image (Write pre-build image with <PSDK> /bin/create-sdcard.sh)
Camera module: Rev A1
Processor module: Rev A3
LCD module: A2

[Operation check procedure]
1. Securely attach the camera module to the EVM with screws
In the case of camera module Rev.A1 (in the case of a black base), make sure that the flexible cable of the sensor is securely attached.

2. Start EVM

3. Move to the boot partition
cd / run / media / mmcblk0p1 /

4. Edit uEnv.txt and add the following at the end (uEnv.txt is the file directly under the boot partition)

■ Camera module Rev.A1 (Black base)
# Add for Camera
fdtfile = am57xx-evm-reva3-cam-mt9t111.dtb

■ Camera module Rev.C (green base)
# Add for Camera
fdtfile = am57xx-evm-reva3-cam-ov10635.dtb

5. Restart EVM

6. Check the video1 display with the following command
ls / dev / video *
→ Camera module Rev.1A is not recognized (video1 is not displayed)
Note that Rev.C was recognized.

7. Check dmesg with the following command
dmesg | grep mt9t
→ mt9t11x 4-003c: Product ID error ffffff87 is displayed (sensor board failure)

Reference
https://e2e.ti.com/support/processors/f/791/t/718709?tisearch=e2e-sitesearch&keymatch=Flight%20Control%20System

Part Number: AM4372

https://e2e.ti.com/support/archive/internal/int_sitara_am335x/f/425/t/352540

#1. According to upper post, the OTG support to detect host/slave from ID pin status on cable connection. not need a power cycle?

#2. Current Processor SDK USB driver support role switch at the connect time automatically, not need manually operation?

#3. connect USB_VBUS to board 5V directly, UBUS_DRV to control 5V power to supply to connector or source from connector base on ID status and role, is the connection OK?

Part Number: AM5746

Hi,

My customers communicate with the FPGA using GPMC(Asynchronous, non-multiplexed mode).
They want to access the FPGA faster, they are considering "Synchronous Burst Read/Write".

TRM: 15.4.4.10.2.2 (Page.3570)
In case of the Burst Read, we considered that the access timing can be adjusted with the WAIT signal.
However, Burst Write (TRM 15.4.4.10.2.4) has no mention about WAIT signal.

Question:
Is it possible to adjust access timing using WAIT signal with Synchronous Burst Write?

AM5746
TRM:spruih8a.pdf

Regards,
Rei

Part Number: TDA2SX

Hi,

I am getting following error while booting from eMMC. Can anybody suggest the possible solution?

LOG:

** Partition 1 not valid on device 1 **
spl_register_fat_device: fat register err - -1spl_load_image_fat: error reading image u-boot.img, err - -1
Card did not respond to voltage select!
*** Warning - MMC init failed, using default environment

spl: no partition table found
SPL: failed to boot from all boot devices

I have also attached full log file.

Thanks,

Niraj

(Please visit the site to view this file)

Part Number: AM5718

HI,

We are working with custom board having AM5718 using ti-processor-sdk-linux-am57xx-evm-05.02.00.10.
Regarding the pci based ethernet we are able to detect the pci based information the boot log and there is an issue we are facing presently in the process of detecting mac address. While trying to fetch the pci based mac the boot log is getting stucked over the below mentioned lines and not able boot further. Kindly suggest us what factors are making this scenario to happen.

Thanks & Regards

P. Venkata prasad.

Part Number: AM3352

hi Ti,

I am working with am3352 development board, w.r.t  uboot and kernel configurations , in am335x-evmsk.dts  file , while updating a node for external i2c slave device we are facing some issues.

there are two i2c lines i2c0 & i2c1 on i2c0 two slave device external RTC(Bq32000) and IO expander(tca6408)is interfaced also respective device drivers are also available in sdk.

when we write dts node for this external i2c slaves , we seem to see that a device node not being created respectively also IOCtl function call is  getting failed , and works fine if we don't update the node in dts file.

we are not able to understand what is happening, is there any other way to check a device node for the i2c connected device, 

below is the dts file we are using:

u can check i2c0 node for info, if there is any wrong update in dts file please let me know, or anything extra need to be added.

this is w.r.t., new kernel 2019  version

/*
 * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License version 2 as
 * published by the Free Software Foundation.
 */

/*
 * AM335x SPX board modifications
 * www.ti.com/.../tmdssk3358
 */

/dts-v1/;

#include "am33xx.dtsi"
#include <dt-bindings/pwm/pwm.h>
#include <dt-bindings/interrupt-controller/irq.h>

/ {
 model = "TI AM335x EVM-SK";
 compatible = "ti,am335x-evmsk", "ti,am33xx";

 cpus {
  cpu@0 {
   cpu0-supply = <&vdd1_reg>;
  };
 };

 memory@80000000 {
  device_type = "memory";
  reg = <0x80000000 0x10000000>; /* 256 MB */
 };

 chosen {
  stdout-path = &uart0;
 };

 vbat: fixedregulator0 {
  compatible = "regulator-fixed";
  regulator-name = "vbat";
  regulator-min-microvolt = <5000000>;
  regulator-max-microvolt = <5000000>;
  regulator-boot-on;
 };

 
 wl12xx_vmmc: fixedregulator2 {
  pinctrl-names = "default";
  pinctrl-0 = <&wl12xx_gpio>;
  compatible = "regulator-fixed";
  regulator-name = "vwl1271";
  regulator-min-microvolt = <1800000>;
  regulator-max-microvolt = <1800000>; 
  gpio = <&gpio1 29 0>;

 /*  Unable  to Comment above 7 lines because this is used as GPMC_CSn0 in our board.
   If commented unable to mount RFS. TODO  */

  startup-delay-us = <70000>;
  enable-active-high;
 };
 

 vtt_fixed: fixedregulator3 {
  compatible = "regulator-fixed";
  regulator-name = "vtt_srini";
  regulator-min-microvolt = <1500000>;
  regulator-max-microvolt = <1500000>;
  gpio = <&gpio3 13 GPIO_ACTIVE_HIGH>;  /* Updated as per SPX schematics */
  regulator-always-on;
  regulator-boot-on;
  enable-active-high;
 };
};

&am33xx_pinmux {
 pinctrl-names = "default";
 pinctrl-0 = <&ddr3_vtt_toggle>;

 ddr3_vtt_toggle: ddr3_vtt_toggle {
  pinctrl-single,pins = <
   0x164 (PIN_OUTPUT | MUX_MODE7) /* ecap0_in_pwm0_out.gpio0_7 */
       /* How it is 0x164
          ecap0_in_pwm0_out offseti 964h TRM PAGE 1458.
          Why and how it made as 164h.
       */

       /*
        Our vtt is gpio3_13, Update accordingly. TODO
        For usb1_drvvbus, offset is A34h,
        What should be the value?
       */
  >;
 };
 
 i2c1_pins: pinmux_i2c1_pins {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x910, PIN_INPUT_PULLUP | MUX_MODE3) /* (J15) gmii1_rxer.I2C1_SCL */
   AM33XX_IOPAD(0x90c, PIN_INPUT_PULLUP | MUX_MODE3) /* (H17) gmii1_crs.I2C1_SDA */
  >;
 };

 uart0_pins: pinmux_uart0_pins {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x970, PIN_INPUT_PULLUP | MUX_MODE0) /* uart0_rxd.uart0_rxd */
   AM33XX_IOPAD(0x974, PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* uart0_txd.uart0_txd */
  >;
 };

 uart1_pins: pinmux_uart1_pins {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x980, PIN_INPUT_PULLUP | MUX_MODE0) 
   AM33XX_IOPAD(0x984, PIN_OUTPUT | MUX_MODE0) 
  >;
 };

 uart3_rs485_gpio_pin: pinmux_uart3_rs485_gpio {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x868, PIN_INPUT | MUX_MODE7) 
   AM33XX_IOPAD(0x850, PIN_OUTPUT | MUX_MODE7) 
  >;
 };
 
 uart3_pins: pinmux_uart3_pins {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x960, PIN_INPUT_PULLUP | MUX_MODE1) 
   AM33XX_IOPAD(0x964, PIN_OUTPUT | MUX_MODE1) 
  >;
 };

 uart4_pins: pinmux_uart4_pins {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x968, PIN_INPUT_PULLUP | MUX_MODE1) 
   AM33XX_IOPAD(0x96C, PIN_OUTPUT | MUX_MODE1) 
  >;
 };

 uart5_pins: pinmux_uart5_pins {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x8C0, PIN_OUTPUT | MUX_MODE4) 
   AM33XX_IOPAD(0x8C4,  PIN_INPUT | MUX_MODE4) 
  >;
 };

 mmc1_pins: pinmux_mmc1_pins {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x8fc, PIN_INPUT_PULLUP | MUX_MODE0) 
   AM33XX_IOPAD(0x8f8, PIN_INPUT_PULLUP | MUX_MODE0) 
   AM33XX_IOPAD(0x8f4, PIN_INPUT_PULLUP | MUX_MODE0) 
   AM33XX_IOPAD(0x8f0, PIN_INPUT_PULLUP | MUX_MODE0) 
   AM33XX_IOPAD(0x904, PIN_INPUT_PULLUP | MUX_MODE0) 
   AM33XX_IOPAD(0x900, PIN_INPUT_PULLUP | MUX_MODE0) 
  >;
 };

 wl12xx_gpio: pinmux_wl12xx_gpio {
  pinctrl-single,pins = <
   AM33XX_IOPAD(0x87c, PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpmc_csn0.gpio1_29 */
  >;
 };
};

&uart0 {
 pinctrl-names = "default";
 pinctrl-0 = <&uart0_pins>;
 status = "okay";
};

&uart1 {
 pinctrl-names = "default";
 pinctrl-0 = <&uart1_pins>;
 status = "okay";
};

&gpio1 {
 status = "okay";
};

&uart3{
 pinctrl-names = "default";
 pinctrl-0 = <&uart3_pins>;
 status = "okay";
 rs485-rts-active-high;
 rs485-rts-delay = <0 0>;
};

&uart4 {
 pinctrl-names = "default";
 pinctrl-0 = <&uart4_pins>;
 status = "okay";
};

&uart5 {
 pinctrl-names = "default";
 pinctrl-0 = <&uart5_pins>;
 status = "okay";
};

&i2c0 {
 pinctrl-names = "default";
 /*pinctrl-0 = <&i2c0_pins>;*/
 status = "okay";
 clock-frequency = <400000>;
 
 tps: tps@2d {
  label = "spx_tps";
  reg = <0x2d>;
 };

        tca6408_i2c0: tca6408@21 {
  label = "i2c0_spx_expander";
  compatible = "ti,tca6408";
  reg = <0x21>;    
 };
 

 
        bq32000_i2c0: bq32000@d0 {
  label = "i2c0_spx_rtc";
  compatible = "ti,bq32000";
  reg = <0xd0>;     
  status = "okay";
 };
 
};

&i2c1 {
 pinctrl-names = "default";
 pinctrl-0 = <&i2c1_pins>;
 status = "okay";
 clock-frequency = <400000>;   /* TODO */

 /*
  EEPROM NOT USED.
 */

 /*
  CY8CPLC10, NO COMPATIABLE DRIVERS  AVAILABLE TODO ??????
 */
};

#include "tps65910.dtsi"

&tps {
 vcc1-supply = <&vbat>;
 vcc2-supply = <&vbat>;
 vcc3-supply = <&vbat>;
 vcc4-supply = <&vbat>;
 vcc5-supply = <&vbat>;
 vcc6-supply = <&vbat>;
 vcc7-supply = <&vbat>;
 vccio-supply = <&vbat>;

 regulators {
  vrtc_reg: regulator@0 {
   regulator-always-on;
  };

  vio_reg: regulator@1 {
   regulator-always-on;
  };

  vdd1_reg: regulator@2 {
   /* VDD_MPU voltage limits 0.95V - 1.26V with +/-4% tolerance */
   regulator-name = "vdd_mpu";
   regulator-min-microvolt = <912500>;
   regulator-max-microvolt = <1351500>;
   regulator-boot-on;
   regulator-always-on;
  };

  vdd2_reg: regulator@3 {
   /* VDD_CORE voltage limits 0.95V - 1.1V with +/-4% tolerance */
   regulator-name = "vdd_core";
   regulator-min-microvolt = <912500>;
   regulator-max-microvolt = <1150000>;
   regulator-boot-on;
   regulator-always-on;
  };

  vdd3_reg: regulator@4 {
   regulator-always-on;
  };

  vdig1_reg: regulator@5 {
   regulator-always-on;
  };

  vdig2_reg: regulator@6 {
   regulator-always-on;
  };

  vpll_reg: regulator@7 {
   regulator-always-on;
  };

  vdac_reg: regulator@8 {
   regulator-always-on;
  };

  vaux1_reg: regulator@9 {
   regulator-always-on;
  };
  
  
  vaux2_reg: regulator@10 {
   regulator-always-on;
  };

  vaux33_reg: regulator@11 {
   regulator-always-on;
  };

  vmmc_reg: regulator@12 {
   regulator-min-microvolt = <1800000>;
   regulator-max-microvolt = <3300000>;
   regulator-always-on;
  };
 };
};

&mmc1 {
 status = "okay";
 vmmc-supply = <&vmmc_reg>;
 bus-width = <4>;
 pinctrl-names = "default";
 pinctrl-0 = <&mmc1_pins>;
};

&mmc2 {
 
 status = "okay";
 vmmc-supply = <&wl12xx_vmmc>; /* Must need */
};

&pruss_soc_bus {
 status = "okay";

 pruss: pruss@0 {
  status = "okay";
 };
};

Thanks & Regards,

Manjunath

Part Number: TDA3XEVM

Hi,

We have some doubts related to bootmodes in tda3x, In our custom board we have sysboot[4] as 0b1 and sysboot[0:3] as 0b0000 , this one mentioned in the datasheet as Memory preferred booting.

Our query is,

If the sbl is not found , In this case , I have doubt that Whether the ROM code will switch automatically from QSPI BOOT (memory) mode to UART(Peripheral) mode. Or we have to modify HW settings to switch QSPI mode to UART mode.

In the datasheet, For the above sysboot settings, it mentioned as first  booting device will be QSP_1 and second booting  device will be UART. Could you please clarify this?

Regards

Prakash

Hello All,

I don't get any graphics output on monitor connected to Display Port. 

I am trying  to run weston sample application on linux and i get following errors.

root@j7-evm:~# weston-simple-egl
weston-simple-egl: ../weston-5.0.0/clients/simple-egl.c:901: main: Assertion `display.display' failed.

Aborted (core dumped)

i also tried modetest

root@j7-evm:~# modetest
trying to open device 'i915'...failed
trying to open device 'amdgpu'...failed
trying to open device 'radeon'...failed
trying to open device 'nouveau'...failed
trying to open device 'vmwgfx'...failed
trying to open device 'omapdrm'...failed
trying to open device 'exynos'...failed
trying to open device 'tilcdc'...failed
trying to open device 'msm'...failed
trying to open device 'sti'...failed
trying to open device 'tegra'...failed
trying to open device 'imx-drm'...failed
trying to open device 'rockchip'...failed
trying to open device 'atmel-hlcdc'...failed
trying to open device 'fsl-dcu-drm'...failed
trying to open device 'vc4'...failed
trying to open device 'virtio_gpu'...failed
trying to open device 'mediatek'...failed
trying to open device 'meson'...failed
trying to open device 'pl111'...failed
trying to open device 'stm'...failed
no device found

Regards

Vinay

Part Number: TMS320C6652

Hi,

Can we configure the GPIO1:13 pins as GPIOs after the BOOT up.

Does the primary functions of these pins are BOOT config pins ?

Regards,

Divy

Part Number: TDA2P-ABZ

Hello support team.

We are confirming Linux on TDA2Px EVM.

Then we built original software according to VisionSDK Linux User Guide.

> make linux

> make linux_install

> make -s -j depend

> make -s -j

We tried to run demo apps at TDA2P EVM (w/ Fusion board).

This environment, we has already confirmed by RTOS version demo apps.

However, we need to confirm it with Linux version.

Then we tested with TDA2Px EVM with Fusion board.

After login the linux system, we tried to run demo apps

> cd /opt/vision_sdk

> ./visionsdk_load.sh.

This vision_sdk_load.h called ./memcache_load.sh which executed insmod command for two module. one is ./bin/memcache.ko and and other is ./bin/cmemk.ko.

However, cmemk.ko is not under ./bin.(/opt/visionsdk/bin absolute path).

it is in /opt/visionsdk.

it is O.K. we can move it to ./bin.

again we tried to run ./vision_sdk_load.sh called disableDssInterruptsOnA15.sh which uses “omapconf” command.

However, several error happened.

please find the below error.

First line is “crossbar=`omapconf dump crossbar irq mpu | grep DISPC | awk -F" " '{ print $4}'`”.

It may happed error.

Because I tried “omapconf dump crossbar irq mpu” command manually.

However, it happened error. “mpu” parameter of omapconf generates error message. In fact, if only “omapconf dump crossbar irq” is executed , it works fine.

Anyway, I want to get your advice “how to fix this issue”.

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

./vision_sdk_load.sh

[   90.927658] DMA: Module install successful, device major num = 241

[   90.934143] DRV: Module install successful

[   90.956941] CMEMK module: reference Linux version 4.4.84

[   90.962968] cmemk initialized

Error: I2C Read failed

Error: I2C Read failed

Error: I2C Read failed

./disableDssInterruptsOnA15.sh: line 11: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 12: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 13: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 14: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 15: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 16: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 17: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 18: COMMANDS: command not found

./disableDssInterruptsOnA15.sh: line 19: COMMANDS: command not found

updated value is

COMMANDS

              ### WARNING ###: use the following [read | write | set bit | clear bit | dump] commands at your own risk!

              No address check done, may generate:

              - bus error (invalid or not accessible <physical address>,

              - platform crash/hang (bad <value>).

                 Read any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

                 Write <value> at any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

                 Set bit at <position> into any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

                 Clear bit at <position> into any OMAP memory address (register), given its <physical address> or <name> as listed in TRM.

                 Dump a range of OMAP memory addresses, from <start address> to <end address>.

                 Note all addresses within given range must be valid and accessible.

              ### WARNING ###: use the following I2C [read | write] commands at your own risk!

              No address check done, may generate:

              - I2C bus error (invalid or not accessible <physical address>,

              - platform crash/hang (bad <value>).

                 Read I2C register at address <addr> from I2C chip at <chip-addr> on I2C <bus>.

                 Write <value> in I2C register at address <addr> from I2C chip at <chip-addr> on I2C <bus>.

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

Best Regards

KORO

Part Number: AM3352

MCU  is AM3352  300MHZ

the old NAND FLASH  is MT29F1G08ABAEAWP, and the new one is MT29F2G08ABAGAWP-IT:G,

the system can work well using the old flash, but use the new one, have some  probability to boot fail (about 30% ~ 40%). and if boot sucess, the system also can work well.

what's the problem? timing between NANDFLASH and BOOTROM code?

SYSBOOT config is:  0100000000001011

Hi

According to the training video "Cascaded Radar And Body & Chassis Automotive Applications", the TX Beamforming can improve a factor of 2 compared to MIMO (20log10(NTX) vs. 10log10(NTX) in MIMO).

Is there any reference to understand and deriviation of the relationship?

Thanks

Part Number: DRA76P

Hello TI team,

There always be consecutively "L3 Custom Error" issues when I was trying to run the vis_sdk on our custom board, the dmesg log is:

[ 33.274743] WARNING: CPU: 0 PID: 0 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x318/0x400()
[ 33.274748] 44000000.ocp:L3 Custom Error: MASTER DSP1_MDMA TARGET L4_PER2_P3 (Read): Data Access in User mode during Functional access
[ 33.274752] Modules linked in: cmemk(O) pvrsrvkm(O) input_polldev ti_fpd3_serdes sd_mod usb_storage scsi_mod
[ 33.274772] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W O 4.4.117-gb7a70b4-dirty #4
[ 33.274776] Hardware name: Generic DRA74X (Flattened Device Tree)
[ 33.274779] Backtrace:
[ 33.274787] [<c020c80c>] (dump_backtrace) from [<c020ca08>] (show_stack+0x18/0x1c)
[ 33.274790] r6:60070193 r5:c1241e94 r4:00000000 r3:dc8ba675
[ 33.274803] [<c020c9f0>] (show_stack) from [<c0b16720>] (dump_stack+0x94/0xa8)
[ 33.274808] [<c0b1668c>] (dump_stack) from [<c0232000>] (warn_slowpath_fmt+0xa8/0xec)
[ 33.274812] r6:00000093 r5:c058ec58 r4:c120394c r3:dc8ba675
[ 33.274825] [<c0231f5c>] (warn_slowpath_fmt) from [<c058ec58>] (l3_interrupt_handler+0x318/0x400)
[ 33.274828] r3:eea3a180 r2:c0e2ebcc
[ 33.274835] r7:00000002 r6:eea3a310 r5:c0e2eb0c r4:80080003
[ 33.274848] [<c058e940>] (l3_interrupt_handler) from [<c029be58>] (handle_irq_event_percpu+0xc0/0x2c0)
[ 33.274852] r10:c0c03250 r9:c1200010 r8:00000000 r7:00000017 r6:c120e9ec r5:ee900c60
[ 33.274864] r4:eea3a680
[ 33.274871] [<c029bd98>] (handle_irq_event_percpu) from [<c029c098>] (handle_irq_event+0x40/0x64)
[ 33.274874] r10:c1200000 r9:c1203a4c r8:ee824000 r7:00000001 r6:c120e9ec r5:ee900c60
[ 33.274886] r4:ee900c00
[ 33.274893] [<c029c058>] (handle_irq_event) from [<c029f950>] (handle_fasteoi_irq+0xc0/0x1c4)
[ 33.274897] r6:c120e9ec r5:ee900c60 r4:ee900c00 r3:00000000
[ 33.274910] [<c029f890>] (handle_fasteoi_irq) from [<c029b740>] (__handle_domain_irq+0x74/0xcc)
[ 33.274913] r7:00000001 r6:00000000 r5:00000000 r4:c1085518
[ 33.274926] [<c029b6cc>] (__handle_domain_irq) from [<c02014d8>] (gic_handle_irq+0x40/0x7c)
[ 33.274929] r8:fa213000 r7:fa212000 r6:c1201ee8 r5:fa21200c r4:c12048c0 r3:c1201ee8
[ 33.274943] [<c0201498>] (gic_handle_irq) from [<c020d500>] (__irq_svc+0x40/0x74)
[ 33.274947] Exception stack(0xc1201ee8 to 0xc1201f30)
[ 33.274952] 1ee0: 00000001 00000000 fe600000 00000000 c12039ec c0c03250
[ 33.274957] 1f00: 00000000 c1291878 00000000 c1203a4c c1200000 c1201f44 c1201f24 c1201f38
[ 33.274961] 1f20: c02234e4 c0208bfc 60070013 ffffffff
[ 33.274965] r8:00000000 r7:c1201f1c r6:ffffffff r5:60070013 r4:c0208bfc r3:c02234e4
[ 33.274981] [<c0208bd4>] (arch_cpu_idle) from [<c0288b30>] (default_idle_call+0x28/0x34)
[ 33.274987] [<c0288b08>] (default_idle_call) from [<c0288e8c>] (cpu_startup_entry+0x350/0x408)
[ 33.274993] [<c0288b3c>] (cpu_startup_entry) from [<c0b18944>] (rest_init+0x90/0x94)
[ 33.274996] r7:00000000
[ 33.275003] [<c0b188b4>] (rest_init) from [<c1000e64>] (start_kernel+0x440/0x494)
[ 33.275006] r4:c129c050 r3:dc8ba675
[ 33.275015] [<c1000a24>] (start_kernel) from [<80008090>] (0x80008090)

and finally a "iommu fault" occurred:

[ 34.917400] omap-iommu 40d01000.mmu: iommu fault: da 0x8e1001c0 flags 0x0
[ 34.924227] remoteproc0: crash detected in 40800000.dsp: type mmufault
[ 34.930881] omap-iommu 40d01000.mmu: 40d01000.mmu: errs:0x00000002 da:0x8e1001c0 pgd:0xedfe6384 *pgd:px00000000

Looking into both the RadioApp and the RTOS(/sys/kernel/debug/remoteproc/remoteproc0/trace0_last) log,

it seems that the "L3 Custom Error" is caused by calling GIO_create() to create "/mcasp5" for below reasons:

1. The RadioApp is blocked from waiting the remote core response after sending the IOA_INIT_REQ command.

01-01 00:00:04.473 273 286 I AUDIOMGR: [AMGR_CtrlThread 998] AMGR_sendIoaInit IOA_SOURCE_0
01-01 00:00:04.473 273 286 I AUDIOMGR: [AMGR_sendIoaInit 945] AMGR_sendMcASPInit
01-01 00:00:04.473 273 286 I AUDIOMGR: [AMGR_sendMcASPInit 639] AMGR_sendCmdMsg IOA_INIT_REQ
01-01 00:00:04.473 273 286 I AUDIOMGR: [AMGR_sendMcASPInit 655] osal_msg_wait...

2. The RTOS is blocked after calling GIO_create().

[ 2.538] [IOA_dataHandler][IOA_Sink_0]:
[ 2.539] [IOA_dataHandler][IOA_Sink_0]: IOA_initWait
[ 2.539] [IOA_dataHandler][IOA_Source_0]:
[ 2.539] [IOA_dataHandler][IOA_Source_0]: IOA_initWait
[ 2.543] [IOA_initWait]: IOA_process: msgId 2304
[ 2.543] [IOA_process]: IOA_INIT_REQ
[ 2.543] [IOA_process]: IOA_INIT_REQ IOA_InitMcAsp
[ 2.543] [IOA_InitMcAsp]: IOA_createMCASP: mcaspName: /mcasp5
[ 2.543] [IOA_createMCASP]: GIO_create: /mcasp5

My question is what's the root cause of the "L3 Custom Error" issue, and how to debug/resolve it?

Part Number: PROCESSOR-SDK-AM65X

Tool/software: TI C/C++ Compiler

Hi:

We found the following U-disk recognition problem in using EVM boards under u-boot.

Test environment:

   Hardware:    AM654X EVM PROCESSOR BOARD (REV 1.0), 8G miscro SD card (Panasonic)
                    
                       USB-HUB (Standard Microsystems, Realtek Semiconductor, Ithink)

                       U-disk (Sandisk  , Kingston , HP ,Sansumg ,BANQ )

   Software:     Processor SDK Linux 06_00_00_07

Detailed description of the problem： 

In U-boot, the EVM board connects a certain type of USB HUB and inserts the U disk, some of which can not be recognized.
The test topology is as follows. The EVM board has tested three different manufacturers'USB-HUB. 
The first and second types of USB-HUB can be recognized normally,   while the third type of USB-HUB(Standard microsystems  chip:  USB2514) has two types of USB-HUB that can not be recognized.But these two U disks can be correctly identified under Linux.   The two U disks are BANQ (F30/64G)  and Sandisk (SDCZ33/32G).

Part Number: TDA2EVM5777

Hi,

I am running a simple camera usecase

Capture(1280x400 @ 60fps)) -> Display

Above  usecase is running fine and i am able to display camera output over HDMI.

Now, I modified the usecase as below:

Capture(1280x400 @ 60fps) -> VPE(Resize: 1152x576) -> Display

Build is successful. After running this usecase, Display is blurred.

Let me know what changes are required to enable HDMI display for custom resolution output?

Regards,

Sagar

Part Number: AMIC110

Hi there,

The specification states that the EMU (4: 2) signals can be mapped to different pins (e.g., EMU4 to A14, C15, T13). How does the CPU recognize which pins are being used? Do all JTAG interfaces use the EMU port (for example XDS200)? Is there anny specification?

best regards
Thomas

Part Number: BEAGLEBOARD-X15

Tool/software: TI C/C++ Compiler

Hi,

I was testing debugging features of OpenMP / OpenCL with SDK 6. I would like to debug printf_debug example as a start. I have changed to the makefile to enable to debugging as follows:

include ../make.inc

OA_TC_OPTS 			= -O0
ifeq ($(VERBOSE),1)
OA_HC_OPTS 			= -O0 -Wall -Wextra -fopenmp
OA_SHELL_OPTS 		= -v -g -k --hc="$(OA_HC_OPTS)" --tc="$(OA_TC_OPTS)"
else
OA_HC_OPTS 			= -O0 -fopenmp
OA_SHELL_OPTS 		= -g -k --hc="$(OA_HC_OPTS)" --tc="$(OA_TC_OPTS)"
endif
CXX_OPTS 			= -O0 -g

EXE     	= printf_debug
HOST_CODE 	= printf_debug_main.cpp
TARGET_CODE = printf_debug_target.c
OBJS 		= $(patsubst %.cpp,%.o,$(HOST_CODE))

$(EXE): $(OBJS)
	$(OA_SHELL) $(OA_SHELL_OPTS) $(OBJS) $(TARGET_CODE) -o $@

%.o: %.cpp
	$(CXX) $(CXX_OPTS) -c $<

clean:
	@rm -f $(EXE) $(OA_SHELL_TMP_FILES) *.log

And I have successfully opened a debugging session. Unfortunately after that, while stepping into __omp_2_omp_runtime_functions_with_printf, application crashed with the following error:

recvfrom failed: Link has been severed (67)
rpmsgThreadFxn: transportGet failed on fd 14, returned -20
TIOCL FATAL: Communication to a DSP has been lost (likely due to an MMU fault). Please wait while the DSPs are reset and the runtime attempts to terminate. A reboot may be required before running another OpenCL application if this fails. See the kernel log for fault information.

you can also find below my debugging session commands:

root@am57xx-evm:~# gdbc6x -q -iex "target remote /dev/gdbtty0" -iex "set confirm off" -iex "symbol-file /usr/share/ti/opencl/dsp.out" -iex "add-symbol-file /tmp/openclDD0MC7.out 0xa2000080" -iex "b exit" -iex "b
__omp_2_omp_runtime_functions_with_printf_wrapper"
Remote debugging using /dev/gdbtty0
0x00805fb4 in ?? ()
Reading symbols from /usr/share/ti/opencl/dsp.out...done.
add symbol table from file "/tmp/openclDD0MC7.out" at
.text_addr = 0xa2000080
Reading symbols from /tmp/openclDD0MC7.out...done.
Breakpoint 1 at 0xfed6633a: file exit.c, line 64.
Breakpoint 2 at 0xa2000202: file __TI_CLACC_KERNEL.cl, line 4.
(gdb) continue
Continuing.

Breakpoint 2, __omp_2_omp_runtime_functions_with_printf_wrapper ($a0_AP=0xa2000000 "\004") at __TI_CLACC_KERNEL.cl:4
warning: Source file is more recent than executable.
4 v[0]=a0;
(gdb) info b
Num Type Disp Enb Address What
1 breakpoint keep y 0xfed6633a in exit at exit.c:64
2 breakpoint keep y 0xa2000202 in __omp_2_omp_runtime_functions_with_printf_wrapper at __TI_CLACC_KERNEL.cl:4
breakpoint already hit 1 time

(gdb) list
1 #pragma OPENCL EXTENSION cl_khr_fp64 : enable
2 __kernel void __omp_2_omp_runtime_functions_with_printf_wrapper(global void *a0) {
3 global void *v[1];
4 v[0]=a0;
5 __omp_2_omp_runtime_functions_with_printf(v);
6 }
(gdb) s
5 __omp_2_omp_runtime_functions_with_printf(v);
(gdb) s
Ignoring packet error, continuing...

You can ignore the error at the last line because the application crashed. Please also check the kernel message below:

[ 163.220920] omap-iommu 40d01000.mmu: iommu fault: da 0x20202020 flags 0x0
[ 163.227751] remoteproc remoteproc2: crash detected in 40800000.dsp: type mmufault
[ 163.235278] omap-iommu 40d01000.mmu: 40d01000.mmu: errs:0x00000002 da:0x20202020 pgd:0xe5683f4d *pgd:px00000000
[ 163.245519] remoteproc remoteproc2: handling crash #1 in 40800000.dsp
[ 163.251997] remoteproc remoteproc2: recovering 40800000.dsp
[ 163.271781] remoteproc remoteproc2: stopped remote processor 40800000.dsp
[ 163.278614] remoteproc remoteproc2: powering up 40800000.dsp
[ 163.280674] ------------[ cut here ]------------
[ 163.280692] WARNING: CPU: 0 PID: 31 at drivers/bus/omap_l3_noc.c:147 l3_interrupt_handler+0x330/0x380
[ 163.280698] 4400000

I appreciate if you can help me to solve this issue.

Kind regards,

Mustafa

Part Number: TDA2EVM5777

Tool/software: TI C/C++ Compiler

Hi,

I did choose 'z' option (that is for Exit - AND SHUTDOWN Remote CPUs) in Vision SDK Usecases. (Vision sdk ver.3.7)

The apps was build with tda2xx_evm_linux_all option.

When i execute apps again after exiting with 'z' option, the apps doesn't run normally.

The below message is showed when i exited app with 'z' option.

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

[HOST] [HOST ] 49.726377 s: SYSTEM: System A15 De-Init in progress !!!
[HOST] [IPU2 ] 49.880528 s: CHAINS: Application Exited !!!
[HOST] [IPU2 ] 49.880680 s: SYSTEM: De-Initializing Links !!!
[HOST] [IPU2 ] 52.185780 s: SYSTEM: De-Initializing Links ... DONE !!!
[HOST] [IPU2 ] 52.185933 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024
[HOST] [IPU2 ] 52.186055 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 251576 B (245 KB)
[HOST] [IPU2 ] 52.186238 s: SYSTEM: Heap = SR_OCMC @ 0x00000000, Total size = 0 B (0 KB), Free size = 0 B (0 KB)
[HOST] [IPU2 ] 52.186390 s: SYSTEM: Heap = SR_DDR_CACHED @ 0x84203000, Total size = 314572800 B (300 MB), Free size = 314572800 B (300 MB)
[HOST] [IPU2 ] 52.186573 s: SYSTEM: Heap = SR_DDR_NON_CACHED @ 0xa0100000, Total size = 1045376 B (0 MB), Free size = 851840 B (0 MB)
[HOST] [IPU2 ] 52.236015 s: SYSTEM: System De-Init Done !!!
[HOST] [IPU2 ] 52.236137 s: SYSTEM: System Common De-Init in progress !!!
[ 45.419022] virtio_rpmsg_bus virtio2: destroying channel rpmsg-proto addr 0x50
[HOST] [IPU2 ] 52.268041 s: SYSTEM: IPC de-init in progress !!!
[HOST] [IPU2 ] 52.268346 s: SYSTEM: IPC Notify de-init in progress !!!
[HOST] [IPU2 ] 52.268590 s: SYSTEM: IPC Notify de-init DONE !!!
[HOST] [IPU2 ] 52.268651 s: SYSTEM: IPC MsgQ Task Delete in progress !!!
[HOST] [IPU2 ] 52.268986 s: SYSTEM: IPC MsgQ Task Delete DONE !!!
[HOST] [IPU2 ] 52.269078 s: SYSTEM: IPC de-init DONE !!!
[HOST] [IPU2 ] 52.269261 s: SYSTEM: System Common De-Init Done !!!
[HOST] [EVE1 ] 52.280028 s: SYSTEM: System Eve De-Init in progress !!!
[HOST] [EVE1 ] 52.281004 s: SYSTEM: De-Initializing Links !!!
[HOST] [EVE2 ] 52.300036 s: SYSTEM: System Eve De-Init in progress !!!
[HOST] [EVE2 ] 52.300982 s: SYSTEM: De-Initializing Links !!!
[HOST] [EVE3 ] 52.320014 s: SYSTEM: System Eve De-Init in progress !!!
[HOST] [EVE3 ] 52.320990 s: SYSTEM: De-Initializing Links !!!
[HOST] [EVE4 ] 52.340023 s: SYSTEM: System Eve De-Init in progress !!!
[HOST] [EVE4 ] 52.340999 s: SYSTEM: De-Initializing Links !!!
[HOST] [DSP1 ] 52.359177 s: SYSTEM: System DSP De-Init in progress !!!
[HOST] [DSP1 ] 52.359208 s: SYSTEM: De-Initializing Links !!!
[HOST] [DSP2 ] 52.361160 s: SYSTEM: System DSP De-Init in progress !!!
[HOST] [DSP2 ] 52.361190 s: SYSTEM: De-Initializing Links !!!
[HOST] [DSP1 ] 52.490331 s: SYSTEM: De-Initializing Links ... DONE !!!
[HOST] [DSP1 ] 52.490361 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024
[HOST] [DSP1 ] 52.490392 s: SYSTEM: Heap = LOCAL_L2 @ 0x00800000, Total size = 227264 B (221 KB), Free size = 227264 B (221 KB)
[HOST] [DSP1 ] 52.490422 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 524288 B (512 KB), Free size = 516216 B (504 KB)
[HOST] [DSP1 ] 52.490514 s: SYSTEM: System DSP De-Init Done !!!
[HOST] [DSP1 ] 52.490514 s: SYSTEM: System Common De-Init in progress !!!
[HOST] [DSP2 ] 52.492313 s: SYSTEM: De-Initializing Links ... DONE !!!
[HOST] [DSP2 ] 52.492344 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024
[HOST] [DSP2 ] 52.492374 s: SYSTEM: Heap = LOCAL_L2 @ 0x00800000, Total size = 227264 B (221 KB), Free size = 227264 B (221 KB)
[HOST] [DSP2 ] 52.492405 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 524288 B (512 KB), Free size = 516216 B (504 KB)
[HOST] [DSP2 ] 52.492496 s: SYSTEM: System DSP De-Init Done !!!
[HOST] [DSP2 ] 52.492527 s: SYSTEM: System Common De-Init in progress !!!
5.673003] virtio_rpmsg_bus virtio0: destroying channel rpmsg-proto addr 0x50
[ HOST] [DSP1 ] 52.522204 s: SYSTEM: IPC de-init in progres !!!
[HOST] [DSP1 ] 52.522326 s: SYSTEM: IPC Notify de-init in progress !!!
[HOST] [DSP1 ] 52.522418 s: SYSTEM: IPC Notify de-init DONE !!!
[HOST] [DSP1 ] 52.522448 s: SYSTEM: IPC MsgQ Task Delete in progress !!!
[HOST] [DSP1 ] 52.523211 s: SYSTEM: IPC MsgQ Task Delete DONE !!!
[HOST] [DSP1 ] 52.523241 s: SYSTEM: IPC de-init DONE !!!
45.765104] virtio_rpmsg_bus virtio1: destroying channel rpmsg-proto addr 0x50
[ HOST] [DSP1 ] 52.523272 s: SYSTEM: System Common De-Init one !!!
[HOST] [DSP1 ] 52.523302 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.533184 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.543189 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.553162 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.563167 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.573171 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.583175 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.593180 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.603184 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.613188 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.623162 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.633166 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.643170 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.653175 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.524217 s: SYSTEM: IPC de-init in progress !!!
[HOST] [DSP2 ] 52.524309 s: SYSTEM: IPC Notify de-init in progress !!!
[HOST] [DSP2 ] 52.524431 s: SYSTEM: IPC Notify de-init DONE !!!
[HOST] [DSP2 ] 52.524431 s: SYSTEM: IPC MsgQ Task Delete in progress !!!
[HOST] [DSP2 ] 52.525224 s: SYSTEM: IPC MsgQ Task Delete DONE !!!
[HOST] [DSP2 ] 52.525254 s: SYSTEM: IPC de-init DONE !!!
[HOST] [DSP2 ] 52.525285 s: SYSTEM: System Common De-Init Done !!!
[HOST] [DSP2 ] 52.525285 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.535167 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.545171 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.555175 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.565180 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.575184 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.585188 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.595162 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.605166 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.615171 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.625175 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.635179 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.645183 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.655188 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.608796 s: SYSTEM: De-Initializing Links ... DONE !!!
[HOST] [EVE1 ] 52.609772 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024
[HOST] [EVE1 ] 52.611022 s: SYSTEM: Heap = LOCAL_L2 @ 0x40020000, Total size = 22528 B (22 KB), Free size = 22528 B (22 KB)
[HOST] [EVE1 ] 52.613066 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 254320 B (248 KB)
[HOST] [EVE1 ] 52.615232 s: SYSTEM: System Eve De-Init Done !!!
[HOST] [EVE1 ] 52.616147 s: SYSTEM: System Common De-Init in progress !!!
[HOST] [EVE1 ] 52.620478 s: SYSTEM: IPC de-init in progress !!!
[HOST] [EVE1 ] 52.621393 s: SYSTEM: IPC Notify de-init in progress !!!
[HOST] [EVE1 ] 52.622918 s: SYSTEM: IPC Notify de-init DONE !!!
[HOST] [EVE1 ] 52.623802 s: SYSTEM: IPC MsgQ Task Delete in progress !!!
[HOST] [EVE1 ] 52.630177 s: SYSTEM: IPC MsgQ Task Delete DONE !!!
[HOST] [EVE1 ] 52.631123 s: SYSTEM: IPC de-init DONE !!!
[HOST] [EVE1 ] 52.632251 s: SYSTEM: System Common De-Init Done !!!
[HOST] [EVE1 ] 52.633197 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.640059 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.650033 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.660037 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.670042 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.680046 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.690050 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.700054 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE1 ] 52.701823 s: SYSTEM: Detaching to [EVE4] ... SUCCESS !!!
[HOST] [EVE1 ] 52.702921 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [EVE1 ] 52.710059 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [EVE1 ] 52.711736 s: SYSTEM: Detaching to [EVE3] ... SUCCESS !!!
[HOST] [EVE1 ] 52.712773 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [EVE1 ] 52.720032 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [EVE1 ] 52.721649 s: SYSTEM: Detaching to [EVE2] ... SUCCESS !!!
[HOST] [EVE1 ] 52.722686 s: SYSTEM: Detaching to [DSP2] ...
[HOST] [EVE1 ] 52.724089 s: SYSTEM: Detaching to [DSP2] ... SUCCESS !!!
[HOST] [EVE1 ] 52.725035 s: SYSTEM: Detaching to [DSP1] ...
[HOST] [EVE1 ] 52.726407 s: SYSTEM: Detaching to [DSP1] ... SUCCESS !!!
[HOST] [EVE1 ] 52.727353 s: SYSTEM: Detaching to [IPU2] ...
[HOST] [EVE1 ] 52.728756 s: SYSTEM: Detaching to [IPU2] ... SUCCESS !!!
[HOST] [EVE2 ] 52.629323 s: SYSTEM: De-Initializing Links ... DONE !!!
[HOST] [EVE2 ] 52.630391 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024
[HOST] [EVE2 ] 52.631611 s: SYSTEM: Heap = LOCAL_L2 @ 0x40020000, Total size = 22528 B (22 KB), Free size = 22528 B (22 KB)
[HOST] [EVE2 ] 52.633746 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 254320 B (248 KB)
[HOST] [EVE2 ] 52.635911 s: SYSTEM: System Eve De-Init Done !!!
[HOST] [EVE2 ] 52.636826 s: SYSTEM: System Common De-Init in progress !!!
[HOST] [EVE2 ] 52.640486 s: SYSTEM: IPC de-init in progress !!!
[HOST] [EVE2 ] 52.641432 s: SYSTEM: IPC Notify de-init in progress !!!
[HOST] [EVE2 ] 52.642957 s: SYSTEM: IPC Notify de-init DONE !!!
[HOST] [EVE2 ] 52.643872 s: SYSTEM: IPC MsgQ Task Delete in progress !!!
[HOST] [EVE2 ] 52.650186 s: SYSTEM: IPC MsgQ Task Delete DONE !!!
[HOST] [EVE2 ] 52.651192 s: SYSTEM: IPC de-init DONE !!!
[HOST] [EVE2 ] 52.652290 s: SYSTEM: System Common De-Init Done !!!
[HOST] [EVE2 ] 52.653266 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE2 ] 52.660037 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE2 ] 52.670042 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE2 ] 52.680046 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE2 ] 52.690050 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE2 ] 52.700054 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE2 ] 52.701793 s: SYSTEM: Detaching to [EVE4] ... SUCCESS !!!
[HOST] [EVE2 ] 52.702860 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [EVE2 ] 52.710059 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [EVE2 ] 52.711797 s: SYSTEM: Detaching to [EVE3] ... SUCCESS !!!
[HOST] [EVE2 ] 52.712834 s: SYSTEM: Detaching to [EVE1] ...
[HOST] [EVE2 ] 52.714329 s: SYSTEM: Detaching to [EVE1] ... SUCCESS !!!
[HOST] [EVE2 ] 52.715366 s: SYSTEM: Detaching to [DSP2] ...
[HOST] [EVE2 ] 52.716738 s: SYSTEM: Detaching to [DSP2] ... SUCCESS !!!
[HOST] [EVE2 ] 52.717684 s: SYSTEM: Detaching to [DSP1] ...
[HOST] [EVE2 ] 52.719056 s: SYSTEM: Detaching to [DSP1] ... SUCCESS !!!
[HOST] [EVE2 ] 52.720093 s: SYSTEM: Detaching to [IPU2] ...
[HOST] [EVE2 ] 52.721618 s: SYSTEM: Detaching to [IPU2] ... SUCCESS !!!
[HOST] [EVE3 ] 52.649088 s: SYSTEM: De-Initializing Links ... DONE !!!
[HOST] [EVE3 ] 52.650125 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024
[HOST] [EVE3 ] 52.651345 s: SYSTEM: Heap = LOCAL_L2 @ 0x40020000, Total size = 22528 B (22 KB), Free size = 22528 B (22 KB)
[HOST] [EVE3 ] 52.653449 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 254320 B (248 KB)
[HOST] [EVE3 ] 52.655615 s: SYSTEM: System Eve De-Init Done !!!
[HOST] [EVE3 ] 52.656530 s: SYSTEM: System Common De-Init in progress !!!
[HOST] [EVE3 ] 52.660464 s: SYSTEM: IPC de-init in progress !!!
[HOST] [EVE3 ] 52.661440 s: SYSTEM: IPC Notify de-init in progress !!!
[HOST] [EVE3 ] 52.662935 s: SYSTEM: IPC Notify de-init DONE !!!
[HOST] [EVE3 ] 52.663850 s: SYSTEM: IPC MsgQ Task Delete in progress !!!
[HOST] [EVE3 ] 52.670194 s: SYSTEM: IPC MsgQ Task Delete DONE !!!
[HOST] [EVE3 ] 52.671201 s: SYSTEM: IPC de-init DONE !!!
[HOST] [EVE3 ] 52.672299 s: SYSTEM: System Common De-Init Done !!!
[HOST] [EVE3 ] 52.673244 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE3 ] 52.680046 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE3 ] 52.690050 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE3 ] 52.700054 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [EVE3 ] 52.701762 s: SYSTEM: Detaching to [EVE4] ... SUCCESS !!!
[HOST] [EVE3 ] 52.702830 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [EVE3 ] 52.704355 s: SYSTEM: Detaching to [EVE2] ... SUCCESS !!!
[HOST] [EVE3 ] 52.705362 s: SYSTEM: Detaching to [EVE1] ...
[HOST] [EVE3 ] 52.706795 s: SYSTEM: Detaching to [EVE1] ... SUCCESS !!!
[HOST] [EVE3 ] 52.707832 s: SYSTEM: Detaching to [DSP2] ...
[HOST] [EVE3 ] 52.709205 s: SYSTEM: Detaching to [DSP2] ... SUCCESS !!!
[HOST] [EVE3 ] 52.710211 s: SYSTEM: Detaching to [DSP1] ...
[HOST] [EVE3 ] 52.711706 s: SYSTEM: Detaching to [DSP1] ... SUCCESS !!!
[HOST] [EVE3 ] 52.712743 s: SYSTEM: Detaching to [IPU2] ...
[HOST] [EVE3 ] 52.714268 s: SYSTEM: Detaching to [IPU2] ... SUCCESS !!!
[HOST] [EVE4 ] 52.668883 s: SYSTEM: De-Initializing Links ... DONE !!!
[HOST] [EVE4 ] 52.669828 s: SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024
[HOST] [EVE4 ] 52.671109 s: SYSTEM: Heap = LOCAL_L2 @ 0x40020000, Total size = 22528 B (22 KB), Free size = 22528 B (22 KB)
[HOST] [EVE4 ] 52.673214 s: SYSTEM: Heap = LOCAL_DDR @ 0x00000000, Total size = 262144 B (256 KB), Free size = 254320 B (248 KB)
[HOST] [EVE4 ] 52.675379 s: SYSTEM: System Eve De-Init Done !!!
[HOST] [EVE4 ] 52.676264 s: SYSTEM: System Common De-Init in progress !!!
[HOST] [EVE4 ] 52.680473 s: SYSTEM: IPC de-init in progress !!!
[HOST] [EVE4 ] 52.681449 s: SYSTEM: IPC Notify de-init in progress !!!
[HOST] [EVE4 ] 52.682943 s: SYSTEM: IPC Notify de-init DONE !!!
[HOST] [EVE4 ] 52.683828 s: SYSTEM: IPC MsgQ Task Delete in progress !!!
[HOST] [EVE4 ] 52.690172 s: SYSTEM: IPC MsgQ Task Delete DONE !!!
[HOST] [EVE4 ] 52.691209 s: SYSTEM: IPC de-init DONE !!!
[HOST] [EVE4 ] 52.692246 s: SYSTEM: System Common De-Init Done !!!
[HOST] [EVE4 ] 52.693161 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [EVE4 ] 52.694534 s: SYSTEM: Detaching to [EVE3] ... SUCCESS !!!
[HOST] [EVE4 ] 52.695479 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [EVE4 ] 52.696852 s: SYSTEM: Detaching to [EVE2] ... SUCCESS !!!
[HOST] [EVE4 ] 52.697797 s: SYSTEM: Detaching to [EVE1] ...
[HOST] [EVE4 ] 52.699139 s: SYSTEM: Detaching to [EVE1] ... SUCCESS !!!
[HOST] [EVE4 ] 52.700176 s: SYSTEM: Detaching to [DSP2] ...
[HOST] [EVE4 ] 52.701701 s: SYSTEM: Detaching to [DSP2] ... SUCCESS !!!
[HOST] [EVE4 ] 52.702738 s: SYSTEM: Detaching to [DSP1] ...
[HOST] [EVE4 ] 52.704264 s: SYSTEM: Detaching to [DSP1] ... SUCCESS !!!
[HOST] [EVE4 ] 52.705270 s: SYSTEM: Detaching to [IPU2] ...
[HOST] [EVE4 ] 52.706765 s: SYSTEM: Detaching to [IPU2] ... SUCCESS !!!
[HOST] [IPU2 ] 52.747941 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [IPU2 ] 52.748307 s: SYSTEM: Detaching to [EVE4] ... SUCCESS !!!
[HOST] [IPU2 ] 52.748398 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [IPU2 ] 52.748673 s: SYSTEM: Detaching to [EVE3] ... SUCCESS !!!
[HOST] [IPU2 ] 52.748764 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [IPU2 ] 52.749100 s: SYSTEM: Detaching to [EVE2] ... SUCCESS !!!
[HOST] [IPU2 ] 52.749191 s: SYSTEM: Detaching to [EVE1] ...
[HOST] [IPU2 ] 52.749466 s: SYSTEM: Detaching to [EVE1] ... SUCCESS !!!
[HOST] [IPU2 ] 52.749557 s: SYSTEM: Detaching to [DSP2] ...
[HOST] [IPU2 ] 52.749801 s: SYSTEM: Detaching to [DSP2] ... SUCCESS !!!
[HOST] [IPU2 ] 52.749893 s: SYSTEM: Detaching to [DSP1] ...
[HOST] [IPU2 ] 52.750198 s: SYSTEM: Detaching to [DSP1] ... SUCCESS !!!
[HOST] [IPU2 ] 52.750411 s: ###############APPLICATION END########################

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

And the next message is showed when i execute apps again. The apps was stopped after showing this message.

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

[HOST] OSA: MEM: 0: Mapped 0xa0100000 to 0xb6963000 of size 0x00100000
[HOST] OSA: MEM: 1: Mapped 0x84203000 to 0xa3d63000 of size 0x12c00000
[HOST] OSA: MEM: 2: Mapped 0xa0200000 to 0xa3ca3000 of size 0x00040000
[HOST] OSA: MEM: 3: Mapped 0xa02c0000 to 0xa3ce3000 of size 0x00080000
[HOST] OSA: MEM: 4: Mapped 0x00000000 to 0x00000000 of size 0x00000000
[HOST] OSA: HOST Remote Log Shared Memory @ 0xa024f140
[HOST] OSA: DSP1 Remote Log Shared Memory @ 0xa02769e0
[HOST] OSA: DSP2 Remote Log Shared Memory @ 0xa029e280
[HOST] OSA: EVE1 Remote Log Shared Memory @ 0xa02c5b20
[HOST] OSA: EVE2 Remote Log Shared Memory @ 0xa02ed3c0
[HOST] OSA: EVE3 Remote Log Shared Memory @ 0xa0314c60
[HOST] OSA: EVE4 Remote Log Shared Memory @ 0xa033c500
[HOST] OSA: IPU2 Remote Log Shared Memory @ 0xa0363da0
[HOST] [HOST ] 126.363081 s: SYSTEM: System A15 Init in progress !!!
[HOST] [DSP1 ] 52.663179 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.673183 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.683187 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.693192 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.703165 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.713170 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP1 ] 52.713322 s: SYSTEM: Detaching to [EVE4] ... SUCCESS !!!
[HOST] [DSP1 ] 52.713353 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [DSP1 ] 52.713444 s: SYSTEM: Detaching to [EVE3] ... SUCCESS !!!
[HOST] [DSP1 ] 52.713475 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [DSP1 ] 52.723174 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [DSP1 ] 52.723296 s: SYSTEM: Detaching to [EVE2] ... SUCCESS !!!
[HOST] [DSP1 ] 52.723327 s: SYSTEM: Detaching to [EVE1] ...
[HOST] [DSP1 ] 52.733178 s: SYSTEM: Detaching to [EVE1] ...
[HOST] [DSP1 ] 52.733300 s: SYSTEM: Detaching to [EVE1] ... SUCCESS !!!
[HOST] [DSP1 ] 52.733331 s: SYSTEM: Detaching to [DSP2] ...
[HOST] [DSP1 ] 52.733422 s: SYSTEM: Detaching to [DSP2] ... SUCCESS !!!
[HOST] [DSP1 ] 52.733453 s: SYSTEM: Detaching to [IPU2] ...
[HOST] [DSP1 ] 52.733544 s: SYSTEM: Detaching to [IPU2] ... SUCCESS !!!
[HOST] [DSP2 ] 52.665192 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.675166 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.685170 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.695174 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.705179 s: SYSTEM: Detaching to [EVE4] ...
[HOST] [DSP2 ] 52.705301 s: SYSTEM: Detaching to [EVE4] ... SUCCESS !!!
[HOST] [DSP2 ] 52.705362 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [DSP2 ] 52.715183 s: SYSTEM: Detaching to [EVE3] ...
[HOST] [DSP2 ] 52.715305 s: SYSTEM: Detaching to [EVE3] ... SUCCESS !!!
[HOST] [DSP2 ] 52.715335 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [DSP2 ] 52.725187 s: SYSTEM: Detaching to [EVE2] ...
[HOST] [DSP2 ] 52.725309 s: SYSTEM: Detaching to [EVE2] ... SUCCESS !!!
[HOST] [DSP2 ] 52.725340 s: SYSTEM: Detaching to [EVE1] ...
[HOST] [DSP2 ] 52.725431 s: SYSTEM: Detaching to [EVE1] ... SUCCESS !!!
[HOST] [DSP2 ] 52.725462 s: SYSTEM: Detaching to [DSP1] ...
[HOST] [DSP2 ] 52.725553 s: SYSTEM: Detaching to [DSP1] ... SUCCESS !!!
[HOST] [DSP2 ] 52.725584 s: SYSTEM: Detaching to [IPU2] ...
[HOST] [DSP2 ] 52.725645 s: SYSTEM: Detaching to [IPU2] ... SUCCESS !!!

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

Could you let me know how can i re-execute apps after exiting with 'z' option?

Regards,

Yoo.