Chencheng, I am sorry that we could not be of any help. I've personally validated the build 2 different times and my peer has done so as well and we are unable to replicate this behavior. I am attaching the full printenv list in case it is useful to you. e2e.ti.com/.../3250.printenv.txt
↧
Forum Post: RE: TMDSEVM572X: Failed to load '/boot/am57xx-evm-reva3.dtb'
↧
Forum Post: RE: SK-AM64B: AM64x DFU and UART Initialization Procedure
The following patch works on my modified (see above) and unmodified SK-AM64B eval boards. By 'works', I mean boots to U-Boot prompt using USB DFU. diff --git a/arch/arm/dts/k3-am64-main.dtsi b/arch/arm/dts/k3-am64-main.dtsi index f8d8b9e85d..c1e0cec82b 100644 --- a/arch/arm/dts/k3-am64-main.dtsi +++ b/arch/arm/dts/k3-am64-main.dtsi @@ -623,7 +623,7 @@ "peripheral", "otg"; maximum-speed = "super-speed"; - dr_mode = "otg"; + dr_mode = "peripheral"; }; }; diff --git a/arch/arm/dts/k3-am642-sk-u-boot.dtsi b/arch/arm/dts/k3-am642-sk-u-boot.dtsi index f9393e098a..484592772c 100644 --- a/arch/arm/dts/k3-am642-sk-u-boot.dtsi +++ b/arch/arm/dts/k3-am642-sk-u-boot.dtsi @@ -245,7 +245,7 @@ }; &usb0 { - dr_mode = "host"; + dr_mode = "peripheral"; bootph-pre-ram; }; diff --git a/arch/arm/dts/k3-am642-sk.dts b/arch/arm/dts/k3-am642-sk.dts index d3aa290..4ac7a80 100644 --- a/arch/arm/dts/k3-am642-sk.dts +++ b/arch/arm/dts/k3-am642-sk.dts @@ -313,11 +313,12 @@ &usbss0 { ti,vbus-divider; + ti,usb2-only; }; &usb0 { - dr_mode = "host"; - maximum-speed = "super-speed"; + dr_mode = "peripheral"; + maximum-speed = "high-speed"; pinctrl-names = "default"; pinctrl-0 = ; phys = ;
↧
↧
Forum Post: RE: TDA4VM: Is it normal that the mathlib powdp() function runs slower on the TDA4VM C66 than on the CPU?
Hi, I wouldn't expect such performance on C66x when using the mathlib libraries. Are you running on a TI TDA4VM EVM with the C66x processor running at 1.35GHz? Best, Asha
↧
Forum Post: RE: SK-AM62A-LP: Monochrome image processing capabilities
Hello Jaimin, I would recommend you to follow the AM6xA ISP Tuning Guide , section 6.2 Enable Camera Streaming With Initial VPAC Configuration, to generate a baseline ISP configuration for monochrome sensor. You can choose MONO as the color pattern. You'll need to add a fake sensor to Gstreamer plugin as described in sections 5.3 Updating TIOVX Modules and 5.4 Update GStreamer Plug-in for VISS. Then you can run a pipeline similar to the one with IMX219. You can also get an OV9281 camera (not expensive) and do the experiment. Regards, Jianzhong
↧
Forum Post: RE: J784S4XEVM: NEON load - off load to C7X
Hi Narendra, What type of algorithms and functions would you be trying to move from utilizing NEON to utilizing the C7x? Best, Asha
↧
↧
Forum Post: RE: AM6422: [u-boot] How the uboot sign the u-boot.img with customer keys?
The build log below is from A53 u-boot build process using SDK 8.x, where "SECURE u-boot-nodtb.bin_HS" & "SECURE arch/arm/dts/k3-am62x-lp-sk.dtb_HS" are called via https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/mach-k3/config_secure.mk?h=08.06.00.007#n9 SECURE u-boot-nodtb.bin_HS MKIMAGE u-boot.img COPY u-boot.dtb MKIMAGE u-boot-dtb.img MKIMAGE fit-dtb.blob SECURE arch/arm/dts/k3-am62x-lp-sk.dtb_HS Best, -Hong
↧
Forum Post: RE: CCSTUDIO: Error when migrating AM263Px package in SysConfig
Hi Aswathi, 1) I tried your recommended solution. Open sysconfig Click package->“Switch” Select New Value -> ZCZ_C “Confirm” Save Acknowledge error “OK I see the package in sysconfig is changed: * @cliArgs --device "AM263Px" --package "ZCZ_C" --part "AM263P4" --context "r5fss0-1" --product "MCU_PLUS_SDK_AM263Px@09.01.00" However, when I open sysconfig again, and click “Show Device View” the package is still ZCZ_S. Also, I can not assign signals to pins not available on the ZCZ_S package. For example, I cannot assign GPIO71 – GPIO74 because they do not appear in the list of available pins as seen here: For reference: Note: I am using the latest CCS, and SDK. Am I doing something wrong? 2) I noticed that in sysconfig is "--product "MCU_PLUS_SDK_AM263Px@09.01.00"". Could this be a problem? Note: I may 'port' my sysconfig to 09.02. Regards, Scott
↧
Forum Post: RE: PROCESSOR-SDK-AM62X: How to start the OV5647 Live camera on TI Apps Launcher
[quote userid="599664" url="~/support/processors-group/processors/f/processors-forum/1362717/processor-sdk-am62x-how-to-start-the-ov5647-live-camera-on-ti-apps-launcher/5201938#5201938"]I have tried to capture the image but not able to capture what can be the problem ?[/quote] I see the following message: Video[ 5319.337288] v4l2_get_link_freq: Link frequency estimated using pixel rate: result might be inaccurate format set: UYVY (59565955) 640x480 (stride 1280) field none bu[ 5319.348495] v4l2_get_link_freq: Consider implementing support for V4L2_CID_LINK_FREQ in the transmitter driver Please try to specify the link frequency in the device tree overlay. [quote userid="599664" url="~/support/processors-group/processors/f/processors-forum/1362717/processor-sdk-am62x-how-to-start-the-ov5647-live-camera-on-ti-apps-launcher/5202066#5202066"]also i am not able to see the output of lsmod | grep ov5647[/quote] Not sure. If ov5647 was not loaded, you wouldn't be able to see anything from media-ctl -p. [quote userid="599664" url="~/support/processors-group/processors/f/processors-forum/1362717/processor-sdk-am62x-how-to-start-the-ov5647-live-camera-on-ti-apps-launcher/5202081#5202081"]Display the supported frame rates for a specific format and frame size ?[/quote] What does "v4l2-ctl -d /dev/v4l-subdevX --list-subdev-mbus-codes pad=0" show?
↧
Forum Post: RE: SK-TDA4VM: J721EXSKG01EVM
Hi Victor, Please expect the Yocto build to take about half a day depending on the PC and especially if its the first time you're building. Thank you, Fabiana
↧
↧
Forum Post: RE: AM625: Error while running AM62X OTP Keywriter
Can we capture the TIFS log when running key programming. You may refer to in AM62x OTP KW user guide PDF. Here is reference on TIFS log, i.e. from "MAIN UART1" if it is available on your board. https://software-dl.ti.com/tisci/esd/latest/4_trace/trace.html#trace-uart-allocation Best, -Hong
↧
Forum Post: RE: AM625-Q1: Porting UBOOT to custom hardware
From my knowledge, USB host boot might not fully work out-of-box in SDK on TI reference board. Have you tried booting from SD with your u-boot build on TI board? Best, -Hong
↧
Forum Post: J784S4XEVM: Unexpected Running State of C71X_0 After Executing launch.js Script: Causes debugging Issues.
Part Number: J784S4XEVM Hello TI Team, We are facing issues while trying to debug C7X with CCS IDE. We have followed below page to setup debug environment. https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j784s4/09_00_00_02/exports/docs/psdk_rtos/docs/user_guide/ccs_setup_j784s4.html Issues: 1. What could be causing an 'Error connecting to Target (Error: 1044)' despite the test connection being successful? 2. Is it expected for C71X_0 to enter a running state after executing the launch.js script? If not, what could be causing this behavior? Please find the attached snaps for your references. Need clarification here: Are the debugging steps for the C7x and R5F processors the same, or do they differ? If they differ, what are the key differences in the debugging procedures for these two types of processors? Can you help us with detailed instructions or documentation for C7X processor for debugging and fixing these issues. regards, Jayasankar
↧
Forum Post: RE: TMDSEVM572X: Failed to load '/boot/am57xx-evm-reva3.dtb'
Could you show me your Yocto u-boot deploy folder? Like this: $ ll build/arago-tmp-default-glibc/work/am57xx_evm-oe-linux-gnueabi/u-boot-ti-staging/1_2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1/deploy-u-boot-ti-staging/ total 1.8M drwxr-xr-x 2 czhang czhang 4.0K May 17 15:04 ./ drwxr-xr-x 9 czhang czhang 4.0K May 17 20:03 ../ lrwxrwxrwx 2 czhang czhang 55 May 17 15:04 MLO -> MLO-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1 lrwxrwxrwx 2 czhang czhang 55 May 17 15:04 MLO-am57xx-evm -> MLO-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1 -rw-r--r-- 2 czhang czhang 126K May 17 15:04 MLO-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1 lrwxrwxrwx 2 czhang czhang 35 May 17 15:04 extlinux.conf -> extlinux.conf-am57xx-evm-r0_tisdk_1 lrwxrwxrwx 2 czhang czhang 35 May 17 15:04 extlinux.conf-am57xx-evm -> extlinux.conf-am57xx-evm-r0_tisdk_1 -rw-r--r-- 2 czhang czhang 177 May 17 15:04 extlinux.conf-am57xx-evm-r0_tisdk_1 -rw-r--r-- 2 czhang czhang 1.5M May 17 15:04 u-boot-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1.img lrwxrwxrwx 2 czhang czhang 62 May 17 15:04 u-boot-am57xx-evm.img -> u-boot-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1.img lrwxrwxrwx 2 czhang czhang 66 May 17 15:04 u-boot-spl.bin -> u-boot-spl.bin-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1* lrwxrwxrwx 2 czhang czhang 66 May 17 15:04 u-boot-spl.bin-am57xx-evm -> u-boot-spl.bin-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1* -rwxr-xr-x 2 czhang czhang 126K May 17 15:04 u-boot-spl.bin-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1* lrwxrwxrwx 2 czhang czhang 62 May 17 15:04 u-boot.img -> u-boot-am57xx-evm-2023.04+gitAUTOINC+f9b966c674-r0_tisdk_1.img
↧
↧
Forum Post: RE: TDA4AEN-Q1: SDK 9.2: Why can't viss node output parameter vx_image be added to graph parameter list
No, not yet
↧
Forum Post: RE: TMDS64EVM: Access ETB or TBR
Hi Anthony, Thank You so much for this. I just need little more help, I'm able to see the ETB Register Summary after RAT on 0x73C025000 this address. But according to TRM of AM64x TI Trace Buffer Router (TBR) with 64KB of storage: the TBR can function as a trace buffer or as a system bridge. As a trace buffer, the TBR can be setup to capture trace data until the internal buffer fills or it can operate as a circular buffer that will capture continuously. When configured as a system bridge the TBR’s storage becomes an elastic buffer that supports the concurrent queueing and dequeuing of trace traffic. The system bridge mode supports interrupt and event notification capabilities that support integration with device level CPUs and/or DMAs to support a variety of use cases, including, for e.g., relocation of trace data to DDR and off-chip export over USB. not more information that this is provided. How do I relocate the trace data to DDR ? or if I have the ETB register Table address , how do I start reading data and more importantly for where ? Do I need to add a memory region in RAM of 64KB for TBR, then how do I start writing my ETM to this ? or is it already mapped to some physical space ? If so where can I find the start address of that physical space?
↧
Forum Post: RE: PROCESSOR-SDK-J784S4: MAIN UART receiving(RX) not working.
Hello Keerthy, We have a requirement to use wkup_uart0 as a debug console on the J784s4-EVM board. I would like to configure wkup_uart0 as a debug console for all the components like tiboot3.bin, tispl.bin and ATF and u-boot and kernel. i followed your below forum, but i didn't succeeded. i am able to configure wkup_uart0 for u-boot and kernel and could see the prints on the wkup_uart0 but terminal is not receiving any inputs. also modified ATF source and copied bl31 to prebuilt directory and rebuilt the u-boot. but booting is stuck before ATF. could you please list what are the files i have to modify from system level to use wkup_uart0 as a debug console? e2e.ti.com/.../3718577 regards, Prasad.
↧
Forum Post: J784S4XEVM: EVM demos connect to Display
Part Number: J784S4XEVM Hi, I am trying to run the vision apps demos given in 9.02 RTOS SDK on J784S4 EVM. I got the apps running, and I connected monitor on display port on main EVM board. Monitor is powered externally, but I don't see anything on the monitor. As per instructions given here, https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j784s4/09_02_00_05/exports/docs/vision_apps/docs/user_guide/BUILD_INSTRUCTIONS.html#MAKEFILE_OPTIONS I made sure that ENABLE_DSS_EDP is enabled in the file, ./vision_apps/platform/j784s4/rtos/common/app_cfg_mcu2_0.h In the below file, I see that #define ENABLE_DSS_SINGLE and #define ENABLE_DSS_EDP Please check and confirm if it needs any modifications. Attached is the file, /* * * Copyright (c) 2018 Texas Instruments Incorporated * * All rights reserved not granted herein. * * Limited License. * * Texas Instruments Incorporated grants a world-wide, royalty-free, non-exclusive * license under copyrights and patents it now or hereafter owns or controls to make, * have made, use, import, offer to sell and sell ("Utilize") this software subject to the * terms herein. With respect to the foregoing patent license, such license is granted * solely to the extent that any such patent is necessary to Utilize the software alone. * The patent license shall not apply to any combinations which include this software, * other than combinations with devices manufactured by or for TI ("TI Devices"). * No hardware patent is licensed hereunder. * * Redistributions must preserve existing copyright notices and reproduce this license * (including the above copyright notice and the disclaimer and (if applicable) source * code license limitations below) in the documentation and/or other materials provided * with the distribution * * Redistribution and use in binary form, without modification, are permitted provided * that the following conditions are met: * * * No reverse engineering, decompilation, or disassembly of this software is * permitted with respect to any software provided in binary form. * * * any redistribution and use are licensed by TI for use only with TI Devices. * * * Nothing shall obligate TI to provide you with source code for the software * licensed and provided to you in object code. * * If software source code is provided to you, modification and redistribution of the * source code are permitted provided that the following conditions are met: * * * any redistribution and use of the source code, including any resulting derivative * works, are licensed by TI for use only with TI Devices. * * * any redistribution and use of any object code compiled from the source code * and any resulting derivative works, are licensed by TI for use only with TI Devices. * * Neither the name of Texas Instruments Incorporated nor the names of its suppliers * * may be used to endorse or promote products derived from this software without * specific prior written permission. * * DISCLAIMER. * * THIS SOFTWARE IS PROVIDED BY TI AND TI'S LICENSORS "AS IS" AND ANY EXPRESS * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. * IN NO EVENT SHALL TI AND TI'S LICENSORS BE LIABLE FOR ANY DIRECT, INDIRECT, * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY * OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE * OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED * OF THE POSSIBILITY OF SUCH DAMAGE. * */ #ifndef APP_CFG_MCU2_0_H_ #define APP_CFG_MCU2_0_H_ #include #define L3_MEM_SIZE (MAIN_OCRAM_MCU2_0_SIZE) #define DDR_HEAP_MEM_SIZE (DDR_MCU2_0_LOCAL_HEAP_SIZE) #define DDR_VISS_HEAP_MEM_SIZE (DDR_MCU2_0_VISS_CONFIG_HEAP_SIZE) /* There are several external board interfaces to the SoC that can either be controlled by the MCU RTOS core * or the MPU HLOS core. The top level build option BUILD_MCU_BOARD_DEPENDENCIES can be used to optionally enable * these interfaces (user can override specific flags in this file), or disable them. */ #ifdef BUILD_MCU_BOARD_DEPENDENCIES #define ENABLE_CSI2RX #define ENABLE_CSI2TX #undef ENABLE_DSS_HDMI /* IMPORANT NOTE: * - Only one of ENABLE_DSS_SINGLE or ENABLE_DSS_DUAL should be defined * - When ENABLE_DSS_SINGLE is defined, only one of ENABLE_DSS_DSI or ENABLE_DSS_EDP should be defined * - When ENABLE_DSS_DUAL is defined, ENABLE_DSS_DSI and ENABLE_DSS_EDP are not used, both EDP and DSI are enabled unconditionally */ #define ENABLE_DSS_SINGLE #undef ENABLE_DSS_DUAL #if defined(ENABLE_DSS_DUAL) #undef ENABLE_DSS_SINGLE #define ENABLE_DSS_EDP #define ENABLE_DSS_DSI #elif defined(ENABLE_DSS_SINGLE) #undef ENABLE_DSS_DUAL #undef ENABLE_DSS_DSI #define ENABLE_DSS_EDP #endif #if defined(ENABLE_DSS_DSI) #undef ENABLE_CSI2TX #endif #define ENABLE_I2C #define ENABLE_BOARD #else #undef ENABLE_CSI2RX #undef ENABLE_CSI2TX #undef ENABLE_DSS_SINGLE #undef ENABLE_DSS_DUAL #undef ENABLE_DSS_EDP #undef ENABLE_DSS_HDMI #undef ENABLE_DSS_DSI #undef ENABLE_I2C #undef ENABLE_BOARD #endif #define ENABLE_FVID2 #define ENABLE_VHWA_VPAC0 #undef ENABLE_VHWA_DMPAC #if defined (ENABLE_DSS_DSI) && !defined(ENABLE_I2C) #error "DSI output depends on I2C, Include ENABLE_I2C" #endif #if defined (ENABLE_DSS_HDMI) && !defined(ENABLE_I2C) #error "HDMI output depends on I2C, Include ENABLE_I2C" #endif #if defined (ENABLE_DSS_DSI) && defined (ENABLE_CSI2TX) #error "CSI2TX and DSI cannot be active at the same time" #endif #endif /* APP_CFG_MCU2_0_H_ */ Please help to fix this on priority. Thank you. Regards, -Narendra
↧
↧
Forum Post: RE: TDA4AL-Q1: TDA4AL-Q1: MAIN_CPSW0 RMII interfaces connect to BCM89830 but cannot ping to PC
Hi, Tanmay Patil I config U24 Pin as CLKOUT mode , devmem2 tool log is provided below root@j721s2-evm:~# devmem2 0x11c0a8 /dev/mem opened. Memory mapped at address 0xffff86fd4000. Read at address 0x0011C0A8 (0xffff86fd40a8): 0x00010008 but , I can't see 50Mhz clock on oscilloscope。 I'm not sure if I missed some configuration。 Regards, Shice
↧
Forum Post: RE: SK-AM62A-LP: Monochrome image processing capabilities
Hi Jianzhong, Thank you for providing above information. We will create dummy config file for image sensor and try to execute pipeline. Also we are ordering OV9281 camera for testing. We need to close our project architecture phase in couple of days and actual validation on OV9281 will take some time as we dont have this sensor currently. We need just one confirmation from your side so we can close our architecture phase. Need Confirmation: We can encode 1080p@60 stream from monochrome sensor using MJPEG hardware encoder ("v4l2jpegenc") and stream it with AM62A34 processor. (Where image sensor provide 8/10 bit RAW data and it is processed through ISP before passing to v4l2jpegenc) Could you please provide confirmation on above point ? Also it would be helpful if you can send us validated gstreamer pipeline for this case with OV9281. Is tiovxdlcolorconvert plugin hardware accelerated? Will it perform color conversion on ISP? Thanks
↧
Forum Post: RE: PROCESSOR-SDK-AM62X: How to start the OV5647 Live camera on TI Apps Launcher
[quote userid="35284" url="~/support/processors-group/processors/f/processors-forum/1362717/processor-sdk-am62x-how-to-start-the-ov5647-live-camera-on-ti-apps-launcher/5203191#5203191"]Please try to specify the link frequency in the device tree overlay.[/quote] About link frequency in the device tree overlay here you can see my dts file :- // SPDX-License-Identifier: GPL-2.0 /* * IMX219 (RPi v2) Camera Module * Copyright (C) 2023 Texas Instruments Incorporated - https://www.ti.com/ */ /dts-v1/; /plugin/; #include &{/} { clk_ov5647_fixed: ov5647-xclk { compatible = "fixed-clock"; #clock-cells = ; clock-frequency = ; }; }; &main_i2c2 { #address-cells = ; #size-cells = ; status = "okay"; i2c-switch@71 { compatible = "nxp,pca9543"; #address-cells = ; #size-cells = ; reg = ; /* CAM port */ i2c@1 { #address-cells = ; #size-cells = ; reg = ; ov5640: camera@36 { compatible = "ovti,ov5647"; reg = ; clocks = ; clock-names = "xclk"; reset-gpios = ; port { csi2_cam0: endpoint { remote-endpoint = ; link-frequencies = /bits/ 64 ; clock-lanes = ; data-lanes = ; }; }; }; }; }; }; &csi0_port0 { status = "okay"; csi2rx0_in_sensor: endpoint { remote-endpoint = ; bus-type = ; /* CSI2 DPHY. */ clock-lanes = ; data-lanes = ; }; }; in above dts file you can see i have set linking frequency how can i know that it is compatible or not ?
↧