Part Number: TDA4AL-Q1 Hello Support-Team,
I ran the TIOVX conformance test suite on our PikeOS port at SYSGO, based on PSDK RTOS 08_05_00_11.
The test tivxPackedDataFormat.CreateUniformImage/0/TIVX_DF_IMAGE_P12 crashed because of an unaligned memory…
Part Number: TDA4AL-Q1 Other Parts Discussed in Thread: TDA4VE-Q1 , TDA4VL-Q1 Is there a tool available to estimate the power consumption of the J721S2 parts ( TDA4VE-Q1/TDA4VL-Q1/TDA4AL-Q1) under various configurations and loads?
I can not find any reference…
Part Number: TDA4AL-Q1 Hello,
We plan to use TDA4AL in our project and need to implement the HSM function. There is some requirement in our group standard and we'd like to see whether the chip can meet it.
For the SMS(security management system),…
Part Number: TDA4AL-Q1 Hello,
I'm trying to use CTT but I cannot find my variant which is TDA4AL.
Is there the Clock Tree Tool (CTT) for TDA4AL? Or are there any plans to provide it?
Best regards,
Part Number: TDA4AL-Q1 I ran the command sh run_app_multi_cam.sh and found that in log ISS: Starting sensor [MY_CAMERA_YUV]... !!! , the app is stuck, open APP_REMOTE_SERVICE_DEBUG to check the IPC log, and find that when sending a com.ti.perf_stats service…
Part Number: TDA4AL-Q1 Other Parts Discussed in Thread: TDA4VM
Hi,
J721S2 SDK, in the path ti-processor-sdk-rtos-j721s2-evm-08_05_00_11/vision_apps/platform/j721s2/rtos/mcu2_1, we add can task to transmission and receive can message use mcu_mcan0 , mcu2_1…
Hi, Could you please check if this issue is similar to the thread (+) TDA4AL-Q1: The IPC service com.ti.perf_stats failed to run on the muc2_1, causing the IPC function to get stuck - Processors forum - Processors - TI E2E support forums
I believe you are…
Part Number: TDA4VL-Q1 Other Parts Discussed in Thread: TDA4VE-Q1 , TDA4VL Hi TI
As ti.com has updated with TDA4VE-Q1 and variant devices, A customer begins to investigate this new deivce.
They found something to be clarified about Deep-learning Performance…
Dear Experts,
From Marco:
I found a very similar issue from earlier this year where a workaround was found by increasing the timeout period from 20 to 200 (ms?) for low temp rather than disabling IO calibration in kernel: https://e2e.ti.com/support…