Part Number:TMS320C6713B
Tool/software: Code Composer Studio
Dear,
We have difficulties to find dynamic memories available for this DSP.
Memory MT48LC32M16A2P75ITC is not available (obsolete) now.
Could you inform me if another memory with the same pinout and capacity exist?
Thank you
Regards
Part Number:AM4372
Tool/software: TI-RTOS
Hi :
We use the JTAG through CCS 8.2 or the Uniflash CLI tool, by flashing the attached image, the CCS / CLI will give us this:
CortexA9: File Loader: Verification failed: Values at address 0x30000000 do not match Please verify target memory and memory map.
CortexA9: GEL: File: C:\TI\pdk_am437x_1_0_13\packages\ti\starterware\binary\bootloader\bin\am43xx-evm\gcc\bootloader_boot_qspi_a9host_debug.out: a data verification error occurred, file load failed.
Can you review the attached .out / .map file (in the zip file) (Please visit the site to view this file)to guide us how to solve?
Customer is using QSPI NOR Flash.
BR Rio
Part Number:AM5728
Tool/software: TI-RTOS
Hi,
I'm currently trying to enable promiscuous mode on the DSP Ethernet MAC driver. I found some documentation, but it doens't seem to be that up to date. In the document "EthernetMediaAccessController(EMAC)/ManagementDataInput/Output(MDIO)Module" in section "2.10.8PromiscuousReceiveMode" there is some mention to set the RXCAFEN, RXCEFEN, RXCMFEN and RXCSFEN to 1, but I can't fine the according defines in driver version 4.
Additionally I tried to activate it by setting rx_filter to EMAC_PKTFLT_ALL for the emac_config() call, just to realise that this is the implementation:
static EMAC_DRV_ERR_E EMAC_config_v4(uint32_t port_num, EMAC_CONFIG_INFO_T *p_config)
{
return EMAC_DRV_RESULT_OK;
}
I would be grateful if someone could tell me how to enable promiscuous mode on the EMAC Driver v4.
Part Number:AM5728
Tool/software: TI-RTOS
I used Timer to creat a task to get a image, then upload the image. And there is a strange problem. After more than 200 Timer interrupts, the program crashed. The exception information is following:
meoutRexmt: Retransmit Timeout 00220.203 TcpTimeoutRexmt: Retransmit Timeout 00223.300 TcpTimeoutRexmt: Retransmit Timeout 00229.300 TcpTimeoutRexmt: Retransmit Timeout 00232.300 TcpTimeoutRexmt: Retransmit Timeout 00234.300 TcpTimeoutRexmt: Retransmit Timeout 00235.300 TcpTimeoutRexmt: Retransmit Timeout 00321.977 TcpTimeoutRexmt: Retransmit Timeout 00333.303 TcpTimeoutRexmt: Retransmit Timeout Exception occurred in ThreadType_Hwi. Hwi handle: 0x0. Hwi stack base: 0xa0200000. Hwi stack size: 0x400000. R0 = 0x2800015f R8 = 0x00004000 R1 = 0x900a3158 R9 = 0x00000001 R2 = 0x8f51a350 R10 = 0x00000004 R3 = 0x00000001 R11 = 0xa05fff64 R4 = 0x8f3c3d1c R12 = 0x00000001 R5 = 0x900a3158 SP(R13) = 0xa05fff20 R6 = 0x00000001 LR(R14) = 0x8f2af278 R7 = 0x6800015f PC(R15) = 0x8f2ad28c PSR = 0x680001df DFSR = 0x00000205 IFSR = 0x00000000 DFAR = 0x28000163 IFAR = 0x00000000 ti.sysbios.family.arm.exc.Exception: line 205: E_dataAbort: pc = 0x8f2ad28c, lr = 0x8f2af278. xdc.runtime.Error.raise: terminating execution
Can you give me some advise?
Part Number:AM3352
Hi
Could it be possible to change port configuration after AM3352 powered up?
For examle, it assumes that M16, L15, L16 and L17 ofAM3352 is configured as GPIO when powering up.
After GPIO operation, we want to make these port change to RGMII_RXD port.
1.
Could it be possible to change the port configuartion during operation dynamically?
2.
If it is possible, could you please tell us recommended software flow? EMAC init required?
BestRegards
Part Number:AM5728
Hi,
I have a question about AM5728 DDR3 I/F .
My customer are going to use only DDR1 and doesn't use DDR2.
I understood that vdds_ddr2 need to be connected to the power supply.
In this case, are bypass capacitors also need to be used on this power line?
If yes, how many and what is the total capacitance?
Should they follow the "Table 8-8 Bulk Bypass Capacitors" in AM5728 datasheet(sprs953e)page.383?
best regards,
g.f.
Part Number:AM5728
Tool/software: Linux
Hi,
I am using ov10635 camera in AM5728 Evk board with the linux SDK version 5.02. I created the SD card using the default images.
I run the create-sdcard.sh file and choose the option 1 for the rootfs.
################################################################################
Multiple rootfs Tarballs found
################################################################################
1:tisdk-server-extra-rootfs-image-k2g-evm.tar.gz
2:tisdk-server-rootfs-image-k2g-evm.tar.gz
Enter Number of rootfs Tarball:It created the SD card successfully. when i boot the AM5728 evk borad with the created SD card It does not have any User interface on and camera application(like gstreamer, v4l2-ctl, Yavta etc).
1.Is this the default behavior or am i miss anything?
Then I have made the entry in uEnv.txt file for using the camera supported dtb am57xx-evm-reva3-cam-ov10635.dtb file, now i can able to get the frames from the camera using the V4L2 based application but the image is full of green color. please help us to solve this issue.
Part Number:AM3354
Tool/software: Linux
Hi everyonoe,
I'm working on a custom AM3354 based board, with a LP55231 LED driver and I want to turn on a LED in U-boot and let it on until the Kernel has finished booting and the product is ready to use.
I managed to turn on the LED in U-boot, but I noticed that the LED_EN GPIO goes to 0 for a short time during the handover between U-Boot and the Kernel, thus restting the LP55231 and turning off the LED.
Is there a way to prevent this?
In both U-Boot and Kernel dts file, the GPIO is configured as:
/* LED Driver Enable */
0x6c (MUX_MODE7 | PIN_OUTPUT_PULLUP) /* gpmc_a11.gpio1_27 */
And the pin has an external pull_down as well.
Should we remove the exrternal pull down? If we do that the pin will be floating so I'm not sure that it will stay high anyway.
Is there a way for the GPIO to keep the internal pull-up before the kernel loads the device tree?
Thanks,
Antoine
Hi E2E,
Our Customer transport data/clock signal of SIM card. (the spec is 5MHz), because the trace is too long, they worry the signal will be attenuated.
Could you promote the redriver or buffer to support it?
Part Number:AM5728
Team,
-Are you aware of any IEEE 1588v2 implementation running on the C66x (via the NDK stack) and using the GMAC_SW (not the PRU-ICSS) ?
Are there any Third party offering it?
Is it a use case that we directly support?
-We do provide the pre-build NDK 3.40 in RTOS SDK 5.02.
As it been validated as well for the C66x?
Is there a way to access the NDK 3.40 docs directly without to have to install the complete RTOS SDK?
I can only find high level NDK docs on the SDK page:
http://software-dl.ti.com/processor-sdk-rtos/esd/docs/05_02_00_10/rtos/index_Foundational_Components.html#ndkBut not the details like it use to be provided. For example for NDK 2.25 we know exactly what was tested:
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ndk/2_25_01_11/exports/ndk_2_25_01_11/ndk_2_25_01_11_release_notes.html#Validation
Thanks in advance,
A.
Part Number:DRA75
Tool/software: Linux
Hi All,
We are using J6 and Vision SDK 3.04
IPU1 firmware is getting loaded by bootloader and it is verified.
We have integrated Following Early boot and Late attach patches to the Kernel
ti_components/os_tools/linux/kernel/linux-kernel-addon$ ls -l earlyboot-kernel-patches/
0001-dra7xx-Kernel-Optimizations-for-early-use-case-enabl.patch
0002-arm-mach-omap2-Remove-edma-related-nodes-from-hwmod-.patch
0003-arm-dts-infoadas-Late-attach-remoteprocs.patch
0004-config_fragments-Make-remoteproc-built-in-enable-use.patch
0005-arm-dts-Disable-DSS-PRCM-for-M4-display.patch
and verifying the late attach functionality at kernel side. dmesg reports that ipu1 will be late-attached
dmesg | grep lat-attach
map-rproc 58820000.ipu: device will be late-attached
We would like to know how we can confirm that late attach functionality is working fine. We are following this page: http://processors.wiki.ti.com/index.php/Early_Boot_and_Late_Attach_in_Linux and this suggest to look in to trace0
root@dra7xx-evm:~# cat /sys/kernel/debug/remoteproc/remoteproc0/trace0 [0][ 0.000] Watchdog enabled: TimerBase = 0x68824000 SMP-Core = 0 Freq = 19200000 [0][ 0.000] Watchdog enabled: TimerBase = 0x68826000 SMP-Core = 1 Freq = 19200000 [0][ 0.000] Watchdog_restore registered as a resume callback [0][ 0.000] 18 Resource entries at 0x3000 [0][ 0.000] messageq_single.c:main: MultiProc id = 2 [0][ 0.000] Time at reset() is 51615 ticks [0][ 0.000] Time at startup() is 51726 ticks [0][ 0.000] Time at main() is 51804 ticks [0][ 0.000] registering rpmsg-proto:rpmsg-proto service on 61 with HOST [0][ 0.000] tsk1Fxn: created MessageQ: SLAVE_IPU1; QueueID: 0x20080 [0][ 0.000] Awaiting sync message from host...
But we are not able to see the trace0 entry after integrating these patches.
root@mmt2020-a880:~# ls -l /sys/kernel/debug/remoteproc/remoteproc0/
-r-------- 1 root root 0 Jan 1 00:00 name
-r-------- 1 root root 0 Jan 1 00:00 recovery
-r-------- 1 root root 0 Jan 1 00:00 state
-r-------- 1 root root 0 Jan 1 00:00 version
and state indicate offline
cat /sys/kernel/debug/remoteproc/remoteproc0/state
offline
In normal (no early boot and late attach) case trace0 is available for IPU1
Can you please let us know how we can verify late- attach feature. Any Kernel changes needs to be done to enable trace0 ?
Any help will be appreciated.
Thanks
Sreeju
Part Number:TMS320C6747
what is the voltage and current of DVDD PINs
Part Number:AM5708
Tool/software: Linux
Hi,
I'm using kernel 4.14.79.
Apart from the problem I'm facing in previous thread,
I'm also facing crash for mmc0 in SDHCI omap driver.
We have SD card on mmc0 and EMMC on mmc1. Whenever I boot using EMMC and SD card is not connected, I face these crash logs after random time since boot.
[ 776.975999] ------------[ cut here ]------------ [ 776.980755] WARNING: CPU: 0 PID: 64 at drivers/mmc/host/sdhci-omap.c:742 sdhci_omap_init_74_clocks+0xb0/0x114 [ 776.990999] Modules linked in: bc_example(O) omapdrm drm_kms_helper cfbfillrect syscopyarea cfbimgblt sysfillrect sysimgblt fb_sys_fops cfbcopyareac [ 777.046558] CPU: 0 PID: 64 Comm: kworker/0:3 Tainted: G O 4.14.79.18.0_Edge_Kernel+ #1 [ 777.055645] Hardware name: Generic DRA72X (Flattened Device Tree) [ 777.061773] Workqueue: events_freezable mmc_rescan [ 777.066588] Backtrace: [ 777.069054] [<c010b4c4>] (dump_backtrace) from [<c010b794>] (show_stack+0x18/0x1c) [ 777.076659] r7:00000009 r6:60010013 r5:00000000 r4:c0d5e9d4 [ 777.082349] [<c010b77c>] (show_stack) from [<c0892570>] (dump_stack+0x8c/0xa0) [ 777.089607] [<c08924e4>] (dump_stack) from [<c012b034>] (__warn+0xec/0x104) [ 777.096600] r7:00000009 r6:c0b16618 r5:00000000 r4:00000000 [ 777.102285] [<c012af48>] (__warn) from [<c012b104>] (warn_slowpath_null+0x28/0x30) [ 777.109888] r9:00000000 r8:c09664f8 r7:000000b4 r6:e7150af9 r5:d3f64380 r4:00000000 [ 777.117669] [<c012b0dc>] (warn_slowpath_null) from [<c0676e58>] (sdhci_omap_init_74_clocks+0xb0/0x114) [ 777.127019] [<c0676da8>] (sdhci_omap_init_74_clocks) from [<c066ec34>] (sdhci_set_ios+0xd4/0x3dc) [ 777.135929] r7:d3f64000 r6:d3f64380 r5:d3f64210 r4:d3f64000 [ 777.141615] [<c066eb60>] (sdhci_set_ios) from [<c0675f34>] (sdhci_omap_set_ios+0xd8/0x10c) [ 777.149916] r9:00000000 r8:c09664f8 r7:00000000 r6:00000000 r5:d3f64210 r4:d3f64000 [ 777.157695] [<c0675e5c>] (sdhci_omap_set_ios) from [<c06589d8>] (mmc_power_up.part.7+0xf4/0x100) [ 777.166520] r9:00000000 r8:c09664f8 r7:00000000 r6:00000001 r5:d3f64210 r4:d3f64000 [ 777.174299] [<c06588e4>] (mmc_power_up.part.7) from [<c0659840>] (mmc_rescan+0x274/0x3f4) [ 777.182512] r7:c09664f0 r6:d3f64000 r5:000493e0 r4:d3f6426c [ 777.188201] [<c06595cc>] (mmc_rescan) from [<c0141e50>] (process_one_work+0x128/0x410) [ 777.196152] r9:00000000 r8:df8cff00 r7:00000000 r6:df8ccb40 r5:d3f74900 r4:d3f6426c [ 777.203933] [<c0141d28>] (process_one_work) from [<c0142190>] (worker_thread+0x58/0x5a0) [ 777.212059] r10:d3f8c000 r9:df8ccb58 r8:c0d02d00 r7:00000008 r6:d3f74918 r5:df8ccb40 [ 777.219920] r4:d3f74900 [ 777.222469] [<c0142138>] (worker_thread) from [<c0147d94>] (kthread+0x138/0x168) [ 777.229897] r10:df473e80 r9:d3f7681c r8:d3f74900 r7:d3f8c000 r6:d3f767c0 r5:00000000 [ 777.237759] r4:d3f76800 [ 777.240306] [<c0147c5c>] (kthread) from [<c0107cf8>] (ret_from_fork+0x14/0x3c) [ 777.247559] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0147c5c [ 777.255421] r4:d3f767c0 [ 777.260798] ---[ end trace e867a9a40e97f5c6 ]--- [ 787.680728] mmc0: Timeout waiting for hardware cmd interrupt. [ 787.686506] mmc0: sdhci: ============ SDHCI REGISTER DUMP =========== [ 787.692976] mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x00003302 [ 787.699444] mmc0: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000 [ 787.705911] mmc0: sdhci: Argument: 0x00000c00 | Trn mode: 0x00000000 [ 787.712378] mmc0: sdhci: Present: 0x00000001 | Host ctl: 0x00000000 [ 787.718844] mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000000 [ 787.725310] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x0000a007 [ 787.731776] mmc0: sdhci: Timeout: 0x00000000 | Int stat: 0x00018001 [ 787.738242] mmc0: sdhci: Int enab: 0x007f0003 | Sig enab: 0x007f0003 [ 787.744708] mmc0: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000001 [ 787.751174] mmc0: sdhci: Caps: 0x25e90080 | Caps_1: 0x00000f77 [ 787.757639] mmc0: sdhci: Cmd: 0x0000341a | Max curr: 0x00000000 [ 787.764106] mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000 [ 787.770572] mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000 [ 787.777037] mmc0: sdhci: Host ctl2: 0x00000000 [ 787.781497] mmc0: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x00000000
And these logs keeps coming untill I restart the board.
How can I fix this problem?
Thanks,
Gunjal
Part Number:AM4376
Tool/software: Linux
Hi All,
We used AM4376 with TI Linux SDK.
We successfully silent the u-boot / kernel messages by enabling silent console option in u-boot and defining silent=1.
We successfully login using telnet on board.
Our application start as systemd service in order to start at boot time.
We define service as follow:
[Unit]
Description=Initmyapplication
[Service]
ExecStart=/usr/bin/myapplication &
Our application have some debug messages implemented using printf.
After completing login process using telnet those printf are not visible on telnet.
After killing application by kill -9 myapplication command and starting application by executing command /usr/bin/myapplication & debug printf are visible.
I have following question
1. How to get those printf when AM4376 start after power on and available on console when we login through telnet?
2. If we start our service after telnet service then those printf are available on console when we login using telnet ?
3. If yes how to do that? What should be the value of 'After' need to define systemd service?
4. Is there any other way to print debug printf output when we login using telnet?
Please guide me to solve the issue.
Regards,
Dhananjay Patil
Part Number:OMAP-L138
Hi,
Iam using OMAPL138 for our project .In that I want to use SPIREVT for DMA enable for SPI.Since Iam only using SPI Rx (Here OMAP is SPI Slave)But I could not able to see any register which contains SPIREVT.
Can any one tell me how to use/config that particular event in software.
Thanks in advance
Regards,
Satheesh
Part Number:AM5718
Tool/software: TI-RTOS
We have a custom board that is equipped with a
SD card
eMMC (NAND flash) 16GB
NOR Flash 512 Mb (64Mx8)
USB
The normal boot order will most likely be USB->SD->eMMC
Our ambition is to have it this way
First an RTOS based program (hereafter “RTOS program”) is executed (on the A15) to perform various tests of peripherals, such as RTC, EEPROM, DDR3 (this mean it must be executed in OCMC ram internal in the SoC) this program will then start a Linux kernel.
This RTOS program also do Board_Init to set up the custom board we have.
Is there a way to concatenate an RTOS program with the linux core and in the RTOS program to call some magic function call, to start the Linux core?
Like RTOS_Start_Bundled_LinuxCore().
http://processors.wiki.ti.com/images/b/b7/TDA_SBL_UserGuide.pdf
Only deals with how to create a bootable image, we assume, either for only a RTOS or a Linux image.
(on page 11 the path given, packages/ti/boot/sbl_auto dont exist, we assume it should be packages/ti/boot/sbl)
Or should the RTOS program be placed in the NOR flash?
If SYSBOOT instruct the RBL to boot from QSPI to start the RTOS program and when it is finished the RTOS program calls a function in RBL and tell it to boot from eMMC ?
In this way we can build an image for NOR flash for the RTOS and a eMMC image for the linux kernal ?
The beauty with this is that the RTOS and Linux is in no ways depending on each other and via SYSBOOT we can skip the execution of the RTOS program.
Regards
Part Number:OMAP-L138
Dears:
there is issue need your suggestions:
The system is FPGA adds OMAPL138, now customer wants to download program to FPGA by OMAPL138.
But customer uses GPIO to connect them, and not uses the function of UPP.
I want to know whether is the speed of using GPIO downloads the program(about 4MB) slower than using UPP? How can I get the download time？
Part Number:PROCESSOR-SDK-AM57X
Tool/software: TI-RTOS
Hello,
I'm using AM572x IDK board with TI-RTOS SDK 05.01.00.11.
I debugged my fatfs application that working with an onboard eMMC0 chip (MMC2 processor slot).
When I'm debugging it, I see, that MMCSD_iodelayFxn() function must select configured MMC mode. It almost correct selects the mmcMode variable value (what about DDR mode select with Pad loopback?). Then it calls BoardMmcCtrlPadConfig() function with that instance number (2 for MMC2 processor slot). OK, that's good.
In BoardMmcCtrlPadConfig() function: it calls BoardGetMmcCtrlPadPinmuxTable() function with non-changed instance argument (value 2 for MMC2 processor slot).
But function BoardGetMmcCtrlPadPinmuxTable() was defined by the pinmux tool and returns configuration modes for MMC3 chip (because of C language has array indexing from 0).
That's why boardGetPinmuxCfg() cannot find required config and skip if(ctrlPadCfg != NULL) body. But when I fixed indexing issue (I passed decremented instance number in BoardGetMmcCtrlPadPinmuxTable() function), rebuilt PDK and project.
But a project cannot config required speed config (default from your pinmux file for the board) and crashes with Data abort exception while returns from BoardCtrlPadIoDelayConfig()function (in my project).
I start only A15_0 core on the processor (without SMP mode).
How should I fix that bug? I need to speed up the eMMC interface.
Also, what about DDR mode select of MMC2 with Pad loopback config?
With regards,
Alex
Part Number:TDA2PXEVM
Tool/software: TI-RTOS
Hi All,
I went through a training slide training.ti.com/am57x-dra7x-dfu-boot-mode-with-linux-host for flashing images using DFU utility.We have the following queries regarding flashing of images:
1)As per our current project requirement, we need to flash TI's Vision SDK images MLO and Appimage through DFU utility.
Is this feasible?If this is feasible can anyone let me know what changes will be required in omapboot utility.
2)Can we flash QSPI using SD Card interface.With this there is also a requirement to change the memory map of QSPI as we need more than one partition in QSPI to keep the redundant images and some config parameters.
Can anyone please help me regarding the above queries?
Regards,
Deepika