Part Number: AMIC110

Tool/software: Linux

Hey everyone,

i'm currently working on a custom board based on the amic110 soc using u-boot and linux as bootloader and OS.

I'm able to boot u-boot and Linux from SD-Card aswell as from UART, but not from SPI flash.

I can write the files, and when i'm trying to read them they are bitwise identical.

The SPI Flash is identified correctly, and everything except the bootprocess is working fine

U-Boot SPL shows only the following Message:

SPL: Unsupported Boot Device!
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

I've already tried several versions of u-boot, including old ones from TI that contain the am335x_evm_spiboot_defconfig, but no success whatsoever.

Any ideas?

Thanks in advance,

Dave

Part Number: AM3358

Tool/software: Linux

Hey everyone,

We are currently thinking of redesigning a existing am3358 based board to use 8b NAND instead of SPI as boot media.

As this board provides dual ethernet using the pru, the TI PinMux tool shows an error on Pin T17, which in case of NAND is used for readybusy line.

As far as i know, NAND does not need the ready/busy line after initialization as it can read the state from an internal register, therefore i will cut the line with a mux as soon as i initialize the PHYs in u-boot/board_init() and use the internal ready/busy bit from the NAND register.

Does anyone know wether a product with PRUETH and NAND using an am335x does already exist, or if it is possible to enable u-boot/Linux to not use the ready/busy line for NAND while being able to boot from NAND?

Thanks in advance

Dave

Part Number: TMS320C6657

Hi，

The customer transplant LWIP on TMS320C6657 base on C6657_EMAC_Example. After test the customer found that when the data packet was sent and received quickly, the GMac could not receive data after a while. And it must be re-initialized before receiving data. Data can be sent and received correctly If the frequency of  is slowed down. The attachment is C6657_EMAC_Example.

(Please visit the site to view this file)

Part Number: TDA2SX

Tool/software: Linux

Hi,

I saw OV2311 support in Processor Vision SDK 3.07 release notes.

Right now, I am using Processor Vision SDK 3.04 on TDA2x. I am working for OV2311 driver to bring-up in TDA2x.

I want to know, whether this OV2311 driver implementation in VSDK 3.07 can be reffered to enable OV2311 support with TDA2x.
If yes,
a) what parts of this driver can be used to support OV2311 with TDA2x.
b) Will it require to port to VSDK v3.07 on TDA2x or is it workable with VSDK v3.04.

Regards,

ARUNKUMAR V N

Part Number: AM5728

Tool/software: Linux

When I run the app in teminal, the app can print context in teminal. But when I add it to matrix and run the app by a icon on matrix, the app can't printf context in terminal. So, where can I find the context?

Part Number: PROCESSOR-SDK-DRA7X

Tool/software: TI-RTOS

Hello TI Team/Shravan,

The Startup KPI for client logo is under 3 seconds, 

In M4 IPL boot we are starting Capture early (usecase below) and GFX pipeline which uses VDRM will be started when linux comes up.

since as per our understanding this is due to dependencies with Western. Is there any way we can remove this dependency and make GFX and VID3 come up early ?

UseCase: weston_dualcamera_dsswb

Capture -> Display_Video   //Started from IPL boot
Capture_1 -> Display_Video1  //Started from IPL boot
DispDistSrc_gfx -> Display_gfx  // Starts after Linux starts since dependeces for western
DispDistSrc_vid3 -> Display_vid3 // Starts after Linux starts since dependeces for western
Capture_dsswb -> Alg_SwCrc

Regards,

Raghu

Part Number: TMDX654IDKEVM

Tool/software: Linux

Hello,

Is there a software way to read the voltage of DC Jack in Linux?

I read the output voltage of the TPS62363 via I2C interface, but this is not what I need for my project.

Best regards!

Part Number: TAS3103A

Hello,

A customer of mine would like to understand the difference between the TAS3103 and the TAS3103A. Can you explain this please?

Thank you.

Part Number: AM5728

Hello

We are using parallel NOR flash for booting of AM5728 in MUXed MOde.

Can you please review the schematic for the same.

Schematic attached for the reference.(Please visit the site to view this file)

Regards

Akash Jain

Part Number: TDA2SX

Tool/software: Linux

Hi,

I am using custom board based on TDA2Sx SOC with tlv320aic34 audio codec and tlv320aic3x linux driver. Below error is coming as i use command aplay. I am not able to probe MCLK as this line is directly connected to codec without any resisters in between.

# aplay -D hw:2,0 /home/Yamaha-V50-Rock-Beat-120bpm.wav

o/p:
Playing WAVE '/home/Yamaha-V50-Rock-Beat-120bpm.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: pcm_write:1940: write error: Input/output error

> i am using the below settings in my dts file, i am not sure whether i m using correct frequency for MCLK

snd3: sound@2 {
               compatible = "simple-audio-card";
               simple-audio-card,name = "DRA7xx-EVM-snd3";
               simple-audio-card,widgets =
                       "Microphone", "Mic Jack",
                       "Line",                  "Line In",
                       "Line",                  "Line Out",
                       "Headphone",             "HP Jack",
                       "Speaker",               "Speaker External";
               simple-audio-card,routing =
                       "Line Out",              "MONO_LOUT",
                       "Speaker External",      "LLOUT",
                       "Speaker External",      "RLOUT",
                       "LINE1L",                "Line In",
                       "LINE1R",                "Line In",
                       "MIC3L",                 "Mic Jack",
                       "MIC3R",                 "Mic Jack";
               simple-audio-card,format = "i2s";
 /*            simple-audio-card,bitclock-master = <&sound2_master>;
               simple-audio-card,frame-master = <&sound2_master>;
               simple-audio-card,bitclock-inversion;*/

               sound2_master: simple-audio-card,cpu {
                        sound-dai = <&mcasp4>;
                        system-clock-direction = "out";
                        system-clock-frequency = <20000000>;
               };

               simple-audio-card,codec {
                       sound-dai = <&tlv320aic34_b>;
                       bitclock-master;
                       frame-master;
                /*     bitclock-inversion;*/
                       system-clock-frequency = <20000000>;
                    /*  system-clock-frequency = <19200000>;*/
               };
        };

Regards,

Niraj

Part Number: TMS320DM8147

Is there a very fast bootloader available (in source code) that brings up a DM8147 as a PCIe slave and configures PCI Hardware IDs? The DM8147 is on a PCIe card designed to be plugged in to a host x86 PC. The TI published uboot based bootloader works, but is too slow to load and run relative to the BIOS PCIe enumeration of a modern PC.

Part Number: TDA3LX

Tool/software: TI-RTOS

Hi,

      My customer wants to increase the TDA3 DSP and EVE speed. I notice that the TDA3 can run in OPP_PLUS mode. For TDA2, I think the SBL code for OPP_PLUS has been already implemented in \PROCESSOR_SDK_VISION_03_06_00_00\ti_components\drivers\pdk_01_10_02_07\packages\ti\boot\sbl_auto\sbl_app\src,  but I cannot find any detail information about TDA3 OPP_PLUS.  I have several questions about the SW/HW OPP_PLUS configuration. Could you please provide more details about the OPP_PLUS of the TDA3.

      1. How to configure the Software for OPP_PLUS for TDA3 by using SBL? Is it same as the TDA2? 

      2. How to configure the Software for OPP_PLUS for TDA3 by using GEL?

      3. Any special requirements for the hardware or PCB ?

Thanks,

Frank  

Part Number: AM5748

TI’s Processor Software Development Kit (SDK) helps developers keep up with the latest available operating system releases to bring new features into their products. It also helps developers save time and resources by allowing them to scale from one processor family to another. For example, TI’s Processor SDK-Android eases software migration between Sitara™ processors AM57x and AM65x. The latest TI Processor SDK (6.0) now supports Android 9, also known as “Pie” with Linux Kernel 4.19.

Here are some key new features and benefits that Android Pie brings as part of the TI Processor SDK:

1. Modular software architecture with Project Treble. Software developers have historically spent significant effort migrating from one Android release to another. With Treble, Android version updatability is easier and faster, by creating a silicon vendor interface between the Android OS and the vendor implementation.

2. Improved Security. Nowadays security is of most importance for developers in virtually all applications, including consumer and industrial. Any improvement in this area is welcome. Android Pie introduced a number of security features such as Protected Confirmation which allows an application to request a user to confirm an operation (e.g. making a payment) and if the user accepts the operation cryptographic techniques are used to protect the operation. Other features include a unified biometric authentication dialog, support for hardware security module, secure key import into Keystore, an option to only allow key decryption on unlocked devices, deprecation of WPS (WiFi Protected Setup), and others.

3. A feature introduced in Android Oreo, which is now stabilized in the Processor SDK with Android Pie, is accelerated dual HD graphical display. Developers using Sitara processors benefit from this new feature by implementing more advanced and richer graphical user interfaces for HMI (Human Machine Interface) applications such as patient monitoring, industrial PCs, PLC panels, EV charging infrastructure, and others.

4. A key peripheral found in Sitara processors is the PRU-ICSS. It is a programmable core used by industrial automation applications for implementing industrial protocols. The latest Android Pie release now adds support for Ethernet enabled via the PRU-ICSS (10/100) on the AM57x processors and PRU-ICSSG (1Gb) on the AM65x processors.

Whether it is Android, Linux or TI-RTOS, the TI Processor SDK provides support for the latest operating system releases and allows customers to scale up and down between Sitara processors. The Processor SDK is fully supported by TI and freely downloadable from TI’s website.

Part Number: AM3358

Tool/software: Linux

Hello,

Hello,

Here are my specs:

TI SDK: 03.03.00.04

Ubuntu 18.04

So i set an IP on my beaglebone black so I can target build via SSH through QT. I can do this successfully by running the following:

ifconfig eth0 10.0.1.170 netmask 255.255.255.0

Unfortunately it defaults back to DHCP when powered down. I followed these steps to resolve it:

1. Stop the dhcp  from /lib/systemd/network/80-container-host0.network, i.e.:

     #  This file is part of systemd.                                                                                                                        

     #                                                                                                                                                        

     #  systemd is free software; you can redistribute it and/or modify it                                                                                    

     #  under the terms of the GNU Lesser General Public License as published by                                                                              

     #  the Free Software Foundation; either version 2.1 of the License, or                                                                                  

     #  (at your option) any later version.                                                                                                                  

     [Match]                                                                                                                                                  

     Virtualization=container                                                                                                                                

      Name=host0                                                                                                                                              

     [Network]                                                                                                                                                

     #DHCP=yes                               /*THE DEFAULT FILE has this set to YES,so comment this line*/                                                                                                                           

      LinkLocalAddressing=yes                                                                                                                                  

     #[DHCP]                                       /*THE DEFAULT FILE has this  setting, so COMMENT this line*/                                                                                                   #UseTimezone=yes                  /*THE DEFAULT FILE has this set to YES, so comment this line*/      

  2. Modify the /lib/systemd/system/systemd-networkd.service file:

[Service]                                                                                                                                                

Type=notify                                                                                                                                              

Restart=on-failure                                                                                                                                      

RestartSec=0                                                                                                                                                                                                                                                                    

#ExecStart=/lib/systemd/systemd-networkd                                          /*The default configuration has this enabled. COMMENT IT*/                 

ExecStart= ExecStart=/sbin/ifup eth1                                                   /*Add this line so that systemd runs ifup upon board boot*/                           

CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_RAW CAP_SETUID CAP_SETGID CAP_SETPCAP CAP_CHOWN CAP_DAC_OVERRIDE CAP_R

ProtectSystem=full                                                                                                                                      

ProtectHome=yes                                                                                                                                          

WatchdogSec=3min                           

After I made these changes I run this command and get the following results:

ifconfig eth0 10.0.1.170 netmask 255.255.255.0

[   77.372257] net eth0: initializing cpsw version 1.12 (0)
[   77.377867] net eth0: initialized cpsw ale version 1.4
[   77.391226] net eth0: ALE Table size 1024
[   77.408554] net eth0: phy found : id is : 0x7c0f1
[   77.432387] libphy: PHY 4a101000.mdio:01 not found
[   77.437232] net eth0: phy "4a101000.mdio:01" not found on slave 1, err -19
[   77.500821] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

Not sure what the error is about, but it does change the IP address appropriately:

eth0      Link encap:Ethernet  HWaddr 0C:AE:7D:29:D3:DA  
          inet addr:10.0.1.170  Bcast:10.0.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:174

It still resets again when powered down. I do not believe I missed anything, any thoughts?

Part Number: TCI6638K2K

Hi Eric:

          I am a colleague of Ziad. I am actively working in the Serdes test thread now. I followed your suggestion to run the serdes_diag tool on TCI6638K2K Dev kit.It goes well and I already see the result from BER sweep. Here I have some more short question on the BER on PCIe mode results:

        1. What is the meanning of pma and cdr in the the BER result(soc_device0_ber_scanout.txt) ? See my txt result below.

        2. There are 2 lines of source code at csl_serdes2.h accessing peripheral_base_addr (0x21800000)

CSL_FINSR(*(volatile uint32_t *)(serdes_lane_enable_params->peripheral_base_addr + 0x180C), 9, 8, serdes_lane_enable_params->num_lanes);

 CSL_FINSR(*(volatile uint32_t *)(serdes_lane_enable_params->peripheral_base_addr + 0x180C),17,17, 0x1);

Are these required? Can you explain what they did? I removed that at my project it seems like no harm.The reason I remove them is that I can't access this address(bus read error) on  Devkit (TCIEVMK2X).

Part Number: 66AK2H06

Tool/software: Linux

We have a custom board, but what I am about to say applies to K2HK EVM as well. Currently we are using default settings from K2HK EVM BSP. However we would like to change the default location of the DSP0-3 code region to DDR3B region - 0x60000000. In essense we want to host and run DSP code from DD3B. I suspect for this we will need to modify following:

1. /etc/mpm/mpm_config.json

2. Device tree file for Linux.

3. Linker file for DSP.

Can you help identify what exact settings need to be modified in the json file and device tree? Do we need to do anything else in kernel .config file?

Our baseline is SDK version is 2.00.02.11. Json and device tree files the same as K2HK evm.

This question is related to:

https://e2e.ti.com/support/processors/f/791/t/425181?mpmcl-load-error-

However in that post they never get complete answer.

After I've made edits to the NDK code, how do I rebuild its libraries to view my changes in action?

Part Number: AM3359

Tool/software: Linux

Customer uses LINUX kernel 4.19 mainline with the GPU drivers on Github which are closed source.

Are there open source drivers available too?

Regards, Bernd

Part Number: TMDSDSK6416

TMDSDSK6416 input is 5V. But 3.3 V output is not coming. Moreover U7 and CT4 is producing heat. The output at CT4 is coming 0.1 V instead of 3.3 V.

Kindly suggest how to resolve this issue related to hardware.

Part Number: TDA2EVM5777

Tool/software: Linux

Hi,

I want to use a 6-channel camera to collect data and store the data in a file. The usecase used is UC_lvds_vip_multi_cam_vpe_enc_null, gChains_usecaseCfg.numLvdsCh = 6; NDK_PROC_TO_USE=none, the problem occurs at runtime:

[HOST] [IPU2  ]     81.937046 s:  CHAINS: ChainsCommon_MultiCam_StartCaptureDevice
 [HOST] [IPU2  ]     81.937625 s:  VIDEO_SENSOR: INST1 : I2C1 : I2C Addr = 0x38
 [HOST] [IPU2  ]     82.287622 s:  VIDEO_SENSOR: VIP 0: DRV ID 1205 (I2C ADDR 0x38): a635:0000:7fa2
 [HOST] [IPU2  ]     82.288171 s:  VIDEO_SENSOR: INST2 : I2C1 : I2C Addr = 0x39
 [HOST] [IPU2  ]     82.638107 s:  VIDEO_SENSOR: VIP 2: DRV ID 1205 (I2C ADDR 0x39): a635:0000:7fa2
 [HOST] [IPU2  ]     82.638809 s:  VIDEO_SENSOR: INST3 : I2C1 : I2C Addr = 0x3a
 [HOST] [IPU2  ]     82.988928 s:  VIDEO_SENSOR: VIP 4: DRV ID 1205 (I2C ADDR 0x3a): a635:0000:7fa2
 [HOST] [IPU2  ]     82.989507 s:  VIDEO_SENSOR: INST4 : I2C1 : I2C Addr = 0x3b
 [HOST] [IPU2  ]     83.339840 s:  VIDEO_SENSOR: VIP 8: DRV ID 1205 (I2C ADDR 0x3b): a635:0000:7fa2
 [HOST] [IPU2  ]     83.340389 s:  VIDEO_SENSOR: INST6 : I2C1 : I2C Addr = 0x3d
 [HOST] [IPU2  ]     83.675379 s:  VIDEO_SENSOR: VIP 10: DRV ID 1205 (I2C ADDR 0x3d): a635:0000:7fa2
 [HOST] [IPU2  ]     83.675959 s:  VIDEO_SENSOR: INST5 : I2C1 : I2C Addr = 0x3c
[   77.147569] davinci_mdio 48485000.mdio: timed out waiting for user access
[   77.247564] davinci_mdio 48485000.mdio: timed out waiting for user access
[   77.447564] davinci_mdio 48485000.mdio: timed out waiting for idle
 [HOST] [IPU2  ]     84.419599 s: src/bsp_deviceI2c.c @ Line 386: 
 [HOST] [IPU2  ]     84.419691 s:  I2C1: DEV 0x78: RD 0x01 ... ERROR !!!
 [HOST] [IPU2  ]     84.419782 s: src/bsp_deviceI2c.c @ Line 412: 
 [HOST] [IPU2  ]     84.419874 s:  I2C1: Error timeout 648 ms!!!
 [HOST] [IPU2  ]     84.419965 s: src/bsputils_lvds.c @ Line 919: 
 [HOST] [IPU2  ]     84.420026 s:  device address - 78 i2c error - -21
 [HOST] [IPU2  ]     84.678734 s:  VIDEO_SENSOR: VIP 7: DRV ID 1205 (I2C ADDR 0x3c): a635:0000:7fa2
 [HOST] [IPU2  ]     84.687244 s:  CAPTURE: Create in progress !!!
 [HOST] [IPU2  ]     84.687671 s:  CAPTURE: VIP1 Slice0 PortA capture mode is [ 8-bit] !!! 
 [HOST] [IPU2  ]     84.808363 s:  CAPTURE: VIP1 Slice1 PortA capture mode is [ 8-bit] !!! 
 [HOST] [IPU2  ]     84.929238 s:  CAPTURE: VIP2 Slice0 PortA capture mode is [ 8-bit] !!! 
 [HOST] [IPU2  ]     85.050082 s:  CAPTURE: VIP3 Slice0 PortA capture mode is [ 8-bit] !!! 
 [HOST] [IPU2  ]     85.170896 s:  CAPTURE: VIP3 Slice1 PortA capture mode is [ 8-bit] !!! 
 [HOST] [IPU2  ]     85.291770 s:  CAPTURE: VIP2 Slice1 PortB capture mode is [ 8-bit] !!! 
 [HOST] [IPU2  ]     85.412737 s:  CAPTURE: Create Done !!!

    What else do I need to set?