Part Number:TDA2PXEVM
Tool/software: Linux
Hi,
The usecase is below.
I'd like to check the disparity map working well or not using still images which is right and left view image.
NullSrc(A15) -> Alg_Census(EVE) -> Alg_DisparityHamDist(EVE) -> Alg_StereoPostProcess(DSP) -> Display_Disparity(IPU)
The NullSrc is 2 channels, right and left image.
Is this usecase possible?
Regards,
Heechang
Part Number:IWR1443
My customer started their board design based on IWR1443BOOST.
Customer found there are some mismatches in decoupling capacitor values between IWR1443BOOST and HardwareDesignChecklist(SWRR150).
Which ones are right values?
Thanks and regards,
KoT
Part Number:UCC28881
TI tida-01097 single firewire communication chip is bluetooth, is it feasible to use sub-1g chip si4432 (sending data working current in 35ma/10ms)?
Is there a good suggestion that a capacitor be added before LDO?
How to select capacitance?
Thankyou very much.
Part Number:TMS320F28335
Hello ,
I am using TMS320F28335 evaluation board and I was hoping to decode the PPM signals using the ecap where it could give me the high time of the signal. I tried the example program of ecap_capture with PWM, it wasn't working. I am not sure why? I connected GPIO0 to GPIO34 as mentioned in the comments. If there is any alternate way to do this, please let me know. Also, do check the code i'm pasting below. it is the same example program but it wouldn't work. Also, you could suggest me if there is any hardware connections that has to be made apart from the GPIO pins.
// TI File $Revision: /main/8 $
// Checkin $Date: April 21, 2008 15:41:29 $
//###########################################################################
//
// FILE: Example_2833xECap_Capture_Pwm.c
//
// TITLE: Capture EPWM3.
//
// ASSUMPTIONS:
//
// This program requires the DSP2833x header files.
//
// Make the following external connection:
// EPWM3 on GPIO4 should be connected to ECAP1 on GPIO24.
//
// As supplied, this project is configured for "boot to SARAM"
// operation. The 2833x Boot Mode table is shown below.
// For information on configuring the boot mode of an eZdsp,
// please refer to the documentation included with the eZdsp,
//
// $Boot_Table:
//
// GPIO87 GPIO86 GPIO85 GPIO84
// XA15 XA14 XA13 XA12
// PU PU PU PU
// ==========================================
// 1 1 1 1 Jump to Flash
// 1 1 1 0 SCI-A boot
// 1 1 0 1 SPI-A boot
// 1 1 0 0 I2C-A boot
// 1 0 1 1 eCAN-A boot
// 1 0 1 0 McBSP-A boot
// 1 0 0 1 Jump to XINTF x16
// 1 0 0 0 Jump to XINTF x32
// 0 1 1 1 Jump to OTP
// 0 1 1 0 Parallel GPIO I/O boot
// 0 1 0 1 Parallel XINTF boot
// 0 1 0 0 Jump to SARAM <- "boot to SARAM"
// 0 0 1 1 Branch to check boot mode
// 0 0 1 0 Boot to flash, bypass ADC cal
// 0 0 0 1 Boot to SARAM, bypass ADC cal
// 0 0 0 0 Boot to SCI-A, bypass ADC cal
// Boot_Table_End$
//
// DESCRIPTION:
//
// This example configures ePWM3A for:
// - Up count
// - Period starts at 2 and goes up to 1000
// - Toggle output on PRD
//
// eCAP1 is configured to capture the time between rising
// and falling edge of the PWM3A output.
//
//###########################################################################
// $TI Release: DSP2833x/DSP2823x Header Files V1.20 $
// $Release Date: August 1, 2008 $
//###########################################################################
#include "DSP28x_Project.h" // Device Headerfile and Examples Include File
// Configure the start/end period for the timer
#define PWM3_TIMER_MIN 10
#define PWM3_TIMER_MAX 8000
// Prototype statements for functions found within this file.
interrupt void ecap1_isr(void);
void InitECapture(void);
void InitEPwmTimer(void);
void Fail(void);
// Global variables used in this example
Uint32 ECap1IntCount;
Uint32 ECap1PassCount;
Uint32 EPwm3TimerDirection;
// To keep track of which way the timer value is moving
#define EPWM_TIMER_UP 1
#define EPWM_TIMER_DOWN 0
void main(void)
{
// Step 1. Initialize System Control:
// PLL, WatchDog, enable Peripheral Clocks
// This example function is found in the DSP2833x_SysCtrl.c file.
InitSysCtrl();
// Step 2. Initalize GPIO:
// This example function is found in the DSP2833x_Gpio.c file and
// illustrates how to set the GPIO to it's default state.
// InitGpio(); // Skipped for this example
InitEPwm3Gpio();
InitECap1Gpio();
// Step 3. Clear all interrupts and initialize PIE vector table:
// Disable CPU interrupts
DINT;
// Initialize the PIE control registers to their default state.
// The default state is all PIE interrupts disabled and flags
// are cleared.
// This function is found in the DSP2833x_PieCtrl.c file.
InitPieCtrl();
// Disable CPU interrupts and clear all CPU interrupt flags:
IER = 0x0000;
IFR = 0x0000;
// Initialize the PIE vector table with pointers to the shell Interrupt
// Service Routines (ISR).
// This will populate the entire table, even if the interrupt
// is not used in this example. This is useful for debug purposes.
// The shell ISR routines are found in DSP2833x_DefaultIsr.c.
// This function is found in DSP2833x_PieVect.c.
InitPieVectTable();
// Interrupts that are used in this example are re-mapped to
// ISR functions found within this file.
EALLOW; // This is needed to write to EALLOW protected registers
PieVectTable.ECAP1_INT = &ecap1_isr;
EDIS; // This is needed to disable write to EALLOW protected registers
// Step 4. Initialize all the Device Peripherals:
// This function is found in DSP2833x_InitPeripherals.c
// InitPeripherals(); // Not required for this example
InitEPwmTimer(); // For this example, only initialize the ePWM Timers
InitECapture();
// Step 5. User specific code, enable interrupts:
// Initalize counters:
ECap1IntCount = 0;
ECap1PassCount = 0;
// Enable CPU INT4 which is connected to ECAP1-4 INT:
IER |= M_INT4;
// Enable eCAP INTn in the PIE: Group 3 interrupt 1-6
PieCtrlRegs.PIEIER4.bit.INTx1 = 1;
// Enable global Interrupts and higher priority real-time debug events:
EINT; // Enable Global interrupt INTM
ERTM; // Enable Global realtime interrupt DBGM
// Step 6. IDLE loop. Just sit and loop forever (optional):
for(;;)
{
asm(" NOP");
}
}
void InitEPwmTimer()
{
EALLOW;
SysCtrlRegs.PCLKCR0.bit.TBCLKSYNC = 0;
EDIS;
EPwm3Regs.TBCTL.bit.CTRMODE = TB_COUNT_UP; // Count up
EPwm3Regs.TBPRD = PWM3_TIMER_MIN;
EPwm3Regs.TBPHS.all = 0x00000000;
EPwm3Regs.AQCTLA.bit.PRD = AQ_TOGGLE; // Toggle on PRD
// TBCLK = SYSCLKOUT
EPwm3Regs.TBCTL.bit.HSPCLKDIV = 1;
EPwm3Regs.TBCTL.bit.CLKDIV = 0;
EPwm3TimerDirection = EPWM_TIMER_UP;
EALLOW;
SysCtrlRegs.PCLKCR0.bit.TBCLKSYNC = 1;
EDIS;
}
void InitECapture()
{
ECap1Regs.ECEINT.all = 0x0000; // Disable all capture interrupts
ECap1Regs.ECCLR.all = 0xFFFF; // Clear all CAP interrupt flags
ECap1Regs.ECCTL1.bit.CAPLDEN = 0; // Disable CAP1-CAP4 register loads
ECap1Regs.ECCTL2.bit.TSCTRSTOP = 0; // Make sure the counter is stopped
// Configure peripheral registers
ECap1Regs.ECCTL2.bit.CONT_ONESHT = 1; // One-shot
ECap1Regs.ECCTL2.bit.STOP_WRAP = 3; // Stop at 4 events
ECap1Regs.ECCTL1.bit.CAP1POL = 1; // Falling edge
ECap1Regs.ECCTL1.bit.CAP2POL = 0; // Rising edge
ECap1Regs.ECCTL1.bit.CAP3POL = 1; // Falling edge
ECap1Regs.ECCTL1.bit.CAP4POL = 0; // Rising edge
ECap1Regs.ECCTL1.bit.CTRRST1 = 1; // Difference operation
ECap1Regs.ECCTL1.bit.CTRRST2 = 1; // Difference operation
ECap1Regs.ECCTL1.bit.CTRRST3 = 1; // Difference operation
ECap1Regs.ECCTL1.bit.CTRRST4 = 1; // Difference operation
ECap1Regs.ECCTL2.bit.SYNCI_EN = 1; // Enable sync in
ECap1Regs.ECCTL2.bit.SYNCO_SEL = 0; // Pass through
ECap1Regs.ECCTL1.bit.CAPLDEN = 1; // Enable capture units
ECap1Regs.ECCTL2.bit.TSCTRSTOP = 1; // Start Counter
ECap1Regs.ECCTL2.bit.REARM = 1; // arm one-shot
ECap1Regs.ECCTL1.bit.CAPLDEN = 1; // Enable CAP1-CAP4 register loads
ECap1Regs.ECEINT.bit.CEVT4 = 1; // 4 events = interrupt
}
interrupt void ecap1_isr(void)
{
// Cap input is syc'ed to SYSCLKOUT so there may be
// a +/- 1 cycle variation
if(ECap1Regs.CAP2 > EPwm3Regs.TBPRD*2+1 || ECap1Regs.CAP2 < EPwm3Regs.TBPRD*2-1)
{
Fail();
}
if(ECap1Regs.CAP3 > EPwm3Regs.TBPRD*2+1 || ECap1Regs.CAP3 < EPwm3Regs.TBPRD*2-1)
{
Fail();
}
if(ECap1Regs.CAP4 > EPwm3Regs.TBPRD*2+1 || ECap1Regs.CAP4 < EPwm3Regs.TBPRD*2-1)
{
Fail();
}
ECap1IntCount++;
if(EPwm3TimerDirection == EPWM_TIMER_UP)
{
if(EPwm3Regs.TBPRD < PWM3_TIMER_MAX)
{
EPwm3Regs.TBPRD++;
}
else
{
EPwm3TimerDirection = EPWM_TIMER_DOWN;
EPwm3Regs.TBPRD--;
}
}
else
{
if(EPwm3Regs.TBPRD > PWM3_TIMER_MIN)
{
EPwm3Regs.TBPRD--;
}
else
{
EPwm3TimerDirection = EPWM_TIMER_UP;
EPwm3Regs.TBPRD++;
}
}
ECap1PassCount++;
ECap1Regs.ECCLR.bit.CEVT4 = 1;
ECap1Regs.ECCLR.bit.INT = 1;
ECap1Regs.ECCTL2.bit.REARM = 1;
// Acknowledge this interrupt to receive more interrupts from group 4
PieCtrlRegs.PIEACK.all = PIEACK_GROUP4;
}
void Fail()
{
asm(" ESTOP0");
}
//===========================================================================
// No more.
//===========================================================================
Thank you,
Akhil Pillai
Part Number:TMDXICE110
Hi all,
I connected TMDXICE110 with CCS using the following Gel file.
C:\ti\ccsv8\ccs_base\emulation\boards\ice_amic110\gel\iceAMIC110.gel
After connecting, executing the following resulted in an error.
Scripts -> AMIC110 DDR Tests -> DDR_DataTransferCheck
When looking at the value of 0x80000000 in the memory browser, erroneous values were written.
This value changes randomly.
Next, I connected TMDXICE110 with CCS using the following Gel file.
C:\ti\ccsv8\ccs_base\emulation\boards\evmam3358\gel\AM335x_15x15_EVM.gel
The connection succeeded when we did the following.
Scripts -> AM335x DDR Tests -> DDR_DataTransferCheck
Why does DDR3 not work properly when using Gel for TMDXICE110?
Is this a gel file malfunction?
My CCS Version is v8.1.0.00011.
My JTAG is XDS200.
Best regards,
Sasaki
Part Number:AM5728
Tool/software: Linux
Hello:
My board is EVM-AM5728.
Now i want to run arm0 by linux and arm1 by bios.
What do you think about the practicability of this plan? Can you give me some help about it ?
What is the function of the SHA/B/C pin for DRV8305? 
Part Number:CC1310
Hello,
I want to use the NVS diver to write in flash, and after i do a write of 8 bytes of data i change the offset of the next write to write after the 8 bytes but erases them, how can i do successive write without erasing the previous writes.
Part Number:CC3220S-LAUNCHXL
Hi,
I've been trying to get the cloud OTA (github) sample working in IAR, but every time I try to build, it gives me the below error. How can I fix this?
Part Number:AM3352
Part Number:IWR1443
What is recommendation for pins not used on a custom board?
CSI2/HS_Debug signals
Analog Test/GPADC inputs
SPI signals
GPIOs
etc.
They can be left unconnected or should be pull-up/down?
I checked HardwareDesignChecklist(SWRR150), but it is not clearly shown.
Thanks and regards,
KoT
Part Number:EMBEDDED-PROGRAMMING
Tool/software: Linux
Hi I'm a newbie of embeded linux. I'm following this tutorial (embedjournal.com/.../)for boot make a custom linux . I have MLO, uboot.img, uImage,am335x-boneblack on the BOOT folder , and bin, dev, home ,lost+found, mnt, run, sys, usr ,boot, etc, lib, media, proc, sbin, tmp ,var on RFS folder
I can boot my linux on beaglebone black with sdcard. So now I want to boot the linux with eMMC flash
Sorry my English is not good. Does anybody have any idea of what did I do wrong or did I miss something?
Part Number:AM5728
Tool/software: TI-RTOS
When I run this code on x86 or arm, the output is what I intended, but the result was different on dsp.
The problem with dsp is that the address of the memory does not occasionally increase, and something seems to align the address.
The dsp, arm, x86 program has an optimization option of -O3.
test source is
main() int *src = (int*)srcbuf; for(i=0; i < 256/4 ; i++) *dest = *src; free(srcbuf); |
x86 or arm result
[03020100][03020100][00021110][00021008] |
dsp result
[03020100][03020100][95a1c318][95a1c210] ... |
I want to know why the output differs from the dsp only.
Part Number:TMS320F28069
Tool/software: Code Composer Studio
Hi sir,
I have doubt about BIOS and Non BIOS applications in tms320f28069, and please explain difference between BIOS and NON-BIOS System.
with reagards,
P M Manoj Kumar.
Part Number:AM5728
Tool/software: TI-RTOS
HI：
Software version: TI_RTOS 4.3, hardware version: AM5728-ES2.0, custom board
Apply a 640-byte memory on the linux side via the CMEM_alloc2 function and use CMEM_getPhys to return the physical address. Then use MessageQ to send the virtual address and physical address to the DSP. What should I do to operate the CMEM memory on the DSP side?
Reference Code：
processor_sdk_rtos_am57xx-evm_4.3/ipc_3_47_01_00/linux/src/tests/
Tool/software: TI C/C++ Compiler
Hi all,
I'm trying to get two the scratchpad of two CLA objects (CLA1_main.c and CLA2_main.c) in one union.
But get the message 10030-D expecting section type (COPY, DSECT, or NOLOAD) instead of ".scratchpad"
[code]
UNION (ClaScratchpads) > CLA_DRAMLS2 PAGE(DataPage)
{ CLA1_main.obj(.scratchpad)
CLA2_main.obj(.scratchpad)
}
[/code]
while this declaration does work:
[code]
ClaScratchpads > CLA_DRAMLS2 PAGE(DataPage)
{ CLA1_main.obj(.scratchpad)
}
[/code]
And what I would like to have is:
[code]
UNION (ClaScratchpads) > CLA_DRAMLS2 PAGE(DataPage)
{ GROUP (CLA1scratch)
{ CLA1_main.obj (.scratchpad)
CLA1_task1.obj(.scratchpad)
CLA1_task2.obj(.scratchpad)
}
GROUP (CLA2scratch)
{ CLA2_main.obj (.scratchpad)
CLA2_task1.obj(.scratchpad)
CLA2_task2.obj(.scratchpad)
}
}
[/code]
Is this an issue in the compiler/linker?
Best regards,
