Part Number: TMS320C5505
Hi team
We have a limitation in our design to use only a pair of I2S data lines for 4channel audio capture.
Do TMS320c5505 supports configuring I2S in half duplex mode, to use Rx and TX in I2S as same direction
And if it supports this configuration, is it possible to change the direction dynamically. - For use in both capture and playback scenarios
Regards
Naveen
Part Number: AM5728
Tool/software: Linux
Hi,
we are developing a custom board based on AM5728 EVM design for the application of video recording. The custom board is intended to record 3 video channels of 1024x768 . Currently it is consuming 28W on full run. Are there any ways to reduce the heat by optimizing the configurations in SDK
Regards
Marka reddy
Part Number: DRA756
Tool/software: Linux
Hello, we currently develop our programs on DRA756, using Processor SDK for Automotive 5.0.
And the kernel we use is ti-linux-kernel 4.14.133, but there is a problem with the dcan.
The connection goes as following:
And the can-pinmux in the dra7-evm.dts:
We can send and receive can-message using loopback mode:
ip link set can0 type can bitrate 100000 loopback on
ip link set can0 up
Then using cansend to send messages:
Send and receive successfully, and we can see the signal both in rx/tx of the soc and the can0_h and can0_l of the transceiver(TJA1048t) using oscilloscope.
But when using the normal mode: ip link set can0 type can bitrate 100000, of course we make sure that loopback if off, there are no signal in the tx and rx.
Can anyone tell me where is the problem?
Part Number: AM5728
Tool/software: TI-RTOS
Hi
I want to use the single spi bus in am5728 which has four chip selects, how can i use two devices on same single bus.
what changes do i need to change in default settings of spi, to use the same bus for two different devices.
thanks
Mr
Part Number: TMS320C6678
Tool/software: TI C/C++ Compiler
Hi there,
My main.c includes a header utils.h and in utils.c I have the following:
I defined global constants like
const int var_1 = 1;
and each core prints them. What they print is not what is defined above, e.g. var_1 is not equal to 1. What do I need to do s.t. when core1 prints var_1 I get 1? My guess was that some things with initialization go wrong? All data is placed in shared memory.
What I tried:
1.) Place them in a custom section (.shared_section > MSMCSRAM in lnk.cmd):
#pragma DATA_SECTION (var_1, ".shared_section")
const int var_1 = 1;
Variables are placed in the right section, still the output is !=1
2.) I added shared_section: load >> MSMCSRAM to lnk.cmd but no change
(In the end, I would like to place these vars in the section .shared_section.)
Thank you very much for your help.
Part Number: AM5728
Tool/software: Linux
Hello
Our Video circuit :
Component Video => ADV7403 => AM5728 (vin3a of VIP2)
We have configure ADV7403 to YUV 16 bit ( YVYU).
Based on media-bus-format.h (/include/uapi/linux/media-bus-format.h) and videodev2.h (/include/uapi/linux/videodev2.h) we should use :
MEDIA_BUS_FMT_YVYU8_1X16 and V4L2_PIX_FMT_YVYU for our configuration.
But in /driver/media/platform/ti-vpe/vip.c we see this in line 248 : /* V4L2 currently only defines one 16 bit variant */
which is for RAW16, not YVYU16.
Questions :
1_ Does V4L2 and VIP supports 16 bit YVYU or not? how we can add this input format ?
2_ Where we should set input format in media decoder chip driver (please you explain it based on ADV7180 driver)
3_ Should the video input format be set to decoder IC driver only or need changes in vip.c, vpe.c, ...?
Best Regards.
Part Number: AM3352
Hello,
customer uses the NMI pin to generate an interrupt. The puls length on the pin is very short (30ns) right now. So it works not always. What is the minimum time for the pin that always an interrupt will be generated? (There is no info in the datasheet!).
Regards, Holger
Part Number: PROCESSOR-SDK-AM65X
Tool/software: TI C/C++ Compiler
Hi all,
I am attempting to create and setup the CAN-ETH gateway example project in CCS. To do this I simply create a project for the R5 core, import the source and build configuration files from "C:\ti\processor_sdk_rtos_am65xx_5_03_00_07\demos\gateway-demos\can-eth-gateway\build" and try to setup up the correct paths and directories from there. I am using the following version:
- CCS v9.1.0.00010
- Processor SDK RTOS for AM65xx v5.03.00.07
- Compiler: TI v18.1.5.LTS
- XDC Tools: v 3.55.2.22
- The archive file of my project can be found here to reproduce my error: (Please visit the site to view this file)
I obviously expect a lot of errors during during this process, but would greatly apprecaite some assistance. This project requires Posix support for the socketndk.h file to work correctly, however when I try to build my project, I get the following error from the socketndk.h file:
- cannot open source file "sys/time.h"
I find this strange, as the include directory for this file is specified via the ${xdc_find:ti/posix/ccs:${ProjName}} path:
It seems to be detected correctly at the includes files as well:
It is thus expected that the TI Posix "time.h" file should be linked to the project successfully. I managed to fix this error by defning my own Path Variable to the directory "C:\ti\bios_6_75_02_00\packages\ti\posix\ccs\sys", and edited the code in the socketndk.h file to "#include <time.h>" instead of "#include <sys/time.h>. Is there a beter solution to this that does not require me to edit the NDK header file? I refer to the following thread as well: https://e2e.ti.com/support/tools/ccs/f/81/t/740620
Please let me know if any other information is required.
I look forward to hearing from you.
Regards,
Johnny
Part Number: PROCESSOR-SDK-AM335X
Tool/software: Linux
Customer had a problem to setup AM335x into USB2 OTG mode so I recommended to check out this patch e2e.ti.com/.../2779439 but it didn't help.
So it is probably an issue of a proper LINUX Kernel setup. Can you provide an example?
Regards, Bernd
Part Number: TMS320C6748
Tool/software: Code Composer Studio
Hi,
I am using TMS320C6748Processor and code based on the OMAP_L138-NOR Writer for loading bin file into NOR_FLASH on the chip. I am unable to flash a .bin file to the chip due to the CFI query failing and NOR failing to initialize because of it. I am unsure if this is a hardware or software error and would like some guidance. I am not sure what I should be seeing in the debug window to diagnose the issue.
Thanks
Part Number: TDA3MV
Tool/software: TI-RTOS
We are supposed to obtain the TDA4X and work on VPAC topic.
Several questions arise after going through some of TI’s documentation:
1) Which cameras were ported, tested & tuned with AE\AWB for TDA4x platform? Will we get a sample of it while receiving the EVM? I noticed in the source code that the camera sensors: AR0140 & OV10640 are mentioned..
2) Did TI test those cameras with both SBL and CCS?
3) Beside the documentations on CDDS portal, do you have any documentation elaborating a bit more on the best practice of H3A AE\AWB engine configuration such as:
- Advantage & disadvantage of min\max, sum of square, sum-only modes?
- adjusting the windows parameters?
- Etc.
Thanks in advance,
Rotem Bernstein
Part Number: OMAP-L137
Hi Champs,
We have some question of OMAPL137 thermal behaver.
1: Our customer is using now OMAPL137DZKB4.
The temperature type is Tj is 0-90. If our operation temp is over 90 degree, what kind of issue happen ?
Does this occur reliability issue ?
Part Number: EVMK2H
A newly purchased EVMK2HX board reports "SOC POWER FAILURE" on every boot. This intuitively appears to be a board fault, but there is mention of "SOC Power Fail" in the EVMK2HX_Rev1_1_known_Issues.pdf file. We downloaded python version 2.7.13, pyserial 2.6 (since they were recommended ), and the latest version of the UCD files. Using the provided "bmc_tool.py", the get version returned 3 blank lines, and the update returned an error related to an i2c command. During the failed boot sequence, the board reports that BMC firmware 1.0.2.6 version is loaded. We did not download the FTDI USB driver since there was already a USB driver in our version of windows (Windows 10 Enterprise).
- The "SOC POWER FAILURE" message occurs every time. How can we tell if this is a hardware fault (or something correctable via sw or fw load)?
- Is the FTDI driver required? (Getting IT permission to load 3rd party drivers just to try it is very time consuming and impractical from a debugging perspective.)
Part Number: AM5728
Tool/software: Linux
Hello,
Could you tell me the way to set the HDMI on AM5728 outputting full-range of color?
In the following site, HDMI output is 24-bit RGB, thus it's RGB888.
software-dl.ti.com/.../Foundational_Components_Kernel_Drivers.html
However, the output color range seems to be limited from 16 to 235 (i.e. limited range).
I want to know the way to change the range to full range (0 to 255).
Processor SDK Linux is used.
Best Regards,
Nomo
Part Number: AM5708
Tool/software: Linux
psdk build error:
[root@zengjia_vivado:build#] MACHINE=am57xx-evm bitbake arago-base-tisdk-image
Loading cache: 100% |#########################################################################################################################################################################| Time: 0:00:01
Loaded 3236 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "arm-linux-gnueabi"
MACHINE = "am57xx-evm"
DISTRO = "arago"
DISTRO_VERSION = "2017.05"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta-processor-sdk = "HEAD:3d2f620a6a98b1b6abb1103d7dc986921436ed19"
meta-arago-distro
meta-arago-extras = "HEAD:b727bf8fce8e9cb5a6b5d5b48c45f0088e67eb53"
meta-browser = "HEAD:880a7bd1d3b9a1b2003f5b0620350f03158bbd43"
meta-qt5 = "HEAD:3601fd2c5306ac6d5d0d536e0be8cbb90da9b4c1"
meta-networking
meta-ruby
meta-python
meta-oe
meta-gnome = "HEAD:fe5c83312de11e80b85680ef237f8acb04b4b26e"
meta-ti = "HEAD:41d6fdc0fe5ea6054616cfccda13baac3ff33791"
meta-linaro-toolchain
meta-optee = "HEAD:d84874bad834657dd04ea69c35a74dd9dbd535b8"
meta = "HEAD:ddf907ca95a19f54785079b4396935273b3747f6"
Initialising tasks: 100% |####################################################################################################################################################################| Time: 0:00:06
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: fontconfig-2.12.1-r0 do_compile: oe_runmake failed
ERROR: fontconfig-2.12.1-r0 do_compile: Function failed: do_compile (log file is located at /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/temp/log.do_compile.48917)
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/temp/log.do_compile.48917
Log data follows:
| DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
| DEBUG: Executing shell function do_compile
| NOTE: make -j 6
| ERROR: oe_runmake failed
| make all-recursive
| make[1]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build'
| Making all in fontconfig
| make[2]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fontconfig'
| make[2]: Nothing to be done for `all'.
| make[2]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fontconfig'
| Making all in fc-blanks
| make[2]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-blanks'
| make[2]: Nothing to be done for `all'.
| make[2]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-blanks'
| Making all in fc-case
| make[2]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-case'
| make all-am
| make[3]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-case'
| make[3]: Nothing to be done for `all-am'.
| make[3]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-case'
| make[2]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-case'
| Making all in fc-lang
| make[2]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-lang'
| make all-am
| make[3]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-lang'
| make[3]: Nothing to be done for `all-am'.
| make[3]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-lang'
| make[2]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-lang'
| Making all in fc-glyphname
| make[2]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-glyphname'
| make all-am
| make[3]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-glyphname'
| make[3]: Nothing to be done for `all-am'.
| make[3]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-glyphname'
| make[2]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/fc-glyphname'
| Making all in src
| make[2]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/src'
| make all-am
| make[3]: Entering directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/src'
| ../arm-linux-gnueabi-libtool --tag=CC --mode=compile arm-linux-gnueabihf-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard --sysroot=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm -DHAVE_CONFIG_H -I. -I../../fontconfig-2.12.1/src -I.. -I../../fontconfig-2.12.1 -I../../fontconfig-2.12.1/src -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/usr/include/freetype2 -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -DFC_CACHEDIR='"/var/cache/fontconfig"' -DFONTCONFIG_PATH='"/etc/fonts"' -isystem/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include -isystem/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0=/usr/src/debug/fontconfig/2.12.1-r0 -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux= -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm= -pthread -c -o fcmatch.lo ../../fontconfig-2.12.1/src/fcmatch.c
| arm-linux-gnueabi-libtool: compile: arm-linux-gnueabihf-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard --sysroot=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm -DHAVE_CONFIG_H -I. -I../../fontconfig-2.12.1/src -I.. -I../../fontconfig-2.12.1 -I../../fontconfig-2.12.1/src -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/usr/include/freetype2 -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -DFC_CACHEDIR=\"/var/cache/fontconfig\" -DFONTCONFIG_PATH=\"/etc/fonts\" -isystem/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include -isystem/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0=/usr/src/debug/fontconfig/2.12.1-r0 -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux= -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm= -pthread -c ../../fontconfig-2.12.1/src/fcmatch.c -fPIC -DPIC -o .libs/fcmatch.o
| ../../fontconfig-2.12.1/src/fcmatch.c:324:63: error: ‘PRI_CHAR_WIDTH_STRONG’ undeclared here (not in a function); did you mean ‘PRI_WIDTH_STRONG’?
| #define FC_OBJECT(NAME, Type, Cmp) { FC_##NAME##_OBJECT, Cmp, PRI_##NAME##_STRONG, PRI_##NAME##_WEAK },
| ^
| ../../fontconfig-2.12.1/src/fcobjs.h:54:1: note: in expansion of macro ‘FC_OBJECT’
| FC_OBJECT (CHAR_WIDTH, FcTypeInteger, NULL)
| ^~~~~~~~~
| ../../fontconfig-2.12.1/src/fcmatch.c:324:84: error: ‘PRI_CHAR_WIDTH_WEAK’ undeclared here (not in a function); did you mean ‘PRI_WIDTH_WEAK’?
| #define FC_OBJECT(NAME, Type, Cmp) { FC_##NAME##_OBJECT, Cmp, PRI_##NAME##_STRONG, PRI_##NAME##_WEAK },
| ^
| ../../fontconfig-2.12.1/src/fcobjs.h:54:1: note: in expansion of macro ‘FC_OBJECT’
| FC_OBJECT (CHAR_WIDTH, FcTypeInteger, NULL)
| ^~~~~~~~~
| make[3]: *** [fcmatch.lo] Error 1
| make[3]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/src'
| make[2]: *** [all] Error 2
| make[2]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build/src'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/build'
| make: *** [all] Error 2
| WARNING: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/temp/run.do_compile.48917:1 exit 1 from 'exit 1'
| ERROR: Function failed: do_compile (log file is located at /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/fontconfig/2.12.1-r0/temp/log.do_compile.48917)
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-graphics/fontconfig/fontconfig_2.12.1.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1201 tasks of which 1193 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/root/psdk/tisdk/sources/oe-core/meta/recipes-graphics/fontconfig/fontconfig_2.12.1.bb:do_compile
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
[root@zengjia_vivado:build#]
Part Number: 66AK2H14
Hello, I'm looking for some example code to use the SPI interface. Where is the best place to look?
I'm also looking for a delay routine that uses a timer.
Thank you,
Joe
Part Number: TDA2P-ACD
Tool/software: TI-RTOS
i compile the MAKECONFIG = tda2px_evm_bios_all , and let UC_iss_monochrome_capt_isp_display=yes in uc_cfg.mk . i met the error as follow.
where i can find the file chains_common_iss.h ?? thanks
"/home/gq/PROCESSOR_SDK_VISION_03_07_00_00/vision_sdk/apps/src/rtos/usecases/iss_monochrome_capt_isp_display/chains_monochrome_issIsp_Display.c", line 68: fatal error: cannot open source file "src/include/chains_common_iss.h"
1 catastrophic error detected in the compilation of "/home/gq/PROCESSOR_SDK_VISION_03_07_00_00/vision_sdk/apps/src/rtos/usecases/iss_monochrome_capt_isp_display/chains_monochrome_issIsp_Display.c".
Compilation terminate
Tool/software: Linux
I have a custom board of which cpu is AM3354.It doesn't have EEPROM and RTC. I disabled the RTC and EEPROM detected related module during u-boot and now u-boot is able to boot. But the kernel is hanging after print "Uncompressing Linux... done, booting the kernel." After a while, the cpu automatically reset.
I used the printascii and located the error happened in __turn_mmu_on:
mcr p15, 0, r0, c1, c0, 0 @ write control reg
mrc p15, 0, r3, c0, c0, 0 @ read id reg
instr_sync
What should I do to solve the problem?
In addition, if I don't have an RTC chip, should RTC_PWRONRSTn be pulled low?
I would be grateful if I could get a reply as soon as possible.Thank you!
Part Number: AM3352
Tool/software: TI-RTOS
I have a customized AM3352 board, it is almost same to beagleboard-black.
A SD card slot is soldered at MMC0, an eMMC chip is attached at MMC1.
The board is running with TIRTOS, built upon pdk 'pdk_am335x_1_0_14'.
After code modification (pinmux) were made to pdk, the eMMC (on MMC1 port) FAT partitions can be successfully mount and written.
But the write operation not stable, it randomly return with error,.
While continuously write to eMMC partition file (according to fatfs f_write), a random FR_DISK_ERR may return and then filesystem get stuck.
Despite the fatfs, I built a test uppon ''MMCSD_evmAM335x_armTestProject" by directly writing eMMC with 'MMCSD_write'. It also return a MMCSD_ERR at some random place.
Sometimes, 1GBytes were successfully written before the write error, sometimes it only has 60MBytes written.
By tracking down the code of pdk, in call stack 'MMCSD_v1_write -> MMCSD_v1_transfer', a SD_STAT(bit CTO) is captured after CMD25 was sent.
The timeout is the point.
By modifying the write blockCount, it has different behavors:
1) Each time write 16 blocks (or less, 16*512 = 8KB), the timeout comes soon. Within 1GB were written, there is must a timeout.
2) Each time write 2048 Blocks (2048*512 =1MB), the timeout comes later. After several loops of test done and several GB were written, the timeout raised.
The timeout didn't happen at the fix block or a fix time, it always comes randomly.
We tried to run Linux on the same board, everything goes fine.
The eMMC partitions were written to full and then clear, the test ran several loops, without any error captured.
Part Number: AM5718
Tool/software: TI-RTOS
Hi experts,
Do you have any documentation which is released by TI for TI RTOS technical support polocy?
Please kindly check whether TI release it.
Best Regards,
Jay.