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

CCS: include for PRU in CCSV6

$
0
0

Tool/software: Code Composer Studio

Hi everyone,

I have already add the PRU compiler in the CCSv6, but some includes isn`t working and I don't know how it solve.

this is the message of the debug console:

"..\resource_table_empty.h", line 54: fatal error #1965: cannot open source file "rsc_types.h"

"../main.c", line 6: fatal error #1965: cannot open source file "pru_cfg.h"

anyone could help me please, I'm a noob in RTO programming.

Thanks

Jaime


TPS53667: RESET pin connection when this pin feature is not used

$
0
0

Part Number:TPS53667

How should we connect RESET pin of TPS53667 when this is not used?

Can we pull up and keep high level?

Best Regards,
Kohei Sasaki

TPS4H160-Q1: Power and ground protection

$
0
0

Part Number:TPS4H160-Q1

Hi,

I'm designing a pcb which is supposed to generate 24V outputs controlled by a microcontroller. As those outputs go to external devices, I want to protect my circuit against external problems such as short circuits polarity inversion ... My question is about the isolation of the ground because I don't know if I'm suppose to have separated ground between my microcontroller and the power outputs and how to connect it each over with a diode or something else. Something else I think it's strange that there is no input capacitors.

Thanks

cc2541: cc2541

$
0
0

Part Number:cc2541

I am using cc2541. I am working on interrupt . i want to call interrupt when pin (low) but my code works when i change the state it miss some time.. but i want when there is constant low on pin then interrupt call.. where i should change? Cade is given below

/******************************************************************************

@file hal_key.c

@brief This file contains the interface to the HAL KEY Service.

Group: WCS, BTS
Target Device: CC2540, CC2541

******************************************************************************

Copyright (c) 2006-2016, Texas Instruments Incorporated
All rights reserved.

IMPORTANT: Your use of this Software is limited to those specific rights
granted under the terms of a software license agreement between the user
who downloaded the software, his/her employer (which must be your employer)
and Texas Instruments Incorporated (the "License"). You may not use this
Software unless you agree to abide by the terms of the License. The License
limits your use, and you acknowledge, that the Software may not be modified,
copied or distributed unless embedded on a Texas Instruments microcontroller
or used solely and exclusively in conjunction with a Texas Instruments radio
frequency transceiver, which is integrated into your product. Other than for
the foregoing purpose, you may not use, reproduce, copy, prepare derivative
works of, modify, distribute, perform, display or sell this Software and/or
its documentation for any purpose.

YOU FURTHER ACKNOWLEDGE AND AGREE THAT THE SOFTWARE AND DOCUMENTATION ARE
PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY, TITLE,
NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL
TEXAS INSTRUMENTS OR ITS LICENSORS BE LIABLE OR OBLIGATED UNDER CONTRACT,
NEGLIGENCE, STRICT LIABILITY, CONTRIBUTION, BREACH OF WARRANTY, OR OTHER
LEGAL EQUITABLE THEORY ANY DIRECT OR INDIRECT DAMAGES OR EXPENSES
INCLUDING BUT NOT LIMITED TO ANY INCIDENTAL, SPECIAL, INDIRECT, PUNITIVE
OR CONSEQUENTIAL DAMAGES, LOST PROFITS OR LOST DATA, COST OF PROCUREMENT
OF SUBSTITUTE GOODS, TECHNOLOGY, SERVICES, OR ANY CLAIMS BY THIRD PARTIES
(INCLUDING BUT NOT LIMITED TO ANY DEFENSE THEREOF), OR OTHER SIMILAR COSTS.

Should you have any questions regarding your right to use this Software,
contact Texas Instruments Incorporated at www.TI.com.

******************************************************************************
Release Name: ble_sdk_1.4.2.2
Release Date: 2016-06-09 06:57:09
*****************************************************************************/
/*********************************************************************
NOTE: If polling is used, the hal_driver task schedules the KeyRead()
to occur every 100ms. This should be long enough to naturally
debounce the keys. The KeyRead() function remembers the key
state of the previous poll and will only return a non-zero
value if the key state changes.

NOTE: If interrupts are used, the KeyRead() function is scheduled
25ms after the interrupt occurs by the ISR. This delay is used
for key debouncing. The ISR disables any further Key interrupt
until KeyRead() is executed. KeyRead() will re-enable Key
interrupts after executing. Unlike polling, when interrupts
are enabled, the previous key state is not remembered. This
means that KeyRead() will return the current state of the keys
(not a change in state of the keys).

NOTE: If interrupts are used, the KeyRead() fucntion is scheduled by
the ISR. Therefore, the joystick movements will only be detected
during a pushbutton interrupt caused by S1 or the center joystick
pushbutton.

NOTE: When a switch like S1 is pushed, the S1 signal goes from a normally
high state to a low state. This transition is typically clean. The
duration of the low state is around 200ms. When the signal returns
to the high state, there is a high likelihood of signal bounce, which
causes a unwanted interrupts. Normally, we would set the interrupt
edge to falling edge to generate an interrupt when S1 is pushed, but
because of the signal bounce, it is better to set the edge to rising
edge to generate an interrupt when S1 is released. The debounce logic
can then filter out the signal bounce. The result is that we typically
get only 1 interrupt per button push. This mechanism is not totally
foolproof because occasionally, signal bound occurs during the falling
edge as well. A similar mechanism is used to handle the joystick
pushbutton on the DB. For the EB, we do not have independent control
of the interrupt edge for the S1 and center joystick pushbutton. As
a result, only one or the other pushbuttons work reasonably well with
interrupts. The default is the make the S1 switch on the EB work more
reliably.

*********************************************************************/

/**************************************************************************************************
* INCLUDES
**************************************************************************************************/
#include "hal_mcu.h"
#include "hal_defs.h"
#include "hal_types.h"
#include "hal_drivers.h"
#include "hal_adc.h"
#include "hal_key.h"
#include "osal.h"

#if (defined HAL_KEY) && (HAL_KEY == TRUE)

/**************************************************************************************************
* CONSTANTS
**************************************************************************************************/
#define HAL_KEY_RISING_EDGE 0
#define HAL_KEY_FALLING_EDGE 1

#define HAL_KEY_DEBOUNCE_VALUE 25

/* CPU port interrupt */
#define HAL_KEY_CPU_PORT_1_IF P1IF

#if defined ( CC2540_MINIDK )
/* SW_1 is at P1.5 */
#define HAL_KEY_SW_1_PORT P1
#define HAL_KEY_SW_1_BIT BV(5)
#define HAL_KEY_SW_1_SEL P1SEL
#define HAL_KEY_SW_1_DIR P1DIR

/* SW_2 is at P1.6 */
#define HAL_KEY_SW_2_PORT P1
#define HAL_KEY_SW_2_BIT BV(6)
#define HAL_KEY_SW_2_SEL P1SEL
#define HAL_KEY_SW_2_DIR P1DIR

/* SW_3 is at P1.7 */
#define HAL_KEY_SW_3_PORT P1
#define HAL_KEY_SW_3_BIT BV(7)
#define HAL_KEY_SW_3_SEL P1SEL
#define HAL_KEY_SW_3_DIR P1DIR

#define HAL_KEY_SW_1_IEN IEN2 /* CPU interrupt mask register */
#define HAL_KEY_SW_1_ICTL P1IEN /* Port Interrupt Control register */
#define HAL_KEY_SW_1_ICTLBIT BV(5) /* P1IEN - P1.5 enable/disable bit */
#define HAL_KEY_SW_1_IENBIT BV(4) /* Mask bit for all of Port_1 */
#define HAL_KEY_SW_1_PXIFG P1IFG /* Interrupt flag at source */


#define HAL_KEY_SW_2_IEN IEN2 /* CPU interrupt mask register */
#define HAL_KEY_SW_2_ICTL P1IEN /* Port Interrupt Control register */
#define HAL_KEY_SW_2_ICTLBIT BV(6) /* P1IEN - P1.6 enable/disable bit */
#define HAL_KEY_SW_2_IENBIT BV(4) /* Mask bit for all of Port_1 */
#define HAL_KEY_SW_2_PXIFG P1IFG /* Interrupt flag at source */


#define HAL_KEY_SW_3_IEN IEN2 /* CPU interrupt mask register */
#define HAL_KEY_SW_3_ICTL P1IEN /* Port Interrupt Control register */
#define HAL_KEY_SW_3_ICTLBIT BV(7) /* P1IEN - P1.7 enable/disable bit */
#define HAL_KEY_SW_3_IENBIT BV(4) /* Mask bit for all of Port_1 */
#define HAL_KEY_SW_3_PXIFG P1IFG /* Interrupt flag at source */


#define HAL_KEY_SW_1_EDGEBIT BV(0)


#endif

/**************************************************************************************************
* TYPEDEFS
**************************************************************************************************/


/**************************************************************************************************
* GLOBAL VARIABLES
**************************************************************************************************/
static uint8 halKeySavedKeys; /* used to store previous key state in polling mode */
static halKeyCBack_t pHalKeyProcessFunction;
static uint8 HalKeyConfigured;
bool Hal_KeyIntEnable; /* interrupt enable/disable flag */

/**************************************************************************************************
* FUNCTIONS - Local
**************************************************************************************************/
void halProcessKeyInterrupt(void);

/**************************************************************************************************
* FUNCTIONS - API
**************************************************************************************************/


/**************************************************************************************************
* @fn HalKeyInit
*
* @brief Initilize Key Service
*
* @param none
*
* @return None
**************************************************************************************************/
void HalKeyInit( void )
{
halKeySavedKeys = 0; // Initialize previous key to 0.

#if defined ( CC2540_MINIDK )
HAL_KEY_SW_1_SEL &= ~(HAL_KEY_SW_1_BIT); /* Set pin function to GPIO */
HAL_KEY_SW_1_DIR &= ~(HAL_KEY_SW_1_BIT); /* Set pin direction to Input */
HAL_KEY_SW_2_SEL &= ~(HAL_KEY_SW_2_BIT); /* Set pin function to GPIO */
HAL_KEY_SW_2_DIR &= ~(HAL_KEY_SW_2_BIT); /* Set pin direction to Input */
HAL_KEY_SW_3_SEL &= ~(HAL_KEY_SW_3_BIT); /* Set pin function to GPIO */
HAL_KEY_SW_3_DIR &= ~(HAL_KEY_SW_3_BIT); /* Set pin direction to Input */
#endif

/* Initialize callback function */
pHalKeyProcessFunction = NULL;

/* Start with key is not configured */
HalKeyConfigured = FALSE;

#if defined ( CC2540_MINIDK )
/* Rising/Falling edge configuratinn */
PICTL |= HAL_KEY_SW_1_EDGEBIT; /* Set the edge bit to set falling edge to give int */
HAL_KEY_SW_1_IEN |= ( HAL_KEY_SW_1_IENBIT | HAL_KEY_SW_2_IENBIT |HAL_KEY_SW_3_IENBIT); /* enable CPU interrupt */
#endif
}


/**************************************************************************************************
* @fn HalKeyConfig
*
* @brief Configure the Key serivce
*
* @param interruptEnable - TRUE/FALSE, enable/disable interrupt
* cback - pointer to the CallBack function
*
* @return None
**************************************************************************************************/
void HalKeyConfig (bool interruptEnable, halKeyCBack_t cback)
{
/* Enable/Disable Interrupt or */
Hal_KeyIntEnable = interruptEnable;

/* Register the callback fucntion */
pHalKeyProcessFunction = cback;

/* Determine if interrupt is enable or not */
if (Hal_KeyIntEnable)
{
#if defined ( CC2540_MINIDK )
HAL_KEY_SW_1_ICTL |= HAL_KEY_SW_1_ICTLBIT; /* enable interrupt generation at port */
HAL_KEY_SW_1_PXIFG = ~(HAL_KEY_SW_1_BIT); /* Clear any pending interrupt */
HAL_KEY_SW_2_ICTL |= HAL_KEY_SW_2_ICTLBIT; /* enable interrupt generation at port */
HAL_KEY_SW_2_PXIFG = ~(HAL_KEY_SW_2_BIT); /* Clear any pending interrupt */
HAL_KEY_SW_3_ICTL |= HAL_KEY_SW_3_ICTLBIT; /* enable interrupt generation at port */
HAL_KEY_SW_3_PXIFG = ~(HAL_KEY_SW_3_BIT); /* Clear any pending interrupt */
/* Interrupt configuration:
* - Enable interrupt generation at the port
* - Enable CPU interrupt
* - Clear any pending interrupt
*/
#endif // !CC2540_MINIDK

/* Do this only after the hal_key is configured - to work with sleep stuff */
if (HalKeyConfigured == TRUE)
{
osal_stop_timerEx(Hal_TaskID, HAL_KEY_EVENT); /* Cancel polling if active */
}
}
else /* Interrupts NOT enabled */
{
#if defined ( CC2540_MINIDK )
HAL_KEY_SW_1_ICTL &= ~(HAL_KEY_SW_1_ICTLBIT); /* don't generate interrupt */
HAL_KEY_SW_2_ICTL &= ~(HAL_KEY_SW_2_ICTLBIT); /* don't generate interrupt */
HAL_KEY_SW_3_ICTL &= ~(HAL_KEY_SW_3_ICTLBIT); /* don't generate interrupt */
#endif // !CC2540_MINIDK

osal_set_event(Hal_TaskID, HAL_KEY_EVENT);
}

/* Key now is configured */
HalKeyConfigured = TRUE;
}


/**************************************************************************************************
* @fn HalKeyRead
*
* @brief Read the current value of a key
*
* @param None
*
* @return keys - current keys status
**************************************************************************************************/
uint8 HalKeyRead ( void )
{
uint8 keys = 0;

#if defined (CC2540_MINIDK)
if (!(HAL_KEY_SW_1_PORT & HAL_KEY_SW_1_BIT)) /* Key is active low */
{
keys |= HAL_KEY_SW_1;
}
if (!(HAL_KEY_SW_2_PORT & HAL_KEY_SW_2_BIT)) /* Key is active low */
{
keys |= HAL_KEY_SW_2;
}
if (!(HAL_KEY_SW_3_PORT & HAL_KEY_SW_3_BIT)) /* Key is active low */
{
keys |= HAL_KEY_SW_3;
}
#endif
return keys;
}


/**************************************************************************************************
* @fn HalKeyPoll
*
* @brief Called by hal_driver to poll the keys
*
* @param None
*
* @return None
**************************************************************************************************/
void HalKeyPoll (void)
{
uint8 keys = 0;
uint8 notify = 0;
#if defined (CC2540_MINIDK)
if (!(HAL_KEY_SW_1_PORT & HAL_KEY_SW_1_BIT)) /* Key is active low */
{
keys |= HAL_KEY_SW_1;
}
if (!(HAL_KEY_SW_2_PORT & HAL_KEY_SW_2_BIT)) /* Key is active low */
{
keys |= HAL_KEY_SW_2;
}
if (!(HAL_KEY_SW_3_PORT & HAL_KEY_SW_3_BIT)) /* Key is active low */
{
keys |= HAL_KEY_SW_3;
}
#endif

/* If interrupts are not enabled, previous key status and current key status
* are compared to find out if a key has changed status.
*/
if (!Hal_KeyIntEnable)
{
if (keys == halKeySavedKeys)
{
/* Exit - since no keys have changed */
return;
}
else
{
notify = 1;
}
}
else
{
/* Key interrupt handled here */
if (keys)
{
notify = 1;
}
}

/* Store the current keys for comparation next time */
halKeySavedKeys = keys;

/* Invoke Callback if new keys were depressed */
if (notify && (pHalKeyProcessFunction))
{
(pHalKeyProcessFunction) (keys, HAL_KEY_STATE_NORMAL);

}
}


/**************************************************************************************************
* @fn halProcessKeyInterrupt
*
* @brief Checks to see if it's a valid key interrupt, saves interrupt driven key states for
* processing by HalKeyRead(), and debounces keys by scheduling HalKeyRead() 25ms later.
*
* @param
*
* @return
**************************************************************************************************/
void halProcessKeyInterrupt (void)
{
bool valid=FALSE;

#if defined ( CC2540_MINIDK )
if( HAL_KEY_SW_1_PXIFG & HAL_KEY_SW_1_BIT) /* Interrupt Flag has been set by SW1 */
{
HAL_KEY_SW_1_PXIFG = ~(HAL_KEY_SW_1_BIT); /* Clear Interrupt Flag */
valid = TRUE;
}
if (HAL_KEY_SW_2_PXIFG & HAL_KEY_SW_2_BIT) /* Interrupt Flag has been set by SW2 */
{
HAL_KEY_SW_2_PXIFG = ~(HAL_KEY_SW_2_BIT); /* Clear Interrupt Flag */
valid = TRUE;
}
if (HAL_KEY_SW_3_PXIFG & HAL_KEY_SW_3_BIT) /* Interrupt Flag has been set by SW3 */
{
HAL_KEY_SW_3_PXIFG = ~(HAL_KEY_SW_3_BIT); /* Clear Interrupt Flag */
valid = TRUE;
}
#endif
if (valid)
{
osal_start_timerEx (Hal_TaskID, HAL_KEY_EVENT, HAL_KEY_DEBOUNCE_VALUE);
}
}

/**************************************************************************************************
* @fn HalKeyEnterSleep
*
* @brief - Get called to enter sleep mode
*
* @param
*
* @return
**************************************************************************************************/
void HalKeyEnterSleep ( void )
{
}

/**************************************************************************************************
* @fn HalKeyExitSleep
*
* @brief - Get called when sleep is over
*
* @param
*
* @return - return saved keys
**************************************************************************************************/
uint8 HalKeyExitSleep ( void )
{
/* Wake up and read keys */
return ( HalKeyRead () );
}

/***************************************************************************************************
* INTERRUPT SERVICE ROUTINE
***************************************************************************************************/

/**************************************************************************************************
* @fn halKeyPort0Isr
*
* @brief Port0 ISR
*
* @param
*
* @return
**************************************************************************************************/
HAL_ISR_FUNCTION( halKeyPort1Isr, P1INT_VECTOR )
{


HAL_ENTER_ISR();

#if defined ( CC2540_MINIDK )
if ((HAL_KEY_SW_1_PXIFG & HAL_KEY_SW_1_BIT) || (HAL_KEY_SW_2_PXIFG & HAL_KEY_SW_2_BIT) || (HAL_KEY_SW_3_PXIFG & HAL_KEY_SW_3_BIT) )
#endif
{
halProcessKeyInterrupt();
}

/*
Clear the CPU interrupt flag for Port_0
PxIFG has to be cleared before PxIF
*/
#if defined ( CC2540_MINIDK )
HAL_KEY_SW_1_PXIFG = 0;
HAL_KEY_SW_2_PXIFG = 0;
HAL_KEY_SW_3_PXIFG = 0;
#endif
HAL_KEY_CPU_PORT_1_IF = 0;

CLEAR_SLEEP_MODE();

HAL_EXIT_ISR();

return;
}
#else

void HalKeyInit(void){}
void HalKeyConfig(bool interruptEnable, halKeyCBack_t cback){}
uint8 HalKeyRead(void){ return 0;}
void HalKeyPoll(void){}

#endif
/**************************************************************************************************
**************************************************************************************************/

FDC2214: Target distance vs resolution of device (FDC22xx, FDC21xx)

$
0
0

Part Number:FDC2214

Hi

Our customer are considering FDCxxxx devices. I found some graphs on the datasheet I do not understand.

On figure 62, there are some curves at each of the output rate. Which is FDC22xx? or FDC21xx? or Both?


In my understanding, the distances and precision are determined by the resolution and sample rate if it is at same condition (same sensor and environments).

Is my understanding correct?

Regards,

Koji Hamamoto

OPT8241: Sensor cleaning method

$
0
0

Part Number:OPT8241

Please help confirm whether the TI original packaging OPT8241 / surface stain / surface scratches the inspection conditions and standard specifications of the information document can provide?
And the following 2 questions to confirm:
(1) if sensor is dirty, the original factory recommended cleaning methods and cleaning solution?
(2) In order to avoid dust and scratches on the sensor surface, can Sensor be shipped with a protective film of Sensor (pass ir reflowable and adhesive-free) on the sensor surface?

TCAN1043-Q1: Difference between TCAN1043-Q1 and TCAN1042-Q1

RTOS: How to use the EVE ?

$
0
0

Tool/software:TI-RTOS

Hi:

   I'm making a chain under the framework TI VisionSDK , the SOC is TDA2XX ;I read through all the documents under the path "PROCESSOR_SDK_VISION_03_02_00_00\vision_sdk\docs" but the question is ,how to use the EVE ? is there guideline or specification on program for EVE ?


PCM2903C: Asking for the PCM2903C routing

$
0
0

Part Number:PCM2903C

Hi Team,
Can PCM2903C support the following routing?
1. USB in -> SPDIF output
2. SPDIF in -> SPDIF output, If this is not possible, any workaround by external circuit?


Thanks,
SHH

DRV8662: Automotive version

$
0
0

Part Number:DRV8662

Hi,

Let me confirm about DRV8662 and DRV2700.

Do you have "Q1" products of DRV8662/2700 or other piezo Haptics drivers for Q1?

Can I understand that there are no Q1 products about piezo Haptics drivers?  

Thank you and Best Regards,

Takumi

TMS570LS1114: Bootloader PC 端代码@QJ Wang

RTOS/LINUXSDK-OMAPL138: DSPLINK 1_65_01_06 cache/memory corruption issue in sma pool handle structure

$
0
0

Part Number:LINUXSDK-OMAPL138

Tool/software:TI-RTOS

Hi Ti guys,

 

We have an issue in the DSPLINK dsp side.
The context:

- A pool of buffers with different buffer sizes

- The DSP is sending messages (with different buffer sizes: 128 Bytes, 256 Bytes...) to the ARM using the message queue.

- Messages "users" in DSP side don't have the same priority.


We find a bug in the following file:

dsp/src/pools/DspBios/sma_pool.c:SMAPOOL_alloc (....) or SMAPOOL_free (....)

I will only cover the ALLOC case(same as FREE case issue)


When a thread is allocating a buffer of 128 Bytes, and this thread is interrupted after "bufHandle[i].freeBuffers-- ;" (Line 273) by a thread which wants to use a buffer of 256 Bytes, this second thread will invalidate "bufHandle[i]" (Line 252) causing a memory corruption/mismatch on the 128 Bytes structure as the write back has not been done yet on it.

SMAPOOL_alloc (....)

{

.....

    HAL_cacheInv ((Ptr) bufHandle, sizeof (SMAPOOL_BufObj)) ; << This line !!!

    for (i = 0 ; i < smaCtrl->ctrlPtr.numBufs ; i++ ) {
        if (smaCtrl->exactMatchReq == FALSE) {
            /* Look for the nearest match for the requested size */
            if (bufHandle[i].size >= size) {
                /* Found a match for required size. */
                break ;
            }
        }
        else {
            /* Look for the exact match for the requested size */
            if (bufHandle[i].size == size) {
                    /* Found a match for required size. */
                break ;
            }

        HAL_cacheInv ((Ptr) &bufHandle [i], sizeof (SMAPOOL_BufObj)) ; << This line !!!
        }
    }

 

We don't understand why there are invalidations here as the size is fixed during all pool life.

Could you advise ? Can we safely remove these 2 invalidations (same in SMAPOOL_free(...) ) or is there a reason to have these invalidations ?

 

 

TPS61175: Enable voltage is not the same as datasheet

$
0
0

Part Number:TPS61175

Hi Expert,

When we testing the enable voltage of TPS61175, we found SW start to generate PWM when VEN=0.85V, which is lower than minimum threshold voltage 1.2V.

Is there anything wrong for schematic? How could I determine what is the enable voltage?

Schematic:

Capture: CH1: EN pin; CH2: SW pin

Thanks.

Zhou

RTOS: Vision SDK -OOM issue ( usecase camera + display server )

$
0
0

Tool/software:TI-RTOS

Hello all,

We are using dra7xx customized board having 1 GB ram.We are using vision SDK for UseCase-camera & as display-server.

We are facing oom issue.  Can i reduce the vsdk_sr1_memory size ? What is the minimal  memory size required  for each region  to execute my usecase?

&reserved_mem {
cmem_ocmc: cmem@40300000 {
compatible = "shared-dma-pool";
reg = <0x0 0x40300000 0x0 0x300000>;
sram = <&ocmcram1>;
no-map;
status = "okay";
};

cmem_pool: cmem@A9000000 {
compatible = "shared-dma-pool";
reg = <0x0 0xA9000000 0x0 0x4000000>;
no-map;
status = "okay";
};

vsdk_sr1_mem: vsdk_sr1_mem@84000000 {
compatible = "shared-dma-pool";
reg = <0x0 0x84000000 0x0 0x10000000>;
status = "okay";
};

vsdk_sr0_mem: vsdk_sr0_mem@A0000000 {
compatible = "shared-dma-pool";
reg = <0x0 0xA0000000 0x0 0x1000000>;
status = "okay";
};

vsdk_eve_mem: vsdk_eve_mem@A5000000 {
compatible = "shared-dma-pool";
reg = <0x0 0xA5000000 0x0 0x4000000>;
status = "okay";
};

Regards,

Gokul

BOOSTXL-CC2650MA: Programming BOOSTXL-CC2650MA

$
0
0

Part Number:BOOSTXL-CC2650MA

Hello,

I am trying to use the BOOSTXL-CC2650MA booster pack with a C2000 Delfino MCUs F28379D LaunchPad Development Kit.

I checked with the booster pack checker, and it says that the devices are compatible.

The question is, how can I program the booster pack? Is a SimpleLink CC2650 wireless MCU LaunchPad needed for it?

I am trying to receive data form a cycling power meter...

Thanks in advance,

Imanol


hot swap with I2C survey closet solution

$
0
0

Max current rating:18A

Input/output voltage: 12V

Maximum input rating : 50V above(we need to have OVP function to prevent customer plug wrong power level that over 12V)

With I2C interface, where we can get the management information such as current information, failure status.

With address pin.

Temp: -55~150 ℃

CC3220S-LAUNCHXL: Confirm OTA tar file structure

$
0
0

Part Number:CC3220S-LAUNCHXL

Dear TI,

Could you please confirm, if the .tar file structure on page 19 in the following document is up to date. 

http://www.ti.com/lit/an/swra510/swra510.pdf

I used Uniflash 4.2.2.1692 to generate OTA image and it gave a different folder contents. In the .tar file generated by Uniflash the only file in folder "1" is dummy-trusted-ca-cert. Also, there are 3 certificates in folder "2". 

Thanks,

David

RTOS/AM4377: implementation BiSS-C singleturn 16bit + multiturn 16bit on PRU

$
0
0

Part Number:AM4377

Tool/software:TI-RTOS

Dear Champs,

My customer found there was an BiSS-C singleturn 18-bit implementation on TIDEP0022 and is trying to implement singleturn 16bit + multiturn 16bit.

Is it possible to implement singleturn 16bit + multiturn 16bit on PRU of AM4377?

If so, could you please provide a guidance how they can implement singleturn 16bit + multiturn 16bit using TIDEP0022 and where should be modified on PRU SW?

Thanks and Best Regards,

SI.

Linux/DLPC6401: Input Configuration of DLPC6401

$
0
0

Part Number:DLPC6401

Tool/software: Linux

Hello Support team,

We are working on one product design, where we need help from your side.

For this product, we are using SN65DSI83 for DSI-to-LVDS output and the output from SN65DSI83 is given to DLPC6401.

1. For the video parameters like Horizontal, Vertical Sync, etc... we need to set these parameters according to DLPC6401 controller for resolution of 1280*800.

We set the video parameters as follows :

1. CHA_ACTIVE_LINE_LENGTH = 1280 or 0x500
2. CHA_VERTICAL_DISPLAY_SIZE = 800 or 0x320
3. CHA_HSYNC_PULSE_WIDTH = 80 or 0x050
4. CHA_VSYNC_PULSE_WIDTH = 9
5. CHA_SYNC_DELAY = 32
6. CHA_HORIZONTAL_BACK_PORCH = 40
7. CHA_VERTICAL_BACK_PORCH = 7
8. CHA_HORIZONTAL_FRONT_PORCH = 40
9. CHA_VERTICAL_FRONT_PORCH = 7
10. LVDS_CLK_RANGE = 62 MHz to 87.5 MHz
11. DSI_CLK_DIVIDER = 3
12. CHA_DSI_LANES = 4
13. CHA_DSI_CLK_RANGE = 430 to 435 MHz
14. CHA_24BPP_MODE = 24bpp mode (format 2)

  but in DLPC6401 data sheet -Section 7.3.1.5  they have mentioned different data for video parameters.

So we need to know about video parameters for 1280 x 800 resolution that we have to configured  to send data to DLPC6401 controller.
1. Horizontal and Vertical Sync Pulse
2. Sync Delay for Horizontal and Vertical Sync
3. Front and Back porch for Horizontal and Vertical Sync

Thanks,

Nilesh Patil

TSW1400EVM: Continuous raw ADC data using TSW1400EVM

$
0
0

Part Number:TSW1400EVM

Currently I am working with the  AWR1642 radar module,TSW1400EVM and MMDEVpack. 

With a small test set-up with corner reflectors, I am able to transmit and receive chirps for 10 seconds as mentioned in the radar studio user guide. With this, I am  also able to collect the ADC data and store it in bin/CSV file. But every time, I need to hit TSW1400 ARM and Trigger frame buttons in HSDCPro GUI in order to capture the raw ADC data. Keeping this in mind, I have mainly two questions,

1)  Is there any way to collect the ADC data in real time without hitting the buttons TSW1400 ARM and Trigger frame?

2) Can the continuous streaming tab in Radar API be used for capturing the data for more than 10 seconds in a row?

It would be really helpful if someone can help me out in clearing my queries. Looking forward for your reply. Thank you in advance for your time.

Viewing all 262198 articles
Browse latest View live


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