Hi： board：Custom board AM5708 I wrote an openCV acquisition display program directly. It is found that the first execution of the program cannot be displayed, and the second execution of the program can be displayed. I think odd numbers can't be successful, even numbers can be displayed successfully. But it will only be like this on SDK 5.3, it can be normal on SDK version 4.3. (Please visit the site to view this file)
↧
Forum Post: AM5708：SDK 5.3 Display error
↧
Forum Post: RE: CCS/AM5718: PRU-EMAC Loopback example
Hi Satheesh, Were you able to get the loopback adapter and successfully run the example? Can we close the thread? Regards, Garrett
↧
↧
Forum Post: DRA750: MMC1 timings in Default Speed Mode
Part Number: DRA750 A customer identified a timing violation in his system using MMC1 in Default Speed mode. Based on our DM, the required hold time in this mode is 20.46ns. Measured hold time is only in the range of 15ns. So far connected SD cards are working without any issues even with this hold time violation. Anyhow, this problem needs to be fixed for an automotive system in production. Can anybody explain why DRA75x needs a hold time of more than 20ns only in DS mode (see DM extract below)? Isn't that violating the SD Specification Part 1 (Physical Layer Specification) which defines an input set-up and hold time for CMD and DAT of always 5ns? Best regards, Manfred
↧
Forum Post: RE: AM5708: OpenCV display issue
Hi, OpenCV is an open-source BSD-licensed library that includes several hundreds of computer vision algorithms. It is designed for computational efficiency with strong focus on real-time application. TI OpenCV provides a transparent API that allows seamless offloads of OpenCL kernels when a supported accelerator is available For OpenCV programming, please refer to opencv tutorial, https://www.opencv-srf.com/p/introduction.html For Display on AM57x, please refer to http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_Graphics.html Rex
↧
Forum Post: RE: Linux/AM3358: how to apply patch to sdk linux kernel
Hello, Please first confirm if these patches are not already applied to the kernel version that you are using. It seems to me like there are already there. This is general linux question which you could google. But you could use git apply command. But first cp the patch in /board-support/linux- and execute it from there. Of course, you could apply it manually also. Hope this helps. BR Margarita
↧
↧
Forum Post: RE: AM5706: Switch solution with PRU-ICSS
Sam, The firmware as the document states can support 2 port only switching. Regards, Garrett
↧
Forum Post: RE: Linux/AM3358: On chip RTC not setting time correctly on reboot
Pavel, thank you for your prompt reply. Regarding the version, we are using the TI SDK Linux RT AM335x V 5.00.15. And I have checked all the voltages on the lines after pulling power from the board and clearly the PMIC is still operating (seems to be the main thrust of the thread you shared) and the voltage domains appear to all be functional. Am I completely off track when I say that I think the most important line I'm seeing is that [ 1.473132] hctosys: unable to open rtc device (rtc0) that seems to be the place that the RTC actually is used to set the system time if I'm not mistaken about what hctosys does. This thread covers where I got the idea that it was related to compiling omap_rtc into the kernel instead of having it as a kernel module (which it is by default) https://patchwork.ozlabs.org/patch/736336/
↧
Forum Post: RE: Linux/AM3358: 4G USB Simcom module IC detect issue
Hi RonB , Dk . I checked the kernel in sdk , the patches you suggested are already applied . so in the next step i checked this values . root@am335x-evm:~# devmem2 0x47401c60 b 1 /dev/mem opened. Memory mapped at address 0xb6ffb000. Read at address 0x47401C60 (0xb6ffbc60): 0x5D Write at address 0x47401C60 (0xb6ffbc60): 0x01, readback 0x01 root@am335x-evm:~# devmem2 0x47401c01 b /dev/mem opened. Memory mapped at address 0xb6fc7000. Read at address 0x47401C01 (0xb6fc7c01): 0xF2 root@am335x-evm:~# devmem2 0x47401c60 b /dev/mem opened. Memory mapped at address 0xb6f68000. Read at address 0x47401C60 (0xb6f68c60): 0x5D root@am335x-evm:~# lsusb -t /: Bus 01.Port 1: Dev 1, class="root_hub", Driver=musb-hdrc/1p, 480M but error is common root@am335x-evm:~# [ 62.950965] usb 1-1: new high-speed USB device number 2 uc [ 63.100902] usb 1-1: device descriptor read/64, error -71 [ 63.370927] usb 1-1: device descriptor read/64, error -71 [ 63.640906] usb 1-1: new high-speed USB device number 3 using musb-hdrc [ 63.790930] usb 1-1: device descriptor read/64, error -71 [ 64.060898] usb 1-1: device descriptor read/64, error -71 [ 64.180900] usb usb1-port1: attempt power cycle [ 64.670908] usb 1-1: new high-speed USB device number 4 using musb-hdrc [ 65.260923] usb 1-1: new high-speed USB device number 5 using musb-hdrc
↧
Forum Post: RE: RTOS/AM6548: Problems initialising ICSSG ETH PHY with Board_Init
Alex, Is the issue still pending? The binary generated in pdk_am65xx_1_0_4\packages\ti\binary\Emac_Icssg_TestApp\bin\am65xx_idk should work as is. Regards, Garrett
↧
↧
Forum Post: RE: Linux/AM5718: McSPI device tree settings
Arpita, From what I understand, on your custom board you have only ADC attached to McSPI3. Thus I would suggest you to remove sn65hvs882 node and add ADC node in am57xx-idk-common.dtsi And I would suggest you to build your DTB file according to the user guide instructions: Compiling the Device Tree Binaries Regards, Pavel
↧
Forum Post: OMAP-L138: USB times out in Windows 10
On previous thread 2942257, it was suggested to migrate to the SDK for a RTOS........is there any other option other than changing to a RTOS that would enable USB to work in WIndows 10? Changning our embedded system to RTOS would not be possible at this point. Thanks, David Masdon David.Masdon@L3T.com 469-777-5075
↧
Forum Post: Linux/AM5728: PWM on Timer15
Part Number: AM5728 Tool/software: Linux I'm using TI's Linux Kernel 4.9 with SDK 4.02 on my custom AM5728 board. My board got a PWM controlled beeper on Timer 15. The hardware was verified by directly manipulating the register bank associated with it, but setting it up through the Linux Device Tree is proving it to be difficult. We have enabled a few things in the kernel: CONFIG_PWM_TIEHRPWM=y CONFIG_PWM_TIPWMSS=y CONFIG_INPUT_PWM_BEEPER=y CONFIG_PWM_OMAP_DMTIMER=y And added a node here in the DTS: beeper { compatible = "pwm-beeper"; pwms = ; }; The U-Boot is also mux'ed correctly. With the above changes, there is still no new device under /sys/class/pwm. Anywhere else I should look at?
↧
Forum Post: Linux/TDA2SX: How do I create a Shared storage area that both Linux and RTOS can access
Part Number: TDA2SX Tool/software: Linux Hi, I developed on PROCESSOR_SDK_VISION_03_06_00_00, and my chip is TDA2Sx . I have two links, network test LINk and McSpi test LINk, among which network test LINk runs on A15 and Linux, while McSpi test LINk runs on IPU2 and RTOS. I wanted to share data between two links, so I wanted to create a storage area that both links could access. How do I create it? Thanks， Kepei
↧
↧
Forum Post: Compiler/AM4379: OpenGL ES2.0 cross compile
Part Number: AM4379 Tool/software: TI C/C++ Compiler there is a cube example with OpenGLES 2.0 in QTCreator, I cross-compile it in TI environment, but when I run it in TL437x-evm-A2 board,there is nothing on the LCD surface ,just the whole screen went black,what problem may I encounter? The Demo OGLES2ChmeleonMan can run in the board. My environment is ti-processor-sdk-linux-am437x-evm-01.00.00.03-Linux-x86-Install.bin and QT5.4.1. and the compile info is : 11:37:04: 为项目cube执行步骤 ... 11:37:04: 正在启动 "/media/tl437x/ti/linux-devkit/sysroots/i686-arago-linux/usr/bin/qt5/qmake" /home/tl/Desktop/qt/cube5.4.1/cube/cube.pro -r -spec linux-oe-g++ CONFIG+=debug CONFIG+=declarative_debug CONFIG+=qml_debug 11:37:04: 进程"/media/tl437x/ti/linux-devkit/sysroots/i686-arago-linux/usr/bin/qt5/qmake"正常退出。 11:37:04: 正在启动 "/usr/bin/make" -w make: Entering directory `/home/tl/Desktop/qt/cube5.4.1/cube-build-Desktop-Debug' arm-linux-gnueabihf-g++ -c -pipe -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi -Wno-psabi -g -Wall -W -D_REENTRANT -fPIE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I../cube -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5 -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtWidgets -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtGui -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtCore -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o main.o ../cube/main.cpp arm-linux-gnueabihf-g++ -c -pipe -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi -Wno-psabi -g -Wall -W -D_REENTRANT -fPIE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I../cube -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5 -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtWidgets -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtGui -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtCore -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o mainwidget.o ../cube/mainwidget.cpp arm-linux-gnueabihf-g++ -c -pipe -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi -Wno-psabi -g -Wall -W -D_REENTRANT -fPIE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I../cube -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5 -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtWidgets -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtGui -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtCore -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o geometryengine.o ../cube/geometryengine.cpp /media/tl437x/ti/linux-devkit/sysroots/i686-arago-linux/usr/bin/qt5//rcc -name shaders ../cube/shaders.qrc -o qrc_shaders.cpp arm-linux-gnueabihf-g++ -c -pipe -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi -Wno-psabi -g -Wall -W -D_REENTRANT -fPIE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I../cube -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5 -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtWidgets -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtGui -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtCore -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o qrc_shaders.o qrc_shaders.cpp /media/tl437x/ti/linux-devkit/sysroots/i686-arago-linux/usr/bin/qt5//rcc -name textures ../cube/textures.qrc -o qrc_textures.cpp arm-linux-gnueabihf-g++ -c -pipe -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi -Wno-psabi -g -Wall -W -D_REENTRANT -fPIE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I../cube -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5 -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtWidgets -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtGui -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtCore -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o qrc_textures.o qrc_textures.cpp /media/tl437x/ti/linux-devkit/sysroots/i686-arago-linux/usr/bin/qt5//moc -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/media/tl437x/ti/linux-devkit/sysroots/i686-arago-linux/mkspecs/linux-oe-g++ -I/home/tl/Desktop/qt/cube5.4.1/cube -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5 -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtWidgets -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtGui -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtCore -I. -I/opt/linaro-2013.03/arm-linux-gnueabihf/include -I/opt/linaro-2013.03/arm-linux-gnueabihf/include/c++/4.7.3 -I/opt/linaro-2013.03/arm-linux-gnueabihf/include/c++/4.7.3/arm-linux-gnueabihf -I/opt/linaro-2013.03/arm-linux-gnueabihf/include/c++/4.7.3/backward -I/opt/linaro-2013.03/lib/gcc/arm-linux-gnueabihf/4.7.3/include -I/opt/linaro-2013.03/lib/gcc/arm-linux-gnueabihf/4.7.3/include-fixed -I/home/gtbldadm/ti/oe-layersetup/build-CORTEX_1/arago-tmp-external-linaro-toolchain/sysroots/am437x-evm/usr/include ../cube/mainwidget.h -o moc_mainwidget.cpp arm-linux-gnueabihf-g++ -c -pipe -march=armv7-a -marm -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9 --sysroot=/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi -Wno-psabi -g -Wall -W -D_REENTRANT -fPIE -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I../cube -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5 -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtWidgets -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtGui -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/include/qt5/QtCore -I. -I/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/lib/qt5/mkspecs/linux-oe-g++ -o moc_mainwidget.o moc_mainwidget.cpp arm-linux-gnueabihf-g++ --sysroot=/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi -o cube main.o mainwidget.o geometryengine.o qrc_shaders.o qrc_textures.o moc_mainwidget.o -L/media/tl437x/ti/linux-devkit/sysroots/cortexa9t2hf-vfp-neon-linux-gnueabi/usr/lib -lQt5Widgets -lQt5Gui -lQt5Core -lGLESv2 -lpthread make: Leaving directory `/home/tl/Desktop/qt/cube5.4.1/cube-build-Desktop-Debug' 11:37:08: 进程"/usr/bin/make"正常退出。
↧
Forum Post: Linux/AM5708: How to set DPLL_CORE via Linux
Part Number: AM5708 Tool/software: Linux Hello, I have loaded Linux which was made by Arago to my board with am5708 . It works fine but I can't understand how to set DPLL_CORE right. I have seen DPLL_ABE where I had to set "assigned-clock-rates" in dts file. I was trying to do same for DPLL_CORE but it haven't work. There is N set to 4 and M set to 277 by default and I can't find where I can change that. Would I get troubles in future if I set neccessary values via bare metal way in one of kernel modules? Best regards
↧
Forum Post: AM5728: TMDSEVM572X
Part Number: AM5728 Hello Experts, Our customer had purchased TMDSEVM572X (Revision A) long time before. Recently, customer is considering to purchase TMDSEVM572X again for next projects because TMDSEVM572X (Revision B) has already released now. If customer will order this on TI-store, would you think it is possible to get the latest TMDSEVM572X ? I hope the old TMDSEVM572X already is out of stock, however, we’d like to confirm it. Can we have any your comments on this, please ? And then, customer would like to know the difference among them. I believe customer is able to know difference when customer will check Readme.pdf in AM57x EVM Schematic Source (Rev.C). but, if there is any more helpful documents/URL, can you share them with us, please ? Best regards, Miyazaki
↧
Forum Post: AM5708: Can it support Graphic and Video Accelerators for HD Display ?
Part Number: AM5708 Hi All, I need your advice for a single board computer application which manages the HMI Touch Screen display. I sent to Rogerio in private email the confidential block diagram of this application. The first socket to define is the processor. Main specs for the processor to look at are: Linux Operating System Graphic Accelerator for the Play-Video feature to support HTML5 in full HD Multi-Core if possible 512Mb RAM 2-4Gb Flash, better if scalable (1Gb RAM, 8Gb Flash for the performance solution) Communication Interfaces: 5x UART (1x debug for Linux Console) 1x 10/100/1000 Mb Ethernet 2x I2X 2x USB 2.0 Able to manage a WiFi-BLE module 2x CAN Bus (data rate up to 1Mbit/s), better if separated: 1 for internal peripherals and the other one for external modules 1x SPI for Touch Screen 1x LVDS/HDMI/RGB 1x Analog Audio Output (Optional) One of the main spec is to have the OS Linux. Indeed customer was using NXP platform i.MX 8 and 6 series but the Chromium browser did not support the graphic and video accelerators. In particular GPU (Graphic) was supported but not the VPU (Video). Could you please recommend me any processor that might fit the above specs? Also any TIDesign or AppNote could be interesting. I was thinking at SITARA AM5708 or even DRA726 . Are you aware whether our processor AM5708 might support the above specs? Many Thanks, Antonio
↧
↧
Forum Post: AM5728: DDR3 memory compliance tests (Jedec Standard JESD79-3-1A.01)
Part Number: AM5728 Dear team, we are working to pass compliance tests for DDR3 memory with AM5728 , unfortunately we are failing (Jedec Standard JESD79-3-1A.01). Can you share any test reports that were passed with some of the reference designs, for instance TIDA-00204 ? Thanks for feedback.
↧
Forum Post: TMS320C5545: RTC clock to extrenal device
Part Number: TMS320C5545 Hi, we have used tms320c5505 in other designs and we have the option to use the RTC clock 32.768KHz to drive external unit via RTC_CLKOUT pin (D8). Now we are going to use tms320c5545 for new design and do not see this option. Would this mean we cannot take the clock out to another device? or there is another way? Thanks
↧
Forum Post: SM320C40: SM320C40 IBIS model
Part Number: SM320C40 Looking for 5V SM320C40 IBIS model
↧