TI E2E support forums
TI E2E support forums
  • User
  • Site
  • Search
  • User
  • E2E™ design support >
  • Forums
    • Amplifiers
    • API solutions
    • Audio
    • Clock & timing
    • Data converters
    • DLP® products
    • Interface
    • Isolation
    • Logic
    • Microcontrollers
    • Motor drivers
    • Power management
    • Processors
    • RF & microwave
    • Sensors
    • Site support
    • Switches & multiplexers
    • Tools
    • Wireless connectivity
    • Archived forums
    • Archived groups
  • Technical articles
  • TI training
    • Tech days
    • Online training
    • Live events
    • Power Supply Design Seminar
  • Getting started
  • 简体中文
  • More
  • Cancel
Processors

Processors

Processors forum

  • Mentions
  • Tags
  • More
  • Cancel
  • Ask a new question
  • Ask a new question
  • Cancel
Texas Instruments (TI) Processors support forum is an extensive online knowledge base where millions of technical questions and solutions are available 24/7. You can search processors content or ask technical support questions on Sitara™ processors, digital signal processors (DSP) and automotive processors. Find the right solution for your circuit design challenges by using our TI E2E™ support forums that are supported by thousands of contributing TI experts.
Frequent questions
    • 2/26/2025
    • Bruno B

    [FAQ] AM6412: unused MMC0_CLK

    Part Number: AM6412

    Tool/software:

    Hi T.I community expert,

    1) There is something which is not clear about MMC0_CLK recommandations:

    When looking at the datasheet (2024) table 5-80 one can read the following :

    ==> MMC0_CLK can be left open when not used

    But on page 94 there is a note specifying some case where external pull is required: 

    The problem is that MMC0_CLK is also described in table 5-1 as being RX : ON after boot without any internal pull inside. This would therefore require an external pull when not used.

    Is there something I am missing ?

    2) I also have the same kind of question regarding I2C0_SCL which is described as RX : ON after BOOT. However I could not find recommandations about external pull when not used.

    Can you confirm ? or not ?

    With best regards

    Bruno

    Processors forum Processors
    • 2/25/2025
    • Josue Zamitiz-Ayala

    [FAQ] PROCESSOR-SDK-AM57X: Why is my Linux image from SDK 09.03.06.05 crashing?

    Part Number: PROCESSOR-SDK-AM57X

    Tool/software:

    Crash log looks like this:

    [    3.443115] ------------[ cut here ]------------
    [    3.447753] WARNING: CPU: 0 PID: 38 at drivers/bus/omap_l3_noc.c:133 l3_interrupt_handler+0x280/0x37c
    [    3.457061] 44000000.l3-noc:L3 Standard Error: MASTER MPU TARGET IPU1 (Read Link): At Address: 0x00082000 : Data Access in User mode during Functional access
    [    3.471191] Modules linked in:
    [    3.474273] CPU: 0 PID: 38 Comm: kworker/u4:3 Not tainted 6.1.119-ti-ge4e8b16e66f5 #1
    [    3.482147] Hardware name: Generic DRA74X (Flattened Device Tree)
    [    3.488281] Workqueue: events_unbound deferred_probe_work_func
    [    3.494140]  unwind_backtrace from show_stack+0x10/0x14
    [    3.499420]  show_stack from dump_stack_lvl+0x40/0x4c
    [    3.504516]  dump_stack_lvl from __warn+0x7c/0x158
    [    3.509338]  __warn from warn_slowpath_fmt+0x124/0x1c0
    [    3.514495]  warn_slowpath_fmt from l3_interrupt_handler+0x280/0x37c
    [    3.520904]  l3_interrupt_handler from __handle_irq_event_percpu+0x7c/0x228
    [    3.527923]  __handle_irq_event_percpu from handle_irq_event+0x38/0x80
    [    3.534484]  handle_irq_event from handle_fasteoi_irq+0x9c/0x204
    [    3.540557]  handle_fasteoi_irq from generic_handle_domain_irq+0x28/0x38
    [    3.547302]  generic_handle_domain_irq from gic_handle_irq+0x74/0x88
    [    3.553680]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44
    [    3.559906]  generic_handle_arch_irq from call_with_stack+0x18/0x20
    [    3.566223]  call_with_stack from __irq_svc+0x84/0xac
    [    3.571289] Exception stack(0xf00e9be0 to 0xf00e9c28)
    [    3.576385] 9be0: 00000000 40132000 00000000 00000000 c2aa0140 c15ae4e8 c2a47810 00000000
    [    3.584594] 9c00: c0e46bcc c0e467ac 00000000 00000000 0000cf90 f00e9c30 c06a31ec c06a3270
    [    3.592803] 9c20: 20000013 ffffffff
    [    3.596313]  __irq_svc from sysc_probe+0xdec/0x1534
    [    3.601226]  sysc_probe from platform_probe+0x5c/0xbc
    [    3.606323]  platform_probe from really_probe+0xc8/0x2ec
    [    3.611694]  really_probe from __driver_probe_device+0x88/0x1a0
    [    3.617645]  __driver_probe_device from driver_probe_device+0x30/0x104
    [    3.624206]  driver_probe_device from __device_attach_driver+0x94/0x108
    [    3.630859]  __device_attach_driver from bus_for_each_drv+0x80/0xd0
    [    3.637176]  bus_for_each_drv from __device_attach+0xac/0x1e4
    [    3.642944]  __device_attach from bus_probe_device+0x84/0x8c
    [    3.648651]  bus_probe_device from device_add+0x3ac/0x78c
    [    3.654083]  device_add from of_platform_device_create_pdata+0x90/0xc0
    [    3.660675]  of_platform_device_create_pdata from of_platform_bus_create+0x1b0/0x244
    [    3.668457]  of_platform_bus_create from of_platform_populate+0x70/0xd4
    [    3.675109]  of_platform_populate from simple_pm_bus_probe+0x90/0x94
    [    3.681488]  simple_pm_bus_probe from platform_probe+0x5c/0xbc
    [    3.687377]  platform_probe from really_probe+0xc8/0x2ec
    [    3.692718]  really_probe from __driver_probe_device+0x88/0x1a0
    [    3.698669]  __driver_probe_device from driver_probe_device+0x30/0x104
    [    3.705230]  driver_probe_device from __device_attach_driver+0x94/0x108
    [    3.711883]  __device_attach_driver from bus_for_each_drv+0x80/0xd0
    [    3.718200]  bus_for_each_drv from __device_attach+0xac/0x1e4
    [    3.723999]  __device_attach from bus_probe_device+0x84/0x8c
    [    3.729675]  bus_probe_device from deferred_probe_work_func+0x78/0xa4
    [    3.736145]  deferred_probe_work_func from process_one_work+0x1d8/0x514
    [    3.742828]  process_one_work from worker_thread+0x220/0x50c
    [    3.748504]  worker_thread from kthread+0xec/0x11c
    [    3.753356]  kthread from ret_from_fork+0x14/0x38
    [    3.758087] Exception stack(0xf00e9fb0 to 0xf00e9ff8)
    [    3.763153] 9fa0:                                     00000000 00000000 00000000 00000000
    [    3.771362] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    [    3.779602] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
    [    3.786254] ---[ end trace 0000000000000000 ]---
    [    3.790893] 8<--- cut here ---
    [    3.793975] Unhandled fault: asynchronous external abort (0x1211) at 0x00000000
    [    3.801330] [00000000] *pgd=80000080004003, *pmd=00000000
    [    3.806762] Internal error: : 1211 [#1] PREEMPT SMP ARM
    [    3.812011] Modules linked in:
    [    3.815093] CPU: 0 PID: 38 Comm: kworker/u4:3 Tainted: G        W          6.1.119-ti-ge4e8b16e66f5 #1
    [    3.824432] Hardware name: Generic DRA74X (Flattened Device Tree)
    [    3.830566] Workqueue: events_unbound deferred_probe_work_func
    [    3.836425] PC is at sysc_probe+0xdec/0x1534
    [    3.840728] LR is at sysc_probe+0xd68/0x1534
    [    3.845031] pc : [<c06a3270>]    lr : [<c06a31ec>]    psr: 20000013
    [    3.851318] sp : f00e9c30  ip : 0000cf90  fp : 00000000
    [    3.856567] r10: 00000000  r9 : c0e467ac  r8 : c0e46bcc
    [    3.861816] r7 : 00000000  r6 : c2a47810  r5 : c15ae4e8  r4 : c2aa0140
    [    3.868377] r3 : 00000000  r2 : 00000000  r1 : 40132000  r0 : 00000000
    [    3.874938] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
    [    3.882110] Control: 30c5387d  Table: 80003000  DAC: fffffffd
    [    3.887878] Register r0 information: NULL pointer
    [    3.892608] Register r1 information: non-paged memory
    [    3.897705] Register r2 information: NULL pointer
    [    3.902435] Register r3 information: NULL pointer
    [    3.907165] Register r4 information: slab kmalloc-256 start c2aa0100 pointer offset 64 size 256
    [    3.915924] Register r5 information: non-slab/vmalloc memory
    [    3.921600] Register r6 information: slab kmalloc-1k start c2a47800 pointer offset 16 size 1024
    [    3.930389] Register r7 information: NULL pointer
    [    3.935119] Register r8 information: non-slab/vmalloc memory
    [    3.940795] Register r9 information: non-slab/vmalloc memory
    [    3.946472] Register r10 information: NULL pointer
    [    3.951293] Register r11 information: NULL pointer
    [    3.956115] Register r12 information: non-paged memory
    [    3.961273] Process kworker/u4:3 (pid: 38, stack limit = 0x43f48f53)
    [    3.967681] Stack: (0xf00e9c30 to 0xf00ea000)
    [    3.972045] 9c20:                                     00000001 00000000 00000000 c141cff4
    [    3.980285] 9c40: eec9b578 c0ff003c 00000001 c2a47810 eec9b578 c1032ba4 00000001 00000001
    [    3.988494] 9c60: 00000303 86677b7d 00000000 00000000 c2a47810 c14fc808 00000000 eec9b584
    [    3.996704] 9c80: 00000000 c150f898 00000001 c0805b0c c2a47810 00000000 c14fc808 c08031fc
    [    4.004943] 9ca0: c2a47810 c14fc808 c2a47810 000000b0 eec9b584 c08034a8 60000013 00000000
    [    4.013153] 9cc0: c15b2cec c14fc808 c2a47810 000000b0 eec9b584 c08035f0 00000001 c14fc808
    [    4.021362] 9ce0: f00e9d2c c2a47810 eec9b584 c0803c04 00000000 f00e9d2c c0803b70 c1952c10
    [    4.029602] 9d00: eec9b584 c080144c eec9b584 c18db76c c1d3c938 86677b7d c2a47810 00000001
    [    4.037811] 9d20: c2a47854 c08038a0 eec9b590 c2a47810 00000001 86677b7d c2a47810 c150fe30
    [    4.046020] 9d40: c2a47810 c08024d8 c2a47810 00000000 c15b2cb8 c07ff68c 00000000 00000000
    [    4.054260] 9d60: 00000000 00000000 00000000 86677b7d c2a47800 c1952c10 00000000 c141cff4
    [    4.062469] 9d80: eec9b5dc c141cff4 00000000 c0ae8f24 eec9b578 c141cdf0 00000000 00000000
    [    4.070678] 9da0: c141cfd0 c0ae9154 00000000 86677b7d c1952c10 00000001 58882000 00000000
    [    4.078918] 9dc0: 58882003 00000000 ff9e8370 00000200 00000000 00000000 00000000 00000000
    [    4.087127] 9de0: 00000000 86677b7d eec9b05c eec9b578 eec3c644 00000000 c141cdf0 c1952c10
    [    4.095336] 9e00: 00000001 00000000 c15602c0 c0ae9354 00000001 00000000 c1952c10 eec3c644
    [    4.103576] 9e20: c141cdf0 00000000 00000000 c180f00d c193ec00 c069ff68 00000000 c1952c10
    [    4.111785] 9e40: c14fc724 c0805b0c c1952c10 00000000 c14fc724 c08031fc c1952c10 c14fc724
    [    4.119995] 9e60: c1952c10 00000001 00000000 c08034a8 60000013 c180f00d c15b2cec c14fc724
    [    4.128204] 9e80: c1952c10 00000001 00000000 c08035f0 00000001 c14fc724 f00e9ee4 c1952c10
    [    4.136444] 9ea0: 00000000 c0803c04 00000000 f00e9ee4 c0803b70 00000000 00000000 c080144c
    [    4.144653] 9ec0: 00000000 c18db76c c1d3c838 86677b7d c1952c10 00000001 c1952c54 c08038a0
    [    4.152862] 9ee0: 00000000 c1952c10 00000001 86677b7d c1952c10 c150fe30 c1952c10 c08024d8
    [    4.161102] 9f00: c1952c10 c150fb7c c150fb90 c0802918 c150fbb4 c1baaa80 c1806600 c180f000
    [    4.169311] 9f20: 00000000 c024f80c c1284a00 c193ec00 c1806600 c1806600 c180661c c1baaa80
    [    4.177520] 9f40: c1806600 c1baaa98 c180661c c1403d40 00000088 c193ec00 c1806600 c0250118
    [    4.185760] 9f60: c155f854 c1571148 f00e9f7c c193ec00 c1bb54c0 c024fef8 c1baaa80 c1bb5740
    [    4.193969] 9f80: f00d9ecc 00000000 00000000 c0256cc0 c1bb54c0 c0256bd4 00000000 00000000
    [    4.202178] 9fa0: 00000000 00000000 00000000 c020021c 00000000 00000000 00000000 00000000
    [    4.210418] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    [    4.218627] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
    [    4.226837]  sysc_probe from platform_probe+0x5c/0xbc
    [    4.231933]  platform_probe from really_probe+0xc8/0x2ec
    [    4.237274]  really_probe from __driver_probe_device+0x88/0x1a0
    [    4.243225]  __driver_probe_device from driver_probe_device+0x30/0x104
    [    4.249786]  driver_probe_device from __device_attach_driver+0x94/0x108
    [    4.256469]  __device_attach_driver from bus_for_each_drv+0x80/0xd0
    [    4.262756]  bus_for_each_drv from __device_attach+0xac/0x1e4
    [    4.268554]  __device_attach from bus_probe_device+0x84/0x8c
    [    4.274261]  bus_probe_device from device_add+0x3ac/0x78c
    [    4.279693]  device_add from of_platform_device_create_pdata+0x90/0xc0
    [    4.286254]  of_platform_device_create_pdata from of_platform_bus_create+0x1b0/0x244
    [    4.294036]  of_platform_bus_create from of_platform_populate+0x70/0xd4
    [    4.300689]  of_platform_populate from simple_pm_bus_probe+0x90/0x94
    [    4.307098]  simple_pm_bus_probe from platform_probe+0x5c/0xbc
    [    4.312957]  platform_probe from really_probe+0xc8/0x2ec
    [    4.318298]  really_probe from __driver_probe_device+0x88/0x1a0
    [    4.324279]  __driver_probe_device from driver_probe_device+0x30/0x104
    [    4.330841]  driver_probe_device from __device_attach_driver+0x94/0x108
    [    4.337493]  __device_attach_driver from bus_for_each_drv+0x80/0xd0
    [    4.343811]  bus_for_each_drv from __device_attach+0xac/0x1e4
    [    4.349578]  __device_attach from bus_probe_device+0x84/0x8c
    [    4.355285]  bus_probe_device from deferred_probe_work_func+0x78/0xa4
    [    4.361755]  deferred_probe_work_func from process_one_work+0x1d8/0x514
    [    4.368408]  process_one_work from worker_thread+0x220/0x50c
    [    4.374114]  worker_thread from kthread+0xec/0x11c
    [    4.378936]  kthread from ret_from_fork+0x14/0x38
    [    4.383666] Exception stack(0xf00e9fb0 to 0xf00e9ff8)
    [    4.388763] 9fa0:                                     00000000 00000000 00000000 00000000
    [    4.396972] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    [    4.405181] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
    [    4.411834] Code: e3a00000 e5991004 e3510000 0a000004 (e594e008)
    [    4.417968] ---[ end trace 0000000000000000 ]---
    [    4.422607] note: kworker/u4:3[38] exited with irqs disabled

    In general look for:
    44000000.l3-noc:L3 Standard Error: MASTER MPU TARGET IPU1 (Read): At Address: 0x0008204C : Data Access in Supervisor mode during Functional access

    Processors forum Processors
    • 2/24/2025
    • Divyansh Mittal

    [FAQ] AM62L: Commonly Asked Questions

    Part Number: AM62L

    Tool/software:

    Please find below the most commonly asked questions about AM62L:

    Processors forum Processors
    • 2/23/2025
    • Kallikuppa Sreenivasa

    [FAQ] AM62L ( AM62L32 , AM62L31 ) Custom board hardware design - FAQs related to Processor collaterals, functioning, peripherals, interface and EVM

    Part Number: AM62L

    Tool/software:

    Hi Board designers, 

    AM62L: Custom board hardware design - FAQs related to Processor collaterals, functioning, peripherals, interface and EVM

    Regards,

    Sreenivasa

    Processors forum Processors
    • 2/23/2025
    • Kallikuppa Sreenivasa

    [FAQ] AM62L ( AM62L32 , AM62L31 ) Design Recommendations / Custom board hardware design - Custom board schematics self-review

    Part Number: AM62L

    Tool/software:

    Hi TI experts, 

    I have completed my custom board schematics based on AM62Lx SOC. Could you guide me on reviewing the schematics.

    Processors forum Processors
    • 2/23/2025
    • Kallikuppa Sreenivasa

    [FAQ] AM62L ( AM62L32 , AM62L31 ) Custom board hardware design – I2C interface

    Part Number: AM62L

    Tool/software:

    Hi TI Experts,

    I have the below queries regarding the I2C interface

    1. Need information on the number of I2C interfaces available
    2. Termination of I2C interfaces when used as I2C interface and not used as I2C interface.
    3. Any additional recommendations / Guidelines
    4. Any concerns on Interfacing SoC Non-Failsafe I2C to devices that are powered before the SoC- Ex PMIC
    5. Any exception that are required to be considered when using the I2C interfaces. 
    6. Can the I2C interface be used to interface with devices supporting SMBus or PMBus 

    Let me know your thoughts.

    Processors forum Processors
    • 2/23/2025
    • Kallikuppa Sreenivasa

    [FAQ] AM62L ( AM62L32 , AM62L31 ) Custom board hardware design - Reusing TI EVM design files

    Part Number: AM62L

    Tool/software:

    Hi TI Experts,

    I am starting a new board design and planning to use TI EVM design files for designing my custom board.
    Please let me know if you have any suggestions.

    Processors forum Processors
    • 2/22/2025
    • Kallikuppa Sreenivasa

    [FAQ] AM62L ( AM62L32 , AM62L31 ) Custom board hardware design - Design notes and Review notes for Reuse of EVM TMDS62LEVM Schematics

    Part Number: AM62L

    Tool/software:

    Hi TI Experts,

    I am starting a new board design and planning to use TI EVM design files for designing my custom board.

    Please let me know if you have any recommendations or guidelines to be followed.

    Processors forum Processors
    • 2/22/2025
    • Kallikuppa Sreenivasa

    [FAQ] AM62L ( AM62L32 , AM62L31 ) Custom board hardware design – Collaterals to Get started

    Part Number: AM62L

    Tool/software:

    Hi TI Experts,

    Can you provide a List of collaterals that can be referred when starting a custom board hardware design.

    Processors forum Processors
    • 2/19/2025
    • Michael Nichols

    [FAQ] PROCESSOR-SDK-J784S4: PSDK QNX: Failure to Build 10.1 Release: PROCMGR_AID_KEYDATA undeclared

    Part Number: PROCESSOR-SDK-J784S4

    Tool/software:

    If an error stating PROCMGR_AID_KEYDATA undeclared when building the 10.1 PSDK QNX release, then please follow the steps after the example error to remediate the build errors.

    Example of error:

    ${PSDK_RTOS}/psdkqa/qnx/codec/vpu/resmgr/src/tivpu_mgr.c:257:67: error: 'PROCMGR_AID_KEYDATA' undeclared (first use in this function); did you mean 'PROCMGR_AID_MEM_ADD'?
      257 |                         PROCMGR_AOP_ALLOW | PROCMGR_ADN_NONROOT | PROCMGR_AID_KEYDATA,
          |                                                                   ^~~~~~~~~~~~~~~~~~~
          |                                                                   PROCMGR_AID_MEM_ADD

    Steps to remediate the build errors (choose option A or B):

    • Option A: downgrade the QNX Software Center package com.qnx.qnx800.target.microkernel.core to 2.0.2.00388T202406131303L or earlier
    • Option B: remove all lines that make reference to PROCMGR_AID_KEYDATA
      • Files/lines to remove:
        • psdkqa/qnx/codec/vpu/OpenMAXIL/test/enc_performance/main.cpp:706:67
        • psdkqa/qnx/codec/vpu/OpenMAXIL/test/enc/main.cpp:690:67
        • psdkqa/qnx/codec/vpu/OpenMAXIL/test/dec/main.cpp:182:67
        • psdkqa/qnx/codec/vpu/resmgr/src/tivpu_mgr.c:257:67
        • psdkqa/qnx/utils/ddr_bw/src/ddr_bw.c:550:67

    This procmgr ability was documented as generally not being required in SDP 7.1 but became undefined as of the microkernel package 2.0.3.02010T202412011711L

    Processors forum Processors
<>

View FAQ threads
  • Tags
  • RSS
  • More
  • Cancel
  • Threads 199049 Discussions
  • Suggested Answer

    AM6421: Industrial Communication SDK Ethercat Application does not Run on R5F0_0 from linux 0

    370 views
    17 replies
    Latest 1 day ago
    by Nick Saulnier
  • Suggested Answer

    TMDS64EVM: Where the Ethernet MAC ID Saved in the I2C 0

    68 views
    2 replies
    Latest 1 day ago
    by Tushar Thakur
  • Not Answered

    TDA4VM: TDA4VM brownout on vdd_cpu during AVS configuration 0

    87 views
    6 replies
    Latest 1 day ago
    by kcastille
  • Not Answered

    TDA4VE-Q1: Recommend DRAM size / DRAM ranks usage 0

    33 views
    1 reply
    Latest 1 day ago
    by Kevin S
  • Suggested Answer

    AM6442: DTS config to load ICSS prusw firmware 0

    41 views
    3 replies
    Latest 1 day ago
    by Nick Saulnier
  • Not Answered

    DRA821U-Q1: DRA821 MCSPI1 transaction to transaction delay issue 0

    45 views
    2 replies
    Latest 1 day ago
    by Luke
  • Not Answered

    J722SXH01EVM: Issue adding edgeai-gst-plugins to yocto build +1

    76 views
    2 replies
    Latest 1 day ago
    by Jared McArthur
  • Not Answered

    TDA4AH-Q1: Audio codec not supported more than 1 device 0

    132 views
    11 replies
    Latest 1 day ago
    by Jared McArthur
  • Suggested Answer

    AM62L: How to control GPIO in U-Boot 0

    187 views
    9 replies
    Latest 1 day ago
    by Shriya Surti
  • Answered

    AM67A: Three Independent Video Outputs with DSI and LVDS 0

    80 views
    4 replies
    Latest 1 day ago
    by Ryan Davitt
  • Not Answered

    PROCESSOR-SDK-RTOS-J721S2: TIDL Importer encountered an error while importing the model​ 0

    75 views
    3 replies
    Latest 1 day ago
    by Marvn Arcangel
  • Not Answered

    AUDIO-AM62D-EVM: Difference in execution clock cycles between AM62D and AM62A, and C7x 0

    221 views
    7 replies
    Latest 1 day ago
    by Mukul Bhatnagar
  • Not Answered

    AM62P: Error of RM 0

    35 views
    1 reply
    Latest 1 day ago
    by Paula Carrillo
  • Not Answered

    AM6442: AM64x R5F code MCU interrupt hander set up 0

    35 views
    1 reply
    Latest 1 day ago
    by Tushar Thakur
  • Not Answered

    AM69A: Number and usage of R5F cores on J784S4 SoCs 0

    40 views
    2 replies
    Latest 1 day ago
    by Brijesh Jadav
  • Suggested Answer

    DRA829V: Iam enabling watchdog in uboot with version (ti-processor-sdk-linux-adas-j721e-evm-09_00_01_03) 0

    55 views
    3 replies
    Latest 1 day ago
    by Keerthy J
  • Answered

    AM5748: Linux SDK 11.x planned release date 0

    71 views
    5 replies
    Latest 1 day ago
    by Gonzalo Vara
  • Answered

    IND-COMMS-SDK: ESC: latch input conf with PDI 0

    237 views
    4 replies
    Latest 1 day ago
    by HS FAE Germany
  • Answered

    AM4378: Regarding Uart2 on the AM4378 0

    49 views
    3 replies
    Latest 1 day ago
    by hiroaki isogawa
  • Not Answered

    AM62P: Fast boot time KPI: unexpected time delay in ROM boot 0

    262 views
    17 replies
    Latest 1 day ago
    by Fan Bomiao
<>