Part Number:TMS320C6748
Tool/software: TI C/C++ Compiler
Starting of C6000-CGT 8.3 compiler time of project compilation has dramatically increased up to 5 minutes. There were no optimizations set up. What a reason might cause such delays in the compilation?
Part Number:AM3358
Tool/software: Linux
When the system is started, the display always displays Please wait...
I have connected a USB mouse, then it shows normal. But it's impossible for our board to connect the mouse all the time.
So I have also tried to add require-input=false option to [core] section in /etc/weston.ini file, but it proved to be ineffective.
# cat /etc/weston.ini
[core]
require-input=false
[shell]
locking=false
animation=zoom
panel-location=top
startup-animation=fade
[screensaver]
# Uncomment path to disable screensaver
#path=@libexecdir@/weston-screensaver
How to display normally without mouse.
My SDK version is 03.01.00.06
could you please provide Linux driver source code which supports both HSR and PRP.
This driver has mentioned in section 4.2.3.3.1 in below link
Tool/software: Linux
Hi.
I'm trying to run multiple channel on nullSoure on nullSrc-decode-display usecase.
I'm modified "nullSrc_tsk.c" to process with multiple input.
But, On Usecase running, different channel data is mixed and display.
Plz. Check out my video.
(Please visit the site to view this video)
I think that in the ProcessData function, data from each channel is mixed into the pBuffer, which is then forwarded to the next link.
how can i fix this problem?
help me.
Regards,
Lee.
Part Number:PROCESSOR-SDK-TDAX
Hello,
I currently try communicate with a different processor over mcspi. I'm using the provided bsp mcspi driver through the GIO interface layer and for the implementation I followed the given example. The TDA2px is configured as a spi slave and should run in interrupt mode, since polling seems to block all execution.
My problem is that I cant read any data in interrupt mode while I can read data in polling mode. I'm using the GIO Standard Model but have also tried the GIO Issue Reclaim Model this does not seem to make a difference. When I'm using a timeout the GIO_read function will fail with a timeout error, otherwise the function does not seem to return.
While debugging I noticed the function mcspiSlaveTransferStart() is only started if there is a transmission already scheduled.
if ((MCSPI_COMMMODE_SLAVE ==
instHandle->spiHWconfig.masterOrSlave) &&
(instHandle->opMode ==
MCSPI_OPMODE_INTERRUPT))
{
if ((Bool) TRUE ==
Queue_empty(Queue_handle(&(chanHandle->
queuePendingList))))
{
/* This is the first buffer just prime
*this */
tempCastIoPtr = (Void *) ioPacket;
Queue_put(Queue_handle(
&(chanHandle->
queuePendingList)),
(Queue_Elem *) tempCastIoPtr);
ioPacketProcess = NULL;
status = IOM_PENDING;
Hwi_restore(hwiKey);
}
else
{
/* This is the not the first buffer.
* Put current packet in queue. */
tempCastIoPtr = (Void *) ioPacket;
Queue_put(Queue_handle(
&(chanHandle->
queuePendingList)),
(Queue_Elem *) tempCastIoPtr);
/* Get the top element in queue. */
ioPacketProcess =
(IOM_Packet *) Queue_get(
Queue_handle(&(
chanHandle
->
queuePendingList)));
instHandle->currentActiveChannel =
(Mcspi_ChanObj *) chanHandle;
Hwi_restore(hwiKey);
status = mcspiSlaveTransferStart(
instHandle, chanHandle,
ioPacketProcess);
}
}If I try to trigger the read a second time to execute mcspiSlaveTransferStart, GIO_read will again fail with a timeout but afterwards the interrupt handler will run.
The communication master is transmitting data in an interval which I confirmed with an oscilloscope.
Part Number:TDA2HG
Tool/software: Linux
I am using PROCESSOR_SDK_VISION_03_06_00_00_setuplinux to develop a board.
Usually, I need to use four cameras. if one of the cameras is broken, the rest of the monitors need to be displayed normally.
but now, if a camera is wrong ,the entire screen is black.
I want to copy a normal video frame to the missing ones, but I don't know if this is correct.
Can you give me any advice?
Part Number:AM5728
Tool/software: TI-RTOS
Hi,
I'm using the Beagleboard-x15 and trying to run the EVM572x audio loopback example (on the C66x) included in the RTOS SDK. I'm seeing stack corruption using that example when I add an array in main. I was able to run the pdkProjectCreate.sh scrip to generate the project, and imported that into CCS to run.
I then added an array into main so my main function looks like (the highlighted code is the only code I added):
volatile int emuwait=0;
int main(Void)
{
while(emuwait);
configureAudio();
McaspDevice_init();
int temp[256];
int i = 0;
for(i = 0; i<256; ++i)
temp[i]=i;
configMcASP_SocHwInfo();
Aic31_init();
Log_info0("\r\nAudio Sample Main\n");
BIOS_start();
return 0;
}
When the audio is running, the temp array gets corrupted. Does the RTOS expect you to not create any data on the stack in main before the OS starts?
CCS Version: 9.0.1.00004
RTOS-SDK version 1.0.14
Part Number:AM3352
Tool/software: Linux
Hi,
I am using am3352, with USB1 as a host. (linux 4.14)
I have several FAT32 usb drives, when connected to USB1, I always got the following error except one drive. These drives work with no error or warning when directly connected to a Windows pc.
[ 8471.997091] usb 1-1.1: new high-speed USB device number 5 using musb-hdrc
[ 8472.156569] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 8472.208405] usb-storage 1-1.1:1.0: Quirks match for vid 13fe pid 3600: 4000
[ 8472.227159] scsi host0: usb-storage 1-1.1:1.0
[ 8473.315922] scsi 0:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 0 CCS
[ 8474.933940] sd 0:0:0:0: [sda] 7585792 512-byte logical blocks: (3.88 GB/3.62 GiB)
[ 8474.953111] sd 0:0:0:0: [sda] Write Protect is off
[ 8474.969580] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[ 8474.987182] sd 0:0:0:0: [sda] No Caching mode page found
[ 8474.992557] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 8475.046383] sda: sda1 sda2
[ 8475.063529] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 8475.186571] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 8475.194935] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
[ 8475.200839] sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0
[ 8475.206014] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 73 bf 80 00 00 08 00
[ 8475.213649] print_req_error: critical medium error, dev sda, sector 7585664
[ 8475.277293] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 8475.285554] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
[ 8475.291507] sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0
[ 8475.296700] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 73 bf 80 00 00 08 00
[ 8475.304344] print_req_error: critical medium error, dev sda, sector 7585664
[ 8475.311365] Buffer I/O error on dev sda, logical block 948208, async page read
The only difference I can tell from the one that work and those raise errors is that those failed drive all have a MBR part, and the worked one doesn't.
Could MBR be the problem?
Please help. Thank you.
Part Number:TDA3XEVM
In the TI code for CFAR, C1/2^C2 is used as threshold scalar. As per the ticket https://e2e.ti.com/support/processors/f/791/p/814969/3018330#3018330, energy of each bin is first converted into binary log domain and then noise floor calculation happens in log domain. So in which way as following the paramter C1/2^C2 is applied to the noise floor in the log domain to get threshold?
1. Threshold = Noise floor + log2(C1/2^C2)
2. Threshold = Noise floor + (C1/2^C2)
3. Threshold = 2^(Noise floor)*C1/2^C2
4. Threshold = Noise floor *(C1/2^C2)
Part Number:TMS320C6678
Tool/software: Code Composer Studio
ccs uses the 6678 specific gel file to prepare the evm for loading an out file for debug
-without it external memory and cpu speed clocks are not set up properly.
I need to combine the gel code and the .out file and write it into flash storage.
How do I achieve this?
If I have a program that only needs internal memory can I include gel code programmatically,
to do the DDR setup, and get it to work correctly?
I want to make an ethernet client program running on core0 that boots from flash, connects up a server on the host PC
which can then go on to boot and reboot itself and other cores with application code.
Part Number:PHYTC-3P-PHYCORE-AM57X
Hello,
We are trying to build the Yocto BSP image for a Phytec AM5728 board.
We following the instructions in the guide: https://wiki.phytec.com/display/public/PRODUCTINFO/BSP-Yocto-TISDK-AM57xx-PD18.2.0+Quickstart
We tried many times to run the procedure, but always with errors. I have attached the log file.
We are generating the build from a VMWare virtual machine running Ubuntu 16 64 bits. Note: We were able to generate the BSP from the pre-built image without problem.
We have replaced the AM57xx instructions by AM5728 in the commands, as described in the guide.
Do you have any idea where the error comes from?
Thank you.
Best regards,
Jorge
(Please visit the site to view this file)
Part Number:TMS320C5535
Hi,
Have installed ccsv6.1.3 and SYS/BIOS 5.42.02.10 and CSL 3.08 on my machine.
Tried building CSL_USB_dmaExample_Out for TMS320C5535 DSP.
Got the following errors
////////////////////////////////////////////////////////////////////////////////
**** Build of configuration Debug for project CSL_USB_MSC_dmaExample_Out ****
"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Building file: ../VC5505_CSL_BIOS_cfg.tcf'
'Invoking: TConf'
"C:/ti/bios_5_42_02_10/xdctools/tconf" -b -Dconfig.importPath="C:/ti/bios_5_42_02_10/packages;" "../VC5505_CSL_BIOS_cfg.tcf"
'Finished building: ../VC5505_CSL_BIOS_cfg.tcf'
' '
'Building file: VC5505_CSL_BIOS_cfg.s??'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5535 --memory_model=large -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_02_10/packages/ti/bios/include" --include_path="C:/ti/c55_lp/c55_csl_3.08/inc" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/src" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/common" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample/Debug" --include_path="C:/ti/bios_5_42_02_10/packages/ti/rtdx/include/c5500" --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --preproc_with_compile --preproc_dependency="VC5505_CSL_BIOS_cfg.d" "VC5505_CSL_BIOS_cfg.s??"
'Finished building: VC5505_CSL_BIOS_cfg.s??'
' '
'Building file: VC5505_CSL_BIOS_cfg_c.c'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5535 --memory_model=large -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_02_10/packages/ti/bios/include" --include_path="C:/ti/c55_lp/c55_csl_3.08/inc" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/src" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/common" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample/Debug" --include_path="C:/ti/bios_5_42_02_10/packages/ti/rtdx/include/c5500" --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --preproc_with_compile --preproc_dependency="VC5505_CSL_BIOS_cfg_c.d" "VC5505_CSL_BIOS_cfg_c.c"
'Finished building: VC5505_CSL_BIOS_cfg_c.c'
' '
'Building file: ../chk_mmc.c'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5535 --memory_model=large -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_02_10/packages/ti/bios/include" --include_path="C:/ti/c55_lp/c55_csl_3.08/inc" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/src" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/common" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample/Debug" --include_path="C:/ti/bios_5_42_02_10/packages/ti/rtdx/include/c5500" --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --preproc_with_compile --preproc_dependency="chk_mmc.d" "../chk_mmc.c"
'Finished building: ../chk_mmc.c'
' '
'Building file: ../csl_usb_msc_dma_example.c'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5535 --memory_model=large -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_02_10/packages/ti/bios/include" --include_path="C:/ti/c55_lp/c55_csl_3.08/inc" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/src" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/common" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample/Debug" --include_path="C:/ti/bios_5_42_02_10/packages/ti/rtdx/include/c5500" --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --preproc_with_compile --preproc_dependency="csl_usb_msc_dma_example.d" "../csl_usb_msc_dma_example.c"
'Finished building: ../csl_usb_msc_dma_example.c'
' '
'Building target: CSL_USB_MSC_dmaExample_Out.out'
'Invoking: C5500 Linker'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5535 --memory_model=large -g --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic -z -m"CSL_USB_MSC_dmaExample_Out.map" --stack_size=0x200 --heap_size=0x400 -i"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/lib" -i"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" -i"C:/ti/bios_5_42_02_10/packages/ti/bios/lib" -i"C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/C55XXCSL_LP" -i"C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample" -i"C:/ti/bios_5_42_02_10/packages/ti/rtdx/lib/c5500" --reread_libs --warn_sections --rom_model --sys_stacksize=0x200 -o "CSL_USB_MSC_dmaExample_Out.out" "./VC5505_CSL_BIOS_cfg.obj" "./VC5505_CSL_BIOS_cfg_c.obj" "./chk_mmc.obj" "./csl_usb_msc_dma_example.obj" "../C5535.cmd" -l"./VC5505_CSL_BIOS_cfg.cmd" -lDebug/C55XXCSL_LP.lib -lrts55x.lib -l"C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/atafs_bios_drv_lib/Debug/atafs_bios_drv_lib.lib" -llibc.a
<Linking>
"./VC5505_CSL_BIOS_cfg.cmd", line 166: error: VECT memory range overlaps
existing memory range SARAM31
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DARAM0
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DARAM1
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DARAM2
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DARAM3
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DARAM4
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DARAM5
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DARAM6
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DARAM7
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM0
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM1
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM2
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM3
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM4
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM5
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM6
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM7
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM8
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM9
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM10
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM11
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM12
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM13
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM14
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM15
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM16
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM17
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM18
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM19
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM20
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM21
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM22
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM23
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM24
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM25
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM26
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM27
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM28
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM29
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM30
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range SARAM31
"../C5535.cmd", line 69: error #10099-D: program will not fit into available
memory. placement with alignment/blocking fails for section ".text" size
0x146b7 page 0. Available memory ranges:
DARAM1 size: 0x2000 unused: 0x2000 max hole: 0x2000
.text > DARAM1
"../C5535.cmd", line 75: error #10099-D: program will not fit into available
memory. run placement with alignment/blocking fails for section ".bss" size
0xb7fe page 0. Available memory ranges:
DARAM5 size: 0x2000 unused: 0x2000 max hole: 0x2000
.bss > DARAM5
"../C5535.cmd", line 76: error #10099-D: program will not fit into available
memory. placement with alignment/blocking fails for section ".const" size
0xdc2 page 0. Available memory ranges:
DARAM0 size: 0x1f40 unused: 0x9b2 max hole: 0x9b0
.const > DARAM0
undefined first referenced
symbol in file
--------- ----------------
__STACK_SIZE C:/ti/bios_5_42_02_10/packages/ti/bios/lib/bios.a55L<boot.o55L>
__SYSSTACK_SIZE C:/ti/bios_5_42_02_10/packages/ti/bios/lib/bios.a55L<boot.o55L>
error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking;
"CSL_USB_MSC_dmaExample_Out.out" not built
>> Compilation failure
makefile:150: recipe for target 'CSL_USB_MSC_dmaExample_Out.out' failed
gmake: *** [CSL_USB_MSC_dmaExample_Out.out] Error 1
gmake: Target 'all' not remade because of errors.
**** Build Finished ****
///////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////C5535.cmd file is as follows////////////////////////////////////////////////
/****************************************************************************/
/* C5535.cmd */
/* Copyright (c) 2012 Texas Instruments Incorporated */
/* Author: Rafael de Souza */
/* */
/* Description: This file is a sample linker command file that can be */
/* used for linking programs built with the C compiler and */
/* running the resulting .out file on a C5535. */
/* Use it as a guideline. You will want to */
/* change the memory layout to match your specific */
/* target system. You may want to change the allocation */
/* scheme according to the size of your program. */
/* */
/****************************************************************************/
MEMORY
{
MMR: o = 0x000000 l = 0x0000c0 /* 192B Memory Mapped Registers */
DARAM0: o = 0x0000C0 l = 0x001F40 /* 8kB Dual Access RAM 0 */
DARAM1: o = 0x002000 l = 0x002000 /* 8kB Dual Access RAM 1 */
DARAM2: o = 0x004000 l = 0x002000 /* 8kB Dual Access RAM 2 */
DARAM3: o = 0x006000 l = 0x002000 /* 8kB Dual Access RAM 3 */
DARAM4: o = 0x008000 l = 0x002000 /* 8kB Dual Access RAM 4 */
DARAM5: o = 0x00A000 l = 0x002000 /* 8kB Dual Access RAM 5 */
DARAM6: o = 0x00C000 l = 0x002000 /* 8kB Dual Access RAM 6 */
DARAM7: o = 0x00E000 l = 0x002000 /* 8kB Dual Access RAM 7 */
SARAM0: o = 0x010000 l = 0x002000 /* 8kB Single Access RAM 0 */
SARAM1: o = 0x012000 l = 0x002000 /* 8kB Single Access RAM 1 */
SARAM2: o = 0x014000 l = 0x002000 /* 8kB Single Access RAM 2 */
SARAM3: o = 0x016000 l = 0x002000 /* 8kB Single Access RAM 3 */
SARAM4: o = 0x018000 l = 0x002000 /* 8kB Single Access RAM 4 */
SARAM5: o = 0x01A000 l = 0x002000 /* 8kB Single Access RAM 5 */
SARAM6: o = 0x01C000 l = 0x002000 /* 8kB Single Access RAM 6 */
SARAM7: o = 0x01E000 l = 0x002000 /* 8kB Single Access RAM 7 */
SARAM8: o = 0x020000 l = 0x002000 /* 8kB Single Access RAM 8 */
SARAM9: o = 0x022000 l = 0x002000 /* 8kB Single Access RAM 9 */
SARAM10: o = 0x024000 l = 0x002000 /* 8kB Single Access RAM 10 */
SARAM11: o = 0x026000 l = 0x002000 /* 8kB Single Access RAM 11 */
SARAM12: o = 0x028000 l = 0x002000 /* 8kB Single Access RAM 12 */
SARAM13: o = 0x02A000 l = 0x002000 /* 8kB Single Access RAM 13 */
SARAM14: o = 0x02C000 l = 0x002000 /* 8kB Single Access RAM 14 */
SARAM15: o = 0x02E000 l = 0x002000 /* 8kB Single Access RAM 15 */
SARAM16: o = 0x030000 l = 0x002000 /* 8kB Single Access RAM 16 */
SARAM17: o = 0x032000 l = 0x002000 /* 8kB Single Access RAM 17 */
SARAM18: o = 0x034000 l = 0x002000 /* 8kB Single Access RAM 18 */
SARAM19: o = 0x036000 l = 0x002000 /* 8kB Single Access RAM 19 */
SARAM20: o = 0x038000 l = 0x002000 /* 8kB Single Access RAM 20 */
SARAM21: o = 0x03A000 l = 0x002000 /* 8kB Single Access RAM 21 */
SARAM22: o = 0x03C000 l = 0x002000 /* 8kB Single Access RAM 22 */
SARAM23: o = 0x03E000 l = 0x002000 /* 8kB Single Access RAM 23 */
SARAM24: o = 0x040000 l = 0x002000 /* 8kB Single Access RAM 24 */
SARAM25: o = 0x042000 l = 0x002000 /* 8kB Single Access RAM 25 */
SARAM26: o = 0x044000 l = 0x002000 /* 8kB Single Access RAM 26 */
SARAM27: o = 0x046000 l = 0x002000 /* 8kB Single Access RAM 27 */
SARAM28: o = 0x048000 l = 0x002000 /* 8kB Single Access RAM 28 */
SARAM29: o = 0x04A000 l = 0x002000 /* 8kB Single Access RAM 29 */
SARAM30: o = 0x04C000 l = 0x002000 /* 8kB Single Access RAM 30 */
SARAM31: o = 0x04E000 l = 0x002000 /* 8kB Single Access RAM 31 */
ROM: o = 0xFE0000 l = 0x01FF00 /* 128kB ROM (MPNMC=0) or CS5 (MPNMC=1) */
VECS: o = 0xFFFF00 l = 0x000100 /* reset vector */
}
SECTIONS
{
vectors (NOLOAD) > VECS /* If MPNMC = 1, remove the NOLOAD directive */
.cinit > DARAM0
.text > DARAM1
.stack > DARAM0
.sysstack > DARAM0
.sysmem > DARAM4
.data > DARAM4
.cio > DARAM0
.bss > DARAM5
.const > DARAM0
}
////////////////////////////////////////////////////////////////////////////
When I changed the target silicon to 5505 to include VC5505_USB.cmd
following is the build error
///////////////////////////////////////////////////////////////////////////////////
**** Clean-only build of configuration Debug for project CSL_USB_MSC_dmaExample_Out ****
"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k clean
DEL /F "VC5505_CSL_BIOS_cfg.h" "VC5505_CSL_BIOS_cfg.h??" "VC5505_CSL_BIOS_.cdb" "CSL_USB_MSC_dmaExample_Out.out" "VC5505_CSL_BIOS_cfg.cmd" "VC5505_CSL_BIOS_cfg.s??" "VC5505_CSL_BIOS_cfg_c.c" "CSL_USB_MSC_dmaExample_Out.hex"
DEL /F "VC5505_CSL_BIOS_cfg_c.d" "chk_mmc.d" "csl_usb_msc_dma_example.d"
DEL /F "VC5505_CSL_BIOS_cfg.d"
DEL /F "VC5505_CSL_BIOS_cfg.obj" "VC5505_CSL_BIOS_cfg_c.obj" "chk_mmc.obj" "csl_usb_msc_dma_example.obj"
Could Not Find C:\ti\c55_lp\c55_csl_3.08\ccs_v6.x_examples\usb\CSL_USB_MSC_dmaExample\Debug\VC5505_CSL_BIOS_cfg.h
Could Not Find C:\ti\c55_lp\c55_csl_3.08\ccs_v6.x_examples\usb\CSL_USB_MSC_dmaExample\Debug\VC5505_CSL_BIOS_cfg_c.d
Could Not Find C:\ti\c55_lp\c55_csl_3.08\ccs_v6.x_examples\usb\CSL_USB_MSC_dmaExample\Debug\VC5505_CSL_BIOS_cfg.d
Could Not Find C:\ti\c55_lp\c55_csl_3.08\ccs_v6.x_examples\usb\CSL_USB_MSC_dmaExample\Debug\VC5505_CSL_BIOS_cfg.obj
'Finished clean'
' '
**** Build Finished ****
**** Build of configuration Debug for project CSL_USB_MSC_dmaExample_Out ****
"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Building file: ../VC5505_CSL_BIOS_cfg.tcf'
'Invoking: TConf'
"C:/ti/bios_5_42_02_10/xdctools/tconf" -b -Dconfig.importPath="C:/ti/bios_5_42_02_10/packages;" "../VC5505_CSL_BIOS_cfg.tcf"
'Finished building: ../VC5505_CSL_BIOS_cfg.tcf'
' '
'Building file: VC5505_CSL_BIOS_cfg.s??'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5505 --memory_model=large -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_02_10/packages/ti/bios/include" --include_path="C:/ti/c55_lp/c55_csl_3.08/inc" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/src" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/common" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample/Debug" --include_path="C:/ti/bios_5_42_02_10/packages/ti/rtdx/include/c5500" --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --preproc_with_compile --preproc_dependency="VC5505_CSL_BIOS_cfg.d" "VC5505_CSL_BIOS_cfg.s??"
'Finished building: VC5505_CSL_BIOS_cfg.s??'
' '
'Building file: VC5505_CSL_BIOS_cfg_c.c'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5505 --memory_model=large -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_02_10/packages/ti/bios/include" --include_path="C:/ti/c55_lp/c55_csl_3.08/inc" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/src" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/common" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample/Debug" --include_path="C:/ti/bios_5_42_02_10/packages/ti/rtdx/include/c5500" --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --preproc_with_compile --preproc_dependency="VC5505_CSL_BIOS_cfg_c.d" "VC5505_CSL_BIOS_cfg_c.c"
'Finished building: VC5505_CSL_BIOS_cfg_c.c'
' '
'Building file: ../chk_mmc.c'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5505 --memory_model=large -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_02_10/packages/ti/bios/include" --include_path="C:/ti/c55_lp/c55_csl_3.08/inc" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/src" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/common" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample/Debug" --include_path="C:/ti/bios_5_42_02_10/packages/ti/rtdx/include/c5500" --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --preproc_with_compile --preproc_dependency="chk_mmc.d" "../chk_mmc.c"
'Finished building: ../chk_mmc.c'
' '
'Building file: ../csl_usb_msc_dma_example.c'
'Invoking: C5500 Compiler'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5505 --memory_model=large -g --include_path="C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" --include_path="C:/ti/bios_5_42_02_10/packages/ti/bios/include" --include_path="C:/ti/c55_lp/c55_csl_3.08/inc" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/src" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/common" --include_path="C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample/Debug" --include_path="C:/ti/bios_5_42_02_10/packages/ti/rtdx/include/c5500" --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic --preproc_with_compile --preproc_dependency="csl_usb_msc_dma_example.d" "../csl_usb_msc_dma_example.c"
'Finished building: ../csl_usb_msc_dma_example.c'
' '
'Building target: CSL_USB_MSC_dmaExample_Out.out'
'Invoking: C5500 Linker'
"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/bin/cl55" -v5505 --memory_model=large -g --define="_DEBUG" --define="CSL_MSC_TEST" --define=c5535 --display_error_number --verbose_diagnostics --diag_warning=225 --ptrdiff_size=16 --algebraic --asm_source=algebraic -z -m"CSL_USB_MSC_dmaExample_Out.map" --stack_size=0x200 --heap_size=0x400 -i"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/lib" -i"C:/ti/ccsv6/tools/compiler/c5500_4.4.1/include" -i"C:/ti/bios_5_42_02_10/packages/ti/bios/lib" -i"C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/C55XXCSL_LP" -i"C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/usb/CSL_USB_MSC_dmaExample" -i"C:/ti/bios_5_42_02_10/packages/ti/rtdx/lib/c5500" --reread_libs --warn_sections --rom_model --sys_stacksize=0x200 -o "CSL_USB_MSC_dmaExample_Out.out" "./VC5505_CSL_BIOS_cfg.obj" "./VC5505_CSL_BIOS_cfg_c.obj" "./chk_mmc.obj" "./csl_usb_msc_dma_example.obj" "../VC5505_USB.cmd" -l"./VC5505_CSL_BIOS_cfg.cmd" -lDebug/C55XXCSL_LP.lib -lrts55x.lib -l"C:/ti/c55_lp/c55_csl_3.08/ccs_v6.x_examples/drv/atafs/atafs_bios_drv_lib/Debug/atafs_bios_drv_lib.lib" -llibc.a
<Linking>
"./VC5505_CSL_BIOS_cfg.cmd", line 166: error: VECT memory range overlaps
existing memory range PROG
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range VEC
>> Compilation failure
makefile:150: recipe for target 'CSL_USB_MSC_dmaExample_Out.out' failed
"./VC5505_CSL_BIOS_cfg.cmd", line 167: error: DARAM memory range overlaps
existing memory range DATA
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range DATA
"./VC5505_CSL_BIOS_cfg.cmd", line 168: error: SARAM memory range overlaps
existing memory range PROG
"../VC5505_USB.cmd", line 23: error #10099-D: program will not fit into
available memory. placement with alignment/blocking fails for section
".text" size 0x146b7 page 0. Available memory ranges:
PROG size: 0x9000 unused: 0x80ae max hole: 0x80ac
.text : > PROG
undefined first referenced
symbol in file
--------- ----------------
__STACK_SIZE C:/ti/bios_5_42_02_10/packages/ti/bios/lib/bios.a55L<boot.o55L>
__SYSSTACK_SIZE C:/ti/bios_5_42_02_10/packages/ti/bios/lib/bios.a55L<boot.o55L>
error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking;
"CSL_USB_MSC_dmaExample_Out.out" not built
gmake: *** [CSL_USB_MSC_dmaExample_Out.out] Error 1
gmake: Target 'all' not remade because of errors.
**** Build Finished ****
//////////////////////////////////////////////////////////////////////////////////
where VC5505_USB.cmd is as follows
////////////////////////////////////////////////////////////////////////////////////////////
-stack 0x2000 /* PRIMARY STACK SIZE */
-sysstack 0x1000 /* SECONDARY STACK SIZE */
-heap 0x2000 /* HEAP AREA SIZE */
MEMORY
{
PAGE 0:
VEC(RWX) : origin = 00000C0h length = 000300h
//DATA(RWX) : origin = 0000400h length = 017C00h
//PROG(RX) : origin = 0018000h length = 00A000h
//DATA(RWX) : origin = 0000400h length = 02f000h
//PROG(RX) : origin = 002f500h length = 00A000h
//PROG(RX) : origin = 002f500h length = 01C000h
//DATA(RWX) : origin = 0000400h length = 03f000h
//PROG(RX) : origin = 003f500h length = 00A000h
DATA(RWX) : origin = 0000400h length = 046c00h
PROG(RX) : origin = 0047000h length = 009000h
}
SECTIONS
{
vectors : > VEC ALIGN = 256
.text : > PROG
.data : > DATA
.cinit : > DATA _
Thanks and Regards,
Sangeeta Gunwani
Part Number:PROCESSOR-SDK-AM335X
I am trying to set up a system on an AM335x chip where the CPU sends messages to the PRU via RPMsg to have the PRU send those messages over the CAN interface at precise times. Since the PRU cannot take advantage of the standard method for sending and receiving over CAN that the CPU side has (i.e. configure a network interface and use the cansend and candump utilities) I figured that I have to perform the initialization manually in the PRU's firmware by following the steps outlined in the AM335X technical manual.
I have the OCP master port enabled by setting STANDBY_INIT = 0, and I see DCAN0 and DCAN1 in the memory map of the AM335X_PRU.cmd file. However, I am unable to actually write to the memory addresses corresponding with the DCAN peripherals. I have no problem writing to peripherals local to the PRUSS, such as UART or the IEP. Should it be possible for the PRU to write to the DCAN register location (for me it is 0x441CC000 as per the .cmd file), and if so, what am I doing wrong?
Part Number:TMS320C6748
Tool/software: TI-RTOS
I was able to run MCASP_Audio_lcdkOMAPL138_c674xExampleProject once and get audio to pass through, but now I gets stuck in the first call to MCASP_log(). See call stack below:
MCASP_Audio_lcdkOMAPL138_c674xExampleProject [Code Composer Studio - Device Debugging]
Texas Instruments XDS2xx USB Debug Probe/C674X_0 (Suspended)
UART_fifoWait_v0(unsigned int)() at uart.c:806 0xC305CE8C
UART_write2_v0$0(struct UART_Config_s *, struct UART_Transaction_s *)() at UART_v0.c:1,002 0xC3047634
UART_write_v0$0(struct UART_Config_s *, void *, unsigned int)() at UART_v0.c:864 0xC305786C
uart_console_putc$0(unsigned char)() at UART_stdio.c:1,659 0xC305DA78
UART_printf(char *)() at UART_stdio.c:642 0xC3042420
Audio_echo_Task() at audioSample_io.c:851 0xC303A648
ti_sysbios_knl_Task_exit__E() at Task.c:481 0xC3052200
Audio_echo_Task() at audioSample_io.c:851 0xC303A648
unregisterEdma3Interrupts(unsigned int)() 0x00000000 (unregisterEdma3Interrupts does not contain frame information)
Texas Instruments XDS2xx USB Debug Probe/PRU_0 (Disconnected : Unknown)
Texas Instruments XDS2xx USB Debug Probe/PRU_1 (Disconnected : Unknown)
Any ideas?
Part Number:AM4378
Tool/software: Code Composer Studio
Hi,
Is there an example of how to configure a memory of 16 bits using GEL files.
If not, How I can do?
There is WR_MEM_32 and RD_MEM_32 which they are for 32 bits... using unsigned int.
Thanks in advance for the help..
Best regards,
Efrain
Part Number:TMS320DM642
Hey team,
Does TI sell an EVM for the TMS320DM642? The DM642 (http://www.ti.com/tool/DM642CODECS appears to only evaluate certain portions of the device.
Thank you!
Part Number:TDA2EVM5777
Part Number:DRA787
Tool/software: TI-RTOS
Our produce use DRA78x, have a 256M QSPI Flash.
Software based on vision SDK, OS is RTOS.
We need to create a FAT partition on QSPI Flash.
how to create a FAT partition?
Part Number:PROCESSOR-SDK-AM335X
Tool/software: Linux
Hi,
I am new to the Linux Processor SDK and currently exploring available options for file transfers from host PC to target board.
The Software Developer's Guide mentions 2 options.
1. Direct Transfer to rootfs partition of SD card
2. File transfer using NFS
My queries are as follows.
1. I tried using this approach but the rootfs partition of the SD card doesn't not allow a paste operation (I guess it is mounted as read only) while the boot partition allows for file transfers. Is this expected?
2. Is it necessary to have a router for the NFS based approach? Or is that only required in the case of a wireless access, would a direct ethernet connection to PC work? Are there any other configurations you would recommend?
3. Are there any other file transfer options apart from the ones I've listed? Anything similar to SFTP that worked on the Beaglebone?