Part Number:CC2650STK
Hi Everyone.
I load on CC2650STK a Simple_Observer_CC2650em example by ble_sdk_2_02_01_18.
Before I load it, I changed the board.c file, like this :
So I built the Stack, the app project and I debug it to load on CC2650STK.
No error, but on Putty nothing appeares.
I red here that simple_observer once started print on terminal something. How I can make it works fine?
Thanks everybody, a lot.
Part Number:CC2640r2f
All,
I see the link to the BLE Software Developer's Guide given on this e2e thread is broken.
Also, this FAQ page links to the "OAD Guide" which is also broken.
Both pages are probably supposed to link to the CC2640 OAD User's Guide or to a page like this OAD document.
Thanks,
Darren
Part Number:TMS320F28035
Tool/software: Code Composer Studio
Hello,
I recently programmed my TMS320F28035 using JTAG. The program was one of the C2000 examples for toggling GPIO's. My LED's toggled on and off as expected. I used the F28035.cmd linker file to load the code onto the MCU via JTAG and no problems after that either. However, I wanted to try using one of the ePWM examples from C2000 example folder. I imported the project to the workspace and chose XDS110 as my debug connection. However, when I tried to debug the code I had gotten the error below. Is there anything I can do to fix this? I don't believe it is a hardware issue since I have played around with the GPIO toggle example for a couple of days with no issues before trying to use the ePWM example. Please help! Here is the error I am getting:
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.
The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.
[End: Texas Instruments XDS110 USB Debug Probe]
Has anyone seen issue:
Error connecting to the target.
(Error - 1266 @ 0x0)
Device is held in reset. Take the device out of reset, and retry the operation.
(Emulation package 5.1.402.0)
The chip reset pin is at 3.3.V
Part Number:TM4C123GH6PM
Title says it all. I'm using the EK-TM4C123GXL launchpad.
#include <stdint.h>
#include <stdbool.h>
#include <inc/hw_memmap.h>
#include <inc/hw_gpio.h>
#include <driverlib/pwm.h>
#include <driverlib/sysctl.h>
#include <driverlib/gpio.h>
#include <driverlib/pin_map.h>
int main(void) {
SysCtlClockSet(SYSCTL_SYSDIV_1 | SYSCTL_USE_OSC | SYSCTL_OSC_MAIN | SYSCTL_XTAL_16MHZ);
SysCtlPeripheralEnable(SYSCTL_PERIPH_GPIOB);
while(!SysCtlPeripheralReady(SYSCTL_PERIPH_GPIOB));
GPIOPinConfigure(GPIO_PB4_M0PWM2);
GPIOPinConfigure(GPIO_PB7_M0PWM1);
GPIOPinConfigure(GPIO_PB6_M0PWM0);
GPIOPinTypePWM(GPIO_PORTB_BASE, GPIO_PIN_4);
GPIOPinTypePWM(GPIO_PORTB_BASE, GPIO_PIN_6);
GPIOPinTypePWM(GPIO_PORTB_BASE, GPIO_PIN_7);
SysCtlPeripheralEnable(SYSCTL_PERIPH_PWM0);
while(!SysCtlPeripheralReady(SYSCTL_PERIPH_PWM0));
PWMGenConfigure(PWM0_BASE, PWM_GEN_0, PWM_GEN_MODE_DOWN | PWM_GEN_MODE_NO_SYNC);
PWMGenConfigure(PWM0_BASE, PWM_GEN_1, PWM_GEN_MODE_DOWN | PWM_GEN_MODE_NO_SYNC);
//0xff =256; 256/16MHz = 16us
//0xff =256; 256/16MHz = 16us
PWMGenPeriodSet(PWM0_BASE, PWM_GEN_0, 0xff);
PWMGenPeriodSet(PWM0_BASE, PWM_GEN_1, 0xff);
//blue
PWMPulseWidthSet(PWM0_BASE, PWM_OUT_0, 0);
//green
PWMPulseWidthSet(PWM0_BASE, PWM_OUT_1, 1);
//red
PWMPulseWidthSet(PWM0_BASE, PWM_OUT_2, 0x80);
PWMGenEnable(PWM0_BASE, PWM_GEN_0);
PWMGenEnable(PWM0_BASE, PWM_GEN_1);
PWMOutputState(PWM0_BASE, (PWM_OUT_0_BIT | PWM_OUT_1_BIT | PWM_OUT_2_BIT), true);
while(1);
return 0;
}
PWM_OUT_1 gets a duty cycle of 1/256 and I see a tiny pulse on the scope. PWM_OUT_0's duty cycle is set to 0, but it is high (100% duty). Setting a 100% duty cycle gets the expected results.
This issue has been found by at least two others:
The second one is marked "answered", but I don't understand af36's workaround.
Part Number:CC2541
I was following the porting procedure from CC2540 to CC2541 from http://processors.wiki.ti.com/index.php/LPRF_BLE_Porting_Projects#Porting_from_CC2540_to_CC2541_Project
(I think there is a typo, it should be from CC2541 to CC2540).
I got several questions.
(1) Step 1. Create and select a new C2541 project configuration based on CC2540 configuration. (see the first figure)
Should I choose Factory settings for debugging or release? What will be the differences?
(2) Step 3. Change the settings in preprocessor tab (see the second figure)
I followed the instruction strictly, and getting a lot of errors. Then I found that I have to change “$PROJ_DIR$\..\..\Componenet\hal\target\CC2540EB “ to CC2541 files. The only thing I could find in that folder was CC2541ARC and CC2541ST. Since the CC2540 project was originated from development board, I thought CC2541ARC should be closer my project. However, after I changed it, there is an error “could not find hal_board_cfg.h”.(comdef.h was looking for this) I checked all CC2540DB, CC2541ST, they all have this hal_board_cfg.h but only CC2541ARC does not have this file. Why there is no such file? Will that be an issue of using CC2541ST for a project from CC2540DB? I look through both of them and found the major differences are the drivers for sensors on the sensor tags. I compiled using CC2541ST and there was no error. I do not have a CC2541 to test right now and am designing one from CC2540.
(3) Also from Step 3, change the setting in the preprocessor tab (see the third figure)
I also found another one which says CC2540““$PROJ_DIR$\..\common\cc2540". I looked in the folder and could not find a cc2541 file. So I just leave this way and did not get errors. Will that be an issue? Why there is no CC2541 file in the common folder?
Part Number:SN74AHC14
As the title says, what does the G4 signify in the SN74AHC14DRG4?
Thanks!
Russell
Part Number:cc2650
Hi,
I'm trying to follow the guide (
) on how to set up cc26xx-web-demo with NAT64 running on edge router with cc2531 slip radio.
It states "Enter e.g. your PC or access point IPv6 address in the Peer router edit box." - How do i find this IPv6 address? Should i use the HOST_IPV6_ADDR "bbbb::101" from wrapper.c? The only output i see using "cat /var/log/6lbr.ip" is bbbb::100.
Thanks in advance
Part Number:MSP430G2955
Hello,
I am trying to use 3 ADC channels to read in analog values into the variable ADC10MEM. I understand that sampling is done sequentially, however I am stuck on how to properly obtain and store the individual ADC readings into the proper variable. More so, if I use an interrupt to trigger during ADC10MEM conversion, how do I know which channel is being stored into the ADC variable?
Thanks
Part Number:TIDA-00883
I have most of the design documents that I need to fabricate the n=board, but I am missing the net list, is this available?
Thanks,
Shawn
Part Number:TLC59116
Hi Team,
Want to confirm with a customer regarding the following question:
The datasheet says, "Change of the outputs at the Stop command allows synchronizing outputs of more than one TLC59116. Applicable to registers from 02h (PWM0) to 17h (LEDOUT3) only."
Can you please let us know if 'STOP' condition also resets the internal blink counter?
Thanks for the help in advance and best regards,
Jerry
Part Number:CC2640R2F
Tool/software:TI-RTOS
Hello,
I'm trying to find RF RTOS Driver example projects for the CC2640R2F, specifically the rfCarrierWave project, but it seems as though there are no RF projects available. I've looked through each SDK revision for the CC2640R2F (1.00.00.22-1.50.00.58), and the only similar one I've been able to find is rfPacketErrorRate in simplelink_cc2640r2_sdk_1_40_00_45. Is there somewhere else I should be looking?
I found the rfCarrierWave project for the CC2650, would it be difficult to port this to the CC2640R2F?
Thanks in advance.
Part Number:AWR1243
The datasheet of AWR1243 shortly describes the radar chip connection to the TDA3x (or TD2x) SoC as external MCU.
Is one TDA3x able to handle two AWR1243 in cascade, i.e. handle 4 Lane Data + 1 Clock lane from two AWR1243?
Does TI provide a reference implementation for a software design on the TDA3x SoC, i.e. some framework for starting a software design using the AWR1243 together with the TDA3x?
Thanks
/Henric
Part Number:F28M35H52C
I am trying to have Flash API function Erase one of the sector of M3 Flash Memory (Sector L). I have followed all the necessary steps suggested in the FLASH API application note and using the same set of F021 Libary and functions used in one of the Control suite example.
I am particularly having challenge when software execution passes Fapi_issueAsyncCommandWithAddress(Fapi_EraseSector, (uint32 *)Bzero_SectorL_start) and passes the while condition after this. When i observe the memory browser for Sector L, I do not see it getting flashed but it still retain the same code.
Below are some screenshots of what i have been observing while trying to erase the sector.
Here the function i call to perform some Flash operations.
#pragma CODE_SECTION(CallFlashAPI, "ramfuncs");
bool CallFlashAPI(void)
{
uint32 u32Index = 0;
uint16 i = 0;
Fapi_StatusType oReturnCheck;
volatile Fapi_LibraryInfoType oLibInfo;
volatile Fapi_FlashStatusType oFlashStatus;
Fapi_FlashBankSectorsType oFlashBankSectors;
Fapi_FlashStatusWordType oFlashStatusWord;
// This function is required to initialize the Flash API based on System
// frequency before any other Flash API operation can be performed
#if CPU_FRQ_125MHZ
oReturnCheck = Fapi_initializeAPI(F021_CPU0_BASE_ADDRESS, 125);
#endif
#if CPU_FRQ_100MHZ
oReturnCheck = Fapi_initializeAPI(F021_CPU0_BASE_ADDRESS, 100);
#endif
#if CPU_FRQ_75MHZ
oReturnCheck = Fapi_initializeAPI(F021_CPU0_BASE_ADDRESS, 75);
#endif
#if CPU_FRQ_60MHZ
oReturnCheck = Fapi_initializeAPI(F021_CPU0_BASE_ADDRESS, 60);
#endif
if(oReturnCheck != Fapi_Status_Success)
{
//Check Flash API documentation for possible errors
Error(oReturnCheck);
}
// Fapi_getLibraryInfo function can be used to get the information
// specific to the compiled version of the API library
oLibInfo = Fapi_getLibraryInfo();
// Fapi_setActiveFlashBank function sets the Flash bank and FMC
// for further Flash operations to be performed on the bank
oReturnCheck = Fapi_setActiveFlashBank(Fapi_FlashBank0);
if(oReturnCheck != Fapi_Status_Success)
{
// Check Flash API documentation for possible errors
Error(oReturnCheck);
}
// Fapi_getBankSectors function returns the bank starting address,
// number of sectors, sector sizes, and bank technology type
// Above information is returned in a structure oFlashBankSectors of type
// Fapi_FlashBankSectorsType
oReturnCheck = Fapi_getBankSectors(Fapi_FlashBank0,&oFlashBankSectors);
if(oReturnCheck != Fapi_Status_Success)
{
// Check Flash API documentation for possible errors
Error(oReturnCheck);
}
// Erase Sector L
// Sector N has the example code so leave it programmed
oReturnCheck = Fapi_issueAsyncCommandWithAddress(Fapi_EraseSector,
(uint32 *)Bzero_SectorL_start);
// Wait until FSM is done with erase sector operation
while (Fapi_checkFsmForReady() != Fapi_Status_FsmReady){}
// Verify that Sector L is erased. The Erase step itself does a verify
// as it goes. This verify is a 2nd verification that can be done.
oReturnCheck = Fapi_doBlankCheck((uint32 *)Bzero_SectorL_start,
/*Bzero_32KSector_u32length*/420,
&oFlashStatusWord);
if(oReturnCheck != Fapi_Status_Success)
{
//Check Flash API documentation for possible errors
//If Erase command fails, use Fapi_getFsmStatus() function to get
// the FMSTAT register contents
//to see if any of the EV bit, ESUSP bit, CSTAT bit or VOLTSTAT
//bit is set (Refer to API documentation for more details)
Error(oReturnCheck);
}
// Erase Sector K
// Sector N has the example code so leave it programmed
oReturnCheck = Fapi_issueAsyncCommandWithAddress(Fapi_EraseSector,
(uint32 *)Bzero_SectorK_start);
// Wait until FSM is done with erase sector operation
while (Fapi_checkFsmForReady() != Fapi_Status_FsmReady){}
// Verify that SectorK is erased. The Erase step itself does a verify as
// it goes. This verify is a 2nd verification that can be done.
oReturnCheck = Fapi_doBlankCheck((uint32 *)Bzero_SectorK_start,
Bzero_16KSector_u32length,
&oFlashStatusWord);
if(oReturnCheck != Fapi_Status_Success)
{
// Check Flash API documentation for possible errors
// If Erase command fails, use Fapi_getFsmStatus() function to get
// the FMSTAT register contents
// to see if any of the EV bit, ESUSP bit, CSTAT bit or VOLTSTAT bit is
// set (Refer to API documentation for more details)
Error(oReturnCheck);
}
// Example: Program 0xFF bytes in Flash Sector K along with auto generated ECC
// In this case just fill a buffer with data to program into the flash.
for(i=0;i<=BYTES_IN_FLASH_BUFFER;i++)
{
Buffer[i] = i;
}
// Example: Program 0xFF bytes in Flash Sector K with out ECC
// Disable ECC so that error is not generated when reading Flash
// contents without ECC
HWREG(FLASH_ERROR_BASE + FLASHERR_O_ECC_ENABLE) = 0x0;
for(i=0, u32Index = Bzero_SectorK_start;
(u32Index < (Bzero_SectorK_start + BYTES_IN_FLASH_BUFFER))
&& (oReturnCheck == Fapi_Status_Success); i+= 16, u32Index+= 16)
{
oReturnCheck = Fapi_issueProgrammingCommand((uint32 *)u32Index,
Buffer+i,
16,
0,
0,
Fapi_DataOnly);
while(Fapi_checkFsmForReady() == Fapi_Status_FsmBusy);
if(oReturnCheck != Fapi_Status_Success)
{
//Check Flash API documentation for possible errors
Error(oReturnCheck);
}
//Read FMSTAT register contents to know the status of FSM after
// program command for any debug
oFlashStatus = Fapi_getFsmStatus();
// Verify the values programmed. The Program step itself does a verify
// as it goes. This verify is a 2nd verification that can be done.
oReturnCheck = Fapi_doVerifyByByte((uint8 *)u32Index,
16,
Buffer+i,
&oFlashStatusWord);
if(oReturnCheck != Fapi_Status_Success)
{
//Check Flash API documentation for possible errors
Error(oReturnCheck);
}
}
//Erase Sector K
//Sector N has the example code so leave it programmed
oReturnCheck = Fapi_issueAsyncCommandWithAddress(Fapi_EraseSector,
(uint32 *)Bzero_SectorK_start);
//Wait until FSM is done with erase sector operation
while (Fapi_checkFsmForReady() != Fapi_Status_FsmReady){}
// Verify that SectorK is erased. The Erase step itself does a verify as
// it goes. This verify is a 2nd verification that can be done.
oReturnCheck = Fapi_doBlankCheck((uint32 *)Bzero_SectorK_start,
Bzero_16KSector_u32length,
&oFlashStatusWord);
if(oReturnCheck != Fapi_Status_Success)
{
// Check Flash API documentation for possible errors
// If Erase command fails, use Fapi_getFsmStatus() function to get the
// FMSTAT register contents
// to see if any of the EV bit, ESUSP bit, CSTAT bit or VOLTSTAT bit
// is set (Refer to API documentation for more details)
Error(oReturnCheck);
}
// Enable ECC
HWREG(FLASH_ERROR_BASE + FLASHERR_O_ECC_ENABLE) = 0xA;
// Leave control over pump
FlashLeavePump();
return gTRUE;
}
Also i configured the M3 for 75Mhz frequency.
Any hints on what i could i be doing wrong ??
Thanks
Part Number:TMS320F28377S
Dear Community,
I need your help. I´m very new at programming at this language and for me it is very difficult to understand all about the controller correlation. I started with some examples, but there are for me some missing informations at some places.
You can find in the attachment a dokument about what I want to do. Of course I take it step after step.
1.My point at the Moment is this PWM-Code in the Attachment. I want to set PWM2A (set low at Zero TBRD) hight at the beginnig of every cyle and down when the GPIO12 goes high (Force high at Trip Event). And EPWM2B the other way arround. But, when I measure the both PWMs I see can that both Pins exactly behave the other way arround.
A Deaband is added, I think There is the Problem, but I can´t find it.
2.I want to use Comp1 with ADCINA2 to compare with a solid standing DAC-value. If the Comp1 goes high I want to feed with this trip4 Event. And than this Event must set down EPMW2A and EPWM2B high.
--I tried some example cmpsss, but at first Point 1 is to solve.
3.I want to change the DAC value with a Rampe (Offset - Rampe= new DAC) and always with the same angle. (Only for the worst Case)
4.A Interrupt that starts at the same time like Trip Event 4. In this Interrupt the ADC-Value is taken and with a simple Bit-shift a new DAC-value for the next cyle will be caculateted. The Value goes into DACVALS.
I guess some flags of the cmp and the trips have to be shout down every cycle, but I don´t know how and which.
Please help. I´m running out of time with this student-project and there are also some big tests and I really need some good results.
This is hopefully my last semester...
Thank you in adavance!!!
I am grateful for any help. I would like to progress the steps gradually, if I have forgotten something, then please tell me.
I will update this post until everything works and share every new intermediate step with you !!! Everday as soon as possible.
(Please visit the site to view this file)(Please visit the site to view this file)
Part Number:TMS320F28027
Hi team,
I'm looking forward to design a extension for C2000 LauchPads.
Kind regards
Dierk Bronner
Part Number:MSP432P401R
Is there a way to start a DMA TX without clearing the TXIFG?
When a DMA TX completes the UART will have a (partial) character in the transmit shift register and the last character in the TXBUF register. The TXIFG will be set as these characters are shifted out the TX transmit shift register. Hence, the TXIFG is already set when you want to send the next packet. I can start another DMA TX by 1) reset the TXIFG and 2) either set the TXIFG or write a character into the TXBUF register.
The problem is either a reset or set of the TXIFG can affect the RXIFG if a receive DMA UART is in process since a reset or set of the TXIFG requires a read of the IFG register, modify a bit, then write the modified back to the IFG register. Example, read the IFG register with the RXIFG equal '1', RCV DMA reads the RXBUF, write the IFG register and the RXIFG is set again. RCV DMA reads the same character twice from the RXBUF register.
The only solution I can think of is to split the TX and RX acroos two UARTS. Any other ideas???
Part Number:MSP430FR5994
Hi team,
I'm looking forward to design a extension for MSP43x LauchPads.
Kind regards
Dierk Bronner