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

CC3220: Out of the box capabilities

$
0
0

Part Number:CC3220

I am considering using the CC3220MODA  for my wifi application.  I want to be able to send simple serial AT commands and allow the CC3220 to do all the heavy lifting for network requirements.  It seems that this device has all that capability.  I will have no need to program the CC3220 onboard MCU for my purposes.  My question is does the onboard MCU in the CC3220 have the serial AT command applications/capability pre loaded (as purchased) or is it necessary to flash it.  If flashing is required, is the basic SDK for AT command control available already from TI?


CCS/TM4C1290NCPDT: TI-RTOS crashes when debugging with Segger J-Link

$
0
0

Part Number:TM4C1290NCPDT

Tool/software: Code Composer Studio

Several of us in the TivaC forum are having trouble getting the TI-RTOS demos to work using a Segger J-Link. 

Please see this thread: e2e.ti.com/.../2379267

Basically, when using an XDS100v2 or the Stelaris ICDI, we are able to program and debug successfully, but with the J-Link, TI-RTOS crashes immediately after trying to start the first task with console output along the lines of this:

DFSR = 0x00000001
MMAR = 0xe000ed34
BFAR = 0xe000ed38
AFSR = 0x00000000
Terminating execution...

It was suggested to post on this forum since they haven't had much luck replicating the problem over in the other forum.

Can anyone shed some light on this or suggest a fix?

Thanks,

Nick

CC3220MODA: Simple SPI Application

$
0
0

Part Number:CC3220MODA

Here's my application. I need to control and LCD screen using serial SPI. I cannot find the documentation that explains how to use SPI on the CC3220SF (or CC3220MODA). Can someone please either provide an simple example code for initializing and sending data, or direct me to the documentation?

CCS/MSP432P401R: new board, xds200 returns the error: "the target indicates that it is busy"

$
0
0

Part Number:MSP432P401R

Tool/software: Code Composer Studio

Hi all,

I'm using CCS 7.2.0.00013 and an XDS200 with Emulation package 7.0.48.0

I've got a factory fresh new bespoke board with an MSP432P401R rev D,

In CCS, selecting "debug" the error message returned is: "the target indicates that it is busy"

Any advice?

Thanks in advance

am5718: Driving a MIPI DSI display using the AM57x8

$
0
0

Part Number:am5718

Hi, 

We are trying to drive a MIPI DSI display.  We notice the AM57x8 has a MIPI DPI peripheral, but not DSI.  Is there a recommended bridge from either the DPI or the HDMI peripherals?  Anyone seen a reference design?

Thanks!

Blake

TMS320C6678: Inherent race condition for IPCGRx?

$
0
0

Part Number:TMS320C6678

Example code, posts on the E2E forums, and my testing all indicate that IPCGR1 and the related registers are covered by the "boot kicker" protection scheme.  Thus, any core that wants to perform IPC must unlock the boot kicker before writing to those registers, write to those registers, and perhaps re-lock the boot kicker.  Is the locking state tracked separately for each DSP core, or could DSP core 0 unlock the bootkicker but have DSP core 1 lock it before DSP core 0 writes all of the BOOTCFG registers that it intended to write?

If the locking state is global, is the preferred solution to this race condition to keep the kicker unlocked, to use some external serialization mechanism (such as the hardware semaphore module), to just not use the IPCGRx registers for IPC (e.g. using Multicore Navigator instead), or something else?  SPRS691E (the data sheet for the C6678) says to leave the kicker unlocked, but SPRS689D (the data sheet for the C6670) says to lock it after each access.

cc2650: Bluetooth LE GAP Service and appearance characteristic

$
0
0

Part Number:cc2650

I am studying a Bluetooth LE peripheral and I noticed it doesn't include the Appearance characteristic of the GAP service, just the Device Name characteristic.

If the GAP service lacks the Appearance characteristic which is mandatory in the table below, is it still Bluetooth compliance?

the device is Bluetooth LE 4.0

The only I could find in the CORE 4.0 specs is:

TPS3808: CT Pin DC level

$
0
0

Part Number:TPS3808

If the CT pin on the TPS3808 is tied to 1/2 the supply rail (that would be 1.65V in the case of Vdd = 3.3V) would the device interpret that as being pulled to Vdd and subsequently provide a 300msec delay?


RTOS/CC3220S-LAUNCHXL: UART1 on the CC3220S Launchpad (again)

$
0
0

Part Number:CC3220S-LAUNCHXL

Tool/software:TI-RTOS

I apologize for asking this question, as I know it's been addressed a couple times, but I'm still not entirely getting the UART1 on the Launchpad to work.  

I started with the MQTT example for the CC3220S using Code Composer Studio.

I changed CC3220S_LaunchXL.c to look like this:

const UARTCC32XX_HWAttrsV1 uartCC3220SHWAttrs[CC3220S_LAUNCHXL_UARTCOUNT] = {
{
.baseAddr = UARTA0_BASE,
.intNum = INT_UARTA0,
.intPriority = (~0),
.flowControl = UARTCC32XX_FLOWCTRL_NONE,
.ringBufPtr = uartCC3220SRingBuffer[CC3220S_LAUNCHXL_UART0],
.ringBufSize = sizeof(uartCC3220SRingBuffer[CC3220S_LAUNCHXL_UART0]),
.rxPin = UARTCC32XX_PIN_04_UART0_RX,
.txPin = UARTCC32XX_PIN_03_UART0_TX,
.ctsPin = UARTCC32XX_PIN_UNASSIGNED,
.rtsPin = UARTCC32XX_PIN_UNASSIGNED
},
{
.baseAddr = UARTA1_BASE,
.intNum = INT_UARTA1,
.intPriority = (~0),
.flowControl = UARTCC32XX_FLOWCTRL_NONE,
.ringBufPtr = uartCC3220SRingBuffer[CC3220S_LAUNCHXL_UART1],
.ringBufSize = sizeof(uartCC3220SRingBuffer[CC3220S_LAUNCHXL_UART1]),
.rxPin = UARTCC32XX_PIN_57_UART1_RX,
.txPin = UARTCC32XX_PIN_55_UART1_TX,
.ctsPin = UARTCC32XX_PIN_UNASSIGNED,
.rtsPin = UARTCC32XX_PIN_UNASSIGNED
}
};

I have a TTL converter on pins 57 and 55, and I verified it worked with pins 4 and 3 first (so I know the TTL converter works)

My Init Looks like this:

UART_Handle InitTerm(void)
{

UART_Params uartParams;

Board_initUART();
UART_Params_init(&uartParams);

uartParams.readMode = UART_MODE_CALLBACK;
uartParams.writeMode = UART_MODE_CALLBACK;
uartParams.writeDataMode = UART_DATA_BINARY;
uartParams.readDataMode = UART_DATA_BINARY;
uartParams.readReturnMode = UART_RETURN_FULL;
uartParams.readEcho = UART_ECHO_OFF;
uartParams.baudRate = 9600;
uartParams.dataLength = UART_LEN_8;
uartParams.stopBits = UART_STOP_ONE;
uartParams.parityType = UART_PAR_NONE;
uartParams.readCallback = &rxCallback;
uartParams.writeCallback = &wrCallback;

uartHandle = UART_open(Board_UART1, &uartParams);
UART_control(uartHandle, UART_CMD_RXDISABLE, NULL);

return(uartHandle);
}

and my Callback handlers look like this:

static int8_t count = 0;
//******************************************************************************
void wrCallback(UART_Handle uartHandle, void *pBuf, uint32_t numBytes)
{
count--;
}

//******************************************************************************
void rxCallback(UART_Handle uartHandle, void *pBuf, uint32_t numBytes)
{
count++;
}

I can never get my callbacks to work.  They never get called.  Am I forgetting to enable interrupts on that second UART?  

What am I missing?  Thank you for any help.

TPS40054: TPS40054 NRND Problem

TLC6C5712-Q1: t(Pwm) - Timing question

$
0
0

Part Number:TLC6C5712-Q1

Hello,

We have a customer who is asking about an external PWM signal to enable, and the timing requirements.

On page 7, t(pwm) - customer would like to know if the PWM edge detection allows for the full 20ms, or if the upstroke and downstroke has to happen within that 20ms (can he have a pulse width that is longer than 20ms?).

Thanks,

Compiler/TMS320DM642: Can't build a bare-bone RTSC project

$
0
0

Part Number:TMS320DM642

Tool/software: TI C/C++ Compiler

Hello,

I am trying to migrate an RTSC project that is working in CCS3.3 to CCS5.5. We use a custom board with TMS320DM642 DSP and Spectrum Digital XDS510USB emulator. At this point all I want to do is to be able to build a bare-bone RTSC "Hello World" project and then connect to the board and debug it. In the original CCS3.3 project, we used ti.platforms.evmDM642 platform. In CCS5.5, such a platform is missing, so I chose xdc.platform.generic platform.  I let the Studio' wizard create such a project for me. My complete list of project's parameters is below:

XDS Tools: 3.25.3.72

SYS/BIOS: 6.35.4.50

XDAIS: 7.21.1.07

Platform: xdc.platform.generic

Compiler version: TI v7.4.4

Device family: C6000

Device variant: DaVince DM64x TMS320DM642

I failed to build the project due to following errors:

"C:\\ti\\ccsv5\\utils\\bin\\gmake" -k all 

making ../src/sysbios.a64 ...
gmake[1]: *** No rule to make target `family/c64/Hwi.c', needed by `BIOS.obj'.
gmake[1]: *** No rule to make target `family/c64/Timer.c', needed by `BIOS.obj'.
gmake[1]: *** No rule to make target `family/c64/TimestampProvider.c', needed by `BIOS.obj'.
gmake[1]: Target `all' not remade because of errors.
gmake: *** [../src/sysbios.a64] Error 2

These errors were followed by another ones:

js: "$internal", line 25: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: can't locate the package 'undefined' along the path: 'C:/ti/bios_6_35_04_50/packages;C:/ti/xdais_7_21_01_07/packages;C:/ti/xdais_7_21_01_07/examples;C:/ti/ccsv5/ccs_base;C:/ti/xdctools_3_25_03_72/packages;..;'. Ensure that the package path is set correctly.
"./package/cfg/app_p64.cfg", line 141
gmake.exe: *** [package/cfg/app_p64.xdl] Error 1
js: "C:/ti/xdctools_3_25_03_72/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
gmake: *** [configPkg/linker.cmd] Error 1
gmake: Target `all' not remade because of errors.

Any help in resolving the errors or in fixing of my setup will be appreciated.

Thanks.

TMS320C6746: C6746 ZCE package DDR2 Layout Reference

$
0
0

Part Number:TMS320C6746

Hello,

Do you have a reference board layout for C6746 DDR2 in ZCE package? "TMS320C6748 LCDK" uses ZWT package, and since pitch is smaller on ZCE, this can't be used entirely. 

Thanks,

Mark

DS100DF410: DS100DF410 operate with FDR10 InfiniBand ?

BQ34Z100-G1: Issues on running optimization cycle.

$
0
0

Part Number:BQ34Z100-G1

Hello everyone.

We have been developing a custom board employing BQ34Z100-G1. Following the procedure stated by Bryan Kahler here (https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/643176), we are now running the optimization cycle in order to minimize the error. The procedure was found at SLUA334B document and we assumed we know the Qmax. For this cycle, we set up a test bench composed of our custom board with BQ34Z100-G1, an electronic load and an power suplpy, all controlled by a computer. After following all the steps, the impedance tracker was not able to optimize its error, keeping its maaximum error in 100%. Could you help on this issue? 

Below you can find the circuit schematic.

Thank you in advance.

Best regards,

Felipe Marques.


LAUNCHXL-CC2640R2: Pairing and bonding example

$
0
0

Part Number:LAUNCHXL-CC2640R2

I have one Launchpad programmed as a Peripheral and a second Launchpad programmed as Central. I want to make sure the connection between the two is exclusive, e.g., if I have multiple other pairs of Launchpads, I want them to be paired and do not interfere with each other. My thinking is that if I enable pairing and bonding I can do just that, making sure the pass keys are unique to each pair. The question is how exactly do I do that?

I modified the Central device by changing the constants in simple_central.c:

// Default GAP pairing mode
#define DEFAULT_PAIRING_MODE                  GAPBOND_PAIRING_MODE_INITIATE

// Default MITM mode (TRUE to require passcode or OOB when pairing)
#define DEFAULT_MITM_MODE                     TRUE

// Default bonding mode, TRUE to bond
#define DEFAULT_BONDING_MODE                  TRUE

Is this enough? 

Once I made those changes I am able to make the two devices to communicate the same way as before. I sniffed the communication between the two with the CC2540 dongle, and it shows that Security is enabled. It also shows the decrypted L2CAP payload and that is the part that confuses me. How can the sniffer decrypt the payload if I never provided the key? I understand I am using the default key "123456", but I would still expect the sniffer to not decypher the payload. Is the security enabling enough to avoid crosstalk among multiple networks (I do not have more Launchpads to test that concept...). 

Thanks for the help!

Compiler/CC-DEBUGGER: Connect to CC-Debugger

$
0
0

Part Number:CC-DEBUGGER

Tool/software: TI C/C++ Compiler

Hello. 

I design a board use CC2530 and i program with CC debugger. i want to test my load program block , what connect to CC Debugger.

I soldered the components necessary as in CC Debugger User' Guide, no more. Of course, i soldered IC CC2530.

My question is:

I just test my load program block. Do I need to solder the crystal, R301 and C401 as in the datasheet of the cc2530?

TUSB8041EVM: Request for TUSB8041EVM reference design layout

$
0
0

Part Number:TUSB8041EVM

TI Customer Support suggested I post here to obtain reference design files. Could someone email me the board layout, schematic, BOM, etc. for the TUSB8041EVM Evaluation Module? If available for OrCAD, that would be great. Much appreciated!

CCS/CC3220SF-LAUNCHXL: cc3220sf

$
0
0

Part Number:CC3220SF-LAUNCHXL

Tool/software: Code Composer Studio

what is this warring?

how to handle with it?

Description Resource Path Location Type
This project contains 1 unresolved buildable linked resource(s). The project may not build as expected. WiFiCoordinator project Problems

CC1120EM-868-915-RD: CC1120EM-868-915-RD

$
0
0

Part Number:CC1120EM-868-915-RD

Hi. I am using cadstar design viewer to look at the design files for the EVM. I am interested in the layout for reference/ But for the .pcb file, I am only able to view the placement. I am not able to see any layers or the routing. Are all the files included in the swrc222 project or am I not using the viewer the right way. 

I only have experience with Candence allegro and Alitum. So was wondering if  I can get any tips on how to view the layout for this board. 

-Thanks

Viewing all 262198 articles
Browse latest View live


Latest Images

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