Part Number: TMS320F28335 Hello, I am using an XDS100v2 debugger with Code Composer studio v9.0.1.00004 on Windows 7.. While debugging a program, the debugger sometimes stops in EQEP1_INT_ISR after I pressed the suspend button in Code Composer. This has happened several time and I think it started happening yesterday. My program is not using the EQEP peripheral. Below is the EQEP1_INT_ISR code and the state of the relevant registers immediately after the debugger stopped in EQEP1_INT_ISR.. As you can see, the PIEIFR5 is not enabled. What could be causing this issue? Stephen interrupt void EQEP1_INT_ISR(void) // EQEP-1 { // Insert ISR Code here // To receive more interrupts from this PIE group, acknowledge this interrupt // PieCtrlRegs.PIEACK.all = PIEACK_GROUP5; // Next two lines for debug only to halt the processor here // Remove after inserting ISR Code asm (" ESTOP0"); for(;;); } PIE Peripheral Interrupt Expansion Registers PIECTRL 0x0D81 PIE, Control Register [Memory Mapped] PIEACK 0x0009 PIE, Acknowledge Register [Memory Mapped] PIEIER1 0x0048 PIE, INT1 Group Enable Register [Memory Mapped] PIEIFR1 0x0029 PIE, INT1 Group Flag Register [Memory Mapped] PIEIER2 0x0000 PIE, INT2 Group Enable Register [Memory Mapped] PIEIFR2 0x0000 PIE, INT2 Group Flag Register [Memory Mapped] PIEIER3 0x0000 PIE, INT3 Group Enable Register [Memory Mapped] PIEIFR3 0x0000 PIE, INT3 Group Flag Register [Memory Mapped] PIEIER4 0x0003 PIE, INT4 Group Enable Register [Memory Mapped] PIEIFR4 0x0003 PIE, INT4 Group Flag Register [Memory Mapped] PIEIER5 0x0000 PIE, INT5 Group Enable Register [Memory Mapped] PIEIFR5 0x0000 PIE, INT5 Group Flag Register [Memory Mapped] PIEIER6 0x0000 PIE, INT6 Group Enable Register [Memory Mapped] PIEIFR6 0x0000 PIE, INT6 Group Flag Register [Memory Mapped] PIEIER7 0x0018 PIE, INT7 Group Enable Register [Memory Mapped] PIEIFR7 0x0000 PIE, INT7 Group Flag Register [Memory Mapped] PIEIER8 0x0003 PIE, INT8 Group Enable Register [Memory Mapped] PIEIFR8 0x0000 PIE, INT8 Group Flag Register [Memory Mapped] PIEIER9 0x000C PIE, INT9 Group Enable Register [Memory Mapped] PIEIFR9 0x0000 PIE, INT9 Group Flag Register [Memory Mapped] PIEIER10 0x0001 PIE, INT10 Group Enable Register [Memory Mapped] PIEIFR10 0x0000 PIE, INT10 Group Flag Register [Memory Mapped] PIEIER11 0x0000 PIE, INT11 Group Enable Register [Memory Mapped] PIEIFR11 0x0000 PIE, INT11 Group Flag Register [Memory Mapped] PIEIER12 0x0000 PIE, INT12 Group Enable Register [Memory Mapped] PIEIFR12 0x0000 PIE, INT12 Group Flag Register [Memory Mapped] eQEP2 eQEP2 Registers QPOSCNT 0x00000000 eQEP Position Counter [Memory Mapped] QPOSINIT 0x00000000 eQEP Initialization Position Count [Memory Mapped] QPOSMAX 0x00000000 eQEP Maximum Position Count [Memory Mapped] QPOSCMP 0x00000000 eQEP Position-compare [Memory Mapped] QPOSILAT 0x00000000 eQEP Index Position Latch [Memory Mapped] QPOSSLAT 0x00000000 eQEP Strobe Position Latch [Memory Mapped] QPOSLAT 0x00000000 eQEP Position Latch [Memory Mapped] QUTMR 0x00000000 eQEP Unit Timer [Memory Mapped] QUPRD 0x00000000 eQEP Unit Period Register [Memory Mapped] QWDTMR 0x0000 eQEP Watchdog Timer [Memory Mapped] QWDPRD 0x0000 eQEP Watchdog Period Register [Memory Mapped] QDECCTL 0x0000 eQEP Decoder Control Register [Memory Mapped] QEPCTL 0x0000 eQEP Control Register [Memory Mapped] QCAPCTL 0x0000 eQEP Capture Control Register [Memory Mapped] QPOSCTL 0x0000 eQEP Position-compare Control Register [Memory Mapped] QEINT 0x0000 eQEP Interrupt Enable Register [Memory Mapped] QFLG 0x0000 eQEP Interrupt Flag Register [Memory Mapped] QCLR 0x0000 eQEP Interrupt Clear Register [Memory Mapped] QFRC 0x0000 eQEP Interrupt Force Register [Memory Mapped] QEPSTS 0x0000 eQEP Status Register [Memory Mapped] QCTMR 0x0000 eQEP Capture Timer [Memory Mapped] QCPRD 0x0000 eQEP Capture Period Register [Memory Mapped] QCTMRLAT 0x0000 eQEP Capture Timer Latch [Memory Mapped] QCPRDLAT 0x0000 eQEP Capture Period Latch [Memory Mapped] SYSCTRL System Control Registers PLLSTS 0x0101 PLL Status Register [Memory Mapped] HISPCP 0x0006 High-Speed Peripheral Clock Pre-Scaler Register [Memory Mapped] LOSPCP 0x0004 Low-Speed Peripheral Clock Pre-Scaler Register [Memory Mapped] PCLKCR0 0xC818 Peripheral Clock Control Register 0 [Memory Mapped] PCLKCR1 0x0300 Peripheral Clock Control Register 1 [Memory Mapped] LPMCR0 0x00FC Low Power Mode Control Register 0 [Memory Mapped] PCLKCR3 0x3F00 Peripheral Clock Control Register 3 [Memory Mapped] PLLCR 0x000A PLL Control Register [Memory Mapped] SCSR 0x0005 System Control and Status Register [Memory Mapped] WDCNTR 0x0000 Watchdog Counter Register [Memory Mapped] WDKEY 0x00C0 Watchdog Reset Key Register [Memory Mapped] WDCR 0x00C0 Watchdog Control Register [Memory Mapped] MAPCNF 0x0000 ePWM/HRPWM Re-map Register [Memory Mapped] DEVEMU Device Emulation Registers DEVICECNF 0x080F006B Device Configuration Register [Memory Mapped] CLASSID 0x00EF Class ID Register [Memory Mapped] REVID 0x0001 Revision ID Register [Memory Mapped] PROTSTART 0x0100 Block Protection Start Address Register [Memory Mapped] PROTRANGE 0x00FF Block Protection Range Address Register [Memory Mapped] PARTID 0x00EF Part ID Register [Memory Mapped] Core Registers Core Registers ACC 0xD800014F Accumulator [Core] P 0x0000014F Product Register [Core] XT 0x001500AD Multiplicand Register [Core] XAR0 0x00000000 Auxiliary Register 0 [Core] XAR1 0x0000FFFF Auxiliary Register 1 [Core] XAR2 0x00000000 Auxiliary Register 2 [Core] XAR3 0x00000000 Auxiliary Register 3 [Core] XAR4 0x00006208 Auxiliary Register 4 [Core] XAR5 0x00000066 Auxiliary Register 5 [Core] XAR6 0x00000001 Auxiliary Register 6 [Core] XAR7 0x0000CEC0 Auxiliary Register 7 [Core] PC 0x3078E2 Program Counter [Core] RPC 0x0063A8 Return Program Counter [Core] ST0 0x00EC Status Register 0 [Core] ST1 0x8A1B Status Register 1 [Core] DP 0x033E Data-Page Pointer [Core] SP 0x0096 Stack Pointer [Core] IER 0x0000 Interrupt Enable Register [Core] IFR 0x0000 Interrupt Flag Register [Core] DBGIER 0x0000 Debug Interrupt Enable Register [Core] STF 0x00000628 Status Register for FPU [Memory Mapped] R0L 0x00000000 Floating Point Unit R0L [Memory Mapped] R0H 0xCB80014F Floating Point Unit R0H [Memory Mapped] R1L 0x00000000 Floating Point Unit R1L [Memory Mapped] R1H 0x43350000 Floating Point Unit R1H [Memory Mapped] R2L 0x00000000 Floating Point Unit R2L [Memory Mapped] R2H 0x00000000 Floating Point Unit R2H [Memory Mapped] R3L 0x00000000 Floating Point Unit R3L [Memory Mapped] R3H 0x00000000 Floating Point Unit R3H [Memory Mapped] R4L 0x00000000 Floating Point Unit R4L [Memory Mapped] R4H 0x00000000 Floating Point Unit R4H [Memory Mapped] R5L 0x00000000 Floating Point Unit R5L [Memory Mapped] R5H 0x00000000 Floating Point Unit R5H [Memory Mapped] R6L 0x00000000 Floating Point Unit R6L [Memory Mapped] R6H 0x00000000 Floating Point Unit R6H [Memory Mapped] R7L 0x00000000 Floating Point Unit R7L [Memory Mapped] R7H 0x00000000 Floating Point Unit R7H [Memory Mapped] RB 0x00000000 Repeat Block Register [Memory Mapped]
↧
Forum Post: TMS320F28335: Debugger stopping in EQEP1_INT_ISR after pressing suspend while debugging code
↧
Forum Post: Support needed to select a MSP340 product family for measuring the IC curve for solar cells for space applications
Hello, I want to build a circuit that measure the IV curve of a solar cell. The solar cells are new concept and the aim is measure the performance of the cells (measuring the IV curve) in space. I am planning to use MSP340 Microcontroller. The first draft of my circuit design (not yet the final version and recommendations are welcomed) is to control a Precision Current Sink (PCS) using one of the MSP340 boards. Basically, the PCS will apply voltage across the cell, and sweep over the whole IV curve. Therefore, the MSP340 will control the applied voltage and the sweeping process. Once a solar irradiance strike the cell, a current will be generated at a given voltage data point. I will also have a temperature sensor, so that my final reading will be I - V - T. The generated current will flow over a Precision Instrumentation Amplifier (PIA), and it will read the current in an analog form. To digitize it, I will need a ADC. The digitized reading through the PIA will be sent to the on board computer using a Controller Area Network (CAN). The onboard computer will then send the data ( digitized reading of the current, voltage across the cell, and the temperature) to earth. My questions are as follow: I know that some MSPs has an ADC. Do I need an external ADC for my application? Which MSP fits my application? Any other recommendations to perform the tasks (measuring the IV curve of a solar cell and measuring the corresponding cells temperature in the space environment) other than the above design description? As mentioned above, I will use a PSC, PIA, ADC and a CAN along with the MSP340. Do you think this will be sufficient? Do I need to have a microprocessor? if so, for what purpose? Thank you for your time Ghanim
↧
↧
Forum Post: MSP430F5514: Connections for using UART-BSL using BSL Scripter Tool
Part Number: MSP430F5514 I want to use UART to interact with the BSL to update the firmware. The suggested pin-connection is this. I am not using the launchpad. From what I understand the connection to the TEST and RESET pins is to invoke the BSL. I can, however, use the software option to invoke the BSL by using the line - ((void (*)())0x1000)(); In this case, can I just use a USB-UART converter(FTDI232)/FET with just the Rx, Tx and GND connections as in normal UART communication?
↧
Forum Post: Compiler/TMS320F28379D: Trying to save code space - memory.c functions included in our compiled & linked code
Part Number: TMS320F28379D Tool/software: TI C/C++ Compiler We have run out of flash space in the designated area of flash for a specific purpose. In this case, our custom boot loader. We are using c++ classes although all objects are static objects and nothing is created dynamically. In our coding technique, we have been extra careful as not use malloc, memcpy etc. However, looking at the generated MAP file, there is at least 512 words consumed by rts2800_fpu32.lib: memory.c.obj. I also noticed that there are functions that we don't need or specify as shown below: 0 00080536 _main 0 000801c9 _malloc 0 000802d9 _max_free 0 00080b29 _memcpy 0 000801a4 _minit 1 00000028 _outFlashStatus 0 00080024 _ram_init 0 00080227 _realloc I looked at the boot28.asm and none of the memory.c functions are being invoked. Question: where are they coming from and how can we save valuable space?
↧
Forum Post: CCS/TMS320F28379D: DAC A OUTPUT UPDATE
Part Number: TMS320F28379D Tool/software: Code Composer Studio Good day, I am using the ADC SOC EPWM example in which I added DAC configuration in order to test the ADC to DAC circuit. I could verify that that the circuit works well, but the DAC output seems not to update the output once I change the ADC input. I verified that the new ADC value is updated in the Registers window. However the Expressions window keep the initial value. How do I make sure that the DAC ouput follows the ADC input ? Please follow below the interrupt command and the windows result interrupt void adca1_isr(void) { v_fonte = AdcaResultRegs.ADCRESULT0; v_recomp = v_fonte + 10; DAC_PTR[DAC_NUM]->DACVALS.all = v_recomp; }
↧
↧
Forum Post: TIDM-1000: Control isn't using Integral gain?
Part Number: TIDM-1000 Hello, According to the code, the control is only using proportional gain. Is that correct? What is the control equation? Stephen
↧
Forum Post: TMS320F28335: DSP is overcurrent and dies
Part Number: TMS320F28335 Hello everyone. I'm part of a research group and our area is Power Electronics. We decided to incorporate the DSP as a component once we needed access to the XINTF bus to establish communication with an FPGA. In this process we have experienced situations in which the DSP was electrically damaged and we're now trying to figure out what could be the root causes for the issue. 1st Occurrence: The equipment was turned off after a successful test exercise. The C2000 J-Tag programmer was left connected between the PC USB Port and the DSP J-Tag pins. In the following day, when the equipment was turned on, the DSP was no longer working and the 1.8V and 3.3V power inputs were draining more current than normal. The DSP was replaced and the equipment returned to normal operation. We established a new power-off procedure which consisted in disconnecting both, the C2000 J-Tag and the FPGA J-Tag programmers cables. This procedure seemed to work well for some time until we had the 2nd Occurrence. 2nd Occurrence: This situation was similar to the first one. In other words, we turned off after normal operation and, again, the DSP was not working when the equipment was turned on. Of, course, this time the programmers cables were disconnected. Symptoms were also the same, both power inputs drained more current than normal and the DSP was completely dead. Replacement of the DSP solved the problem. As an additional safety measure, although the digital circuit is galvanically isolated from the AC power line, we decided to disconnect the equipment from the power outlet after turned off. Since then, the DSP has been operating well and no further issues have been observed. 3rd Occurrence: The PCA was completely assembled following the same processes and procedures used in the first PCA (reflow soldering). As we started the bring-up procedures, during the first turn-on step, we observed over-current in the 1.8V power input. Disconnection of the power pins from the PCA circuit eliminates the over-current situation and the rest of the board goes back to normal operation. As an additional information that may help: - The DSPs used in the first board are samples provided by Texas. The DSP used in the second board was purchased from an authorized distributor. - Power to the DSP is provided by Texas LDOs (LM1117DT-1.8 and LM1117DT-3.3). No DC-DC converters. - We based our circuit in the reference guide supplied by Texas. We would like to understand: - Is this DSP more sensitive than average components of the same category? - Have you observed similar situations in other implementations using this component? - The electric safety measures we have taken are really necessary? Would you recommend anything different? - As far as the assembly process are there specific precautions, limits that we need to observe in order to avoid esd, thermal or mechanical stress. Thank you all.
↧
Forum Post: CCS/SM320F2812: Debugging on TMS320F2812 vs SM320F2812
Part Number: SM320F2812 Tool/software: Code Composer Studio Good Afternoon, We have been debugging/integrating on an eval board, ezdsptms320f2812 without issue and have recently switched to our tactical hardware which uses the SM320F2812HFGM150. We are receiving warnings related to unconfigured memory. It appears to flash the device successfully, however, it doesn't not appear to run properly. We have verified the XCLKIN and XCLKOUT are running 30MHz and 150Mhz respectively which indicates that it has run through the PLL setups and our initialization functions. In addition, the watchdog is not asserting as we would expect. Also, if we try to force a watchdog assertion, it is ignored. Is this anything we need to be aware of with the differences in parts that would cause these behaviors outside of the pinout and packaging differences? Vr, Dan
↧
Forum Post: CCS/MSP430FR2422: missing ctpl_msp430fr2422.c file
Part Number: MSP430FR2422 Tool/software: Code Composer Studio I've downloaded the FRAMUtilities_03_10_00_10_setup.exe expecting to find a copy of the ctpl_ msp430fr2422 .c file so I could use several of the FRAM utilities, but it seems to be missing. Any idea where I can get a configuration file for the MSP430FR2422 device?
↧
↧
Forum Post: CCS/MSP432P401R: MSP432 Multiple SPI Slave Devices in one SPI bus
Part Number: MSP432P401R Tool/software: Code Composer Studio Hi All I want to use a MSP432P401R to control two SPI slave devices in one SPI bus with separate chip select pins (other SPI buses on my 432 are occupied). Question/Problem I have no trouble to control these two devices when deploying my debug code from a launch pad to my final target (MSP432 on my PCB). However, when I stop debug in CCS, reboot the target MSP432 and my PCB, only one SPI slave device work. Trouble shooting steps 1. At the first, I wonder if the failed slave device takes long time after reset, I add some delay before calling the failed slave device, my problem still exists. 2. I swap the SPI calling order; the problem still exists. 3. I wonder if the code burning process does complete successfully; while all other devices controlled by the 432 on my PCB work. Part of My code const eUSCI_SPI_MasterConfig spiMasterConfigADF4351 = { EUSCI_A_SPI_CLOCKSOURCE_SMCLK, // SMCLK Clock Source 3000000, // SMCLK = DCO = 3MHZ 500000, // SPICLK = 500khz EUSCI_A_SPI_MSB_FIRST, // MSB First EUSCI_A_SPI_PHASE_DATA_CAPTURED_ONFIRST_CHANGED_ON_NEXT, EUSCI_A_SPI_CLOCKPOLARITY_INACTIVITY_LOW, // CLK low when SPI not enabled for ADF4351 EUSCI_A_SPI_3PIN // 3Wire SPI Mode }; const eUSCI_SPI_MasterConfig spiMasterConfigAD8366 = { EUSCI_A_SPI_CLOCKSOURCE_SMCLK, // SMCLK Clock Source 3000000, // SMCLK = DCO = 3MHZ 500000, // SPICLK = 500khz EUSCI_A_SPI_MSB_FIRST, // MSB First EUSCI_A_SPI_PHASE_DATA_CHANGED_ONFIRST_CAPTURED_ON_NEXT, // Phase //EUSCI_A_SPI_PHASE_DATA_CAPTURED_ONFIRST_CHANGED_ON_NEXT, EUSCI_A_SPI_CLOCKPOLARITY_INACTIVITY_LOW, // High polarity EUSCI_A_SPI_3PIN // 3Wire SPI Mode }; // Typical 3 pin SPI initialization GPIO_setAsPeripheralModuleFunctionInputPin(ADF4351_SPIPort, ADF4351_SPICLK | ADF4351_SPISIMO | ADF4351_SPISOMI, GPIO_PRIMARY_MODULE_FUNCTION); SPI_initMaster(ADF4351_SPI, &spiMasterConfigADF4351); SPI_enableModule(ADF4351_SPI); GPIO_setAsOutputPin(ADF4351_CSPort, ADF4351_CSPin); // set chip select high as default value GPIO_setOutputHighOnPin(ADF4351_CSPort, ADF4351_CSPin); GPIO_setAsOutputPin(AD8366_CSPort, AD8366_CSPin); adf4351_initialization (ADF4351_SPI, ADF4351_CSPort, ADF4351_CSPin); SPI_disableModule(ADF4351_SPI); // re-config SPI since SPI master configurations of the two devices are different GPIO_setAsPeripheralModuleFunctionInputPin(AD8366_SPIPort, AD8366_SPICLK | AD8366_SPISIMO | AD8366_SPISOMI, GPIO_PRIMARY_MODULE_FUNCTION); SPI_initMaster(AD8366_SPI, &spiMasterConfigAD8366); SPI_enableModule(AD8366_SPI); AD8366_Set_Gain (4500, 4500, AD8366_SPI, AD8366_CSPort, AD8366_CSPin); PS. Software platform CCS 8.3.0.0009 Hardware: MSP432P401R launch pad -> JATG -> target MSP432P401R
↧
Forum Post: SAFETI-HALCOGEN-CSP: is there any platforms that can run test cases even before the target board is available?
Part Number: SAFETI-HALCOGEN-CSP Hello, I have to wait the target board design/manufacturing to run the test cases based on CSP for HALCoGen , right? Any recommended approach (ex. use of simulator)? HALCoGen CSP User's Guide mentions TAU provides capability to add our own test cases. I plan to use TAU for testing additional codes developed by ourselves, not only HALCoGen-generated source codes. The target microcontroller is TMS570LC4357-EP. Best regards, Akai
↧
Forum Post: TMS320F28377S: can TMS320F28377S support CLB?
Part Number: TMS320F28377S Hi, I am confusing about the description of CLB for TMS320F28377S . in website, it mentions CLB in features, but in datasheet it said it's not ok for TMS320F28377S . Can you confirm that for me? If it's not ok, could you give me a C2000 device list which has CLB? Thank you! Yuan
↧
Forum Post: TMS320F28062: TMS320F28062 input I/O port not respond to the input voltage or control signal?
Part Number: TMS320F28062 Dear all: Customer used TMS320F28062 for BLDC driver. In mass-produced product testing, it was found that when the DSP may work for several days, It may occur that all input I/O port no longer respond to the input circuit voltage or control signal, and the communication, output, and other parts can work normally. What is the cause? can you give some advice? By the way, Can I provide the output status of the I/O port when the DSP is not programmed or When the power-on, thanks!
↧
↧
Forum Post: CCS/CCSTUDIO-C2000: TMS320F28035 TMS320F28379D
Part Number: CCSTUDIO-C2000 Tool/software: Code Composer Studio Dear sir, I can't find the TIDM-1001 and TIDM-2PHILPFC software source code. TIDM-1001 : http://www.ti.com/tool/TIDM-1001?keyMatch=TIDM-1001&tisearch=Search-EN-Everything TIDM-2PHILPFC : http://www.ti.com/tool/TIDM-2PHILPFC Please help me to solve the problems. Thanks!
↧
Forum Post: TMS320F28388D: No SYNC0 received running CPU1_Echoback_Solution demo codes
Part Number: TMS320F28388D Hello Champs, Customer is testing "f2838x_cpu1_echoback_solution" demo codes in below folder: C:\ti\ C2000Ware _2_00_00_02\libraries\communications\Ethercat\f2838x\examples\f2838x_cpu1_echoback_solution They found that after enabling "DC_SYNC" in TwinCAT, there will be below errors shown: Box 1 (F2838x CPU1 etherCAT (1001): 'SAFEOP to OP' failed! Error: 'check device state for OP'. Al Status '0x0014' read and '0x0008' expected. Al status Code '0x002d' - no SYNC0 or SYNC1 received. Would you please kindly help? Thanks! Best Regards, Linda
↧
Forum Post: MSP430F5636: MSP430F5636IZQW is LIFEBUY. What should I introduce instead of MSP430F5636IZQW?
Part Number: MSP430F5636 My customer uses MSP430F5636IZQW (MicroStar BGA), but MSP430F5636IZQW has become LIFEBUY. I saw TI.com and datasheets, but the other MicroStar BGA packages are Active. So I have a question. What should I introduce instead of MSP430F5636 IZQW? May I introduce the F563x series Microstar BGA? Best Regard, Nori
↧
Forum Post: CCS/TMS570LC4357: [TMS570LC43x] Why Ti safety library defines this MCU as little endian system?.
Part Number: TMS570LC4357 Tool/software: Code Composer Studio hello in order to develop spi devices, i have been worked for spi implement. and i can find a bug(maybe) at HL_sys_common.h (demo_app\ HALCoGen \ TMS570LC4357 _NoOS\include) Ti reference manual for TMS570LC43 indicate this system have BE32(big endian). but, little endian is defined at HL_sys_common.h. and mibspi rambase struct include member variable in little endian method. Could you please check this? thanks
↧
↧
Forum Post: TMS320F280041: TMS320F280049C binary compatability
Part Number: TMS320F280041 Hi E2E, Good day! May I know if the binary compiled for TMS320F280049C is compatible with TMS320F280041 ? Thank you for your usual support. Best regards, Franz
↧
Forum Post: LAUNCHXL2-RM57L: Can't read 10-15 Mc/s pulses of 35 nanosecond pulse width, suggest a counter IC
Part Number: LAUNCHXL2-RM57L Hey, everyone! My application involves counting of high speed (10-15 Mc/s) digital pulses, coming from a single photon counting module (SPCM-AQR). The pulse width is 35 nanoseconds. I had bought Hercules RM57Lx LaunchPad for the same purpose but it cannot count such precise pulses. Please, suggest me a counter IC which I can use with the RM57Lx board for my purpose. I need to count every 5 microseconds. Thanks in advance. Regards, Apurv
↧
Forum Post: MSP430FR2433: Why driverlib guide says slave and shows master i2c api
Part Number: MSP430FR2433 Hello, In reading through the driver lib api for the latest mspware file pack I've noticed something I don't understand. Why does the bottom section in text refer to slave function calls / api, but the actual function call names are shown as "master". Image attached showing this.
↧