Quantcast
Channel: Processors forum - Recent Threads
Viewing all 17527 articles
Browse latest View live

AM3358: Temperature issue

$
0
0

Part Number: AM3358

Hi,

I made a 6 layer custom board using the AM3358BZCZ100 with DDR3. My board is booting linux without problam and every thing is working perfectly fine and stable except the temperature of the CPU is too high (compared with BBB).

If I startup my board with 600MHz the temperature reaches around 60 degree Celsius. When I startup my board with 1GHz the temperature reaches around 75 degree Celsius. When I run in 1GHz CPU mode and I am in Linux, I can feel a temperature difference between the situation the CPU load runs 100% or only 5%.

I have thermal pictures attached that shows where the heat is building up on the CPU:
(Please visit the site to view this file)

I checked with the "AM335x_to_TPS65217_hookup_reference" if I have a too high voltage on one of the Pins, but that seems to be OK.
I use one layer for GND only and one for power. In the screenshot below I show the VDD_MPU and VDD_CORE:


CCSTUDIO: Operating temperature of TMDSEMU560V2STM-UE

$
0
0

Part Number: CCSTUDIO

Hello, 

My customer would like to know about the operating condition of TMDSEMU560V2STM-UE, especially for the temp condition. Do you have any information? I searched e2e, but i couldn't find the answer for that.

Best Regards,
NK

TI video encoder that would be compatible with an ARM M4

$
0
0

I am looking to compress a video signal into a mpeg-4 format from the digital buss of an ARM M4 microcontroller (i.e. STM32F4 Discovery Kit and Peripherals). This port is  also connected to a 3.5 inch touch screen display. The image array is capable of operating at 15 fps in SXGA resolution and has an active array size of 1280 x 1024. The sensor is a OV9655 CMOS sxga sensor @ 1.3 MegaPixels. As I have not done this before would I be incorrect in thinking that there might be a TI video encoder chip that would be compatible with the ARM M4? Failing that are there TI  development kits that would allow me to create one? Any such insight into this would be duly appreciated. Further Note: it does not necessarily have to be a mpeg-4 format, but given a choice in the matter that would be my preference. Thanks in advance for anyone that might be able of help?

Compiler/AM5728: install pip3 for python3

$
0
0

Part Number: AM5728

Tool/software: TI C/C++ Compiler

software :processor-linux-sdk5.3

hardware: am5728/am5708 customboard

Hi,

How to install pip3 on processor-linux-sdk5.3 filesystem, I tried :

curl bootstrap.pypa.io/get-pip.py -o get-pip.py
python3 get-pip.py

but it comes with error:

Traceback (most recent call last):
File "get-pip.py", line 22312, in <module>
main()
File "get-pip.py", line 197, in main
bootstrap(tmpdir=tmpdir)
File "get-pip.py", line 82, in bootstrap
import pip._internal
File "/tmp/tmpoqe52cc2/pip.zip/pip/_internal/__init__.py", line 40, in <module>
File "/tmp/tmpoqe52cc2/pip.zip/pip/_internal/cli/autocompletion.py", line 8, in <module>
File "/tmp/tmpoqe52cc2/pip.zip/pip/_internal/cli/main_parser.py", line 7, in <module>
File "/tmp/tmpoqe52cc2/pip.zip/pip/_internal/cli/cmdoptions.py", line 24, in <module>
File "/tmp/tmpoqe52cc2/pip.zip/pip/_internal/models/search_scope.py", line 11, in <module>
File "/tmp/tmpoqe52cc2/pip.zip/pip/_internal/utils/misc.py", line 5, in <module>
ImportError: No module named 'getpass'

Is there any way to install pip3 ?

Thank you,

Andi

TDA2EXEVM: TDA2: Error of create an new use case

AM4372: Camera integration using DVP port: 8 or 10 bit / Replacing OV2659 with more recent CMOS, like AV2715-1E

$
0
0

Part Number: AM4372

The OV2659 CMOS modules supports 8 but as well as 10 bit operation. On the EVM and in the reference design files it is always connected using 8 bit.

My questions:

  1. Which is the actual advantage of using 10 bit for that module? What is going to change?
  2. Does the provided driver support 10 bit operation out of the box?
  3. In order to use 10 but on OV2659, it is sufficient to map CAM_DATA0 to D0 instead of D2, CAM_DATA1 to D1 instead of D3, and so on?

Second part:
OV2659 it quite old and not really useful for new designs. Without completely abandoning the DVP interface, OV2715-1E seems to be a good alternative to me as it supports 1080P but still offers 8/10 bit operation. On the connector side, it appears to be PIN compatible except that you need to increase AVDD from 2.8V in the TI reference design to 3.3V.

Does anyone have already tried that? Any experience or hints on the driver side?

Did anyone successfully connect other CMOS modules?

CCS/PHYTC-3P-PHYCORE-AM65X: PHYTC-3P-PHYCORE-AM65X

$
0
0

Part Number: PHYTC-3P-PHYCORE-AM65X

Tool/software: Code Composer Studio

I am trying to run the set up script and for the phyCORE-AM65x Development Kit and it cannot detect the board. How can I fix this? See the output from running the scriot below
Thanks


dallas@dallas-OMEN-by-HP-Obelisk-Desktop-875-0xxx:~$ dir Desktop gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz.1 snap tisdk Documents gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz Music Templates Videos Downloads gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf Pictures ti-processor-sdk-linux-am65xx-evm-06.00.00.07 workspace_v9 examples.desktop gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz Public ti-processor-sdk-linux-am65xx-evm-06.00.00.07old dallas@dallas-OMEN-by-HP-Obelisk-Desktop-875-0xxx:~$ cd ti-processor-sdk-linux-am65xx-evm-06.00.00.07 dallas@dallas-OMEN-by-HP-Obelisk-Desktop-875-0xxx:~/ti-processor-sdk-linux-am65xx-evm-06.00.00.07$ dir bin board-support docs example-applications filesystem linux-devkit linux-devkit.sh Makefile Rules.make setup.sh targetNFS dallas@dallas-OMEN-by-HP-Obelisk-Desktop-875-0xxx:~/ti-processor-sdk-linux-am65xx-evm-06.00.00.07$ ./setup.sh ------------------------------------------------------------------------------- TISDK setup script This script will set up your development host for SDK development. Parts of this script require administrator priviliges (sudo access). ------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Verifying Linux host distribution Ubuntu 12.04 LTS, Ubuntu 14.04, or Ubuntu 14.04 LTS is being used, continuing.. -------------------------------------------------------------------------------- Starting with Ubuntu 12.04 serial devices are only accessible by members of the 'dialout' group. A user must be apart of this group to have the proper permissions to access a serial device. User 'dallas' is already apart of the 'dialout' group ------------------------------------------------------------------------------- setup package script This script will make sure you have the proper host support packages installed This script requires administrator priviliges (sudo access) if packages are to be installed. ------------------------------------------------------------------------------- System has required packages! -------------------------------------------------------------------------------- Package verification and installation successfully completed -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- In which directory do you want to install the target filesystem?(if this directory does not exist it will be created) [ /home/dallas/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS ] -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- This step will extract the target filesystem to /home/dallas/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS Note! This command requires you to have administrator priviliges (sudo access) on your host. Press return to continue /home/dallas/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS already exists (r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction [r] o [sudo] password for dallas: Old /home/dallas/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS removed Multiple filesystems found. 1:tisdk-rootfs-image-am65xx-evm.tar.xz 2:tisdk-docker-rootfs-image-am65xx-evm.tar.xz Enter Number of rootfs Tarball: [1] Successfully extracted tisdk-rootfs-image-am65xx-evm.tar.xz to /home/dallas/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- This step will set up the SDK to install binaries in to: /home/dallas/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS/home/root/am65xx-evm The files will be available from /home/root/am65xx-evm on the target. This setting can be changed later by editing Rules.make and changing the EXEC_DIR or DESTDIR variable (depending on your SDK). Press return to continue Rules.make edited successfully.. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- This step will export your target filesystem for NFS access. Note! This command requires you to have administrator priviliges (sudo access) on your host. Press return to continue /home/dallas/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS already NFS exported, skipping.. [ ok ] Stopping nfs-kernel-server (via systemctl): nfs-kernel-server.service. [ ok ] Starting nfs-kernel-server (via systemctl): nfs-kernel-server.service. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Which directory do you want to be your tftp root directory?(if this directory does not exist it will be created for you) [ /tftpboot ] -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- This step will set up the tftp server in the /tftpboot directory. Note! This command requires you to have administrator priviliges (sudo access) on your host. Press return to continue /tftpboot already exists, not creating.. /tftpboot/*Image-am65xx-evm.bin already exists. The existing installed file can be renamed and saved under the new name. (r) rename (o) overwrite (s) skip copy [r] o Successfully overwritten *Image-am65xx-evm.bin in tftp root directory /tftpboot /tftpboot/k3-am654-base-board-am65xx-evm.dtb already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-base-board-am65xx-evm.dtb in tftp root directory /tftpboot /tftpboot/k3-am654-base-board.dtb already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-base-board.dtb in tftp root directory /tftpboot /tftpboot/k3-am654-evm-csi2-ov490-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-csi2-ov490-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-csi2-ov490.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-csi2-ov490.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-csi2-ov5640-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-csi2-ov5640-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-csi2-ov5640.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-csi2-ov5640.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-hdmi-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-hdmi-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-hdmi.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-hdmi.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-oldi-lcd1evm-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-oldi-lcd1evm-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-oldi-lcd1evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-oldi-lcd1evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-tc358876-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-tc358876-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-evm-tc358876.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-evm-tc358876.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-gp-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-gp-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-gp.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-gp.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-idk-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-idk-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-idk.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-idk.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-idk-interposer-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-idk-interposer-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-idk-interposer.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-idk-interposer.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-pcie-usb2-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-pcie-usb2-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-pcie-usb2.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-pcie-usb2.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-pcie-usb3-am65xx-evm.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-pcie-usb3-am65xx-evm.dtbo in tftp root directory /tftpboot /tftpboot/k3-am654-pcie-usb3.dtbo already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten k3-am654-pcie-usb3.dtbo in tftp root directory /tftpboot /tftpboot/ti-sci-firmware-am65x-gp.bin already exists. The existing installed file can be renamed and saved under the new name. (o) overwrite (s) skip copy [o] o Successfully overwritten ti-sci-firmware-am65x-gp.bin in tftp root directory /tftpboot /etc/xinetd.d/tftp already exists.. /tftpboot already exported for TFTP, skipping.. Restarting tftp server [ ok ] Stopping xinetd (via systemctl): xinetd.service. [ ok ] Starting xinetd (via systemctl): xinetd.service. -------------------------------------------------------------------------------- --------------------------------------------------------------------------------" This step will set up minicom (serial communication application) for SDK development For boards that contain a USB-to-Serial converter on the board such as: * BeagleBone * Beaglebone Black * AM335x EVM-SK * AM57xx EVM * K2H, K2L, and K2E EVMs the port used for minicom will be automatically detected. By default Ubuntu will not recognize this device. Setup will add a udev rule to /etc/udev/ so that from now on it will be recognized as soon as the board is plugged in. For other boards, the serial will defualt to /dev/ttyS0. Please update based on your setup. -------------------------------------------------------------------------------- NOTE: If your using any of the above boards simply hit enter and the correct port will be determined automatically at a later step. For all other boards select the serial port that the board is connected to. Which serial port do you want to use with minicom? [ /dev/ttyS0 ] /deev/ttyS1 Copied existing /home/dallas/.minirc.dfl to /home/dallas/.minirc.dfl.old Configuration saved to /home/dallas/.minirc.dfl. You can change it further from inside minicom, see the Software Development Guide for more information. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- This step will set up the u-boot variables for booting the EVM. -------------------------------------------------------------------------------- ./bin/setup-uboot-env.sh: line 54: ifconfig: command not found Autodetected the following ip address of your host, correct it if necessary [ ] 192.168.0.22 Select Linux kernel location: 1: TFTP 2: SD card [ 1 ] 1 Select root file system location: 1: NFS 2: SD card [ 1 ] 1 Available kernel images in /tftproot: Image-am65xx-evm.bin k3-am654-base-board-am65xx-evm.dtb k3-am654-base-board.dtb k3-am654-evm-csi2-ov490-am65xx-evm.dtbo k3-am654-evm-csi2-ov490.dtbo k3-am654-evm-csi2-ov5640-am65xx-evm.dtbo k3-am654-evm-csi2-ov5640.dtbo k3-am654-evm-hdmi-am65xx-evm.dtbo k3-am654-evm-hdmi.dtbo k3-am654-evm-oldi-lcd1evm-am65xx-evm.dtbo k3-am654-evm-oldi-lcd1evm.dtbo k3-am654-evm-tc358876-am65xx-evm.dtbo k3-am654-evm-tc358876.dtbo k3-am654-gp-am65xx-evm.dtbo k3-am654-gp.dtbo k3-am654-idk-am65xx-evm.dtbo k3-am654-idk.dtbo k3-am654-idk-interposer-am65xx-evm.dtbo k3-am654-idk-interposer.dtbo k3-am654-pcie-usb2-am65xx-evm.dtbo k3-am654-pcie-usb2.dtbo k3-am654-pcie-usb3-am65xx-evm.dtbo k3-am654-pcie-usb3.dtbo ti-sci-firmware-am65x-gp.bin Which kernel image do you want to boot from TFTP? [ Image-am65xx-evm.bin ] -------------------------------------------------------------------------------- Would you like to create a minicom script with the above parameters (y/n)? [ y ] y Successfully wrote /home/dallas/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/bin/setupBoard.minicom Board could not be detected. Please connect the board to the PC. Press any key to try checking again.

PROCESSOR-SDK-AM335X: where are kernel/u-boot source codes for modify&customizing my own linux system ?

$
0
0

Part Number: PROCESSOR-SDK-AM335X

Studying the TI-SDK, I found yoctoproject  is a powerful tool.
but still i don't know detail feature about it.
my build procedure is ...
1. install TI-SDK (download from TI hompage)
2. install ARM toolchain
3. clone git repository ( git clone git://arago-project.org/git/projects/oe-layersetup.git tisdk )
4. and then follow TI-SDK quick start guide ..

cd tisdk

./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-06.00.00.07-config.txt
cd build

. conf/setenv
export TOOLCHAIN_PATH_ARMV7=$HOME/gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf
export TOOLCHAIN_PATH_ARMV8=$HOME/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu
MACHINE=am335x-evm bitbake arago-base-tisdk-image

and i successfully build beaglebone black image and run.
So, my question is
1. where is downloaded (or copied from TI-SDK) u-boot/kernel source code for customizing my own linux image ?
    i want import new device driver, add read new device tree mechanism, apply patch for realtime linux and so on.
    there is too much directories and TI-SDK quick start guide don't tell me where it is. i can't found it.
2. i download and install TI-SDK from TI website. but what is the my build procedure "step 3 : clone git repository ( git clone git://arago-project.org/git/projects/oe-layersetup.git tisdk ) " ?
    this is also included TI-SDK ? ( i think this is yocto project repo. may be.)
3. my first build spends a lot of time (about 8 or more hours) .
    If I rebuild later, it will end soon ?

TDA2P-ACD: How to image distortion correction

$
0
0

Part Number: TDA2P-ACD

Hi 

I want to correct the image distortion of fisheye lens.

I saw the comment in TI E2E about TI ISP tuning tool but Our TI respresentative(FAE) do not known it

Could you help me ?

AM5726: AM5726

$
0
0

Part Number: AM5726

Hi,

I've been trying to install a SSH server following this article, but it failed.

Here is the shell command and the debug message I got:

shaoyu@ubuntu_shaoyu_vm:~/.ssh$ ssh -v -i ~/.ssh/id_rsa root@192.168.1.100
OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.1.100 [192.168.1.100] port 22.
debug1: Connection established.
debug1: identity file /home/shaoyu/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /home/shaoyu/.ssh/id_rsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
debug1: Remote protocol version 2.0, remote software version dropbear_2019.78
debug1: no match: dropbear_2019.78
debug1: Authenticating to 192.168.1.100:22 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:wLBo59J2ox82+rUUZLuIK/i2Qz+VceVgwnEKxpZZkXE
debug1: Host '192.168.1.100' is known and matches the RSA host key.
debug1: Found key in /home/shaoyu/.ssh/known_hosts:1
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: RSA SHA256:5ExEuf2vcmr+ejKnaosM0XFI6a05MV3abddPUYxrbzY /home/shaoyu/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
root@192.168.1.100: Permission denied (publickey).

Could someone give me some advices, THANKS!

AM3359: AM3359BZCZA80 and XAM3359ZCZ

$
0
0

Part Number: AM3359

Hi All,

we are using this AM3359BZCZA80 in our designs. though recently I noticed that in Digikey, Mouser and Quest Components that 296-35073-ND was 0 qty and discontinued.

I would like to know the road map / plan for this processor and how many years will it be active or supported? TI website shows it is still active, though distributors are saying low qty and being discontinued.

also, can you clarify where did XAM3359ZCZ chip were from? seems to be in the market, though TI website part making only states AM3359BZCZA80

Cheers,

Mike I.

AM3354: linux/am3354 tilcdc_crtc_irq : sync lost

$
0
0

Part Number: AM3354

we are using process-sdk-linux-am335x-06.00.00.07,how to solve the above problem

TDA2E: Questions about running TIDL on EVE

$
0
0

Part Number: TDA2E

Hi,

I want to divide the image captured by the camera into two parts. Can I realize that the left half image runs on EVE1, the right half image runs on EVE2, and EVE1 and EVE2 run the same network? What is the way to ensure that EVE1 runs on the left half of the image, while EVE2 runs on the right half of the image? And the left and right are stitched together in the same image.

Thanks!

AMIC110: AMIC110 connecting with C2000

$
0
0

Part Number: AMIC110

Hi,
I was connecting 28377D and AMIC110 with SPI.
Part of spi setting on DSP was
    SPI_setConfig(SPIA_BASE, DEVICE_LSPCLK_FREQ, SPI_PROT_POL0PHA0,
                  SPI_MODE_SLAVE, 500000, 16);
from c2000 ware.
The spi setting on amic 110 was MCSPI_CH1CONF_CLKD_DIVBY128, MCSPI_CH0CONF_POL_ACTIVEHIGH and MCSPI_CH0CONF_PHA_EVEN.
FIFO and MOA was also enabled. Both SPIs were in full-duplex mode.
There is an uint16 array storing data from spi rx buffer in DSP.
There is an uint32 array storing data from spi rx buffer in AMIC110.
AMIC110 was continually sending 0x1234 while reading the spi rx buffer in while(1) loop. There are no other tasks for this test.
DSP was reading amic110 data while sending 0x55AA for test in interrupt.
Data received in DSP uint16 array was 0x1234 as sent by amic110.
However, what the AMIC110 read from its spi rx buffer was 0x5678 instead of 0x55AA.
How 0x55AA was converted to 0x5678?
Kind regards
Orient

AM5746: USB2.0 connection is not stable

$
0
0

Part Number: AM5746

Hi,

My customers are investigating whether the problem they are experiencing is related to errata i819.

"i819 A Device Control Bit Meta-Stability for USB3.0 Controller in USB2.0 Mode"

Their problem is that the USB 2.0 connection is not stable.
When the USB cable is connected / disconnected, it becomes unconnected.

Question 1:
Could you tell me more about the phenomenon caused by this errata?

Question 2:
This eratta is considered critical when using USB2.0 mode.
Are there any plans to correct it by changing the revision of AM5746?

■Environment
AM5746
Customer's board
pdk_am57xx_1_0_11
bios_6_76_00_08


AM5718: g_mass_storage

$
0
0

Part Number: AM5718

Hi,

I am using AM5718 IDK EVM,and ti-processor-sdk-linux-am57xx-evm-05.03.00.07.

I could successfully attach USB2 to a host PC with the command'modbprobe g_mass_storage file=/dev/mmcblk0p3' where
/dev/mmcblk0p3 is a partition of flash.

When we develop our custom board, we wish to do the same but due to security reasons, we would like to not display
/dev/mmcblk0p3 on any host PC. We need to access it using our custom application.

Can you suggest a method so that USB2 is accessible (as Mass Storage Device) only via a program and not displayed on host PC?

regards,

Anupama

66AK2H06: Package details information

$
0
0

Part Number: 66AK2H06

Hi

My customer wants to know 66AK2H06 AAW package information.
There is solder mask details in Figure 13-2 in datasheet.
http://www.ti.com/lit/ds/symlink/66ak2h06.pdf


Customer wants to know similar information on package side (not PCB side).
Metal size and solder mask opening.
Such information is available for customers?

Thanks and regards,
Koichiro Tashiro

AM5728: PCIe receive interrupt issue

$
0
0

Part Number: AM5728

Hello,

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

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

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

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

On the software front,

- Linux 4.9.41 used is for booting is from Phytec GIT-repo

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

- PCIe RC is driven using external clock and PCIE RefClock register is programmed appropriately to select external clock

- DSP enumerates FPGA as a PCIe endpoint during firmware initialization

Application description,

- FPGA keeps providing interrupts once every ~2ms

- Upon receiving the interrupt, DSP starts EDMA transfer to fetch data from FPGA Fifo to DSP buffer (which is aligned to 256 bytes)

- DSP is required to process the received buffer and transmit back to a separate FPGA Transmit Fifo, again using EDMA, over PCIe bus

- It is possible for Transmit EDMA transfer to be active along with FPGA raising Rx interrupt at the same time

Issues being faced,

1. When both Transmit and Receive paths are enabled together, then, DSP PCIe driver is missing some Rx interrupts being raised by FPGA

2. Our FPGA engineer says that all raised interrupts are being acknowledged by a bus grant on PCIe bus. We have implemented an exception in case interrupt is raised by FPGA and bus grant is not received from PCIe root-complex, and this is never triggered during data transfers when check on FPGA ILA

3. When interrupts are missed, we are observing the ISR does not get invoked, even though the bus grant has been received by FPGA

4. From the DSP side, we keep profiling the duration between consecutive interrupts and flag off when duration is greater than 3ms

5. When Transmit path is disabled in our code, no Receive interrupts are missed in this condition

Any inputs on solving the missing interrupts issue will be appreciated. PLease let me know if any more information is needed.

thanks--

Somesh

TMDXIDK437X: PRU demo

$
0
0

Part Number: TMDXIDK437X

Hi,

Software:processor_sdk_rtos_am437x_5_02_00_10      PRU-ICSS-EtherCAT_Slave_01.00.07.02    PRU-ICSS-Industrial_Drives_01.00.02.03

The sampling of the adc signal needs to be done using the pru core to load the pru_adc_sampling_bin.h firmware, is this firmware only for motors with idk or is it universally? If use a third-party encoder, such as Nikon, does ti have a similar pru demo for reference?

CCS/TMDSLCDK6748: I need an example code for I2S .

$
0
0

Part Number: TMDSLCDK6748

Tool/software: Code Composer Studio

Hello

I need  an easy example code for I2S(TMS320C6748).

Do you Provide an example code?

Thanks.

Viewing all 17527 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>