Hello,
Can someone please give me step by step guide on how to use DVSDK and Codec Engine for custom board? I successfully learned how to design multimedia systems using DVSDK for OMAPL138-EVM, but now I want to switch to a custom board.
There are tutorials for Processor SDK but I don't know if they are suitable for DVSDK too or not.
Thanks in advance
Part Number:DM3730
Hi Team,
I received the following request from a customer that is using the DM3730
They are working on power optimization for it and would like to understand if is possible to dynamically manage the clock.
Maximum clock is 800MHz but they would change it dynamically at 300MHz or even lower when required.
SGX Off, Graphics Accelerator is not used
Please, let me know if is possible and how to achieve it!
Regards,
Fabio
Part Number:SMJ320C40
Hello,
I was told to reach out to an Applications Engineer in this forum for this question. I was wondering if there was a difference in thermal properties between the SMJ320C40 and SM320C40 ('SMJ' versus 'SM')? Specifically, any difference between SMJ320C40GFS60 and SM320C40GFS60?
The differences I found were that the 'SMJ' designates the MIL-PRF-38535 standard, and the 'SM' designates the standard processing. They seem to have the same operating temperature range (-55 C to 100 C), and the same packge type, but have different Processing Levels (QML for 'SMJ', Standard for 'SM'). I was wondering if there were any changes in their thermal properties too? Are there any other noteable differences between the two difference devices ('SMJ' versus 'SM')?
Any help is much appreciated! Thanks again!
Hello,
I have a PCB that uses the CC2540 BLE chip from TI, using just this board has the current draw hovering around 20 microAmperes,
but when plugging in the CC Debugger from TI, this spikes the current draw up by almost 25milliAmperes.
Needed to know if this is an expected behavior or if this is a problem on our end.
For side details, only pins 1,2,3,4 and 7 are interfacing with the board.
pins 8, 9, and 10 have pull ups externally
pin 7 is pulled up externally.
Part Number:AM5728
Hello @lding, @Biser Gatchev-XID,
Following up on the previous request for USB driver support on TI-DSP.
[Ref. https://e2e.ti.com/support/processors/f/791/t/719360?AM5728-USB-access-from-DSP]
We are using AM5728 and looking forward to access USB device on DSP side. Would you please update if TI has the USB driver support for DSP SYS/BIOS?
Appreciate your quick response.
Regards
Rajesh
Part Number:TMS320C6748
Tool/software: Code Composer Studio
I'm getting the linker errors at the end of the build log at <https://pastebin.com/99yasisu>
Part Number:AM3356
Tool/software: Linux
We're selecting external NAND and DDR3/L for an AM3356 project and we want to check if any of the below devices have been confirmed to work with the AM335x and any version of Linux.
I have a pretty high confidence on the DDR3 devices based on the datasheets, except for the Micron MT41K512M16 which is a "twin die" device. This E2E post suggests that "dual die" DDR3 are not compatible with AM335x but recommends the MT41K512M16 which is a dual die device.
Thanks in advance,
Ruben
Part Number:OMAP-L138
Tool/software: Linux
Currently I am trying to enable IPC communication between the ARM and DSP cores on our custom board following this guide and the following sources:
IPC 3.40.01.08
SYS/BIOS 6.73.01.01
xdctools 3.32.01.22
Additionally, the kernel being run is Linux 4.9.
A thorough check of the device trees shows that the core is enabled and has a properly reserved memory node. Additionally, our kernel configuration has all the proper modules enabled. However, when attempting to activate the modules, the following error occurs (This error also occurs on startup.):
root@custom:~# rmmod da8xx_remoteproc [ 680.410317] remoteproc remoteproc0: releasing dsp root@custom:~# modprobe da8xx_remoteproc da8xx_fw_name=messageq_single.xe674 [ 685.215987] davinci-rproc davinci-rproc.0: assigned reserved memory node dsp_cma@c3000000 [ 685.243597] remoteproc remoteproc0: dsp is available [ 685.249146] remoteproc remoteproc0: Direct firmware load for messageq_single.xe674 failed with error -2 root@custom:~# [ 685.281354] remoteproc remoteproc0: powering up dsp [ 685.298329] remoteproc remoteproc0: Direct firmware load for messageq_single.xe674 failed with error -2 [ 685.317958] remoteproc remoteproc0: request_firmware failed: -2
Additionally, MessageQApp can properly set up the LAD daemon and begin searching for the DSP.
root@custom:~# /usr/bin/MessageQApp Using numLoops: 100; procId : 1 Entered MessageQApp_execute Local MessageQId: 0x80 ^CIpc: Caught SIGINT, calling Ipc_stop... root@custom:~# cat /tmp/LAD/log.txt [0.154486] Initializing LAD... [0.156447] opening FIFO: /tmp/LAD/LADCMDS [11.779057] Retrieving command... [11.781899] LAD_CONNECT: [11.782063] client FIFO name = /tmp/LAD/207 [11.782172] client PID = 207 [11.782325] assigned client handle = 0 [11.782688] FIFO /tmp/LAD/207 created [11.783963] FIFO /tmp/LAD/207 opened for writing [11.784474] sent response [11.784607] DONE [11.784704] Retrieving command... [11.785922] Sending response... [11.786137] Retrieving command... [11.786793] LAD_MULTIPROC_GETCONFIG: calling MultiProc_getConfig()... [11.786967] MultiProc_getConfig() - 2 procs [11.787072] # processors in cluster: 2 [11.787168] cluster baseId: 0 [11.787258] ProcId 0 - "HOST" [11.787354] ProcId 1 - "DSP" [11.787451] status = 0 [11.787536] DONE [11.787827] Sending response... [11.788020] Retrieving command... [11.788727] LAD_NAMESERVER_SETUP: calling NameServer_setup()... [11.788947] NameServer_setup: entered, refCount=0 [11.789196] NameServer_setup: creating listener thread [11.790665] NameServer_setup: exiting, refCount=1 [11.791134] status = 0 [11.791269] DONE [11.791368] Sending response... [11.791957] Retrieving command... [11.792217] LAD_MESSAGEQ_GETCONFIG: calling MessageQ_getConfig()... [11.792351] status = 0 [11.792456] DONE [11.792549] Sending response... [11.793125] Retrieving command... [11.793380] LAD_MESSAGEQ_SETUP: calling MessageQ_setup()... [11.793516] MessageQ_setup: entered, refCount=0 [11.793631] NameServer_create(): 'MessageQ' [11.793936] MessageQ_setup: exiting, refCount=1 [11.794077] status = 0 [11.794179] DONE [11.794269] Sending response... [11.796188] listener_cb: Entered Listener thread. [11.796397] NameServer: waiting for unblockFd: 2, and socks: maxfd: 2 [11.796693] Retrieving command... [11.796911] NameServer_attach: --> procId=1, refCount=0 [11.797181] NameServer_attach: created send socket: 5, procId 1 [11.797520] NameServer_attach: connect failed: procId=1, errno=22 (Invalid argu) [11.797996] closing send socket: 5 [11.798216] NameServer_attach: <-- refCount=0, status=-1 [11.798348] Sending response... [11.799902] Retrieving command... [11.800591] LAD_MESSAGEQ_CREATE: calling MessageQ_create(0x1b7c8, 0x1b7e8)... [11.800754] MessageQ_create: creating 'HOST' [11.800930] NameServer_add: Entered key: 'HOST', data: 0x80 [11.801062] MessageQ_create: returning obj=0x1c5d0, qid=0x80 [11.801171] status = 0 [11.801268] DONE [11.801356] Sending response... [11.802378] Retrieving command... [11.802627] LAD_NAMESERVER_GETUINT32: calling NameServer_getUInt32(0x1c4e8, 'SL. [11.802792] NameServer_getLocal: entry key: 'SLAVE_DSP' not found! [11.802920] NameServer_getRemote: no socket connection to processor 1 [11.803038] value = 0x80 [11.803142] status = -5 [11.803298] DONE
Checking under /lib/firmware in the kernel shows that it does have the source code (messageq_single.c) present. However, this source code is never built into the .xe674 file that is being looked for. I want to make sure that the firmware code is actually being built during the build process linked above, or if necessary, manually build this firmware code myself on the board.
Part Number:TMS320C6678
Tool/software: TI-RTOS
i'm trying to boot using ethernet from RBL directly instead of using IBL. Would the procedure in the related post work for ethernet boot?
Part Number:DRA726
Tool/software: Linux
Is there any example on using eCAP3 to read a frequency.
I need to read between 10 hz and 10khz
Michel Catudal
ACTIA Corp
Part Number:AM4378
Hello
I am using AM4378 to create a UART receiver circuit.
data: 8bit
bps: 230400
parity: none
stopbit: 1 bit
In rare cases, sending a 1000-character packet may result in the loss of one or more characters.
Technical Reference Manual -Table 21-6. UART Mode Baud and Error Rates
There is "Error Rates" in the above specification, and there is a 0.16% Error at 230400 bps. Is this the cause?
Is there any way to avoid it?
Thank you in advance.
Part Number:TDA2EVM5777
Tool/software: Linux
Hi,
I'm testing the TIDL usecase in linux with changing the last two link(ObjectDraw, Display) with Null link.
The null link just read meta data from TIOP link and do nothing.
The usecase was executed but FPS was too slow in each link.
Could you suggest any points what i missed?
Regards,
Yoo
Part Number:SM320C40
Hi E2E,
Good day!
Do you have an information regarding the Maximum Junction Temperature of SM320C40GFS60?
Looking forward to your response. Thanks.
Best regards,
Franz
Part Number:AM5718
Tool/software: Linux
Hello. I'm currently trying to boot customized am5718 on our company's board.
Since the company's board doesn't have eeprom, I've commented out mostly every parts of the code related to checking the board using eeprom in uboot/board/ti/am57xx/board.c.
I thought having the eeprom related code might prevent the board from booting normally.
Anyway, I'm getting the following error now when the u-boot command is supposed to appear.
I don't know how to proceed from here. Can anyone help me out please?
Part Number:66AK2H06
Tool/software: TI-RTOS
Hi,
I have a question from customer who is evaluating 66AK2H06.
It seems only *.lds file is prepared for 66AK2H06. This is for GNU tool.
There is no *.cmd file for TI ARM linker.
If customer wants to use TI ARM tool chain, where should customer get *.cmd file for linker?
Thanks and regards,
Koichiro Tashiro
Part Number:TDA2SX
Tool/software: Linux
Dear Champs,
I've been able to run OpenVX TIDL Object Detection (OD) in my end (VSDK v3.7 on TDA2x EVM). Please refer below link for my steps.
However, I'm seeing two issues while running this use case
1. The performance of OpenVX TIDL OD is quite poor:
In Linux, the FPS can only reach 5. As comparison, I ran TIDL OD use case in TI-RTOS, the FPS can reach 20. I compared the performance statistics, it looked like 4 EVEs are used in TI-RTOS but only one EVE is used in Linux. I attached the log below FYR.
(Please visit the site to view this file)
(Please visit the site to view this file)
2. Must run OpenVX TIDL Object Classification (OC) first then run OD:
OC must run prior to OD. If I ran OD directly, sometimes I got the error mentioned in below post
Most of the times OD just did not work, I saw only a big blinking rectangle around the video (picture below)
Log below FYR.
(Please visit the site to view this file)
Please help investigate the issues.
Thanks.
Part Number:TMS320DM8148
Tool/software: TI-RTOS
I will use can bus communication in my new project(based on TMS320DM8148),I want to know if therer is a standard lib of CAN bus driver in TI-RTOS?
What if I need to implement it?
Part Number:TMS320C6678
Hello Champs,
Customer wanted to use FPGA to send camera data to C6678 SRIO, because the camera data is too large, he worried the CPU load is too heavy, so he sent 1 doorbell after every frame data from FPGA, how to judge if the DSP has received all the data without losing any frame data?
If not using doorbell, is there any other method to judge if the DSP has received a packet data?
Thanks.
Rgds
Shine
