Part Number: TMS320F28377D Tool/software: TI C/C++ Compiler The first way sometimes I can't get any data, I wonder what the problem is? I'm using SCIA interrupt. When I remove ram or sci from the code, the speed is good. But I have to use it this way
↧
Forum Post: Compiler/TMS320F28377D: sci, can and ram sharing were used at the same time with two cpu. but the data flow is very slow
↧
Forum Post: RTOS/TMS320F28388D: TMS320F28388D TI RTOS support
Part Number: TMS320F28388D Tool/software: TI-RTOS Hi Team, Can TI RTOS support F28388D now? when can provide the user guide and full project example code about RTOS based on F28388D? do we have software tool to test the performance of OS, such as measuring run time of periodic task and deadline.
↧
↧
Forum Post: MSP432P401M: Debugging using USB
Part Number: MSP432P401M Hi, I have few question on Debug and Programing this controller using USB. Debug and Programming this controller has to be through JTAG Or is it possible to do through the USB also? Thank you.
↧
Forum Post: TMS320F28377S: "Break at address "0x3ff16a" with no debug information available, or outside of program code. "
Part Number: TMS320F28377S related to https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/825198?tisearch=e2e-sitesearch&keymatch=%20user%3A416579 After reset application, I expected that mcu boot to flash address 0x80000(bootloader begin) But there're log "Break at address "0x3ff16a" with no debug information available, or outside of program code. " This area is BOOT ROM section.. could you explain why mcu is trapped in this area?
↧
Forum Post: TMS320F28377D: What is "Base_Speed" means in M-method velocimetry?
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
↧
↧
Forum Post: MSP430F5438A: 4-wire JTAG, Device not supported (IAR)
Part Number: MSP430F5438A I try to use Debug mode on IAR using the FPA FlashPro430. I'm facing some difficulties with the device recognition. Here are the logs of my issue : Wed Jul 31, 2019 10:32:12: Using license: Standalone license - IAR Embedded Workbench for Texas Instruments MSP430, Baseline Edition 6.10 Wed Jul 31, 2019 10:32:12: Firmware version 20408002 Wed Jul 31, 2019 10:32:12: Interface dll version 2.4.8.2 Wed Jul 31, 2019 10:32:12: Invalid parameter(s) : (Configure) , mode=0xf, value=0x1 Wed Jul 31, 2019 10:32:14: Could not find device (or device not supported) : (OpenDevice) , Device=MSP430F5438A, PwLength=0x0 Wed Jul 31, 2019 10:32:31: Fatal error: Could not find device (or device not supported) Session aborted! Wed Jul 31, 2019 10:32:31: Failed to get device Wed Jul 31, 2019 10:32:31: Unknown device : (SetEEMSequencer) Wed Jul 31, 2019 10:32:33: Fatal error: Closing debug session Session aborted! I checked several times the wire connections since it seems to be one major mistake with this this kind of issue but I didn't find anything. I am using the experimenter board (MSP-EXP4305438) with the MSP430F5438. Here are the different documentation for the JTAG interface I found : FlashPro430 pinout (soldering side) Signal Connections for 4-Wire JTAG Communication My interface (red wires are power supply) If you can't see, the Vcc/sense of the flasher goes on the bottom-right of the JTAG connector on the photo Note that I tried with USB and FET Power supply mode. I also checked the power supply output of the flasher with a multimeter and I checked the GND pin of the JTAG connector of the board to be sure to be in the good orientation. I can't be sure it doesn't come from my interface but I did a lot of checks.
↧
Forum Post: CCS/MSP430FR2155: Function not returning value
Part Number: MSP430FR2155 Tool/software: Code Composer Studio I am working on MSP430FR2155 and made some work with I2C .When debugging step by step the function returning value correctly bu if I step over the function is not returning any value. any guess? int8_t I2CReadRegisterByteWithCRC(uint8_t I2CSlaveAddress, uint8_t Register) { uint8_t TargetRegister = Register; ///uint16_t SentByte = 0; uint8_t ReadData[2]; uint8_t temp; //uint16_t ReadDataCount = 0; uint8_t CRCInput[2]; uint8_t CRC = 0; int8_t ReadStatus = 0; int8_t WriteStatus = 0; WriteStatus = wire_Send_bytes(I2CSlaveAddress, &TargetRegister, 1); ReadStatus =wire_read_bytes(I2CSlaveAddress, ReadData, 2); if (ReadStatus != 0 || WriteStatus != 0) { return -1; } CRCInput[0] = (I2CSlaveAddress << 1) + 1; CRCInput[1] = ReadData[0]; CRC = CRC8(CRCInput, 2, CRC_KEY); if (CRC != ReadData[1]) return -1; temp=ReadData[0]; return temp; }
↧
Forum Post: TIDM-FRAM-EEPROM: About SPI clocks using the direct memory access (DMA)
Part Number: TIDM-FRAM-EEPROM Hi community member, I have a question about the SPI clock of TIDM-FRAM-EEPROM. 1. Do you think it is possible to design for faster SPI clock (eg 10 MSPS)? My customer wants to communicate at speeds faster than 1MSPS. The Design Guide says: This design is also designed to support EEPROM emulation with SPI and supports slave clock polarity high with rising edge as the trigger. This example is capable of supporting SPI clocks up to 1 Mbps using the direct memory access (DMA). All MSP430FR5x and MSP430FR6x devices have onboard DMA. 2. If TIDM-FRAM-EEPROM design is not capable of SPI Clock of 10 MSPS, LPM is considered to be one of the factors. Do you think that the CPU can support 10MSPS if it is SPI communication in always active mode? I think it can omit the wake-up time from LPM and interrupt latency. Best regards. Cruijff
↧
Forum Post: TMS320F28377D: hrpwm_deadband_sfo_v8 frequency sweep code
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 > 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++; } }
↧
↧
Forum Post: TM4C1294NCPDT: Need BSP/Device Drivers for this part number
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
↧
Forum Post: TMS570LC4357: Endianness for external memories
Part Number: TMS570LC4357 Hi, From other TI posts got to know that TMS570LC4357 supports big endian and the endianness cannot be changed. Also, the following was mentioned, 'the byte ordering is managed inside the MCU depending on the endianness. The external data bus connections need not account for the endianness change.' But how will the microcontroller determine which endianness to operate in? Page 329 of technical reference manual shows a read only bit 0 for 'ENDIAN', which determines the endianness. Who will set this bit? Is there any additional pin to determine the endianness? As suggested, we are maintaining same external data bus connections (D15:D0 of microcontroller to D15:D0 of external memory). Do you foresee any concern? Regards, Archana Rao
↧
Forum Post: TMS570LC4357: Boot up configuration pins
Part Number: TMS570LC4357 Hi, Does Hercules TMS570LC4357 need any hardware boot strap configuration pins (such as pull up or pull down on specific pins) during initial boot up? I don't see anything in datasheet or tech reference manual asking for configuration pins during boot up. Please advise. Regards, Archana Rao
↧
Forum Post: TMS320F28377D: Unable to flash brand new MCU
Part Number: TMS320F28377D Hi, You are my last hope, been pulling my hair out for last couple of weeks. Got 6 brand new boards built with TMS320F28377D on them, 2 - work, 4 don't. Replaced MCU on one of the boards that did not work - still does not work. Got some very expensive software to rule out JTAG issues - JTAG is fine. Power supplies are fine. +3V3, +1V2 are fine. Grounding is fine. No shorts detected. Nothing is warming up that should not. I can control IOs via the JTAG software. So down the rabbit hole I go. 1. Set Boot mode pins (GPIO72,GPIO84) to 1,0 respectively to get the MCU into WAIT mode and try to flash the firmware. Output I get is C28xx_CPU1: GEL Output: Memory Map Initialization Complete C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed. C28xx_CPU1: Writing Flash @ Address 0x00080000 of Length 0x00000008 (page 0) C28xx_CPU1: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) C28xx_CPU1: Trouble Halting Target CPU: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) C28xx_CPU1: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.2.0.00004) C28xx_CPU1: Unable to determine target status after 20 attempts C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected C28xx_CPU1: PLL configuration status = 0. C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0) C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected C28xx_CPU1: File Loader: Memory write failed: Unknown error C28xx_CPU1: GEL: File: C:\ProjectFiles\rimac\obc\src\clp\obc\ccs\OBC_A_Debug\obc.out: Load failed. C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled. C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug. C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x5D200@Program: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled. C28xx_CPU1: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug. C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected At no point power supplies trip or go low - very unsure as to why the target it not connected. 2. Instead of flashing code, connecting to the MCU via debugger to see what is happening inside (Using the same .ccxml as the Debug Configuration). I Launched the .ccxml from the Target Configurations in CSS and Connected to the CPU 1 core. Great. Do System Reset then CPU Reset. Looking at the Disassembly tab, I can see that the Program Counter is at 0x003FF16A. Looking at the Delfino user manual, it seems that this is somewhere within the Secure ROM area. I let the code execute and it gets itself into ESTOP0, the Program Counter is at 0x003FE2ED which is within the Boot ROM space. The MemoryErrRegs, RomWaitStateRegs and RomPrefetchRegs registers are all 0s. RESC register shows that XRSn and TRSTn are 1, everything else is 0. I am using Blackhawk USB560-v2 Debugger, but I tried XDS200 too and it is the same issue. 3. Return Boot Mode pins both to HIGH, so the Boot ROM jumps to Boot from Flash instead of Wait. Again, Launch Target Configuration connecting to the target, System Reset, CPU Reset, let the code to execute, it stops at ITRAP0 @0x0 from 0x0F189 (GS3 RAM)? So, what is going on here? I am lost. Any advise on what I am doing wrong, what could be causing what I am seeing would be much appreciated. I can flash the same code with the exact same tools on the other 2 boards and they work, but these 4 are just dead. Much appreciated
↧
↧
Forum Post: TMDSEMU110-U: GPIO control for embedded XDS110 - prerequisites
Part Number: TMDSEMU110-U Hi, I am trying to control the XDS110 GPIOOUT pins in a custom embedded XDS110 design. In a related thread https://e2e.ti.com/support/microcontrollers/other/f/908/p/824023/3049028#3049028 I got the info that the logical GPIOOUT0 pin maps to PF0 on the Tiva MCU. On the PC I am running this batch file to toggle GPIOOUT0..1 on and off: :loop dbgjtag.exe -f @xds110 -Y gpiopins,config=0x3,write=0x3 dbgjtag.exe -f @xds110 -Y gpiopins,config=0x3,write=0x0 goto loop As a first test, I connect the original TMDSEMU110-U with the little AUX breakout board and apply 3.3V to TGTVDD(SENSE). I can see a square wave on GPIOOUT0 and GPIOOUT1 using an oscilloscope - as expected. To try the same on custom hardware, I am using an EK-TM4C1294XL launchpad. I installed a 16 MHz crystal and flashed the XDS110 firmware. The board correctly shows up as XDS110 on the PC and the xdsdfu and dbgjtag tools will talk to it without a problem. Running the batch scripts now, I see no activity on any of the PF0..3 pins, they all sit at 0V. Reading back the GPIO config after running the batch file always returns 0 (on the TMDSEMU110, I see the config value 0x03 as set from batch file): dbgjtag.exe -f @xds110 -Y gpiopins -v -----[Print the board config pathname(s)]------------------------------------ xds110.i -----[Print the controller-open software log-file]--------------------------- The library build date was 'Jan 24 2019'. The library build time was '14:27:46'. The library package version is '8.0.903.6'. The library component version is '35.35.0.0'. The controller does not use a programmable FPGA. The controller has a version number of '5' (0x00000005). The controller has an insertion length of '0' (0x00000000). The user GPIO pin config is 0x00. The user GPIO pin input is 0x00. What am I doing wrong? Do the version pins PK4..7 need to be set to a specific value? Is there some other connection that I need to make to get the GPIOs to function? Thanks for your help
↧
Forum Post: BOOSTXL-SENSORS: BOOSTXL-SENSORS
Part Number: BOOSTXL-SENSORS Hi, I'm running the BOOSTXL-SENSORS BoosterPack on the MSP432P401R LaunchPad. In the Users Guide Section 3.2 It says that there is a TI-RTOS example of the source code called "BOOSTXL-SENSORS_TI-RTOS_SensorGUI_MSP432P401R to be found in the SimpleLink MSP432 SDK. I can find the "No RTOS" version but cannot find the TI-RTOS version mentioned in the SimpleLink MSP432 SDK and I want to run this example as my I want to use the TI-RTOS version. Please can someone tell me where to look or send a link to this example so I can import it into CCS. Many Thanks, Bill
↧
Forum Post: CCS/TMS320F28379D: CCS/TMS320F28379D
Part Number: TMS320F28379D Tool/software: Code Composer Studio Hi How to fix these errors?
↧
Forum Post: TMS320F28388D: Max ePWM frequency on F28388 vs older parts
Part Number: TMS320F28388D Hi, Chapter 3.7.3.3 of the F28388 TRM (SPRUII0) states that " the ePWM clockl each have an additional /2 divider, which is required to support CPU frequencies over 100MHz ". However the datasheet states that the ePWM and HRPWM work with frequencies up to 200MHz. Can someone confirm that the ePWM modules do work up to 200MHz? Thanks, Pierre
↧
↧
Forum Post: CCS/RM46L850: RM4
Part Number: RM46L850 Tool/software: Code Composer Studio Hi !!! I want to know why two PLL configuration is required for EMAC_LOOP_TXRX.
↧
Forum Post: MSP430FR5969: SPI communication with TMS570
Part Number: MSP430FR5969 Hi, I'm working with MSP430 as a slave and TMS570 as a master. I have problem with frequency of data flow. Currently I set TMS570 on 312 500 Hz and MSP430 receive and transmit data correct. Unfortunately I need to obtain higher frequency, When I'm trying to set 400 kHz or 600 kHz data sending from MSP430 (slave) is not correct. Thats mean random byte are sent double and I have no control which one. It's my clock setting on MSP (24MHz): /* Set DCO frequency to max DCO setting */ CS_setDCOFreq(CS_DCORSEL_1, CS_DCOFSEL_6); /* Select DCO as the clock source for SMCLK with no frequency divider */ CS_initClockSignal(CS_SMCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1); How I send data from slave when clock is generated by TMS (Master): if (numberOfParam >= MEASUREMENTS_LAST_HOUR) { uint8_t *data_ptr; //data_ptr = FramStart_ptr; data_ptr = FramStart_ptr - MEASUREMENTS_LAST_HOUR; EUSCI_B_SPI_transmitData(EUSCI_B0_BASE, INIT_MSG); for (i = 0; i < MEASUREMENTS_LAST_HOUR; i++) { while (!EUSCI_B_SPI_getInterruptStatus(EUSCI_B0_BASE, EUSCI_B_SPI_RECEIVE_INTERRUPT)); read = EUSCI_B_SPI_receiveData(EUSCI_B0_BASE); EUSCI_B_SPI_transmitData(EUSCI_B0_BASE, *data_ptr); data_ptr=data_ptr+1; } while (!EUSCI_B_SPI_getInterruptStatus(EUSCI_B0_BASE, EUSCI_B_SPI_RECEIVE_INTERRUPT)); read = EUSCI_B_SPI_receiveData(EUSCI_B0_BASE); EUSCI_B_SPI_transmitData(EUSCI_B0_BASE, TRANSMISSION_END); while (!EUSCI_B_SPI_getInterruptStatus(EUSCI_B0_BASE, EUSCI_B_SPI_RECEIVE_INTERRUPT)); read = EUSCI_B_SPI_receiveData(EUSCI_B0_BASE); EUSCI_B_SPI_transmitData(EUSCI_B0_BASE, 0); } Could you please tell me what should I set to get data flow with 1 MHz on the SPI?
↧
Forum Post: MSP430FR6989: MSP430FR6989 HFXTCLK High Frequency Clock
Part Number: MSP430FR6989 Hello, I need an ~4Mhz clock output from the MSP430 for an ADC. I'd like to use Pin 4.0 and use the MCLK. Is that possible? Do I need an external crystal for the HFXTCLK? How can I get the frequency of the HFXTCLK? Regards Tobi
↧