Quantcast
Channel: Forums - Recent Threads
Viewing all 262198 articles
Browse latest View live

TPS563200: can we use 40 uF of output cap for both TPS566335 and TPS568330 ?

$
0
0

Part Number: TPS563200

Hi, 

My customer is using these two parts, can you help to let us know if we can use 40 uF for the output cap of these two parts? 

Great thanks for your help. 


TAS5766MDCAEVM: How to configure TAS5766MDCAEVM to do SNR test ?

$
0
0

Part Number: TAS5766MDCAEVM

Hi 

Is there a pure path code for configure TAS5766MDCAEVM for SNR measurement ?

TMS320F28377D: What is "Base_Speed" means in M-method velocimetry?

$
0
0

Part Number: TMS320F28377D

Dear team:

In the encoder M method, there is a formula: speed = Base_Speed* (x2-x1)/4000. So how do I determine this Base_Speed when actually calculating it?

Best regards

CCS/AWR1843BOOST: The TM4C129 chip in the AWR1843BOOST functions in both function and flash modes, as well as communicating with the GUI as a UART.I didn't find the source code, or the firmware, in the SDK.

$
0
0

Part Number: AWR1843BOOST

Tool/software: Code Composer Studio

Of course, there are other functions that I have not found. Have you introduced the design of TM4C129 on this board in detail, or the source code and firmware? For future expansion, thank you

CCS/TMS320C6713B: CCSv9 can be used XDS200/XDS560 and so on?

$
0
0

Part Number: TMS320C6713B

Tool/software: Code Composer Studio

Hi,

Now, CCSv9 was launched.

 -Code Composer Studio Version 9

 -processors.wiki.ti.com/.../Download_CCS

Also, it is not possible to use XDS510.

 -Spectrum Digital XDS510USB JTAG debuggers are not supported with 64bit CCS installations.

 -processors.wiki.ti.com/.../Download_CCS

So, What-XDS model, 100,110,200,220,560, can be used?

If you have any information, pls let me know.

Regards,

kyt

DRV8847: Questions for DRV8847S I2C Waveform

$
0
0

Part Number: DRV8847

Hi Experts,

Recently our customer is debugging on our DRV8847S on their board, and captured some strange I2C SDA line waveform as below, where you will see a bar when voltage goes from high to low. Also we checked some application notes for this device, and saw one waveform looks like similar to customer's behavior, but not sure(http://www.ti.com/lit/an/slvae40/slvae40.pdf). Do you have any thoughts why there is a bar in here?

1. Strange I2C SDA line waveform captured on customer's board:

2. Looks like there is a similar behavior captured in this application note, but not sure:

Thanks a lot!

ADS8881: Purpose of AVDD

$
0
0

Part Number: ADS8881

Hello,

I would like you to confirm about below.

* There are two analog power (AVDD and REF) in ADS8881.

According to datasheet of ADS8881(Figure 45. Detailed Block Diagram), it seems that "REF" voltage is used for all of analog power source (supply for ADC, clamp voltage of input line).

According to datasheet, "The internal circuits of the device operate on AVDD" is described. So, this voltage is used for something. However, I'm not sure which purpose this supply is used.

So, could you please tell us internal usecase of this voltage ?

(Especailly, I would like to know when AVDD become low voltage than min spec of datasheet, which function will be affected.

One of function, I guess that this voltage is used for POR(Power on reset). so I can see that device will not boot up as one of issue..)

Best Regards,

TDA2P-ACD: GPIO interrupt delay

$
0
0

Part Number: TDA2P-ACD

Hi

We are using PWM module to generate 60 Hz signal. Same signal is routed back to TDA.
Further, we are using GPIO interrupt (GPIO_4) for detecting rising edge of PWM. Inside ISR we are time-stamping
this event. So, difference between two consecutive interrupts should be 16 667 us. But, in our case, time difference is
always very close to 16 000 us or 17 000 us. For example, if we change PWM signal to 50 Hz 100 Hz, or any frequency which
period is rounded to 1 ms (eg. 20 ms or 10 ms) time-stamp is very precise. So, our conclusion that this could be related
to GPIO interrupt latency and GPIO clock. Is this correct? What is clock frequency used for GPIO_4 and is it possible to change it.
Please, give us some hint, our customer is waiting for replay.

Time-stamp function returns time in micro seconds.

Best regards,
Stefan.


CCS/CC1352R: CCS/I2C

$
0
0

Part Number: CC1352R

Tool/software: Code Composer Studio

If I want to write to a register in a sensor using I2C protocol, is the following code correct? Device 7-bit slave address is 0x57. The register address is 0x06 and the data I want to write on that register is 0x03. The code is after all the initialization.

                txBuffer[0] = 0x06;
                temp[0]=0x03;
                i2cTransaction.slaveAddress = 0x57;
                i2cTransaction.writeBuf = txBuffer;
                i2cTransaction.writeCount = 1;
                i2cTransaction.writeBuf = temp;
                i2cTransaction.writeCount = 1;
                i2cTransaction.readBuf = rxBuffer;
                i2cTransaction.readCount = 4;

AM3359: Qt application on ICE

$
0
0

Part Number: AM3359

Respected sir,

                      I was able to run the hello world application from Linux SDK and RTOS SDK on AM3359 ICE. Now i want  to run Qt based application on AM3359 ICE as my project will be on Qt. But i am not able to find any user guide or getting started guide for running Qt based appliacation on above mentioned device. So can anybody share the Document /link/Example/Process for the same??

Regards,

Digvijay

TMS320F28377D: hrpwm_deadband_sfo_v8 frequency sweep code

$
0
0

Part Number: TMS320F28377D

for(;;)
    {
        while(UpdateFine == 0)    //UpadatFine is the enable flag for freq. sweep
        {
            if(CountUpdatefine >= CountUpdateMax)    //Get into loop every 0XFFFF times
            {
                if(Period < PeriodMax)
                {
                    //
                    // Perform sweep
                    //
                    PeriodIncrement = InputPeriodInc >> 16;                                       
                    PeriodFineIncrement = (Uint16)InputPeriodInc;            
                    Period = Period + PeriodIncrement;                            
                    PeriodFine_temp = (Uint32)PeriodFine +                   
                                                 (Uint32)PeriodFineIncrement;
                    if(PeriodFine_temp >= 0x10000)                           
                    {
                        PeriodFine_temp = PeriodFine_temp - 0x10000;         
                        Period = Period + 1;
                    }

                    //
                    // Period is odd - CMP is divide by 2 for 50% duty
                    //
                    if (Period % 2 == 1)
                    {
                        PeriodOdd = 1;
                    }
                    else
                    {
                        PeriodOdd = 0;
                    }

                    PeriodFine = (Uint16) PeriodFine_temp;                  

                    //
                    // Update PWM values for non-zero increment
                    //
                    if (InputPeriodInc != 0)
                    {
                        FreqCtl_func();
                    }
                }
                else
                {
                    Period = PeriodMin;
                    PeriodFine = 0;
                    if (InputPeriodInc != 0)
                    {
                        FreqCtl_func();
                    }
                }
                CountUpdatefine = 0;
            }
            CountUpdatefine++;
        }
    }

I cannot understand the meaning of variables like PeriodIncrement\PeriodFineIncrement or InputPeriodInc. Could you kindly help to explain the logic of frequency sweeping code ?

Thanks,

Brian

SN74AVC4T774: OE pin design issue

$
0
0

Part Number: SN74AVC4T774

Hi Sir,

My customer design VccA=1.8V and VccB=3.3V and mentioned that if they connect OE pin to VccA = 1.8V, still can see the port B signal pass through to port A.

But if the change OE pin connect to VccB =3.3V, port B signal will not pass the signal to portA.

do you have any idea about it? any suggestions?

TPS92641: Tj calculation

$
0
0

Part Number: TPS92641

Hi team,

Would you advise that Tj calc below is correct?

In case of Iin=50mA, Vin=50V, Ta=25 deg

Tj = Ta + (RθJA(effective)  x  Power )

    = Ta + Rθja x (Vin - Vcc) x Iin

    = 25 + 38.7 x (50  - 8.5) x 50m

    = 105.3 deg

Thanks

Best regards,

Shidara

Analog Switch

$
0
0

Hi E2E,

Did you have a Analog Switch which function is like as below? 

Thanks!

CC2640R2F: Close to production - Is it worth updating to newest SDK?

$
0
0

Part Number: CC2640R2F

Team,

my customer is close to going into production based on SDK v2.30.
The newest SDK is v3.20.

Is there a good reason to move to the newest SDK?
It would be possible, but means to put in effort.

They only use BLE 4.2.
Project is based on SimplePeripheral.
No bonding, no security.

Thanks!


LM5176: LM5176 Two parallel four-switch

$
0
0

Part Number: LM5176

Hi Team,

We want to use LM5176 to design for large watt load, condition is
  Vin 9~36V to 12V output 400w

I saw a file sharing between two parallel four-switch with droop method for higher power.



Can share provide this schematic & BOM ?

thanks

Kevin

TLV320AIC3254: BiQuad Filter Design

$
0
0

Part Number: TLV320AIC3254

Hi Expert,

May I know how to calculate the "Scale" data?

TM4C1294NCPDT: Need BSP/Device Drivers for this part number

$
0
0

Part Number: TM4C1294NCPDT

Hello,
We are starting a new design with TM4C1294NCPDT as the part number. We are doing the schematics of the board by extracting the interface details from the EK-TM4C1294XL evaluation board.

Where can we find the drivers/BSPs for the different interfaces like CAN and Ethernet?

Regards,
Nagendra

DDC264EVM: DDC264EVM

$
0
0

Part Number: DDC264EVM

Hello 

I need the altium or gerber file of DDC264 evaluation board and ADS1299 evaluation board

Does anyone know whether these designs are available?

Thanks

CCS/AM5718: New BIOS Project creation based on ICSS_EMAC_BasicExample_idkAM571x_wSoCLib_C66Testproject

$
0
0

Part Number: AM5718

Tool/software: Code Composer Studio

Hello

I am working on AM5718IDK. I have a requirement to use the subset of ICSS_EMAC_BasicExample_idkAM571x_wSoCLib_C66Testproject example project with MAC to MAC communication from DSP. For that, I have modified the existing auto generated project(pdkProjectCreate.bat)  and working fine. Then I have developed a new BIOS project from existing modified source code. I have included platform as ti.platforms.idkAM571X and C:\ti\pdk_am57xx_1_0_13\packages\ti\build\pruss\lnk_c66_m4_REV2.cmd linker file as you added in the original sample project. 

while compering the linker file generated by project

orginal project


-l"E:\SDR-MP-SC\pru1_2\ICSS_EMAC_BasicExample_idkAM571x_wSoCLib_C66Testproject\Debug\configPkg\package\cfg\icss_emac_c66_wSoCLib_pe66.oe66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\icss_emac\test\am571x\c66\bios\src\sysbios\sysbios.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\pruss\lib\am571x\c66\release\ti.drv.pruss.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\icss_emac\lib\am571x\c66\release\ti.drv.icss_emac.profiling.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\board\lib\idkAM571x\c66\release\ti.board.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\spi\lib\c66\release\ti.drv.spi.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\gpio\lib\c66\release\ti.drv.gpio.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\i2c\lib\am571x\c66\release\ti.drv.i2c.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\uart\lib\c66\release\ti.drv.uart.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\utils\profiling\lib\c66\release\ti.utils.profiling.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\csl\lib\am571x\c66\release\ti.csl.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\osal\lib\tirtos\c66\release\ti.osal.ae66"
-l"C:\ti\bios_6_73_01_01\packages\ti\targets\rts6000\lib\ti.targets.rts6000.ae66"
-l"C:\ti\bios_6_73_01_01\packages\ti\targets\rts6000\lib\boot.ae66"

--retain="*(xdc.meta)"


--args 0x0
-heap 0x0
-stack 0x1000

MEMORY
{
L2SRAM (RWX) : org = 0x800000, len = 0x40000
OCMC_RAM1 (RWX) : org = 0x40300000, len = 0x80000
APP_CODE_MEM : org = 0x80001000, len = 0x2ff000
APP_CACHED_DATA_MEM : org = 0x80300000, len = 0x1400000
APP_UNCACHED_DATA_BLK3_MEM : org = 0xa0000000, len = 0x200000
APP_CACHED_DATA_BLK1_MEM : org = 0x81700000, len = 0xf400000
APP_CACHED_DATA_BLK2_MEM : org = 0x90b00000, len = 0x8000000
}

my new project


-l"E:\SDR-MP-SC\pru1_2\icss_emac_ethernet\Debug\configPkg\package\cfg\icss_emac_c66_wSoCLib_pe66.oe66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\icss_emac\test\am571x\c66\bios\src\sysbios\sysbios.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\pruss\lib\am571x\c66\release\ti.drv.pruss.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\icss_emac\lib\am571x\c66\release\ti.drv.icss_emac.profiling.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\board\lib\idkAM571x\c66\release\ti.board.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\spi\lib\c66\release\ti.drv.spi.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\gpio\lib\c66\release\ti.drv.gpio.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\i2c\lib\am571x\c66\release\ti.drv.i2c.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\drv\uart\lib\c66\release\ti.drv.uart.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\utils\profiling\lib\c66\release\ti.utils.profiling.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\csl\lib\am571x\c66\release\ti.csl.ae66"
-l"C:\ti\pdk_am57xx_1_0_13\packages\ti\osal\lib\tirtos\c66\release\ti.osal.ae66"
-l"C:\ti\bios_6_73_01_01\packages\ti\targets\rts6000\lib\ti.targets.rts6000.ae66"
-l"C:\ti\bios_6_73_01_01\packages\ti\targets\rts6000\lib\boot.ae66"

--retain="*(xdc.meta)"


--args 0x0
-heap 0x0
-stack 0x1000

MEMORY
{
L2SRAM (RWX) : org = 0x800000, len = 0x40000
OCMC_RAM1 (RWX) : org = 0x40300000, len = 0x80000
EXT_RAM : org = 0x80000000, len = 0x80000000
}

 while building my new project following error message is coming

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

"C:\\ti\\ccsv8\\utils\\bin\\gmake" -k -j 4 all -O

Building file: "C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/icss_emac/test/am571x/c66/bios/icss_emac_c66_wSoCLib.cfg"
Invoking: XDCtools
"C:/ti/xdctools_3_50_08_24_core/xs" --xdcpath="C:/ti/bios_6_73_01_01/packages;C:/ti/edma3_lld_2_12_05_30C/packages;C:/ti/pdk_am57xx_1_0_13/packages;C:/ti/bios_6_73_01_01/packages/ti/platforms/idkAM571X;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.idkAM571X -r release -c "C:/ti/ti-cgt-c6000_8.2.2" --compileOptions "-g" "C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/icss_emac/test/am571x/c66/bios/icss_emac_c66_wSoCLib.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring icss_emac_c66_wSoCLib.xe66 from package/cfg/icss_emac_c66_wSoCLib_pe66.cfg ...
generating custom ti.sysbios library makefile ...
Linking with library ti.drv.pruss:./lib/am571x/c66/release/ti.drv.pruss.ae66
Linking with library ti.drv.icss_emac:./lib/am571x/c66/release/ti.drv.icss_emac.profiling.ae66
Linking with library ti.board:./lib/idkAM571x/c66/release/ti.board.ae66
Linking with library ti.drv.spi:./lib/c66/release/ti.drv.spi.ae66
Linking with library ti.drv.gpio:./lib/c66/release/ti.drv.gpio.ae66
Linking with library ti.drv.i2c:./lib/am571x/c66/release/ti.drv.i2c.ae66
Linking with library ti.drv.uart:./lib/c66/release/ti.drv.uart.ae66
Linking with library ti.utils.profiling:./lib/c66/release/ti.utils.profiling.ae66
Linking with library ti.csl:./lib/am571x/c66/release/ti.csl.ae66
Linking with library ti.osal:./lib/tirtos/c66/release/ti.osal.ae66
Starting build of library sources ...
making C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/icss_emac/test/am571x/c66/bios/src/sysbios/sysbios.ae66 ...
gmake[1]: Entering directory `C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/icss_emac/test/am571x/c66/bios/src/sysbios'
gmake[1]: Nothing to be done for `all'.
gmake[1]: Leaving directory `C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/icss_emac/test/am571x/c66/bios/src/sysbios'
Build of libraries done.
cle66 package/cfg/icss_emac_c66_wSoCLib_pe66.c ...
Finished building: "C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/icss_emac/test/am571x/c66/bios/icss_emac_c66_wSoCLib.cfg"

Building file: "../source/icss_emacFwConfig.c"
Invoking: C6000 Compiler
"C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6600 --include_path="E:/SDR-MP-SC/pru1_2/icss_emac_ethernet" --include_path="C:/ti/bios_6_73_01_01/packages/ti/posix/ccs" --include_path="C:/ti/ti-cgt-c6000_8.2.2/include" --define=USE_BIOS --define=SOC_AM571x --define=idkAM571x --define=C66X --define=am5718 -g --diag_warning=225 --diag_wrap=off --display_error_number --preproc_with_compile --preproc_dependency="source/icss_emacFwConfig.d_raw" --obj_directory="source" --cmd_file="configPkg/compiler.opt" "../source/icss_emacFwConfig.c"
Finished building: "../source/icss_emacFwConfig.c"

Building file: "../source/main_dsp.c"
Invoking: C6000 Compiler
"C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6600 --include_path="E:/SDR-MP-SC/pru1_2/icss_emac_ethernet" --include_path="C:/ti/bios_6_73_01_01/packages/ti/posix/ccs" --include_path="C:/ti/ti-cgt-c6000_8.2.2/include" --define=USE_BIOS --define=SOC_AM571x --define=idkAM571x --define=C66X --define=am5718 -g --diag_warning=225 --diag_wrap=off --display_error_number --preproc_with_compile --preproc_dependency="source/main_dsp.d_raw" --obj_directory="source" --cmd_file="configPkg/compiler.opt" "../source/main_dsp.c"
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 721: warning #48-D: incompatible redefinition of macro "Cache_wait" (declared at line 344 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 729: warning #48-D: incompatible redefinition of macro "Cache_inv" (declared at line 341 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 730: warning #48-D: incompatible redefinition of macro "Cache_wb" (declared at line 342 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 731: warning #48-D: incompatible redefinition of macro "Cache_wbInv" (declared at line 343 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 737: warning #48-D: incompatible redefinition of macro "Cache_Module_name" (declared at line 345 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 738: warning #48-D: incompatible redefinition of macro "Cache_Module_id" (declared at line 346 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 739: warning #48-D: incompatible redefinition of macro "Cache_Module_startup" (declared at line 347 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 740: warning #48-D: incompatible redefinition of macro "Cache_Module_startupDone" (declared at line 348 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 741: warning #48-D: incompatible redefinition of macro "Cache_Module_hasMask" (declared at line 349 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 742: warning #48-D: incompatible redefinition of macro "Cache_Module_getMask" (declared at line 350 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 743: warning #48-D: incompatible redefinition of macro "Cache_Module_setMask" (declared at line 351 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 744: warning #48-D: incompatible redefinition of macro "Cache_Object_heap" (declared at line 352 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"C:/ti/bios_6_73_01_01/packages/ti/sysbios/family/c66/Cache.h", line 745: warning #48-D: incompatible redefinition of macro "Cache_Module_heap" (declared at line 353 of "C:/ti/xdctools_3_50_08_24_core/packages/xdc/runtime/knl/Cache.h")
"../source/main_dsp.c", line 176: warning #179-D: variable "info" was declared but never referenced
"../source/main_dsp.c", line 177: warning #179-D: variable "numPorts" was declared but never referenced
Finished building: "../source/main_dsp.c"

Building file: "../source/test_common_utils.c"
Invoking: C6000 Compiler
"C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6600 --include_path="E:/SDR-MP-SC/pru1_2/icss_emac_ethernet" --include_path="C:/ti/bios_6_73_01_01/packages/ti/posix/ccs" --include_path="C:/ti/ti-cgt-c6000_8.2.2/include" --define=USE_BIOS --define=SOC_AM571x --define=idkAM571x --define=C66X --define=am5718 -g --diag_warning=225 --diag_wrap=off --display_error_number --preproc_with_compile --preproc_dependency="source/test_common_utils.d_raw" --obj_directory="source" --cmd_file="configPkg/compiler.opt" "../source/test_common_utils.c"
"../source/test_common_utils.c", line 361: warning #179-D: variable "i" was declared but never referenced
Finished building: "../source/test_common_utils.c"

Building target: "icss_emac_ethernet.out"
Invoking: C6000 Linker
"C:/ti/ti-cgt-c6000_8.2.2/bin/cl6x" -mv6600 --define=USE_BIOS --define=SOC_AM571x --define=idkAM571x --define=C66X --define=am5718 -g --diag_warning=225 --diag_wrap=off --display_error_number -z -m"icss_emac_ethernet.map" --heap_size=0x800 --stack_size=0x800 -i"C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/pruss/lib/am571x/c66/release" -i"C:/ti/ti-cgt-c6000_8.2.2/lib" -i"C:/ti/ti-cgt-c6000_8.2.2/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="icss_emac_ethernet_linkInfo.xml" --rom_model -o "icss_emac_ethernet.out" "./source/icss_emacFwConfig.obj" "./source/main_dsp.obj" "./source/test_common_utils.obj" -l"configPkg/linker.cmd" -lti.drv.pruss.ae66 -l"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd" -l"C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/icss_emac/firmware/icss_dualemac/bin/am571x/c66x/REV2/icss_dualemac_PRU0.bin" -l"C:/ti/pdk_am57xx_1_0_13/packages/ti/drv/icss_emac/firmware/icss_dualemac/bin/am571x/c66x/REV2/icss_dualemac_PRU1.bin" -llibc.a
<Linking>
"configPkg/linker.cmd", line 175: warning #10097: memory range not found: APP_CACHED_DATA_BLK1_MEM on page 0
"configPkg/linker.cmd", line 175: error #10265: no valid memory range(null) available for placement of ".fardata"
"configPkg/linker.cmd", line 175: error #10099-D: program will not fit into available memory. run placement with alignment fails for section ".fardata" size 0x4002cce
"configPkg/linker.cmd", line 161: warning #10097: memory range not found: APP_CODE_MEM on page 0
"configPkg/linker.cmd", line 161: error #10265: no valid memory range(null) available for placement of ".text"
"configPkg/linker.cmd", line 161: error #10099-D: program will not fit into available memory. placement with alignment fails for section ".text" size 0x25e20
"configPkg/linker.cmd", line 173: warning #10097: memory range not found: APP_CACHED_DATA_MEM on page 0
"configPkg/linker.cmd", line 173: error #10265: no valid memory range(null) available for placement of ".const"
"configPkg/linker.cmd", line 173: error #10099-D: program will not fit into available memory. placement with alignment fails for section ".const" size 0x377b
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 18: warning #10097: memory range not found: APP_CACHED_DATA_BLK1_MEM on page 0
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 14: error #10265: no valid memory range(null) available for placement of "PRU0_REV2_DMEM"
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 14: error #10099-D: program will not fit into available memory. run placement with alignment fails for section "PRU0_REV2_DMEM" size 0x2000
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 13: warning #10097: memory range not found: APP_CACHED_DATA_BLK1_MEM on page 0
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 9: error #10265: no valid memory range(null) available for placement of "PRU0_REV2_IMEM"
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 9: error #10099-D: program will not fit into available memory. run placement with alignment fails for section "PRU0_REV2_IMEM" size 0x2000
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 31: warning #10097: memory range not found: APP_CACHED_DATA_BLK1_MEM on page 0
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 27: error #10265: no valid memory range(null) available for placement of "PRU1_REV2_DMEM"
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 27: error #10099-D: program will not fit into available memory. run placement with alignment fails for section "PRU1_REV2_DMEM" size 0x2000
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 26: warning #10097: memory range not found: APP_CACHED_DATA_BLK1_MEM on page 0
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 22: error #10265: no valid memory range(null) available for placement of "PRU1_REV2_IMEM"
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 22: error #10099-D: program will not fit into available memory. run placement with alignment fails for section "PRU1_REV2_IMEM" size 0x2000
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 21: warning #10097: memory range not found: APP_CACHED_DATA_BLK1_MEM on page 0
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 19: error #10265: no valid memory range(null) available for placement of "PRU0_REV2_EXT"
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 19: error #10099-D: program will not fit into available memory. run placement with alignment fails for section "PRU0_REV2_EXT" size 0x1000
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 34: warning #10097: memory range not found: APP_CACHED_DATA_BLK1_MEM on page 0
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 32: error #10265: no valid memory range(null) available for placement of "PRU1_REV2_EXT"
"C:/ti/pdk_am57xx_1_0_13/packages/ti/build/pruss/lnk_c66_m4_REV2.cmd", line 32: error #10099-D: program will not fit into available memory. run placement with alignment fails for section "PRU1_REV2_EXT" size 0x1000
"configPkg/linker.cmd", line 185: warning #10097: memory range not found: APP_CACHED_DATA_MEM on page 0
"configPkg/linker.cmd", line 185: error #10099-D: program will not fit into available memory. run placement with alignment fails for section ".plt" size 0x0
"configPkg/linker.cmd", line 189: warning #10097: memory range not found: APP_CACHED_DATA_MEM on page 0
"configPkg/linker.cmd", line 189: error #10099-D: program will not fit into available memory. placement with alignment fails for section "xdc.meta" size 0x100
../../master/ELFLNK/build.c:2612:internal fatal error #10251: ("xdc.meta:icss_emac_c66_wSoCLib_pe66.oe66")

INTERNAL ERROR: C:\ti\ti-cgt-c6000_8.2.2\bin\lnk6x.exe had an internal inconsistency and aborted

This is caused by a defect in the TI Linker.
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".

We need to see this ENTIRE error message and a complete, reproducable
test case including ALL of the command-line options.
Include all of the object files, libraries, and linker command files
used to link the program.


>> Compilation failure
makefile:148: recipe for target 'icss_emac_ethernet.out' failed
gmake[1]: *** [icss_emac_ethernet.out] Error 1
makefile:144: recipe for target 'all' failed
gmake: *** [all] Error 2

**** Build Finished ****

Regards

Satheesh Kumar S

Viewing all 262198 articles
Browse latest View live


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