Quantcast
Channel: Processors
Viewing all 149826 articles
Browse latest View live

Forum Post: RE: Linux/PROCESSOR-SDK-AM335X: PRU debug printout

$
0
0
Thanks, Nick Saulnier. How do I know which channel in the pru receives the data in this example?

Forum Post: RE: TDA2EXEVM: different result between quantStatusTool and TDA2EXVEM

$
0
0
Hi Praveen I try to run on standalone DSP by following steps in section 3.3.5 in the userguide, Open the CCS and download the "dsp_test_dl_algo.out" through the emulator to the tda2xx development board. EVE and DSP are matching. Final output is only 10 bytes similar to the... A3 86 FF 8D 90 D1 6E E0 6F 80 ----------------------------------------------------------------------------------------------------------------------------- When I use the configuration file you provided.Generate these two files "Generate these two files outputNetFile = "tidl_net_cifar.bin" outputParamsFile = "tidl_param_cifar.bin" Then copy the two files to the SD card, copy the four. y to the SD card, and pass the SD card boot program to run ALG_TIDL. Piece of selected the DSP result is wrong. Piece of selected the eve result is right. -------------------------------------------------------------------------------------------------------------------------------- Thank you very much! Mary

Forum Post: RE: Linux/DRA746: Waylandsink: Not able to play an video file

$
0
0
Hi Ikshwaku, ON TI-EVM with PSDKLA3.04 images, no issue observed for this stream. Able to playback without any error. But we configure weston with desktop shell. waylabndsink with ivi-shell support is not available yet. Can you confirm if the issue is observed consistently for every playback and at the same duration? Ramprasad

Forum Post: TDA2EG: add new ddr3 support

$
0
0
Part Number: TDA2EG Our custom board used 2*4GB DDR3 and the DDR3 type is V73CBG04168RC -J11. Where do I need revise the uboot code to adapt the new DDR3? Please tell me the tutorial or some advice. My SDK version is 3.02.

Forum Post: RE: Linux/TDA3XEVM: INTERNAL ERROR

$
0
0
Hi Rishabh, The above mentioned commands i.e., Building dependencies using "make -s depend" and then VSDK using "make -s" are working fine, but i am compiling many times to make sure that its working completely fine. Thank you for helping me about this error, get back to you shortly., Regards Balaji

Forum Post: RE: RTOS/TMDXICE110: Pinmux file

$
0
0
Hello, Garrett. Thank you for answer. I was able to find pinmux config and looked them. LED_1_pin is really on K15,GPIO0_17. After I changed code like You said, my board still not blink LED1. After I tried change GPIO DEVICE CONFIG((GPIO_USER1_LED_PORT_NUM + 1 ) to GPIO DEVICE CONFIG((GPIO_USER1_LED_PORT_NUM), and my board is able to blink LED1. Now I want to manage LED2 and etc. How can I do my configuration to function GPIO_init(). Should I write it to gpioPinConfigs[], or it doing another way? If it should write to gpioPinConfigs[], then how will it be correct?

Forum Post: RE: Linux/AM5728: Qt QMenu issue

$
0
0
Hello, Could you try on your side export QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS="rotate=180". You could try to run evtest here is the link to the guide: processors.wiki.ti.com/.../Evtest I would recommend you to take a look into this guides also: processors.wiki.ti.com/.../How_to_Recalibrate_the_Touchscreen (chapter Weston based Graphic System) processors.wiki.ti.com/.../Processor_Linux_SDK_Graphics_and_Display If the last guide you could find how you could run qt demo without weston. You could try this. In additional, here is the link to the qt forum https://forum.qt.io/. Hope this helps you. BR Margarita

Forum Post: RE: TDA2EXEVM: Counter get paused for some time while working with Ethernet Tx and Rx rate of 14mbps

$
0
0
Hi Stanley, It's SYSBIOS . I have one end Autosar stack on A15. On which we are continuously receiving data for one camera which is approximately 14 Mbps. Received data send from A15 to IPU1 through cddipc mechanism.Which standard MCAL driver mcal29. When we are receiving data from Ethernet camera, received data loop-back transmitted to Ethernet again for checking purpose. For measurement of CPULOAD we have Timer3 running on MPUA15. As i said previously for the Ethernet speed above 8-9mbps approximately, after 7 to 8 sec Timer3 counter register not increment for approximate 1sec. means stuck for some sec and again started to increment. That's why we get same value of previous calculation and current calculation. If i reduce the speed up to 7mbps it's working properly. i check it for 1.5 Hr. Timer not stop anywhere in code.

Forum Post: AM5728: Linux SDK build issue

$
0
0
Part Number: AM5728 After Running the following . sudo ./create-sdcard.sh In Last Step it is asking for ZImage and *.dtb file path. But after compiling ti-processor-sdk-linux-am57xx-evm-04.03.00.05 zImage is only available in prebuilds No new zImage is created after compiling .

Forum Post: RE: Linux/AM4378: Disabling sleep mode

$
0
0
Dear Steve, How to add "consoleblank=0" in bootargs? i tried as follow. u-boot# setenv bootargs consoleblank=0 But it did not work. Can you tell, How do i add bootargs? Regards, Winiston.P

Forum Post: Linux/AM5728: SD card problem

$
0
0
Part Number: AM5728 Tool/software: Linux Hi, I saw message “failed to set system capabilities” from serial port。 I have no power regulator for SD, how to skip power switch? Thank you!

Forum Post: RE: AM4372: About kernel and uboot am437x-gp-evm.dts

$
0
0
Hello Sasaki, The reason why the eMMC can not be used in U-Boot is because the NAND is the device selected to use. If you remove the GPMC/NAND node or implement the same mechanism used in kernel's device tree source and replace the NAND pinmux settings with the eMMC pinmux settings in both places device tree and /board-support/u-boot- /board/ti/am43xx/mux.c you will be able to use the eMMC in U-Boot, but you will not be able to boot from it. To be able to boot from eMMC its connections must match the table 5-32 or 5-33 in the TRM. Best regards, Kemal

Forum Post: RE: TDA2: Running caffe-jacinto object detection using Vision SDK 3.03 TIDL_OD usecase

$
0
0
Hi Navin, Inside the deploy.prototxt, Did you set the "keep_top_k" parameter to 20 , and "confidence_threshold" to 0.15? It seems that these two parameters influence the real time MAC and the performance. Best Regards, Eric Lai

Forum Post: RTOS/AM5726: FATFS on RAMdisk example

$
0
0
Part Number: AM5726 Tool/software: TI-RTOS Hi everybody , I would like to work with RAM disk – I didn’t find any API reference for that in C:\ti\pdk_am57xx_1_0_9\packages\ti\fs\fatfs\docs. could you help me ? any example of RAMdisk I can reuse ? regards Carlo

Forum Post: RE: Linux/TDA2EVM5777: Can camera capture and audio playback work simultaneously TDA2x EVM ?

$
0
0
Hi Uday, Q1. How many instances of the camera are you using? If you're using more than 4 instances of the camera then VIN6A and McASP are muxed and can't be used together. So yes, #3 should work provided VIN6A isn't used. Q2. No, there are no use-cases on VSDK which exercise audio, so no compile time flag exists to enable audio from IPU. Q3. Yes, you could add the same functionality on the IPU side provided you're not using VIN6A (if you're using lesser than 4 instances of capture, this should be OK). Regards Shravan

Forum Post: RE: Linux/TDA3XEVM: INTERNAL ERROR

$
0
0
Hi Rishabh, i am facing the same error again, here is the reference log. balaji@FSETBLR2D036:~/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/vision_sdk/build$ gmake -s depend mkdir: cannot create directory ‘/home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/vision_sdk/links_fw/include/config’: File exists mkdir: cannot create directory ‘/home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/vision_sdk/links_fw/include/config/apps’: File exists mkdir: cannot create directory ‘/home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/vision_sdk/links_fw/include/config/apps/tda3xx_evm_bios_all’: File exists # makeconfig: Config is [ tda3xx_evm_bios_all ] # makeconfig: Output file is @ /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_04_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/vision_sdk/links_fw/include/config/apps/tda3xx_evm_bios_all/system_cfg.h # makeconfig: Input file is @ /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/vision_sdk/build/configs/tda3xx_evm_bios_all/cfg.mk # makeconfig: Generating header ... # makeconfig: Generating alg plugin config ... # makeconfig: Generating usecase config ... # makeconfig: Generating footer ... # makeconfig: Done !!! # # CPUs that are NOT required but included in config [ tda3xx_evm_bios_all ], # # WARNING: IPU1_1 can be excluded from application # # CPUs that are required but not included in config [ tda3xx_evm_bios_all ], # # # Edit /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/vision_sdk/build/configs/tda3xx_evm_bios_all/cfg.mk to include or exclude CPUs in an application # # Compiling tda3xx-evm:ipu1_0:release:edma3lld_drv: src/edma3_drv_init.c # Compiling tda3xx-evm:ipu1_0:release:edma3lld_drv: src/edma3_drv_basic.c # Compiling tda3xx-evm:ipu1_0:release:edma3lld_drv: src/edma3_drv_adv.c # # Archiving tda3xx-evm:ipu1_0:release:edma3lld_drv # # Compiling tda3xx-evm:ipu1_0:release:edma3lld_rm: src/edma3resmgr.c # Compiling tda3xx-evm:ipu1_0:release:edma3lld_rm: src/edma3_rm_gbl_data.c # Compiling tda3xx-evm:ipu1_0:release:edma3lld_rm: src/configs/edma3_tda3xx_cfg.c # # Archiving tda3xx-evm:ipu1_0:release:edma3lld_rm # # Compiling tda3xx-evm:c66xdsp_1:release:edma3lld_drv: src/edma3_drv_init.c # Compiling tda3xx-evm:c66xdsp_1:release:edma3lld_drv: src/edma3_drv_basic.c # Compiling tda3xx-evm:c66xdsp_1:release:edma3lld_drv: src/edma3_drv_adv.c # # Archiving tda3xx-evm:c66xdsp_1:release:edma3lld_drv # # Compiling tda3xx-evm:c66xdsp_1:release:edma3lld_rm: src/edma3resmgr.c # Compiling tda3xx-evm:c66xdsp_1:release:edma3lld_rm: src/edma3_rm_gbl_data.c # Compiling tda3xx-evm:c66xdsp_1:release:edma3lld_rm: src/configs/edma3_tda3xx_cfg.c # # Archiving tda3xx-evm:c66xdsp_1:release:edma3lld_rm # # Compiling tda3xx-evm:arp32_1:release:edma3lld_drv: src/edma3_drv_init.c # Compiling tda3xx-evm:arp32_1:release:edma3lld_drv: src/edma3_drv_basic.c # Compiling tda3xx-evm:arp32_1:release:edma3lld_drv: src/edma3_drv_adv.c # # Archiving tda3xx-evm:arp32_1:release:edma3lld_drv # # Compiling tda3xx-evm:arp32_1:release:edma3lld_rm: src/edma3resmgr.c # Compiling tda3xx-evm:arp32_1:release:edma3lld_rm: src/edma3_rm_gbl_data.c # Compiling tda3xx-evm:arp32_1:release:edma3lld_rm: src/configs/edma3_tda3xx_cfg.c # # Archiving tda3xx-evm:arp32_1:release:edma3lld_rm # Nothing to be done for tda3xx csl_init Nothing to be done for tda3xx csl_intc # Compiling tda3xx:ipu1_0:release:csl: ./soc/common/csl_device_xbar.c # Compiling tda3xx:ipu1_0:release:csl: ./soc/common/csl_device_common.c # Compiling tda3xx:ipu1_0:release:csl: ./arch/m4/src/interrupt.c # Compiling tda3xx:ipu1_0:release:csl: ./arch/m4/src/ipu_wugen.c # Compiling tda3xx:ipu1_0:release:csl: ./arch/m4/src/ammu.c # Compiling tda3xx:ipu1_0:release:csl: ./arch/m4/src/unicache.c # Compiling tda3xx:ipu1_0:release:csl: ./arch/m4/src/ipu_ecc.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/adc/V0/priv/adc.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/crc/V0/priv/crc.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/dcan/V0/priv/dcan.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/dcc/V0/priv/dcc.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/edma/V1/priv/edma.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/elm/V0/priv/elm.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/emif/V0/priv/emif.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/epwm/V0/priv/csl_epwm.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/esm/V0/priv/esm.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/gpio/V1/priv/gpio_v2.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/gpmc/V1/priv/gpmc.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/i2c/V2/priv/i2c.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/l3fw/V0/priv/l3fw.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/l4fw/V0/priv/l4fw.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/mailbox/V0/priv/mailbox.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/mcan/V0/priv/mcan.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/mcasp/V0/priv/mcasp.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/mcspi/V0/priv/mcspi.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/mmc/V0/priv/mmcsd.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/mmu/dsp/V0/priv/mmu.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/ocmc/V0/priv/ocmc_ecc_l1.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/ocmc/V0/priv/ocmc_ecc_l2.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/qspi/V1/priv/qspi.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/rti/V0/priv/rti.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/spinlock/V0/priv/spinlock.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/tesoc/V0/priv/tesoc.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/timer/V1/priv/timer.c # Compiling tda3xx:ipu1_0:release:csl: src/ip/uart/V1/priv/uart.c # # Archiving tda3xx:ipu1_0:release:csl into /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/ti_components/drivers/pdk_01_09_00_17/packages/ti/csl/lib/tda3xx/m4/release/ti.csl.aem4 ... # # Compiling tda3xx:ipu1_0:release:csl_utils_common: ./src/app_utils.c # # Archiving tda3xx:ipu1_0:release:csl_utils_common into /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/ti_components/drivers/pdk_01_09_00_17/packages/ti/csl/example/utils/common/lib/tda3xx/m4/release/csl_utils_common.aem4 ... # # Compiling tda3xx:ipu1_0:release:csl_uart_console: ./src/uartConfig.c # # Archiving tda3xx:ipu1_0:release:csl_uart_console into /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/ti_components/drivers/pdk_01_09_00_17/packages/ti/csl/example/utils/uart_console/lib/tda3xx/m4/release/csl_uart_console.aem4 ... # # Compiling tda3xx:ipu1_0:release:csl_utils_i2c: ./src/i2c.c # # Archiving tda3xx:ipu1_0:release:csl_utils_i2c into /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/ti_components/drivers/pdk_01_09_00_17/packages/ti/csl/example/utils/i2c/lib/tda3xx/m4/release/csl_utils_i2c.aem4 ... # # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_vm.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/V2/hw_pmhal_vmdata.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/V2/hw_pmhal_data.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/V2/hw_pmhal_data_names.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_pmic.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_pmicComm.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_i2cComm.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_mm.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_prm_int.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_bgap.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/V2/hw_pmhal_bgap_data.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_pdm.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_rm.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_sd.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_cm.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/common/hw_pmhal_bgap_common_data.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/V2/hw_pmhal_prmdata.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pm_utils.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/V2/hw_pmhal_clocktree_data.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_prcm_stats.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_clocktree.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_tps65917.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_lp8731.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_lp8733.c # Compiling tda3xx:ipu1_0:release:pm_hal: prcm/pmhal_lp8731_ lp3907 .c # # Archiving tda3xx:ipu1_0:release:pm_hal into /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/ti_components/drivers/pdk_01_09_00_17/packages/ti/drv/pm/lib/tda3xx/m4/release/pm_hal.aem4 ... # # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_vm.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/V2/hw_pmhal_vmdata.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/V2/hw_pmhal_data.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/V2/hw_pmhal_data_names.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_pmic.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_pmicComm.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_i2cComm.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_mm.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_prm_int.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_bgap.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/V2/hw_pmhal_bgap_data.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_pdm.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_rm.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_sd.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_cm.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/common/hw_pmhal_bgap_common_data.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/V2/hw_pmhal_prmdata.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pm_utils.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/V2/hw_pmhal_clocktree_data.c # Compiling tda3xx:ipu1_0:release:pm_hal_optimized: prcm/pmhal_prcm_stats.c INTERNAL ERROR: /home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/ti_components/cg_tools/linux/ti-cgt-arm_16.9.2.LTS/bin/armacpia experienced a segmentation fault while processing function (unknown or file scope) file (unknown) line 0 This is caused by a defect in the compiler itself. TI Customer Support may be able to suggest a workaround to avoid this. Upgrading to the newest version of the compiler may fix this problem. Contact TI in the E2E support forums at http://e2e.ti.com under "Development Tools", "TI C/C++ Compiler". See the link titled "Submitting an issue". Include this ENTIRE error message and a copy of the .pp file created when option --preproc_with_comment (-ppc) is used. >> Compilation failure make[4]: *** [/home/balaji/workdir/projects/PROCESSOR_SDK_VISION_03_03_00_00/PROCESSOR_SDK_VISION_03_03_00_00_setuplinux/vision_sdk/binaries/apps/tda3xx_evm_bios_all/ti/drv/pm/src/pmhal/optimized/obj/tda3xx/m4/release/pmhal_prcm_stats.oem4] Error 1 make[3]: *** [pm_hal_optimized] Error 2 make[2]: *** [pdk] Error 2 make[1]: *** [pdk] Error 2 gmake: *** [depend] Error 2 regards balaji

Forum Post: RE: RTOS/AM5726: FATFS on RAMdisk example

$
0
0
The RTOS team have been notified. They will respond here.

Forum Post: RE: Linux/AM5728: SD card problem

$
0
0
Please read this guide training.ti.com/dos-donts-posting-to-e2e-community-forums and post the required information.

Forum Post: RE: AM4372: Device tree settings in kernel and U-boot

$
0
0
Hi Kemal-san Thank you for your support! I got it! Best regards, Sasaki

Forum Post: RE: AM5728: Linux SDK build issue

$
0
0
Hello, Please follow this guide: software-dl.ti.com/.../Foundational_Components.html BR Margarita
Viewing all 149826 articles
Browse latest View live


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